Database Info

Evo Shift Stuck In Boot Loop Please Help!

Hello,
I have an Evo Shift stuck in the boot loop. As soon as I put the battery in all it does is reset itself to the screen with the white background and green "HTC" logo, and will keep restarting until the battery dies.
If I hold volume down and turn it on, it does go into the bootloader, but picking ANYTHING, such as recovery or factory reset, does nothing but sending it back to the HTC screen.
I have tried flashing the RUU.exe (2.27.651.2) through Fastboot USB and it completed successfully, but it just restarts right back to the HTC screen. I have also put PG06img that I found on here on the root of my card, and it will never load it up.
Are there any other solutions anyone can think of? They would be much appreciated. I see a lot of these threads for regular Evos, but not for Shifts.
The only other thing I really know about the phone is that it is:
S-On
Hboot- 0.98.0001
Radio- 1.08.00.0506
Thank you so much for all of your help!

Seems to me you aren't rooted and that's more than likely your problem, boot into fastboot and use the ruu application for gingerbread.
Sent from my PG06100 using Tapatalk

Rooster85 said:
Seems to me you aren't rooted and that's more than likely your problem, boot into fastboot and use the ruu application for gingerbread.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
While I am pretty sure I am not rooted, if you are talking about the early RUU release; 1.17.651.1, the application starts and then ends up failing in the beginning of the process. Is this what you are talking about? The drivers should be all good, the application starts to flash and then dies though. Thanks!

