Database Develop

[Q] Stuck in bootloop after attempted upgrade

I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.

jggrnaut said:
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
Click to expand...
Click to collapse
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....

berndblb said:
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
Click to expand...
Click to collapse
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?

jggrnaut said:
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
Click to expand...
Click to collapse
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.

berndblb said:
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
Click to expand...
Click to collapse
Well it has gotten worse and I think I have lost fastboot now. I downloaded the CWM from part 1 above and flashed it in fastboot. I typed fastboot reboot and now I am stuck in a bootloop still. It says "The device is unlocked" at top of Asus splash screen for about 15 seconds, screen turns black and the goes back to Asus splash screen.
I tried holding power and volume key to get back to fastboot but no luck. Any ideas?

Wow! You are really having some bad luck there!!
First the failed firmware update and now this.... Please post the commands you used to flash CWM.
I have no explanantion for this since you did not even boot into CWM.......
Unless..... the bad firmware flash left a command behind calling the stock recovery to do something (which in your case did not work anyway since it just looped) and now the bootloader tries to execute the command which is not "understood" by CWM. But that still does not explain why you cannot boot into the BL anymore......
Can you turn it off by long pressing power? Try every which way to get into fastboot. Without it there is not much you can do I'm afraid.
Try the restart pin hole (I believe it's on the left side of the tablet near the top) in conjunction with Volume Down, try leaving it alone for a while, try timing the button press somewhat differently - anything to get you into the BL again...
I feel very sorry for you, mate!!

Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.

jggrnaut said:
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
Click to expand...
Click to collapse
I don't know what happened before - maybe you were doomed since the bad firmware flash - but that last step sealed the coffin.
Using Wipe Data from the bootloader with a custom recovery installed is asking for trouble. Never ever do that.... Sorry, it's a brick. [emoji24]

VZW lg g2 stuck?!

My boss went to take the lollipop ota today and his phone is rooted now it boots to twrp (I did not know it was rooted) until I seen the twrp recovery it's stuck looping back into twrp everytime it's reboots NEED HELP ASAP
Thanks in advance

chazla86 said:
My boss went to take the lollipop ota today and his phone is rooted now it boots to twrp (I did not know it was rooted) until I seen the twrp recovery it's stuck looping back into twrp everytime it's reboots NEED HELP ASAP
Thanks in advance
Click to expand...
Click to collapse
The reason why this is happening is you are trying to install the update OTA with a custom recovery. The way these OTA updates work is the OS downloads the file and stores it in a secure location. It has an auto-run updating sequence to allow the OS to update in the regular recovery. Because you have TWRP, TWRP has no idea where to find the file to update the device and therefore, does nothing. However, when you boot up the phone again, it realizes the phone has not yet been updated and goes back into recovery to make sure the update goes through. It is a continuous cycle that therefore never completes it's self. To fix this, run these instructions:
Because the G2 does not have an external SD card, you should do this: use TWRP's awesome "terminal command" option to run the following: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You need to get this PERFECTLY or else you will destroy your phone. Hope this helps.

I found it after doing what I should have done first and took the time to search thanks again

[Not Rooted] HTC one boot loop. currently in cwm recovery, but nothing working

Hello, so...where to start. Phone was original stock. It randomly froze and started boot looping. I had installed the Sprint update 6.23.651. 6 about a month prior to this. (the update made it sluggish)
So I did research, I went to Hboot, but recovery and factory reset didnt do anything. After selecting either one, it just started looping immediately. So tried fastboot commands, nothing work really except erase cache. ADB did not show anywhere even though my drivers were up to date. Contaced HTC and dowloaded the update application. Put the phone on fastboot, ran the wizard. when it was all done, it said it was finish updating. But was still looping. HTC told me i had to send it in and pay a fee. BS! i did nothing to my phone, they broke it with the updates.
Long story short, i figure how to unlock it. Great, so i started trying to flash updates that had the same CID and Model. To list last few:
1) Guru_Reset_M7_Sprint_1.31.651.2
2)Guru_Reset_M7_Sprint_3.04.651.2
3)RUU_M7_WLS_JB_50_Sprint_1.29.651.7
But none of them worked. Just gave me some error that i cant recal. tried other comands that further bricked my phone, like (fastboot flash boot boot_signed.img) (fastboot flash recovery recover.img). I have been working on this for 3 days, today is the 4th. After this, it would loop once and turn off. So i tried multiple recovery images out of the zips listed above. Those made it so that it finally say entering recovery, but then it would loop and turn off.
Then i kept reading that people are being told to relock the hboot (fastboot oem relock) and then flash the zip. Tried it with those 3 listed above again. the 12 signature error showed up of course.
Tried running the update 6.23....from spring, the wizard gave me some error, basically, my phone is way off to even set back to where it was at first.
After some research, I tried tried cwm 6.0.4.8-m7 to have a standard known recovery image flashed. I had actually tried it before but it didnt work. and for whatever reason, it lunched clockworkrecovery.
Here i erased data/factory reset. Also wiped the calvik data (something like that) since that what it says everywhere to do for first step. (kept a mental note that wouldn't fix my phone since it was further bricked than before i began). But before exiting the recovery mode, i noticed that adb commands were finally working! so i tried the two methods if found to install a rom. Sideload and push. Through side load, it takes forever to reach 100% but once it gets there it says
* failed to write data 'protocol fault (no status)' * {in cmd}
So i tried to push. after pushing it to the sdcard (internal btw) i got to the sdcard and run it. End result. *(bad) installation aborted * {on the phone}
so then im like whatever, lets reboot and see if anything changes. Bootlooping still. Recovery and factory/reset send me to bootloader now (it used to just loopboot). so i flash recovery again. Doesnt work. fastboot erase cache, then flash image, still not working. So i managed to remember some steps i followed that might of been the reason recovery worked. so I flash boot_signed.img, then flash recovery. doesnt work. so fastboot boot boot.img cmd responds but phone freezes, then manually turn it off. then get back into fastboot, flash recovery, erase cache, flash recovery(x3 times). and recovery works.
This is the 3rd time i got into recovery, but it takes me about 10 mins of doing the different combinations of the what i just mentioned before it goes through.
So im at the point where i could possibly get it fixed. But nothing seems to work
I would really appreciate it if someone could help me. I know that the rom has to match my hboot version? but im at hboot 1.6 and the only thing i found was here
http://forum.xda-developers.com/showthread.php?t=2795856
but that only gives me the firmware and the exe that doesnt work for me. I also tried to run the exe and during it, seach my C-drive for rom.zip. Apparently it creates a temporary rom. I pulled it out, it doesnt contain everything
Last thing i was going to do, was put relock it and run recovery. but because im not sure how to make recovery work every time from the get-go. when relocked, recovery didnt work, so i had to flash, thus i had to unlock, spent 10 minutes making it work and forgot that it was unlocked. I could try and see if i could relock and get recovery to run. But it could take forever to get it to work, thus is why im looking to see if there is anything i can do from recovery. (also, both time i was in recovery, i did erase wipe everything, so maybe thats why it wont work after reboot and have to reflash it)
This is where im on.
clockwork recovery window in phone.
phone stuff:
hboot-1.6 something
s-on
os 6.23.651...etc
cid SPCS_001
modelid: PN0720000
the guru zip mention above have the same cid and modelid as my phone according to
http://www.htc1guru.com/downloads/ruu-file-downloads/
Thank You, I hope i am as close to fixing it as i think i am.

madeofscars117 said:
Hello, so...where to start. Phone was original stock. It randomly froze and started boot looping. I had installed the Sprint update 6.23.651. 6 about a month prior to this. (the update made it sluggish)
So I did research, I went to Hboot, but recovery and factory reset didnt do anything. After selecting either one, it just started looping immediately. So tried fastboot commands, nothing work really except erase cache. ADB did not show anywhere even though my drivers were up to date. Contaced HTC and dowloaded the update application. Put the phone on fastboot, ran the wizard. when it was all done, it said it was finish updating. But was still looping. HTC told me i had to send it in and pay a fee. BS! i did nothing to my phone, they broke it with the updates.
Long story short, i figure how to unlock it. Great, so i started trying to flash updates that had the same CID and Model. To list last few:
1) Guru_Reset_M7_Sprint_1.31.651.2
2)Guru_Reset_M7_Sprint_3.04.651.2
3)RUU_M7_WLS_JB_50_Sprint_1.29.651.7
But none of them worked. Just gave me some error that i cant recal. tried other comands that further bricked my phone, like (fastboot flash boot boot_signed.img) (fastboot flash recovery recover.img). I have been working on this for 3 days, today is the 4th. After this, it would loop once and turn off. So i tried multiple recovery images out of the zips listed above. Those made it so that it finally say entering recovery, but then it would loop and turn off.
Then i kept reading that people are being told to relock the hboot (fastboot oem relock) and then flash the zip. Tried it with those 3 listed above again. the 12 signature error showed up of course.
Tried running the update 6.23....from spring, the wizard gave me some error, basically, my phone is way off to even set back to where it was at first.
After some research, I tried tried cwm 6.0.4.8-m7 to have a standard known recovery image flashed. I had actually tried it before but it didnt work. and for whatever reason, it lunched clockworkrecovery.
Here i erased data/factory reset. Also wiped the calvik data (something like that) since that what it says everywhere to do for first step. (kept a mental note that wouldn't fix my phone since it was further bricked than before i began). But before exiting the recovery mode, i noticed that adb commands were finally working! so i tried the two methods if found to install a rom. Sideload and push. Through side load, it takes forever to reach 100% but once it gets there it says
* failed to write data 'protocol fault (no status)' * {in cmd}
So i tried to push. after pushing it to the sdcard (internal btw) i got to the sdcard and run it. End result. *(bad) installation aborted * {on the phone}
so then im like whatever, lets reboot and see if anything changes. Bootlooping still. Recovery and factory/reset send me to bootloader now (it used to just loopboot). so i flash recovery again. Doesnt work. fastboot erase cache, then flash image, still not working. So i managed to remember some steps i followed that might of been the reason recovery worked. so I flash boot_signed.img, then flash recovery. doesnt work. so fastboot boot boot.img cmd responds but phone freezes, then manually turn it off. then get back into fastboot, flash recovery, erase cache, flash recovery(x3 times). and recovery works.
This is the 3rd time i got into recovery, but it takes me about 10 mins of doing the different combinations of the what i just mentioned before it goes through.
So im at the point where i could possibly get it fixed. But nothing seems to work
I would really appreciate it if someone could help me. I know that the rom has to match my hboot version? but im at hboot 1.6 and the only thing i found was here
http://forum.xda-developers.com/showthread.php?t=2795856
but that only gives me the firmware and the exe that doesnt work for me. I also tried to run the exe and during it, seach my C-drive for rom.zip. Apparently it creates a temporary rom. I pulled it out, it doesnt contain everything
Last thing i was going to do, was put relock it and run recovery. but because im not sure how to make recovery work every time from the get-go. when relocked, recovery didnt work, so i had to flash, thus i had to unlock, spent 10 minutes making it work and forgot that it was unlocked. I could try and see if i could relock and get recovery to run. But it could take forever to get it to work, thus is why im looking to see if there is anything i can do from recovery. (also, both time i was in recovery, i did erase wipe everything, so maybe thats why it wont work after reboot and have to reflash it)
This is where im on.
clockwork recovery window in phone.
phone stuff:
hboot-1.6 something
s-on
os 6.23.651...etc
cid SPCS_001
modelid: PN0720000
the guru zip mention above have the same cid and modelid as my phone according to
http://www.htc1guru.com/downloads/ruu-file-downloads/
Thank You, I hope i am as close to fixing it as i think i am.
Click to expand...
Click to collapse
Make sure you have latest HTC drivers installed on your computer, relock your bootloader and then launch the 6.23.651.6 RUU

Wow, I dont know why I didnt think of that. Everything must be running together.
Alright, so it updated. My phone is back to how it used to be looping like when it first broke. So, from here. Should I unlock it, flash the recovery to cwm, relock bootloader and see if it enters cwm recovery and try to push or sideload a rom?
when relock, i beleive it restarts, so i dont know if it that would stop the cwm recovery from working. Also, if i manage to get all of what i mentioned working. Wouldnt I get the 12 signature error?
Im sorry, its been days and nothing seems clear anymore since I havent been able to fix it

Phone only boots to recovery

Hi All,
I'm having difficulty getting my C6603 to load in to anything other than recovery.
I unlocked the bootloader, installed TWRP (twrp-3.0.2-0-yuga.img) and believe I have root permissions on the device. When the phone is off and unplugged from my PC, if I press and hold the power button it will show the Sony logo then load into TWRP.
Any ideas what I've done wrong?
Edit: I seem to have fixed it by downloading a different boot image and redoing the steps. I lost all data but at least it is better than a bricked phone.

did you install the recovery in boot partition using fastboot commands?
if yes then that is the reason you are booting into recovery.
use dd method to install twrp in FOTA partition.
edit: opps din read your 'edit' part of post gl mate

My Galaxy S4 active (AT&T) is bricked, tried to restore it

This is my backup phone so I don't care for the data that is on it and just want it working again. It was rooted before and I needed it unrooted in order to download an app that was blocked by root detection. I tried uninstalling the root using Super SU in its settings, when I restarted my phone it just freezes at the AT&T white screen.
I'm still able to go into the boot recovery menu, I tried putting on the I537UCUCOC7 (5.0.1) firmware found here (https://forum.xda-developers.com/showthread.php?t=2629093). I downloaded it, extracted the zip, and renamed the file "update.zip" and put the file on a microSD then in the recovery boot menu I went to install from external and selected the update.zip. It sorta kinda looked like it accepted it but I get a red error message about the sideloader and I'm still stuck at the white screen when it boots.
What else can I do from here?
P.S. I already tried wiping the cache and data/factory restore options and that didnt work.

Is there anything else that can be done?

I restored my phone to 4.4.2. How can I install 5.0.1? When I search for software updates it says theres nothing available even though I know it can go to 5.0.1 cause thats what I had before it bricked.

Please share how did you restore when I only able to boot into recovery and clearing cache and factory reset does not help. Phone just stack on boot loop

RemixDeluxe said:
I restored my phone to 4.4.2. How can I install 5.0.1? When I search for software updates it says theres nothing available even though I know it can go to 5.0.1 cause thats what I had before it bricked.
Click to expand...
Click to collapse
alex4cta said:
Please share how did you restore when I only able to boot into recovery and clearing cache and factory reset does not help. Phone just stack on boot loop
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s4-active/general/guide-update-to-i537-att-firmware-t2835481