[Q] Newbie: problems using Regaw rooter for EVO 4G LTE - Sprint HTC EVO 4G LTE

I was attempting to use the method found here: http://forum.xda-developers.com/showthread.php?t=1690919 to root my EVO 4G LTE, but am unable to post in that thread with questions, as I have less than 10 posts, apparently. My issue is that I go all the way through the process, install ROM manager, and then try to flash the latest ClockworkMod (Superuser 3.0.7 efghi), but it gives me the following error:
"You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use Google Search on your computer to find instructions to root your phone"
I rebooted into recovery mode, and it does say "UNLOCKED" and "TAMPERED" at the top... in case that's helpful. Does anyone know where I might go to figure this out? I've been combing through the original post by regaw_leinad but haven't spotted anything yet. Any help is appreciated.

CWM doesn't work on our phone. You have to flash TWRP via terminal emulator.
Sent from my EVO using XDA

Yeah they really should put a disclaimer on that cwm thread. You would never know looking at the op that it doesn't work.

Evo_Shift said:
Yeah they really should put a disclaimer on that cwm thread. You would never know looking at the op that it doesn't work.
Click to expand...
Click to collapse
There is a disclaimer and the download was removed from the thread ages ago. This is only an issue for people who don't research first and try to use rom manager to install cwm (no offense to op). ROM manager should have a disclaimer also.

hmm... okay, well thanks for the info. maybe i've hosed something, as after installing the GooManager app as directed on the teamwin site and then initiating the download of the OpenRecoveryScript, it does not seem to do anything after the download, though the app says that it would reboot to install.

i'm still up against a wall with using either the GooManager, or trying to copy the openrecovery script directly onto the internal SD card and using terminal emulator... is there another method? or another way to approach this or start all over or something? it just seems like i can't get anything to work like it's supposed to at this point... even the terminal emulator is telling me that "su" isn't a recognized command... any help is appreciated.

mckraut79 said:
i'm still up against a wall with using either the GooManager, or trying to copy the openrecovery script directly onto the internal SD card and using terminal emulator... is there another method? or another way to approach this or start all over or something? it just seems like i can't get anything to work like it's supposed to at this point... even the terminal emulator is telling me that "su" isn't a recognized command... any help is appreciated.
Click to expand...
Click to collapse
I used the same root process and flashed cwm via rom manager and then had to go to goomanager. Goomanager works since I got twrp working, but I haven't flashed anything since I wanna wait to see if the new roms break lte (if lte comes to Seattle).

i tryed flashing twrp through goo manger also and it didnt work after it downloaded it woulndt reboot.. so i had to flash twrp using terminal emulator.. worked like a charm

Won't break lte like the Wimax issues. Lte info OS stored on the simcard unlike Wimax in a separate partition
sent from my EVO LTE

any advice on the su command not found in terminal emulator? i searched on google and saw other people having similar problems and mentioned making sure that SuperSU was running first which I have installed unbeknownst to me... though if I try to launch SuperSU, it tells me that there is no SU binary installed and SuperSU cannot install it, and all I can do is quit.

Try the flashable in the supersu thread

just to add another note... I also went through the process to install the Android SDK, so that I could connect via adb... after doing that, I can access my device via adb, but after doing "adb shell", I then try to use the su command, and get the same error,
su
/system/bin/sh: not found
what am I missing here? is my phone not truly rooted then?