samcrac said:
While I am pretty sure I am not rooted, if you are talking about the early RUU release; 1.17.651.1, the application starts and then ends up failing in the beginning of the process. Is this what you are talking about? The drivers should be all good, the application starts to flash and then dies though. Thanks!
Click to expand...
Click to collapse
Use the new RUU. But make sure your SD card is formatted to a FAT32 partition. (Stock 2gig sd card and some other store boughts are not)
You can format on your computer and then place the RUU on the root of sd card again
(Bootloader won't recognize the ruu zip if not partitioned)
Sent from my Supreme Shift

notsointeresting said:
Use the new RUU. But make sure your SD card is formatted to a FAT32 partition. (Stock 2gig sd card and some other store boughts are not)
You can format on your computer and then place the RUU on the root of sd card again
(Bootloader won't recognize the ruu zip if not partitioned)
Click to expand...
Click to collapse
Ok, I just did this, everything updated fine and all completeted on the bootloader. It then said "press power to reboot." I did so, and went right back into the same boot loop. Any other ideas. I figured running this, and the RUU.exe on the computer were the sure fire ways to get this thing working again???

samcrac said:
Ok, I just did this, everything updated fine and all completeted on the bootloader. It then said "press power to reboot." I did so, and went right back into the same boot loop. Any other ideas. I figured running this, and the RUU.exe on the computer were the sure fire ways to get this thing working again???
Click to expand...
Click to collapse
So just a little information.
you said your not rooted?
So that means you have no ability to flash anything because you have no custom recovery and the bootloader isnt unlocked (S-on)
So what DID you do before it bootlooped? there had to have been something you were trying to do.
Not trying to blame anything on you at all just want to make sure we are helping the most accurate way possible

notsointeresting said:
So just a little information.
you said your not rooted?
So that means you have no ability to flash anything because you have no custom recovery and the bootloader isnt unlocked (S-on)
So what DID you do before it bootlooped? there had to have been something you were trying to do.
Not trying to blame anything on you at all just want to make sure we are helping the most accurate way possible
Click to expand...
Click to collapse
No I hear ya. I was sold the phone fairly cheap and was told "all you need to do is to reinstall the RUU, that is all that is wrong." Obviously I was skeptical, but when I checked everything out, everything looked good, and again, for the price, I knew it was a gamble. That being said, I'm sure something was tried in order to modify the phone and this is how it got like this.
I have soft bricked my old Evo 4g a handful of times and an RUU or Rom flash would always solve the problem.
Anyway, there is no custom recovery, and I'm pretty sure theres no root because it is still "S-ON," I am just trying to see if anyone here has any more info before it goes in for repair.
The only last thing I would guess you MIGHT be able to do is to install a custom recovery, but is there ANY way to do this by just being in the bootloader and using FASTBOOT USB? Any more help is greatly appreciated. Thanks!

samcrac said:
No I hear ya. I was sold the phone fairly cheap and was told "all you need to do is to reinstall the RUU, that is all that is wrong." Obviously I was skeptical, but when I checked everything out, everything looked good, and again, for the price, I knew it was a gamble. That being said, I'm sure something was tried in order to modify the phone and this is how it got like this.
I have soft bricked my old Evo 4g a handful of times and an RUU or Rom flash would always solve the problem.
Anyway, there is no custom recovery, and I'm pretty sure theres no root because it is still "S-ON," I am just trying to see if anyone here has any more info before it goes in for repair.
The only last thing I would guess you MIGHT be able to do is to install a custom recovery, but is there ANY way to do this by just being in the bootloader and using FASTBOOT USB? Any more help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
It shouldn't have a custom recovery if it shows s-on.
I don't see why the RUU wouldn't work.
Honestly it doesn't sound like a softbrick- sounds like its just bricked (Which ive only heard of 1 Shift getting bricked completley)

notsointeresting said:
It shouldn't have a custom recovery if it shows s-on.
I don't see why the RUU wouldn't work.
Honestly it doesn't sound like a softbrick- sounds like its just bricked (Which ive only heard of 1 Shift getting bricked completley)
Click to expand...
Click to collapse
Make it 2! Thanks for your help though!!!

Also Stuck In A Bootloop
samcrac said:
Hello,
I have an Evo Shift stuck in the boot loop. As soon as I put the battery in all it does is reset itself to the screen with the white background and green "HTC" logo, and will keep restarting until the battery dies.
If I hold volume down and turn it on, it does go into the bootloader, but picking ANYTHING, such as recovery or factory reset, does nothing but sending it back to the HTC screen.
I have tried flashing the RUU.exe (2.27.651.2) through Fastboot USB and it completed successfully, but it just restarts right back to the HTC screen. I have also put PG06IMG that I found on here on the root of my card, and it will load it up (I'll see the blue loading bar and then the brown loading bar in the top right hand corner of the screen), but it then checks it again, and then goes back to the original screen for the bootloader.
Are there any other solutions anyone can think of? They would be much appreciated. I see a lot of these threads for regular Evos, but not for Shifts.
The only other thing I really know about the phone is that it is:
S-On
Hboot- 0.98.0001
Radio- 1.08.00.0506
Thank you so much for all of your help!
Click to expand...
Click to collapse
I'm trying to resolve a very similar problem as him, but I know of the history of my phone (since I'm the only owner), so hopefully an answer for me can assist him also.
The Story: One day, I'm playing Uno HD (downloaded from Android Market). I toss out a Draw 4, and then I see: "Google Infrastructure Failure" and a Triangle with an exclamation mark. I reset the phone, and it starts up fine. Then a few hours later, my phone randomly restarts itself into the bootloader screen after trying to reload the home screen (because the memory manager is overly aggressive).
I see no HTC Screen. It goes straight to the bootloader without any input. If I plug it to the charger from an off state, the amber light comes on, and 10 seconds later, bootloader screen. With a battery, it appears automatically after 45 seconds.
Fastboot can read my memory card just fine. It's already been re-formatted as FAT32 in my pitiful attempt to try to repair it. It's checked and read a PG06IMG file I placed on the SD Card's root, went through the entire process of reading it, but it doesn't ask me if I want to upgrade. It takes me back to the original screen. (Maybe I'm loading the wrong file).
Recovery and Factory Reset immediately restarts the bootloader after showing me the skateboarding android splash screen.
I've also tried to flash the newest stock RUU for it. (2.76.651.4), but after the RUU sends the command to start up in bootloader mode, the phone shuts off. Thus giving me the connection error.
(Maybe if someone could rewrite the .exe file to not send out the command to begin loading as if it was in the bootloader screen, it could work. I'd pay for that.)
Other Stuff:
ROM: Stock Sprint Gingerbread OTA ROM. I've been living the vanilla life. No root access. No funny stuff. Just a stock phone with apps (Third Blade, Uno HD, ASTRO File Manager, ect...)
Directly from bootloader screen:
SPEEDY XA SHIP S-ON
HBOOT-0.98.0001
RADIO-1.08.00.0506
eMMC-boot
April 11 2011, 22:32:34
Is there a way we can flash a file from the SD Card which will turn off the security and/or temp/perm root it? (forgive my noobness for such a question)
EDIT: I'm referring to a way that's outside of the adb push method. My device can't be found, and the device won't get past the bootloader screen, so that method doesn't help me too much. However, I do have the ADK Installed and the ADB Command Line works fine.

Ok .. HERE'S THE SOLUTION:
First off all if your S- ON it means you are NOT rooted
If you get stuck in a bootloop .. don't worry it can be fixed.
What you need to do is download PG06IMG.ZIP and place it on your sd card, you can access your sd card by going into recovery then mount section, then usb. This will allow you to move the file from your computer to the root of your sd card.
Once you do this be sure you back up any info you don't want to lose. Once you have the file in place, go back to fastboot ( hold vol down and power) it will read file and when it asks you to update press vol up. It will take a few minutes to update this will revert your phone back to stock but if you have an old recovery it will not do a full restore, it will only update the rom.
Once you get your phone back to working, I recommend updating your recovery by downloading Rom Manager and flashing the latest clockwork recovery. This problem happens usually due to an old recovery.
One other thing you can try if you do NOT want to reset your phone, you can try flashing a new kernal.
Sent from my PG06100 using Tapatalk

RUU won't work if your stuck in bootloop ..
Sent from my PG06100 using Tapatalk

If you want to root your phone use visionary to temp root then use shift rr .. you can then flash a custom recovery which is essential to avoid this from happening again
flylike2kites said:
I'm trying to resolve a very similar problem as him, but I know of the history of my phone (since I'm the only owner), so hopefully an answer for me can assist him also.
The Story: One day, I'm playing Uno HD (downloaded from Android Market). I toss out a Draw 4, and then I see: "Google Infrastructure Failure" and a Triangle with an exclamation mark. I reset the phone, and it starts up fine. Then a few hours later, my phone randomly restarts itself into the bootloader screen after trying to reload the home screen (because the memory manager is overly aggressive).
I see no HTC Screen. It goes straight to the bootloader without any input. If I plug it to the charger from an off state, the amber light comes on, and 10 seconds later, bootloader screen. With a battery, it appears automatically after 45 seconds.
Fastboot can read my memory card just fine. It's already been re-formatted as FAT32 in my pitiful attempt to try to repair it. It's checked and read a PG06IMG file I placed on the SD Card's root, went through the entire process of reading it, but it doesn't ask me if I want to upgrade. It takes me back to the original screen. (Maybe I'm loading the wrong file).
Recovery and Factory Reset immediately restarts the bootloader after showing me the skateboarding android splash screen.
I've also tried to flash the newest stock RUU for it. (2.76.651.4), but after the RUU sends the command to start up in bootloader mode, the phone shuts off. Thus giving me the connection error.
(Maybe if someone could rewrite the .exe file to not send out the command to begin loading as if it was in the bootloader screen, it could work. I'd pay for that.)
Other Stuff:
ROM: Stock Sprint Gingerbread OTA ROM. I've been living the vanilla life. No root access. No funny stuff. Just a stock phone with apps (Third Blade, Uno HD, ASTRO File Manager, ect...)
Directly from bootloader screen:
SPEEDY XA SHIP S-ON
HBOOT-0.98.0001
RADIO-1.08.00.0506
eMMC-boot
April 11 2011, 22:32:34
Is there a way we can flash a file from the SD Card which will turn off the security and/or temp/perm root it? (forgive my noobness for such a question)
EDIT: I'm referring to a way that's outside of the adb push method. My device can't be found, and the device won't get past the bootloader screen, so that method doesn't help me too much. However, I do have the ADK Installed and the ADB Command Line works fine.
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk

Also if your phone can't be found its b/c you need to put it into diag mode .. ##DATA .. if you need more help google
tech-9 said:
If you want to root your phone use visionary to temp root then use shift rr .. you can then flash a custom recovery which is essential to avoid this from happening again
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk

For the thread starter, the person that sold you the phone probably tried writing to the system partition with s-on. Since you can get to the bootloader, see if you can get into recovery. If you can, recovery can be seen in adb, even the stock recovery. From there, gingerbread root, plenty of guides out there, make sure you flash the misc.img, download the froyo downgrade zip (that pgimg09.zip or something like that, just search for it, but not with the numbers I just gave, those are made up.)
From there either flash the gingerbread zip or ruu, and goon with a unrooted life. Or follow one of the many guides to froyo root, and live the life of the rooted. Your choice.
For the second person with a similar issue, the same method will work for you (assuming you can get to recovery), gingerroot, froyo downgrade, and since you like being unrooted, just ruu or zip back to gingerbread.
Solution found enjoy, and just think, if root hadn't been discovered for gingerbread, you would be screwed right now, make sure to thank otaking.

I have the same boot loop problem. I tried using the PG06IMG.zip file and fastboot/bootloader screen says I have the wrong image. It's most likely because it's for 2.2 and I have 2.3. I also don't have any recovery. Is there a PG06IMG.zip for 2.3 or the like?

similar problem here
i'm fairly certain i tried recovery with the wrong or corrupt or incomplete PG06IMG.zip on my first attempt. i got the right one from here http://forum.xda-developers.com/showthread.php?t=1255474
i ran it, says update installed, but when i reboot i still get the loop
from bootloader
SPEEDY XE SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Nov 15 2010, 13:19:54

zdavidzz said:
i'm fairly certain i tried recovery with the wrong or corrupt or incomplete PG06IMG.zip on my first attempt. i got the right one from here http://forum.xda-developers.com/showthread.php?t=1255474
i ran it, says update installed, but when i reboot i still get the loop
from bootloader
SPEEDY XE SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Nov 15 2010, 13:19:54
Click to expand...
Click to collapse
Try downloading the zip again and re run it. Possibly a bad download?
Sent from my PG06100 using Tapatalk

also adb is telling me device not found. i think i might have to factory reset. is that crazy?
---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------
and... that didn't help

i'm downloading the zip again right now.
since i have s-on, will i be able to install it though?
i can get the file on the root of the sdcard with an adapter since i can't push from adb. and i can't temp root the phone because if i try a normal reboot i get this stupid boot loop. is there a way to get s-off through hboot on the phone?
i don't know why i didn't notice that first file was messed up, it was only 6MB.

Help, Goes straight to TWRP on startup

Hello Everyone,
I am a Noob, Yes. Please help. I was trying to install TWRP onto my TF300T. I installed it Via ADB. Had it installed with my stock ROM. I tried to do a backup so I could flash CM10. It said it wasn't mounted. I tried again and then it reboot and now goes straight to TWRP. I can get my device on ADB via the cmd screen but it says that the device is attached in recovery and my serial number is now 01233456789ABCD. Have I completely bricked my tablet? Is there anything I can do? I have been searching the forums for literally hours and am at wits end. Any suggestions would be appreciated. Sorry if this has been gone over time and time again but I can't figure it out. Please help. Thanks
Marc

To add,
When I try to do anything via fastboot it just hangs waiting for device. I can't get it to go to the fastboot page on my tablet, it just goes straight to the TWRP page.

Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...

splashg said:
Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...
Click to expand...
Click to collapse
Yes, that would be correct. So I managed to reset the device and cold boot back to a working device. Now i'm still wanting to flash a custom recovery and change ROMS to cyanogenmod (had it on my S1 and loved it) but am a bit nervous. How do I reset my partition and clear the old TWRP and flash a working version of CWR via fastboot or a version of TWRP that will work with my OTA rom. I thought I had done quite a bit of research before hand but am feeling a bit overwhelmed now. I don't want to go through another twelve hours of trying every trick I can find on the internet to unbrick my device.
Thanks

Just a few other things to add. So now when i have my device connected to my computer in normal function i can recognize it when I enter adb devices on my cmd prompt. Then I do the fastboot reboot bootloader which it then sends it into the fastboot screen. type in adb devices and it doesn't recognize the device anymore. I try the commands to install the cwm recovery.img and my cmd screen goes through the normal steps saying it's completed it. Then i try to reboot the device through fastboot and it freezes on the bootload screen with the green box no longer flashing on the rck box. Hold power button for six seconds to reboot and i have a working device again. So now i'm lost. How do I reset everything so I can start over, repartition so I can flash a custom recovery and carry on. any help is appreciated.

I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.

splashg said:
I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.
Click to expand...
Click to collapse
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.

lomoski said:
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.
Click to expand...
Click to collapse
I finally gave up, sent mine in today, it will cost but what the hell, i want my tablet in working order. I've tried the remedies myself, to no avail.
So off to ASUS.

Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.

steveb05 said:
Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.
Click to expand...
Click to collapse
I won't know how much it will cost until the unit is in their hands. I initiated my RMA online as well, they told me i will be contacted by phone after they examine it, I'm prepared to invest another 100 bucks as i got the unit for $299. I'll be hesitant to go much higher. I will post a number when i hear from them, if they haven't replied back to you.

I've got the same problem on my TF300T.
I'm going to try to get it working.
Not entirely sure what caused it, since I had used encryption in cm10.1 prior to flashing Asus stock 4.2.1.
BTW, I've been able to get back to fastboot by running adb reboot bootloader when TWRP is loaded.
Update: Seems to be that new 10.6.x.x bootloader... gotta love Asus :-/
--- Update II----
I can't flash anything in fastboot anymore :-/

[Q] I just updated and now my shield is frozen on the boot splash

I never rooted or unlocked the bootloader, not sure what's up. I had a 32gb SD card in it if that matters.
Anyone know what I could try and do?

Try to flash stock from fastboot, maybe something on your system has been corrupted... Are you rooted or bootloader unlocked?

thegunrun said:
I never rooted or unlocked the bootloader, not sure what's up. I had a 32gb SD card in it if that matters.
Anyone know what I could try and do?
Click to expand...
Click to collapse
You can try to recover to the recovery image.
https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/HowTo-Flash-Recovery-Image.txt
You can find the boot, system and recovery .img's here
http://forum.xda-developers.com/showthread.php?t=2388870
The blob and tegra114-roth here
https://drive.google.com/?authuser=0#folders/0B7j6Imwr_sirRnl5MFRRR2sxRWM
I would upload the userdata.img, but it's too big for me to upload, and I don't think it is needed...

Guys, the OP mentioned that he has not unlocked/rooted his device, so he cannot flash the recovery image.
That should definitely not happen on an unlocked device. Can you at least see the splash animation? Things to try (in that order):
1) On the boot splash animation, connect SHIELD to your PC and try to run "adb logcat" to see if you can see what is crashing. Attach the log here if you can get it.
2) If you cannot use adb, reboot your SHIELD while holding the back and home buttons. This will bring you to the bootloader menu. Then connect to your PC and try to "fastboot erase userdata" and "fastboot erase cache" before doing "fastboot reboot". This will remove all your user data, so your SHIELD should boot again correctly provided the OTA went without any issue. You might not like the idea of losing your user data though.
3) Contact NVIDIA. You have not unlocked your SHIELD, just did a regular OTA. This is covered by the warranty so they should be able to help you.

Gnurou said:
....That should definitely not happen on an unlocked device. Can you at least see the splash animation? Things to try (in that order):....
Click to expand...
Click to collapse
Fixed that line for you.
If the device is locked getting Nvidia to fix the software should not be a problem.

I had the same problem. NVidia swapped out my Shield with a retail refurbished unit.

Happened to me but I shut it down using the nvidia button and let it sit for a few minutes and it booted.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.

i have got the same problem
its impossible to boot in 4.3. the only few times i got it, it tooks 10 ton 15 minutes
i go back to 4.2 and i had the same problem. the only way to get the shield back to normal is to format all (system, data, etc..) through cwmr
when i trie to update to 4.3 trought ota, i got the same problem and i have to repeat the proccess again to come back to 4.2
in 4.2 boots ok, and everything works, but i cant update
any ideas?

My boot-up problem seemed to have been caused by my 64GB SanDisk MicroSD card. When I pulled it out to transfer it to my replacement Shield, the original came up. Try pulling out your SD card before powering on if you are still having trouble.

jdsemler said:
My boot-up problem seemed to have been caused by my 64GB SanDisk MicroSD card. When I pulled it out to transfer it to my replacement Shield, the original came up. Try pulling out your SD card before powering on if you are still having trouble.
Click to expand...
Click to collapse
hi, i tried to boot without the sd and i get the same result
stock in boot logo
i thing the problem its something related with the ota update an my boot.img
someone has access to boot, system and recovery img from update 63?
maybe if i install from bootloader i get something
thanks in advance

If you power on holding back and home, you will boot into a menu. If you go into Recovery, do you get any options? On mine, it would say "No Command" and be stuck there. If yours also says "No Command", you can't really load anything using recovery.
You should consider going here. You'll have to either login or create a login, but after that, you can submit your problem to NVidia. That's what I did, and they shipped me a new unit overnight with a prepaid label to send my unit back.

Hi, Thanks for your answer. Im able to update the shield throught fastboot. This is hoy i can downgrade from 4.3 to 4.2.
Moreover ,i cant get a new unit, cause i live in spain, (and i already unlock my bootloader)

cg_gm said:
Hi, Thanks for your answer. Im able to update the shield throught fastboot. This is hoy i can downgrade from 4.3 to 4.2.
Moreover ,i cant get a new unit, cause i live in spain, (and i already unlock my bootloader)
Click to expand...
Click to collapse
good news!!! last update (64) solve the problem. now im in 4.3 and all is working ok
thanks for your help, hope thath nvidia dont mess up with the updates again

Need advice on mess with S3 update ....

Hello all,
Short story, wife had the 4.3 OTA nag popup, accidentally hit 'ok' and pulled battery before unit booted.
I thought maybe I could avoid the 4.3 OTA by flashing CWM via heimdall. I followed the CM directions for d2vzw at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw, basically I did the following:
heimdall flash --ABOOT aboot.mbn --no-reboot
heimdall flash --BOOT boot.img --no-reboot
heimdall flash --RECOVERY recovery-clockwork-6.0.4.5-d2vzw.img
However when I try to boot into recovery mode, I get the android character with spinning globe. I only saw the picture long enough to pull the battery.
Any suggestions on this on? It looks like the confirmation for OTA sets something, and it appears that whatever I did above either was wrong, didn't happen properly, or is ignored at this point. If I boot back into download mode I still see custom binary no, and current/system binary official.
I would like to get this to CWM and CM 10.2, but suspect it is too late ... can anyone tell me how to work around this, or should I just bite the bullet and reboot to see if the OTA updates at this point?
Thanks for any help you can advise on ....

vax1170 said:
Hello all,
Short story, wife had the 4.3 OTA nag popup, accidentally hit 'ok' and pulled battery before unit booted.
I thought maybe I could avoid the 4.3 OTA by flashing CWM via heimdall. I followed the CM directions for d2vzw at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw, basically I did the following:
heimdall flash --ABOOT aboot.mbn --no-reboot
heimdall flash --BOOT boot.img --no-reboot
heimdall flash --RECOVERY recovery-clockwork-6.0.4.5-d2vzw.img
However when I try to boot into recovery mode, I get the android character with spinning globe. I only saw the picture long enough to pull the battery.
Any suggestions on this on? It looks like the confirmation for OTA sets something, and it appears that whatever I did above either was wrong, didn't happen properly, or is ignored at this point. If I boot back into download mode I still see custom binary no, and current/system binary official.
I would like to get this to CWM and CM 10.2, but suspect it is too late ... can anyone tell me how to work around this, or should I just bite the bullet and reboot to see if the OTA updates at this point?
Thanks for any help you can advise on ....
Click to expand...
Click to collapse
Boot into download mode (vol down + Home + power button). Do you see this? If you see the last 2 lines you are on 4.3
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery

buhohitr said:
Boot into download mode (vol down + Home + power button). Do you see this? If you see the last 2 lines you are on 4.3
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
Click to expand...
Click to collapse
No not quite. I don't see the last few lines. My eyes are a bit old but what I see is only:
ODIN MODE
product name: SCH-I535
custom binary download: no
current binary: Samsung official
System status: Official
QUALCOMM secureboot ENABLE
And nothing else after that (just the green antroid graphic and 'downlaoding....')
Thank you for the fast response

vax1170 said:
No not quite. I don't see the last few lines. My eyes are a bit old but what I see is only:
ODIN MODE
product name: SCH-I535
custom binary download: no
current binary: Samsung official
System status: Official
QUALCOMM secureboot ENABLE
And nothing else after that (just the green antroid graphic and 'downlaoding....')
Thank you for the fast response
Click to expand...
Click to collapse
Seems like the 4.3 didn't make it. You can boot up the phone and re check..Once phone is up just turn off wifi and 4g to prevent the OTA.

buhohitr said:
Seems like the 4.3 didn't make it. You can boot up the phone and re check..Once phone is up just turn off wifi and 4g to prevent the OTA.
Click to expand...
Click to collapse
Sorry I wasn't clear ....
I believe the phone already had the OTA software downloaded and staged for install. It was popping up that nag screen that asks to run the update. My wife pressed 'OK' on that and as the phone shutdown and brought up the 'samsung' splash screen, the battery was pulled.
It was after this that I attempted to follow the CM directions to flash the older bootloader and CWM. However I don't think it was successful.
After running the procedure, I attempt to boot into recovery. I am expecting to see the usual CWM menu, however I don't. I get the android with the spinning globe in the belly. I am thinking, the flash with CWM didn't take, and the OTA is now attempting to install.
If possible I would like to flash CWM and then load up CM 10.2 from an internal SD card I've prepared.
Let me know what you think .... thanks!

vax1170 said:
Sorry I wasn't clear ....
I believe the phone already had the OTA software downloaded and staged for install. It was popping up that nag screen that asks to run the update. My wife pressed 'OK' on that and as the phone shutdown and brought up the 'samsung' splash screen, the battery was pulled.
It was after this that I attempted to follow the CM directions to flash the older bootloader and CWM. However I don't think it was successful.
After running the procedure, I attempt to boot into recovery. I am expecting to see the usual CWM menu, however I don't. I get the android with the spinning globe in the belly. I am thinking, the flash with CWM didn't take, and the OTA is now attempting to install.
If possible I would like to flash CWM and then load up CM 10.2 from an internal SD card I've prepared.
Let me know what you think .... thanks!
Click to expand...
Click to collapse
It's possible that the 4.3 bootloader already flashed and it's in the process of flashing the rom when you pulled the battery. In any case, if the software is half done you phone won't boot, and if you attempt to flash the old rom, you will brick your phone if the bootloader already locked. So you need to turn it on to see where you at or you can take a chance and try to Odin old stock rom, again if the bootloader already locked you will brick your phone and if not then you will be back to the older version. I would turn it on and see.

Thanks.
Is there anyway to tell for sure if the bootloader is the new one?
Fortunately I have 2 other S3's I can compare against. One is a 32g S3 with OTA 4.3. The other is a 32g S3 I picked up preinstalled with CWM/CM10. The hosed up phone is a 16g S3.
Can I pull something down from these phones with heimdall to check/compare if the 4.3 bootloader is there? I already did a print-pit on all 3 phones, but from what little I know it seems like the only differences are likely due to the memory sizes. 32 vs 16.
If there is no way to tell, then perhaps I'll reboot it and see..... thanks for the help,

vax1170 said:
Thanks.
Is there anyway to tell for sure if the bootloader is the new one?
Fortunately I have 2 other S3's I can compare against. One is a 32g S3 with OTA 4.3. The other is a 32g S3 I picked up preinstalled with CWM/CM10. The hosed up phone is a 16g S3.
Can I pull something down from these phones with heimdall to check/compare if the 4.3 bootloader is there?
If there is no way to tell, then perhaps I'll reboot it and see..... thanks for the help,
Click to expand...
Click to collapse
If you don't see the last 2 lines like I mentioned above, it should be the old bootloader...since the timing you pull the battery, no one really know what state it's in unless you boot it up.

Am I correct in assuming that the 3 heimdall statements I executed above should have resulted in CWM coming up when I do the up-home-power?
The CM instructions for d2vzw are not clear if you really need to let heimdall reboot the phone between each step. I was trying to avoid a full reboot as I expected the OTA to take over if I did.
Perhaps I should reboot it; if it boots up into anything, at least I can sell it ....

vax1170 said:
Am I correct in assuming that the 3 heimdall statements I executed above should have resulted in CWM coming up when I do the up-home-power?
The CM instructions for d2vzw are not clear if you really need to let heimdall reboot the phone between each step. I was trying to avoid a full reboot as I expected the OTA to take over if I did.
Perhaps I should reboot it; if it boots up into anything, at least I can sell it ....
Click to expand...
Click to collapse
Yes, you can boot up now and see what's going on...

So it looks like it is bricked to some degree. What might you advise to undo this?
When I power the phone up I see the usual Samsung galaxy logo, then the screen goes black with pulsing blue LED.
If I boot into recovery, I see the android with spinning globe for about 60sec, then the dead android with red triangle, and phone resets.
If I boot into download mode, it still comes up with the same messages I indicated above. It looks like the boot loader is not new. I can connect with heimdall and print-pit, so something is still alive here.
What is your best advice here? At this point, I don't think I care if it is put back to stock 4.1.2 or upgraded; booting and working with anything is fine.
Thanks

vax1170 said:
So it looks like it is bricked to some degree. What might you advise to undo this?
When I power the phone up I see the usual Samsung galaxy logo, then the screen goes black with pulsing blue LED.
If I boot into recovery, I see the android with spinning globe for about 60sec, then the dead android with red triangle, and phone resets.
If I boot into download mode, it still comes up with the same messages I indicated above. It looks like the boot loader is not new. I can connect with heimdall and print-pit, so something is still alive here.
What is your best advice here? At this point, I don't think I care if it is put back to stock 4.1.2 or upgraded; booting and working with anything is fine.
Thanks
Click to expand...
Click to collapse
I would try to use Odin and flash MF1 full firmware here http://www.androidfilehost.com/?fid=23134718111254196

Thanks for confirming ... I was poking around the forums and figured I should probably try the procedure to completely reflash my device back to stock. I'll try that later tonight. Thanks again ... crossing my fingers

[RESOLVED]
Looks like flashing the 4.1.2 stock image worked, device boots now!
There was somewhat unexpected behavior however, I don’t know if this is interesting or not. I followed the usual directions to use Odin to flash the full MF1 stock rom; this took about 8-10 min to complete.
On reboot, I saw the tiny blue message at top, and the phone appeared to start in recovery mode, at which point the android graphic with spinning belly globe came up. The progress bar went the full length (no error) and phone rebooted. Phone seemed to reboot fine with typical Samsung and LTE logos. When the phone came up, I was surprised. After unlocking the screen, I got a pop-up indicating that the phone update failed. I then found that all my old data was still available; wi-fi passwords, apps, account syncing, etc. everything. I was expecting the device to be wiped clean with the flash - but maybe I misunderstood. Download mode still seems to report the same messages as before (so it looks like it hasn’t been locked). Needless to say, I hit airplane mode and disabled WiFi, and the phone is not activated, so there is no ability for it to pull the OTA again. If it makes any difference, when I flashed this phone it had no SIM card, and it also had a new 1gb SD card I left in there which was populated with CWM and CM images.
Some summary details to anyone who is interested:
- Phone was running stock 4.1.2 MF1, it received the 4.3 OTA package and was popping up the request to update. Accidentally hit ‘ok’ and phone started reboot sequence to apply update. On phone startup, battery was pulled to prevent update.
- Attempted to run the CM 10.2 d2vzw procedure to flash older bootloader and CWM using heimdall. Transferred just fine, but this didn’t appear to work. Upon entering recovery mode, the android graphic comes up and attempts to do something, but fails.
- On reboot, the phone has pulsing blue LED; bricked
- ODIN’ed the stock 4.1.2 image back, and phone is un-bricked, pops up message on failed update, and all previous data is retained.
If there is any other information from this that could be useful to developers let me know. The phone will not be put back into service for some time, and I can transfer off or adb anything someone might find interesting. Just let me know and I'll try to retried and post here.
Thanks for the help!

vax1170 said:
Looks like flashing the 4.1.2 stock image worked, device boots now!
There was somewhat unexpected behavior however, I don’t know if this is interesting or not. I followed the usual directions to use Odin to flash the full MF1 stock rom; this took about 8-10 min to complete.
On reboot, I saw the tiny blue message at top, and the phone appeared to start in recovery mode, at which point the android graphic with spinning belly globe came up. The progress bar went the full length (no error) and phone rebooted. Phone seemed to reboot fine with typical Samsung and LTE logos. When the phone came up, I was surprised. After unlocking the screen, I got a pop-up indicating that the phone update failed. I then found that all my old data was still available; wi-fi passwords, apps, account syncing, etc. everything. I was expecting the device to be wiped clean with the flash - but maybe I misunderstood. Download mode still seems to report the same messages as before (so it looks like it hasn’t been locked). Needless to say, I hit airplane mode and disabled WiFi, and the phone is not activated, so there is no ability for it to pull the OTA again. If it makes any difference, when I flashed this phone it had no SIM card, and it also had a new 1gb SD card I left in there which was populated with CWM and CM images.
Some summary details to anyone who is interested:
- Phone was running stock 4.1.2 MF1, it received the 4.3 OTA package and was popping up the request to update. Accidentally hit ‘ok’ and phone started reboot sequence to apply update. On phone startup, battery was pulled to prevent update.
- Attempted to run the CM 10.2 d2vzw procedure to flash older bootloader and CWM using heimdall. Transferred just fine, but this didn’t appear to work. Upon entering recovery mode, the android graphic comes up and attempts to do something, but fails.
- On reboot, the phone has pulsing blue LED; bricked
- ODIN’ed the stock 4.1.2 image back, and phone is un-bricked, pops up message on failed update, and all previous data is retained.
If there is any other information from this that could be useful to developers let me know. The phone will not be put back into service for some time, and I can transfer off or adb anything someone might find interesting. Just let me know and I'll try to retried and post here.
Thanks for the help!
Click to expand...
Click to collapse
You're a lucky son of .....lol.

[Q] Razr HD Stuck in loop after trying to sideload kitkat

Hello,
I have a stock RAZR HD and I'm living in Germany. I tried sideloading KitKat on the device since I won't get the OTA update but during the upgrade the device rebooted and is now in a boot loop. In recovery, no matter what key combination I use, I won't show any of the menues to update, factory reset etc. Is the device a lost cause? I was reading through the Droid Razor HD Utility 1.32 and that seems like a way to recover, but I'm a little hesitant.
Any guidence would be greatly appreciated.

Zlynt said:
Hello,
I have a stock RAZR HD and I'm living in Germany. I tried sideloading KitKat on the device since I won't get the OTA update but during the upgrade the device rebooted and is now in a boot loop. In recovery, no matter what key combination I use, I won't show any of the menues to update, factory reset etc. Is the device a lost cause? I was reading through the Droid Razor HD Utility 1.32 and that seems like a way to recover, but I'm a little hesitant.
Any guidence would be greatly appreciated.
Click to expand...
Click to collapse
At the recovery image, press and hold vol up then press power and hold both for about 2 seconds and then let go of both buttons. You'll be in the new recovery. Install the ota again to complete the upgrade.
It's a two stage install. The first time you install the OTA, it replaces the recovery if it senses it's an older recovery and then it reboots you back to the recovery image of Andy lying on his back with a red ! over him. This is where you must do the vol up + power to go back into the recovery. They changed the key combination on is with the new recovery. If you don't go into recovery, it will then proceed to attempt and boot into your phone but it won't be able to so it will reboot again.
Once you are back in recovery after the reboot, go and install the OTA again. This time, it will upgrade your phone to KitKat. It could take up to 15 minutes so be patient.
Sent from my DROID RAZR HD using Tapatalk

Zlynt said:
Hello,
I have a stock RAZR HD and I'm living in Germany. I tried sideloading KitKat on the device since I won't get the OTA update but during the upgrade the device rebooted and is now in a boot loop. In recovery, no matter what key combination I use, I won't show any of the menues to update, factory reset etc. Is the device a lost cause? I was reading through the Droid Razor HD Utility 1.32 and that seems like a way to recover, but I'm a little hesitant.
Any guidence would be greatly appreciated.
Click to expand...
Click to collapse
dont ust the razr utility, if parts of the ota flashed (sounds like it did) before you got stuck, it will just continue to bootloop.
were you running the stock us verizon xt926 software before you sideloaded the ota?
is your bootloader locked or unlocked?

bweN diorD said:
dont ust the razr utility, if parts of the ota flashed (sounds like it did) before you got stuck, it will just continue to bootloop.
were you running the stock us verizon xt926 software before you sideloaded the ota?
is your bootloader locked or unlocked?
Click to expand...
Click to collapse
Hi, thanks for replying. I was running stock verizon software and the bootloader is locked.

Zlynt said:
Hi, thanks for replying. I was running stock verizon software and the bootloader is locked.
Click to expand...
Click to collapse
with your bootloader being locked and you cant get into recovery (im assuming you tried Ibolski's tip and still cant get in), you should wait for the fxz to get leaked. sorry but any other path is risky and likely to make your phone unrecoverable.

bweN diorD said:
with your bootloader being locked and you cant get into recovery (im assuming you tried Ibolski's tip and still cant get in), you should wait for the fxz to get leaked. sorry but any other path is risky and likely to make your phone unrecoverable.
Click to expand...
Click to collapse
Hi, ok i didn't see or try that trick. Yes if I hold vol up and hit power, i can now get into the recovery menu. I think though I need to use a different file to upgrade to Kitkat. Is there a copy out there that doesn't require all the tweaking to that i can just load onto my sd card and apply? I think that's what's messed this up is the file i used I just tried to install like previous files.

Zlynt said:
Hi, ok i didn't see or try that trick. Yes if I hold vol up and hit power, i can now get into the recovery menu. I think though I need to use a different file to upgrade to Kitkat. Is there a copy out there that doesn't require all the tweaking to that i can just load onto my sd card and apply? I think that's what's messed this up is the file i used I just tried to install like previous files.
Click to expand...
Click to collapse
there is no other file.
you need to flash the ota again in recovery.
the file first flashes the new recovery, then reboots to install the remaining files.
what you are experiencing is normal. flash again and the install should complete.

bweN diorD said:
there is no other file.
you need to flash the ota again in recovery.
the file first flashes the new recovery, then reboots to install the remaining files.
what you are experiencing is normal. flash again and the install should complete.
Click to expand...
Click to collapse
thanks, i'll try again. However, since my phone has been boot looping i now have a low battery. any hints on how to charge while in a boot loop? Can i just run this while attached to power? I have a moto cable and charger.

Zlynt said:
thanks, i'll try again. However, since my phone has been boot looping i now have a low battery. any hints on how to charge while in a boot loop? Can i just run this while attached to power? I have a moto cable and charger.
Click to expand...
Click to collapse
When i try to install from SD it shows:
install /sdcard ...
Installation aborted
Not sure if this is because of the low battery or not. I started the process from http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/ however RSD never shows my device, however I know it works as from within the RAZR HD utility, it sees the device.
I'm really not sure what to try next.

Zlynt said:
When i try to install from SD it shows:
install /sdcard ...
Installation aborted
Not sure if this is because of the low battery or not. I started the process from http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/ however RSD never shows my device, however I know it works as from within the RAZR HD utility, it sees the device.
I'm really not sure what to try next.
Click to expand...
Click to collapse
being locked you cant use that link to fix it as some of the KK files (recovery at least) should have flashed and it will brick you.
also, if any kk files flashed razr utility will brick you
im going to have to revert back to what i said in post 5 at this point. sorry im not sure what else you can try that wont make this worse.
as for the charging, if it wont charge, you will need a moto factory adapter (google it) to flash the fxz when it leaks. they are $10 from team black hat and bypass the battery while flashing. it will not charge the battery it just powers the phone directly for those with a low/dead battery.