[Q] [Support] Updated before un-rooting, help! - Thunderbolt Q&A, Help & Troubleshooting

So I grabbed the 2.11.605.5 update this morning, and before thinking, hit update. I rooted the phone just a few days ago, and now the phone is caught in a loop of powering down, showing the "unpacking box" screen with a progress bar, then a triangle with an angry exclamation point in the middle. Eyagh!
Verizon and HTC tech support only suggest a factory reset. I'd obviously like to avoid this if possible.
I note when I go into the HBOOT menu, and select RECOVERY (putting me into the ClockworkMod Recovery menu) that I'm offered an option to "backup and restore". Is this feasible, or will it only restore the corrupted system?
Does anyone have any ideas of what else I can do? I've done a quick search of the forum, and don't find any relevant topics, but perhaps there's some institutional memory here of someone similarly stupid, and a fix?
I appreciate the help, folks.

You're probably going to have to flash another ROM.
Sent from my ADR6400L using XDA App

If you can get into recovery, just restore your last nano.

Fastlivin said:
So I grabbed the 2.11.605.5 update this morning, and before thinking, hit update. I rooted the phone just a few days ago, and now the phone is caught in a loop of powering down, showing the "unpacking box" screen with a progress bar, then a triangle with an angry exclamation point in the middle. Eyagh!
Verizon and HTC tech support only suggest a factory reset. I'd obviously like to avoid this if possible.
I note when I go into the HBOOT menu, and select RECOVERY (putting me into the ClockworkMod Recovery menu) that I'm offered an option to "backup and restore". Is this feasible, or will it only restore the corrupted system?
Does anyone have any ideas of what else I can do? I've done a quick search of the forum, and don't find any relevant topics, but perhaps there's some institutional memory here of someone similarly stupid, and a fix?
I appreciate the help, folks.
Click to expand...
Click to collapse
Did you make a backup anytime before this happened? If so, just restore that backup and you should be good to go. If not, make a backup now, flash whatever rom you had before, again, but don't wipe anything. This probably won't work, but if it does, might be able to save everything that you had before these bootloops.

Related

[Q] Help with Eris and Evil Eris

