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).
Related
Just updated the ruu found in the bamf remix 1.5 post and lost my root? Or seemed to.
First post because most the time I can find the answers through posts but this I can't seem to find.
I was previously rooted, flashed the new ruu via hboot and everything went smooth. Reboot, reinstall superuser and clockwork via marketplace, and superuser wouldn't take an auto update when it prompted me there was a new version out. Clockwork says I need root before it can do anything.
Few notes to consider :
- s-off is still there (least it says so in hboot)
- my first root I did was the longer way with Android sdk command line, no one click, no 400mb file
- dumb me is dumb, got excited about the new ruu and no nandroid backup
Now I'm chilling here, tried reboots, flash in hboot, and all I can do is sit here staring at my stick Rom like.... Herpa derp want root and bamf back
Help??? Please? Would rather not have to re root. As I won't have access to my computer for days.
-
Did you update to bamf 1.5, or someone posted the stock untouched ruu and you decided to flash that?
Download titanium back up and root, hit "problems?"
and install busybox.
Sometimes when I flash roms it will say i dont have root access, and go through titanium, hit problems, and keep installign busybox (ive had to do it up to 3 times)
and then it works for me
I used the ruu file that was posted in the bamf remix 1.5 thread in the first post right above the zip file for the actual Rom
And I didn't make it to installing bamf. Just finished with the ruu flash via hboot and was on my way to flash bamf when clockwork told me I didn't have root. This is when I went forum hunting about two hours ago :/
Samsuck said:
Download titanium back up and root, hit "problems?"
and install busybox.
Sometimes when I flash roms it will say i dont have root access, and go through titanium, hit problems, and keep installign busybox (ive had to do it up to 3 times)
and then it works for me
Click to expand...
Click to collapse
Wish I could say it worked for me... *sigh* guess I just really lost root then :/
So you didn't do any RUU, you flashed the radio. I flashed that radio before i flashed BAMF 1.5 and everything is working fine over here. Did you check MD5 sum to make sure that it downloaded correctly?
g00s3y said:
So you didn't do any RUU, you flashed the radio. I flashed that radio before i flashed BAMF 1.5 and everything is working fine over here. Did you check MD5 sum to make sure that it downloaded correctly?
Click to expand...
Click to collapse
Yeah. Little goofy on the terminology, fairly new to Android least. But yeah I always check any Rom or kernel or anything like that
I'm not sure, I don't understand how you can lose root just by flashing the radio, never heard of it happening before, sorry.
g00s3y said:
I'm not sure, I don't understand how you can lose root just by flashing the radio, never heard of it happening before, sorry.
Click to expand...
Click to collapse
No problem. I assume I did something wrong but I can't put a finger on it.
Ah well. I appreciate the help m8!
I'm gonna go out on the limb here and say that when you first rooted you never removed the zip file from you sd card and hboot pulled that image instead of the radio update.
afewgrams said:
I'm gonna go out on the limb here and say that when you first rooted you never removed the zip file from you sd card and hboot pulled that image instead of the radio update.
Click to expand...
Click to collapse
Possibly.... If I delete that. Download the new radio, and flash via hboot any ideas what would happen?
Edit... Yup that's what I did. I know... Im a genius swear I had moved that file and over written. Took a lot longer to flash that old file lol. Thanks!
Now just live with the stock sense UI and no root till I can redo that, /cringe
No Pants Hero said:
Possibly.... If I delete that. Download the new radio, and flash via hboot any ideas what would happen?
Edit... Yup that's what I did. I know... Im a genius swear I had moved that file and over written. Took a lot longer to flash that old file lol. Thanks!
Now just live with the stock sense UI and no root till I can redo that, /cringe
Click to expand...
Click to collapse
It's an honest mistake. I had the file on my sd for awhile before I found out. Glad I could help.
I did the same thing but I am stuck in Fastboot/HBoot. If I select reboot or power down in the Fastboot menu, I just come back to Fastboot. If I choose bootloader, I can't use the volume keys to select any of the menu options except the first one (Fastboot). After a few seconds it looks like it starts running the update process on PG05IMG but fails and says "Main version is older." Google/forum searches haven't shown me anything and I don't know where to go from here.
Similar problem
Hi, and thanks for bearing with a noob.
I have a HTC desire, rooted using unrevoked 3. I and I have tried a couple different ROMs successfully and was able to use Titanium Backup and ROM manager successfully, but after flashing cyanogen 7, I want to start using Titanium Backup, but it tells me could not aquire root priv., I went to the problems tab and it tells me make sure im rooted. did I lose root? the only choices it gives me from there is 'prefrences' and 'upgrade superuser' when i upgrade su. I did that to no avail.
also going into ROM manager it tells me ; superuser was not found.
anyway, i have been trying to search for the answer to this for a few days and have tried a couple things. my question is basically, did I lose root and need to unroot and reroot? or is there a way to enable superuser?
Thanks for any help
Have had my T-Bolt for about a month now and just rooted it yesterday! Loving it even more now! I decided to root because I was one of the lucky people that got the update a couple weeks ago and have been having random reboots ever since. I was hoping a different ROM might help with that.
I came from a D1 that I had rooted about a month after it first came out, so I know the basics of using Clockwork.
I put Das BAMF 1.6.3 on yesterday and it seems to be working good. Problem I am having is that I am still getting some random reboots. Not sure if it has to do with the radio installed on the phone or something with the kernal?
It isn't happening all the time. I noticed one last night and one this morning. Suggestions?
Which kernel & radio are you using?
I had the same problem had to switch to a different kernal. It was getting a little to warm causing the phone to reboot. Most noticeably when I used the navigation.
Sorry it took a while for me to respond. Been pretty busy.
After the reboot yesterday, I put a new kernel on there cause I say someone tried that when they got reboots and it fixed the problem.
Here is what I put on, the lean kernel, extremely undervolted - http://forum.xda-developers.com/showthread.php?t=1021404
It seems to be running good. No reboots since I put it on. But then this afternoon I got one. I wasn't doing anything crazy on my phone but it just rebooted out of nowhere. I was on 3G if that matters...???
BUMP
Had one random reboot today. Can't figure out what is doing it. This time I was in the middle of typing a text while on WiFi.
If you are using extremely undervolted try switching to normal. The extremely undervolted setting is also overclocked and may not get enough juice to run properly. see if running normal for a while also has you rebooting.
schmaltzy said:
BUMP
Had one random reboot today. Can't figure out what is doing it. This time I was in the middle of typing a text while on WiFi.
Click to expand...
Click to collapse
I like the BAMF Tom's, but the CM7 alpha for the Tbolt is stable and awesome... no wireless tether yet, but I'm sure it is on the way!
Sent from my ThunderBolt using XDA Premium App
I had random reboot problems after I flashed to the new radio. I switched back to the original radio and have not had a problem at all with bamf 1.6.3 or 1.7.
Sent from my ADR6400L using XDA App
I put the .7cdma and .6lte on and it solved my reboots. Before that I got random reboots and even a couple times where it just shut off. There is a radio thread in the dev section with all the combinations. Been on this radio for weeks and no reboots.
1.6.3 and 1.7bamf not o/c
OK.....need a little help with flashing a new radio....
See, I came form the origional Droid, which was super easy when switching ROMS. Download the ROM you want, throw the zip on the SD, boot into recovery, flash your ROM, good to go!
Seems a little more complicated with the Thunderbolt, so I'm still getting a little use to it.
I went to the post that has all the different radios, but I'm still not exactly sure on how to flash one. Can anyone explain???
schmaltzy said:
OK.....need a little help with flashing a new radio....
See, I came form the origional Droid, which was super easy when switching ROMS. Download the ROM you want, throw the zip on the SD, boot into recovery, flash your ROM, good to go!
Seems a little more complicated with the Thunderbolt, so I'm still getting a little use to it.
I went to the post that has all the different radios, but I'm still not exactly sure on how to flash one. Can anyone explain???
Click to expand...
Click to collapse
Pretty easy actually. Just download the image that you want to use. Make sure it is at the root of your sd card. Boot your phone into Hboot and it will try and load the file automatically at that point.
Tell the phone it's ok to install. Once you have it installed, don't forget to delete the image file from your root or at least rename it. Otherwise if you go back into hboot, it's going to try and install the image again.
Hope that helps.
Dnakaman said:
Pretty easy actually. Just download the image that you want to use. Make sure it is at the root of your sd card. Boot your phone into Hboot and it will try and load the file automatically at that point.
Tell the phone it's ok to install. Once you have it installed, don't forget to delete the image file from your root or at least rename it. Otherwise if you go back into hboot, it's going to try and install the image again.
Hope that helps.
Click to expand...
Click to collapse
How do you get into Hboot?
I'm running Das BAMF 1.7 Remix and I get a "bootloader" option under the restart. Is that the same thing??
Couple of ways.
If your rom supports it. You can hold the power button down and pick restart and then pick bootloader.
or if your phone is powered down, just hold the volume down key while holding down the power key and that should get you to the bootloader.
Edit: Make sure that your image is named PG05IMG at the root of your sd card.
It's the LTE radio causing reboots, so from http://forum.xda-developers.com/showthread.php?t=1045081 select either the second or fourth option. Any combo that has the 1.12.605.6 LTE radio. Also don't forget to rename it PG05img.zip and put it on the root of your sd card.
If your in hboot and it doesn't recognize the file, make sure it's not named PG05img.zip.zip, changing the name in windows will cause that to happen.
DixonToofar said:
It's the LTE radio causing reboots, so from http://forum.xda-developers.com/showthread.php?t=1045081 select either the second or fourth option. Any combo that has the 1.12.605.6 LTE radio. Also don't forget to rename it PG05img.zip and put it on the root of your sd card.
If your in hboot and it doesn't recognize the file, make sure it's not named PG05img.zip.zip, changing the name in windows will cause that to happen.
Click to expand...
Click to collapse
Thanks Dixon.
I was one of the lucky few that was getting quite a few reboots before I was rooted when Verizon sent out the update. Is it the LTE radio the cause for sure? I know there was a lot of speculation on what was the actual cause, but then I rooted so I stopped following the problem.
Does it matter that I have my LTE turned off all the time? I don't live in an LTE area so I never have it on, yet I still get 1 or 2 random reboots a day. Still better than the 6-8 I was getting when I wasn't rooted!
schmaltzy said:
Thanks Dixon.
I was one of the lucky few that was getting quite a few reboots before I was rooted when Verizon sent out the update. Is it the LTE radio the cause for sure? I know there was a lot of speculation on what was the actual cause, but then I rooted so I stopped following the problem.
Does it matter that I have my LTE turned off all the time? I don't live in an LTE area so I never have it on, yet I still get 1 or 2 random reboots a day. Still better than the 6-8 I was getting when I wasn't rooted!
Click to expand...
Click to collapse
I don't know if anyone can say for certain, but many people(Myself included) experienced reboots after switching to the updated .7 radios. After switching back to the .6 LTE radio, I haven't had a single reboot in weeks, and many others have had the same results. Whether it is the cause or not, switching seems to solve the problem. If it doesn't, then chances are something else is causing them on your phone, but you won't know until you try.
I usually have LTE turned off as well, and I know at least a couple of my reboots happened while it was turned off. Whatever the cause, it doesn't seem to be related to the use of the radio. Just having the .7 version loaded seems to be enough.
Should I make a Nandroid backup before I flash a new radio? Or would that not back anything up as far as the radio goes?
schmaltzy said:
Should I make a Nandroid backup before I flash a new radio? Or would that not back anything up as far as the radio goes?
Click to expand...
Click to collapse
I would always make sure you have a recent Nandroid backup before flashing anything. It won't back up the radio itself, but you never know what else could go wrong.
OK, last question....hopefully!!
There was just a new radio that was released. Looks like it is a new Gingerbread radio. Now I'm thinking about just throwing a gingerbread ROM and do everything once.
Question is....if I switch from a Froyo ROM to a GB ROM, in what order do I flash the ROM/Radio??
1) Backup, Wipe data/cache, flash ROM, boot into HBOOT, then flash the new radio?
or
2) Backup, boot into HBOOT, flash new radio, boot into recovery, wipe, flash ROM?
Doesn't matter. Some will tell you one way, others will tell you the other way.
From what I can tell, either way works. I've done both with the new radio and have had no issues either way.
Happy Flashing!
Ok, I have watched this video on YouTube (How to root the HTC thunderbolt, setting up ADB-step 1 & How to root the HTC thunderbolt- version 2.5) and followed these instruction http://www.androidpolice.com/2011/0...otloader/#rooting-the-thunderbolt-version-2-5
and I think I'm going to give it a try. Do you guys have any issues with those instructions or any advice?
Ok, I just finished and I am rooted. Now, what rom should I try first??? Do I update my radio to the MR2.5 and if so how?
thanks
Go to the development section and just scroll through the list, or search, and you'll find the leaked MR2.5 radio. Directions on how to flash should be in the thread, but if you don't find, just rename the radio as PG05IMG.zip and place it on the root of the sdcard (aka, not in any folders in the sdcard). Power off the phone, then power on in hboot by pressing the volume down and power button at the same time. The phone will look for the .zip file automatically and get the radio installed (it'll go through a series of checks so don't be alarmed).
Be aware that the MR2 and 2.5 radios only work on GB and SOME froyo roms. Just read the OP for each rom and see what radio they say to use and you shouldn't have problems. As for picking a rom, each person will tell you something different. Just check out the screenshots, read a little bit about each, and just try them out til you find the one you love
Good luck and congrats on rooting.
dbow32 said:
Ok, I just finished and I am rooted. Now, what rom should I try first??? Do I update my radio to the MR2.5 and if so how?
thanks
Click to expand...
Click to collapse
Step 1 would be read. A lot. There's some nice ROMs out there, but I've yet to try the perfect one so far. As for the radio, there's a lot of them out there and no ROM will play well with all of them. Some radios might even brick your phone. The MR2.5 only works with some gingerbread ROMs and one froyo ROM. MR2.0 works with most gingerbread ROMs, and the very latest RUU of froyo. The radio in RUU base 605.7 works with all ROMs I'm aware of up to the 605.7RUU. But, its not stable and will cause random restarts. All gingerbread ROMs are built on a very flawed alpha leak. If stability and reliability are qualities you value highly, avoid them. At this point, solid and reliable looks like the MR2 radio and a ROM based on the most recent froyo RUU. AOSP ROMs like cm7 are still in alpha builds at this point.
The radio is easy to flash. Just figure out which one you'll need for the ROM you want. Have any questions, just hit me up. I like to get my hands dirty with this stuff.
download the new mr2 radio found in the development section. then download das bamf 2.1 gingerRemix.
to do the radio, download and copy and rename it PG05IMG.ZIP (Make sure your computer isn't set to hide the .zip otherwise you will have a file named PG05IMG.zip.zip and it wont corrispond), then put it into your sd card. connect phone into disk drive and your sd folder will open. copy and paste into the root. at this time you can also download the 2.1 gingermix and copy that into your root also. now you need to hold down power button and select restart, then bootloader. it will open and ask if you wwant to update. press power button for yes, up and down volume button for up and down. select update and let it process. then reboot. radio shoulg be good to go. now for the remix gingerbread rom...open rom manager and select reboot into recovery. again use up and down volume and power button:
1Wipe Data/Factory Reset
2Mounts and partitions -> format system (probably unnecessary, but born of an abundance of caution)
3Advanced -> wipe dalvik cache (also probably unnecessary)
4Install zip from SD card -> select rom
5Reboot
(these are the steps I take and were given to me from the mentor I have who helps me when I stop breathing for hours cuz I think I have just bricked my phone. -dont want to take credit for his advice to me)
before doing a new rom, you always want to backup. and more often then not, you will want to do a full wipe of data and factory reset which is found from your Rom manager under the "reboot into recovery"
I'm sure if I missed a step in there someone will point it out, but I think I have it pretty much in line for ya. hopefully
before I rooted I was on the MR2.0 RUU and I had no problems or reboots. I really want a senseless (stock) ROM that is just bare bones. I'm reading through all the different ROMS but I just don't know which one to try. I'm afraid of doing the wrong one with the wrong radio. the one I'm considering right now is the DAS BAMF 1.7. What do you think about that one? Also, if and when the official OTA GB comes out, will I receive it?
I was on 1.7 until gingerbread came out. I love GB and won't be looking back anytime soon
i just tried to get the MR2.0 radio and the link is not working. any ideas?
Server might be busy. Do a Google search for the new mr2 radio and you should have a couple different options to download from.
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.
I installed the CLEANrom tapped edition rom after wiping everything as instructed. It boots and initially I had issues with wifi working, but that seems to be working after flashing a stock kernel. Now if I try to play anything with sound or change the volume using rockers or in the phone itself it forces a reboot.
Any ideas?
Thanks
You are probably on old firmware and need to flash the patch
http://www.myandroidfiles.com/Downloads/Rezound/3.14.605.5/GB%20Firmware%20Patch.zip
Sent from my Rezound
Still having issues
Thanks for the reply. I actually ended up flashing it back to the rom that I had. I also made sure I flashed it to the original recovery as well which is amon ra. The rom I flashed it back to was the clean rom standard 4.4.
Unfortunately, I'm having the same problem no. If I go into the dialer and hit a number it freezes and force reboots. If I hit the volume rocker, it freezes and force reboots. It just force reboots for almost everything except for texting and going into apps.
any thoughts? The 4.4 worked fine on the firmware that's on here, and I did do the wipe and reset before I installed back. Maybe I bricked it?
Definitely not bricked. You wouldn't be able to even boot if bricked. What firmware are you on?
Here is some information
CleanROM standard 4.4
htc sense version 3.6
android version 4.0.3
kernel 3.0.16
I think the hboot was 2.11 or something like that.
Yeah, I figured it's not totally bricked. It should be on ICS. The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Mr. Lando said:
CleanROM standard 4.4
htc sense version 3.6
android version 4.0.3
kernel 3.0.16
I think the hboot was 2.11 or something like that.
Yeah, I figured it's not totally bricked. It should be on ICS. The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Click to expand...
Click to collapse
Even though your on ics, it looks like your on gb firmware. Search for the gb patch for ics and flash in recovery and problem solved
2.11 hboot is gb firmware, 2.21 or up is ics firmware
Mr. Lando said:
The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Click to expand...
Click to collapse
It runs just great on the correct firmware lulz
Correct Process for Updating firmware
Hello,
You stated that 2.11 in the hboot indicates gb firmware. Do you know a link to the correct thread that would give me the appropriate process for updating the FW one that will work with the CLEANrom 1.4 dev version? I got the wifi working again after flashing the "old firmware patch" and then reloading CLEANrom 4.4 everything went back to normal. However, I hate sense and I would like something without it which is what the dev version provides, but if I cannot get wifi working then it's kind of useless. When I say "if I cannot get wifi working" what I am indicating is that when I try to run the cleanrom dev version 1.4 WIFI gets stuck on "turning on" but never turns on and eventually just says "error" with no further details. I searched through forum feeds and found a few forums that hinted on steps, but many people have seemed to be confused by this issue in the past and perhaps it is related to firmware as you said.
Thanks
i would wipe everything again, reflash the rom, and then immediately the patch. that should fix everything. key thing is flash the patch before booting the rom. ive flashed the patch after rebooting before and had things go haywire. not a promise that it will work, just letting you know what ive run into
Scosler has everything listed in the op for the rom, and all files are there as well. There's a bunch of different instructions for however your phone is set up.
Sent from my Rezound
Continuing...
Hi,
Not to sound like a total idiot here, and I probably do, but you had mentioned I should update the firmware so that hboot indicates 2.21 or higher. Is there an easy process for this or a thread I can turn to so that I can be sure it's updated. I believe I already did the step you mentioned.
I wiped/reset ----> flashed the 1.4 rom ----> ran the PH98IMG.zip----> then boot ----> then no PROFIT. wifi will not work. Maybe it's firmware after all. I don't know how I ended up on gb, I had a friend walk me through this the first time and I'm pretty technical. I used the automated tool by that one guy to flash the amonra recovery and I thought that was 2.21 or higher, but maybe I'm wrong.
If s on and on 2.11 hboot Method 4:
-Copy ROM to SD Card AND PH98IMG.zip AND GB Firmware Patch to ROOT of SD Card
-Reboot to recovery
-wipe data / Factory Reset
-Flash ROM
-Flash GB Fimrware Patch
-Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
-Reboot
-Profit!
Based on what you typed you didn't flash the firmware fix...
Mr. Lando said:
Hi,
Not to sound like a total idiot here, and I probably do, but you had mentioned I should update the firmware so that hboot indicates 2.21 or higher. Is there an easy process for this or a thread I can turn to so that I can be sure it's updated. I believe I already did the step you mentioned.
I wiped/reset ----> flashed the 1.4 rom ----> ran the PH98IMG.zip----> then boot ----> then no PROFIT. wifi will not work. Maybe it's firmware after all. I don't know how I ended up on gb, I had a friend walk me through this the first time and I'm pretty technical. I used the automated tool by that one guy to flash the amonra recovery and I thought that was 2.21 or higher, but maybe I'm wrong.
Click to expand...
Click to collapse
If i were you i would either s-off or flash one of the ics leak ruu's. that will help. there are many ways to solve your problem but those are your best bets
My issue is resolved. Thanks for all of your help and insight.
Sent from my ADR6425LVW using XDA
Care to share what you did? I am having exact same issue . . .
nvm - resolved: applied GB Patch right after ICS ROM flash (who would have known - I was kind of ignoring those GB patch instructions, since they did not apply to ICS).