• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Boot-looping and I don't know what to do!

Oh wait... just noticed the part about root checker. If you have a bootable,working phone why not just keep using it?
 
Oh wait... just noticed the part about root checker. If you have a bootable,working phone why not just keep using it?
I would love to keep it but the volume down button has recently quit working. I will attempt getting it back to S on tonight. And again, Thanks for all the help guys, I couldn't have done it without you.
 
And you can't live without a working volume down? WTF :p just playing around.

I think you could follow the directions here they are in the OP I would say second half but then I realized they aren't the second half so from about 2/5 to 7/8 in the OP
 
Aah gotcha. Glad we could help.

I find quite interesting that twice now a .exe file has fixed what appeared to be an emmc failure brick. :eek:

Thanks for reporting back. :)
 
And you can't live without a working volume down? WTF :p just playing around.

I think you could follow the directions here they are in the OP I would say second half but then I realized they aren't the second half so from about 2/5 to 7/8 in the OP

Lmao! I'm already worried that the volume up will break next and I won't be able to load roms or even get it back to stock when it does lol. Other than that, this phone has really been great and I haven't had problems like a lot of others have had in the past. Will let you know when I get it back to stock.
 
Aah gotcha. Glad we could help.

I find quite interesting that twice now a .exe file has fixed what appeared to be an emmc failure brick. :eek:

Thanks for reporting back. :)


Kinda makes you wonder how many bootloops of death were legit failures.

Wonder if my first phone could've been saved?
 
Kinda makes you wonder how many bootloops of death were legit failures.

Wonder if my first phone could've been saved?

my thots exactly. it may have been saved... it it may have had something permantly destroyed by running the PG05IMG file first. or maybe not.

i cant imagine what running the RUU does that running a PG05IMG doesnt. :confused: you can extract rom.zip from a running RUU and it looks for all the world exactly the same,and will even flash in hboot if renamed PG05IMG. maybe there is something slightly different about the image files?

sadly we prolly will never know for sure. but whenever i see looping in recovery,ill defiantely reccomend the .exe files!
 
Just double checking here... I ran the [ROM]RUU_Mecha_S_VERIZON_WWE_1.70.605.0_Radio_0.01.69.0 625r_NV_8K_1.41_9K_1.64 - xda-developers and got the phone bootable again and back to stock unrooted rom with S-off. So now in order to get the S-on, I have to place the PG05IMG_hboot_only_1.04.0000 on my sd card and rename it to PG05IMG and flash in H-boot. Correct or not?

well,sort of ;)

just doing that wont do anythig for you,as the revolutionary hboot will block its install and remain afterward. youll have to follow the first part of the guide,and get the old,eng 1.04.2000 hboot back on the phone first. then you can flash hboot_only. since you have the 1.07.605.0 fimware on the phone now,you can skip the part about flashing no_hboot first :)

holler if you have any questions on the first part of that guide,as there is potential to brick your phone if you flash a bad file or wrong file for the bootloader.
 
well,sort of ;)

just doing that wont do anythig for you,as the revolutionary hboot will block its install and remain afterward. youll have to follow the first part of the guide,and get the old,eng 1.04.2000 hboot back on the phone first. then you can flash hboot_only. since you have the 1.07.605.0 fimware on the phone now,you can skip the part about flashing no_hboot first :)

holler if you have any questions on the first part of that guide,as there is potential to brick your phone if you flash a bad file or wrong file for the bootloader.

Ok, I'll give it a try
 
Way to go. Good luck with going into refirb hell ;) don't accept any device that isn't up to snuff make them send you new ones over and over until you get one that works 100%...may want to hold off on rooting the refirb until you have been able to put it to thru the paces
 
Way to go. Good luck with going into refirb hell ;) don't accept any device that isn't up to snuff make them send you new ones over and over until you get one that works 100%...may want to hold off on rooting the refirb until you have been able to put it to thru the paces

That's a great idea, will do:) And now that i'm unrooted, does that mean I have to take off my jacket, put my cigar out, and leave them on the table:D
 
I think you can keep them ;) you unrooted due to having to get a replacement phone not because it was too difficult for you to grasp or too much work

Edit

yup. but youll get them right back when you get your new phone :D well keep them safe for you :p
Perhaps I stand corrected, try to sneak out the back when scotty isn't looking ;)
 
welcome back :)

you are lucky- seems lots of folks,if they arent still on the first,are on like the 5th or 6th :eek:

glad the new one looks good :cool:
 
i believe,simply becasue vzw doesnt do many checks or inspections before sending them back out. there have been reports of refurbs coming with roms installed,and non-working hardware.

if the phone looks presentable,and powers on,its sent thru some very brief testing and goes right back out. there does not appear to be any sort of checklist that makes sure all hardware functions,and something that pushes the most current firmware. at least if there are these things,the folks that work in that devision are trying to get away with as little work as possible instead of thuroughly testing/refurbing :eek:
 
Back
Top Bottom