02-02-2017 06:54 AM
266 ... 56789 ...
tools
  1. bigsupersquid's Avatar
    post the errors you're getting and I'll look when I get back from the store.
    10-25-2011 06:57 PM
  2. BLoux89's Avatar
    ok so im going to show you every prompt you told me to type in followed by the messages that followed afterward:

    adb shell strings /dev/mtd/mtd8
    - FACT_RESET_3

    adb shell flash_eraseall /dev/mtd/mtd8
    - /sbin/sh: flash_eraseall: not found

    adb reboot recovery
    - no text (phone just restarts)

    adb shell mount /dev/block/mmcblk0p1 /sdcard
    -no text

    adb push xionia_cwma_125186.img /sdcard/
    -cannot stat 'xionia_cwma_125186.img': no such file or directory

    adb shell
    -~#

    flash_image recovery /sdcard/xionia_cwma_125186.img
    -failed with error: -1 error opening /sdcard/xionia_cwma_1251686.img

    and then back to "~#"

    any other suggestions?
    10-25-2011 07:51 PM
  3. bigsupersquid's Avatar
    ok so im going to show you every prompt you told me to type in followed by the messages that followed afterward:

    adb shell strings /dev/mtd/mtd8
    - FACT_RESET_3
    adb is working, and your phone is in a factory reset bootloop. The custom recoveries don't support the factory reset, and just reboot into recovery until you clear mtd8.
    adb shell flash_eraseall /dev/mtd/mtd8
    - /sbin/sh: flash_eraseall: not found
    the flash_eraseall utility is not included in your recovery.
    I'll have to dig it out of xionia recovery, it'll take me a bit.

    adb reboot recovery
    - no text (phone just restarts)
    that worked correctly.

    adb shell mount /dev/block/mmcblk0p1 /sdcard
    -no text
    the sdcard mount didn't cause an error, so it's probably mounted.

    adb push xionia_cwma_125186.img /sdcard/
    -cannot stat 'xionia_cwma_125186.img': no such file or directory
    the xionia .img is not in the platform_tools directory with adb, or the command prompt is in another directory and adb is in your system path.

    adb shell
    -~#

    flash_image recovery /sdcard/xionia_cwma_125186.img
    -failed with error: -1 error opening /sdcard/xionia_cwma_1251686.img
    since it couldn't be pushed, it's not there for flash_image to flash.

    and then back to "~#"

    any other suggestions?
    give me a little bit to find the flash_eraseall, or if you can get the xionia recovery installed with adb, then it has a 'fix bootloop' option, or you can use the adb shell flash_eraseall /dev/mtd/mtd8 if the menu option fails.
    you'll need the xionia .img file in the directory you're running the command prompt from to be able to push it to the sdcard and flash it.
    once you get that done, it gets a lot easier.
    10-25-2011 08:24 PM
  4. BLoux89's Avatar
    idk man, i got Xionia right where it needs to be and it just isnt complying with me... this is tough. definitely making a little progress compared to earlier.
    10-25-2011 08:45 PM
  5. bigsupersquid's Avatar
    if you type
    Code:
    dir
    in the dos prompt, does it show the recovery img?
    if not, the file needs moved to whatever the path is on the command line.
    10-25-2011 08:47 PM
  6. BLoux89's Avatar
    i definitely did it right because the 'push' and 'flash' both complied with me... multiple lines appeared that read "mtd: successfully wrote block at c2a7800..." but the screen on my phone is still black and the command prompt reads '~#' now... what do i do from here?
    10-25-2011 08:55 PM
  7. BLoux89's Avatar
    well bigsupersquid... the journey is over... my phone is back on. thank you SO SO MUCH for all your help throughout this hectic, nerve-racking day! you're a good man squiddy lol!
    10-25-2011 08:59 PM
  8. chacodroid's Avatar
    Hi super squid,

    Thank you for your postings. I recently purchased a new Optimus V for Virgin. After downloading Gingerbreak and getting root access I downloaded ROM manager premium and backed up the ROM and then flashed to aspoc(?). During the reboot I got stuck on the android logo. Since then I came across this post to unbrick it.

    Right now I can get the adb shell to recognize the phone but not see the sd card. I tried your boot method and pulled the card before pressing and holding home, volume up, power. When it boots in to the black screen I put the card back in and run the adb shell. Card still not found.

    Suggestions?
    10-31-2011 07:09 PM
  9. bigsupersquid's Avatar
    insert the card and
    Code:
    adb shell mount /dev/block/mmcblk0p1 /sdcard
    to mount it.
    then follow the recovery flashing instructions.
    I suggest the new iho recovery by BobZhome for any current roms... aospCmod is no longer supported.
    (like Harmonia or harmonious bumblebee, for froyo, or an inferior human organs ROM for gingerbread.)
    10-31-2011 09:33 PM
  10. Kelemvor33's Avatar
    Is there a way to tell which screen I have before I start the root process so I know what to expect?
    11-04-2011 12:14 PM
  11. dwappo's Avatar
    Depends when you bought it. I bought mine like 4 months ago, and it had that problem.
    11-04-2011 12:53 PM
  12. Kelemvor33's Avatar
    Is there a setting or something that I can check on the phone to tell under About or anything? Or two phones look identical in all the settings even if they have different screens.

    I bought mine earlier this summer as well at Target. Who knows how long it might have been sitting in a warehouse. heh.
    bigsupersquid likes this.
    11-04-2011 02:26 PM
  13. bigsupersquid's Avatar
    Is there a setting or something that I can check on the phone to tell under About or anything? Or two phones look identical in all the settings even if they have different screens.

    I bought mine earlier this summer as well at Target. Who knows how long it might have been sitting in a warehouse. heh.
    if you have froyo 2.2.1 instead of 2.2.2, you have an old novatek screen for sure.
    if it's got 2.2.2, it could be either one.
    I'm not sure if this'll work in the stock rom, test it for me and see, and let us know. if it works I'll add it to the first post.
    download terminal emulator from market.
    open it...
    type
    Code:
    dmesg | grep novatek
    if you see any output other than an error, it should be a couple of lines with novatek in them; if so, you have the old screen type.
    if it doesn't give you any output, or an error, type
    Code:
    dmesg | grep hitachi
    if you see any output other than an error, it should be a couple of lines with hitachi in them; if so, you have the new screen type.

    if you get an error, toolbox probably doesn't handle grep.
    then try
    Code:
    dmesg > /sdcard/dmesg.txt
    then you can close the terminal.
    look through dmesg.txt (on your sdcard) for hitachi or novatek, somewhat near the top of the file. whichever you find is the screen type you have.
    11-04-2011 03:09 PM
  14. Kelemvor33's Avatar
    grep: permission denied
    write: Broken pipe

    Didn't find any Hitachi references but found this:
    mddi_novatek_lcd_on: started.

    So that should mean I'm good to go right?
    11-04-2011 03:46 PM
  15. bigsupersquid's Avatar
    yep. you can use whatever recovery and ROM you want.
    pinocytosis likes this.
    11-04-2011 06:08 PM
  16. dhaliwood's Avatar
    hell squid im having some difficulties installing a recovery on my optimus v. its currently running cyangenmod 7 2.3.3. whenever i try to boot into recovery its just a black screen and have to remove my battery for it work again. ive tried using the terminal and adb shell but no luck there.
    i want to restore my phone back to the way it was when i bought it because it dosnt have the android market and all the google apps. if you can help me i would appreciate it ive been up for three days trying to figure this out and its killing me!!

    i have a 8gb sdhc card and its rooted.
    when i go to adb shell and type the commands in to flash the recovery on the second line
    cat /sdcard/flash_image > /system/bin/flash_image-- it says directory not found when it clearly is on the card.
    please help!
    11-13-2011 07:35 PM
  17. bigsupersquid's Avatar
    I've read that flash_image GUI
    [APP] Flash Image GUI - xda-developers
    works for installing recovery if your ROM isn't broken too.
    use the bobzhome iho recovery, and once it's installed and working, install the gapps.zip (linked in the iho wiki) and you'll have market and it'll download the gapps.
    11-14-2011 08:54 AM
  18. mewikime's Avatar
    Hi, I need some help because I entered into the Black Screen mode on my new 2.2.2 phone while trying to flash Harmonia 1.7. I used Gingerbreak to root the phone and installed Terminal Emulator from the market.

    I put flash_image and xionia_cwma_12518.4_virgin.img on the root of the SD card, changing the name of xionia to recovery.img so it would be easier to type in the Emulator.

    In Emulator I typed

    su
    mount -o remount,rw -t yaffs2 /system /system
    cat /sdcard/flash_image > /system/bin/flash_image
    chmod 755 /system/bin/flash_image
    flash_image recovery /sdcard/recovery.img
    reboot recovery


    Everything seemed to go fine. In recovery, I did
    1. a nandroid backup
    2. wiped cache
    3. wiped dalvic cache
    4. wiped data/factory reset
    5. formatted boot
    6. formatted system
    7. formatted data
    8. formatted cache
    9. flashed the harmonia 1.7 zip

    Everything here went okay too, when I went to "Reboot system now" I got the black screen after the LG logo.

    I pulled the battery out, and I was able to reenter recovery by using the home, vol down and power button and just to try it I restored my nandroid from when I previously did a backup. Luckily my phone booted back up just fine, and I've rebooted a couple of times just to make sure it still works.

    So where do I go from here with regards to flashing Harmonia 1.7? Did I use the wrong Xionia? What did I do wrong that made it enter the blackscreen mode? TIA for any help

    Also, I installed busybox by Stephen (Stericson), but there's also Busybox Installer app by JRummy16. Do I need the other one, and if so, what version? What does busybox do?
    11-27-2011 04:05 PM
  19. bigsupersquid's Avatar
    sometimes harmonia doesn't flash the boot.img right for some reason.
    you can install the picasticks remix kernel zip in the first post of this thread to fix it.
    download it to your card, and install the zip file from recovery like you did the rom.
    that should take care of it.
    mewikime likes this.
    11-27-2011 05:46 PM
  20. mewikime's Avatar
    sometimes harmonia doesn't flash the boot.img right for some reason.
    you can install the picasticks remix kernel zip in the first post of this thread to fix it.
    download it to your card, and install the zip file from recovery like you did the rom.
    that should take care of it.
    Thanks for replying, BSS. OK, so now that I'm currently operating stock again, I just go into recovery, wipe everything again, install Harmonia and then Picasticks remix, or Picasticks first then Harmonia? And how do I turn "signature verification" off?

    And should I update from xionia_cwma_12518.4_virgin.img to xionia_cwma_12518.6.img ?
    11-27-2011 06:03 PM
  21. bigsupersquid's Avatar
    if you can see the recovery, the version you're using is fine.
    wipe, install harmonia, then the kernel.
    the signature verification toggle is under the install zip menu in recovery.
    mewikime likes this.
    11-27-2011 07:52 PM
  22. mewikime's Avatar
    OK, well Picasticks remix worked, after I figured out how to turn of signature verification! lol I left xionia as it was.

    Thanks, BigSuperSquid!
    11-27-2011 08:46 PM
  23. StikX420's Avatar
    I'm having the same issue. Normal Boot Seems like it wants to boot fine Boots to the Android splash screen and Goes to a black screen maybe 20 seconds after. Recovery boots lg splash screen and goes black almost immediately. When I connect it to the laptop, ADB recognizes it in the device list but says its "Offline" any ideas?
    11-29-2011 04:55 AM
  24. bigsupersquid's Avatar
    try adb while booted into the blacked-out recovery?
    if it gets to the Android splash on a regular boot, the boot.img kernel is compatible with your screen, and it's having other problems with the rom than the kernel drivers.
    StikX420 likes this.
    11-29-2011 07:33 AM
  25. StikX420's Avatar
    tried that... while in recovery mode ADB nor the comp recognized the phone.
    11-30-2011 02:28 AM
266 ... 56789 ...
LINK TO POST COPIED TO CLIPBOARD