So Weaksauce won't do anything since it says I'm already rooted... Rootchecker and SuperSU say I am NOT rooted. Not sure where to go from here since SuperSU doesn't seem to have access to install new binaries..
I was on CleanROM and had an issue with something so I tried to reinstall it, but installed a Sense rom over it by accident and realized root was messed up. Did "Wipe For New ROM" or whatever the option in TWRP is, installed CleanROM which is pre-rooted, then ran into this seemingly uncorrectable root issue.
TheCheeks said:
So Weaksauce won't do anything since it says I'm already rooted... Rootchecker and SuperSU say I am NOT rooted. Not sure where to go from here since SuperSU doesn't seem to have access to install new binaries..
I was on CleanROM and had an issue with something so I tried to reinstall it, but installed a Sense rom over it by accident and realized root was messed up. Did "Wipe For New ROM" or whatever the option in TWRP is, installed CleanROM which is pre-rooted, then ran into this seemingly uncorrectable root issue.
Click to expand...
Click to collapse
Have you tried flashing SU in recovery?
...
droidkevlar said:
Have you tried flashing SU in recovery?
Click to expand...
Click to collapse
I flashed Superuser-3.1.3-arm-signed.zip in recovery, still no root.
RUU that bad boy.
TheCheeks said:
I flashed Superuser-3.1.3-arm-signed.zip in recovery, still no root.
Click to expand...
Click to collapse
.
godhamba said:
RUU that bad boy.
Click to expand...
Click to collapse
Never heard of RUU before but this sound like a solid fix. Will attempt this right now. Here is where I'm at though if you've got any other ideas:
S-Off (bootloader says UNLOCKED in fastboot)
I wiped /system, /data /cache and dalvik before installing a GPE ROM.
Weaksauce says already rooted, SuperSU says it can't update binaries.
Read this thread and follow the instructions. This will get your phone completely back to stock except that it will be pre-rooted. You should know what to do from there.
TheCheeks said:
Never heard of RUU before but this sound like a solid fix. Will attempt this right now. Here is where I'm at though if you've got any other ideas:
S-Off (bootloader says UNLOCKED in fastboot)
I wiped /system, /data /cache and dalvik before installing a GPE ROM.
Weaksauce says already rooted, SuperSU says it can't update binaries.
Click to expand...
Click to collapse
.
godhamba said:
Read this thread and follow the instructions. This will get your phone completely back to stock except that it will be pre-rooted. You should know what to do from there.
Click to expand...
Click to collapse
Thanks, that's the thread I found too. Attempted to get adb/fastboot working on my computer here at work but I'm tired of driver after driver. I know my MBP at home has a properly working adb/fastboot folder and boy is using Terminal better than CMD
The only question I have is what file(s) do I push? They have a tiny <10MB stickerfix.zip at the top of the post, but I feel like I should probably do the full RUU at the bottom, followed by the TWRP ruu/zip?|
Edit: NVM, I should read better. stickersfix is the last thing to flash to make sure any needed HTC stuff is put on the device.
Related
Hey all,
I rooted my HOX (1.73, 4.0.3) with the kpenn ne-Click a few days after I got it for the Tether and to de-bloat. Since then I haven't read anything on the One X till I heard Jelly Bean coming along. Anyhoo my question is what the upside of getting the new OTA (4.0.4) would be and how I would go about it if I wanted to (I've never updated before and ATT has stopped asking me to update, also I get nothing when I try to check for an update).
I've been reading around and it seems like most people are on to 1.85 and are flashing 4.1/2.2. My primary uses of my phone are for the media applications/web browsing and I haven't noticed any real drop in performance but I have heard the new updates have sped up the HOX considerably which is something I'm always interested in.
Thanks!
DON'T flash any OTA you will lose your root and will lose your ability to re root because there is no boot loader unlock for the new base. If you want to update and flash a new ROM and want to stick to sense, look at clean rom or xi40. Both are updated on the new base and are heaps and bounds better than the original ATT software :thumbup:
Shaddy-Z. said:
DON'T flash any OTA you will lose your root and will lose your ability to re root because there is no boot loader unlock for the new base. If you want to update and flash a new ROM and want to stick to sense, look at clean rom or xi40. Both are updated on the new base and are heaps and bounds better than the original ATT software :thumbup:
Click to expand...
Click to collapse
i one-clicked unrooted my phone earlier and freaked out (and the new updates didn't work out on my phone anyway). i ended up getting kpenn's one click again and putting SU back into my phone. Do you have any links that can take me on a step by step process of unlocking my phone and flashing those roms on it? I just love being able to control my phone and pushing it to its absolute limits.
Sigh. I followed the tutorial but I made a few mistakes...
1) I unlocked my phone way earlier than I should have so I wiped everything before I could make a back-up..
2) Re-locked accordingly to see if I could keep updating. I did manage to get to 1.85 like the tutorial said but.....
3) Since I didn't have a custom recovery I wasn't sure how to proceed. I couldn't get the root to flash so I tried using the 1-click 1.85 root since my phone was running 1.85.
....This ended up updating to 2.2 so now I have an unlocked HOX 2.2/4.0.4. With all the bloat.
Dumb dumb dumb. Ugh.
Pbdeng said:
Sigh. I followed the tutorial but I made a few mistakes...
1) I unlocked my phone way earlier than I should have so I wiped everything before I could make a back-up..
2) Re-locked accordingly to see if I could keep updating. I did manage to get to 1.85 like the tutorial said but.....
3) Since I didn't have a custom recovery I wasn't sure how to proceed. I couldn't get the root to flash so I tried using the 1-click 1.85 root since my phone was running 1.85.
....This ended up updating to 2.2 so now I have an unlocked HOX 2.2/4.0.4. With all the bloat.
Dumb dumb dumb. Ugh.
Click to expand...
Click to collapse
it's UNLOCKED?
you're lucky then.
just push a recovery like twrp then push root. Then you can debloat.
Yep, it's still unlocked. That was around the 4-7th reset I did (I messed up a lot). Do you have a link that shows me how to do that? I'm actually not as bummed about going to 2.2 since it runs so much faster than 1.73 did.
Pbdeng said:
Yep, it's still unlocked. That was around the 4-7th reset I did (I messed up a lot). Do you have a link that shows me how to do that? I'm actually not as bummed about going to 2.2 since it runs so much faster than 1.73 did.
Click to expand...
Click to collapse
make sure you have your unlock token and then go to http://www.htcdev.com/bootloader/unlock-instructions/page-4/
and follow the directions.
after that look at this thread to install twrp http://forum.xda-developers.com/showthread.php?t=1777773
then this one to re-root
http://forum.xda-developers.com/showthread.php?t=1673935
I notice one of the links is for 1.85. Does that mean that I'll go from 2.2 back to 1.85? I just wanted to make sure since my impression from the forums is that there is no 2.2 root yet unless it was flashed.
Pbdeng said:
I notice one of the links is for 1.85. Does that mean that I'll go from 2.2 back to 1.85? I just wanted to make sure since my impression from the forums is that there is no 2.2 root yet unless it was flashed.
Click to expand...
Click to collapse
no those pages just tell you how to manually install root and recovery.
your bootloader is still unlockable
unlock it
then install a recovery
then install root via that recovery
Ahh, thanks a bunch man.
Sorry if this is repetitive....
So I've checked my phone and currently it states that it is
"Re-locked"
I downloaded a recovery so it's currently on my phone. Furthermore I all ready had a copy of SU sitting in my phone's download folder.
Does this mean that I'm going to...
- Unlock bootloader (that is currently relocked) and have everything erased again.
- Reboot from recovery (of the evita 2.2.img I just downloaded with TWRP)
- Then flash the SU root I all ready have on my phone?
Pbdeng said:
Sorry if this is repetitive....
So I've checked my phone and currently it states that it is
"Re-locked"
I downloaded a recovery so it's currently on my phone. Furthermore I all ready had a copy of SU sitting in my phone's download folder.
Does this mean that I'm going to...
- Unlock bootloader (that is currently relocked) and have everything erased again.
- Reboot from recovery (of the evita 2.2.img I just downloaded with TWRP)
- Then flash the SU root I all ready have on my phone?
Click to expand...
Click to collapse
yeah unlock the boot loader. set up the phone again
then install the recovery then root.
to make your unlock stick, turn off fastboot in power options, then power down phone completely then restart it to the bootloader.
Hmm, so my phone is definitely unlocked now. I installed the recovery and I manually flashedthe new SuperSU in that link you posted for me. As far as I can tell nothing is happening.
Note: It says that it installs the recovery but there is no reboot that occurs. I've done this both with the android app and manually and nothing is happening.
I don't see SuperSU and rootchecker is confirming that my phone isn't rooted yet.
so you reboot to recovery, choose the superSU package to install then what happens?
I know this works I've done it quite a few times myself.
Presently I installed the latest img file with TWRP with the app. There is not reboot that occurs (unless I'm suppose to reboot on my own?). If that's the case then I've been a total idiot.
I've just been installing the openrecovery and then I press "Flash Roms" to flash the supersu. I get a little notification that says "Preparing to Flash" and then nada.
After you install twrp recovery you reboot. Then you boot to recovery and flash the super su zip manually
Wooh! I got it to work! Thank you so much!
Pbdeng said:
Wooh! I got it to work! Thank you so much!
Click to expand...
Click to collapse
No problemmo.
Does this also mean that I can flash any ROMs I want on my phone now?
Yes. But you will have to flash kernels aka boot.img separately using fast boot.
Just about to finish with the 2.20 exploit when I ran into a hiccup and now my bootloader screen shows TAMPERED with UNCLOCKED right below it. I just backed up my current system, am I to reboot or can I stay in TWRP and flash the perm root without having to reboot?
thinkhope said:
Just about to finish with the 2.20 exploit when I ran into a hiccup and now my bootloader screen shows TAMPERED with UNCLOCKED right below it. I just backed up my current system, am I to reboot or can I stay in TWRP and flash the perm root without having to reboot?
Click to expand...
Click to collapse
What are you trying to do? Flash the SU.zip onto your stock ROM? if so, just flash it in TWRP and reboot.
absolutelygrim said:
What are you trying to do? Flash the SU.zip onto your stock ROM? if so, just flash it in TWRP and reboot.
Click to expand...
Click to collapse
Yes. Is the tampered message anything to worry about? I pushed the SU .zip and rebooted and phone seems to work fine, though it seems like I don't have LTE all of a sudden.
thinkhope said:
Yes. Is the tampered message anything to worry about? I pushed the SU .zip and rebooted and phone seems to work fine, though it seems like I don't have LTE all of a sudden.
Click to expand...
Click to collapse
No, tampered just means /system partition was modified, most likely due to su being present in /system/xbin
Now that su is there, do you have a superuser app, such as SuperSU? If not, download it from the market and run the program to update your su binary and get configured. As for the LTE, I don't know
absolutelygrim said:
No, tampered just means /system partition was modified, most likely due to su being present in /system/xbin
Now that su is there, do you have a superuser app, such as SuperSU? If not, download it from the market and run the program to update your su binary and get configured. As for the LTE, I don't know
Click to expand...
Click to collapse
Thanks! Yes I do, I installed root checker just to double check and I indeed have root access. Now onto flashing a custom ROM. If someone can just give me a nod and let me know I'm heading in the right direction, I'd really appreciate it.
I'm going to use AOKP JellyBean. I download it, extract the boot.img to my fastboot folder, open up a cmd and "fastboot flash boot boot.img" Can I delete the boot.img from the ROM zip file after I flashed it throught fastboot? This is where Im getting a little confused.
thinkhope said:
Thanks! Yes I do, I installed root checker just to double check and I indeed have root access. Now onto flashing a custom ROM. If someone can just give me a nod and let me know I'm heading in the right direction, I'd really appreciate it.
I'm going to use AOKP JellyBean. I download it, extract the boot.img to my fastboot folder, open up a cmd and "fastboot flash boot boot.img" Can I delete the boot.img from the ROM zip file after I flashed it throught fastboot? This is where Im getting a little confused.
Click to expand...
Click to collapse
Yes, but you don't have to. It should work as long as you already flashed boot.img from fastboot
absolutelygrim said:
Yes, but you don't have to. It should work as long as you already flashed boot.img from fastboot
Click to expand...
Click to collapse
Thank you very much!!
Sent from my One X using xda app-developers app
Ok, im having some issues..
Non AT&T one XL (UK - Tmobile) with bootloader unlocked through htcdev, viper can install fine.
To get full root access, do i need to do anyhting else? Or is there a way to check that I have access?
Been researching, but 90% of stuff is about the AT&T version..
Currently elemental beta claims it installs in aroma but then bootloops whatever I do, and flash gui says it successfully flashed recoveries/kernals but then doesnt appear to really have done it.. Not sure if related, but it feels like my device is teling me it's doing things, but not really!
Cheers
Dacra said:
To get full root access, do i need to do anyhting else? Or is there a way to check that I have access?
Click to expand...
Click to collapse
Yup, custom ROMs by definition are rooted. Unless the dev screwed something up (rare).
Just open an app that requires root such as Titanium Backup, Adaway, etc. (download one, if needed). If you don't have root, the app will let you know. There are also a number of "root checker" apps on the Play Store.
redpoint73 said:
Yup, custom ROMs by definition are rooted. Unless the dev screwed something up (rare).
Just open an app that requires root such as Titanium Backup, Adaway, etc. (download one, if needed). If you don't have root, the app will let you know. There are also a number of "root checker" apps on the Play Store.
Click to expand...
Click to collapse
Well that works fine, adaway opens and is granted SU permission no problem.
Kernel installs and flash gui not working must be related to something else then, getting so frustrated trying to figure it out!
Some people have had the issue of kernels not installing in AROMA. But no idea why Flash Image GUI didn't work either.
You might try the other install methods mentioned in the Elemental thread (particular the method for hboot 1.14 or higher, if that applies to you): http://forum.xda-developers.com/showthread.php?t=2061577
redpoint73 said:
Some people have had the issue of kernels not installing in AROMA. But no idea why Flash Image GUI didn't work either.
You might try the other install methods mentioned in the Elemental thread (particular the method for hboot 1.14 or higher, if that applies to you): http://forum.xda-developers.com/showthread.php?t=2061577
Click to expand...
Click to collapse
I am hboot 1.14, but done everything in the elemental thread many times, kind of why i created this, as dont want to put people off that when it's working for most.
I've wiped everything in TWRP and started again completely from scratch, but still the same happens, driving me crazy!
S off is coming soon so when it comes you say f u to hboot 1.14! But if you want to get a recovery or something flashed I'd syggestt doing it the manual way... Fastboot flash recovery recovery.img
a box of kittens said:
S off is coming soon so when it comes you say f u to hboot 1.14! But if you want to get a recovery or something flashed I'd syggestt doing it the manual way... Fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I can manually flash recovery no problem with fastboot, it just says it's worked with gui but doesn't. Thought it might be related to elemental not working either.
Flash img gui doesnt work with viperxl
Sent from my VENOMized HoxL
area51avenger said:
Flash img gui doesnt work with viperxl
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
100 percent?
I decided to go back to stock when the new Jellybean finally rolled out.
So I wiped the phone. and put the factory boot.img back in and used the 4.0.4 RUU. (updated OTA after reboot)
Then I unlocked the Bootloader and put TWRP 2.5.0.0 on it.
Then I rebooted and downloaded SuperSU and Busybox from the Play store
I tried updated the Binary and it failed. So I flashed the UPDATE Super SU.zip
rebooted and was able to update the Binary. But everytime I try to update the busybox it says "it looks like the installation of BusyBox was not successful"
and when I delete Tmobile bloatware using TB (which promted and is granted Superuser permissions). The Phone will randomly reboot and when it restarts all the applications I just deleted are back.
What am I missing?
Like this:
usaff22 said:
Same as this problem, many people have asked a similar question before:
http://forum.xda-developers.com/showthread.php?t=2067495
Edit:
And these:
http://forum.xda-developers.com/showthread.php?p=39138367
http://forum.xda-developers.com/showthread.php?t=2190194
Click to expand...
Click to collapse
usaff22 said:
Like this:
Click to expand...
Click to collapse
Thanks.
I just didnt know what "keywords" to search for that.
Yesterday I rooted my nexus 5 following a guide from teamandroid website for android 4.4.2. Everything went okay and I was able to root it.
Then today I wanted to experiment with xposed framework but realized that I didn't have a recovery when I tried to make a backup. So first I tried installing TWRP through Goomanager but for some reason it would fail after the download. So I decided to install CWM touch trough fastboot. So I installed it and then did a backup. The problem came when I tried to exit. A message appeared and it said "ROM may flash stock recovery on boot. Fix?". I pressed yes, and then it told me something like "Root may have been lost. Try to get it back?" and pressed yes again. I rebooted and thats when supersu dissapear.
I panicked and tried to do the same procedure fro the guide again to get root. I repeated every single step but it wasn't succesful. I thought that maybe CWM was causing the problem so I installed TWRP trough fastboot and did the root process one more time. But again supersu just wouldn't appear back.
I really don't know what else to do. Everything in the stock ROM works fine but I just can't root my phone again. Does anyone know what I can do?
PS: Im not a native speaker.
just flash the latest supersu in your recovery, that is all. did you really search?
simms22 said:
just flash the latest supersu in your recovery, that is all. did you really search?
Click to expand...
Click to collapse
Thanks. It worked. I'm new to this so I wasn't sure what to do.
patrick.star said:
Thanks. It worked. I'm new to this so I wasn't sure what to do.
Click to expand...
Click to collapse
figured as much, rereading your post later, after first read. if you have any more questions, just ask.