So I've been trying to flash custom ROMs the past few days, and almost all of them end in bootloops. Even the two Stock-Rooted ROMs I found resulted in boot loops, regardless of how wipes & re-flashes I performed. The only ROM that I got to stick was Stock w/ Goodies... What's going on? I'm thouroghly confused. Would being S-OFF fix this?
Thanks in advance
bjb_nyj101 said:
So I've been trying to flash custom ROMs the past few days, and almost all of them end in bootloops. Even the two Stock-Rooted ROMs I found resulted in boot loops, regardless of how wipes & re-flashes I performed. The only ROM that I got to stick was Stock w/ Goodies... What's going on? I'm thouroghly confused. Would being S-OFF fix this?
Thanks in advance
Click to expand...
Click to collapse
Try either viper rom or mean bean rom, both have instructions and a s-on kernel installer, just read the first 4 posts and follow the instructions to the dot... Good luck!
Sent from my EVO using xda app-developers app
jocarog said:
Try either viper rom or mean bean rom, both have instructions and a s-on kernel installer, just read the first 4 posts and follow the instructions to the dot... Good luck!
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Thank you for the quick reply.
So is being S-ON the reason for this problem? Why is that?
Also, is it worth the trouble of me getting S-OFF? I don't want to brick my phone, and apparently that's possible with Rancun?
bjb_nyj101 said:
So I've been trying to flash custom ROMs the past few days, and almost all of them end in bootloops. Even the two Stock-Rooted ROMs I found resulted in boot loops, regardless of how wipes & re-flashes I performed. The only ROM that I got to stick was Stock w/ Goodies... What's going on? I'm thouroghly confused. Would being S-OFF fix this?
Thanks in advance
Click to expand...
Click to collapse
tl:dr version - No, but do it.
You don't NEED to be S-Off, but I STRONGLY suggest you do go S-Off. I was dev unlocked for a long time and it was a pain in my pants to do almost anything.
First things first, are you making sure to wipe everything before you flash? You need to make sure to wipe system, restore, and wipe caches before you flash. Every time, S-On or S-Off. No. Matter. What.
If you don't want to go s-off and that doesn't work, use an app called Flash Image GUI. It's a dollar and works wonders. I have no affiliations with the app or the dev, but it made my life a lot easier when I would flash. What you would do is browse for a kernel image (your rom), check Kernel Image, make sure the two boxes are checked at the bottom and flash the image. When that was done, you have to boot into your recovery and install your kernel again after wiping.
That worked for me every time.
mstrblueskys said:
tl:dr version - No, but do it.
You don't NEED to be S-Off, but I STRONGLY suggest you do go S-Off. I was dev unlocked for a long time and it was a pain in my pants to do almost anything.
First things first, are you making sure to wipe everything before you flash? You need to make sure to wipe system, restore, and wipe caches before you flash. Every time, S-On or S-Off. No. Matter. What.
If you don't want to go s-off and that doesn't work, use an app called Flash Image GUI. It's a dollar and works wonders. I have no affiliations with the app or the dev, but it made my life a lot easier when I would flash. What you would do is browse for a kernel image (your rom), check Kernel Image, make sure the two boxes are checked at the bottom and flash the image. When that was done, you have to boot into your recovery and install your kernel again after wiping.
That worked for me every time.
Click to expand...
Click to collapse
Yup, I'm definitely wiping every time.
So with Flash Image GUI, I flash my ROM with the app, reboot to recovery, then flash the ROM again?
You should get S-OFF to make your life easier, it's free and the easiest way is facepalm... Everything is in the original development thread, is real easy, and yeah your headache/bootloops are due to the need of flash the kernel separately, with S-OFF the process is easier and in one step... Venom team also has a kernel installer for s-on and it's free... Mean bean includes it for free but you have to follow the special instructions for s-on in the OP, good luck!
Sent from my EVO using xda app-developers app
I'm going to make this a lot easier than everyone else has been. No offence people.
DO YOU WANT TO BE HAPPY!? ARE YOU HAVING PROBLEMS IN THE BEDROOM!? IS WORK GETTING YOU DOWN!? FEAR NO LONGER!!!! WITH THE BEST DEVELOPERS ON THIS PLANET HERE TO PROVIDE YOU WITH ALL THE TOOLS YOU NEED TP SATISFY YOUR EVERY NEED! I PRESENT TO YOU: just S-OFF dude.
Enjoy.
Delakit said:
I'm going to make this a lot easier than everyone else has been. No offence people.
DO YOU WANT TO BE HAPPY!? ARE YOU HAVING PROBLEMS IN THE BEDROOM!? IS WORK GETTING YOU DOWN!? FEAR NO LONGER!!!! WITH THE BEST DEVELOPERS ON THIS PLANET HERE TO PROVIDE YOU WITH ALL THE TOOLS YOU NEED TP SATISFY YOUR EVERY NEED! I PRESENT TO YOU: just S-OFF dude.
Enjoy.
Click to expand...
Click to collapse
LOL you made me laugh... Get S-OFF or keep s-on and read a lot to get it to work... Is just an extra step on every single flash...
Sent from my EVO using xda app-developers app
bjb_nyj101 said:
Yup, I'm definitely wiping every time.
So with Flash Image GUI, I flash my ROM with the app, reboot to recovery, then flash the ROM again?
Click to expand...
Click to collapse
Yep - and in recovery just flash it like you would normal app wiping everything if I remember correctly.
Mnstrblueskies responses and verbage are confusing the situation. I'm fairly literate about this and his posts are making my head spin.
If you are S-on, the kernel doesn't get flashed. You need to use flash image GUI app or fastboot to flash the kernel (i.e.boot.IMG) before or after flashing ROM. Preferably before, I suppose. Or use the HTC dumlock feature in TWRP (I'm not real familiar, but instructions are in their op/thread) (I'm S-off).
The easiest way to update firmware/radios will require S-off. If you're already on the latest OTA (3.16), you'll have the latest touch panel drivers and will only be able to use sense 3.16 based ROMs, no AOSP or older sense. This can be remedied by getting S-off and downgrading your TP drivers.
Good luck
Sent from my EVO using xda premium
Related
I've been (at least trying to) patiently wait for Deck to post full install instructions for CM10 but the CM10 op is still bare as bones. Has anyone else posted an install guide or instructions yet?
I'm currently rooted with RegawMod and running MeanRom 2.1 and it's really terribly laggy and frustrating, I can't wait any longer for CM10. Do I need S-off to install CM10 or do I just wipe, flash, and go?
Thanks for any help or links!
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Its been my daily for 3 weeks.
Sent from my EVO using Tapatalk 2
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Sent from my EVO using xda app-developers app
corcgaigh said:
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Click to expand...
Click to collapse
Dont use flash image gui unless you know how to do it manually through fastboot. You are just asking for issues
Instructions:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Rxpert said:
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Click to expand...
Click to collapse
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Yes hboot 1.12 allows for access to the boot partition
Also luuuuucckkyyyyyy...
EdhyMonker said:
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Click to expand...
Click to collapse
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Bit off topic, anyone check to see if you can push a new splash, right now I'm too lazy to start my PC just to fastboot one measly splash
Rxpert said:
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Click to expand...
Click to collapse
The S-OFF guide was way over my head so I just let it be. If there's not a real good reason for doing it, and I can still run CM10, then I'd rather not.
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
om4 said:
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
Click to expand...
Click to collapse
No, S-ON people with 1.12 H-boot can flash radios and firmware from recovery. They can do whatever they please in recovery just like S-OFF. S-OFF users can flash things from bootloader and even change the appearance of their h-boot to read S-ON and **locked** even though they are S-OFF
To the OP, this is the best rooting guide I've seen. It really explains everything step by step. http://androidforums.com/evo-4g-lte...panda-s-htc-dev-ltevo-root-dummies-guide.html Its recommended to have Linux at least bootable, because in the small chance the phone gets bricked... the unbricker program requires linux.
I ran it in windows before the unbricker was available, no issues here
You basically just hook the phone up to it and run the program like you do for most other root programs. All 1-click
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
om4 said:
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
Click to expand...
Click to collapse
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
You don't have to flash any firmware updates. There are a few users with issues although they may be related to the ROM update and not necessarily the firmware included. I haven't really checked since I'm s on. If you want to update the radios there's an update zip here somewhere, be sure to read through everything carefully. Radios are more risky then every day flashing
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
EdhyMonker said:
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
Click to expand...
Click to collapse
ive only ever seen this issue with cyanogenmod and the old htc vogues, still great phones for what they were
EdhyMonker said:
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
Click to expand...
Click to collapse
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Rxpert said:
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Click to expand...
Click to collapse
Thanks, but I tried this and it says "no image or wrong image" when trying to flash the PJ75IMG.zip file.
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
joebarkho said:
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
Click to expand...
Click to collapse
I thought that might've been the issue so I tried it both ways, didn't work either way. I'll take another shot at it tomorrow.
I think I've done it this time. I was able to unlock the bootloader and also able to put TWRP recovery onto the phone. The mistake I made was trying to flash MIUI to the phone without backing anything up, so here I am and have been for the last 4 hours trying to figure out how to get my phone to boot into a ROM of any sort to try and S-OFF using the FacePalm method.
I honestly don't know what I should do at this point. I can still enter recovery and flash ROMs. Just, none of them actually load. The only time I can get any of them to load is when I flash it via recovery, then flash the boot.img via fastboot. However, when I do it this way, my touch screen within the ROM no longer works. So I can't press or do anything, to give my phone super user permissions. I'm really frustrated and just want to fix my phone. Can anyone offer some help or advice so I can try and fix this sometime between now and my death?
Thank you in advance.
cdboss said:
I think I've done it this time. I was able to unlock the bootloader and also able to put TWRP recovery onto the phone. The mistake I made was trying to flash MIUI to the phone without backing anything up, so here I am and have been for the last 4 hours trying to figure out how to get my phone to boot into a ROM of any sort to try and S-OFF using the FacePalm method.
I honestly don't know what I should do at this point. I can still enter recovery and flash ROMs. Just, none of them actually load. The only time I can get any of them to load is when I flash it via recovery, then flash the boot.img via fastboot. However, when I do it this way, my touch screen within the ROM no longer works. So I can't press or do anything, to give my phone super user permissions. I'm really frustrated and just want to fix my phone. Can anyone offer some help or advice so I can try and fix this sometime between now and my death?
Thank you in advance.
Click to expand...
Click to collapse
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
certain putesbi
FinZ28 said:
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thank you for your reply and help.
I'm running HBOOT 2.09 to be exact. I'm also running TWRP 2.5, so I'm good there as well. Right now I can't boot into a ROM appropriately to achieve S-OFF. I tried creating a Ubuntu Live CD and the Kernel got messed up I guess when putting it on the disc. That was another frustration of mine, lol. I can't achieve the FacePalm method because I can't boot into a ROM to adb shell as super user, since it physically needs to be accepted on the phone.
I'm going to read what you suggested, though, perhaps that will give me the answer.
Edit: I'm going to go with your suggestion of flashing a ROM that's made for 3.16, and see if my touch panel works so I can S-OFF and flash whatever I want. I'll let you know how that goes.
cdboss said:
Thank you for your reply and help.
I'm running HBOOT 2.09 to be exact. I'm also running TWRP 2.5, so I'm good there as well. Right now I can't boot into a ROM appropriately to achieve S-OFF. I tried creating a Ubuntu Live CD and the Kernel got messed up I guess when putting it on the disc. That was another frustration of mine, lol. I can't achieve the FacePalm method because I can't boot into a ROM to adb shell as super user, since it physically needs to be accepted on the phone.
I'm going to read what you suggested, though, perhaps that will give me the answer.
Click to expand...
Click to collapse
What ROM are you trying to run? If it isn't based on software version 3.16 it WON'T WORK.
Sent from my EVO using xda premium
FinZ28 said:
What ROM are you trying to run? If it isn't based on software version 3.16 it WON'T WORK.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Just edited my post. I'm an idiot and didn't completely read your post. My apologies. I'm in the process of getting Viper4G at the moment, to try and achieve S-OFF.
cdboss said:
Just edited my post. I'm an idiot and didn't completely read your post. My apologies. I'm in the process of getting Viper4G at the moment, to try and achieve S-OFF.
Click to expand...
Click to collapse
I was able to get into Viper, tried doing the FacePalm S-OFF and it wasn't successful, for whatever reason. However, at least I'm better off than I was before. Any suggestions from here? I really want to get MIUI on this and not really feeling up to installing Ubuntu tonight.
If not, I really want to thank you. At least I'm able to use my phone again, lol.
cdboss said:
I was able to get into Viper, tried doing the FacePalm S-OFF and it wasn't successful, for whatever reason. However, at least I'm better off than I was before. Any suggestions from here? I really want to get MIUI on this and not really feeling up to installing Ubuntu tonight.
If not, I really want to thank you. At least I'm able to use my phone again, lol.
Click to expand...
Click to collapse
You're going to have to go the Dirty Racun route, unfortunately
Sent from my EVO using xda premium
FinZ28 said:
You're going to have to go the Dirty Racun route, unfortunately
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Guess I'll have to try and make another Live CD. I have no interest in dual booting a copy of Ubuntu at the moment, lol.
Thanks for the help.
FinZ28 said:
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I now was able to get S-OFF. What exactly do I do to downgrade those drivers and flash a ROM that I want?
cdboss said:
I now was able to get S-OFF. What exactly do I do to downgrade those drivers and flash a ROM that I want?
Click to expand...
Click to collapse
If you want to downgrade your touch panel, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1704612
The above thread links to here:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
The touch panel you want to downgrade to is located under the 3.15 firmware, so just follow the directions posted in order to downgrade.
Sent from my EVO using xda premium
FinZ28 said:
If you want to downgrade your touch panel, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1704612
The above thread links to here:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
The touch panel you want to downgrade to is located under the 3.15 firmware, so just follow the directions posted in order to downgrade.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Awesome, thank you. I was able to get the ROM I wanted on here and looks like everything is good to go. Appreciate the help, FinZ28.
cdboss said:
Awesome, thank you. I was able to get the ROM I wanted on here and looks like everything is good to go. Appreciate the help, FinZ28.
Click to expand...
Click to collapse
You're welcome
Sent from my EVO using xda premium
I am looking to use moonshine to achieve s-off. I currently have S-ON and SuperCID. I need to update firmware first, so I need to switch back to stock. I am planning on using this method to do so.
Do I need to un-SuperCID, if so, how?
If I leave SupeCID, and run RUU what happens? No OTAs, or something worse?
Excuse my noob questions.
no noob questions here man thats why we help and as far as updating firmware are you planing on using a custom rom and kernel or just wanting s-off for a custom kernel on 2.07 firmware?
supercid does not need to be changed you only have extra steps if you are s-off which then you would need to relock the bootloader first
t1gartist said:
no noob questions here man thats why we help and as far as updating firmware are you planing on using a custom rom and kernel or just wanting s-off for a custom kernel on 2.07 firmware?
supercid does not need to be changed you only have extra steps if you are s-off which then you would need to relock the bootloader first
Click to expand...
Click to collapse
Well my plan was to go back to stock to ota to the 2.07 then load custom rom, vipers new one actually, after doing moonshine to achieve s-off
I thought leaving supercid was going to prevent me from successful ota. I can always flash the zip instead of ota though, right?
Also I made a more detailed thread in the development section on what I am going to work on doing, with steps that I think are correct, here is the link. I was finally able to post in that section
http://forum.xda-developers.com/showthread.php?t=2531701
d3fiance said:
Well my plan was to go back to stock to ota to the 2.07 then load custom rom after doing moonshine to achieve s-off
I thought leaving supercid was going to prevent me from successful ota. I can always flash the zip instead of ota though, right?
Also I made a more detailed thread in the development section on what I am going to work on doing, with steps that I think are correct, here is the link. I was finally able to post in that section
http://forum.xda-developers.com/showthread.php?t=2531701
Click to expand...
Click to collapse
Since you have super cid you don't need use moonshine. Find the face palm method and enjoy
Sent from my DLX using xda app-developers app
thats right phaded.. im sorry defiance i forgot about facepalm method been so long since my first device all the others are already updated
t1gartist said:
thats right phaded.. im sorry defiance i forgot about facepalm method been so long since my first device all the others are already updated
Click to expand...
Click to collapse
I wonder why I got stuck on moonshine? Face off seems so much easier, for me anyways. No need to go back to stock... So as far as Firmware, after s off I just go in and flash the zip through adb?
d3fiance said:
I wonder why I got stuck on moonshine? Face off seems so much easier, for me anyways. No need to go back to stock... So as far as Firmware, after s off I just go in and flash the zip through adb?
Click to expand...
Click to collapse
After s-off, flash a recovery through fastboot and then whatever Rom you want
Sent from my DLX using xda app-developers app
Phaded said:
After s-off, flash a recovery through fastboot and then whatever Rom you want
Sent from my DLX using xda app-developers app
Click to expand...
Click to collapse
I am happy to announce I am now S-OFF after facepalm! I actually found your thread about customer recovery. Will be doing that shortly.
One thing that is left to figure out is the tampered flag. I am not able to find any information on how to actually reset it. I found something on a different website about issuing a -t command. But that was after the s-off was achieved using revone. After further research, apparently all I need to do is flash another hboot to get rid of that flag?
P.S
This thread looks like a winner http://forum.xda-developers.com/showthread.php?t=2156713 am I on a correct path here?
yes thats correct
You can ignore that flag. If and when you return the phone to complete stock that will taken care of.
Sent from my DLX using xda app-developers app
t1gartist said:
yes thats correct
Click to expand...
Click to collapse
Phaded said:
You can ignore that flag. If and when you return the phone to complete stock that will taken care of.
Sent from my DLX using xda app-developers app
Click to expand...
Click to collapse
New problem. Flashed 2.6 twrp, erased system, cache and internal storage. Went to sideload mode, keeps saying starting. Issue a command in and to load a Rom, nothing happens, cmd return a list of all the commands. Twrp still states starting sideload. Restart the phone to recovery, still the same problem. Flash older version of twrp?
Also twrp keeps telling me I am not rooted.
Thoughts?
Why did you wipe internal storage? Easiest way is to load the ROM onto internal and flash.
Rebooting twrp will install su binaries.
Try older twrp or cwm
Sent from my DLX using xda app-developers app
Phaded said:
Why did you wipe internal storage? Easiest way is to load the ROM onto internal and flash.
Rebooting twrp will install su binaries.
Try older twrp or cwm
Sent from my DLX using xda app-developers app
Click to expand...
Click to collapse
Well Viper Sense 5 rom needed a full wipe, so, I wiped everything. Are you saying I do not have to wipe internal storage, just clear everything else, then flash the rom?
The problem was that I have a bad habit of putting spaces when renaming zip files. Once I renamed the zip adb worked just fine. :facepalm:
d3fiance said:
Well Viper Sense 5 rom needed a full wipe, so, I wiped everything. Are you saying I do not have to wipe internal storage, just clear everything else, then flash the rom?
The problem was that I have a bad habit of putting spaces when renaming zip files. Once I renamed the zip adb worked just fine. :facepalm:
Click to expand...
Click to collapse
Exactly, you don't need to wipe your internal storage. You lose pictures, videos, etc
Sent from my DLX using xda app-developers app
yeah with twrp 2.4.4.0 and later it is preselected for you so you dont wipe everything on your device just whats needed so lesson learned and in about a week you will be graduated to advanced droid dna room any hour lol
Phaded said:
Exactly, you don't need to wipe your internal storage. You lose pictures, videos, etc
Sent from my DLX using xda app-developers app
Click to expand...
Click to collapse
t1gartist said:
yeah with twrp 2.4.4.0 and later it is preselected for you so you dont wipe everything on your device just whats needed so lesson learned and in about a week you will be graduated to advanced droid dna room any hour lol
Click to expand...
Click to collapse
I am still learning as I go. Thanks for sticking around guys. But yay for graduation haha! :victory:
I have been flashing roms for the past 8 hours. Looking for the perfect sense 5. Every rom has issues with data on my phone. Tried 5 . Google play store will not download anything, Or it starts downloading at dial up speeds. 2 roms I actually had to reflash twice because they kept hanging u at at the initial start.
5 roms doing the same thing? I was starting to think something happened to the phone, so I reflashed the original UKB DNA 1.3 rom that I have been running all this time, and it does the same thing.
Any ideas?
flash a dead stock rom one by mircomod777 see how it runs should be last 4.1 version
t1gartist said:
flash a dead stock rom one by mircomod777 see how it runs should be last 4.1 version
Click to expand...
Click to collapse
So my phone went completely nuts last night. I decided to flash another back up that was working perfectly before going with your recommended rom. Kept failing in TWRP. So after 3 attempts I just decided to reload another rom. Rom installed, phone rebooted, went through initial setup. Once I finished with the initial setup my phone was running sense5 with all of the information from the backup. Needless to say I nuke everything, flash original TWRP (2.4.0.0 beta) that worked for me prior to 2.6. Do a clean install of Viper Sense5 rom and voila! Running perfect right now, no complaints. Fingers crossed. I guess I am done flashing roms for right now and sticking to Vipers. At least until KitKat comes.
good deal
So I already had an HTC Rezound for a year and was too afraid to root-so I bought an already rooted rezound from eBay that came with a 16 gig recovery sd card. I don't know what to do or how to flash a Rom or what I should do as a root noob... Can I please get some guidance from an experienced person?
Sent from my ADR6425LVW using xda app-developers app
undeadking said:
So I already had an HTC Rezound for a year and was too afraid to root-so I bought an already rooted rezound from eBay that came with a 16 gig recovery sd card. I don't know what to do or how to flash a Rom or what I should do as a root noob... Can I please get some guidance from an experienced person?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Any idea what's on it now? Check the rom info in Settings, About Phone.
Also power it off, pull the battery, put it back in and turn the phone back on while holding Volume down, that'll get you the bootloader. See what version you have and if it's s-on or s-off.
From there you can select Recovery on the menu and boot into it, see what recovery you have.
Let us know and we can go from there.
Sent from my ADR6425LVW using xda app-developers app
undeadking said:
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Looks like just the stock rom. What version hboot, are you s-on/off and what recovery do you have?
Just did what you said and took some pictures that i will post to show you what I'm working with.
Sent from my DROID RAZR HD using xda app-developers app
Is this the right information that you needed to know?
Sent from my ADR6425LVW using xda app-developers app
undeadking said:
Is this the right information that you needed to know?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You are already unlocked and have Amon Ra recovery installed, the "hard" stuff is done (actually it's not hard), and FYI you are S-ON... You are pretty good to go for any ICS based ROM. If you want to move into JellyBean or KitKat based ROMs you should switch to TWRP or CWM Recovery. Other than that, your good to go.
Ok, thanks a bunch! Ive done tons of reading about flashing roms and am still a little weary about the actual process. Ive read that a computer is needed in some cases but in others people are switching roms right from their phone- whats the safest or correct way to do it?
Sent from my DROID RAZR MAXX HD using xda app-developers app
undeadking said:
Ok, thanks a bunch! Ive done tons of reading about flashing roms and am still a little weary about the actual process. Ive read that a computer is needed in some cases but in others people are switching roms right from their phone- whats the safest or correct way to do it?
Sent from my DROID RAZR MAXX HD using xda app-developers app
Click to expand...
Click to collapse
Although there are ways around it (that I don't recommend, mind you) the rule of thumb is based on whether you are S-ON or S-OFF...
When S-ON, a computer has to be involved so that the boot.img can be loaded... you must either: A) flash the boot.img manually with fastboot after flashing the ROM in recovery, or B) boot the recovery image file with fastboot and flash the ROM file
When S-OFF, no computer is required, all partitions of the phone are writable by recovery directly.
acejavelin said:
Although there are ways around it (that I don't recommend, mind you) the rule of thumb is based on whether you are S-ON or S-OFF...
When S-ON, a computer has to be involved so that the boot.img can be loaded... you must either: A) flash the boot.img manually with fastboot after flashing the ROM in recovery, or B) boot the recovery image file with fastboot and flash the ROM file
When S-OFF, no computer is required, all partitions of the phone are writable by recovery directly.
Click to expand...
Click to collapse
Don't forget you can use the phone (or a computer) to pack the boot.img into a PH98IMG.zip. As long as it boots, that is.
Hi All,
I am also new at rooting the Rezound and I'm having trouble. I did quite a bit of reading and followed the instructions here: theunlockr.com/2012/08/24/how-to-root-the-htc-rezound-video/
Apparently this was for an older version because I can't install ClockworkMod Recovery ("an error occurred ..."). I read that getting a backup of ClockworkMod Recovery was the best thing to do before installing any ROMs. Is that really necessary? It seems like I could always find an RUU on this site and flash back to ICS if I wanted to right?
Can some one point me in the right direction for what I should do next? Basically all I want to do is flash a ROM on my Rezound that will enable me to use it as a wall controller for my home automation system. So, ideally I'd like to remove the swipe to unlock feature (just be able to press the power button to get to the home screen) and to be able to force a nightly reboot with Tasker and remove as much bloatware as possible. This device is connected to my home network through wifi only. Any ideas what the best ROM would be for that?
By the way my recovery screen looks like undeadking's. I have S-On.
Thanks!
next
Easiest way to get where you want is to HTC unlock if not already done,
S-0ff with RumRunner, then follow this thread with all its great stuff:
http://forum.xda-developers.com/showthread.php?t=2509770
You will end up with newest radios that are best for newer stock and custom roms.
There are several daily-user type custom roms mentioned in Development.
After you read a little about each, you'll know what you want to try first.
I like the custom Sense roms for best battery life.
michaelbsheldon said:
Easiest way to get where you want is to HTC unlock if not already done,
S-0ff with RumRunner, then follow this thread with all its great stuff:
http://forum.xda-developers.com/showthread.php?t=2509770
You will end up with newest radios that are best for newer stock and custom roms.
There are several daily-user type custom roms mentioned in Development.
After you read a little about each, you'll know what you want to try first.
I like the custom Sense roms for best battery life.
Click to expand...
Click to collapse
Thanks, I was able to get my ROM working. The problem I was having was I was still S-ON. I was a little leery about turning it off so I found instructions for flashing with it still on here: androidforums.com/rezound-all-things-root/499172-how-manually-flash-roms.html
I installed the LiquidSmooth ROM and I was able to disable the lock screen. Thanks again.
acejavelin said:
Although there are ways around it (that I don't recommend, mind you) the rule of thumb is based on whether you are S-ON or S-OFF...
When S-ON, a computer has to be involved so that the boot.img can be loaded... you must either: A) flash the boot.img manually with fastboot after flashing the ROM in recovery, or B) boot the recovery image file with fastboot and flash the ROM file
When S-OFF, no computer is required, all partitions of the phone are writable by recovery directly.
Click to expand...
Click to collapse
There are ways using terminal emulator with an s-on device alongside using a proper busybox installation to flash without using a pc and no fastboot/hboot access is needed. flashing a boot.img while in rom, rebooting to recovery and finish installing the matching rom by flashing its zip.
petewill8 said:
Thanks, I was able to get my ROM working. The problem I was having was I was still S-ON. I was a little leery about turning it off so I found instructions for flashing with it still on here: androidforums.com/rezound-all-things-root/499172-how-manually-flash-roms.html
I installed the LiquidSmooth ROM and I was able to disable the lock screen. Thanks again.
Click to expand...
Click to collapse
the one big issue you need to worry about while being s-on is if you soft brick while s-on there is absolutely almost no fix...with s-off you con ruu.exe to safely restore your phone which you cannot do while s-on....if you plan on flashing custom roms alot than i HIGHLY suggest going s-off or you'll regret not doing so when that time comes
REV3NT3CH said:
the one big issue you need to worry about while being s-on is if you soft brick while s-on there is absolutely almost no fix...with s-off you con ruu.exe to safely restore your phone which you cannot do while s-on....if you plan on flashing custom roms alot than i HIGHLY suggest going s-off or you'll regret not doing so when that time comes
Click to expand...
Click to collapse
I second this... S-Off is highly recommended, it might not seem necessary now, but when something goes wrong, you will be glad you did it.
Thank you both. I had not read that before. I guess I will be performing the S-Off after all.
Don't freak out if your ROM doesn't boot after running rum runner happened to me xD just go into recovery and flash your stuff again. Clean flash it. Make sure you're s-off though Lol hopefully doesn't happen to you
Sent from my Rezound. CyanogenMod 11. S-off
pball52998 said:
Don't freak out if your ROM doesn't boot after running rum runner happened to me xD just go into recovery and flash your stuff again. Clean flash it. Make sure you're s-off though Lol hopefully doesn't happen to you
Sent from my Rezound. CyanogenMod 11. S-off
Click to expand...
Click to collapse
Just do a quick backup of your ROM in recovery then when done restore it.
Sent from my Rezound using xda app-developers app
Just a thing. All my recoveries failed all 4, they would do the same thing and boot loop itself. *sigh* o well.
Sent from my Resound using tapatalk. CyanogenMod 11. S-off.
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Need to wait for hboot to be modded to have that removed
Wonders_Never_Cease said:
Need to wait for hboot to be modded to have that removed
Click to expand...
Click to collapse
Ah okay thanks. Wasnt sure if Hboot was universal or if it was by build.
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Wonders_Never_Cease said:
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Click to expand...
Click to collapse
I'm on build 2.22.401.5 running VenomOne rom, S-Off, rooted all the good stuff. Will your hboot mod work for mine?
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Wonders_Never_Cease said:
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Click to expand...
Click to collapse
OK and I can just install either one of those hboots over my existing one and it wont brick my phone or is this more to this?
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Wonders_Never_Cease said:
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Click to expand...
Click to collapse
Found it, thanks man. Gonna mess with it a little later.
CavyS said:
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Click to expand...
Click to collapse
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
thinkhope said:
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
Click to expand...
Click to collapse
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
CavyS said:
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
Click to expand...
Click to collapse
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
redpoint73 said:
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
Click to expand...
Click to collapse
It was just easier for me to fallow a set of instructions going step by step than jumping around just to avoid 1 easy step.
thinkhope said:
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah still works, you might of read that Firewater for some people doesnt work on 4.4.3. For me Firewater worked and I'm S-Off for some people it doesnt and you have to use Sunshine in that case.
thinkhope said:
So the toolkit still works??
Click to expand...
Click to collapse
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
redpoint73 said:
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
Click to expand...
Click to collapse
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Click to expand...
Click to collapse
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
redpoint73 said:
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
Click to expand...
Click to collapse
I definitely did have the evita. Had to alter the cid to make htc dev believe it was a different phone or something like that, if I remember correctly.
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Well, sounds easy enough. I will be attempting later tonight after work. Thanks for all of your help. If it's OK, mind if I PM you if something goes wrong?
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Click to expand...
Click to collapse
S-off is needed to flash radio, hboot, SIM unlock, and some other things. But not for root or to flash ROMs. Pretty much similar to how things were on the EVITA; with the exception that boot.img will flash automatically along with the ROM (not possible on most hboots on the EVITA, and had to be flashed manually with fastboot).
It sounds like you are already on the "official" 2.23 software (Android 4.4.3) by OTA? If so, you don't need to update firmware (radio, hboot, etc.) as the OTA already updated it. Otherwise, s-off is needed to flash the firmware manually; which is pretty much required for any 2.xx Sense based custom ROMs (otherwise there will be serious bugs like very long boot times, broken WiFi, Bluetooth). While s-off is not strictly needed to flash the ROM (it will flash correctly) things just won't run right if firmware is outdated. This is the only reason you would "need" to have s-off for flashing ROMs. AOSP and GPE ROMs won't suffer this issue.
But if you are already on the new OTA, this isn't an issue for flashing any ROM. You can verify by looking at the hboot version and baseband. If you are on hboot 3.18 and baseband 1.19; your firmware is up to date, and won't be an issue for running any ROMs.
thinkhope said:
mind if I PM you if something goes wrong?
Click to expand...
Click to collapse
I actually prefer you just posting to the forums. Either to an existing relevant thread, or start a new one if a relevant one does not already exist.
Couple reasons for this:
- Info given to you can help others reading the forums, and benefit the community as a whole instead of being hidden away in PM
- You can get help from more than just one user. I don't claim to even remotely know everything, and often its helpful to have more than one set of eyes on a problem (especially the tougher ones). And I might not even be online to help.
In particular for the 2nd point: my wife and I are going to be having a baby, with scheduled induction tomorrow (Sept. 5) unless it happens by itself sooner. So I won't be available to help you when that happens, anyway!
In any case, good luck!