Rebooting Das BAMF - Thunderbolt Q&A, Help & Troubleshooting

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!

Related

Can't Activate... please help

So I got a thunderbolt yesterday to replace my X2.
I activated the phone and then rooted it.
I downloaded InfuseTheory and installed it. Booted up and I got to the activation screen. After waiting for more than 20 mins and not getting anywere, I restarted and tried again but had no luck.
I've tried to flash a diff. radio but it wouldn't flash. Tried a diff rom but it's still not activating. Also tried 2 diff kernels and still nothing.
I'm not getting any bars, there's just an x right on the signal bars.
Can someone please help me, I had to reactive my X2, and it says I have 90 days 'till my sim expires.
Thanks
if you reactivated.your old droid.you gonna need a new sim but it sounds like the radio was wrong
Sent from my ADR6400L using XDA Premium App
The radio was working fine until I flashed a new rom and wiped data/cache.
I'm pretty sure it's a software issue.
Isn't there anything else I can do?
parter28 said:
The radio was working fine until I flashed a new rom and wiped data/cache.
I'm pretty sure it's a software issue.
Isn't there anything else I can do?
Click to expand...
Click to collapse
That's what he's saying. You flashed a MR2 rom without flashing the MR2 radio.
Then when you tried to flash a radio and it wouldn't flash to begin with, you probably tried to flash it in recovery. That's not correct. You name it PG05IMG.zip on the root of the sdcard and boot to hboot. Do a little more research
Ok thank you, now I kinda get it.
So what can I do fix the issue. I already have the radio, should I just boot into hboot and let it do its thing?
Would you please please help me or point me towards the right link?
http://forum.xda-developers.com/showthread.php?t=1154010
Either radio from this thread will work. I use the MR2 radio.
Like Absolute_Zero said, name it "PG05IMG.zip" and make sure it's on the root of the SD card. Boot into hboot (hold volume down with power button from full power off) and it will automatically prompt you to start an update. Select yes, let it do it's thing, and then you should be good to go.
If you already have the MR2 radio downloaded (I would reccomend the one labled official MR2) You need to rename it PG05IMG.zip (it is case sensitive and the 0 is a zero) and place it on the root of your sdcard. (not in any folders) Turn the phone off completely. Pull the battery to be sure. Then put the battery back in, press and hold the volume down button and the power button until you the see the hboot (bootloader) screen show up. If you have the PG05IMG.zip on your sd card it will automatically detect it and ask you to press volume up to start the update. Let it do its thing and then when it asks press power to reboot the phone.
IMPORTANT: after you are done, and boot up to confirm it worked by making sure you have a signal. Delete or rename the PG05IMG.zip on your sd card. It will only cause trouble if you leave it there and then need to access recovery from a bootloop or similar situation.
Sent from my HTC Thunderbolt
Ok guys I got it to work. Thanks for all the help, really appreciate it.
I had to go to the Verizon store and get a new LTE card, the guy reallly liked the sense 3.0 lockscreen on my rooted thunderbolt.

[Q] New ROM ... No Radio

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).

[Q] Stuck in boot cycle...not a wcdma problem