i rebooted into recovery and verified that the boot loader shows UNLOCKED and TAMPERED (that's desired, right?) and that TWRP was my new recovery image, if that's the term for it. i had already downloaded the latest viperboy image, and booted into twrp and went through the install process for that image..... and the weird thing was everything seemed like it took and it installed. but nothing was different on a reboot. any ideas?

Unlocked and tampered don't necessarily mean you have root. At the risk of sounding stupid I have one question. Have you tried re-running Regaw one click then flashing your desired ROM of choice?
Seems re-running the script has fixed other people's issues.
sent from my LTEvo

believe me, if anything I'm the one that sounds stupid here I'm sure. at any rate, I did run regaw twice, but that was a while ago, and it was because it seemed like the first time through it didn't complete the process successfully for some reason. i can run it again today. after i do that, is the best way to tell if you're rooted to run the terminal emulator and try an su command and see if it's successful or not?

An app that requires root will work, if you get a prompt you should be golden. I would recommend re-running you should be fine, if there is an additional problem there is a fix for what clockwork would have messed up in the twrp thread (on my phone can't find it now), but I think you should be fine.
Edit: I lied, if you have the misc partition issue from trying cwm the fix is in viper Rom thread here. http://forum.xda-developers.com/showthread.php?p=26663638
sent from my LTEvo

well i ran the root method from regaw again and it looks like i'm now good to go as far as i can tell.... i'm running viperboy's ROM... i saw one from flex360 (the super stable/fast one), but not sure which ZIP package to download... so not sure if i will try any others since i'm not sure what to do there (and i can't post in those threads to ask for advice). i see the charmeleon one looks popular also...but then i would have to flash that boot file also? maybe i should just let good enough alone and be happy with the ROM i have.. thanks for all the help and suggestions here, you guys are helpful

No problem, viper Rom is good (running it until cm9 is official) you can flash another Rom but heed any OP warnings. Also, don't be flash happy, it could prove harmful in the end. :beer:
sent from my LTEvo

excellent! thanks for the info... that's really exactly what i wanted to hear... the validation that the rom i have is perfectly fine and just be happy

Also, as for the charmeleon ROM, I believe you SONT need to flash a boot.img. I believe that info is deprecated. Within the first few pages you'll find out for sure.
I believe when joelz first posted the ROM he thought that'd be necessary, but was able to include boot.img in ROM zip.
sent from my Jewel via xda premium.

Related

s-off no root?

Hi all,
I'm in the process of rooting my phone and I WAS going to put an almost stock rom on it - the bloatware but I'm having trouble running Titanium Backup and getting the phone to recognize that it's been rooted.
So far I have:
Ran Revolution
This gave me S-Off the first go around but didn't install Clockwork Mod, so I ran it again and I have S-Off and CWM now.
After that I had problems with the SMS, Error Code 64 Error Class 2, I called support and they had me do some stuff with ##82# and got it fixed.
Then I downloaded Titanium backup, which told me I didn't have Root.
Grabbed Root Checker, it told me I didn't have Root too.
After more searching I found someone saying that if I hit Problems? in Titanium it would download and update Busy Box for me, so I tried that, only it downloaded a program called Superuser instead (Android with a Pirate Patch logo).
Checked for updates with Superuser and it told me I was Legacy, then when I tried to update it failed.
Grabbed Busy Box Installer and attempted to run it, won't install because it says I don't have Root.
If I'm not mistaken, I can just flash a rom now, but I wanted to backup my apps and data, so I'd like to get Titanium running somehow. I suspect my problems are related to still having the stock rom Sprint gave me on release last July...but I can't get rid of that without getting rid of my apps and data. Is there something I'm missing here?
to gain root access on stock rom, you have to find the proper signed zip (I've used Superuser-3.0.7-efghi-signed.zip) and install from recovery, s-off is not needed for this operation. If you look there are a lot of how to.
S-off and root are two different operation and they are not related. To get root you need just a recovery
sgunfio said:
to gain root access on stock rom, you have to find the proper signed zip (I've used Superuser-3.0.7-efghi-signed.zip) and install from recovery, s-off is not needed for this operation. If you look there are a lot of how to.
S-off and root are two different operation and they are not related. To get root you need just a recovery
Click to expand...
Click to collapse
Thanks, I must have missed that. The documentation's kind of scattered to the four winds. I'll let you know how it goes.
you are welcome
i had problem with s-off just because the how to linked a pg86img.zip that not worked with my phones... tons of tryouts then i just redownloaded it from an other link, just worked like a charme at first try
I'm struggling to find a good guide for getting the Superuser zip onto the phone. I'm assuming the file you mentioned earlier will work for the Evo 3D and I found that. I found this and it's saying to install from Fastboot, which I'm not able to find a guide on and not exactly sure how to do...
www dot komodocontacts dot com/page/how-to-unlock-and-install-superuser-su-on-android-without-breaking-ota-updates
It's not as simple as loading the files up in recovery is it?
Any ideas?
well, i've to save the zip on sdcard, then reboot the phone in fastboot to access to recovery (you may enter in fastboot in two way: power+(vol -) or adb reboot fastboot, the you have to enter in recovery and "apply any zip", select the proper zip and ... done
---------- Post added at 08:30 AM ---------- Previous post was at 08:18 AM ----------
I forgot .... you may use "adb reboot recovery"...
Thanks a lot, got it.
Also found this video, first part goes through running Revolution.
www dot youtube dot com/watch?v=xlO8QtMVq6g

[UPDATED 3.16.13] [ROOT] [GUIDE] 6 Steps! [Works with all builds up to 3.16.651.3]

This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!

[Q] HTC One X + (boots to HTC white screen only)

Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Update: I've finally figured out how to get the TWRP recovery booted. Now working on trying to get my phone to boot up an OS of some sort. Very slowly but surely.
bullmurf said:
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Click to expand...
Click to collapse
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Addicted2xda said:
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Click to expand...
Click to collapse
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
bullmurf said:
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
Click to expand...
Click to collapse
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Addicted2xda said:
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Click to expand...
Click to collapse
"use sideload to copy / install a custom ROM..." OK I don't know anything about this but it will point me in the right direction. I have the phone unlocked. The HBOOT version is 1.40.0000. I'll see if I can do what you suggested, thanks.
Update: Atempting an adb sideload using TWRP which seems to be the only option for me.
ADB Sideload
What is ADB sideload?
--------------------------------------------------------------------------------
ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. ADB sideload is a different ADB mode that you can use to push and install a zip using one command from your computer. Most likely ADB sideload won't be very useful for your average recovery user, but ADB sideload can be a huge time-saver for a ROM developer.
How do I use ADB sideload?
--------------------------------------------------------------------------------
1.Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher
2.Have newer ADB binaries installed on your computer. If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.
3.Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
4.From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
Click to expand...
Click to collapse
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
bullmurf said:
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
Click to expand...
Click to collapse
Update: after trying the same thing 100 times it decided to send "sideload". command line was adb sideload name.zip. Installing Viper ROM for HOX+ atm. I'll see if it fixes all of my problems. Thanks for all of the help to this point. I'll type up a guide of what went wrong with my root and how we managed to get it fixed.
Update: Phone is booting to HTC white screen and then shutting off. Now trying to figure that one one out.
Update" Phone is booting to HTC white screen now and staying there. In TWRP under reboot is says "no os installed, do you still wish to reboot". Still digging in the forums to figure this one out and how to fix it. I installed the Viper ROM fine but when it asked to reboot now it just rebooted to HTC white screen. Missing something here? The phone is S-ON, does that make a difference in using the TWRP?
Is there an RUU exe file I can run from my computer? I relocked the phone but the links you gave me are for installing the ap through google play. Not sure how you do that with a phone that wont boot past htc screen.
Update: I've found an RUU application from these boards that is supposed to work for HOX+ so i'm downloading it. It really is taking forever to find the information I need along the way from this board but it's here....somewhere...I think...Will keep plugging away but feel free to throw me a bone ever once in a while! =)
Update: The version that worked for others isn't the same version I have. Going to dig again for 1.19.502.1 version.
Update: Found the version in the last place I thought it would be...HTC website...Downloading it and just hoping its and application I can run on my computer.
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
I would suggest you to use hasoon's all in one toolkit
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
bullmurf said:
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
Click to expand...
Click to collapse
There is a great lockscreen called CLocker
Addicted2xda said:
There is a great lockscreen called CLocker
Click to expand...
Click to collapse
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
bullmurf said:
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
Click to expand...
Click to collapse
You will find it in the playstore itself
You need to set lockscreen to None
Addicted2xda said:
You will find it in the playstore itself
You need to set lockscreen to None
Click to expand...
Click to collapse
Thanks again man. I got it and the ring is gone \0/ Phone looks freakin amazing now with that lock screen and Elegancia rom. Glad you stopped by to help :good: Still learning my way around the forums and my rooted phone. It's great to not be stressed about bricking it ^^
suppils soars
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
mrmagoogt said:
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
Click to expand...
Click to collapse
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Addicted2xda said:
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Click to expand...
Click to collapse
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
mrmagoogt said:
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
Click to expand...
Click to collapse
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Addicted2xda said:
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Click to expand...
Click to collapse
Thanks, I used a script to charge my battery, relock bootloader and installed ruu file to get back to stock, rooted again using Hasoon2000's all in one kit...

[Q] How do I unroot?

Hello, recently I have rooted my phone using the toolkit. The current recovery I have is TWRP. I wanted the root in the first place to be able to use xposed. However, it wont work, Whenever I try to install the update or new version it force reboots my phone. Also I found out I cannot update my software! I tried unrooting using the unroot option on SU but it was only temporarily. I want a permanent unroot and back to stock.
Android version : 4.4.2
Software number : 1.12.502.18
I downloaded my stock image from http://forum.xda-developers.com/showthread.php?t=2701376 and the toolkit from http://forum.xda-developers.com/showthread.php?t=2699065
I tried to flash it using the toolkit but it gave me an error when I tried to flash it. I don't recall correctly but it said something about a remote error right when it was sending the image over. Honestly I do not want to do it again to see what it said in fear of bricking my phone. So I will try to be as detailed as possible.
When I downloaded the image it said something about the name not being the original one. When I first tried flashing the stock ROM with the original name when I download it"stock recovery 1.12.502 recovery.img" it (the toolkit) gave me an immediate error of not being able to select it. So I renamed it to "recovery.img". I tried again and it actually was in the process of flashing. THen the error showed up as said above. Someone please help me. Thank you.
Update
So i just downloaded a different image. I flashed it successfully! I am currently rebooting from the original recovery! Currently I am on the htc one loading screen. It's been a couple minutes, hopefully I did not brick it...
NOPE! I successfully returned to stock! ANother issue...I still have root access! How can remove SU? I tried the unroot option in the app but I am still rooted after reboot...
UNROOTED. Sadly SU won't delete...but at least I'm unrooted and can update now.
Sent from my HTC One_M8 using XDA Free mobile app
helpmeunrootmyphone said:
UNROOTED. Sadly SU won't delete...but at least I'm unrooted and can update now.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know if the app is that big of a deal to you, but if it is, your options are...
1. Try factory reset in settings (may or may not work)
2. Reflash TWRP and flash the SuperSU.zip again than do a full unroot in settings.
3. Reflash TWRP and flash stock Sense ROM
Also, I made a guide in general which will help you fully return to stock. To begin the guide, you will need to be unlocked, rooted, and S-Off. That guide will help you hide the tampered and relocked banner.
If you don't care about the banners and the SuperSU app, it's probably not worth the effort and time.
Good luck.
Sent from my HTC One_M8 using Tapatalk
So you had an issue with Xposed, and you solution was to unroot? Wouldn't it have made more sense to troubleshoot the xposed problem? If you bothered to unlock the bootloader and root in the first place, IMO unrooting is a step backwards.
I'm also not a big fan of applying OTAs to a modded device. Yes, you cannot install official OTA updates on a modded phone. In particular, if stock recovery is not present, as its required for the OTA to install. If you want the latest software, just wait until the rooted version is posted in the Development section. Custom ROMs based on the 1.58 update started to be posted one day after the OTA started rolling out; and the stock rooted version was posted only 2 days after OTA release. For some people, getting it from here may even be faster than waiting for the OTA! That's pretty much how it goes. As long as there is developer interest in the device, you can rely on the latest software being available very quickly in the Development section.
The stock AT&T software is garbage anyway. I can't stand the amount of bloat, gimped features (WiFi hotspot) and other AT&T meddling. I don't understand why anyone would prefer this over other options. Software updates are always going to go to the international version first, anyway (AT&T is notorious for delaying updates for "testing"). What are you really getting with the 1.58 update? Extreme Power Savings mode, and a few other fixes? International M8 has had EPS mode for some time now.
---------- Post added at 09:31 AM ---------- Previous post was at 09:17 AM ----------
helpmeunrootmyphone said:
I downloaded my stock image from http://forum.xda-developers.com/showthread.php?t=2701376 and the toolkit from http://forum.xda-developers.com/showthread.php?t=2699065
I tried to flash it using the toolkit but it gave me an error when I tried to flash it. I don't recall correctly but it said something about a remote error right when it was sending the image over. Honestly I do not want to do it again to see what it said in fear of bricking my phone. So I will try to be as detailed as possible.
When I downloaded the image it said something about the name not being the original one. When I first tried flashing the stock ROM with the original name when I download it"stock recovery 1.12.502 recovery.img" it (the toolkit) gave me an immediate error of not being able to select it. So I renamed it to "recovery.img". I tried again and it actually was in the process of flashing. THen the error showed up as said above. Someone please help me.
Click to expand...
Click to collapse
Why do you need to use the toolkit at all, to flash recovery? Flashing recovery is a single fastboot command. Easy.
The toolkit adds unnecessary complication; and I've seen them cause errors when doing it "manually" works just fine. The toolkit might not be the problem in your case, but we would never know unless you try to do it manually.
If you really want to flash stock recovery (not my personal recommendation), I would start by wiping cache and flashing recovery with fastboot. I've seen maybe dozens of cases where issues with flashing a recovery was solved simply by wiping cache:
fastboot erase cache
fastboot flash recovery "filename.img"
I am having the same issue as above using the same build file from the link given in the other thread. However, whenever I am in Bootloader, the computer or terminal does not recognize my device.
1.12.502.18
Anytime I try to use the toolkit or manually through the command line, it gives me "unc paths are not supported" or "device not found". It is the same for both Bootloader and Recovery. My original problem was the person I bought it from had root on it so I decided to wipe the OS without backing up and now cannot get the Stock Recovery ROM or any other Custom ROM to install on the phone. I have also tried the SD card method and that brought up an error as well resulting in "failed."
Any help would be appreciated as the phone as it sits right now does not have any OS on it so it is stuck on the HTC Boot up screen.
Thanks in advance for those that can help.

AT&T HTC One M8 Questions and Problems Rooting...Help!

I know there has been many threads giving explicit instructions on how to unlock bootloader, gain s-off, and install TWRP recovery. But I am having problems/questions that no one (at least of what I've read) has encountered. I will try and make this clear for y'all but bear with me. Before I start just let it be known that I DO HAVE my bootloader unlocked. I ended up going to a cell phone repair place and paying a small fee to get my bootloader unlocked.
1. Do I need to gain s-off to be able to root and install TWRP recovery?
I say this because the I have tried the has00n application to unlock bootloader, gain s-off, root, and install TWRP recovery, but I ran into problems with my computer recognizing my device. I had all the necessary files downloaded (at least to my knowledge) but it honestly just wouldn't recognize my device.
2. If I do not need to gain s-off to install TWRP recovery and install a custom ROM (I'm going to be installing Cyanogenmod), how do I go about doing that?
Honestly I'm so fed up with this that I just want to sell this phone and get another one, all I want to do is get Cyanogenmod on this phone but it's so immensely difficult.
Please help me! I have been trying to get this accomplished for so long but I feel like because this phone is older all the info about how to root and gain s-off is outdated.....
All of your help is greatly appreciated!!
You shouldn't need s-off for installing a custom rom. That's for tinkering with model id and scary stuff like that. I'm not sure what that tool is but I only know of one way to get s-off, and that's sunshine s-off.
As for rooting, when you install a custom rom via twrp or cwm, it will typically ask you if you'd like to root your phone AFTER installing the rom, but BEFORE you restart the first time. So the process should be:
Unlock
Install twrp or cwm
Wipe and factory reset
Install rom
Once completed, phone will prompt if you want to restart
Select YES to root on restart
And then wait for the phone to reboot! (it'll take a little while first time)
After the boot, it'll probably ask you to install superSU, which is the root manager app. If it doesn't, find it in the play store and you're set.
Sent from my HTC One_M8 using Tapatalk
shoe-jitsu said:
You shouldn't need s-off for installing a custom rom. That's for tinkering with model id and scary stuff like that. I'm not sure what that tool is but I only know of one way to get s-off, and that's sunshine s-off.
As for rooting, when you install a custom rom via twrp or cwm, it will typically ask you if you'd like to root your phone AFTER installing the rom, but BEFORE you restart the first time. So the process should be:
Unlock
Install twrp or cwm
Wipe and factory reset
Install rom
Once completed, phone will prompt if you want to restart
Select YES to root on restart
And then wait for the phone to reboot! (it'll take a little while first time)
After the boot, it'll probably ask you to install superSU, which is the root manager app. If it doesn't, find it in the play store and you're set.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. So as of right now I am using the fastboot adb to control my phone from the command prompt on the computer, but there is a problem. When I try and flash the custom recovery (either TWRP or CWM) it says that the files are unrecognizable, so they're pretty much corrupted. I honestly don't know that to do. I know I can achieve root if I just get either one of these recoveries to flash but it seems that all the files for the htc one m8 TWRP and CWM are corrupted. What are you suggestions at this point? The fastboot iadb is working perfect I just need a non-corrupted recovery file and I'm searching around the internet withno luck of finding one. Is there one that you can attest to working? If so that would be amazing. Again, thanks for your help, hopefully we can get this sorted out!
Hmm, do you have the latest version of twrp? Sometimes older versions don't install, I would try to see what version of twrp htc one m8 users are using, I'm not by my computer right now so I'm not sure. I also know that twrp works better on htc one for some reason, I've never found a version of cwm that works on my htc one. Make sure you are using the proper install command to install it too, I think it's fastboot flash recovery FILENAME.IMG
If all else fails, all I can think of at this point is that you got a bad download or something ?
Sent from my HTC One_M8 using Tapatalk
shoe-jitsu said:
Hmm, do you have the latest version of twrp? Sometimes older versions don't install, I would try to see what version of twrp htc one m8 users are using, I'm not by my computer right now so I'm not sure. I also know that twrp works better on htc one for some reason, I've never found a version of cwm that works on my htc one. Make sure you are using the proper install command to install it too, I think it's fastboot flash recovery FILENAME.IMG
If all else fails, all I can think of at this point is that you got a bad download or something
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yeah I've been trying to use the most current version of twrp and it didn't work. I ended up trying past versions and those didn't work either. The fastboot command i am using is the same as the one you stated. There's just a problem with the files. I'm beyond frustrated but really thank you for your help. When you're by your computer can you please send me the twrp version you have, it would be much appreciated.
flapjackSam said:
Yeah I've been trying to use the most current version of twrp and it didn't work. I ended up trying past versions and those didn't work either. The fastboot command i am using is the same as the one you stated. There's just a problem with the files. I'm beyond frustrated but really thank you for your help. When you're by your computer can you please send me the twrp version you have, it would be much appreciated.
Click to expand...
Click to collapse
Can you copy and paste your command window to this thread? It would help to see the exact error outputting. You can highlight and right click to copy anything from command window.
flapjackSam said:
Yeah I've been trying to use the most current version of twrp and it didn't work. I ended up trying past versions and those didn't work either.
Click to expand...
Click to collapse
Is the phone currently on Lollipop, or otherwise? You can't know what version TWRP is correct, without this info. Current TWRP (2.8.7.0) won't work if the phone is on older OS version. Vice versa, if the phone is currently on Lollipop, older versions of TWRP (I believe older than 2.8) won't work. You have to flash the specific TWRP version that matches your OS version. Guessing which TWRP version to flash is not the right way to go about this.
Also, you need to tell us the actual TWRP version number you got, and where you downloaded it from. I've seen quite a few instances where folks thought they had the "most recent" version, but in fact they weren't even close. Its always best to be specific as possible, and provide all the details when getting help here.
Additionally, go into Settings (or do getvar all), and tell us the software number. If you got the Stagefright patch, it might be screwing up install of TWRP as well.
flapjackSam said:
The fastboot command i am using is the same as the one you stated. There's just a problem with the files..
Click to expand...
Click to collapse
Again, just saying you used the "same" command isn't enough. A single wrong character, wrong file name, wrong path will cause the command to fail. As the previous response requested, please cut/paste, or better yet post a screenshot of your command prompt window, so we can see the exact command syntax, and the specific error message.
I can virtually guarantee that as long as you downloaded the file direct from the TWRP website, and tried downloading (and flashing) it more than once (to eliminate the possibility of corruption during file transfer); that the issue is almost certainly pilot error.
Somehow I'm a little frusrated. I've brought my phone since today. So it is currently on Lollipop. There is no Power in setting to uncheck Fastboot. Is there any way I can root my phone?
MistakenUtopia said:
Somehow I'm a little frusrated. I've brought my phone since today. So it is currently on Lollipop. There is no Power in setting to uncheck Fastboot. Is there any way I can root my phone?
Click to expand...
Click to collapse
Press and hold the power button until is hard reboots, then hold vol down as well. You should go to boot loader before the HTC screen pops up.
Back Up!
Just a reminder, after you install TWRP, boot into recovery (TWRP) and create a backup file saved to your SD card first before trying to install a new ROM!
Always can restore if things go wrong or you don't like it.
:fingers-crossed:

Categories

Resources