I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Are you s-on then?
Did you RUU first? Might want to do that since you had made changes before. That will bring you back to nice and fresh stock.
The latest one is here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
IF YOU ARE S-ON... you can relock, RUU and then flash the recovery again and get root and see if that helps.
If you are s-off then await someone else's answer, but I think you run the RUU without relocking.
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
disdard said:
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
Click to expand...
Click to collapse
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
GetRipped said:
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
feralicious said:
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
Click to expand...
Click to collapse
Oh hai there.:angel:
disdard said:
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Click to expand...
Click to collapse
It sounds like you just need a new launcher. If you're getting to that point are you able to pull it down and see the notification area?
If yes then you could use Droid Explorer to push another launcher to the phone.
If not, yeah you maybe looking at starting over. Have you tried using a different recovery? I know personally I've had issues with every launcher except for Amon Ra.
I ran RUU, and once reset to stock breezed through the process of rerooting. Unfortunately had that done before any of the other replies, because it would have been easier to just do the resetting. But I got into the mess while trying to straighten out the issue of my dialer and people app disappearing so just fully going back to stock ensured I got the entire mission accomplished. And at the point it would boot to, you couldn't pull up the notification window so a new launcher wouldn't have fixed it.
Atleast I learned a bunch through the process!!! Just getting into rooting and customization, took the first step and rooted and kinda figured out how things work. Once I figure out a little more and decide which ROM I want to try, I'd like to try a custom ROM. All stuff I'm familiar doing with computers just gotta figure out exactly how it all works on phones....
Glad you are back up and running! Sorry if my method was more involved/time consuming.
I would suggest that before you flash a custom ROM you make a nandroid of your stock set up. Then you can always flash back to that if you don't like the ROM or run into issues and avoid troubleshooting or RUUing just to fix something.
It's a good safety net and a good habit to always have a nandroid to go back to in case of issues. I usually keep one handy of stock and of any ROMs I like, and always make one before flashing a new ROM or even a theme for a ROM.
Related
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.
So im new to the Rezound but not to the rom and rooting world. I had made a N00b mistake by flashing ICS to my rezound without following the proper directions. Now I got myself in a situation that im hoping to get out of. When I try to boot it lets me get to my homescreen but then after 10's it restarts the phone. To top it off, I cannot mount my sd. It seems like the phone is getting worst by the minute. Is there a way out of this? Is there some sort of way to access my internal sd from my comp. Just at a clear loss of ideas. Please help.
supreme329 said:
So im new to the Rezound but not to the rom and rooting world. I had made a N00b mistake by flashing ICS to my rezound without following the proper directions. Now I got myself in a situation that im hoping to get out of. When I try to boot it lets me get to my homescreen but then after 10's it restarts the phone. To top it off, I cannot mount my sd. It seems like the phone is getting worst by the minute. Is there a way out of this? Is there some sort of way to access my internal sd from my comp. Just at a clear loss of ideas. Please help.
Click to expand...
Click to collapse
What did you flash? Was it the new RUU? If you can get to your homescreen then you are still not in bad shape.
The build from the android police leak. I never ran into these problems before. I had the Bionic for a while thought I would give HTC a whirl. My brain is at a stand still lol. I looked for hours and cannot find anything. I usually feel bad posting in a forum but hey im stuck.
supreme329 said:
The build from the android police leak. I never ran into these problems before. I had the Bionic for a while thought I would give HTC a whirl. My brain is at a stand still lol. I looked for hours and cannot find anything. I usually feel bad posting in a forum but hey im stuck.
Click to expand...
Click to collapse
I guess what I'm referring to is that you say you didn't follow directions. Which directions didn't you follow? The steps are pretty straight forward.
Reading back, I flashed it with the bootloader unlocked and I wasnt supposed to. Also I was supposed to chancg something in a file and i neglected to do as well. Just looking for some type of solution to bail me out.
supreme329 said:
Reading back, I flashed it with the bootloader unlocked and I wasnt supposed to. Also I was supposed to chancg something in a file and i neglected to do as well. Just looking for some type of solution to bail me out.
Click to expand...
Click to collapse
Flash the ruu then the Rom of your choice. All the instructions are in the ruu thread to lock, flash, unlock, recovery, etc. Then flash a Rom and not the AP one.
You also have the option to flash one of the ICS ROMe with the old firmware patch but I recommend the RUU path.
Not to thread hijack, but just out of curiosity, why don't you recommend using the patch? I know some people prefer to because it doesn't mark the bootloader as tampered, but are there some adverse effects?
bosox284 said:
Not to thread hijack, but just out of curiosity, why don't you recommend using the patch? I know some people prefer to because it doesn't mark the bootloader as tampered, but are there some adverse effects?
Click to expand...
Click to collapse
Just that the new firmware is more stable with the ROM and everything works as expected.
NilsP said:
Flash the ruu then the Rom of your choice. All the instructions are in the ruu thread to lock, flash, unlock, recovery, etc. Then flash a Rom and not the AP one.
You also have the option to flash one of the ICS ROMe with the old firmware patch but I recommend the RUU path.
Click to expand...
Click to collapse
Nils is right on this. You need to flash the RUU again. There are a lot of folks that needed to flash the RUU twice (myself included) to get everything to take.
It sound to me like you this happened to you. If you have the new RUU flashed properly, your phone will boot to the setup language preference screen.
If you had an incomplete/bad RUU update, you phone will boot to your last/current ROM with no SD or internal memory access. Nandroid backups won't restore properly either. Good luck, reflash the RUU with bootloader unlocked, allow system to reboot, flash a new recovery, and rock.
I've tried multiple, and I mean multiple ROMS. All of them will just randomly crash, even if I'm not doing anything! I recently had my friend help me fix my phone because CWM recovery messed up my phone and made it so I couldn't charge my batteries at all. That problem is over with and I have a new recovery (Amon RA). Everytime I flashed a ROM I immediately flashed PH98IMG.zip because I am S-ON. Every ROM I've installed said it was compatible with S-ON. My phone just resets itself at random no matter what ROM I am on. Should I go back to stock or something? I really need help, my phone is useless at the moment.
My current ROM is CleanROM Professional Edition. This is also crashing.
Please reply someone, I need my phone to work ASAP :/
are you installing any apps or overclocking?
This happened to me as well when I was running on the leak prior to the last leak before the ota. Either way... Relock and RUU again with a fresh download. That fixed it for me. Also S-off really helps with this type of stuff because it makes it super easy to flash anything at any time including hboots. Just be careful about combos. S-off was actually the pain in the ass I thought it would be. Didn't go as smoothly as people described. BUT if u do your homework before attempting it u won't be stuck having to ask questions about what to do in the event something doesn't go perfectly. So to recap, easy for now, RUU with a fresh download the ota is prob Ur best bet. Or hard for now easy for later s-off.
Sent from my ADR6425LVW using xda app-developers app
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.
I've been searching all morning to find another thread to see if this has been answered before. I was trying to install a GSM Rom onto my Rezound. The install failed at around 2 %. I'm almost positive I thought I was on the correct ICS firmware, when apparently I wasn't. So instead of trying to fight installing the rom over and over again. I had a back up rom that I installed instead. My problem I think is that I didn't go back and re wipe everything after the failed install.
Which I could slap myself for, but my problem is this. The phone can go into Hboot, which gives me hope not all is lost. But I can't go into recovery or boot up. The phone will only load the white HTC screen then just reboots over and over again. I've seen where it tries to load recovery but then just reboots. I'm not sure if I have to reload the RUU or what I have to do. If anyone has had this problem or knows of a thread on how to fix it I would greatly appreciate it.
Edit: Just a little about my phone if it helps.
Vigor Pvt S-OFF RL
HBOOT - 2.25.0000
Radio - 1.22.10.0421r/1.22.10.0424r
OpenDSP- v13.6.0.7611.00.0104
eMMC-boot
Since you can't get to recovery it might be time to just put an RUU on you card and let hboot install it. Then you can install a recovery and then one of your backups.
Or just reinstall recovery
Sent from my Vivid 4G using Tapatalk 2
Ok, unfortunately I'm stuck at work and can't fix it right away. But I do thank you both for your help. I'll try the RUU first, since it needs to be done anyways. I was using Clockwork Mod Touch for my recovery before, is Amon Ra that much better ? I'll let you guys know the results soon as I can get it done.
stfumate said:
Ok, unfortunately I'm stuck at work and can't fix it right away. But I do thank you both for your help. I'll try the RUU first, since it needs to be done anyways. I was using Clockwork Mod Touch for my recovery before, is Amon Ra that much better ? I'll let you guys know the results soon as I can get it done.
Click to expand...
Click to collapse
I prefer CWM touch myself but the one from here not the official
stfumate said:
Ok, unfortunately I'm stuck at work and can't fix it right away. But I do thank you both for your help. I'll try the RUU first, since it needs to be done anyways. I was using Clockwork Mod Touch for my recovery before, is Amon Ra that much better ? I'll let you guys know the results soon as I can get it done.
Click to expand...
Click to collapse
If you plan to do a restore, stick to the same recovery.
Not sure how restoring over a previous rom borked your recovery though, that is weird.
mjones73 said:
If you plan to do a restore, stick to the same recovery.
Not sure how restoring over a previous rom borked your recovery though, that is weird.
Click to expand...
Click to collapse
Well I started off as I normally would, wiping data, wiping cache, wiping davlik, then installing. I tried one of the new JB roms Tron. But I couldn't get the GPS to work at all. So I stumbled across a GSM rom and went to install, it booted into it's own installation touch screen. I kept it simple not choosing many extras, then the last option was. Are you on ICS firmware? Which to my noobness, I've been running ICS roms since I acheived S-OFF. So I was pretty positive that I upgraded my firmware whenever I did that. So I chose Yes and it started to install, got to 2% and said it was done. Again I assumed the install had just failed and after having tried installing a GSM rom once before I had to go through and do it multiple times. I was tired and didn't feel like messing with it. So instead of rebooting, I went back into recovery and flashed another rom I had set on my SD card in case I didn't like the GSM. To which I think that my mistake came when I didn't either
A) Re-wipe my data, cache, davlik.
or
B) Restore my previous Rom from before.
So after the new rom installed and looked as everything went smooth. I selected reboot, the HTC white screen came up and the phone shut off. Then would power back up and display the HTC white screen and shut off again. So far the only thing I've been able to get it to do is the power cycle with the white screen and boot up in Hboot. But none of the options will work as the only thing it will do is power cycle. That's pretty much where I'm at until I can try reinstalling the RUU and flash the new(same) recovery.
The problem is nothing you've done there should have touched the recovery, that's why I find it weird.
I'd assume the rom asked which firmware you were on so it could installed the old firmware patch if needed.
Anyway, hopefully the RUU should straighten it out.
Well good news, re-installing the RUU fixed the phone. It re-locked my hboot, so I just finished unlocking that and re-flashing recovery. Thanks a bunch for all of your help. I greatly appreciate it !