I Have restorted to being the noob that signs up to ask a question...The other day I was driving (pre-root) and I look down to notice my phone had power cycled on its own. I thought it would come back one, boy I was wrong....
It spiralled into endless boot cycle. It would at first reboot get to the 4g screen and then back to the htc...over and over. I was able to get into Hboot, and atempt to do a factory reset that didnt help because it became a endless reboot that way as well.
Now before any of you say "why dont you warranty replace the phone" Im a VZW agent, alas we dont have a warranty on our phones when it comes to our concessions lines...
Now, at that point I said enough is enough and I delved into the world of rooting. I self taught everything within a few hours. I had my phone unlocked and ready to go. I picked Ineffabile (http://forum.xda-developers.com/showthread.php?t=1420513) to use as a rom, I followed the procedure to a T it installed correctly, but then when it came back on everything seemed to work fine...for about 5 minutes and then it happened agian a power cycle all over again. and again...and again. It now comes on works for about 5mins and then reboots.
Im at a complete loss at this point I have gone back into the SD card and deleted the ph98 file etc.... I just dont know what to do. I need this phone to work.
Any help is appreciated Thank you so much!
I know you said it's not the wcdma problem but will your phone stay booted with the back cover off?
Else I'd ruu back to stock. Could try the different radios and see if it helps.
If you want to try the older radios and are on the OTA you'll have to hexedit you mainver. There's a guide if you look.
older radios? Im still new to this so I applogize...
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
Here's a couple guides to help you get familiar with rooting stuff:
http://androidforums.com/evo-3d-all-things-root/389787-beginners-guide-rooting-android-devices.html
http://androidforums.com/evo-4g-all-things-root/129648-quick-intro-rooting-those-new-rooting.html
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
feralicious said:
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
Click to expand...
Click to collapse
I dont have insurance =/ and cant get it either. Im trying to find the radios, and what kernal should I be flashing? because I cannot find the one that should match the rom im using.
What I dont understand is why the phone powers on, works for a few moments like nothing is wrong what so ever. Then freezes and reboots.
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
http://themikmik.com/showthread.php...-Beats-Tweaks-2-01-605-11&p=164906#post164906
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
feralicious said:
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
Click to expand...
Click to collapse
This is a clean SD card, and I didnt create a backup because I couldnt get the phone past Hboot when it was doing boot cycles previous to the root. I re-ruu'd right now. And im starting from scratch. I used clockwork before, Im trying amon ra now.

[Q] rezound boot loop/ *#*# not working

So i would like to apologize first off by saying i am a complete and total noob in every sense of the word. This is the first time trying to root any phone. ok so heres the deal, the phone powers up... FINALLY... and will load to the homescreen but reboots the device. I used the BAMF ICS rom and put in a PGIMGnewfirmwarepeople.zip... ive tried to do the *#*# but as soon as i bring it up i can only get maybe the * or at best the *# but then it reboots itself. I mess with cars on a daily basis but unlike a car part i cant bang or heat up the phone to get the desired result. i attempted to do this since i saw the video on the rezound redifined 4.0.3 ICS with nova launcher.. it was a video by driodzero?
i have no idea where to go from here... i would greatly appreciate any help anyone can provide
If it is indeed a network bootloop, try booting with the backpate removed. As long as the network signal isn't overly strong it should be able to get you in.
i think that was one of the things i did... i tried to let it boot with the back off, then with the back off and SIM card out... but to no avail. is there a way to somehow cmd prompt the *#*# in order to switch the problem... i dont know if this helps but it is S-ON
No SIM means no signal, which means no network bootloop. Must be another cause. Looking at the Bamf ICS thread, did you upgrade your firmware to ICS properly first. Hmm.
i will go back and look.. the problem is it will not let be go back and down grade img file...
twd420 said:
i will go back and look.. the problem is it will not let be go back and down grade img file...
Click to expand...
Click to collapse
Yeah, S-off is suggested eventually since it allows you to downgrade from the leaks. Risk of perma-brick in certain situations, like flashing a bad download of radios. But it helps more than hurts to have that freedom.
On S-on you also need to make sure the boot.img gets flashed seperate in the bootloader for a given ROM.
thanx i will try the wire trick to get it to S-OFF but right now i cant even get the phone to power up to the home screen
You can check the hboot/radio version in the bootloader to confirm firmware version. See what it says there.
Would attempt a clean reinstall of the ROM if it is indeed on ICS (hboot 2.21 or 2.25) firmware proper.
Then make sure to wipe system, davik-cache and cache, flash ROM twice, the patch Joelz has, and flash the boot.img as a PH98IMG.zip in bootloader. Then boot the ROM up.
i would definitely try that except i can not get it to power on, nor can i get it to charge... i think its bricked, since ive even gone to the standard battery as well as using different chargers. i greatly appreciate your insight
twd420 said:
i would definitely try that except i can not get it to power on, nor can i get it to charge... i think its bricked, since ive even gone to the standard battery as well as using different chargers. i greatly appreciate your insight
Click to expand...
Click to collapse
Did you use ClockworkMod by any chance? My first Rezzy charging capability fried on its own eventually, but aside from hardware failure: that recovery has been reported to have issues when battery drains down...

[Q] Wifi error after rooting and unlocking

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.

Categories

Resources