Related
Hello All,
I am completely stuck after trying to fix my girlfriend's phone.
S-Off
HBOOT 6.13.1002
Radio 0.99.01.0225_2
eMMC-boot
___________________________
The phone was rooted over a year ago (not by me). I flashed the HTC12-MROM found here:http://forum.xda-developers.com/showthread.php?t=1892450
The ROM was recently updated, so I did a nandroid backup and tried installing the new rom zip. When I tried to format and wipe the system, everything went to hell.
Whenever I tried to format system, wipe data/cache, I got these messages:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I also got messages saying:
error formatting /cache!
error formatting /data
I tried just rebooting the phone, but got stuck in bootloops.
I pulled the battery, tried to do a factory reset, but still got stuck in bootloops.
My genius idea was to try to unroot and take it to a verizon store. No such luck.
I used this guide to try to unroot. http://theunlockr.com/2011/10/14/how-to-unroot-and-return-the-droid-incredible-2-back-to-stock/ I got through Step 1 and flashed the stock ROM file, but the phone was still bootlooping.
I pulled the battery and tried to get into CWM, but the screen goes to a generic phone with a red triangle and exclamation point. If I try to simply reboot the phone, it says "updating software..." but does not move. It's been in this position for at least a half hour.
Can anyone suggest a fix? I can still get into HBOOT. I want to fix this or get it back to stock so I can bring it to Verizon.
Thanks in advance for your help.
That's one of the oldest RUU (Froyo) file from VZW - you might want to try flashing a newer GingerBread RUU from your computer to the DI2 via micro-usb cable. Boot into Bootloader (HBoot) first - make sure that the PC recognize it in USB (nothing like "unknown" or errors reading device, etc.)
http://www.androidfiles.org/ruu/sec....01.1111_NV_VZW1.92_release_225831_signed.exe
Download & flash it, follow the prompts and it should restore your device to stock unrooted condition, then it's a matter of unrooting it again & pushing CWM (with 'adb")
Let it bootup initially and go thru the setup - most likely, you will need to (Re)Activate it OTA again, download/update PRL's - if you can make outgoing call and receiving incoming call, got working 3G/Evdo data and WiFi - it's good to go. If NOT, you will need to call VZW tech support at #8899 [Send/Call] as they will need to take steps to restore your device's security settings (i.e.. "A" keys, etc.) on their end and have you power cycle the device 2 or3 times, get you to make a successful test call, etc.
As for that continuous bootlooping while it's in bootloading mode, it might be a PG32IMG.zip file on the mSD card, pull the Sim card & use a PC to rename and/or delete it, that should help stop the endless loop and help launch it into bootloader and/or recovery.
Thanks for getting back to me. How exactly do I flash this? I can only get into HBOOT. Should I rename this file PG32IMG.zip and put it on the base of the SD?
EDIT
That was a completely retarded question. I figure I can use a cmd prompt to flash this, however, I don't think I've ever had to do that. Can you walk me through it?
Thanks again!
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator). It installed completely fine, but still bootloops. Gets to the red droid eye then boots back to the white HTC screen. It's still not loading.
Any other ideas?
double zero said:
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator) ... It's still not loading. Any other ideas?
Click to expand...
Click to collapse
Okay, let's try to get it stop the bootlooping first. Pull out the mSD card & VZW's Sim card too, if installed after taking out the battery. Let it sit for a minute + and re-insert battery only. Power on while holding the Volume Down key only to get it into Bootloader mode - press the Power key to confirm and you should be in HBoot, move down to Factory Reset and press it.
Next, try to go into Recovery screen from HBoot menu and see if you can see the HTC/factory recovery menu (if the RUU was installed, your previous CWM or TWRP should be gone)
Reconnect via mUSB cable to the PC, and clean flash the RUU again - do NOT put the mSD card back in the side slot yet. Let's see (and hope) if it will continue to setup all the way to finish (HTC activation screen) without bootloop or freezing at the white HTC screen.
The other option is to manually flash things using ADB tools (factory Images - system.img and recovery.img, etc.) that's probably beyond your skills ?? as the file systems, bootloader, etc. were likely corrupted & damaged. There are details / guides & steps-by-steps on how to do it in the Development sub-section ...
Let's see if these ideas will work for your devices and if not ... unless someone else "cruising" here has further tips, your device is almost fully restored back to stock to bring back to Big Red for help, IF and if ...
I pulled the SD and Sim Card as you suggested and got it into HBOOT. I hit "Factory Reset" and the phone eventually went into the white HTC screen (and did not move).
I pulled the battery, went back into HBOOT and scrolled down to Recovery. However the phone is stuck at the generic phone with red triangle/exclamation point.
Should I try to get into HBOOT and try to flash the RUU again?
double zero said:
... Should I try to get into HBOOT and try to flash the RUU again?
Click to expand...
Click to collapse
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Letitride said:
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Click to expand...
Click to collapse
Letitride,
I did exactly as you said, installed the RUU again (it said it was successful). I powered down and put into another microSD card I had (FAT formatted and completely blank). No luck. The phone only boots up to the Red Droid Eye, then reboots to White HTC screen, etc.
I also tried using the factory rom in PG32IMG.ZIP format, same thing. The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Thanks.
double zero said:
... The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Click to expand...
Click to collapse
DD - Here's XDA's Guide to ADB for your reference - http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
Link to VZW's RUU files (only used the ones on the bottom of the listed directory for VivoW - it's for DI2 http://www.androidfiles.org/ruu/?dir=Vivo_VivoW
The .1111 Radio flashed is different as shown on the Bootloader is different because it is from a different RUU/Rom build, it is one of the correct ones designed for the device - it is fine. Mine is using a .0312 radio and there is a newer radio with .0320 - they all worked in conjunction with the device, results varied depending on the hardware or build date - results varied.
Both of our DI2 are running fine on HBOOT 6.13.1002
Here is a link to one of the thread with a working HBOOT .96.2000 in ZIP format that you can download & flash from Bootloader - it might help reverse/downgrade to this older version from your existing/newer one - it might NOT work, however as yours is newer (post #37) - http://forum.xda-developers.com/showthread.php?t=1064366&page=4
Is it possible that the device was flashed with the leakded/unofficial RUU or IMG zip file released for China / CDMA-GSM and not meant for VZW's CDMA market ?? If so, it likely corrupted the file/root/boot structure ??
Were you able to do a Factory Reset inside the HBOOT menu ??
Also, do you see the HTC Recovery Menu as it should've been flashed onto the device ?
In any event, let's try doing a wipe of the device once you get into "ADB" with the following command prompt, once it's connected via USB
fastboot -w
Then, try running the RUU again (select this one from the list in the link) - without the new blank mSD card, and with the mSD card
Vivo_VivoW/RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_4.08.605.3_Radio_1.09.01.0722_NV_VZW1.92_release_212888_signed.exe
Add'l thoughts for DZ
Playing w N7 but thinking about your issues, with device still S-OFF (unlocked) - if nothing is working but you can still get into Bootloader, why not try (manually, via ADB if necessary) flash Custom Recovery (CWM or TWRP, whichever works) - boot into that - and, load the SuperDuperWipe script written by ChillyBean in a Zip file. That should do the deep cleansing and wiping to hopefully removed all the hidden files & bits/pieces left on the / or /SD directories that possibly contributed to all the issues you are experiencing - I don't believe it can reverse or rollback your HBOOT version to .97 or earlier (never tried it, maybe it will or it won't) At this point, it doesn't hurt to try or you have everything to gain ...
If the custom recovery & superwipe worked, then, try flashing the RUU again and see if it will boot up fully without looping? From there, you will have a good base, backup first and decide to load/restore custom rom, kernel or minor mods/tweaks ...
Meanwhile, hope you are reading up on ADB - it's a bit "scarely" doing it the first time, after a few command prompts & success - you will feel good about it.
Hi everyone let me start by saying this: I know what I did was a stupid stupid stupid nOOb mistake, but please understand It did not occur due to lack of reading or negligence to the formation of good understanding prior to rooting and flashing roms etc.
I should also point out that I have read as many other threads and articles on this subject as I can and have resorted to making my own thread ONLY because it is specifically unique to all those I have found elsewhere (including on this site).
Anyway, heres how hellish my last two days have been:
Rooted phone, went perfectly.
Flashed Cyanogenmod Nightly, went perfectly
Decided I wanted go back to stock until stable Cyanogenmod was released as it was too bug ridden for my usage.
This is where it got bad. I cannot remember for the life of me WHY I thought I needed to do this but when I went into Advanced Wipe (TWRP) options i ticked pretty much everything (I am extremely embarrassed and ashamed of this idiotic and reckless action *hangs head in shame*)
Needless to say, at this point I no longer had an OS, so I went about restoring the lot from my backup in TWRP:
Boot Restored fine
DATA restored fine
Cache Restored fine
System FAILED again and again no matter what I tried (literally 20 plus attempts)
At this point I tried flashing back to Cyanogenmod out of desperation but was met only with FAILED and words to the effect of "cannot read .zip file", I found the same message appearing no matter what ROM I tried to flash (I tried a variety of the more popular/stable roms to rule out corrupt data)
At this point I tried sideloading RUU which failed in a similar manner although I cannot remember the exact message)
Then after more pulling my hair out and reading everything I could about other people having similar problems, someone suggested I relock Bootloader before flashing an RUU. This didnt help at all and now I cant unlock Bootloader again, which leaves me unable to access Recovery
I am now at the point of mental breakdown (only slightly exaggerating here) after HOURS of reading and troubleshooting and now a full two days without a phone. I only got the phone 3 days ago so you can imagine how crappy I feel right now.
If any of the resident magicians can help me here I would be grateful beyond words One more thing, In one of the threads I read on another site, someone was suggesting to the OP that since RUU and ROM flashing wernt working, he may have "corrupted NVRAM (internal Storage), If my memory serves me correctly Im sure one of the Advanced Wipe option tick boxes was indeed 'internal storage'
Thanks for any advice. Tommy.
nOOb HTC Guy said:
Hi everyone let me start by saying this: I know what I did was a stupid stupid stupid nOOb mistake, but please understand It did not occur due to lack of reading or negligence to the formation of good understanding prior to rooting and flashing roms etc.
I should also point out that I have read as many other threads and articles on this subject as I can and have resorted to making my own thread ONLY because it is specifically unique to all those I have found elsewhere (including on this site).
Anyway, heres how hellish my last two days have been:
Rooted phone, went perfectly.
Flashed Cyanogenmod Nightly, went perfectly
Decided I wanted go back to stock until stable Cyanogenmod was released as it was too bug ridden for my usage.
This is where it got bad. I cannot remember for the life of me WHY I thought I needed to do this but when I went into Advanced Wipe (TWRP) options i ticked pretty much everything (I am extremely embarrassed and ashamed of this idiotic and reckless action *hangs head in shame*)
Needless to say, at this point I no longer had an OS, so I went about restoring the lot from my backup in TWRP:
Boot Restored fine
DATA restored fine
Cache Restored fine
System FAILED again and again no matter what I tried (literally 20 plus attempts)
At this point I tried flashing back to Cyanogenmod out of desperation but was met only with FAILED and words to the effect of "cannot read .zip file", I found the same message appearing no matter what ROM I tried to flash (I tried a variety of the more popular/stable roms to rule out corrupt data)
At this point I tried sideloading RUU which failed in a similar manner although I cannot remember the exact message)
Then after more pulling my hair out and reading everything I could about other people having similar problems, someone suggested I relock Bootloader before flashing an RUU. This didnt help at all and now I cant unlock Bootloader again, which leaves me unable to access Recovery
I am now at the point of mental breakdown (only slightly exaggerating here) after HOURS of reading and troubleshooting and now a full two days without a phone. I only got the phone 3 days ago so you can imagine how crappy I feel right now.
If any of the resident magicians can help me here I would be grateful beyond words One more thing, In one of the threads I read on another site, someone was suggesting to the OP that since RUU and ROM flashing wernt working, he may have "corrupted NVRAM (internal Storage), If my memory serves me correctly Im sure one of the Advanced Wipe option tick boxes was indeed 'internal storage'
Thanks for any advice. Tommy.
Click to expand...
Click to collapse
are you using the all in one tool kit to do all of this?
skinsfanbdh said:
are you using the all in one tool kit to do all of this?
Click to expand...
Click to collapse
Yes and btw Ive regained access to Recovery which is a step in the right direction, but still have all the same problems ie nothing will flash and cannot restore system etc.
nOOb HTC Guy said:
Yes and btw Ive regained access to Recovery which is a step in the right direction, but still have all the same problems ie nothing will flash and cannot restore system etc.
Click to expand...
Click to collapse
So you managed to unlock your bootloader again as well?
try using the all in one program to sideload a rom
Yer ive managed to unlock bootloader again. I have tried sideloading a variety of roms including the RUU and cyanogenmod. When attempting to sideload cyanogen mod, terminal simply bought up a loud of command lines and their meanings :S RUU however at least came up with the "sideloading" and percentage, gets to 100% and appears to finish, but nothing beyond that (I may be missing something im totally new to all of this) Cheers.
nOOb HTC Guy said:
Yer ive managed to unlock bootloader again. I have tried sideloading a variety of roms including the RUU and cyanogenmod. When attempting to sideload cyanogen mod, terminal simply bought up a loud of command lines and their meanings :S RUU however at least came up with the "sideloading" and percentage, gets to 100% and appears to finish, but nothing beyond that (I may be missing something im totally new to all of this) Cheers.
Click to expand...
Click to collapse
A ruu.exe is executed from the pc and not from the phone. Its useless to sideload it.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
nOOb HTC Guy said:
Yer ive managed to unlock bootloader again. I have tried sideloading a variety of roms including the RUU and cyanogenmod. When attempting to sideload cyanogen mod, terminal simply bought up a loud of command lines and their meanings :S RUU however at least came up with the "sideloading" and percentage, gets to 100% and appears to finish, but nothing beyond that (I may be missing something im totally new to all of this) Cheers.
Click to expand...
Click to collapse
If you got the a list with commands and their meanings then either a) You're not in sideloading mode or b) you didn't type the command properly.
I'm assuming you're still using TWRP, if so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload ...
Open a command prompt and change directory to adb.exe & fastboot.exe folder / or hold shift and right click in folder where adb.exe/fastboot.exe is and then choose open command window here. Make sure your device is connected to PC and then type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. If you're "hooked" up right and you can see the device serial number + sideload next to it, type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ ...I think you could use either, anyways, when finished flash as per usual.
BerndM14 said:
If you got the a list with commands and their meanings then either a) You're not in sideloading mode or b) you didn't type the command properly.
I'm assuming you're still using TWRP, if so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload ...
Open a command prompt and change directory to adb.exe & fastboot.exe folder / or hold shift and right click in folder where adb.exe/fastboot.exe is and then choose open command window here. Make sure your device is connected to PC and then type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. If you're "hooked" up right and you can see the device serial number + sideload next to it, type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ ...I think you could use either, anyways, when finished flash as per usual.
Click to expand...
Click to collapse
Okay so I tried sideloading with your instructions, which came up "failed" but actually had put "sideload.zip" in the directory, but when I tried to flash it I got the same old "error flashing zip"
Next I tried to push file, which comes up with terminal message "error: closed".
It seems that the phone will not flash ANYTHING atall........
OKAY BREAKTHROUGH lol instead of sitting here twiddling my thumbs waiting for replies, I thought I'd spend the time trying to sideload Cyanogenmod, IT WOOOOORRRKKEED and im in a good mood for the first time today thanks to you! My only problem now is that I cannot seem to restore from my backup, it always fails at system :S
nOOb HTC Guy said:
OKAY BREAKTHROUGH lol instead of sitting here twiddling my thumbs waiting for replies, I thought I'd spend the time trying to sideload Cyanogenmod, IT WOOOOORRRKKEED and im in a good mood for the first time today thanks to you! My only problem now is that I cannot seem to restore from my backup, it always fails at system :S
Click to expand...
Click to collapse
I'll be back in around 2 hours or so, off to work now. At least a breakthrough of some sorts, will check on this thread later, hopefully you don't have to wait so long for your device to be fixed :fingers-crossed:
:victory:
if your using a different recovery or a different version of the same recovery your backups may not work unless you flash the recovery you made the backups with
Guys, Im still stuck with cyanogen mod, nothing else will flash or sideload successfully. Also, what I thought was the ruu for my phone was not, can anyone find the correct ruu for mine? Htc one m8 on vodafone uk, cant find an ruu anywhere
Also, cannot obtain s-off since I get "permission denied" message when trying to adb shell and "su" through terminal..... Dont know if I require s-off to flash roms or ruu? thanks.
Ok it doesnt look there is an ruu for mine yet. So maybe I should focus on trying to get my own stock backup to restore, but nothing works! Its always the system bit that fails, boot data cache all restore successfully, any ideas? Would be absolutely amazing if I could just restore to the backup successfully! :good:
success!
YES YES YES YES YES!!!!! NOOOOOBBB POOWWWEERRR!!!!! Sorted it finally!!!!
For anyone else who has had problems restoring from backups, try restoring with files on phone memory and not sd card! Thats what worked for me.
Guys, thankyou all so much for your help I am eternally grateful and more relieved than you can imagine. Finally have a phone again
Howdy,
I successfully rooted my Nexus 7 2013 last week and things have been going along smoothly until a few hours ago. I came across this article that shows how to install Android L Preview Keyboard. After about an hour I'm at the point where I tried to go back to Root by wiping the system. Now everytime I power on the tablet the start screen comes on asking me what language to use but I also get an error message that Google Keyboard has failed. This prevents me from inputting anything into the tablet. So I'm STUCK!
Does anyone have any ideas what I can do to get back into ANY operating situation? Even if I have to go back to stock, that's fine.
phoophan said:
Howdy,
I successfully rooted my Nexus 7 2013 last week and things have been going along smoothly until a few hours ago. I came across this article that shows how to install Android L Preview Keyboard. After about an hour I'm at the point where I tried to go back to Root by wiping the system. Now everytime I power on the tablet the start screen comes on asking me what language to use but I also get an error message that Google Keyboard has failed. This prevents me from inputting anything into the tablet. So I'm STUCK!
Does anyone have any ideas what I can do to get back into ANY operating situation? Even if I have to go back to stock, that's fine.
Click to expand...
Click to collapse
Since when do you install a system app?
But yeah, wiping data in recovery will fix it. Of course, you could just restore that nandroid I know you made.
phoophan said:
Howdy,
I successfully rooted my Nexus 7 2013 last week and things have been going along smoothly until a few hours ago. I came across this article that shows how to install Android L Preview Keyboard. After about an hour I'm at the point where I tried to go back to Root by wiping the system. Now everytime I power on the tablet the start screen comes on asking me what language to use but I also get an error message that Google Keyboard has failed. This prevents me from inputting anything into the tablet. So I'm STUCK!
Does anyone have any ideas what I can do to get back into ANY operating situation? Even if I have to go back to stock, that's fine.
Click to expand...
Click to collapse
Piece of cake! Probably take less than 10 minutes! Flash the stock rooted rom in your custom recovery. Or download the factory image, extract the system.img from inside the factory image. Place the system.img inside the folder where you have fastboot.exe and adb.exe (android sdk platform-tools folder). Put your N7 in the bootloader screen, plug into your computer. Shift right-click inside your platform-tools folder, choose 'Open command window here.' Type in command window fastboot devices then hit enter and you should see your device id. Type fastboot flash system system.img then hit enter. When it says it's finished type fastboot reboot or you can use your device power and volume buttons to boot into your custom recovery (TWRP?) to install the supersu zip that you put in your storage earlier. It would also be a good idea to do a factory reset from inside TWRP to get rid of the L keyboard. A factory reset using TWRP does Not wipe your storage, if you wipe data that will wipe everything.
With all of the above I'm assuming you have a custom recovery and have the sdk installed. I can't give much help with toolkits because I know very little about them. If you make system changes you need a backup (nandroid) or at least know how to use adb/fastboot. If you make system changes you will need to be able to revert those changes or flash your rom in recovery or fastboot flash the system or whole factory image if you ever want to do an OTA or version update. Knowledge is power, just saying! ; )
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
merkk said:
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
Click to expand...
Click to collapse
Can you boot to recovery?
If you can, then flash a newer TWRP build, they have MTP support, you can mount it while connected to your PC, copy a ROM zip over (there is a stock on in these threads somewhere), flash it from recovery, wipe everything first. Then you should be able to boot into a working device.
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
merkk said:
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
Click to expand...
Click to collapse
Yes, first thing is to flash this.
http://cubegamemc.de/kevinjoa/lollipop/recovery-geehrc/twrp/
You can flash it through fastboot.
follow these steps:
1. Download and place the file on your PC.
2. Reboot your device into Fastboot Mode. To do that, simply hold down the Volume DOWN+Power buttons together.
3. Once inside the Fastboot mode, connect your device to your PC via USB cable.
4. Launch a Command Prompt Window in the folder you saved the recovery image to. You can do that by holding down the Shift button on your keyboard and right-click on any blank area on the screen, then select Open command window here.
4. Enter the following command into the Command Prompt Window. You need to replace recoveryfilename.img with the actual name of the Recovery Image you downloaded.
Code:
fastboot flash recovery recoveryfilename.img
5. Once it is done, reboot your device
Code:
adb reboot recovery
should do it. If not, just hold down the power button, and get back to recovery.
at that point you should have the newest recovery. This recovery has MTP enabled so you can transfer files just like you can if you had a running device.
Once it shows up on you PC you can transfer a ROM zip or a backup to the internal SD. From there you I am sure you know how to flash a zip or restore a backup. It is the same as an older version. MTP should be under the "MOUNT" section of TWRP. I don't remember because I have a different device now.
Good luck!
If this doesn't work, follow the thread here: You would need the super big full bin file if you do though because you do not have a working ROM or zip currently on your internal SD card and this contains a very old recovery, but it does work.
http://forum.xda-developers.com/showthread.php?t=2230106
edit: I altered the directions from the source here for the att version. Don't worry, I changed them to suit your current need.
http://theunlockr.com/2013/03/26/how-to-install-twrp-recovery-on-the-lg-optimus-g-att/
My phone seems to behave a little differently than what you describe. Holding down the volume down and power button just turns it on. Holding vol up and power puts me into a screen with the android bot on it with the option to restart bootloader, go into recovery, or power off. and at the bottom there's some text indicating fastboot mode is on.
I was able to use the fastboot command to load the newer recovery. But for some reason, none of the adb commands work on my phone.
I'm copying a twrp backup to the phone now and i'll restore that. Hopefully that'll fix the issue of the phone not booting and if i am really lucky, fix the issue of the phone not being activated, but I'm not too hopeful about that.
Thanks again for all your help
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
merkk said:
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
Click to expand...
Click to collapse
EDIT:: TRY THIS FIRST<
Do a full wipe of the system and data, not internal. GO to recovery, select wipe, then factory reset. Then boot your phone. You will have to setup everything again but it might help. If it does not, you can always restore your backup again.
^^^^^^^^^^^^^^^^^^^^^^^
Interesting that your phone was the opposite for the buttons. Maybe I had it backwards, or maybe my source did. Either way I am glad you have a device that boots now.
Check this...
Go to the about section and see if your imei and other information are blank or have 0's. I am almost certain that there are 0000's.
If that's the case then you lost your EFS some how. and there is a way to recover that as long as you have a backup somewhere. You should have one somewhere if you used freegee to unlock your phone in the beginning. If not, perhaps an earlier backup you had of your device. A lot of the recoveries for this device make a backup of the EFS.
well i just dropped the phone off at a sprint repair store to see if they could do anything with it now that it actually boots. If they can't fix it, I'll try what you suggested. Although i already tried a factory reset and that didn't help.
well you are right about the esn/meid/IMEI - they are all zeros
I did a restore and then used freegee to restore the efs. Will free tell you if there is no backup of the EFS? Because i restored it, it finished pretty much instantly, and then i restarted the phone just be safe. Unfortunately it didn't fix it.
Phone still says searching for service, and now there's a little red x over the bars. Before the bars were blank but there was no red x. Not sure if that makes any difference.
Also, something else weird is going on now. I just tried copying a newer backup to the phone to try and restore the newer one. I don't seem to be able to copy files now. When i drag the folder windows , it says the device has stopped responding. If i try and copy each individual file in the backup folder, it starts to copy, and then just sits there like it froze, or like it's copying so slowly it might as well be frozen. I had to reflash twrp to the newer version and then I'm able to copy files.
Reloaded the efs backup again but still can't activate/have all zeros.
HI all. I am in serious need of help please.
My wifes M9 is stuck on a screen with only a backlight. How this came about is after several failed attempts of updating the system via Wi-Fi. South Africa does not have a RUU available and only over the air updates are available
After about 2 days on the net, searching and reading and trying and failing I have determined the following.
What I have tried
1. Boot to Bootloader and tried recovery. This give me an Error - "Failed to boot to recovery"
2. Tried a Official RUU from HTC, this failed due to CID - Error wrong Customer ID
3. Learned a bit of ADB but this is no use as It seems USB debugging is disabled on the phone
4. Tried Custom ROM's via the SD card but this is blocked as the phone is **Locked** and **S-On**
5. Fastboot sees the phone as I can push reboot commands but because of locked status I can not do much
6. I can not get a unlock token as OEM is locked and this must be unlocked for ADB command to get token to get unlock.bin from HTCDEV
Basically it seems like I am at a dead end as it appears that I need to get into a boot status to enable debugging and enable developer mode from phone settings to be able to work from ADB
So here is the Million dollar question, How can I "wipe" the phone with a SD card boot image/loader or does any one know of a RUU-.exe for South Africa CID_016 that I could flash the phone with or possibly any other methods to get a ROM on it that we can use it again
I repeat, phone goes to blank screen with only backlight after HTC Logo, S-on, USB debugging seems to be disabled and it is in Locked status. I am able to boot in download mode and bootloader and fastboor does see the device. ADB devices does not see the phone, even after trying loads of different drivers, ADB USB ADB Interface etc etc
Please I need help
I'm suffering from the same fate. Except I had rooted it before, then I tried to update it to 5.1 and I relocked my bootloader. Android 5.1 loaded successfully but it got stuck while booting and now I can't unlock my bootloader. I have tried EVERYTHING!
https://www.google.com/url?q=https:...261000&usg=AFQjCNEBlBxkVmymaiJO1eaxKcHsKsE-wg
1.download this zip file
2. Rename the file to 0PJAIMG.zip (zero not O)
03. Copy the file to the root directory of a SD card which is formatted to fat32
04. Put the card into your phone and boot to Download Mode.
05. You will be asked whether you want to flash the file. Confirm with the volume up button.
06. Your phone will reboot at least one time. Depending on your current firmware version it may reboot to Android instead of rebooting to Download Mode. If this happens you just need to shut your phone down and manually boot it to Download Mode.
07. Flashing may take some time.
08. At the end you will be asked to push the power button. You phone will shut down if you do so.
09. Wait some seconds and then turn your phone on, again.
10. First boot may take a while.
11. Congrats! thanks to flippy
YES!!! OP I tried this and it works!!! My phone is finally alive again thanks to flippy's instructions.
Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Thank you so much for taking the time to answer this Degerli43! I know virtually every answer possible is available on this forum, but finding it is the trick!
Note to anybody else doing this, be sure to locate the correct image file for your provider and area, as the link above and the one below may not be the correct one for you. I am a T-Mobile US customer and used this one -
https://www.androidfilehost.com/?w=...6ce7fb817fc1524b58f67fe05270f032107d2306abcd4
This worked perfectly after I could not boot or enter TWRP recovery. Anybody who can still access Android Recovery the Downloader should be able to use it to get un-bricked to a clean carrier state if the image file will take.
ksnax said:
Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Click to expand...
Click to collapse
Did you ever visit the general section? :silly: There's a sticky thread with stock files and linked instructions for recovering TWRP backups and flashing RUUs. Read the OP, follow it's instructions to my google sheet and you will see where the steps that helped you out are taken from.
Sent from my HTC One S using XDA Labs