About a week ago my evo started randomly rebooting, and would continue rebooting until I hard reset. I nand restored and that would work for a little bit, but only a little bit. Eventually I managed to unroot my evo and took it to sprint. They seemed to fix it (not sure what they actually did, other than reflashing everything, I think by using an RUU, which I had already done) but as soon as I rooted my evo, the problem came back.
I like to think I'm not a noob, but I'm not a genius about this either. I tried several different ROMs and none worked. I'm back to an unrooted stock 2.1 evo and I haven't encountered any problems.
I've tried finding anything I could. I don't use the exchange something, that was what I read was causing most of the problems. I don't think the GPS bug was affecting me either. I dont think it's a faulty battery or anything along those lines, my evo never restarted in bootloader or a recovery.
Can anyone possibly help me out?
what recovery are you using? you may want to try amon since it does a better job with wiping / clearing the lint.
is this happening with all roms?
Yeah every ROM is doing it, including stock rooted ROMs. I've tried amon and clockword, neither fixed it.
MagicalSandwich said:
but as soon as I rooted my evo, the problem came back.
Click to expand...
Click to collapse
Did you followed the same guide for rooting before and after you got the phone fixed? if so, then that guide was wrong, or might be old, or you didn't followed the steps properly.
Find the best and most trusted guide to root for your evo. Ask and review,
Read as much replies as you can before you use that guide.
_________________________________________________
¤I slide with Syle¤
¤-MyTouch 3G Slide- HTC Espresso Sense¤
¤SlideMEROOT5 Rom¤
Well I could not get out the bootloader and bootloop after running the stock ruu.exe and updating several recovery images PC36img none of em work so I had to go to sprint to order a new one. I really want to come back to MYN ROm when I get my new Evo..But I do not want to brick it again. The only dilemma is I really do not have the total idea of what made my phone just crash force close android and start bootlooping.
I used the unrevoked one click root method and the unrevoked forever to nand unlock it. I was flashing several different kernels at first. When I saw still no improvement in battery life I went to start off flashing Fresh, then AVA then Myn. I had got a force close to with AVA rom and bootloop but i was able to get into recovery and to the splash screen. I wished I had pay attention to what kernel I flashed which was 24hrs before my phone crashed same thing happened when I flashed Myn's rom. However, I was getting crazy bootloops when I first used the battery tweak and after I saw the battery drain I tried a different kernel. At first i was wiping both cache in between but since so many kernels even the stock kernel was giving me a loop at the splash screen (where myn warm 2.2. would come up) I started wiping less just to finally get a kernel which would be stable. The last kernel I flashed I remember was netarchy 4.1.8 cfs fresh compatible around saturday 3pm and around 3am the phone just crashed android crashed and the worst bootloop started happening.
So can anyone give me some feedback please that has their device running smooth with this Rom and/or have had this issue before? Do you recommend unrevoked forever? Does anyone may think its due to flashing so many kernels?
Are you paying for the new phoneor is the warranty taking fare of it.
I'm new to to android scene, but it seems like you shot first and asked questions later... approach could have cost you a new phone.
Anyways have you given up on your old phone. I'm sure there's ways to fix.
What recovery version do you have?
Depending on what recovery you have, you should have usb access still, if so drop a another rom in there and flash via recovery.
Sent from my PC36100 using XDA App
you more then likely didnt actually brick that phone. i would wager if you had asked and tried a few more things that you could have gotten it to work. If the phone boots at all and goes to a boatloader or fastboot then it is 99.999% of the time not bricked and can be fixed.
for example (and you may have tried) the only PC36IMG that normally works most of the time is the original eng bootloader in toasts old root method. if you tried any others most have them dont seem to rewrite everything to get it working.
as far as what caused it there is no way of knowing with the information you provided. I have run the rom and it has been stable. I doubt it was flashing so much as myself and many others flash daily with out problems.
At a lost but luckily I did not have to pay for a new phone
omegasun18 said:
you more then likely didnt actually brick that phone. i would wager if you had asked and tried a few more things that you could have gotten it to work. If the phone boots at all and goes to a boatloader or fastboot then it is 99.999% of the time not bricked and can be fixed.
for example (and you may have tried) the only PC36IMG that normally works most of the time is the original eng bootloader in toasts old root method. if you tried any others most have them dont seem to rewrite everything to get it working.
as far as what caused it there is no way of knowing with the information you provided. I have run the rom and it has been stable. I doubt it was flashing so much as myself and many others flash daily with out problems.
Click to expand...
Click to collapse
I agree I do not think i bricked it but I have tried so many PC36IMG and different bootloaders I am now way more familiar with android and recovery than before lol. I saw your posts in another thread about a guy with the same issue flintr i think but the toast 2 eng still was not working however those were the first i was trying it may work now since I'm sure I was using a different hboot the 97 version then.
I am not sure if there is anyway its going to work now since even though it still says im Ship S-off I have tried running the stock ruu. I tried the fastboot and i flashed an older hboot to get my fastboot commands..so i ran the command fastboot flash recovery recovery-1.8ra. img but it still would not get into recovery i really do not have any idea what happened.
I really think somehow my kernel is affecting everything. I tried to flash a kernel through fastboot and i was getting error it could also be though i do not have the right format for my kernel file.
potna said:
Are you paying for the new phoneor is the warranty taking fare of it.
I'm new to to android scene, but it seems like you shot first and asked questions later... approach could have cost you a new phone.
Anyways have you given up on your old phone. I'm sure there's ways to fix.
What recovery version do you have?
Depending on what recovery you have, you should have usb access still, if so drop a another rom in there and flash via recovery.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I can't get into recovery..as soon as i select recovery it starts bootlooping.
I'm not paying for the new phone I went to a small sprint store so they just looked at it tried to clear data in bootloader and then ordered me a new phone.
Fair enough, sometimes a fresh start can be good. Good luck
Sent from my PC36100 using XDA App
Hey all
I've searched for an answer to my problem but have been able to find it. Anyway, I have tried about 8 different ROMS over the past month or so and Skyraider is easily my favorite. However, I had to remove due to the fact that whenever I would try to power down the device, it would reboot instead.
I've tried installing both manually and from ROM manager with the same outcome. I've cleared date & davlik and performed full wipes each time. My last hope was fixing permissions but that failed to correct the issue as well.
Again, I really enjoy using this ROM and do not relish the thought of not being able to use it. Does anyone have any thoughts on a possible fix?
patsfan1130 said:
Hey all
I've searched for an answer to my problem but have been able to find it. Anyway, I have tried about 8 different ROMS over the past month or so and Skyraider is easily my favorite. However, I had to remove due to the fact that whenever I would try to power down the device, it would reboot instead.
I've tried installing both manually and from ROM manager with the same outcome. I've cleared date & davlik and performed full wipes each time. My last hope was fixing permissions but that failed to correct the issue as well.
Again, I really enjoy using this ROM and do not relish the thought of not being able to use it. Does anyone have any thoughts on a possible fix?
Click to expand...
Click to collapse
You sure its Skyraider? That happened to me... Phone wouldnt shut off, if your in dark you can see the screen doesnt even shut down. With me though, it would shut off if plugged in.. Turned out the phone was damaged, a power surge damaged it. Got it replaced. If you flash another rom and it still wont shut down, then your gonna need a replacement.
Thanks for the response Mike. No, It does not happen with any other ROM I flash. Been bouncing between CM, Virtuous and uncommon for a week now and the power button works as it should.
I dunno, I realize I am a n00b with all of this but it simply doesnt make sense to me
Again, Thank you for the response
What radio are you using? A lot of people using 2.05 were having that issue and it went away when they upgraded to a 2.15 radio baseband.
No problem. But what you have going on is very odd, i wasnt aware that a ruu could do that. Try upgrading to the latest radio.
That's the baseband version correct? Sorry, I'm not too saavy with radios. Anyway..it says 2.15.00.07.28
patsfan1130 said:
That's the baseband version correct? Sorry, I'm not too saavy with radios. Anyway..it says 2.15.00.07.28
Click to expand...
Click to collapse
Yes, that's the baseband version and you should be good to go with the one you are using. The only other things I can come up with is to ensure you are S-OFF and running HBOOT 0.79 or higher.
Please forgive my ignorance here. I am definately S-off but I am unsure how to see what HBOOT I am running. I go into recovery but I dont see any version.
patsfan1130 said:
Please forgive my ignorance here. I am definately S-off but I am unsure how to see what HBOOT I am running. I go into recovery but I dont see any version.
Click to expand...
Click to collapse
Not a problem. This is how we learn. To find your HBOOT version power down then reboot into recovery. When you get to the white recovery screen look in the top left corner. The first line should state S-OFF and the second line should state your HBOOT version.
I was really hoping I would see it lower than 0.79 but it's 0.92. ah well..I suppose it's simply my phone doesn't play well with this ROM.
Thank you for the suggestions
I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.
patsfan1130 said:
I was really hoping I would see it lower than 0.79 but it's 0.92. ah well..I suppose it's simply my phone doesn't play well with this ROM.
Thank you for the suggestions
Click to expand...
Click to collapse
Well that's unfortunate. I read a couple of posts in the Skyraider thread that sounded as though a couple of people had the "recommended" setup (like you) but also had the reboot problem. Those posts seemed to get no response so I guess there was no fix found. Most of the discussion on this problem starts around post #2432 in the Skyraider thread if you want to do some more digging but I couldn't really find anything more.
Some other factors to consider:
When you first flashed the ROM did you wipe all data? (factory reset, wipe data cache, wipe dalvik cache).
If you flashed a custom kernel, try going back to the stock kernel.
What version of ClockworkModRecovery are you running? They released a buggy update a couple of weeks ago and it was pulled shortly after release so if you have a version higher than 2.5.0.5 then you should revert to an older version of CWM.
You could flash the 2.15.00.09.01 radio baseband but I don't think it would make a difference with this problem. Also, if you screw up or accidentally flash the same radio over itself then you will have a brick so use extreme caution if you decide to go that route.
That pretty much exhausts my knowledge on the subject so if everything is as it should be then you could always try wiping everything and flashing the ROM again.
RebelShadow said:
I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.
Click to expand...
Click to collapse
I didn't think of that but definitely a possibility. Good call.
Best of luck.
RebelShadow said:
I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.
Click to expand...
Click to collapse
Well wouldn't you know it! Problem solved
I did not know the add ons were not compatible
Thanks everyone!
I'm glad I was able to help...
Really though, good to hear you got it working. Enjoy.
Hello everyone,
I just want to say I did not make this thread prematurely. Iv had this current issue for over a month. Iv talked to various people on here and other related forums and tried everything others have suggested with nothing working, So I come here to hopefully, somehow, get an answer or a fix.
I've had my Evo since Feb, rooted almost immediately and have been trying different roms ever since. Yet I always found myself going back to CM. Well just recently, Iv run into a problem where ALMOST every rom I try to flash, it gets stuck at the white htc evo 4g screen, constantly rebooting over and over. I actually waited once for hours to see if it eventually would go into the rom but it didnt. Iv tried battery pulls, clearing cache and davlich, nothing works.
Here is what works with no issues that iv tried: Any CM, Miui, Mikfroyo, MikZ, Myns, MynsZ
WHat iv tried and does not work:Mikg, Virus, Kings, Leo, Alliance, Stock Gb,
Btw, I was originally using clockwork and was told to go to Amon Ra(latest version yes)-
Heres what exactly happens:
I download the rom, which Iv tried from my phone and my pc both. Put it on root of sd. reboot into recovery. Wipe: Cache,Davlick,Boot,System,Sd ext.,Data,Sd secure, All userdata/factory reset in that order and sometimes 2 and 3 times. I then flash the rom. The screen shows the progress of the installation of w/e rom it is, always says complete or successful. Reboot.
Almost immediately Shows the screen with the squigley colored lines then after a second or 2, phone vibrates, reboots right to white evo 4g screen. Sits on that screen for approx.10-15 seconds, vibrates goes black for 2-3 seconds and then back to the white evo 4g screen and it does this over and over til im forced to pull the battery. Very VERy frustrating.
I was told maybe the links of the downloads were bad so i tried multiple downloads of the same zip. I was told to check to see if the md5 sum thing matched, it did. I was told to download sd formatter, did that. I was told to update all the latest radios,prl,ext.
I do not know a whole lot about this but Im thinking that every Gb rom i try doesnt work. With the exception of 2 Aosp roms(cm and miui). I could be way off here but im just throwing that out there.
One thing I will mention. In the middle of trying to figure all this out, I deleted my sd card when trying to wipe. Now what is important is this issue was def. happening before I ever made this mistake. SO maybe its a moot point, I just want to mention everything.
Im hoping, praying that some of you MUCH more knowledgeable flashmatics can point me in the right direction because Iv been pulling my hair out for over a month trying everything I can read or was told to come to a conclusion as to why this would be happening.
Thank you for your time. Its much appreciated.
Try downloading and flashing a stock HTC kernel,then reflash the Rom you're trying to run .
Sent from my PC36100 using XDA App
BrianBusby2038 said:
Try downloading and flashing a stock HTC kernel,then reflash the Rom you're trying to run .
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You are the only response Iv gotten so i thank you.
Someone else mentioned this.
So I downloaded: Htc kernel #15
WHat I did was flash the rom(had been various ones) then flashed this kernel, rebooted, same result. Is this what you mean?
Have youve ever even heard of this? WHere every froyo rom iv tried works, 2 specific gb roms work(CM and miui) yet various other(gb) will not work.
Has anyone EVER heard of anything like this?
What hboot version?
Sent from my PC36100 using XDA Premium App
My suggestion is go completely stock. Unroot with a 3.70 RUU and then root your phone again. Start from scratch and then load up or attempt to load up one of the Sprint Lovers rom and see what happens. Maybe just maybe you had a bad root. I do recommend Amon as well though.
Or try this get Caulkins wipe all zip and format your phones harddrive and load up Sprint Lovers and see what happens
I would recommend flashing the kernel first before the ROM,however,since you can successfully flash froyo ROMS,playa may be right and you should try running the ruu and starting over.I was thinking the problem was an incompatibility between an ASOP ROM and a Sense kernel but doesn't hold water if you can get froyo based ROMS to boot up.
Sent from my PC36100 using XDA App
unvivid said:
What hboot version?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
not sure how do i find that out? I though if I updated all radios, ext. it included that. If im way off here sorry.
playya said:
My suggestion is go completely stock. Unroot with a 3.70 RUU and then root your phone again. Start from scratch and then load up or attempt to load up one of the Sprint Lovers rom and see what happens. Maybe just maybe you had a bad root. I do recommend Amon as well though.
Or try this get Caulkins wipe all zip and format your phones harddrive and load up Sprint Lovers and see what happens
Click to expand...
Click to collapse
Like I said I will try anything, so I will be trying to do this as soon as I have time. I may run into problems with how to do this, can you possibly point me in the direction or a how to? I mean I obviously would know how to flash a sprint lovers rom but im talking about the un-rooting step regarding 3.70 ruu??, Iv never did it and probably would be lost(noob).
htcevo4g03 said:
not sure how do i find that out? I though if I updated all radios, ext. it included that. If im way off here sorry.
Click to expand...
Click to collapse
Not a problem. Turn your phone off and hold the power button and the volume down button. This will take you to the bootloader screen. The hboot and radio versions should be at the top. I'm betting your hboot is .76
I had the same issue that you did and nothing worked, I was unable to flash any new GB Rom besides cm. I tried flashing stock, using multiple versions of clockwork and amon ra. Nothing worked, updating my hboot to the latest version fixed my issue, I'm guessing its something to do with the hboot version and hardware combination. You may lose fastboot commands, if you're unsure of what those commands are I doubt you'll miss them. And recent developments have allowed for downgrading of hboot. I'll dig the link up for the latest hboot.
Edit: http://forum.xda-developers.com/showthread.php?p=7027238
I personally flashed the 2.02 hboot for downgradability. I'd avoid 2.16 since it is so new and I've heard of issues after flashing. Anything prior to that should be fine.
Sent from my PC36100 using XDA Premium App
unvivid said:
Not a problem. Turn your phone off and hold the power button and the volume down button. This will take you to the bootloader screen. The hboot and radio versions should be at the top. I'm betting your hboot is .76
I had the same issue that you did and nothing worked, I was unable to flash any new GB Rom besides cm. I tried flashing stock, using multiple versions of clockwork and amon ra. Nothing worked, updating my hboot to the latest version fixed my issue, I'm guessing its something to do with the hboot version and hardware combination. You may lose fastboot commands, if you're unsure of what those commands are I doubt you'll miss them. And recent developments have allowed for downgrading of hboot. I'll dig the link up for the latest hboot.
Edit: http://forum.xda-developers.com/showthread.php?p=7027238
I personally flashed the 2.02 hboot for downgradability. I'd avoid 2.16 since it is so new and I've heard of issues after flashing. Anything prior to that should be fine.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
This.
I was having the same problem htcevo4g03 was having and I had hboot 0.76.2000. Here is what I did:
Made a nandroid backup
Using rom manager I downgraded to clockworkmod 2.5.0.7
Downloaded hboot 2.10.0001 under Evo Stock and Radios
Wiped data and cache (I don't know is this is necessary but probably not a bad idea)
Flashed hboot 2.10.0001
Downloaded and flashed fresh evo 4.2 (a rom that wouldn't flash before) via recovery and it worked!
unvivid said:
Not a problem. Turn your phone off and hold the power button and the volume down button. This will take you to the bootloader screen. The hboot and radio versions should be at the top. I'm betting your hboot is .76
I had the same issue that you did and nothing worked, I was unable to flash any new GB Rom besides cm. I tried flashing stock, using multiple versions of clockwork and amon ra. Nothing worked, updating my hboot to the latest version fixed my issue, I'm guessing its something to do with the hboot version and hardware combination. You may lose fastboot commands, if you're unsure of what those commands are I doubt you'll miss them. And recent developments have allowed for downgrading of hboot. I'll dig the link up for the latest hboot.
Edit: http://forum.xda-developers.com/showthread.php?p=7027238
I personally flashed the 2.02 hboot for downgradability. I'd avoid 2.16 since it is so new and I've heard of issues after flashing. Anything prior to that should be fine.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Hey Man,
I haven't tried anything yet but im going to this morning.
Looking at the bootloader screen, says:
Supersonic EVT2-3 SHIP S-OFF
HBOOT-2.10.001
MICROP-041f
RADIO-2.15.00.05.02
Ok so I should download anything prior to 2.16 and flash like a rom?
Thoughts after youve seen my version?
TeamGold said:
This.
I was having the same problem htcevo4g03 was having and I had hboot 0.76.2000. Here is what I did:
Made a nandroid backup
Using rom manager I downgraded to clockworkmod 2.5.0.7
Downloaded hboot 2.10.0001 under Evo Stock and Radios
Wiped data and cache (I don't know is this is necessary but probably not a bad idea)
Flashed hboot 2.10.0001
Downloaded and flashed fresh evo 4.2 (a rom that wouldn't flash before) via recovery and it worked!
Click to expand...
Click to collapse
looks like the hboot version youve downgraded too is the one Iv had
unvivid said:
Not a problem. Turn your phone off and hold the power button and the volume down button. This will take you to the bootloader screen. The hboot and radio versions should be at the top. I'm betting your hboot is .76
I had the same issue that you did and nothing worked, I was unable to flash any new GB Rom besides cm. I tried flashing stock, using multiple versions of clockwork and amon ra. Nothing worked, updating my hboot to the latest version fixed my issue, I'm guessing its something to do with the hboot version and hardware combination. You may lose fastboot commands, if you're unsure of what those commands are I doubt you'll miss them. And recent developments have allowed for downgrading of hboot. I'll dig the link up for the latest hboot.
Edit: http://forum.xda-developers.com/showthread.php?p=7027238
I personally flashed the 2.02 hboot for downgradability. I'd avoid 2.16 since it is so new and I've heard of issues after flashing. Anything prior to that should be fine.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I downloaded and flashed Hboot 2.02 from the evo stock and radios and then tried to flashed Virus and Synergy, but the same thing is happening.
Im going to try hboot 2.15 but it sure dont look good. This is UNREAL
Bump:
Anyone of you guys that replied earlier in the thread or Anyone else out there?
Any help would be very much appreciated!
Sent from my PC36100 using XDA App
Might sound weird, but have you tried reformatting the SD card?
tnEVo said:
Might sound weird, but have you tried reformatting the SD card?
Click to expand...
Click to collapse
hey the reply is much appreciated!
If you read my op, I mentioned someone told me to dl sd formatter on my pc which I went through the steps and it didnt work.
Hey man If you get a chance please read my op, this is prob going on a month and a half and no fix to this point. I would have though if I brought the issue here, it would be resolved like that but it hasnt. Iv tried everything ppl have thrown at me and not a thing has worked. Other than froyo roms and 2 gb roms(cm7/miui), cannot getting anything to work. Ill flash a rom, it always says successful I reboot, turns to the white screen and gets stuck, rebooting over and ove, always back to the white screen and Im forced with a battery pull to do anything else. AMAZING!
If you can just look over the OP maybe just maybe you might have something you think could work.
The very last thing i tried, in which 2 ppl said they were having the same issue, was to downgrade the Hboot. I did this and it didnt work. SO frustrating.
The one thing I did not try that was said to do was unroot, go back to stock, and root again.
SO lost here. Again thanks for contributing to this thread.
htcevo4g03 said:
hey the reply is much appreciated!
If you read my op, I mentioned someone told me to dl sd formatter on my pc which I went through the steps and it didnt work.
Hey man If you get a chance please read my op, this is prob going on a month and a half and no fix to this point. I would have though if I brought the issue here, it would be resolved like that but it hasnt. Iv tried everything ppl have thrown at me and not a thing has worked. Other than froyo roms and 2 gb roms(cm7/miui), cannot getting anything to work. Ill flash a rom, it always says successful I reboot, turns to the white screen and gets stuck, rebooting over and ove, always back to the white screen and Im forced with a battery pull to do anything else. AMAZING!
If you can just look over the OP maybe just maybe you might have something you think could work.
The very last thing i tried, in which 2 ppl said they were having the same issue, was to downgrade the Hboot. I did this and it didnt work. SO frustrating.
The one thing I did not try that was said to do was unroot, go back to stock, and root again.
SO lost here. Again thanks for contributing to this thread.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I would just go ahead a unroot,wipe the hell out of it then go a reroot the see what you get. With everything you have tried so far that maybe the thing you need,sorry I couldn't be more help.
Same situation here now
So.. i'm in basically the same situation.. with a wrinkle.
I just tried.. about 8 roms.. ALL of them get stuck on the white screen
Except.. CM 7.0.3.1.. that seems to install
Any thoughts on what the heck that could be?
Roms I tried:
miui
warm 2.2
calkins new one
kings 3d
fresh 4.2
I agree... unroot, run the s-on tool form unrevoked.
run the RUU for your phone
re-root
flash Amon Ra recovery and try a new ROM
Hey hip,
OK if I have to start from scratch I will. But since I'm a super noob, can you please be a little more specific on the steps I have to take? I don't know much about s-off and s-on tool and also what ruu is. If you can just point me in the right direction then I can follow the directions.
And ty for your time
Sent from my PC36100 using XDA App
Anyone know how to get s-on without recovery?
Long story short, loaded miui 10/14 with tiamat 4.1 sbc kernel last night. Everything fine.
Woke up this morning in an endless bootloop and it won't go away no matter what I do. Have the PC36IMG on the card, it asks to update, it does but no recovery. Just an endless bootloop.
Try to run ruu, 107 usb connection error.
Change batteries, still nothing, same bootloop.
Got a card reader, replaced the PC36IMG with a new one, same bootloop.
Format card, put PC36IMG back on the card, it updates per normal. Still nothing
Any thoughts would be appreciated otherwise I believe I have a fried phone
http://forum.xda-developers.com/showthread.php?t=1218386&highlight=how+to+root. You might wanna check out the files in the faq's in that thread. Im no droid expert just taking a shot in the dark. Hope you get your evo functioning again.
What radio version do you have?
Concordium said:
What radio version do you have?
Click to expand...
Click to collapse
Whatever the radio version that comes with the PC36IMG update for froyo, hboot version 2.10
Ran that update last night and everything updated. Then it stayed in the endless bootloop
Sent from my PC36100 using XDA App
andygu3 said:
Whatever the radio version that comes with the PC36IMG update for froyo, hboot version 2.10
Ran that update last night and everything updated. Then it stayed in the endless bootloop
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yeah it helps when you load HBoot and actually look at what radio version you have. Assuming things doesn't bode well for your phone when you start flashing things through HBoot.