So, decided to run lagfix earlier on my phone (usually not an issue). After it completed, it rebooted a few seconds later. No biggie I thought... However, now it keeps rebooting at the splash screen (before the boot animation).
I'm able to get into Bootloader and Recovery still.
I tried clearing my cache/dalvik, but when I clear my dalvik cache, it simply reboots and I have no idea why. Did lagfix mess up my partitions somehow?
I tried just reinstalling the kernel, but it still just reboots at splash.
Anybody have any ideas as to what I could try? ADB and Fastboot still recognize my device, so I don't think I've bricked it..
Current setup in sig. Running Amon-Ra 3.15. Thanks in advance, I appreciate it!
Edit: also reboots from recovery when I try to do a factory reset from recovery. I'm guessing my cache partition got messed up somehow?
Have you tried to RUU? If you cannot get recovery working, that may be your only option.
Before an RUU, try fastboot flashing a recovery image. TWRP or CWM.
Sent from my Infected Rezound using xda app-developers app
Uzephi said:
Have you tried to RUU? If you cannot get recovery working, that may be your only option.
Before an RUU, try fastboot flashing a recovery image. TWRP or CWM.
Sent from my Infected Rezound using xda app-developers app
Click to expand...
Click to collapse
Sorry, may not have been clear in my OP.
I am able to get into both bootloader and recovery.
No, I haven't tried to RUU (not exactly sure which one to download, either. Been out of the loop for that stuff for a while).
You said you get reboot if factory reset from recovery. Sounds like something messed up that partition. Fastboot flash a new recovery IMG to see if that fixes that issue, then you could try factory reset again and it may work.
As for RUU, there is no RUU out yet for the recent OTA. So you would need to use the previous RUU OTA so you can update to recent OTA. There is a thread explaining the OTA RUU somewhere in this forum.
Note: I only had this Rezound for a little under 2 Mos but have had HTC devices before, and going off that prior knowledge. most "unofficial" or "leaked" RUU will not update, from what I remember.
Sent from my Infected Rezound using xda app-developers app
Uzephi said:
You said you get reboot if factory reset from recovery. Sounds like something messed up that partition. Fastboot flash a new recovery IMG to see if that fixes that issue, then you could try factory reset again and it may work.
As for RUU, there is no RUU out yet for the recent OTA. So you would need to use the previous RUU OTA so you can update to recent OTA. There is a thread explaining the OTA RUU somewhere in this forum.
Note: I only had this Rezound for a little under 2 Mos but have had HTC devices before, and going off that prior knowledge. most "unofficial" or "leaked" RUU will not update, from what I remember.
Sent from my Infected Rezound using xda app-developers app
Click to expand...
Click to collapse
Nott sure if its an issue with the recovery or not.
Looks like it reboots out of Recovery if I try to manually wipe /data or dalvik (only ones I've tried so far).
Doesn't hurt to try the recovery option before RUU.
I do not know if Rezound RUU repartitions the memory, but my other HTC devices did when RUU. So if it is partition error, RUU is your best bet.
Sent from my Infected Rezound using xda app-developers app
Ok! Update that looks promising.
I no longer get reboots when wiping /data or dalvik. What I did to fix this was in Amon Ra recovery, it has an option to format /system, /data, and /cache to EXT4. They were already EXT4, but this menu also has an option to format to EXT3. I formatted all the partitions to EXT3, and then upgraded them all back to EXT4 right away. I went into the wipe menu, and was able to perform a factory reset as well as manually wipe all partitions I needed to!
Going to try restoring my nandroid backup now to see if it works or not.
Edit: Restore success! Had to go through setup again, but all my apps are still there. Just all my settings / data for apps got reset which is unfortunate, but not a huge deal. I have a backup from a couple weeks ago, which should be good enough.
Related
I bought an evo 3d from a guy today off craiglist and he gave it to me with MIUI loaded onto it. So I figured no problem I will just restore to factory and do what I want to do rooting wise from there. I did a factory restore but it is still running MIUI and I don't know how to get it uninstalled and back to factory. It is running HBOOT 1.50 so I tried to flash a new rom via fastboot-->recovery even though I know that wont leave the rom completely working right but I was just trying to get rid of this MIUI rom. It said it flashed correctly but nothing changed on reboot it is still running MIUI. He gave it to me with the HBOOT unlocked already. Is there anyone that can help me getting a different rom, preferrably one as close to sense as possible running on this thing? I never ran into problems like this with my EVO 4g. Thanks to all!
vtotheinay said:
I bought an evo 3d from a guy today off craiglist and he gave it to me with MIUI loaded onto it. So I figured no problem I will just restore to factory and do what I want to do rooting wise from there. I did a factory restore but it is still running MIUI and I don't know how to get it uninstalled and back to factory. It is running HBOOT 1.50 so I tried to flash a new rom via fastboot-->recovery even though I know that wont leave the rom completely working right but I was just trying to get rid of this MIUI rom. It said it flashed correctly but nothing changed on reboot it is still running MIUI. He gave it to me with the HBOOT unlocked already. Is there anyone that can help me getting a different rom, preferrably one as close to sense as possible running on this thing? I never ran into problems like this with my EVO 4g. Thanks to all!
Click to expand...
Click to collapse
If already unlocked, using fastboot to get into recovery and flashing from there should have worked.
I would fastboot oem lock the device. Then running an ruu to get to stock. Wipe the entire sd card. Then follow htc evo hacks guide to root/unlock. Hboot 1.5.
That will unlock it again and give you your recovery. (I would probably use twrp instead of cwm if I were you).
Once done with that go ahead and flash su and make your nand backup. Should be good to go after that.
Sent from my PG86100 using XDA App
vtotheinay said:
I bought an evo 3d from a guy today off craiglist and he gave it to me with MIUI loaded onto it. So I figured no problem I will just restore to factory and do what I want to do rooting wise from there. I did a factory restore but it is still running MIUI and I don't know how to get it uninstalled and back to factory. It is running HBOOT 1.50 so I tried to flash a new rom via fastboot-->recovery even though I know that wont leave the rom completely working right but I was just trying to get rid of this MIUI rom. It said it flashed correctly but nothing changed on reboot it is still running MIUI. He gave it to me with the HBOOT unlocked already. Is there anyone that can help me getting a different rom, preferrably one as close to sense as possible running on this thing? I never ran into problems like this with my EVO 4g. Thanks to all!
Click to expand...
Click to collapse
If you relock the device, run the RUU first, then fastboot oem lock. You should try the superwipe tool located in the development thread under InfectedROM Eternity, Then try flashing a ROM. There are a few ROMs that are pretty stock, including a basic sense ROM with very few alterations. Head over to development and check them out.
thos25 said:
If already unlocked, using fastboot to get into recovery and flashing from there should have worked.
I would fastboot oem lock the device. Then running an ruu to get to stock. Wipe the entire sd card. Then follow htc evo hacks guide to root/unlock. Hboot 1.5.
That will unlock it again and give you your recovery. (I would probably use twrp instead of cwm if I were you).
Once done with that go ahead and flash su and make your nand backup. Should be good to go after that.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I tried going to fastboot then recovery when I flashed the other rom but like I said it did nothing,. Its actually running TWRP recovery already, but I will try to relock and start over. Thanks guys.
vtotheinay said:
I tried going to fastboot then recovery when I flashed the other rom but like I said it did nothing,. Its actually running TWRP recovery already, but I will try to relock and start over. Thanks guys.
Click to expand...
Click to collapse
Did you do a full wipe?
Twolazyg said:
Did you do a full wipe?
Click to expand...
Click to collapse
yeah I did a factory reset by going through menu-->settings-->about phone-->factory reset and tried factory resetting through recovery mode but as soon as it boots it looks like it has been reset. Unfortunately after I do the touch android character to continue options (sign into google, etc) it just goes straight into miui rather than how a factory evo 3d should look which is running gingerbread. Its so frustrating.
vtotheinay said:
yeah I did a factory reset by going through menu-->settings-->about phone-->factory reset and tried factory resetting through recovery mode but as soon as it boots it looks like it has been reset. Unfortunately after I do the touch android character to continue options (sign into google, etc) it just goes straight into miui rather than how a factory evo 3d should look which is running gingerbread. Its so frustrating.
Click to expand...
Click to collapse
Doing a factory reset is not the same as wiping.
You need to do a full wipe from recovery. Boot into the bootloader by hooking your phone up to the pc, navigate to your adb and fastboot folder and type:
Code:
adb reboot bootloader
Then type:
Code:
fastboot boot recovery.img
Once in recovery flash the superwipe.zip I mentioned before, then flash a ROM.
Check out this thread for information on how to get fastboot and adb, where to put them, and everything else you need to know about flashing with 1.5.
Then, before you do anything with your phone, look here for the superwipe.zip
Twolazyg said:
Doing a factory reset is not the same as wiping.
You need to do a full wipe from recovery. Boot into the bootloader by hooking your phone up to the pc, navigate to your adb and fastboot folder and type:
Code:
adb reboot bootloader
Then type:
Code:
fastboot boot recovery.img
Once in recovery flash the superwipe.zip I mentioned before, then flash a ROM.
Check out this thread for information on how to get fastboot and adb, where to put them, and everything else you need to know about flashing with 1.5.
Then, before you do anything with your phone, look here for the superwipe.zip
Click to expand...
Click to collapse
OH ok I had no idea. Thanks for that. When I click your link and try to download the superwipe zip from the page, the download link just takes me back to the thread link. Do you have a link to DL the superwipe?
vtotheinay said:
OH ok I had no idea. Thanks for that. When I click your link and try to download the superwipe zip from the page, the download link just takes me back to the thread link. Do you have a link to DL the superwipe?
Click to expand...
Click to collapse
Here you go.
Twolazyg said:
Here you go.
Click to expand...
Click to collapse
thanks. im still having a problem cause the phone is running TWRP recovery and the bootloader is unlocked but he wiped the SD card so all the files that should be on it after the unlock and flash of the recovery are gone. Im having a huge problem trying to get this MIUI off the phone. I just want to get it back to running a stock rom so I can activate it on my line and I am not too good with this whole unrooting stuff. Is there a simple way to do it? I tried going through fastboot--recovery then flashing the superwipe but it just ended up causing the phone to be stuck on the white screen on reboot with the green HTC.
vtotheinay said:
thanks. im still having a problem cause the phone is running TWRP recovery and the bootloader is unlocked but he wiped the SD card so all the files that should be on it after the unlock and flash of the recovery are gone. Im having a huge problem trying to get this MIUI off the phone. I just want to get it back to running a stock rom so I can activate it on my line and I am not too good with this whole unrooting stuff. Is there a simple way to do it? I tried going through fastboot--recovery then flashing the superwipe but it just ended up causing the phone to be stuck on the white screen on reboot with the green HTC.
Click to expand...
Click to collapse
After you wipe the hone you need to flash a ROM. When you wipe the phone it is completely blank.
Are you just doing a factory reset and rebooting? If so, that won't get you back to an HTC ROM. You need to wipe and then flash a new ROM. That will get you off of miui.
So you flashed the super wipe and then didn't flash a ROM? You have no OS loaded on your phone. Download a ROM, put it on your sd card, and flash it. Make sure it's a sense ROM since you'll need to be on a sense ROM to activate it. No need to unroot.
Sent from my HTC EVO 3D using Tapatalk
k2buckley said:
Are you just doing a factory reset and rebooting? If so, that won't get you back to an HTC ROM. You need to wipe and then flash a new ROM. That will get you off of miui.
So you flashed the super wipe and then didn't flash a ROM? You have no OS loaded on your phone. Download a ROM, put it on your sd card, and flash it. Make sure it's a sense ROM since you'll need to be on a sense ROM to activate it. No need to unroot.
Sent from my HTC EVO 3D using Tapatalk
Click to expand...
Click to collapse
No I used superwipe and then flashed clean rom 2.9.5 but it got stuck on the white screen on the reboot.
Do I have to use adb to run fastboot and then go into recovery or can I turn the phone off, boot into fastboot by holding power, vol down and going into recovery?
vtotheinay said:
No I used superwipe and then flashed clean rom 2.9.5 but it got stuck on the white screen on the reboot.
Do I have to use adb to run fastboot and then go into recovery or can I turn the phone off, boot into fastboot by holding power, vol down and going into recovery?
Click to expand...
Click to collapse
Since you're on hboot 1.5, you either need to flash using joeykrim's flash image gui app, or you need to put your phone in Gaynor, plug into the computer, and from the command prompt on your computer boot your recovery image. It's something like fastboot boot recovery.img. You will need to search for the exact command. Once you boot into recovery using that method you will be fine, just use recovery like normal. If you don't use one of those two methods you won't be able to flash the boot.img, so the phone won't boot. Good luck.
Sent from my HTC EVO 3D using Tapatalk
I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?
jeggen said:
I have a new HTC Evo LTE and HBOOT 1.15.000 Radio 1.05.11.0606and do not have S-OFF.
I installed Fresh 5.2.1 and had problems, when back and did a wipe including system and installed 5.2.1 again and it didn't work. After doing that I went back, wiped system again, and then restored the backup I previously made. Now the backup sometimes loads, sometimes doesn't, but even when it does I have no radio. I am going to try to install a stock rom through recovery or fresh 5.1.1 and HOPE I get radio back.
Any other suggestions of what I could do?
Click to expand...
Click to collapse
So now I'm just in a boot loop. I relocked, installed stock recovery and ran RUU. When I did that I booted just long enough that I could almost slide the ring to unlock before I rebooted. Then the device just constantly reboots.
I unlocked again, installed TWRP 2.2.2.0 in case there was a bug causing flashing issues. Recovery boots just fine now. I flashed Stock Rooted DeOdexed 1.22.651.3 from here since that was the version I had before this whole fiasco. I'm going to try to restore backup again but don't know how to get out of this horrible mess. Worse part about it is that it's my wife's phone! Help please!
You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"
metalfan78 said:
You might need to run a different RUU. I'm not too experienced with that kind of issue though.
"We're coming from a pure power source"
Click to expand...
Click to collapse
I reflashed stock recovery, relocked bootloader (fastboot oem lock), ran RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3_Radio_1. 05.11.0606_NV_SPCS_2.45_003_release_268323_signed. exe), and still had the boot loop problem. RUU said it completed but the bootloader still said "relocked". Isn't RUU supposed to totally wipe and restore the entire device?
I recall on my old EVO there was a zip you could place in the SDcard that the bootloader automatically looked for and would use to reflash to factory everything. Is there a way to do this with the EVO 4g LTE?
Is it possible that radios/firmware somehow got borked even though I am on S-ON? Is there a way to reflash them from bootloader?
Just thinking through ideas I'd try next and something that could possibly help recover or at least put me in a position to go back to Sprint for help.
Could have been a bad download. I think there is info on re locking in the development sticky section. It might give you some more information on what to do next.
"We're coming from a pure power source"
Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?
jeggen said:
Just an update. Flashed again a stock ROM and installed the boot.img from stock using fastboot to be sure it was in place. (fastboot flash boot boot.img). That didn't work, still had boot loop where the phone loads enough to show the background and then restarts.
Used the PJ75IMG.zip file and attempted to install automatically in bootloader (from here) <-- Didn't install says "Main Version is older! Update Fail!
I then installed stock recovery and locked bootloader. Bootloader now shows "*** TAMPERED*** and *** RELOCKED***.
Ran RUU <-- Have a hard time doing anything since it doesn't boot up long enough to connect. Eventually RUU will fail with a connection error. I haven't been able to run RUU from HBOOT either and without the device stable long enough I'm not sure how to get RUU to run on the phone.
Still only boot far enough to see the background screen (wallpaper) and then reboot.
I'll gladly give $20 to anyone who offers a workable solution, paid either to you, or dev/charity of your choice if you don't want it.
This all started when I installed Fresh 5.2.1. Not sure if it was the fresh install or using TWRP to wipe data/cache and I also wiped system. Was that a mistake?
I just don't understand why I can't flash back even to stock. Since I'm relocked and never had S-OFF I don't understand how I was able to do something that can't be undone by flashing. I've flashed phones dozens of times so am comfortable with the process and just can't understand what went wrong and how to recover.
Is there an updated version of the PJ75IMG.zip file I could use?
Would it work to flash CM10 & the boot.img using fastboot?
Click to expand...
Click to collapse
I sent you a PM
Sent from my EVO using xda premium
I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2
jeggen said:
I'm back up and running. With a kind and helpful tech we ran RUU again (twice) and still had boot loop. I was going to give up on it but we went into the default recover and cleared data and factory reset and it seems to be back to normal again and working fine.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
Awesome glad you got it fixed.
Sent from my EVO using xda premium
I just got my EVO LTE today. It has hboot 1.12, and is dev unlocked. I've tried flashing the newest nightly of CM10 with both CWM (5.8.3.5) and TWRP (2.2.2.0), and everything seems to go well until I boot into CM10, and it just sits at the CM loading animation forever. Yes, I've done the normal wiping of caches. Any ideas out there? Thanks in advance!
bilbo524 said:
Yes, I've done the normal wiping of caches.
Click to expand...
Click to collapse
Wiping caches isnt the proper wipe.
Thats your issue,.
Do a factory reset, wipe system, data, cache, and dalvik cache
Rxpert said:
Wiping caches isnt the proper wipe.
Thats your issue,.
Do a factory reset, wipe system, data, cache, and dalvik cache
Click to expand...
Click to collapse
Ah. I'll try this right now.
I only ever did cache partition and dalvik when flashing CM7 on my EVO Shift and it worked fine first try, just assumed that's all I needed here.
Thanks already given
bilbo524 said:
Ah. I'll try this right now.
I only ever did cache partition and dalvik when flashing CM7 on my EVO Shift and it worked fine first try, just assumed that's all I needed here.
Thanks already given
Click to expand...
Click to collapse
No problem, I'll stick around for more options if that doesnt fix it.
Also, in an unrelated note, I would highly suggest looking into getting S-OFF
Worked like a charm! :highfive:
I was reading up on lazy panda, but I guess I don't see the benefits of s-off if all I'm doing is CM10 official builds. Care to enlighten me?
bilbo524 said:
Worked like a charm! :highfive:
I was reading up on lazy panda, but I guess I don't see the benefits of s-off if all I'm doing is CM10 official builds. Care to enlighten me?
Click to expand...
Click to collapse
S-OFF = bootloader securities off. You can flash things through the bootloader that are not signed by HTC.
With H-boot 1.12 you can still flash all the usual things that you would normally flash in the bootloader through the recovery, but S-OFF provides an extra bit of safety net in the fact that its future proof. Once you are S-OFF you are S-OFF until you flash the S-ON tool.
With HTC unlock, if somehow the phone gets updated (friends, family, ect not knowing to decline OTA's when using your phone) you lose all ability to flash new radios and other firmware bits. You would also have to fastboot flash kernels each time you flash a ROM. Its a pretty big pain.
Now, being on CM means you wont get HTC updates, so you shouldnt have to worry about it, but S-OFF is still regarded as being better for that added ability to flash through bootloader if things go wrong.
Its suggested that you have access to linux on your computer if you decide to S-OFF, because theres a chance you could temp brick the phone, and the unbrick tool only works in linux.
We have a great guide for this over on AF. Don't be discouraged by the size of it. Lazypanda only takes a few minutes if it doesnt brick.
http://androidforums.com/evo-4g-lte-all-things-root/605567-s-off-lazypanda-root-dummies-guide.html
I'll have to look into that. As an IT Engineer with a Linux background, it should be cake
Thanks again for all of your help!
Rxpert said:
but S-OFF provides an extra bit of safety net in the fact that its future proof. Once you are S-OFF you are S-OFF until you flash the S-ON tool.
Click to expand...
Click to collapse
Does this mean you can upgrade your hboot to 1.15 or 1.19 while still keeping S-OFF? I've been reluctant to touch my hboot out of fear of losing the S-OFF.
edit: whoops, found my answer in another thread. I guess it won't lose the S-OFF but I'm still going to leave it alone.
Sent from my EVO using xda app-developers app
Yes, but theres literally no need to update your h-boot
I had the same issue - didn't do factory wipe, just cache etc.. I cannot even boot into recovery - in a boot loop at that point too. Any suggestions on how to boot into recovery at that point?
if your boot looping. do a hard shut down of your phone. hold the power button down for like 20 seconds. your phone's capacitative buttons should flash. once its off. hold down the Volume down button and push power on the phone. it'll vibrate and should load into the bootloader menu. from there just select recovery and you should get in.
Is the "hard shutdown" an equivalent to a battery pull? ie. a function of the hardware, not software?
Sent from my EVO using xda premium
Yes, holding power for 10+ seconds is the same as a battery pull
I highly advise using lazy panda from a booted Linux pc. I used ubuntu 12.0.4. No bricking problems. As an IT guy you should have no problems with setting up a bootable drive or cd
Took your advice and did the following:
1. Obtained S-OFF via lazy panda.
2. Full backup via TWRP.
3. Flashed stock ROM and followed Regaw's S-ON guide to put phone back to stock (S-ON, no dev unlock, etc). (http://forum.xda-developers.com/showthread.php?t=1744700)
4. Re-rooted, used lazy panda again.
5. Booted into stock ROM and downloaded newest PRL.
6. Flashed newest Radio, PRI with ZIP from http://forum.xda-developers.com/showthread.php?t=1704612
7. Restored TWRP backup and am now running CM10 Nightly with newest Radio, PRI, and PRL, with S-OFF and no stupid dev-unlock.
Thanks for all of the help, guys! Everything went perfect.
I'm sure someone has ran into a similar issue.
I have a Sprint HTC EVO 4g lte.
Issue: I'm constantly being booted into my bootloader (Where I can see the mini me droids on skateboards)
My TWRP v2.3.3.0 is still fully functional, but for some aparent reason, after i flash a backup, or a new fresh rom from my SD Card, it completes the install and tells me to reboot.
After rebooting, I land straight into my bootloader with no hesitation.
I initially had Viper4g_2.0.2 rom and tried updating the Kernel for custom tweaks (Undervoltage, Underclocking, etc.), but I ended up here
Your assistance will gladly be appreciated
If I missed anything, please let me know.
Thanks,
Rizzo
are u s-on?? sounds like thats whats wrong
evo401 said:
are u s-on?? sounds like thats whats wrong
Click to expand...
Click to collapse
Thanks for the prompt response.
Yes, I am. I've been S-On ever sense I rooted my phone (over a year ago). The customer Kernel I tried using with the Viper4g Rom is named Beastmode.LTE RC7 by Zarbos which is S-On friendly if I'm not mistaken. It worked well, until i did some extreme tweaking to the voltages and underclocking.
Do you have any suggestions for a fix?
Or am I S.O.L. ?
I never had any luck with that particular kernel on ViperROM, however, I successfully ran the Liberty kernel from dev Evolutionmods. It's S-on friendly and can be flashed from recovery.
One other thought: You didn't do a system wipe from recovery after restoring your backup, did you? Go into recovery, wipe Dalvik cache, data, factory reset and wipe system, then try reflashing Viper like new. The system wipe will remove your current ROM from your phone.
Sent using my HTC EVO LTE and a magic wand
FinZ28 said:
If you made a backup of your ROM prior to flashing the new kernel, just select 'Recovery' from the menu in the bootloader and go into recovery and flash your backup. Otherwise, you may need to reflash your ROM completely to clear the issue. You can also retry flashing the kernel again through recovery.
Sent using my HTC EVO LTE and a magic wand
Click to expand...
Click to collapse
Thanks a lot for your input. However, I tried flashing two different new roms Viper elite 1.2.1(older version) and Viper4g 2.0.2 (newer version) and they both landed me straight to my bootloader after the installations were done.
I tried reflashing the customer Kernel since its still on my SD card, but neither one of these methods have helped me so far.
I don't even see the HTC Sprint logo animation anymore when my phone boots up, it just takes me straight to my boot loader.
How long have you had your phone, you say?
Edit: Don't try flashing the Zarboz kernel any more, at least until you get the phone up and running.
Sent using my HTC EVO LTE and a magic wand
FinZ28 said:
I never had any luck with that particular kernel on ViperROM, however, I successfully ran the Liberty kernel from dev Evolutionmods. It's S-on friendly and can be flashed from recovery.
One other thought: You didn't do a system wipe from recovery after restoring your backup, did you? Go into recovery, wipe Dalvik cache, data, factory reset and wipe system, then try reflashing Viper like new. The system wipe will remove your current ROM from your phone.
Sent using my HTC EVO LTE and a magic wand
Click to expand...
Click to collapse
No. I never wipe after installations. I only wipe prior to flashing roms/updates/backups.
What Hboot are you on?
Sent using my HTC EVO LTE and a magic wand
FinZ28 said:
How long have you had your phone, you say?
Edit: Don't try flashing the Zarboz kernel any more, at least until you get the phone up and running.
Sent using my HTC EVO LTE and a magic wand
Click to expand...
Click to collapse
I would say for about a year or a little less and never had a problem until today, when I decided I wanted to expand my horizons with custom kernels (For purposes like; underclocking/overclocking, undervoltage, battery life enhancements, etc.. ).
FinZ28 said:
What Hboot are you on?
Sent using my HTC EVO LTE and a magic wand
Click to expand...
Click to collapse
This is the info my bootloader shows me...
***Tampered***
***Unlocked***
Jewel PVT SHIP S-ON RL
HBOOT 1.15
RADIO 1.05.11.0606
OpenDSP v25.1.0.32.0405
eMMC - boot
Jun 18 2012
Have you tried just flashing a stock/rooted Sprint Rom to see if it loads up?
enos said:
Have you tried just flashing a stock/rooted Sprint Rom to see if it loads up?
Click to expand...
Click to collapse
standby for an update....
FinZ28 said:
Go into recovery, wipe Dalvik cache, data, factory reset and wipe system, then try reflashing Viper like new. The system wipe will remove your current ROM from your phone.
Sent using my HTC EVO LTE and a magic wand
Click to expand...
Click to collapse
I tried following these steps and I received successful for wiping Cache & Dalvik-Cache set and failed 'factory reset wipe'. It seems I may I have a problem with Updating partition details (What does this mean)? Ex. Shown below:
Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik/-cache...
Cleaned: /cache/dalvik-cache...
Cleaned: /cache/dc
-- Dalvik Cache Directories Wipe Complete!
Updating partition details...
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
is my SD card damaged? and if so, I wouldn't understand how, because I can still flash my [backups/roms/kernels] directly from the SD card via the TWRP recovery flash method....
No I don't think so, I have received those same errors when clearing cache and my phone did load a ROM and works just fine.
---------- Post added at 11:13 PM ---------- Previous post was at 11:00 PM ----------
I was having a similar issue today, still not real sure what caused the problem but I was able to find a stock/rooted ROM and loaded that through TWRP and I'm back up andrunning just fine.
I am going to try and download a custom ROM again and load it up to see if I still have problems. I am S-Off but from what I've read S-On shouldn't necessarily cause problems loading a ROM.
I would try the ROM's found HERE and see if they'll load up for you. If they do then you can be sure your phone is working and start figuring out why the customs aren't loading up.
I'm not sure if viper has a s-on installer but I know mean Rom has. Your s-on so you have to flash the kernel separately unless the Rom does it for you. Try mean Rom and I strongly suggest you check out the dirty racoob thresd
Sent from my EVO using xda premium
As a last resort, you may have to format internal storage. Also, try removing SD. Does your internal mount in TWRP, or external?
Sent from my EVO using xda premium
enos said:
I would try the ROM's found HERE and see if they'll load up for you. If they do then you can be sure your phone is working and start figuring out why the customs aren't loading up.
Click to expand...
Click to collapse
I followed these instructions and flashed the jewel_1.22.651.3_rooted deodexed_8-27-2012.zip via TWRP. It did show successful but I'm noticing that i receive the same message regarding mounting after every flash (rom, backup, kernel). Example shown below:
_______________________________________________
HTC Evo 4G LTE Rooted DeOdexed 1.22.651.3 Update
-Prepared by HAUS
Formatting and Mounting Partition...
Extracting System Files...
Installing System Files On /data As Needed
Setting Permissions...
Copying fotaBoot To /data/system For Customized Reload...
Running skin _fota tool...
Installing Kernel, please wait...
Kernel Will Be Installed On Startup.
Finished!
Updating partition details...
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
--------------------------------------------------
After flashing, I get the option to go back home, reboot, or Wipe cache/dalvik...
Once I reboot, I'm back into my bootloader...
scottspa74 said:
As a last resort, you may have to format internal storage. Also, try removing SD. Does your internal mount in TWRP, or external?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I can not mount my SD card or my internal storage via TWRP. I'm starting to think that my TWRP may be corrupted when it comes to mounting and partitioning SD card and internal storage. (a new recovery?)
Do i need to install/flash a new recovery, or should i try formatting the internal storage by mounting USB storage via TWRP and formatting it via my PC?
I had a similar issue awhile back... Everything would wipe but somehow it seemed my system partition had corrupted... I had to run a pj75img stock zip in order to get anything to install or restore... Phone finally booted and I was back to normal... I was s-off too though..
Sent from my EVO using Tapatalk 2
OK, go here: http://unlimited.io/jewel.htm and follow their instructions through step 11. This will restore your phone back to stock and unlock your phone. You then will have the option to continue their steps and s-off if you want or you can install twrp and continue being s-on. It is important to look at step 9 and read it carefully. If you get this error just follow step 9 to the letter and it should re run the ruu and complete. VERY IMPORTANT, make sure you chose the correct ruu. Only run a ruu that is correct for your current hboot. Make sure you use Dirty Racuns ruu for this install. I think this will fix you up and like I said, at this point you might as well go s-off.
Running ICS rooted S on
flashed "Official jb ruu 3.15.651.16 Odex. zip" using TWRP it said it was successful. Went back to reboot system. The phone got to the htc quietly brilliant screen, then went black. I got a few white bars to pop up on the top of the black screen then nothing.
I then went in and flashed "boot img flasher v1.2 jb.zip" it failed until I cleared the D-cache, then it passed. Back to the reboot screen. reboot system and it did the same thing.
I then recovered ICS and rebooted and the phone is back to the old system
What am I missing?
Would it be easier to take the OTA version and then root to S off?
I've never bothered with RUU's but if I'm not mistaken you have to re-lock your bootloader and run the RUU through the bootloader, not recovery.
With some of the threads popping up about people having issues with the new JB RUU, you might be better off finding a rooted JB ROM, like MeanBean, and run that, instead. You'd be better off getting S-off, then upgrading.
Sent using my HTC EVO LTE and a magic wand
jchtcusre1 said:
Running ICS rooted S on
flashed "Official jb ruu 3.15.651.16 Odex. zip" using TWRP it said it was successful. Went back to reboot system. The phone got to the htc quietly brilliant screen, then went black. I got a few white bars to pop up on the top of the black screen then nothing.
I then went in and flashed "boot img flasher v1.2 jb.zip" it failed until I cleared the D-cache, then it passed. Back to the reboot screen. reboot system and it did the same thing.
I then recovered ICS and rebooted and the phone is back to the old system
What am I missing?
Would it be easier to take the OTA version and then root to S off?
Click to expand...
Click to collapse
If you're s-on, retry flashing...(wipe everything and start over)..you're gonna have to flash jb Roms twice (as long as they are the zip format ones to my knowledge)...s-on is causing the kernel to take 2 flashes to install....first flash will install the kernel and then after that is successful, reflash without wiping anything and the Rom should boot....its a known procedure/hurdle for s-on users...hope that explains the bootloop. Let me know if it works...
Sent from my EVO using xda app-developers app
onefasttreopro said:
If you're s-on, retry flashing...(wipe everything and start over)..you're gonna have to flash jb Roms twice (as long as they are the zip format ones to my knowledge)...s-on is causing the kernel to take 2 flashes to install....first flash will install the kernel and then after that is successful, reflash without wiping anything and the Rom should boot....its a known procedure/hurdle for s-on users...hope that explains the bootloop. Let me know if it works...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
This is true with MeanBean due to how the kernel installs. You have to basically flash the ROM twice when you're S-on. Some ROM's have a S-on kernel installer, while others don't.
I still say get S-off, upgrade your firmware and install a rooted JB ROM.
Sent using my HTC EVO LTE and a magic wand
Than
Thank you both, I'll give that a try and see what happens. I wished I could have found that info earlier Been reading and messing with this phone for Hours.
Umm boot img flasher is a windows program that you run on a windows pc. You have to extract all the files out of the zip. NOT flash it on your phone. What hboot do you currently have?
Nope still not there. I tired flashing the rom 5 times and although I got to the second HTC quietly Brilliant screen, it still just goes black. I think I'll look into the dirty racun or lazy panda since I'm still at 1.12 h boot.
jchtcusre1 said:
Nope still not there. I tired flashing the rom 5 times and although I got to the second HTC quietly Brilliant screen, it still just goes black. I think I'll look into the dirty racun or lazy panda since I'm still at 1.12 h boot.
Click to expand...
Click to collapse
Did you do a clean install wiping cache/del cache/system/ factory reset then flash the rom?
What version of twrp are you using? v2.3.3.0 is the latest version
Btw RUU's are .exe files not .zip files AFAIK
Since you're on Hboot 1.12, flashing the kernel separately isn't an issue like it is with the newer Hboots. That being said, it sounds like your issue lies elsewhere. Make sure you've got a good download (verify MD5 checksum) and make sure you wipe properly. For me, I'd wipe cache and Dalvik, factory reset and wipe system (this will wipe your current ROM from your phone), then flash the new ROM. Once you've flashed the new ROM, don't wipe anything in recovery, just go ahead and reboot. I'd definitely look at going S-off, as already stated.