Related
Hello xda, in accordance with the signup video I have scoured the earth looking for an answer. However I'm not sure how much necro posting is frowned upon here so I thought it would be safer to just start a new thread.
I have an HTC Desire HD from Telus(for use on the Rogers network). I am in the process of rooting it but have encountered a problem. I can gain temporary root on the terminal emulator(Because the $ turns to #) however when attempting to run clockwork flash clockworkmod recovery I get the error "An error occurred while attempting to run privileged commands!"
I get the same error when attempting the "Fix Permissions" so I'm currently at a loss of what to do.
I have the ninja superuser icon in the apps menu however when I open it the screen is blank. I am unsure if this is how it is supposed to be or not. I have seen several references to a permission box that pops up during some of the steps but I haven't seen that at all.
I've tried four separate methods, the last of which coming from this thread http://forum.xda-developers.com/showthread.php?t=954997
I am currently at step B.d which involves running the S-OFF tool and Easy Radio OFF tool. But still clockwork will not flash a backup, and when I restart the phone I can not get super user to work on the terminal (ie by typing su) and must use the rage method to regain temporary root.
Also, I don't know if this is related or not, but when I restart the phone and attempt to boot in recovery mode, the volume buttons don't allow me to select other options, and instead the phone just forces me to reboot normally.
Some more facts:
model HTC Desire HD A9191
Build # 1.32.405.6
Android 2.2
Anymore info I'm probably forgetting just ask away!
So my question is: Can anyone identify what the issue is?
Thanks much for taking the time to read my question.
Does visionary not work for you?
I've seen that alot of success has been gained by doing temp root and perm root through it?
It does sound like the rage method might not be working for you from what I can tell..
I do want to check all the steps you followed before where fine?
Sent from outer space on my DHD running beatmod gingersense v1.3
Visionary was how I rooted mine. Worth a try if you havent tried it: http://android.modaco.com/content/software/320350/19-nov-r14-visionary-one-click-root/
Thanks for the visionary suggestion, but Visionary still isn't working :/
Has visionary been tested with the Telus Desire? I heard there was a difference. What happens when I attempt to temproot is it moves to a blank screen then goes back to the menu.
When I used visionary on 1.32 it did not always work first try ... generally always worked after 2 runs. then used it to perm root
It works. You do not have Telus software in your phone anymore.
Sent from my Desire HD using Tapatalk
Try my method (I made it because the methods I found for my Telus desire HD were flaky at best and only got temproots from it.)
Since you already flashed to 1.32 start at step 2
If you want to go gingerbread, dl the 2.36.405 ruu and use that and your pc to put 2.3.3 on it (dont worry, it works fine, i was using it since it came out and built a rom based off that, kingdom, and pyramid roms for my own sense 3 rom) and use the gingerbreak method.
http://driphter.com/index.php?topic=3867.0
Still haven't managed to get root. JSLEnterprises my antivirus won't let me download your file :/
I'm at a loss for what to do.
lemonpartyz said:
Still haven't managed to get root. JSLEnterprises my antivirus won't let me download your file :/
I'm at a loss for what to do.
Click to expand...
Click to collapse
Disable your Antivirus (Avast say's its malicious), Norton or F-Prot says its clean.
and Internet Explorer 9 says its not trustworthy (because there's .bat files in the zip), Firefox says its fine.
There is no malicious code in the zip, you can edit each individual batch file in the Resource folder to see the code. Its very simple and basic.
I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Edit: I went into the resource folder and then followed the steps from there and everything worked, except I still don't have the # symbol in terminal (even when entering "su") and ROM manager still gives me the same error.
lemonpartyz said:
I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Click to expand...
Click to collapse
go into the resource folder, edit the visionary install batch in notepad, delete the "cls" line, save and exit
rerun it with the phone attached. See if it truly installed successfully.
lemonpartyz said:
I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Edit: I went into the resource folder and then followed the steps from there and everything worked, except I still don't have the # symbol in terminal (even when entering "su") and ROM manager still gives me the same error.
Click to expand...
Click to collapse
you dont need to use the termial in my method.
Once visionary is installed, and you run it, and everything is done exactly whats described in my 9 easy steps thread (along with outcomes along the way), then you should be perm rooted, with s-off and eng-off with supercid.
I managed to install visionary with your method, however when running Eng-S I encountered the error "Bootloader corrupt, DO NOT REBOOT! Seek help from XDA!"
Help?
Edit: Followed the advice here http://forum.xda-developers.com/showthread.php?p=14936635 and s-off worked properly this time. Hopefully my DHD won't brick on reboot. Could super user be the problem? it never asks me for permissions or anything, all I have is an icon and a blank screen when i open the app.
Edit2: Rom manager took three attempts to install correctly. Still the same result "An error occurred while attempting to run privileged commands!"
FML
lemonpartyz said:
I managed to install visionary with your method, however when running Eng-S I encountered the error "Bootloader corrupt, DO NOT REBOOT! Seek help from XDA!"
Help?
Edit: Followed the advice here http://forum.xda-developers.com/showthread.php?p=14936635 and s-off worked properly this time. Hopefully my DHD won't brick on reboot. Could super user be the problem? it never asks me for permissions or anything, all I have is an icon and a blank screen when i open the app.
Edit2: Rom manager took three attempts to install correctly. Still the same result "An error occurred while attempting to run privileged commands!"
FML
Click to expand...
Click to collapse
looks like the superuser application isnt running properly.
I would use the 1.32 ruu (not the pd98img.zip off the sd) and then from a fresh install (without resoring any data other than google account to visit the market)
run through the visionary, s-off tool, eng-off tool, and then reboot again, then install rom manager from the market, run it, it should ask you for permission and may hang for a second, and then say you have about 5 seconds to allow root permissions.
Then install rom's away. if you're not into making seperate rom specific app folders on your sd card, google JSL Er3BuS. its a sense 3 rom without the extra scripts.
How do I install the 1.32 RUU if I can't install it from the SD card?
Thanks!
lemonpartyz said:
How do I install the 1.32 RUU if I can't install it from the SD card?
Thanks!
Click to expand...
Click to collapse
It is very easy mate,
1. Download the RUU of your choice from http://shipped-roms.com/index.php?category=android&model=Ace
2. Put your phone in charge mode only with USB debug on.
3. Make sure you have HTC Sync installed on your PC, and close HTC Sync application from your system bar in windows (make sure that HTC Sync is not running as all you need is the driver)
4. Right click on the RUU file and select "Run as Administrator"
5. Connect your DHD by the USB cable to your PC.
6. Click some boxed and "next"s.
7. Waiting!
8. Profit!
I tried following the steps here http://forum.xda-developers.com/showthread.php?t=841890
But got the error "ERROR [120]: Low MAIN BATTERY POWER. When the battery is above 30%.
This is getting ridiculous lol
I'm sorry I'm such a bother.
naailalzuhir said:
It is very easy mate,
1. Download the RUU of your choice from http://shipped-roms.com/index.php?category=android&model=Ace
2. Put your phone in charge mode only with USB debug on.
3. Make sure you have HTC Sync installed on your PC, and close HTC Sync application from your system bar in windows (make sure that HTC Sync is not running as all you need is the driver)
4. Right click on the RUU file and select "Run as Administrator"
5. Connect your DHD by the USB cable to your PC.
6. Click some boxed and "next"s.
7. Waiting!
8. Profit!
Click to expand...
Click to collapse
Tried this, now the update process has taken 45 minutes.
Well, it took 5 hours to finish, but finish it finally did. Rom manager installed no problem, flashed no problem and I am in the process of installing cryogen. Thanks everyone for their help and kind words.
Fingers crossed cryogen works.
I'm going away for the weekend, but when I come back I'll update this thread with the full details of what went down so hopefully someone will be helped by my many many hours spent raging.
-Lemonpartyz
lemonpartyz said:
Well, it took 5 hours to finish, but finish it finally did. Rom manager installed no problem, flashed no problem and I am in the process of installing cryogen. Thanks everyone for their help.
Click to expand...
Click to collapse
Glad its sorted for you , and hoping it status that way...enjoy your custom roms setting your phone free
Look forward to your post letting us know how its going.
Sent from outer space on my DHD running beatmod gingersense v1.3
This should work for any and all a100 Honeycomb builds, you'll need to install an app from the market called terminal emulator. Also, you'll need a file manager like Astro to unzip the file.
This mod should root your tab in a matter of seconds after the script file is launched. I've tested this on my tab from a clean build and it works like a champ.
Here we go!
- Install the following apps from the market:
Terminal Emulator
https://market.android.com/details?id=jackpal.androidterm&hl=en&rdid=jackpal.androidterm&rdot=1
Astro File Manager
https://market.android.com/details?id=com.metago.astro&hl=en
- Download the attached file from this post.
- Extract and put both the root.sh and su in /mnt/sdcard from the root.zip file.
(Using Astro, find the root.zip file it might be in /mnt/sdcard/Downloads or could be else where if your not using the website to view XDA. Copy it from where ever it's at and paste it in /mnt/sdcard. Press your finger on the zip file and tap Extract when the menu pops up. Tap "Extract to This Directory".)
- Next, open terminal emulator and copy / paste the following:
sh /mnt/sdcard/root.sh
Text will fly by, the script will automatically copy the su binary and install it to the proper location.
Once the script finishes running, be sure to install superuser from the market:
Very Important, if you skip this you won't be "officially rooted yet"!!!
https://market.android.com/details?id=com.noshufou.android.su
Open the superuser app once it's installed, click on the wrench in the upper right corner, scroll to the bottom and find "Su binary v... Tap to check for updates" and tap that link. It should bring you to an update screen, click the button at the bottom to update!
Once you have done the above, then install busybox, Titanium, etc.. if needed.
Thanks goes to abliss for origionally coming up with the root commands!
This mod really just automates his work.
permission denied every step of the way. Used both script manager and terminal
ok terminal manager is out, I didn't realize that doing a hard reset wouldn't wipe the /system/xbin directory completely so technically busybox tools were still installed and sh wouldn't normally be there. I'll see if there's another way..
this method work for any build? and if so, is there any problem during the process that could "kill" my a100 or it's safe?
This method should, yes and it's safe.. It's actually more safe (if that's possible) than the method origionally posted in the dev section since there really isn't any room for user error.
Sent from my MB860 using XDA App
Ill give the new method a go around tomorrow and report back for you.
I wasn't expecting it to anyway, but I figured I'd let you know this doesn't work on the A101.
Hoping someone can find a working root method for this model.
Sorry to hear about the a101, that thing sounds like a tough nut to crack!
Sent from my MB860 using XDA App
This working for me i manage to root my a100
It works and its so simple
Thank you so much for this! It was so easy. Though the only problem I had was with the terminal emulator, no fualt of the Dev, but it might help someone. When I was trying to write in the line of code I kept getting errors because I couldnt get the keyboard to write lower case. So copy and paste if your a noon like me to get it through the terminal.
Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...
mvan4310 said:
Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...
Click to expand...
Click to collapse
You sure you don´t have an a101? what build number are you running?
A100_2.007.04_COM_GEN1
Most definitely an A100...
mvan4310 said:
A100_2.007.04_COM_GEN1
Most definitely an A100...
Click to expand...
Click to collapse
I have no idea then.. the only thing I could say is to try and restore from a "Full" rom, like Acer_A100_1.014.08_COM_GEN1 and try to root it before doing anything else. It wouldn't hurt to try anyway and the worst that could happen is that you'd have to restore all your apps and stuff. If we can ever get this thing to run cwm and a different kernel, you'll definitely be needing root.
Works great!
Thanks so much for the script and instructions. Im enjoying my rooted tab yay!
mvan4310 said:
Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...
Click to expand...
Click to collapse
Did you check the boxes for USB Debugging and Unknown sources just in case?? (in Settings > development)
I checked them both. Root Checker shows I have root, but other apps cant get root access, and SuperUser cant update because of this issue... I dont know what the hell to do because this has me stuck atm... Im gonna flash back to 1.018 and see if that helps, probably not, but it wont hurt to check.
EDIT:
I reverted back and got root. It seems to be the newest update that stopped it. Im updating back up again to see if I retain root. What a pain...
Edit 2:
Yep, Im rooted now. It unrooted me when updating, ran the script you provided and its working now. Dont know why it didnt take before reverting back, but works wonderfully now. Now that Im rooted, let me know what I can do and peek around at to help out here.
Has anyone tried that on an A500?
A500 has its own rooting methods. You can find info about the A500 here
http://forum.xda-developers.com/forumdisplay.php?f=1136
Thanks alot crossix. Worked like a charm.
Sent from my A100 using Tapatalk
I was in the process of replacing framework-res.apk and missed the step of changing the permissions before replacing it. I found several threads on how to unbrick the phone by flashing a new ROM but I was hoping I can somehow fix the permissions on the framework file and be done. I installed adb and I already had the LG USB drivers installed but when I run adb devices it doesn't list anything. Windows 7 shows "LG AndroidNet Phone" and a removable disk under "Safely Remove Hardware" so I think I have the right drivers.
Is there hope that I can fix the file permissions?
BTW, I'm a newb so I may be missing something. And also scared of having to flash a ROM
I need help.
do you have CWM in the phone ? if so boot into that and run adb devices and see if it finds it their
No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.
gabcon73 said:
No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.
Click to expand...
Click to collapse
unless your phone will boot normaly to the home screen or you have CWM on it you will haveto flash the koren rom theirs no way to get it into recovery that i know of ... have you tryed a factory reset ?
I replied to you at another thread, so I'll repeat here.
What you need to do is re-root while it's looping. It might take you 100 tries before it succeed , but eventually it should succeed.
After that you can try fix the permissions, but if the new .apk file is not copied successfully first time it might get you in boot loop again, so I'd recommend at that point push the .apk again and then change the permissions.
I found that zergrush dated 2011-10-21 has more chances to succeed, because it has more retries before it gives up, the new version tries only few times and gives up too quickly.
I've attached the root I was using with 3 versions of zergrush.
Open CMD window and execute root.bat, let it copy all needed files to the phone. If it fails, try execute loop.bat, it will just execute zergrush indefinitely , so you can go do other stuff. You can check if root succeeded by opening another CMD window and type: adb shell
then, if it shows sign "$" type su, if it shows "#" you are good to go.
P.S.
This method only works with AT$T stock rom, if you are on LU6200 you are probably out of luck, as their root requires wifi and user interaction...
Having CWM is very handy in such situations, not only because you can restore backups, but because you'll have root access.
Thanks [email protected], I'll give it a try. And yes, I have the stock ROM.
I'm having problems downloading root.zip, I've tried two computers and different browsers, it only downloads 554 bytes.
Yeah, for some reason it was downloading 404 page...
I reuploaded it.
I let the loop.bat run overnight without success so I decided to call AT&T and have it replaced under warranty. The new phone arrived today and I've been busy reinstalling and reconfiguring. I may install CWM just so I can easily recover from a backup in case I do some other stupid thing to the phone.
Thanks guys
Okay, ive been doing my research, and I lasted aprox. 4-5 days and its sadly to know but this phone (HTC Evo Design 4G / Kingdom / Hero S) doesnt have that much of fame. But I was crazy trying and trying alot of methods trying to root my phone, but just couldnt. I was about to give up, until I found a Guide, and made it possible for me to root the phone, so I decided to share this guide to you guys, to who ever has a HTC Evo Design 4G / Kingdom / Hero S. Credits go to LOLINTERNET who wrote this guide. :good:
Ok, here we go. :laugh:
In order to root your Evo Design you'll need to unlock your bootloader, flash recovery, flash su binary, and install superuser and busybox. In this guide I will try to explain these steps as simply as I can. My goal is for it to be thorough enough that anyone that reads it can root their phone and enjoy the full benefits of this nifty little phone.
First and foremost, you will need to install the Java SE Development Kit. You won't use this directly in any way, but you need it in order to install the Android SDK.
Click Here To Download SDK
After installing the Java JDK, you will have to install the Android SDK which contains two tools that are essential to gaining root. They are adb (Android Debug Bridge) and fastboot. These tools are used to send files to your phone from a Windows command prompt. You will need these tools to unlock your bootloader and flash recovery.
Click Here to Download Android SDK
Instructions on installing the SDK
How to add packages to the SDK
Once you have the Java JDK and the Android SDK installed you will need to install the proper drivers for your phone. This one is pretty straightforward and necessary for your phone to be recognized while plugged into your computer. After you have the HTC drivers installed you can begin the fun parts, but first you will need a few things. :good:
HTC Drivers CREDITS TO: CNexus
You will need a recovery.img. 2fast4u88's unofficial ClockWorkMod Recovery version 5.0.2.7 and 5.0.2.8 are the only two recoveries I have used since I got my Evo Design. Many thanks to him for putting in so much work to get this device where it is today.
Download Recovery
Also, you'll need su binary version 3.0.3.2 efghi. This is the actual file that will root your device. It is a flashable .zip file that you save to your sdcard and flash in recovery. You'll be amazed at how easy this step is.
Download for su binary version 3.0.3.2 efghi
Download for su binary version 3.0.7 efghi
3.0.3.2 binary is for Gingerbread and 3.0.7 is for ICS
The superuser app is like the control center for apps that request root permissions after you're finally rooted. You will need to install this app and then Busybox, both of which can be found in the Google Play Store. After installing the Busybox app you will need to actually install busybox. The app itself is basically an installer for Linux applets that are required by root apps such as Titanium Backup and Root Explorer among many others.
Now that you have a basic overview of what it is you will be doing and the files need to do it, the only thing left is to actually perform these steps and root your device. So, lets do this!
1. Unlock your bootloader at htcdev.com. You will need to sign up and you will be warned that unlocking your bootloader will void your warranty. Once you've followed all instructions at the website an unlock token will be emailed to you. DO NOT DELETE THIS FILE. You can place it in the platform tools folder of the Android SDK and use fastboot in command prompt to relock and unlock your bootloader whenever you like. Also, anytime you unlock your bootloader all data will be wiped so be sure you sync all your contacts and backup other information first before performing this step.
2. After unlocking your bootloader you will need to flash a recovery.img. The manual way to flash recovery is to place the downloaded recovery.img for 2fast4u88's unofficial ClockWorkMod recovery port of version 5.0.2.7 in the platform-tools folder of the Android SDK. Power down your phone but be sure that Fast Boot in Power under the settings menu is unchecked or it will just reboot normally instead of into bootloader (also called hboot) like you want. After it's been powered down for a minute or two, press and hold Volume down then press and hold the power button. When the white HTC splash screen appears you can let go. Scroll down with the volume down button and select fastboot by pressing power. Plug your phone into your computer and open a command prompt, then run these commands without quotations.
"cd C:\android\platform-tools" (This is where adb and fastboot live. It may be different for you depending on where you installed the SDK. I always suggest installing it to the root of your C: drive.)
"fastboot flash recovery recovery.img"
Should only take a few seconds, then you have yourself a recovery partition and you can proceed to the next step after rebooting. Yay!
3. Next, we're going to flash the su binary in recovery. First, you'll need to place it on your sdcard. Doesn't matter where exactly just as long as you can find it. I would suggest the root of your sd just to make things easier on yourself. After you have the su binary zip saved to your sdcard power off your phone and boot into hboot. Now, I can't remember which, but either hboot or fastboot will have an option to boot into Recovery. Once you're booted into recovery, select "install zip from sdcard," then "choose zip from sdcard." Scroll down and find the su binary then select it. Pressing the Up Vol button will take you directly to the end if you don't want to scroll all the way through. After selecting the su binary zip select "yes" to flash. It's a small file, so it won't take long. When it's done select "reboot to system" and we'll move on to the next step because you just rooted your phone.
4. But, you're not done yet. You need to install the superuser app and the busybox app in that order. This is the easy part because both apps are free in the Play Store. Install Superuser, then Busybox. You shouldn't have to interact with the Superuser app, but if you want to set an automatic response to apps that request root you can open it and go to Preferences. Scroll down and you should see a few options. I have mine set to automatically grant su permission to apps that request it because I have no reason not to lol. I also unchecked the option to receive a notification every time an app is granted root permission because that junk just gets annoying. Next, after you install the Busybox app, you'll need to actually install Busybox. The app is merely an installer for the actual Busybox applets that govern root apps. The app should open automatically after you install it. You should see it in your notification bar. Open it up and follow the prompts. When you're done, reboot your phone.
5. Check If you have rooted your phone successfully, download Root Checker on Play Store.
6. Congratulations! You should now have a rooted Evo Design 4G. Enjoy. I hope this guide is both complete and comprehensive enough that everyone can enjoy the benefits of having a rooted device, but if I've missed something or if you have any questions whatsoever, please post them here and I will do my best to answer them in a timely manner. I hope you enjoy rooting your device, but please be careful. You now have administrator privileges, so use them wisely. I would highly suggest installing Quick Boot from the Play Store so that you can boot into recovery easily without having to go through hboot. I would also suggest using your newly installed app that requires root access to boot into recovery and make a backup. If anything should ever happen to your phone's system and data you will have a backup and can restore it to that state. Again, I hope you enjoy. I apologize for this being such a lengthy guide, but hopefully you understand the wonderful world of Android a little better for having read it. :good:
*EXTRA* 7. I recommend doing a backup via recovery of your phone, because this phone doesnt seem to have any roms or any stock roms etc, so i recommend making a backup, but dont worry, ill try to make a backup ROM so there could be one on the internet, because I searched and could find one! :s
Great post Julio. I saw this post somewhere else but I could not remember were.
Will this work on a Freedompop version of this phone?
THe evo design 4g FreedomPop version IS supposed to be already rooted. But when I try to load SU from the app store it says su binaries are out of date. Will flashing these binaries do the trick for it to accept it?
If it is rooted, do you think all I need to do is update that damned su binaries file?
Hope you still visit this site because those are my first questions towards doing some goodness towards my Evo!
Hope to catch you later.
maikalwolf said:
Great post Juan. I saw this post somewere else but I could not remember were.
Will this work on a Freedompop version of this phone?
THe evo design 4g FreedomPop version IS supposed to be already rooted. But when I try to load SU from the app store it says su binaries are out of date. Will flashing these binaries do the trick for it to accept it?
If it is rooted, do you think all I need to do is update that damned su binaries file?
Hope you still visit this site because those are my first questions towards doing some goodness towards my Evo!
Hope to catch you later.
Click to expand...
Click to collapse
Lmao, its Julio! :laugh: and yea I think that will do it!! Try flashing the su binary I have up in the post! Do you have CWM Recovery?
re you follow up question
julio626 said:
Lmao, its Julio! :laugh: and yea I think that will do it!! Try flashing the su binary I have up in the post! Do you have CWM Recovery?
Click to expand...
Click to collapse
Yes, the phone was rooted and just needed the new binaries, which I promptly fixed. I have also put a link to your page to the instruction for others to use.
maikalwolf said:
Yes, the phone was rooted and just needed the new binaries, which I promptly fixed. I have also put a link to your page to the instruction for others to use.
Click to expand...
Click to collapse
Thanks man!
Gracias Julio
It was quite tedious to be honest. But reading your guide and this one how-to-unlock-the-bootloader-of-any-htc-device en cultofandroid I finally was able to root my phone. Thank you so much!
Amazing
This is the best guide I have ever found. It was fluid and easy to understand for me. Just went from my JB IPhone 5 (cellular happened to break). now i have this phone lol (but its so slow and useless I decided to root and it was an unbelievable pain.. nothing worked). Then I found your guide which is fantastic, completely like no other. I am very impressed with it and just wanted to say THANK YOU!!!!!! :good:
So Close PLEASE can you help.
I followed this guide about a year ago & got to the image you see linked h**p://i.imgur.com/zfle9n7.jpg To be blunt I do not recall where I left off in the rooting process except to say I'm dead ended. Where did my efforts go wrong and what do I need to do in order to finally get this rooted? Also please tell me what bearing info in this thread: h**p://forums.androidcentral.com/htc-evo-design-4g/142434-s-off-s.html may have on my results. THANK YOU
OK so first of all, if this is the wrong place for this I'm sorry, it's quite late for me and I've been researching how to fix this for about two days and running up with nothing.
I recently upgraded to a Pixel 2XL, loving the device but unfortunately a couple of my apps save data into the data/data part of phone. The only way to then move that over and preserve the data is to use something like adb backup and restore. The backup seems to work fine, but so far every time I try to use restore on my pixel 2xl it 'ends' without actually adding the missing app data across.
I've tried using usb 2 and 3, no difference. I've made sure the usb debugging is on and that my phone is unlocked. I also made sure to try using the commands through both cmd and powershell and that both were in admin mode. I've also tried looking into other options like a friend suggested using es file explorer manager to change the download location, but I wasn't able to puzzle out a way to make something that was in data/data save elsewhere.
My phone isn't rooted, and I'd rather not go that far if I can help it. Any advice or ideas?
Aahhh,"...your phone isn't rooted..."that's probably it/key. I'm unsure whether any kind of "restore" works without root access -- backup of course works because that simply involves "copying" and "storing" files (essentially the basic process of backing up) and, as the system needs to be able to read and access the data, you pretty much have the "read access" to it. Restore on the otherhand, for those who are unaware, are essentially "copying" those stored files and "overwriting" the existing files -- which require "write access". The process of "rooting" is to acquire "root access" which allows both "read/write access" (therefore: "r/w access"). *again, for those who are unaware.
Sorry for just blabbering on about that, I guess I got carried away. In any case, basically (all in all, the reason why I blabbered on) I don't think you're going to go far without root access -- or "rooting" as you say -- but there is one thing I can suggest. When using adb, try running this command first before running any other adb command (i.e. restore):
Code:
adb root
It might just give you enough of that "root access" I was blathering about...
Also, among the all the things you made sure to do and include you made sure of, one thing you didn't mention is making sure you have the most up to date platform-tools (r28.0.1 *at least last I personally saw a few weeks ago).
Good luck to you, hope I made these things somewhat understandable, and hope this helped as well....
Thank you for the suggestions, tried it but no dice sadly. I kinda am hairy on rooting it too as I just got the phone and it's been a long time since I've done android dev work. If you have any other ideas I'd be welcome to hearing them but again thanks for trying.
simplepinoi177 said:
Aahhh,"...your phone isn't rooted..."that's probably it/key. I'm unsure whether any kind of "restore" works without root access -- backup of course works because that simply involves "copying" and "storing" files (essentially the basic process of backing up) and, as the system needs to be able to read and access the data, you pretty much have the "read access" to it. Restore on the otherhand, for those who are unaware, are essentially "copying" those stored files and "overwriting" the existing files -- which require "write access". The process of "rooting" is to acquire "root access" which allows both "read/write access" (therefore: "r/w access"). *again, for those who are unaware.
Sorry for just blabbering on about that, I guess I got carried away. In any case, basically (all in all, the reason why I blabbered on) I don't think you're going to go far without root access -- or "rooting" as you say -- but there is one thing I can suggest. When using adb, try running this command first before running any other adb command (i.e. restore):
Code:
adb root
It might just give you enough of that "root access" I was blathering about...
Also, among the all the things you made sure to do and include you made sure of, one thing you didn't mention is making sure you have the most up to date platform-tools (r28.0.1 *at least last I personally saw a few weeks ago).
Good luck to you, hope I made these things somewhat understandable, and hope this helped as well....
Click to expand...
Click to collapse
Where your bootloader is apparently unlocked, download a TWRP recovery image to the directory fastboot is in and boot it using the fastboot command "fastboot boot twrp.img". From there, take a nandroid backup of your device. Restoring is done in the same fashion. AND, since TWRP is memory resident when booting it this way, the stock recovery remains untouched.
Strephon Alkhalikoi said:
Where your bootloader is apparently unlocked, download a TWRP recovery image to the directory fastboot is in and boot it using the fastboot command "fastboot boot twrp.img". From there, take a nandroid backup of your device. Restoring is done in the same fashion. AND, since TWRP is memory resident when booting it this way, the stock recovery remains untouched.
Click to expand...
Click to collapse
Great idea! And that's why veterans and those with experience are the best to go to...!
OK so first, thank you so much for all the advice. I've taken awhile to get back to you because this took some time to parse. I'm admittedly kind of a novice at this. So I've used the instructions here https://www.xda-developers.com/how-to-install-twrp/ to try and install twrp. I think I did it right, had the zip contents and img file in the same directory that adb is in, then ran the command...and this is what I got back.
N:\platform-tools>fastboot flash recovery twrp-3.2.3-1-taimen.img
Sending 'recovery' (40960 KB) OKAY [ 1.203s]
Writing 'recovery' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.219s
as the 'fastboot reboot' command appeared to bring me right back to normal operating for the phone I'm guessing the failed stopped me with that 'flashing not allowed in lock state' there. Am I missing a step?
close, but not exactly right...
you got the downloading platform tools right, and putting the necessary files in that same folder that fastboot.exe resides in also right (you wouldn't believe how many novices actually make the mistake of not doing this)...
but you don't ever (underlined and emphasized not really for you AshtonHunter, but for any who are under the wrong impression; it's caused endless headaches and has even been complained by developers on Twitter...) "fastboot flash" TWRP with Pixels (any; and AFAIK any a/b slotted devices). You boot the twrp .img file. Also, for those who do not know and for future reference, there is no "recovery" for fastboot to "flash" to on Pixels (any), as there no longer is a separate partition for recovery; recovery resides in the boot partition. All in all, the command should be exactly this:
Code:
fastboot boot twrp-3.2.3-1-taimen.img
Immediately afterwards, you'll see your Pixel 2 XL restart and load up TWRP...
Good luck to you and hope this helps...
Hey everyone. So I tried this but it also didn't work. Same error 'cannot in locked state' when trying to run the command. I do notice there's a green 'locked' on my phone when it's in the screen after the 'adb reboot bootloader' command. Any ideas?
simplepinoi177 said:
close, but not exactly right...
you got the downloading platform tools right, and putting the necessary files in that same folder that fastboot.exe resides in also right (you wouldn't believe how many novices actually make the mistake of not doing this)...
but you don't ever (underlined and emphasized not really for you AshtonHunter, but for any who are under the wrong impression; it's caused endless headaches and has even been complained by developers on Twitter...) "fastboot flash" TWRP with Pixels (any; and AFAIK any a/b slotted devices). You boot the twrp .img file. Also, for those who do not know and for future reference, there is no "recovery" for fastboot to "flash" to on Pixels (any), as there no longer is a separate partition for recovery; recovery resides in the boot partition. All in all, the command should be exactly this:
Code:
fastboot boot twrp-3.2.3-1-taimen.img
Immediately afterwards, you'll see your Pixel 2 XL restart and load up TWRP...
Good luck to you and hope this helps...
Click to expand...
Click to collapse
AshtonHunter said:
OK so first of all,
if this is the wrong place for this I'm sorry, it's quite late for me and I've been researching how to fix this for about two days and running up with nothing.
I recently upgraded to a Pixel 2XL, loving the device but unfortunately a couple of my apps save data into the data/data part of phone. The only way to then move that over and preserve the data is to use something like adb backup and restore. The backup seems to work fine, but so far every time I try to use restore on my pixel 2xl it 'ends' without actually adding the missing app data across.
I've tried using usb 2 and 3, no difference.
I've made sure the usb debugging is on and that my phone is unlocked. I also made sure to try using the commands through both cmd and powershell and that both were in admin mode. I've also tried
looking into other options like a friend suggested using es file explorer manager to change the download location, but I wasn't able to puzzle out a way to make something that was in data/data save elsewhere.
My phone isn't rooted, and I'd rather not go that far if I can help it. Any advice or ideas?
Click to expand...
Click to collapse
AshtonHunter said:
Hey everyone. So I tried this but it also didn't work. Same error 'cannot in locked state' when trying to run the command. I do notice there's a green 'locked' on my phone when it's in the screen after the 'adb reboot bootloader' command. Any ideas?
Click to expand...
Click to collapse
You would only get this error if your device isn't "unlocked"... I/we were all under the impression that (which is why I quoted) your device is "unlocked"... So maybe some clarification is in order...
There are two types of "unlocking" that can be attributed to the device; 1) your device can be "locked" to a carrier or global region, and it can be "unlocked" so the device can be used on any network anywhere, and 2) all Pixel's (and all smartphones AFAIK) have their bootloader in a locked state, and in order to do any kind of "rooting" or data restore/recovery or modification down to the system level you have to "unlock" the bootloader or have it in an "unlocked" state.
*BEWARE! Before running these commands, please note that running critical will erase/wipe EVERYTHING -- I am pretty sure running both will actually cause this to happen.
Considering all of this, when you said your "...phone is unlocked", you are speaking in terms of #2 I listed above, correct? Basically, you have run the command -- while in Bootloader Mode -- "fastboot flashing unlock" & (just as important, imho) "fastboot flashing unlock_critical", right? Because, if you haven't done these, then your device was never "unlocked" (in the sense that most relates to us and what you are intending) as well as without having one these commands, you had no chance at restoring your /data folder or partition "data" (pun not intended).
After clearing any misunderstanding and/or issues of these type, we might be able to better help after that point...but it is looking like you may need to root or at least do the same steps towards that end to accomplish what you are seeking...
So, get back to me/us on this, and hope this all helps...
Ok! So after confirming I could do it without any issue and having a day of time to work on it, my phone's bootloader is now unlocked and I've managed a backup using TWRP. Only thing now is I'm not entirely sure what I should be looking at and how in here. Advice is welcome but I'm going to be digging into it myself to see if I can puzzle it out with some friends of mine online. Also just again thank you all for all the assistance. I would have never gotten this far with it without you all!
AshtonHunter said:
Ok! So after confirming I could do it without any issue and having a day of time to work on it, my phone's bootloader is now unlocked and I've managed a backup using TWRP. Only thing now is I'm not entirely sure what I should be looking at and how in here. Advice is welcome but I'm going to be digging into it myself to see if I can puzzle it out with some friends of mine online. Also just again thank you all for all the assistance. I would have never gotten this far with it without you all!
Click to expand...
Click to collapse
What exactly are you wanting to do now that your bootloader is unlocked, and you have twrp? Can I assume you want to root it?
AshtonHunter said:
Ok! So after confirming I could do it without any issue and having a day of time to work on it, my phone's bootloader is now unlocked and I've managed a backup using TWRP. Only thing now is I'm not entirely sure what I should be looking at and how in here. Advice is welcome but I'm going to be digging into it myself to see if I can puzzle it out with some friends of mine online. Also just again thank you all for all the assistance. I would have never gotten this far with it without you all!
Click to expand...
Click to collapse
I'm glad you were successfully able to get it done! (clicking a "Thanks!" would be all I would welcome in return)
So, now, you might be able to successfully do what you originally did and restore through adb if you wish...I mean, if you simply have a /data folder that's been backed up, there might not be too many options available for you. Another thing you might try is running a custom recovery (TWRP I believe is the best or only) and restoring -- and/or backing up from your old device/phone, wiping everything, setting phone up, then use that TWRP backup to restore -- but you can only really run a restore if it was a TWRP backup to begin with... One other good way is running a Titanium Backup backup and restoring that way...
Good luck and hope this helps...
please help
simplepinoi177 said:
Aahhh,"...your phone isn't rooted..."that's probably it/key. I'm unsure whether any kind of "restore" works without root access -- backup of course works because that simply involves "copying" and "storing" files (essentially the basic process of backing up) and, as the system needs to be able to read and access the data, you pretty much have the "read access" to it. Restore on the otherhand, for those who are unaware, are essentially "copying" those stored files and "overwriting" the existing files -- which require "write access". The process of "rooting" is to acquire "root access" which allows both "read/write access" (therefore: "r/w access"). *again, for those who are unaware.
Sorry for just blabbering on about that, I guess I got carried away. In any case, basically (all in all, the reason why I blabbered on) I don't think you're going to go far without root access -- or "rooting" as you say -- but there is one thing I can suggest. When using adb, try running this command first before running any other adb command (i.e. restore):
Code:
adb root
It might just give you enough of that "root access" I was blathering about...
Also, among the all the things you made sure to do and include you made sure of, one thing you didn't mention is making sure you have the most up to date platform-tools (r28.0.1 *at least last I personally saw a few weeks ago).
Good luck to you, hope I made these things somewhat understandable, and hope this helped as well....
Click to expand...
Click to collapse
sorry in advance, I'm not very familiar with this webiste.
Im in a similar situation where it wont let me restore my adb backup, I am rooted and the bootloader is unlocked (though twrp is not installed). could you please help, i beg you.