Cant get into recovery (please help)

[sschreibeis]

Since these pg05img files arent working I think you will need to reflash recovery thru hboot, I will find you the img when I sit down at a computer in a few min. Not sure why the root enabled RUU file that cyber warrior supplied ya with did not work, tho.
On second thought you won't have time before the reboot starts. There will have to be a way to solve this in the bootloader I guess.
Do you have another SD card you can trywith the mr1 RUU?

Just so you know... the MR1 RUU (pg05img.zip) that I had you flash in hboot is the first file out of the two that you need to flash to unroot the phone back to stock. I saw that someone posted this link for you: [HOWTO] Restore to stock for root users and non-root users UPDATED 5/17/2011 - xda-developers
What I gave you is the first part of that procedure (brings you back to stock) the second zip unroots you back to s-on.

I'm surprised the MR1 RUU didn't fix your phone.. good luck.. if I think of anything else I'll let you know but that should have wiped your phone clean. You were saying something about maybe having a corrupt file on the sd card. Can you delete everything off of the card (put it on your computer for now) and try the zip I gave you again.

Ok, well I ran the second part of it to unroot it. I beleive it is successfully unrooted (says s-on in hboot). I am now just going to try and take it back and just hope that it is enough to get a new one. I just got it on July 27th so it is still within the 14 days on returns.
Is there any other way they would be able to find out that I rooted? When you turn it on, it just bootloops. If you go into hboot is says s-on. Am I missing anything?

 

[zero neck]

Ok, well I ran the second part of it to unroot it. I beleive it is successfully unrooted (says s-on in hboot). I am now just going to try and take it back and just hope that it is enough to get a new one. I just got it on July 27th so it is still within the 14 days on returns.
Is there any other way they would be able to find out that I rooted? When you turn it on, it just bootloops. If you go into hboot is says s-on. Am I missing anything?

Sounds good - I don't think they will be able to tell it was once rooted, or fix it, for that matter. You should have a replacement in no time.

 

[sschreibeis]

Sounds good - I don't think they will be able to tell it was once rooted, or fix it, for that matter. You should have a replacement in no time.

Thanks for all your help with this. I am humbled by the time people are taking out of their lives to try and help a total stranger. I really appreciate it!

 

[Cyber Warrior]

Yea.. you're good to go.. there have been so many people returning this phone for new ones they won't even care. Just tell them the phone will not start up.

 

[fatboy97]

Interesting read... I never attempted, nor will I ever, unroot my phone... thanks go to Cyber Warrior and zero neck for jumping into to help.

 

[PapaSmurf6768]

Good job team! Hopefully Big Red will give you a replacement. Don't know if you want to even attempt rooting again though, I'd be pretty PO'd if this happened to me!

 

[zero neck]

sschreibeis, i think it's likely that that particular device had a hardware flaw of some sort. Considering that you just got a pretty thorough crash course in trouble shooting, i wouldn't necessarily avoid rooting the replacement tbolt they give ya. it's up to you, though, of course.

 

[sschreibeis]

Yea.. you're good to go.. there have been so many people returning this phone for new ones they won't even care. Just tell them the phone will not start up.

Interesting read... I never attempted, nor will I ever, unroot my phone... thanks go to Cyber Warrior and zero neck for jumping into to help.

Good job team! Hopefully Big Red will give you a replacement. Don't know if you want to even attempt rooting again though, I'd be pretty PO'd if this happened to me!

Thanks everyone for your help. I will let you know later today how it went (tonight sometime). I don't want to sound like a broken record but...I do really appreciate your help in this.

 

[sschreibeis]

sschreibeis, i think it's likely that that particular device had a hardware flaw of some sort. Considering that you just got a pretty thorough crash course in trouble shooting, i wouldn't necessarily avoid rooting the replacement tbolt they give ya. it's up to you, though, of course.

I was wondering the same thing. I really did follow all the steps exactly. I also have learned a ton and will most likely still be rooting for the tethering. Don't think I will be flashing ROMs for a while though. I am really confident with everything now, but I am still pretty sore from all of this.

 

[zero neck]

I was wondering the same thing. I really did follow all the steps exactly. I also have learned a ton and will most likely still be rooting for the tethering. Don't think I will be flashing ROMs for a while though. I am really confident with everything now, but I am still pretty sore from all of this.

if you use just rooted stock you run the risk of receiving the verizon ota update, which could make you lose root or possibly cause worse problems than that. it's a good idea to update your radio and flash a rom of some sort, even if it is just basically a debloated stock rom, after you've rooted, if only to just avoid OTA complications.

 

[ssethv]

I just read this WHOLE thread and I am stumped I have never heard of this.... BUT i will say this... ever since the newest update of ROMmanager, there has been alot of different issues, not sure if they are related to this but just an fyi...

GOOD LUCK and keep us posted

 

[sschreibeis]

if you use just rooted stock you run the risk of receiving the verizon ota update, which could make you lose root or possibly cause worse problems than that. it's a good idea to update your radio and flash a rom of some sort, even if it is just basically a debloated stock rom, after you've rooted, if only to just avoid OTA complications.

Thanks! See, I learned something new again. Do you have any suggestions. I think I would like to stick to just a debloated stock ROM. Do you have a suggestion on ROM with Kernal and Radio that I should go with (something safe).

 

[sschreibeis]

Well everyone, I now officially have a new Thunderbolt. Everything worked out. Thanks again for all your help. I am going to root again tonight and eventually flash a radio and ROM. Any suggestions on what I should put on there would be appreciated (ROM and Radio). I do kind of like the Stock setup that they have. I really don't need anything fancy.

 

[zero neck]

Thanks! See, I learned something new again. Do you have any suggestions. I think I would like to stick to just a debloated stock ROM. Do you have a suggestion on ROM with Kernal and Radio that I should go with (something safe).

this is the OTA update (MR2 official) rom, unchanged except for root enabled and with busybox basically:
[ROM] Official 1.70.605.0 MR2 OTA Deodexed Rooted Busybox Mirrors Added - xda-developers
and with this you would flash one of the MR2+ radios after you've rooted, probably beginning with the official mr2 radio bc they go hand in hand.
official mr2 radio:
http://dl.dropbox.com/u/25213603/1.70 PG05IMG.zip
the md5 for this radio can be found around somewhere. i listed it in a sticky in the roots forums, i will paste it in here later if i get a chance.

this rom+radio combo would be a good place to start, but if you're feeling adventurous there are lots of good roms for the thunderbolt. if you like sense, there are sense 3.0 roms with gingerbread that are pretty awesome, such as gingeritis 3d (themikmik.com), and if you like aosp (android open source project - straight android roms) there are several that are very popular - cm7, liquid thunderbread, etc. ssethv is hyping up droidth3ory's latest ao5p rom - forget the whole title of it...

anyway, that should get ya started. glad it all worked out in the end, i think the tbolt you had before was just flawed and the issue wasnt really user related, seems more like a hardware problem to me, but i'm not really an expert so who knows.