Apparently my indecisiveness with unlocking my bootloader caught up with me.
I accepted the OTA when it was announced, but at the time had no root and had not unlocked my bootloader. As of the update, I cannot get temp root by any of the cookie-cutter methods (CleanTool, ZergRush, One Click, etc). I've tried to regain temp root post-OTA, but always fails at
Code:
adb remount
remount failed: Operation not permitted
The question is - does anyone have any ideas on how I can backup my apps/settings prior to unlocking my bootloader NOW? Bettery yet - is there a modified zergRush file that will work with the 2.01.601.11 firmware?
I'm thinking I may be SOL but it never hurts to ask.
You can use MyBackup to back all that up and you don't need root. Free version is a 30 day trial.
Sorry, it is likely HTC patched the security vulnerability. It is good that they did. Those exploit based roots are bad because they are based on security holes that could be exploited maliciously. My backup would probably work well.
Okay, I'll take a look at MyBackup. Interesting that they can do the backup w/o root, must admit I'm a little skeptical.
I've only used it since having root but I like it. I use TiBU as well and AppMonster so I'm covered for sure.
The only weird thing is that I had a MyBackup backup on my ext sd card. It then had problems so I had to recover the data and then copied it back onto my card once I reformatted it and now MyBackup says it can't find my backup.
Not a big deal since I restored a nand and don't need the messages I received since that nand, but just thought I'd report that since I just recommended the app.
Unlocked, restoring everything back now.
Does this happen to backup user settings (background, widgets, WiFi, bluetooth, etc)? Always such a pain reconnecting to all the wireless networks and getting it back to the way I like it to feel.
MyBackup did a great job. Got all my apps back, all app icons but no widgets. Most system settings were not saved (WiFi and bluetooth included), so I'll have to live with that. At least it made it a 1-2 hour restore instead of starting from scratch.
We still can perm root though right?
-Sent from my Droid 2-
I'm trying that now. Supposedly those who had root but wanted to update had to re-lock, update, unlock, re-root....so I'm guessing it works.
Root achieved.
Final procedure:
Backup anything you can/want (MyBackup works for this)
Unlock bootloader using HTCDev.com (this will wipe to factory defaults)
Restore any backups
Flash AmonRa Recovery using CleanFLASH
Reboot to recovery
Install SU through "Developer Menu"
Reboot
Open Superuser app -> Preferences -> SU Binary update
Verify SU privileges through an app (Titanium Backup, Root Explorer, etc)
spitzaf said:
Root achieved.
Final procedure:
Backup anything you can/want (MyBackup works for this)
Unlock bootloader using HTCDev.com (this will wipe to factory defaults)
Restore any backups
Flash AmonRa Recovery using CleanFLASH
Reboot to recovery
Install SU through "Developer Menu"
Reboot
Open Superuser app -> Preferences -> SU Binary update
Verify SU privileges through an app (Titanium Backup, Root Explorer, etc)
Click to expand...
Click to collapse
Step 1.5 : Do the update?
If you weren't updated, yes. In my case I was starting the whole process after receiving the update, and was trying to figure out how to get root without the exploit so I could keep my data and settings.
Sent from my ADR6425LVW using XDA App
Related
Hi,
I used to root the tablet successfully. But I found I did not have the root access grant this morning after consuming the power.
So I tried to root it again, but I got remount failed when executing NookandZergy.bat.
remount failed: Operation not permitted
Is there anyone could help me?
Thanks,
Kevin
its weird that you loosed root , first check if you are still on version 1.4.0, if so then try first using the unrooting script method and then root again, if not and you got the 1.4.1 upgrade silently then you will have restore stock(Go back to 1.4.0) and start from scratch, if you previously had a titanium backup of your apps then you good if not do it now and copy your titanium backup folder in to your pc.
Veronica
Thank you for your reply.
It was upgraded to 1.4.1 automatically.
Do you know how to go back to 1.4.0?
And how to prevent it upgrading?
Thanks,
Kevin
Kevin_Lu said:
Thank you for your reply.
It was upgraded to 1.4.1 automatically.
Do you know how to go back to 1.4.0?
And how to prevent it upgrading?
Thanks,
Kevin
Click to expand...
Click to collapse
Yes use this method to go back to stock, after that you probably want to use this to get 1.4.1 with root and android market (You must go back to stock to use this method is why i put it as second option) then use this method to block OTA, Indirect just released an update! as some users have reported that they are getting the upgrade with the 999 method. If you want to be even safer then freeze device manager but you will have issues with some B&N bloat apps i think, you can unfreeze anytime.
My prime came with 9.4.2.15.
Viper's tool work great. Rooted.
Installed OTA Rootkeeper from the market.
Let the OTA 9.4.2.21 update run.
Restored root with great success.
So those who are still locked(with warranty) should know that 9.4.2.21 update and rootkeeper seem to work.
Now... I have to give this tablet back to my girlfriend and I'm worried about loosing root with a wipe. How should I go about wiping or switching the main user account? Or should superuser and root be immune to wipe? Could I just download rootkeeper again and restore?
thanks in advance... long time android tinker-er but new to rootkeeper and locked bootloaders.
junglizste said:
My prime came with 9.4.2.15.
Viper's tool work great. Rooted.
Installed OTA Rootkeeper from the market.
Let the OTA 9.4.2.21 update run.
Restored root with great success.
So those who are still locked(with warranty) should know that 9.4.2.21 update and rootkeeper seem to work.
Now... I have to give this tablet back to my girlfriend and I'm worried about loosing root with a wipe. How should I go about wiping or switching the main user account? Or should superuser and root be immune to wipe? Could I just download rootkeeper again and restore?
thanks in advance... long time android tinker-er but new to rootkeeper and locked bootloaders.
Click to expand...
Click to collapse
I wish Rootkeeper would include the option of choosing where you put your backup..
Anyway, the wipe will eradicate any and all data on the Prime, including the SU backup that Rootkeeper creates. *Root stays intact, just not the backup.*
But, lucky for you, sparkym3 has graced us with a root app that you can keep ready to go in your ASUS WebStorage or DropBox or external mSD card, whatever you want.
But again, everything on the internal SD card will be lost when you wipe so be sure to back up your apps and their data (don't do system apps and data, restoring these usually just causes problems) to a location other than /sdcard along with any movies, music, and other personal files.
*EDIT:
Actually, no root methods currently work on .21, ASUS patched the exploit (badly I may add)
Factory reset should not touch root and you have root keeper so your good.
Blackwidowman said:
Factory reset should not touch root and you have root keeper so your good.
Click to expand...
Click to collapse
this is true as I had trouble trying to unroot on. 21 after using root keeper, as a factory data reset does not remove root
JSale said:
this is true as I had trouble trying to unroot on. 21 after using root keeper, as a factory data reset does not remove root
Click to expand...
Click to collapse
This is true. But it does remove the backup and all other files, so you need to be sure and back up as well as run Rootkeeper again after the wipe.
Why trying to unroot? You could try reverting to .15 either through an "emergency update" or with the .blob method, both of which are in my signature, then remove root and upgrade again to .21.
At this point however, you'll be at the mercy of time for the next root method; you won't be able to revert again I don't think since you won't have root.
I installed .21 and my root access was intact. I did not use OTA rootkeeper. Do I need to use it?
---
Sorry . I mixed up with HTC sensation upgrade. I used OTA rootkeeper to restore root.
I am about to install a custom rom to my stock Evo 3D that's on Hboot 1.5 and still on Gingerbread (yes I know I have been talking about it for a while now) and since pretty much any and all methods to do so would result in the memory being wiped, I wanted to backup my data and settings (namely all my settings for my apps and savedata for my games) before I did so.
Problem is, I am not aware of any method to do so that doesn't require root.
SuperOneClick is not supported for my phone, and tacoroot would only give me a shell, which I can't run Titanium Backup under.
Is there any way for me to backup my app data without root or gain a temporary root while still being able to use the phone itself so I can backup my data before I wipe it for a custom rom?
You could try this temp root method.
That post is in the Sensation forum but it says in the OP that it might work on the Evo 3D (untested).
If you try it, let us know how it goes.
Edit: Here's another temp root method for the Evo 3D. It may be the same thing as the link above just repackaged for the E3D. I've never used it myself and can't test it now since I'm currently running ICS and JB ROM's.
ramjet73
Lots of people say its supposed to work on the Evo3D, and there are even some batch files for it designed for the Evo3D, but when I tried to run the fre3vo file I kept getting "The exploit has failed" and the cursor remained as $ instead of #.
I tried three reboots now and nothing, there was also a method called a "perm-temp-root" but the download links are dead so I couldn't try it.
Nobody seems to maintain these anymore because they claim the method is outdated since we have S-OFF now and the last posts are from 2011.... problem is the whole reason I WANT to temp-root is to backup all of my settings and data so I can then use the S-OFF methods and flash a custom ROM to get a proper root, which I can't do without being forced to wipe my data first.
EDIT: Funny how as I was typing that you made an edit about the permtemproot. But yeah, that appears to be the same thing, just repackaged. And what drives me nuts about all the ones I tried with batch files is that they have zero error handling, they just assume the exploit worked and I get a ton of error mesages and apps like superuser that I can't use installed...
Sorry, I forgot to mention. The tacoroot method actually did work, but it only gives me root access in a CLI through ADB, I can't even use the terminal app with it, so its useless for performing a backup that way. All the other temproot methods didn't work.
Any ideas?
Cyber Akuma said:
Sorry, I forgot to mention. The tacoroot method actually did work, but it only gives me root access in a CLI through ADB, I can't even use the terminal app with it, so its useless for performing a backup that way. All the other temproot methods didn't work.
Any ideas?
Click to expand...
Click to collapse
Uhhh, I'm gonna have to say this is a lost cause, You just gotta lose the data, That's why we root, To be able to backup, Which is why most of us root before doing anything so we don't really lose anything like valuable save data, I don't even move a widget or an icon on a new phone until it's s-off and running the newest version of whatever lol.
I got this thing on release day, I couldn't just not use it for like a year until it was finally rooted.
Cyber Akuma said:
I got this thing on release day, I couldn't just not use it for like a year until it was finally rooted.
Click to expand...
Click to collapse
I didn't mean that in an offensive manner, But there's no way to not lose your data, Simply unlocking your bootloader erases your data.
So I have the HTC Evo 4G LTE and i upgraded to the 3.16 update. Ran QBKING77's root and unlock method and everything worked great, my question is, i was using the phone and ran my backup of titanium and after i did that it said that i lost root access, so i did the twrp recovery (2.4.1) and reset the phone to right after the unlock, i deleted the titanium backup i had and downloaded all my apps and settings again manually, If i use Root checker basic (one with a white background and hashtag with a green checkmark) it says i have root access, if i use Root Checker (with blue android) it says i do not, if i try to use titanium backup it says i do not have root, but every other root program i have works fine and says i have root access, ROM Toolbox Pro works just fine...how do i get Titanium Backup to work???
edit- this is the error i get with titanium backup: sorry, i could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again. This attempt was made using the "/system/xbin/su" command
What rom are you on?? Also you can try to update your su app from within the app or flash the su zip found here
http://forum.xda-developers.com/showthread.php?t=1538053
to see if it will resolve the issue. Also what version of titanium backup are you using? You should have the option to hit the problems button and download a reliable version of busy box from within the titanium backup app. If not and your running a stock rom then download busybox from the play store, install latest ver and see if it helps.
#Root-Hack_Mod*Always=LTE
laie1472 said:
What rom are you on?? Also you can try to update your su app from within the app or flash the su zip found here
http://forum.xda-developers.com/showthread.php?t=1538053
to see if it will resolve the issue. Also what version of titanium backup are you using?
#Root-Hack_Mod*Always=LTE
Click to expand...
Click to collapse
Using the stock ROM, didn't flash anything, Using TB Version 6.01, and SuperuserSU Pro.
tonyevo52 said:
Using the stock ROM, didn't flash anything, Using TB Version 6.01, and SuperuserSU Pro.
Click to expand...
Click to collapse
Have you checked if Super SU is granting titanium backup root access?
Sent from my EVO using xda premium
Download busybox from the play store, run the app and get latest ver of busy box, clear data on tb, reboot, and see if you still get the error. If so try flashing the su zip from the link. If that's a no go I'd recommend backing up your data via other apps, making a nand & flashing a stock rooted rom.
#Root-Hack_Mod*Always=LTE
alpha_mau5 said:
Have you checked if Super SU is granting titanium backup root access?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
It says it has access, says grant, but now the root checker basic i was using says i do not have access, restarting to see if i can change it, when i start SuperuserSU, it say i need to update the binaries and when i hit ok, it says installing and then operation failed and starts the program. As well, anything that has been granted access, a little black popup shell shows at the bottom of the screen real quick saying that super setcpu has been granted root access for the interactive shell?
I have tried two versions of busybox, busybox free which tells me there was a problem opening a shell with root access and then closes and i tried busybox installer which says device is rooted but when i hit install it says that instillation failed.
Im on the stock rom from the 3.16 update, everything i have read is that i would not be able to flash a rom because of compatibility issues and i the 3.16RUU is not available for download anywhere..and just FYI, still fairly new to rooting, but learning!
Thanks
Thanks 72, I flashed the SU Update 1.04 from your link and its working perfect now, good to go...take care. Hopefully it stays rooted!
tonyevo52 said:
Thanks 72, I flashed the SU Update 1.04 from your link and its working perfect now, good to go...take care. Hopefully it stays rooted!
Click to expand...
Click to collapse
No prob glad it worked out for you. Also have you read cap's post here
http://forum.xda-developers.com/showthread.php?t=2126626&page=4
Relating to flashing roms for those in your situation?? Check it out, definitely worth it.
#Root-Hack_Mod*Always=LTE
Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
I have the same problem. Initially, I thought that the sdcards were not mounted (for su root) but that wasn't the issue.
TB will currently backup VIRTUAL items (e.g. Accounts, WiFi access points) which have the TB logo next to it. It seems to fail for all other items.
gale2000 said:
Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
Click to expand...
Click to collapse
Same problem here. According to this post:
http://forum.xda-developers.com/showthread.php?t=2391363&page=7
the small app called sdfix could solve the problem. I haven't tried yet.
cr2069 said:
Same problem here. According to this post: http://forum.xda-developers.com/showthread.php?t=2391363&page=7 the small app called sdfix could solve the problem. I haven't tried yet.
Click to expand...
Click to collapse
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Anybody have luck with Helium?
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
iammudd said:
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Click to expand...
Click to collapse
Too bad, seems to be TB's problem. Waiting for any progress...The main reason I want rooting is to use TB, but it's not working...
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/ascend-mate2/orig-development/2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
iammudd said:
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
Click to expand...
Click to collapse
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
foltz61 said:
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Yes, fastboot boot TWRP_MT2-L03_RECOVERY.img allowed me to try it out first. If it had failed, then hopefully I would still have had the stock recovery. (After playing around with TWRP a bit, I DID eventually flash it.)
foltz61 said:
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
iammudd said:
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
Click to expand...
Click to collapse
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
Click to expand...
Click to collapse
Same problem and this also fixed it for me thanks
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
Click to expand...
Click to collapse
This workaround has been made obsolete. See next post:
I didn't know what the drawbacks are to using this folder so I was initially reluctant but I've given up and went down this path as well. However, I've reduced some permissions and here's what appears to be working for me:
Use ES Explorer to create the new folder and change its permissions to rwx for group and others. (I didn't need to change owners for any of the folders.)
Use ES Explorer to TEMPORARILY add read-only permission to /data for OTHERS.
Change TiBu backup folder location by manually navigating to the new folder.
Once the new folder has been selected, I restore /data to its original permissions. (The read permission was only needed temporarily for TiBu to find the new folder.)
Copying the files back to my PC, I can see that the zip files for the apks appear to have "reasonable" apk sizes (i.e. not zero-length as before).
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
kemonine96 said:
In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Click to expand...
Click to collapse
Thanks, this appears to have done the trick. It was very baffling when TiBu would work for some tasks but not others. Glad you stumbled onto this thread.
And another follow up for those using Helium or looking for an "adb backup" based solution
This device does not appear to include the full adb backup stack. From some limited testing tonight the pop-up prompt when running "adb backup' or using Helium Backup does not produce prompt on the device so it just fails. This is a known problem on some devices and it's too bad Huawei decided this wasn't a necessary inclusion.
kemonine96 said:
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
Click to expand...
Click to collapse
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
nrfitchett4 said:
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
Click to expand...
Click to collapse
Were you able to get adb backup to work at all? I never was able to get it to work.
I solved my titanium backup issues by going into SuperSU, then settings for SuperSU, and unchecked the mount namespace seperation box, then reboot
kemonine96 said:
Were you able to get adb backup to work at all? I never was able to get it to work.
Click to expand...
Click to collapse
It worked just fine for me. Used it to backup kids unrooted phones. That's been a couple years though.