I'm having a little trouble and I'm sincerely hoping you'll help. I've tried flashing my Eris using the file, "Evil_Tazz_3.zip" and my Eris is now bricked and stuck in a bootloop. All it will do is show an animation of the sketchy letters ANDROID falling down the screen and then a smoky light following close behind it reveling the Droid itself. And it'll repeat this animation rapidly about 100 times before freezing and then restarting the whole process all over. To be frank it pisses me off because it always seems that I'm the only one who has trouble with this stuff.
My Eris is rooted and it does allow me to access the recovery screen. What am I supposed to do?
Anyways, thanks for your time.
Best Regards -Joseph Bergen
jbergen said:
I'm having a little trouble and I'm sincerely hoping you'll help. I've tried flashing my Eris using the file, "Evil_Tazz_3.zip" and my Eris is now bricked and stuck in a bootloop. All it will do is show an animation of the sketchy letters ANDROID falling down the screen and then a smoky light following close behind it reveling the Droid itself. And it'll repeat this animation rapidly about 100 times before freezing and then restarting the whole process all over. To be frank it pisses me off because it always seems that I'm the only one who has trouble with this stuff.
My Eris is rooted and it does allow me to access the recovery screen. What am I supposed to do?
Anyways, thanks for your time.
Best Regards -Joseph Bergen
Click to expand...
Click to collapse
Whatever you do, DO NOT DO ANYTHING ELSE UNTIL BTFB0 responds to your plea for help.
Do not just start trying different solutions, DO NOT FLASH ANY RUU, if you know what that is. BTFB0 is the guy who can get your phone unbricked if anyone can. He is the expert, I won't pretend to be able to duplicate his knowledge in this area.
Be patient until he has a chance to see this. You don't have to PM him, I'm sure he'll respond when he has a chance here in public. He will ask specific questions about what version of bootloader you have, 1.47 or 1.49, and you might as well find out if it's S=OFF or S=ON.
Also, do you have Amon RA recovery on your phone and can you get to it?
Have you tried flashing anything else since your phone has gotten stuck in this boot loop? If not and you can get into recovery still, then simply wipe data, wipe dalvik, and try flashing again. Don't worry you're phone doesn't sound bricked, just like you got a bad download or an error when flashing the rom. I would probably try a different rom or at least re-download the one you want to use.
It may still be wise to wait for BTFB0 to get here and offer some more advice as I am sure he has more knowledge in this area than me. But I do feel confident that he will say the same thing as I have.
Well, the OP merely said that he is having trouble with a specific ROM; he didn't mention failures during flashing; so, his problem could be as simple as having failed to "wipe" before flashing his ROM.
jbergen:
If you can boot into a custom recovery, your phone is not "bricked". It's not even soft-bricked; it's just not booting into the main OS correctly.
Providing as much detail as you can is helpful to people that are offering help to you; in particular, the following pieces of information:
- What recovery is on your phone? (Amon_RA, Clockwork? What version #?)
- When you are flashing the ROM file with your recovery, do you notice any "E:" messages?
An "E:" at the beginning of a line on the screen means that an error occurred!
- Are you having this same trouble on more than one ROM, or is this the only ROM you have tried since you rooted?
- What method did you use to root the phone?
- Did you use the "Wipe data/factory reset" menu item before you flashed the ROM file?
- Did you make any Nandroid backups that you still have on your SD card? If yes, did you attempt to restore one? What was the result? (BTW, every rooted phone user should be making Nandroid backups before they flash ROMs - no exceptions.)
- Do you have a media card slot or USB card reader device that will allow you to copy a different ROM file onto your SD card? -OR-
- Do you know how to "mount" the SD card onto the PC when your recovery is booted? (On Amon_RA, it is called "Toggle MS-USB" or something like that; it's also in the Clockwork menu somewhere too)
Given the information you have provided, there are any number of things that could be going on. I would suggest downloading a different ROM to your PC (let's say the stock HTC Eris March 2011 ROM), and then transferring it to your SD card. Then,
- Verify the exact size of the file and/or MD5 signatures of the file (if the developer provided it).
- make sure your phone is well charged
- perform a "Wipe data/factory reset" from the recovery menu
- Flash the ROM file from the recovery menu - and pay attention to the screen to see if there are any `E:' errors
- If there are errors, there is no point in attempting to boot the phone
- If there are no errors, boot the phone.
- Report your results here - and answer the questions that I asked.

[Q] Verizon update crashes, phone reboots

So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Mount the SD card either in recovery or on a PC and see if there is a PG05IMG.zip on it. Remove it if so, then reboot.
tqhx said:
So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Click to expand...
Click to collapse
You can't install an OTA if your rooted, even if you haven't made any changes. The problem is the custom recovery (e.g. ClockworkMod)
When the update tries to install the updated recovery, it sees that the old stock recovery isn't there, and fails.
As far as recovering from that, I'm not entirely sure.
Seeing as you used the one touch root, I doubt you installed the S-Off eng bootloader. Try what the above poster suggested first.
Thanks for the replies guys. I did have s-off, but yeah ill tell you i tried what he suggested with no luck.
I ended up being ok i made another clockwork backup, did a full restore from a backup before the date of the update, then did just a data restore from the backup i had just made. Phone is back to normal. Thanks for the responses, ill give you both marks for being helpful
I'm in the same boat, except I was silly enough to not have a backup made. I do not see the PG05IMG.zip from recovery. Any other possible ways to fix this? If I have to clear all my data and start again, I'm ok with that though I'd obviously prefer not to do that.
Boot into clockwork recovery and wipe cache only.
Sent from my HTC Thunderbolt
This same issue has happened to me with the Verizon update. Long story on how it i clicked okay to the update. I told it reject at least 3 times already.
Anyway - i was stuck in this nasty reboot cycle. I was lucky to have a backup from March when I first rooted my TB. Not having a more recent backup is my bad.
So I have worked most of today with near factory settings from my recovered backup and now I am restoring todays backup to see if I can fix this reboot BS.
I did the Wipe Cache from ClockMod and when the phone rebooted it gave the prompt to reinstall the update which I cancelled. So success!!! Now I can clean up my junk apps and do a proper backup to protect myself in the future.

Stuck on yellow triangle, need fix!

New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
ikradex said:
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
Click to expand...
Click to collapse
Seriously dude? Use some common sense please and give relevant information on what you have. What model/variant do you have, rom are you on, what kernel have you flashed?
How do you expect anybody to be able to help you if you dont give such basic info???
Are you sure the kernel supports the rom/version you have installed?
ikradex said:
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
Click to expand...
Click to collapse
Maybe because you wiped all data....so...there's no ROM to boot up to.
Try flashing one via Odin
gastonw said:
Maybe because you wiped all data....so...there's no ROM to boot up to.
Try flashing one via Odin
Click to expand...
Click to collapse
Wiping data doesnt wipe rom , It just wipes appdata, ie settings etc. All that happens is a factory reset so when you next boot its back to default. For example you would need to re-enter google account and re-install apss either manually or from a backup.
You can only wipe rom by formatting system partition.
TheATHEiST said:
Wiping data doesnt wipe rom , It just wipes appdata, ie settings etc. All that happens is a factory reset so when you next boot its back to default. For example you would need to re-enter google account and re-install apss either manually or from a backup.
You can only wipe rom by formatting system partition.
Click to expand...
Click to collapse
Thought you had me in ignore.
So there's no way you can wipe your OS via recovery? Good to know that, it's like ROM over ROM then. The new one clears the old one.
gastonw said:
Thought you had me in ignore.
So there's no way you can wipe your OS via recovery? Good to know that, it's like ROM over ROM then. The new one clears the old one.
Click to expand...
Click to collapse
I did have you on ignore but I still see little boxes saying this comment has been ignored etc which was actually more annoying so I removed ignore.
Yes you can wipe OS via recovery but only by formatting system/deleting partition etc. All the "wipe" options do is remove files that have been created by rom like app settings/cache etc.
Your confusion was probably also the reason why you made a big thing in a previous topic about you trying to avoid wiping data, because you thought it wiped rom? :silly:
Wiping data/factory reset in cwm is one of the best ways to get rid of system issues, Its basically like doing a clean install of Windows on a PC. After you have wiped you can simply restore your needed apps from a backup using Titanium Backup. Other things like sms/mms etc can be also backed up easily and contacts will be synced via Google account.
TheATHEiST said:
I did have you on ignore but I still see little boxes saying this comment has been ignored etc which was actually more annoying so I removed ignore.
Yes you can wipe OS via recovery but only by formatting system/deleting partition etc. All the "wipe" options do is remove files that have been created by rom like app settings/cache etc.
Your confusion was probably also the reason why you made a big thing in a previous topic about you trying to avoid wiping data, because you thought it wiped rom? :silly:
Wiping data/factory reset in cwm is one of the best ways to get rid of system issues, Its basically like doing a clean install of Windows on a PC. After you have wiped you can simply restore your needed apps from a backup using Titanium Backup. Other things like sms/mms etc can be also backed up easily and contacts will be synced via Google account.
Click to expand...
Click to collapse
hum...okay.
I actually know what Factory Reset does, I mean..."factory"..."reset", kinda......gives it away.
And yes, it made sense to me that you could wipe the ROM you are on before installing a new one, just like the format c:/s days in win98.
You learn something every day, speaking of which, how come no one recommends noobs to root their device with exynos abuse? It's because they're noobs and wouldn't be able to handle/understand the exploit?
I still don't do factory resets because I don't need to, and I avoid needing to perform it.
TheATHEiST said:
Seriously dude? Use some common sense please and give relevant information on what you have. What model/variant do you have, rom are you on, what kernel have you flashed?
How do you expect anybody to be able to help you if you dont give such basic info???
Are you sure the kernel supports the rom/version you have installed?
Click to expand...
Click to collapse
Thanks for the reply Figured if someone was willing to help me I'd give them the information they wanted.
Have Samsung Galaxy S II (GT-I9100) (couldn't tell you what "variant" it is). I was following this guide. It told me to get an insecure kernel from here. The guide said it didn't really matter which kernel I picked so I picked the first one (GT-I9100_BGKF5_insecure) and used Odin to flash it. Got a green pass and the phone began reboot but it's now stuck on the yellow triangle (the warning message that you've flashed an insecure kernel).
I couldn't tell whether there would be compatibility issues as the thread just seems to be one big list of kernels and nothing else. AFAIK the phone was running ICS.
Looking at the replies, I keep seeing factory reset. Is that a liable option to restore my phone back to its original state. I don't care as long the phone works again. If not can someone run through how to fix my predicament I heard if I can access download and recovery mode I should be able to fix it.
ikradex said:
Thanks for the reply Figured if someone was willing to help me I'd give them the information they wanted.
Have Samsung Galaxy S II (GT-I9100) (couldn't tell you what "variant" it is). I was following this guide. It told me to get an insecure kernel from here. The guide said it didn't really matter which kernel I picked so I picked the first one (GT-I9100_BGKF5_insecure) and used Odin to flash it. Got a green pass and the phone began reboot but it's now stuck on the yellow triangle (the warning message that you've flashed an insecure kernel).
I couldn't tell whether there would be compatibility issues as the thread just seems to be one big list of kernels and nothing else. AFAIK the phone was running ICS.
Looking at the replies, I keep seeing factory reset. Is that a liable option to restore my phone back to its original state. I don't care as long the phone works again. If not can someone run through how to fix my predicament I heard if I can access download and recovery mode I should be able to fix it.
Click to expand...
Click to collapse
Of course, you're not bricked yet.
Before trying your back up, why don't you flash a stock ROM via odin and take a long breath?
This is JB leak.
These are ICS, look for 4.0.3 unbranded.
gastonw said:
Of course, you're not bricked yet.
Before trying your back up, why don't you flash a stock ROM via odin and take a long breath?
This is JB leak.
These are ICS, look for 4.0.3 unbranded.
Click to expand...
Click to collapse
I know this is leading onto another thread but my phone now is having trouble connecting to my computer. Keep getting "USB not recognized" error. Installed/Uninstalled kies & drivers then installed drivers again alone and still won't recognize it
Tried another usb port? another pc/laptop? sure kies is not running in background? reinstalled kies?
Don't worry, your pc WILL see your device.
Sent from the little guy

[Q] "No Command"/"Error" in Recovery Mode After OTA Update to 4.3

Hey everyone,
I have an unrooted Samsung Galaxy S3 GT-i9300 on T-Mobile (UK). I recently updated firmware 4.3 and noticed the battery drained really quickly. After a lot of researching, I found that a factory reset should fix the issue, which it did!
I have since discovered that when in recovery mode, everything seems normal (as in the menu is displayed, including the option "Wipe Cache Partition") the words "No Command" is displayed under the Android robot, with a red exclamation mark. If I choose an option, whether it's Wipe Cache Partition" or "Reboot Now" it seems to do the actions(it shows "Erasing" once "Wipe Cache Partition" has been selected and also reboots the phone) but the word "Error" is displayed under the robot when the action has been done or just before the phone reboots, after selecting "Reboot Now"
Is this normal? Why all of a sudden does it say "No Command" and "Error"?
I haven't tried to root my phone or install any custom roms or try to modify the phone in any way since I got it.
Can anyone out there please let me know why these words have started to appear in recovery mode?
I'd really appreciate it!!
P.S. I searched the forums before posting and although some were similar, they didn't cover my exact problem.
Try downloading the same official firmware and flashing with odin, there is a guide in general forum. Factory reset then try again.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Try downloading the same official firmware and flashing with odin, there is a guide in general forum. Factory reset then try again.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your reply. I found the guide to flashing the phone with Odin and I'm a little worried in case I mess up and brick the phone, I read that if you make a mistake, that can happen.
Just to say, I checked the recovery mode again and it seems to do everything normally, such as wiping the cache(it says so in the log) but it just says "No Command" after each action. The word "Error" only appears the very first time you see the robot, and when you select "Reboot Now" just before it reboots "error" shows up under the robot and then the phone restarts.
So, do you know if this is normal? Or do you think it's something to do with the way the firmware 4.3 works?
I'd just like to know whether it's normal or if there's something wrong behind the scenes in the phones firmware.
Hope you can help and thank you again.
MasterfulNinja said:
Thank you very much for your reply. I found the guide to flashing the phone with Odin and I'm a little worried in case I mess up and brick the phone, I read that if you make a mistake, that can happen.
Just to say, I checked the recovery mode again and it seems to do everything normally, such as wiping the cache(it says so in the log) but it just says "No Command" after each action. The word "Error" only appears the very first time you see the robot, and when you select "Reboot Now" just before it reboots "error" shows up under the robot and then the phone restarts.
So, do you know if this is normal? Or do you think it's something to do with the way the firmware 4.3 works?
I'd just like to know whether it's normal or if there's something wrong behind the scenes in the phones firmware.
Hope you can help and thank you again.
Click to expand...
Click to collapse
Honestly, I'd quite like to see a pic of the errors in recovery. Meanwhile if you don't feel like using Odin (if you stick tight to the tutorials nothing bad will happen) you can try to repair with Kies, you might have installed it anyway. Here is a detailed guide http://forum.xda-developers.com/galaxy-s3/general/guide-how-to-reinstall-stock-firmware-t1978840
If this fails for any reason go ahead and try Odin using this noobproof guide http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081. That should almost certainly eradicate any errors.
Benko111 said:
Honestly, I'd quite like to see a pic of the errors in recovery. Meanwhile if you don't feel like using Odin (if you stick tight to the tutorials nothing bad will happen) you can try to repair with Kies, you might have installed it anyway. Here is a detailed guide http://forum.xda-developers.com/galaxy-s3/general/guide-how-to-reinstall-stock-firmware-t1978840
If this fails for any reason go ahead and try Odin using this noobproof guide http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081. That should almost certainly eradicate any errors.
Click to expand...
Click to collapse
Thank you so much for the links! I actually just tried the update via Kies, reinstalling the stock firmware and it took a while and I did everything it said but the messages still show in recovery mode, just like before. So I'm wondering if it's actually supposed to normal to display those words, and maybe that's just that way it is now?
I took some pics of the screen, so you can see what I'm talking about.
Here's the "No Command" message displayed. As you can see, it has wiped the cache partition after I selected it.
https://www.dropbox.com/s/irolo6rp8wh5ibf/Photo 27-04-2014 23 39 34.png
And here's the "Error" message it says just after I've selected "Reboot Now" and before the phone restarts.
https://www.dropbox.com/s/9o0yuopkf3dov76/Photo 27-04-2014 23 40 17.png
Have you seen or heard of this before?
No problem. And no, not in this context. But then again, I haven't had a stock recovery (nor a stock ROM) on my phones for years.
But I do get tons of phones in for repair every week, have not really noticed these 'errors' anywhere.
It seems to execute everything fine.
Would be interesting if you'd flash a TWRP recovery what it says then. You can easily replace it by your stock recovery again.
If everything looks good there then it probably is just the way it is.
Benko111 said:
No problem. And no, not in this context. But then again, I haven't had a stock recovery (nor a stock ROM) on my phones for years.
But I do get tons of phones in for repair every week, have not really noticed these 'errors' anywhere.
It seems to execute everything fine.
Would be interesting if you'd flash a TWRP recovery what it says then. You can easily replace it by your stock recovery again.
If everything looks good there then it probably is just the way it is.
Click to expand...
Click to collapse
That would be interesting, but doing so would require me to root my phone, right?
Oh I see, so it's a quite an unusual thing to happen . . . The fact that it says "Error", yet executes things fine anyway.
I've come to a possible conclusion that it's probably down to that particular version of the stock rom? Maybe people how have updated in the UK, using that version would experience the same? Because, after reinstalling it via Kies, and there being no change regarding those messages in recovery mode, doesn't that point to the firmware being the cause? For example, if I flashed the phone with a custom rom(that didn't have any error messages) surely, those messages wouldn't show up after I'd installed it, right?
Does what I'm saying make sense?
Sorry if I'm going on, I'm not too familiar with the technical side of Anroid systems.
MasterfulNinja said:
That would be interesting, but doing so would require me to root my phone, right?
Oh I see, so it's a quite an unusual thing to happen . . . The fact that it says "Error", yet executes things fine anyway.
I've come to a possible conclusion that it's probably down to that particular version of the stock rom? Maybe people how have updated in the UK, using that version would experience the same? Because, after reinstalling it via Kies, and there being no change regarding those messages in recovery mode, doesn't that point to the firmware being the cause? For example, if I flashed the phone with a custom rom(that didn't have any error messages) surely, those messages wouldn't show up after I'd installed it, right?
Does what I'm saying make sense?
Sorry if I'm going on, I'm not too familiar with the technical side of Anroid systems.
Click to expand...
Click to collapse
No, you don't need root for flashing TWRP via Odin. Use this great and easy guide (if the guide helped you hit the users thanks button):
http://forum.xda-developers.com/galaxy-s3/help/twrp-flashing-tar-t2680354
I'm not sure if this is really the UK-ROM or just a common thing under certain circumstances and I've just never noticed it, but I really doubt it.
If everything is fine with TWRP and also installing ROMs causes no problems I would just accept this as one of the never solved mysteries - which I rarely do normally
we have same issue i already flash custom recovery via odin stil no command when i rebooting into recovery. . did you fix it?

Delete

Delete
Peeptastic said:
Hard reset my phone and now I can't get past the set up screen. It may be because I used titanium backup to free a few apps and did not disable this before the hard reset. I get as far as the wifi setup screen and it won't get any farther. It either gets stuck at "Just a sec" (the next button is there, and when I press it it makes a noise, but it does not do anything) or "checking for updates". I can get into stock recovery. Factory reset and clear cache don't seem to have an effect. Can someone please help me? Thanks either way. Oh, I have the Sprint LS991 G4. Please.
Click to expand...
Click to collapse
Sounds like using Titanium backup is the cause of this. You may need to flash your stock firmware, if this is even an option yet for this new device. Did you not make a backup of stock? Or is custom recovery even available yet? Anyway, you could ask for further assistance in your device's specific help forum here:
http://forum.xda-developers.com/sprint-g4/help
Good luck!
Delete

Categories

Resources