Related
Not...really sure what I did wrong, but I would love some help here. I wanted to install Kang with Cornerstone from the old Alpha .6. Booted into recovery, wipe data, wipe cache, flash, flash Gapps, boom. Works fine at first. After playing around with it, I decide I don't like how it tiles apps, so I switch to the latest kang build (2012 02 29), same thing. Wipe, flash aaaand...bootloop. I go back, attempt to flash again, perhaps foolishly, and it now restarts recovery when it gets about halfway through.
I then try to restore to the backup I had made a few hours prior, MD5 sum error. Note that I had about 5 gigs free at the time. I try an older backup I had, same thing. If its worth anything, the backup thinks it was made on march 1st, which hasn't happened yet where I am.
So now I'm completely locked out of android. Thankfully, I can at least boot back to WebOS, so its not completely fried. Is there something I can do here to fix this, or am without a paddle here? I'm thinking it might be fixed if I completely remove android and redo the whole process, but is there anything else I can do first?
Will reward help with e-hugs
Semianonymous said:
Not...really sure what I did wrong, but I would love some help here. I wanted to install Kang with Cornerstone from the old Alpha .6. Booted into recovery, wipe data, wipe cache, flash, flash Gapps, boom. Works fine at first. After playing around with it, I decide I don't like how it tiles apps, so I switch to the latest kang build (2012 02 29), same thing. Wipe, flash aaaand...bootloop. I go back, attempt to flash again, perhaps foolishly, and it now restarts recovery when it gets about halfway through.
I then try to restore to the backup I had made a few hours prior, MD5 sum error. Note that I had about 5 gigs free at the time. I try an older backup I had, same thing. If its worth anything, the backup thinks it was made on march 1st, which hasn't happened yet where I am.
So now I'm completely locked out of android. Thankfully, I can at least boot back to WebOS, so its not completely fried. Is there something I can do here to fix this, or am without a paddle here? I'm thinking it might be fixed if I completely remove android and redo the whole process, but is there anything else I can do first?
Will reward help with e-hugs
Click to expand...
Click to collapse
Did you use ACME uninstaller?
Your best bet is to wipe everything, and reinstall. Hell, while you're at it, if it were me I'd check for WebOS updates first.
It'll be fine after a complete reinstall, but I think that's not only your best option but just about your only one.
Unrelated, but FWIW:
For anyone who's ever said, "I wish I could just get rid of WebOS altogether, so I could have that extra space". This situation is why we don't want to even be able to do that.
This is my first time trying to ask help on the forums, considering i've never run across a issue of this magnitude with my HTC Evo 4g before. So please do try to help me out if its in the wrong thread, etc..
Anywho onto the problem
im not sure how to classify my problem
I have a htc evo 4g rooted, Via revolutionary method, im not sure if this plays a part in causing my htc evo 4g to reboot randomly every 1-5minutes.
This problem only comes up when i flash any other rom on my device. I first tried flashing Fresh Evo 4.3.3and after 1-5 minutes of use my phone goes into a reboot mode (when i attempt to download anything through market place, or heck i leave the phone idle).
I had also tried flashing the MikGinger - Re-Eng GB Sense (3/9/2012)
I did wipe data/factory reset
wipe cache partition
and also wipe dalvik cache 3x before each rom install.
This definitely didnt help what so ever. What my issue is, is that the stock rom (root enabled) android 2.3.3 functions perfectly fine but every other rom i attempt to flash works to the extent of 1-5 minutes idle or not. It forces a reboot. Oh and the kernel used on the android 2.3.3 rom is freedom-v0.8.5-UNIVERSAL-signed.zip Its the only kernel that runs stably on my htc evo 4g, enabling tethering, and full scale rooting, with semi stable functionality
Heres the current stock recovery menu version when i hold down Power and +volume
-Revolutionary-
SUPERSONIC EV2T2-3 Ship S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANE-ATMEL224_16ab
RADIO-2.15.00.05.02
Mar 8 2011, 17:02:15
i also have clockworkmod Recovery v5.0.2.2 installed.
*Notes*
I always make nandroid backups, and i keep multiple ones backed up on the pc and phone for just incase measures like this one.
Im unable to diagnose what exactly my phones malfunction is so anyone who can provide useful info on how to diagnose the problem please do give me some advice, as everything else i've tried so far has failed (flashing, unrooting, re-rooting revolutionary method).
I'd also appreciate any advice that doesn't point me towards unrooting again and returning my device (as this is the 2nd htc evo 4g i have gone through, and the sprint repair center techs are idiots as far as im concerned. Their replacement htc evo's come shipped out refurbed and updated hboot which is harder to root and the stories go on and on.)
Try switching to Amon Ra recovery. You can use the original version - latest version is 2.3, or use the Amon Ra style recovery, I believe that the latest version is 3.11. Flash one of those as PC36IMG.zip via hboot.
From there, wipe everything except the SD card and battery stats, then flash whichever rom you want. Don't flash a kernel, just let it boot up and sit for at least five minutes. Then flash whatever mods you want to flash.
Hopefully it's just that things aren't being wiped properly - CWM is known for this on the Evo. Wiping system and boot via Amon Ra will hopefully get you on the right track.
If not, Evos can have a reboot issue that requires a replacement. Unfortunately if it doesn't do it on the stock rom then reproducible the problem for Sprint may be difficult. Hopefully it won't come to that.
alright ill give it a go, i did a system restore, and rolled back my phone to android 2.3.3 I'll try doing amon recovery later on tomorrow or come sunday. I need my phone to be in a operable stat to function for work. I'll be sure to post my results though. In the mean time if you can post a link (i dont mean to be lazy) just im heading to bed now.
And yes it is hard to reproduce errors for sprint techs. They think all it requires is a simple factory reset, and then install the most up to date RUU and it fixes the problem. If anything it makes the problem worse, as this is what happened with my first htc evo 4g (from launch). Except it caused the phone into a hard core brick like state. it literally locked you out of every function but dialing 911.
Add in:
Forgot to mention i updated my
-Revolutionary-
SUPERSONIC EV2T2-3 Ship S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANE-ATMEL224_16ab
RADIO-2.15.00.05.02
Mar 8 2011, 17:02:15
to
-Revolutionary-
SUPERSONIC EV2T2-3 Ship S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANE-ATMEL224_16ab
RADIO-2.15.00.12.19
Mar 8 2011, 17:02:15
(Just the radio was updated, updating radio did more than enhance signal quality it also broke some system functions, and alleviated other issues like glitchy rebooting bugs).
Its notable that after re-installing a backup of my android 2.3.3 alot of things restored broken (Broken links, that a fix permissions wouldnt fix), so i did another
wipe data/factory reset
wipe cache partition
wipe dalvik cache
from within CWM. (Im still surprised i havent borked my RSA keys yet, from the 39 times i have attempted reflashing both fresh & mikginger{Regardless a new rsa key backup was made})
{Question, since i have 2 RSA key backups, one from my original HTC EVO 4g, can i use them on the new device, or flash it to another 3g/4g enabled hotspot considering it is a active and available key? Or will it only function on the htc Evo 4g it was binded with (MAC address wise?) I havent tested it yet, and i dont know if ill set off red-flags. Hence the question.}
Then restored the phone, i noticed alot of things changed, like suddenly a vast majority of quirky reboots disappeared (Overclocking cpu suddenly doesnt cause a forced reboot if overclock is left to long due to overheat, it instead stalls and then crashes sense, and functions again instead of rebooting) a very nice improvement.
I've almost reinstalled everything through titanium backup, but only certain programs, im trying the one by one install, method, and seeing if this will beable to be upgraded to fresh 4.3.3 because if it can, then ill be a happy camper. Till then, ill explore your option, and if it backfires ill continue testing out my new fresh install of android 2.3.3 (rooted), with ICQ removed, and 98% of the stock apps removed. See how far i can get on getting my phone to run like android 2.3.2 the most stable android os i have ever run
(I dont want to restore my android 2.3.2 backup though to buggy, the only qirk was the texting bug and dialer bug, if its possible to port over the 2.3.3 updates to the text bug, and dialer bug, please do tell me as attempting to install from 2.3.3 into 2.3.2 tends to make the system run into a endless boot on 2.3.2)
I'm getting ready to head to work, but I just wanted to let you know to NOT restore a wimax backup from one phone to another. Toss it, it has no use now.
Amon Ra is in the Evo Development section. If I have time later tonight at work I'll post the link, but for now I gotta run. I will check back in with you though.
plainjane said:
I'm getting ready to head to work, but I just wanted to let you know to NOT restore a wimax backup from one phone to another. Toss it, it has no use now.
Amon Ra is in the Evo Development section. If I have time later tonight at work I'll post the link, but for now I gotta run. I will check back in with you though.
Click to expand...
Click to collapse
Do you mean install this version of Amon Ra? Just to clarify Amon Ra and CWM have their own ways of making a full backup, and i cannot just restore a backup made with CWM via Amon Ra, or can i? Im new to using Amon Ra, as i never trusted it much (to worried it may cause more harm than good, as im more use to using CWM)
Edited:
Yep i tried Amon Ra, it didnt work. I tried reflashing Fresh 4.3.3 2x and it ended it the same 1-5minute idle or not before reboot failure, same with MikGinger - Re-Eng GB Sense (3/9/2012). Nothing works but the stock roms with SU added in. I tried with my android 2.3.3 backup, and android 2.3.2. It seems my phone is incapable of working on android 4.3.3 but it works on all previous builds. It makes no sense to me though why it is like this, anyone think they can explain as to whats going on exactly with my phone?
supernet2ec2 said:
Do you mean install this version of Amon Ra? Just to clarify Amon Ra and CWM have their own ways of making a full backup, and i cannot just restore a backup made with CWM via Amon Ra, or can i? Im new to using Amon Ra, as i never trusted it much (to worried it may cause more harm than good, as im more use to using CWM)
Edited:
Yep i tried Amon Ra, it didnt work. I tried reflashing Fresh 4.3.3 2x and it ended it the same 1-5minute idle or not before reboot failure, same with MikGinger - Re-Eng GB Sense (3/9/2012). Nothing works but the stock roms with SU added in. I tried with my android 2.3.3 backup, and android 2.3.2. It seems my phone is incapable of working on android 4.3.3 but it works on all previous builds. It makes no sense to me though why it is like this, anyone think they can explain as to whats going on exactly with my phone?
Click to expand...
Click to collapse
I think it might be that you needed to update your radio and that fixed some things, but also I notice that your HBOOT version is not the right version. that version is only used to downgrade so you can gain s-off. use the hboots in this thread http://forum.xda-developers.com/showthread.php?t=715485
try that and see if it works
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
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.
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 !