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.
Related
I'm on HBOOT 1.5 and have unlocked my phone the HTC unlock method and from what I've read and understand the only drawback is that I have to use fastboot in order to write to the boot area and properly flash a ROM (which I have done many times and am very familiar with the process), or I can just use the Flash Image GUI app (which I have also used many times). Are there other restrictions I'm not aware of?
petermg said:
I'm on HBOOT 1.5 and have unlocked my phone the HTC unlock method and from what I've read and understand the only drawback is that I have to use fastboot in order to write to the boot area and properly flash a ROM (which I have done many times and am very familiar with the process), or I can just use the Flash Image GUI app (which I have also used many times). Are there other restrictions I'm not aware of?
Click to expand...
Click to collapse
Nope, not that bad at all as far as I can tell. I'm running CM9 and love it
like it was my wife. I couldn't care less about more time in the command
prompt because if you don't use it you loose it. My 3D with HB 1.5 has ICS
port and my wife's fully rooted 4G doesn't so I'm feeling pretty good about
my HB 1.5 3D right now!
I don't have hboot 1.5 but I think you can use boot manager also which let's you install multiple roms on your ad card and let's you boot into them.
I blame 1.5hboot HTC method for random reboots and soft freezes
No issues with hboot 1.5 No reboots no nothing just some minor steps when it comes to flashing.
Sent from my PG86100 using xda premium
Don't you guys have to be connected to a computer in order to flash a rom?
oohaylima said:
Don't you guys have to be connected to a computer in order to flash a rom?
Click to expand...
Click to collapse
not with flash gui
Sent from my PG86100 using XDA
oohaylima said:
Don't you guys have to be connected to a computer in order to flash a rom?
Click to expand...
Click to collapse
nope just flash in recovery. if the rom has a custom kernel i just use flash img gui and it extracts the kernel and flashes it for you the just reboot in to recovery and flash the rom.
the only thing with 1.5 is we can't flash radios or splash screens.
Excellent. I thought you guys had to go through an elaborate process to install a Rom.
No, not really. Also, intentional brick method ftw.
there are many customization optiom option just like changing splash screen, cpu overclock, and many more for advance user.
Sent from my SCH-I500 using Tapatalk
jdeoxys said:
No, not really. Also, intentional brick method ftw.
Click to expand...
Click to collapse
I seen that method not a total brick tho if you do brick your phone it will behave like one no power. Dead
Sent from my PG86100 using xda premium
stevestone said:
there are many customization optiom option just like changing splash screen, cpu overclock, and many more for advance user.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I could already do an overclocked CPU with HBOOT 1.5, so I'm sure I could do the other things you mentioned also. Where can I find splash screens for the EVO 3D? I just did the HBOOT downgrade here because I like a challenge, not because I think I needed to. My wife is still on HBOOT 1.5. I'm just not sure having HBOOT 1.5 is really that bad a thing. I don't think there is anything you can't do with HBOOT 1.5 execpt that you need to use the computer or flash image gui.
EDIT: Oh and I never had any reboot issues or whatnot as someone else associated with HBOOT 1.5. Not that I ever noticed.
hboot 1.5 is not all that bad for your average user.
For "power users" it is a nightmare because it makes it a pain to flash kernels. Okay, maybe not a pain, but still. We like more control over our devices to be able to flash things where ever we'd like. Also, HTC's unlock makes the bootloader unable to accept PG86IMG.zips, which means flashing them via bootloader doesn't work. What does that mean? No "all-in-one" firmware update packages when new software versions are released. Lastly, no splash screen flashing. While this isn't a big deal, it still allows one to further customize their device.
I for one am very happy to be back on eng hboot 1.04 and thanks to the efforts of Unknownforce and everyone involved, this got made possible and for power users, it will make phone exchanges less of a risk.
I dont know... I dont really see the differences
For me personally, yes, its a terrible curse on my phone. For one, I couldn't change that super bright HTC splash screen, also I couldn't make or restore a nandroid backup unless I was fastbooted into recovery, which means I had to be at my computer. Fastbooting into recovery was just a command away, and id unplug from the computer right after booting to recovery so that I wasn't stuck at the computer, but still, I had to have a comp. Lastly, I use boot manager so if I switch roms and it wouldn't boot, I have to flash to the boot partition, which means I had to be at a comp. That happened at work and I was without a phone all day. I was spoiled with s-off on my EVO 4g so its really hard to get used to the HTC unlock. Thankfully, I downgraded and I'm now s-off, and loving it.
xcpefrmreality said:
For me personally, yes, its a terrible curse on my phone. For one, I couldn't change that super bright HTC splash screen, also I couldn't make or restore a nandroid backup unless I was fastbooted into recovery, which means I had to be at my computer. Fastbooting into recovery was just a command away, and id unplug from the computer right after booting to recovery so that I wasn't stuck at the computer, but still, I had to have a comp. Lastly, I use boot manager so if I switch roms and it wouldn't boot, I have to flash to the boot partition, which means I had to be at a comp. That happened at work and I was without a phone all day. I was spoiled with s-off on my EVO 4g so its really hard to get used to the HTC unlock. Thankfully, I downgraded and I'm now s-off, and loving it.
Click to expand...
Click to collapse
Does the cwm recovery not allow you to make and restore backups normally then?
Sent from my GT-I9100
Atomix86 said:
Does the cwm recovery not allow you to make and restore backups normally then?
Sent from my GT-I9100
Click to expand...
Click to collapse
A nandroid backs up your boot partition, and when u restore, it writes to boot partition. With htcdev unlock u can't do that unless you fastboot (from comp) to recovery.
And this is kinda weird, but good, with htcdev unlock, cwm wouldn't let my phone charge with power off. Now that I'm 1.4 s-off. It will. Charged all night with power off.
Easy adb and a computer Your all set . Root is easy. Swapping kernels is fine too. Stock kernel isn't bad .
Sent from my PG86100 using xda premium
xcpefrmreality said:
A nandroid backs up your boot partition, and when u restore, it writes to boot partition. With htcdev unlock u can't do that unless you fastboot (from comp) to recovery.
Click to expand...
Click to collapse
I don't see what the problem is. Can you not keep the boot partition the same when backing up and restoring? It never stopped me doing anything when I had an S-On Wildfire S
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
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
I am quite noob to flashing so I understand that it is my fault if something goes wrong..
My husband volunteered his Evo 4g lte for me to make my attempts. I unlocked the boot loader, though it was S-ON, and flashed TWRP recovery (latest version). It seems my phone was wiped entirely (will not boot into Android) and the backup I made did not "stick".. I made attempts to flash a ROM but figured it would not work since the phone is S-ON. I'm stuck in boot loop at the moment - shows HTC screen then reboots - and my PC will not recognize the phone in any way even if I attempt to mount storage while in TWRP. Am I screwed?
I would settle with being able to get it back to stock, but I don't think that is possible even.. Any advice, tips? If I need to share further information, let me know. Feeling stuck at the moment and I've got to get some sleep so it may be a few hours before I respond.
P.S. I'm on HBOOT 2.10 and was running the HTC RUU update that came out (Sense 5.. etc) if that helps. If my problems have been addressed elsewhere, please do point me in that direction if it would help..
Luna_Sky said:
I am quite noob to flashing so I understand that it is my fault if something goes wrong..
My husband volunteered his Evo 4g lte for me to make my attempts. I unlocked the boot loader, though it was S-ON, and flashed TWRP recovery (latest version). It seems my phone was wiped entirely (will not boot into Android) and the backup I made did not "stick".. I made attempts to flash a ROM but figured it would not work since the phone is S-ON. I'm stuck in boot loop at the moment - shows HTC screen then reboots - and my PC will not recognize the phone in any way even if I attempt to mount storage while in TWRP. Am I screwed?
I would settle with being able to get it back to stock, but I don't think that is possible even.. Any advice, tips? If I need to share further information, let me know. Feeling stuck at the moment and I've got to get some sleep so it may be a few hours before I respond.
P.S. I'm on HBOOT 2.10 and was running the HTC RUU update that came out (Sense 5.. etc) if that helps. If my problems have been addressed elsewhere, please do point me in that direction if it would help..
Click to expand...
Click to collapse
Being that you are hboot 2.10, you must use the TWRP recovery found here:
http://forum.xda-developers.com/showthread.php?t=2639180
Also, because you are S-on, for AOSP ROMs, you must either fastboot flash the boot img or use flashify or flash img GUI. Both are available in play store. First, install the correct TWRP recovery and get up and running. Then read up on S-on kernel installing. I also strongly recommend getting S-off using the rumrunner method.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Evolution_Freak said:
Being that you are hboot 2.10, you must use the TWRP recovery found here:
http://forum.xda-developers.com/showthread.php?t=2639180
Also, because you are S-on, for AOSP ROMs, you must either fastboot flash the boot img or use flashify or flash img GUI. Both are available in play store. First, install the correct TWRP recovery and get up and running. Then read up on S-on kernel installing. I also strongly recommend getting S-off using the rumrunner method.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just to add on, I never had luck with rumrunner on the new partition layout, that being said firewater worked just fine.
Sent from my EVO using XDA Premium 4 mobile app
Both have worked for me on the new partition. The most common problems with getting s-off seem to be that people don't turn off their antivirus, or they forget to uninstall htc sync before running the utility. Or both.
I don't know why one would want to remain s-on. Just seems like it makes it a lot harder, with no real benefit in return.
Personally I would just rerun the ruu to get back to stock, then get s-off and the right twrp, then make a nandroid before going with anything custom.
Sent from my EVO LTE using XDA Premium 4 mobile app
Evolution_Freak said:
Being that you are hboot 2.10, you must use the TWRP recovery found here:
http://forum.xda-developers.com/showthread.php?t=2639180
Also, because you are S-on, for AOSP ROMs, you must either fastboot flash the boot img or use flashify or flash img GUI. Both are available in play store. First, install the correct TWRP recovery and get up and running. Then read up on S-on kernel installing. I also strongly recommend getting S-off using the rumrunner method.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you for the response! I have come to realize that doing this with S-ON is probably the worst thing I could have done.. *bangs head on desk*. I don't know if you saw in my OP, but my computer is not recognizing my phone at all, I can put files on a micro-sd (using an adapter).. I know I can use the external for other ROMS, but would the method that you linked to still work for the PJ75IMG file or could I use the version of TWRP that I have to move the PJ75IMG to the internal storage maybe? I'm using TWRP 2.7.1.0b..
EDIT/UPDATE: Okay, I thought I would try running adb fastboot and fastboot through the command terminal despite the computer not displaying the device as a storage device & it not working earlier this morning.. It appears my computer recognized it so I flashed the boot.img for the last ROM that I attempted to flash (SlimKat) and rebooted the phone.. It booted into SlimKat O.O It is up and running now.. So I *think* I'm good to go with that rom?!
If I want to change ROMS (this isn't the ROM I necessarily wanted), what should I look for? Will any ROM work that is for the new partition layout is what I mean? I was really interested in Dirty Unicorn.. Though the husband may appreciate SK!
Luna_Sky said:
Thank you for the response! I have come to realize that doing this with S-ON is probably the worst thing I could have done.. *bangs head on desk*. I don't know if you saw in my OP, but my computer is not recognizing my phone at all, I can put files on a micro-sd (using an adapter).. I know I can use the external for other ROMS, but would the method that you linked to still work for the PJ75IMG file or could I use the version of TWRP that I have to move the PJ75IMG to the internal storage maybe? I'm using TWRP 2.7.1.0b..
EDIT/UPDATE: Okay, I thought I would try running adb fastboot and fastboot through the command terminal despite the computer not displaying the device as a storage device & it not working earlier this morning.. It appears my computer recognized it so I flashed the boot.img for the last ROM that I attempted to flash (SlimKat) and rebooted the phone.. It booted into SlimKat O.O It is up and running now.. So I *think* I'm good to go with that rom?!
If I want to change ROMS (this isn't the ROM I necessarily wanted), what should I look for? Will any ROM work that is for the new partition layout is what I mean? I was really interested in Dirty Unicorn.. Though the husband may appreciate SK!
Click to expand...
Click to collapse
Yes, any ROM that supports the new partition layout will work. Also, in response to your other question, I believe you have to be S-off to use the PJ75IMG bootloader method. I'm glad to hear that you're up and running.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Evolution_Freak said:
Yes, any ROM that supports the new partition layout will work. Also, in response to your other question, I believe you have to be S-off to use the PJ75IMG bootloader method. I'm glad to hear that you're up and running.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm experiencing some problems with SlimKat and the hubby is really wanting me to flash Dirty Unicorn. Should I make attempts to resolve the problems with SK or can I move forward with flashing the DU rom?
Also, I want to make sure I have the process down that I should do BEFORE flashing a new rom... When using TWRP 2.7.1.0b, would the use of the default wipe feature (that says it wipes cache, etc, but not internal storage) work before flashing that rom or should I go into the advanced options? I assume I use the default wipe feature..
Luna_Sky said:
I'm experiencing some problems with SlimKat and the hubby is really wanting me to flash Dirty Unicorn. Should I make attempts to resolve the problems with SK or can I move forward with flashing the DU rom?
Also, I want to make sure I have the process down that I should do BEFORE flashing a new rom... When using TWRP 2.7.1.0b, would the use of the default wipe feature (that says it wipes cache, etc, but not internal storage) work before flashing that rom or should I go into the advanced options? I assume I use the default wipe feature..
Click to expand...
Click to collapse
You can move forward if that is your choice. I personally use advanced and wipe data, system, cache and dalvik. However the default (factory reset) in TWRP seems to work as well
Sent from my Nexus 5 using XDA Premium 4 mobile app
Evolution_Freak said:
You can move forward if that is your choice. I personally use advanced and wipe data, system, cache and dalvik. However the default (factory reset) in TWRP seems to work as well
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm curious, if I have Dirty Unicorn up and running, can I use the RUU that was released by HTC a few months back to revert back to the all stock rom? Or do I have to flash something? Just curious.
S-Off
Evolution_Freak said:
You can move forward if that is your choice. I personally use advanced and wipe data, system, cache and dalvik. However the default (factory reset) in TWRP seems to work as well
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Though both devices are now running custom roms, would I be able to do S-Off? Would it be worth it in the long run? From what I have seen, it seems that USB 2.0 ports are required or at least recommended. All of my ports are 3.0, are there any programs out that would work for me to achieve S-Off?
Luna_Sky said:
Though both devices are now running custom roms, would I be able to do S-Off? Would it be worth it in the long run? From what I have seen, it seems that USB 2.0 ports are required or at least recommended. All of my ports are 3.0, are there any programs out that would work for me to achieve S-Off?
Click to expand...
Click to collapse
I definitely recommend getting S-off. I recently returned my EVO LTE to stock, ran the 4.13 RUU, rooted and gained S-off (again) using the Firewater exploit in roughly a minute's time. I was using 3.0 USB ports when I did it.
Magnum_Enforcer said:
I definitely recommend getting S-off. I recently returned my EVO LTE to stock, ran the 4.13 RUU, rooted and gained S-off (again) using the Firewater exploit in roughly a minute's time. I was using 3.0 USB ports when I did it.
Click to expand...
Click to collapse
Well, I made my best attempts to use Firewater to no success. I followed the instructions exactly and things were looking good.. until it told me that "someone pissed in the firewater" and to reboot the device. I tried a couple of times and had no luck. Does the Android version matter or anything like that?
I'm running on the latest build of the Dirty Unicorn rom if that makes any difference.. Just thought I'd throw it out there again.
Luna_Sky said:
Well, I made my best attempts to use Firewater to no success. I followed the instructions exactly and things were looking good.. until it told me that "someone pissed in the firewater" and to reboot the device. I tried a couple of times and had no luck. Does the Android version matter or anything like that?
I'm running on the latest build of the Dirty Unicorn rom if that makes any difference.. Just thought I'd throw it out there again.
Click to expand...
Click to collapse
You should try using a closer to stock, sense ROM.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Evolution_Freak said:
You should try using a closer to stock, sense ROM.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashed Viper4G and ran Firewater again... Got S-Off just like that. Thank you for the tip!