Does the thunderbolt need to be rooted to upload a stock PG05IMG from my SD card? Im trying to load PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_release_174685_signed.zip from my SD card as my handset is stuck at the bootup screen, thus wont reload through an RUU.
The phone was previously rooted by someone else and I did a system clear through the clockwork recovery (Version 3.1.0.2) menu to wipe their info. Afterwards, it only showed the bootscreen. Oops....
Ive tried to load the aforementioned file through the bootloader screen by renaming it PG05IMG.zip, etc, but the phone keeps rejecting it.
killgorian said:
Does the thunderbolt need to be rooted to upload a stock PG05IMG from my SD card? Im trying to load PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_release_174685_signed.zip from my SD card as my handset is stuck at the bootup screen, thus wont reload through an RUU.
The phone was previously rooted by someone else and I did a system clear through the clockwork recovery (Version 3.1.0.2) menu to wipe their info. Afterwards, it only showed the bootscreen. Oops....
Ive tried to load the aforementioned file through the bootloader screen by renaming it PG05IMG.zip, etc, but the phone keeps rejecting it.
Click to expand...
Click to collapse
What exactly are you trying to do? Completely unroot the thing and put S-On? I'd like to be sure before I dole out instructions. And why such an old RUU? Why not the 1.70 RUU. And how was the Tbolt rooted and S-Off'd before?
Honestly, Im just trying to get it to boot again as easily as possible. I dont care if it's rooted, unrooted, anything, I'd just like it to work.
I grabbed the old RUU because I figured I could update from there. It actually makes no difference to me at this point what's on it, I just want it to work again. lol
killgorian said:
Honestly, Im just trying to get it to boot again as easily as possible. I dont care if it's rooted, unrooted, anything, I'd just like it to work.
I grabbed the old RUU because I figured I could update from there. It actually makes no difference to me at this point what's on it, I just want it to work again. lol
Click to expand...
Click to collapse
I hope wiser minds than mine chime in, but I don't think flashing an old RUU would be wise if Revolution was used. Revolution replaces the hboot and I don't think flashing a new RUU replaces it. I'm not sure what bad would come of it, actually.
It sounds to me like you just need to flash a new ROM. I don't know what radios you have, but you probably have newer ones since those are the radios of choice for newer ROMs. I'd try that first. If that doesn't do it, then I think what needs to happen next it to figure out what hboot you have. If it was done via the jcase method, then flashing an RUU should work fine. If not, well... I'm not an expert on that front, but there are threads on that subject. I wish I could dish out a real simple answer, but I'm not sure it so simple.
Definitely sounds like all that is needed in the OP's case is to flash a new ROM (custom or stock) from recovery as loonatik suggested or possibly restore a backup if one exists. Just sounds like /system was formatted and nothing flashed afterwards.
Absolute_Zero said:
Definitely sounds like all that is needed in the OP's case is to flash a new ROM (custom or stock) from recovery as loonatik suggested or possibly restore a backup if one exists. Just sounds like /system was formatted and nothing flashed afterwards.
Click to expand...
Click to collapse
Thanks for confirming. If you can hold volume-down while powering it up and get into ClockworkMod, flashing another ROM is just a matter of a few button pushes.
Exactly what I thought. I've loaded custom roms on the a855 and Eris before, but the above file won't load. I'm wondering if the bl is locked but it has clockwork, so I'm confused...
That's an entire RUU. That's why. Go get just a ROM and flash through clockwork.
Hey just wanted to say that worked and thank you very much. I am a bit curious however as to why the full RUU didnt work...
killgorian said:
Hey just wanted to say that worked and thank you very much. I am a bit curious however as to why the full RUU didnt work...
Click to expand...
Click to collapse
A full RUU contains a LOT more than just a ROM. It must also be flashed differently; through the bootloader and not recovery. An RUU contains a new bootloader and radios, as well as a ROM. If you'd flashed that RUU correctly through the bootloader, you probably would have lost S-Off and root, or ended up with a device that did even less desirable things... like bootloop.
Thats what I actually tried to do. I renamed and tried to upload through bootloader but it failed. I've flashed RUU's before but never had the issue which worries me a bit. Could be my "bad luck" saved my butt from a more serious issue.
However I loaded the PlainJane rom and it appears I killed my radio now so my journey through aggravation has not yet ended. lol. Im going over your very helpful Q&A post now and seeing if I have a compatible radio for the ROM.
Edit: Nevermind, it seems to be good to go. Thanks again for the help.
killgorian said:
Thats what I actually tried to do. I renamed and tried to upload through bootloader but it failed. I've flashed RUU's before but never had the issue which worries me a bit. Could be my "bad luck" saved my butt from a more serious issue.
However I loaded the PlainJane rom and it appears I killed my radio now so my journey through aggravation has not yet ended. lol. Im going over your very helpful Q&A post now and seeing if I have a compatible radio for the ROM.
Click to expand...
Click to collapse
in the rom thread most devs put what radios are compatible and a link to the radio. Not sure how new plainjane is, but most of the newer radios work with all the custom roms.
killgorian said:
Thats what I actually tried to do. I renamed and tried to upload through bootloader but it failed. I've flashed RUU's before but never had the issue which worries me a bit. Could be my "bad luck" saved my butt from a more serious issue.
However I loaded the PlainJane rom and it appears I killed my radio now so my journey through aggravation has not yet ended. lol. Im going over your very helpful Q&A post now and seeing if I have a compatible radio for the ROM.
Click to expand...
Click to collapse
If you used Revolution or updated to the patched bootloader, it's designed to not allow flashing over. That's probably why it failed.
Related
Oh, fuuuu...crap.
I may have screwed up here. I rooted my device using Revolutionary, and then using ROM Manager installed the latest Synergy mod on my stock (unrooted Froyo) Thunderbolt. Everything loaded fine, it seemed to be flawless ... but after the update I'm not getting any signal at all. I figured this was a radio issue, so I downloaded the latest radio that was leaked (the 2.11.605 one), put it on my SD card, and flashed that. It said it was "updating" the radio (RADIO_V2), but still no luck. I've tried a few different versions, and although it seems to "flash" and update fine, there's still no signal. Not 1x, 3g, or 4g. Nada. :-\
According to HBOOT, "RADIO" is 1.16.00.0223r, if that helps.
Any ideas on how I can basically undo all this, or have I spectacularly failed at this?
-BT7
bandtrumpet7 said:
Oh, fuuuu...crap.
I may have screwed up here. I rooted my device using Revolutionary, and then using ROM Manager installed the latest Synergy mod on my stock (unrooted Froyo) Thunderbolt. Everything loaded fine, it seemed to be flawless ... but after the update I'm not getting any signal at all. I figured this was a radio issue, so I downloaded the latest radio that was leaked (the 2.11.605 one), put it on my SD card, and flashed that. It said it was "updating" the radio (RADIO_V2), but still no luck. I've tried a few different versions, and although it seems to "flash" and update fine, there's still no signal. Not 1x, 3g, or 4g. Nada. :-\
According to HBOOT, "RADIO" is 1.16.00.0223r, if that helps.
Any ideas on how I can basically undo all this, or have I spectacularly failed at this?
-BT7
Click to expand...
Click to collapse
Well you shouldn't panic. Which radio did you flash? I would flash the MR2 one from this link http://forum.xda-developers.com/showthread.php?t=1154010 . If that doesn't work, I would download the rom directly from Synergy here http://androidfilehost.com/XxXViRuSXxX/roms/synergy/thunderbolt/
From recovery, wipe everything manually (Wipe data/cache/dalvik) than flash the file from where it is on your SD card. If you need specific instructions feel free to ask.
bandtrumpet7 said:
Oh, fuuuu...crap.
I may have screwed up here. I rooted my device using Revolutionary, and then using ROM Manager installed the latest Synergy mod on my stock (unrooted Froyo) Thunderbolt. Everything loaded fine, it seemed to be flawless ... but after the update I'm not getting any signal at all. I figured this was a radio issue, so I downloaded the latest radio that was leaked (the 2.11.605 one), put it on my SD card, and flashed that. It said it was "updating" the radio (RADIO_V2), but still no luck. I've tried a few different versions, and although it seems to "flash" and update fine, there's still no signal. Not 1x, 3g, or 4g. Nada. :-\
According to HBOOT, "RADIO" is 1.16.00.0223r, if that helps.
Any ideas on how I can basically undo all this, or have I spectacularly failed at this?
-BT7
Click to expand...
Click to collapse
Am I reading this right???? You said you rooted with Revolutionary.... Then you flashed some Synergy mod with ROM Manager (always a no-no).... onto your STOCK, UNROOTED FROYO Tbolt???? How did we go from rooted with Revolutionary to stock, unrooted Froyo? I'm confused.
loonatik78 said:
Am I reading this right???? You said you rooted with Revolutionary.... Then you flashed some Synergy mod with ROM Manager (always a no-no).... onto your STOCK, UNROOTED FROYO Tbolt???? How did we go from rooted with Revolutionary to stock, unrooted Froyo? I'm confused.
Click to expand...
Click to collapse
Sure hope he's just confused...
loonatik78 said:
Am I reading this right???? You said you rooted with Revolutionary.... Then you flashed some Synergy mod with ROM Manager (always a no-no).... onto your STOCK, UNROOTED FROYO Tbolt???? How did we go from rooted with Revolutionary to stock, unrooted Froyo? I'm confused.
Click to expand...
Click to collapse
Lol I saw that, I decided not to say anything, I guess you have the sharper tongue than me
Ya pretty scary. I'm hoping he meant he rooted his phone and when he said unrooted, he meant "stock" froyo build on his phone.
Sounds like he is able to boot up, just not get any signal.
I'm guessing he is not too skilled in the ways of Android yet.
Lol just found something interesting. Synergy isn't even on rom manager? I was checking to see if the version ofcsynergy he was using was a previous froyo build, and I can't even find it on rom manager
He probably meant that he used Rom Manager to load the rom rather than using recovery.
haha weird
OK, so I was tired when I wrote my initial post, and I probably didn't make a whole lot of sense. Let me be a bit clearer.
For reference, no, I'm "not too skilled in the ways of Android yet". I've been living with Froyo, anxiously awaiting Gingerbread, and then got fed up and read about all the benefits that come with rooting. Now that an easier method has presented itself - the Revolutionary method, as opposed to opening a command prompt and doing the adb stuff, which I can do - I rooted a friend's phone - but decided to not take the plunge myself - I decided to go ahead and give GB a shot.
So let me break down what happened:
- My phone was unrooted previously, running the same software it came with. I'd done a few OTA updates that Verizon provided but had never gone into my phone. That's why I called it "stock", sorry if that terminology confused people. I just meant it was the OS that came on my phone - Android 2.2 w/ HTC Sense and all that jazz.
- I ran the Revolutionary method posted in the "Thunderbolt Android Development" forum. Worked fine. Ran Recovery and installed Superuser permissions as the documentation said. Worked great. Have a phone where if HBOOT launches, it says -Revolutionary- at the top, and it's got -S OFF. My phone technically is rooted.
- The Synergy mod was also posted in the "TB Android Development" forum. I downloaded that and installed it using ROM Manager (Install ROM from SD). Worked fine ... but then had no signal. Every other aspect of the phone seemed to be working. My radio just wasn't working.
- Downloaded an updated radio from the TB Android Dev. forum, ran that, it said it was updating the radio. Rebooted the phone after the update ... still no signal.
I "solved" this problem by flashing the leaked HTC/TB Gingerbread build, the latest one that was like 400 MB, and when I booted my phone up again I had Gingerbread on my phone with HTC Sense 2.1, and I had signal. So I'm living right now with a fully working phone, but I wanted to dip my foot into custom ROMs. So now I have a backup method just in case the radio thing doesn't work again, but what can I do to install a custom ROM and ensure that I get signal?
Thanks for the response, xebryus - and to everyone else, sorry I was a little confusing. Everybody starts from somewhere, right?
-BT7
Download the GB ROM you want, boot into clockwork (please don't install VIA ROM Manager). In clockwork using you Volume keys to move and the Home button to select....
Select Wipe Data/Factory Reset
Select Wipe Cache
Select Advanced
Select Wipe Dalvik
Select Go Back
Select Mounts and Storage
Select Format /system
Select Go Back Until you are at the first screen
Select Install from SD Card
Select Choose ZIP
Go to the folder where you downloaded the ROM
Select ROM
Select Yes.
When it is done Reboot.
Enjoy!
Sent from my SHIFTAO5P using XDA App
Hey, at least you didn't brick your phone, so kudos for you for getting that far.
As others have stated there are basically two kinds of radio versions out there. One that work with Froyo builds and ones that work with GB builds.
So depending on the rom you are loading, you just have to make sure you have the right radio to match the rom(the rom thread should tell you what radio it requires). From what you were saying, it sounded like you just had the wrong radio.
Anyways, couple of things you want to make sure you do. Any check to make sure the checksum is correct on the radio (so that it's not corrupt) otherwise you could have some major issues. Also, once you flash the radio and you get your phone back up, make sure to either rename or delete the PG05img file from your SD root, otherwise, again a major hassle.
Check out the noob thread at the top of this forum also. It has great info there that will help you on your journey.
Good Luck.
I have always felt more in control flashing from recovery or hboot but I'm curious why no rom manager?
Sent from my Tbolt running Das Bamf 3.0...
RevosFTS said:
I have always felt more in control flashing from recovery or hboot but I'm curious why no rom manager?
Sent from my Tbolt running Das Bamf 3.0...
Click to expand...
Click to collapse
When the TB first came out, it seemed that people were having issues with using rom manager to flash roms (alot of force closes, things in general not working correctly). So many experienced people said to use recovery rather than rom manager to flash anything on the TB.
I guess that idea just kinda stuck after that.
Ok thanks. I will still use recovery anyhow I am more used to it. Plus I'm kinda old school I love adb haha
Sent from my ADR6400L using XDA App
I have downloaded Synergy Rom and have no problems except that I am not able to get the radio to flash. I am on verizon and chose the MR3.5 radio. I did a battery pull and then pressed the power and volume down button to enter HBoot but I do not have an option to Upgrade. What am I doing wrong any help is appreciated. I need help quick, thanks!!!
1more thing when i am in the HBoot window my only options are Fastboot, Recovery, Factory Reset, Simlock, Hboot USB, System Info, Image Crc..... it says radio is 1.16.00.0402w.
Does this mean the radio was already upgraded. Why can I not get a signal then?
Did you rename the .zip and have it on the root of your SD card?
Sent from my ADR6400L using XDA App
HarlyFan said:
1more thing when i am in the HBoot window my only options are Fastboot, Recovery, Factory Reset, Simlock, Hboot USB, System Info, Image Crc..... it says radio is 1.16.00.0402w.
Does this mean the radio was already upgraded. Why can I not get a signal then?
Click to expand...
Click to collapse
Nope..402w is still MR1. Sounds like you are already in bootloader so at this point if it isn't updating then more than likely the file is named incorrectly as stated above.
Radios HAVE to be named PG05IMG.zip (3rd character is a ZERO, not the letter "O"). It HAS to be in the root folder of your SD card. Now, turn the phone OFF.
Next, hold down the VOL-DOWN button. Keep it held down. Is it still held down ? If so, push and hold down the POWER button. When the screen turns on, you can release both. This menu will automatically look for 3 or 4 files with certain names. One of the names (files) it looks for is .... PG05IMG.zip. When/if it finds it, it will check it and ask you if you want to load it. Tell it to load it and then leave your phone alone. It will update it and reboot like normal (if successful).
Hello, and sorry for filling up the forums here in the Q&A. I really need some help, It is quite urgent. I am losing work, and all this stuff. I am running Amon Ra, and CleanROM 4.1
My phones keeps rebooting, randomly. Even if I remove the back cover, sim card, and SD card. I can't touch the dialer, If I do. BOOM, reboot. I will get 2 minutes to mess around, them reboot. Sometimes 2 seconds. This is very annoying. Should I flash a different Rom? GO back to complete stock? Flash this? Flash that? I need a professional answer here guys :/
Is this the first Rom you flashed? Did the problem present immediately? The more details the more we can narrow down your problem.
I have flashed countless amount of roms, this starting happening when I flashed this: http://forum.xda-developers.com/showthread.php?t=1556183 Ever since, everytime I power up my phone, I get like 30 seconds of usage then bam, reboot. I tried different roms and everything, It could be a problem, I've also tried Rez Rom, Or just ICS. I have tried a battery from my T bolt and got farther, but still got rebooted on. My SD card, both external and internal are wiped, everything, I mean everything I have wiped individually in amon ra recovery. Could it be my SIM Card? It says SIM CARD IS NOT AVAILABLE, After 10 seconds I get a weak signal, then when I go to dialer, it reboots.
Did the SIM card go bad? The rom could be the culprit, but how? I have flashed 3 different roms since. (Senseless clean rom 4.0, Clean Rom 4.1, Rez Rom 3.2) What could have changed? I haven't used my phone in 6 hours or so. Should I go into verizon to get a new SIM? Should I fear that they wont service me due to my unlocked rezound? I have tried everything. My next step is to flash an old rom, to see what happens.
T Greezy said:
I have flashed countless amount of roms, this starting happening when I flashed this: http://forum.xda-developers.com/showthread.php?t=1556183 Ever since, everytime I power up my phone, I get like 30 seconds of usage then bam, reboot. I tried different roms and everything, It could be a problem, I've also tried Rez Rom, Or just ICS. I have tried a battery from my T bolt and got farther, but still got rebooted on. My SD card, both external and internal are wiped, everything, I mean everything I have wiped individually in amon ra recovery. Could it be my SIM Card? It says SIM CARD IS NOT AVAILABLE, After 10 seconds I get a weak signal, then when I go to dialer, it reboots.
Did the SIM card go bad? The rom could be the culprit, but how? I have flashed 3 different roms since. (Senseless clean rom 4.0, Clean Rom 4.1, Rez Rom 3.2) What could have changed? I haven't used my phone in 6 hours or so. Should I go into verizon to get a new SIM? Should I fear that they wont service me due to my unlocked rezound? I have tried everything. My next step is to flash an old rom, to see what happens.
Click to expand...
Click to collapse
Holy hell, it's crazy in here tonight. There are three people with a similar issue running around right now.
You did install the new RUU right before installing this ROM? If not, your solution is right here.
If so, do it again.
If you've done it again already, give some more details as to when it started and what you did right before.
---------- Post added at 08:28 PM ---------- Previous post was at 08:25 PM ----------
a-jive said:
Holy hell, it's crazy in here tonight. There are three people with a similar issue running around right now.
Click to expand...
Click to collapse
Ha, never mind. You just have two threads on the same topic. Bad form, sir! No flaming from me, but that sort of thing gets some folks around here PISSED.
I am very sorry. How do I check the RUU Version? I don't remember flashing one before flashing that ROM. I don't really know, but does the PRL have something to do with this? I think I have accidentally messed with that by NOT being on that new RUU leak before I flashed the rom, so with that being said, the other new roms, I have to be on that new RUU ( 3.11.605.22 ) to have the rom stable, and not rebooting? Correct? Thank you for your guys help!
T Greezy said:
I am very sorry. How do I check the RUU Version? I don't remember flashing one before flashing that ROM. I don't really know, but does the PRL have something to do with this? I think I have accidentally messed with that by NOT being on that new RUU leak before I flashed the rom, so with that being said, the other new roms, I have to be on that new RUU ( 3.11.605.22 ) to have the rom stable, and not rebooting? Correct? Thank you for your guys help!
Click to expand...
Click to collapse
No prob here. Just warning you! Some of the old hands around here get tired of us noobs (I was a green horn not too long ago myself).
Boot into your bootloader, the newest HBOOT should be listed as 2.21.0000 and the date is Mar 11, 2012. If those are off, check out that link I posted. If you don't remember doing it (it's a PITA) you probably didn't do it.
No matter what though, if you can't get the phone to stop rebooting on you, you should RUU back to stock before trying anything.
When you unlock, make sure you flash the newest version of Amon Ra, because 3.14 has some issues with the new firmware.
Go slow and it'll be fine. For the record, in the instruction I sent he mentions that it may hang on the HTC screen for a couple minutes the first reboot.... it hung for almost 20 min when I did it. So don't get impatient!
Good luck.
Not trying to scold anyone here but next time read ALL the threads about it before trying to update to an RUU and 99% of these problems will just go away
werdna87 said:
Not trying to scold anyone here but next time read ALL the threads about it before trying to update to an RUU and 99% of these problems will just go away
Click to expand...
Click to collapse
No doubt, dude. Personally, I study my ass off before I do something that could kill my $500+ pocket computer. But I don't mind helping out those who skip the important parts.... some days anyway!
Running the new RUU is a nerve wracking ordeal, no doubt! You have to be patient and run everything twice. Patience is the name of the game!
OLDsJUNKIE said:
Running the new RUU is a nerve wracking ordeal, no doubt! You have to be patient and run everything twice. Patience is the name of the game!
Click to expand...
Click to collapse
bad logic to go by, some things brick if you run twice, AKA Froyo radio on the Inc
Hey guys! Just updated to the new version of Amon Ra. I am currently waiting for the new RUU to download. In the meantime, can someone give me a link or tut on how to update HBOOT? I'm currently on 2.11.0000 OCT 6, 2011 and cannot seem to find the new version. Thank you so much for putting up with me guys, means a lot! Sorry for the people I offended with my lack of knowledge! Forums are new to me, looks like I got some brushing up to do!
werdna87 said:
bad logic to go by, some things brick if you run twice, AKA Froyo radio on the Inc
Click to expand...
Click to collapse
Umm, if you check, the new leaked firmware usually needs to run twice. Once for the bootloader and once for basically everything else. If you are running things twice and getting bricks, you are doing something wrong.
---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------
T Greezy said:
Hey guys! Just updated to the new version of Amon Ra. I am currently waiting for the new RUU to download. In the meantime, can someone give me a link or tut on how to update HBOOT? I'm currently on 2.11.0000 OCT 6, 2011 and cannot seem to find the new version. Thank you so much for putting up with me guys, means a lot! Sorry for the people I offended with my lack of knowledge! Forums are new to me, looks like I got some brushing up to do!
Click to expand...
Click to collapse
When you run the RUU, it will update your hboot to 2.21 in the process.
Ok, I'll keep you guys updated! I'll give it a go!
T Greezy said:
Hey guys! Just updated to the new version of Amon Ra. I am currently waiting for the new RUU to download. In the meantime, can someone give me a link or tut on how to update HBOOT? I'm currently on 2.11.0000 OCT 6, 2011 and cannot seem to find the new version. Thank you so much for putting up with me guys, means a lot! Sorry for the people I offended with my lack of knowledge! Forums are new to me, looks like I got some brushing up to do!
Click to expand...
Click to collapse
Just want to make sure you have the process down before.you start...
Once the RUU is downloaded, you will lock the boot loader, put the renamed ruu on your SD, run the RUU from the boot loader (don't try to flash it like a rom). You will then have to unlock and reflash that new among ra.
Then rock out. Just follow that step.by step closely for the RUU. Its kind of a weird process.
a-jive said:
Just want to make sure you have the process down before.you start...
Once the RUU is downloaded, you will lock the boot loader, put the renamed ruu on your SD, run the RUU from the boot loader (don't try to flash it like a rom). You will then have to unlock and reflash that new among ra.
Then rock out. Just follow that step.by step closely for the RUU. Its kind of a weird process.
Click to expand...
Click to collapse
Ok, so go back to HTC Dev.com and just re-lock? Or is there a tool I should use.
Besides that, I got a great feeling this is going to work!
Blah, it seems I have ran into a problem. The file for the new RUU I downloaded was corrupt. Anybody got a download link to the 3.11.605.22? Thanks.
I need a link to the new RUU. All the others are corrupt
T Greezy said:
I need a link to the new RUU. All the others are corrupt
Click to expand...
Click to collapse
Are you still stuck today?
Nope! Got my phone working as new! Updated and everything!
YOU GUYS ROCK, THANK YOU.
I had the exact same problem with my phone two days ago. You have to upgrade to the stock ICS first to update the RUU and junk, then re-flash Amon Ra, then install Cleanrom 4.0 or the dev version.
So im new to the Rezound but not to the rom and rooting world. I had made a N00b mistake by flashing ICS to my rezound without following the proper directions. Now I got myself in a situation that im hoping to get out of. When I try to boot it lets me get to my homescreen but then after 10's it restarts the phone. To top it off, I cannot mount my sd. It seems like the phone is getting worst by the minute. Is there a way out of this? Is there some sort of way to access my internal sd from my comp. Just at a clear loss of ideas. Please help.
supreme329 said:
So im new to the Rezound but not to the rom and rooting world. I had made a N00b mistake by flashing ICS to my rezound without following the proper directions. Now I got myself in a situation that im hoping to get out of. When I try to boot it lets me get to my homescreen but then after 10's it restarts the phone. To top it off, I cannot mount my sd. It seems like the phone is getting worst by the minute. Is there a way out of this? Is there some sort of way to access my internal sd from my comp. Just at a clear loss of ideas. Please help.
Click to expand...
Click to collapse
What did you flash? Was it the new RUU? If you can get to your homescreen then you are still not in bad shape.
The build from the android police leak. I never ran into these problems before. I had the Bionic for a while thought I would give HTC a whirl. My brain is at a stand still lol. I looked for hours and cannot find anything. I usually feel bad posting in a forum but hey im stuck.
supreme329 said:
The build from the android police leak. I never ran into these problems before. I had the Bionic for a while thought I would give HTC a whirl. My brain is at a stand still lol. I looked for hours and cannot find anything. I usually feel bad posting in a forum but hey im stuck.
Click to expand...
Click to collapse
I guess what I'm referring to is that you say you didn't follow directions. Which directions didn't you follow? The steps are pretty straight forward.
Reading back, I flashed it with the bootloader unlocked and I wasnt supposed to. Also I was supposed to chancg something in a file and i neglected to do as well. Just looking for some type of solution to bail me out.
supreme329 said:
Reading back, I flashed it with the bootloader unlocked and I wasnt supposed to. Also I was supposed to chancg something in a file and i neglected to do as well. Just looking for some type of solution to bail me out.
Click to expand...
Click to collapse
Flash the ruu then the Rom of your choice. All the instructions are in the ruu thread to lock, flash, unlock, recovery, etc. Then flash a Rom and not the AP one.
You also have the option to flash one of the ICS ROMe with the old firmware patch but I recommend the RUU path.
Not to thread hijack, but just out of curiosity, why don't you recommend using the patch? I know some people prefer to because it doesn't mark the bootloader as tampered, but are there some adverse effects?
bosox284 said:
Not to thread hijack, but just out of curiosity, why don't you recommend using the patch? I know some people prefer to because it doesn't mark the bootloader as tampered, but are there some adverse effects?
Click to expand...
Click to collapse
Just that the new firmware is more stable with the ROM and everything works as expected.
NilsP said:
Flash the ruu then the Rom of your choice. All the instructions are in the ruu thread to lock, flash, unlock, recovery, etc. Then flash a Rom and not the AP one.
You also have the option to flash one of the ICS ROMe with the old firmware patch but I recommend the RUU path.
Click to expand...
Click to collapse
Nils is right on this. You need to flash the RUU again. There are a lot of folks that needed to flash the RUU twice (myself included) to get everything to take.
It sound to me like you this happened to you. If you have the new RUU flashed properly, your phone will boot to the setup language preference screen.
If you had an incomplete/bad RUU update, you phone will boot to your last/current ROM with no SD or internal memory access. Nandroid backups won't restore properly either. Good luck, reflash the RUU with bootloader unlocked, allow system to reboot, flash a new recovery, and rock.
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
NoClemency said:
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
Click to expand...
Click to collapse
S-OFF is really the way to go if it's still an option for you it's the only way to get the new firmware without relocking and taking the OTA then unlocking and rooting again read post 2 in the lazypanda thread found here http://forum.xda-developers.com/showthread.php?t=1737123 just go down the list and verify everything works before running lazypanda there are plenty of members that subscribe to that thread so there is plenty of help availiable
Also, rerooting won't do anything. You're already rooted? Think the problem is in the rom u installed. Possibly a bad download. Try downloading from a good connection and install it again. If it is close to stock like flex's stock w goodies just clear cache and dalvik in recovery.
And what do u mean u tried a few recoveries? Cwm doesnt work well with the evo LTE. Try twrp 2.2 and leave it alone until its updated again.
What is your hboot? What rom did you try flashing?
Sent from my lair.
Im also getting this issue and i know its not anything to do with rooting and all that since ive been rooted since i picked this up from best buy on preorder release day and ive been flashing and running the same rom and mods forever now also i was using wifi yesterday soooo yea lol
Recognized Hooker Killer
First, I don't believe I can make my phone S-off, because it has software version 2.13.651.1 710Rd on it and even though I do have a nandroid back on 1.13 hboot, for the default rom from a long time ago with my old HTC EVO LTE, I can't flash back a hboot to 1.13 so I believe I'm stuck S-On for now. Let me know if I'm wrong.
I've attempted several different roms including fresh rom 5.1.1, viper4G_1.0.0, and a jelly bean rom (cm-cfX-20120904-OFFICIAL-jewel all with the same problem. As for recoverys, I should have said I've tried restoring back to several different nandroid backups that I created in the past that were working just find with my old HTC EVO LTE.
Right now my phone is unlocked and rooted. I am running H Boot-1.19.000, I am S-On, and Radio-1.12.11.0809.
I know this problem has something to do with flashing new roms, because when I do a nandroid back up to the default rom, I don't have this problem, and the wifi is working great, I only have this problem if I try to flash any custom rom or use a nandroid backup that I made with my old HTC EVO LTE.
Again, this is not my first time around the track with an HTC EVO LTE, this just happens to be a new phone that I recently got from Sprint when they were thinking my dropped calls were caused by my phone when in fact they figured out they had a tower down. Since then, the tower is back up, so that is why I just rooted this new phone they gave me.
Let me know if you have any suggestions or if you need anymore information.
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Please Help
NoClemency said:
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Click to expand...
Click to collapse
Hey im having the same exact issue I however went back to my stock backup from right after I rooted. The issue I had was I flashed a CMX nightly. I had been running them fine and suddenly everything went haywire i was bootlooping but only after about 30 seconds after the rom would load up. I'd have just under a minute to fish around and the it would reboot again. it was in this short window that I saw the wifi error and that it would not connect to the sprint network at all for voice or data. Im S-On Hboot 1.15 Evo LTE. I used Flash GUI to go from Stock sense to CMX as im sure youve figured out you have to do. Since i had backups of previous CMX nightlies I tried to just restore But none of my nandroids would fix the looping issue I managed to flash the boot img from the CMX rom i was previously on through adb/fastboot and it took but still my device kept looping. Finally i found this http://forum.xda-developers.com/showthread.php?t=1917106 but I didn't have any Sense Based Roms only my Stock Nandroid back up. So i used the Boot Image Flasher Tool, it took, then Instead of rebooting the system I went straight to my custom recovery and restored my Stock Sense BackUp since the tool flashes the stock sense kernel. To my relief the phone booted right up no problem connected to the network and all but to my dissmay the wifi is STILL broken somehow it says error and will not switch on. Everything else seems to be working fine though. This is crucial there is no way I can go without wifi on my phone. I don't want to ruin anything further or permanitely but i do plan to move forward. My plan is to download a sense rom (MeanRom) which im doing now but it's taking forever on 3G. Wipe everything (using TWRP 2.2) Data Dav rom and use super wipe, and try to install MeanRom. If anyone has any other suggestions Im all ears. Also im alittle confused on the Hboot kernel limitations I know I have to use Flash GUI if Im going from a sense Rom to Aosp and vise versa but do I have to use it when say Going to a nandroid backup of a sense rom while currently on a Aosp rom because I couldnt find a boot.img file in my backup file when i used the tool to extract it. I hate S-On HTC really screwed us with this. And I hate my original evo which had S-Off for dying on me on the 15th day and me having to get this replacement with 1.15 im sorry guys I love this phone but it has become a nightmare and the Evo 3D was no walk in the park either. I apprectiate any comment from anyone this is the first time in almost 8 years of hacking I've been truely worried I may not be able to fix something.
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
You also might want to try a different rom with its corresponding boot img. I'm currently running Venom rom with its boot img file and its working great. Right now, it sounds like your kernel is what is giving you problems like mine, so flashing the correct boot img should fix it.
vel7wil said:
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
Click to expand...
Click to collapse
Thank you I'll be sure to try this out quick update, in TWRP recovery I had (force MD5 check on all zips?) checked now I don't remember checking it or if it came checked by default but as soon as I unchecked it I was able to run superwipe and flash MeanRom which both failed multiple times when it was checked on. Not sure if this was the cause of my problem but I agree I think I got a bad kernel in the CMX nightly. Either that or the Flash GUI app didnt exract the boot image properly. Either way I haven't been brave enough to try another AOSP rom man I hate having S-On my first Evo was perfect then I get stuck with this locked down replacement. One question though is that boot image for a stock/sense rom just wanna be sure.
vel7wil's advice worked for me I was having the same issue. Download the zip he recommends. Use flash image gui to flash the kernel and clear dalvik and cache. I just did a standard reboot after that and it said "android updating... apps x of xx" then everything was back to working.
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Are you s-on then?
Did you RUU first? Might want to do that since you had made changes before. That will bring you back to nice and fresh stock.
The latest one is here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
IF YOU ARE S-ON... you can relock, RUU and then flash the recovery again and get root and see if that helps.
If you are s-off then await someone else's answer, but I think you run the RUU without relocking.
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
disdard said:
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
Click to expand...
Click to collapse
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
GetRipped said:
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
feralicious said:
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
Click to expand...
Click to collapse
Oh hai there.:angel:
disdard said:
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Click to expand...
Click to collapse
It sounds like you just need a new launcher. If you're getting to that point are you able to pull it down and see the notification area?
If yes then you could use Droid Explorer to push another launcher to the phone.
If not, yeah you maybe looking at starting over. Have you tried using a different recovery? I know personally I've had issues with every launcher except for Amon Ra.
I ran RUU, and once reset to stock breezed through the process of rerooting. Unfortunately had that done before any of the other replies, because it would have been easier to just do the resetting. But I got into the mess while trying to straighten out the issue of my dialer and people app disappearing so just fully going back to stock ensured I got the entire mission accomplished. And at the point it would boot to, you couldn't pull up the notification window so a new launcher wouldn't have fixed it.
Atleast I learned a bunch through the process!!! Just getting into rooting and customization, took the first step and rooted and kinda figured out how things work. Once I figure out a little more and decide which ROM I want to try, I'd like to try a custom ROM. All stuff I'm familiar doing with computers just gotta figure out exactly how it all works on phones....
Glad you are back up and running! Sorry if my method was more involved/time consuming.
I would suggest that before you flash a custom ROM you make a nandroid of your stock set up. Then you can always flash back to that if you don't like the ROM or run into issues and avoid troubleshooting or RUUing just to fix something.
It's a good safety net and a good habit to always have a nandroid to go back to in case of issues. I usually keep one handy of stock and of any ROMs I like, and always make one before flashing a new ROM or even a theme for a ROM.