Note1: Do at your own risk. As always, it's your device and you're responsible for your actions.
Note2: Following these steps will, in this order: void your warranty, factory reset your TF701, provide root.
These instructions will show you how to gain root on the Asus TF701 by unlocking the bootloader and using fastboot.
Prerequisites: drivers, adb and fastboot (this), firmware >= 10.14.1.47, asus unlock app
Unlock:
- Download the Asus unlock device app from asus.com
- Install and run the app. This will require a valid google account (if you use one time passwords, you'll need to generate one for this purpose) and internet access.
- When booting with [vol-] + [power] pressed, the transformer will show the message "The device is unlocked"
Root:
As the TF701 is very similar to the Nvidia Shield, this method is based on that.
- Download and unpack View attachment root.zip and cd into that directory
- Boot the transformer to the bootloader with [vol-] + [power] pressed
- fastboot boot zImage_dtb ramfs.img.gz
- When seeing the smeared graphics, wait until the transformer reboots 2 minutes and then hard reset (as I did), or press power once (as menollo did)
- The transformer should boot normally and start optimizing applications
- Check root
Foot note: I compared the TF701 and the Shield, and concluded that they should be similar enough to be able to boot the same ramfs. The root method itself was not developed by me.
This is my first instructional root post, what may or may not explain the general structure/mess.
If this was any help, please consider pressing the thanks button. Thanks.
This is based on previous version of https://github.com/linux-shield/shield-root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you tested this yourself and get it to work successfully?
of course i have
Thanks for the verification and screenshot! I hope there will be more dev support now that we have root.....
Sure.
My dev system's ready, I'm going to have a a try at getting a recovery running for the TF701.
However there's still a fair chance, someone will beat me to it.
Interesting, still a very new device. i think i will wait a bit to mess with it
but thanks for your contribution
fellow users, if this worked for you please leave a feedback for others
The big question, is do you have RW privileges to your /System folder? Try copying or deleting a file in /system, or open build.prop and add
# test
at the bottom and save. Or you can try setting the permissions via ES File explorer.
If you can't, then you really don't have full root access. Only Superuser and SU binary. This can cause problems when a root app tries to remount /system as RW (superuser updating binary for example).
Moscow Desire said:
The big question, is do you have RW privileges to your /System folder? Try copying or deleting a file in /system, or open build.prop and add
# test
at the bottom and save. Or you can try setting the permissions via ES File explorer.
If you can't, then you really don't have full root access. Only Superuser and SU binary. This can cause problems when a root app tries to remount /system as RW (superuser updating binary for example).
Click to expand...
Click to collapse
Using FX File explorer i remounted /system as RW, opened build.prop and added #test to the bottom, then saved the file. It works.
lpdunwell said:
Using FX File explorer i remounted /system as RW, opened build.prop and added #test to the bottom, then saved the file. It works.
Click to expand...
Click to collapse
Good to know
Have anyone tried this method for tf701 from tf300t? I know, it's for different models, but...
http://forum.xda-developers.com/showthread.php?t=2228613
lpdunwell said:
Using FX File explorer i remounted /system as RW, opened build.prop and added #test to the bottom, then saved the file. It works.
Click to expand...
Click to collapse
I confirm we have RW privileges in the /system folder. Titanium Backup wouldn't work at first so i started removing bloatware manually in the /system/app folder. I could do this without any problems. TB is working now, it need a wipe data first...
---------- Post added at 10:02 AM ---------- Previous post was at 10:00 AM ----------
HaPe000 said:
Have anyone tried this method for tf701 from tf300t? I know, it's for different models, but...
http://forum.xda-developers.com/showthread.php?t=2228613
Click to expand...
Click to collapse
I'v tried Motochopper when i got my tablet and is not working on the TF701.
FYI the "fastboot oem unlock" does nothing (atleast on US version) just says unknown command. But the other command works, I didn't even have to press power button rebooted on it own. Attached screen shot showing the command not needed.
adb oem unlock is indeed not needed, the asus app unlocks the bootloader, so you can skip that command.
And i also read the code that installs the superuser app. It copies some files, and after that, there is a reboot command, so it should reboot automatically.. (i dont know what happend in my case beacause you can't see the output.. i thought my power button press rebooted the device, but maybe i was just pressing it while the script was executing the reboot)
so after unlocking, you only have to reboot into fastboot (volume down), and run
Code:
fastboot boot zImage_dtb ramfs.img.gz
(in the folder where you downloaded/extracted the shield root files).
Is it possible to backup Apps and esp. Appdata (game data) with Asus backup tool and restore them again? I would hate to lose all my work in angry birds... :silly:
Yezariael said:
Is it possible to backup Apps and esp. Appdata (game data) with Asus backup tool and restore them again? I would hate to lose all my work in angry birds... :silly:
Click to expand...
Click to collapse
The rooting itself does not wipe anything, but unlocking with the asus tool factory resets your device.. so if you haven't unlcoked yet, your device will be wiped.. and at that moment you do not have root yet to backup your data unfortunately.
menollo said:
The rooting itself does not wipe anything, but unlocking with the asus tool factory resets your device.. so if you haven't unlcoked yet, your device will be wiped.. and at that moment you do not have root yet to backup your data unfortunately.
Click to expand...
Click to collapse
As of my understanding the Asus backup tool (on board by default) does backup data as well. Is this not true?
menollo said:
The rooting itself does not wipe anything, but unlocking with the asus tool factory resets your device.. so if you haven't unlcoked yet, your device will be wiped.. and at that moment you do not have root yet to backup your data unfortunately.
Click to expand...
Click to collapse
You are speaking from experience??
Because on none of the Asus Transformer tablets did unlocking do anything to the data partition.
What you are stating may be true for the Nexus, but I highly doubt it's true for the TF701.
Edit: It seems Asus has changed how the unlock tool works. I have read from two users so far who confirm that using the Unlock Tool will wipe your data - unlike on the TF700 (or the 101 and 300 for that matter) where unlocking did not touch your data. Correct me if I'm wrong - this seems strange.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Recovery File Name
The TF700T recovery file name was EP201_768_SDUPDATE.ZIP. Anyone know what the name is for the TF701T?
berndblb said:
You are speaking from experience??
Because on none of the Asus Transformer tablets did unlocking do anything to the data partition.
What you are stating may be true for the Nexus, but I highly doubt it's true for the TF701.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Unlocking will not only wipe your data partition, but also your internal sdcard. So backup all your stuff before unlocking. It happened on my Nexus 7, my wife's ME301T and with the TF701.
Sent from my GT-N7100 using XDA Premium 4 mobile app
ChrisDos said:
The TF700T recovery file name was EP201_768_SDUPDATE.ZIP. Anyone know what the name is for the TF701T?
Click to expand...
Click to collapse
From what I've read so far (caution: hearsay) the recovery on the TF701 recognizes a firmware file no matter if it sits on internal or microSD.
On the TF700 you had to rename the firmware file if you wanted to flash it from the microSD. This seems no longer necessary. Just download the firmware and unzip it once.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Related
This file will only work on Bell/Rogers HTC Raider as far as i know with an unlocked bootloader.
*Credit to bjg222
*Credit to pirateghost for creating a CWM root zip file
*Credit to bananacakes for CWM recovery 5.0.2.7
Instructions
-Unlock bootloader through htcdev.com
-Boot into H-Boot using volume down+power and select fastboot by tapping the power button again
-Connect phone to pc using usb and make sure usb-debugging is enabled and you are in charge mode
-Download adbfastbootrecovery.zip View attachment adbfastbootrecovery.zip
-Extract file contents to somewhere on computer (i recommend desktop!)
-Run adb from the folder you just extracted and type in Fastboot flash recovery root_recovery.img and wait for it to finish
-Put attached CWM root zip file on root of internal sdcard (HTC_STORAGE) View attachment VIVID_CWM_ROOT.zip
-Boot into H-Boot using volume down+power and select recovery (volume down+power)
-Select install zip from sdcard
-Flash attached VIVID_CWM_ROOT.zip through recovery
-Reboot
Click to expand...
Click to collapse
You should now have permanent root on your Bell\Rogers HTC RAIDER
*These are the exact steps i used and they worked perfectly and i hope they do for you as well*
*Standard disclaimer: I am not responsible if this screws up your device*
Thanks, wish something like this comes out for vivid.
Sent from my HTC PH39100 using xda premium
ceo.mtcl said:
Thanks, wish something like this comes out for vivid
Click to expand...
Click to collapse
if i had to guess something like this probably will once the vivid gets it's bootloader unlocked.
erik10002 said:
if i had to guess something like this probably will once you the vivid gets it's bootloader unlocked.
Click to expand...
Click to collapse
yes, let me modify my sentence then, 'wish vivid gets it's boot loader unlocked'
Sent from my HTC PH39100 using xda premium
so I flashed CWM and that was a success. Finished flashing root.zip and seemed to be working.
However now the SU interface on the phone is gliched, with no button or anything that I can click on. Anyone has similar problem?
Wipe data and cache and than reinstall superuser
Sent from my Sensation using XDA App
93795311 said:
so I flashed CWM and that was a success. Finished flashing root.zip and seemed to be working.
However now the SU interface on the phone is gliched, with no button or anything that I can click on. Anyone has similar problem?
Click to expand...
Click to collapse
Wiped data and cache, reinstalled SU from marketplace, problem still exists.
I do have root access on my raider, however I don't get any promt pop up from SU whenever an app is asking for root; instead the app gains root access automatically, and the glitched SU interface would still show no app and no log entry.
Tried to update binary, showed my current version is Legacy, and then update failed on "obtaining root access"
93795311 said:
Wiped data and cache, reinstalled SU from marketplace, problem still exists.
I do have root access on my raider, however I don't get any promt pop up from SU whenever an app is asking for root; instead the app gains root access automatically, and the glitched SU interface would still show no app and no log entry.
Tried to update binary, showed my current version is Legacy, and then update failed on "obtaining root access"
Click to expand...
Click to collapse
remove superuser.apk from /system/app
reboot
then see if the superuser from market will work properly
Pirateghost said:
remove superuser.apk from /system/app
reboot
then see if the superuser from market will work properly
Click to expand...
Click to collapse
Deleted superuser.apk through RE file explore, rebooted and installed SU on the market.
Now I can get prompt working, however something is still missing.
here are the screenshots of the UI
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
93795311 said:
Deleted superuser.apk through RE file explore, rebooted and installed SU on the market.
Now I can get prompt working, however something is still missing.
here are the screenshots of the UI
Click to expand...
Click to collapse
Look to see if the superuser.apk is still in your /system/app if it is
Use add remount your system and then rm superuser.apk and maybe try getting the binary into xbin again.
Sent from my HTC-X710a using XDA App
ToyGUN said:
Look to see if the superuser.apk is still in your /system/app if it is
Use add remount your system and then rm superuser.apk and maybe try getting the binary into xbin again.
Sent from my HTC-X710a using XDA App
Click to expand...
Click to collapse
No, the .apk file is gone since I manually deleted it, and reinstall it from market didn't put it back to /system/app
I screwed up, got the phone rooted and everything but then was fooling around and flashed a rom I shouldn't have and now my phone is stuck in a cycling boot sequence where I see the HTC screen and then turns off and turns back on. I am am able to get to the bootloader but recovery and factory reset don't work. Can anyone help, I've tried looking for a Raider recovery image to flash but that was unsuccessful.
Thanks in advance, I'm new to droids
If your phone turns on and off by its own then your isn't bricked. Something must have gone wrong while you were trying to root it.
You probably need to flash recovery if you can and flash your phone with a stock rom.
Zombiejc said:
I screwed up, got the phone rooted and everything but then was fooling around and flashed a rom I shouldn't have and now my phone is stuck in a cycling boot sequence where I see the HTC screen and then turns off and turns back on. I am am able to get to the bootloader but recovery and factory reset don't work. Can anyone help, I've tried looking for a Raider recovery image to flash but that was unsuccessful.
Thanks in advance, I'm new to droids
Click to expand...
Click to collapse
Sent from my T-Mobile G1 using XDA App
Zombiejc said:
I screwed up, got the phone rooted and everything but then was fooling around and flashed a rom I shouldn't have and now my phone is stuck in a cycling boot sequence where I see the HTC screen and then turns off and turns back on. I am am able to get to the bootloader but recovery and factory reset don't work. Can anyone help, I've tried looking for a Raider recovery image to flash but that was unsuccessful.
Thanks in advance, I'm new to droids
Click to expand...
Click to collapse
try this:
http://forum.xda-developers.com/showthread.php?t=1338919
grab the one for your phone, and try to install it.
Thanks guys, I downloaded what seemed to be the right rom, the one that said Rogers in the name, but when going thru the installation process the program errors out with 155 error and that supposedly an error that I'm installing the wrong rom, I don't know what to do now.
I am having the same problem as member 93795311 except I cannot even delete SU apk using Root explorer as I can't change to "mount as r/w". I have tried going into adb shell "su" but I get permission denied. I have install busybox sucessfully. I downloaded Root Checker Pro and this was what the result was:
Superuser Application Status:
Superuser application - version 3.0.6 - is installed!
System File Properties for Root Access:
Standard location
ls -l /system/bin/su:
-rw-r--r-- root root 22228 2008-08-01 08:00 su
Standard location
ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate location /sbin/su:
/sbin/su: Permission denied
Alternate location /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Can anyone give me some direction? I seem to be partially rooted but I don't know what to do from here.
Thanks.
hey guys i need help with my Rogers HTC Raider,
i'm at the htcdev part where you enter the command
fastboot oem_get_identifier token and it just stops.
it says "waiting for device" for a while now.
i did do an "adb devices" and it shows the device HT1....so i know it detects it.
any suggestions?
albaboi123 said:
hey guys i need help with my Rogers HTC Raider,
i'm at the htcdev part where you enter the command
fastboot oem_get_identifier token and it just stops.
it says "waiting for device" for a while now.
i did do an "adb devices" and it shows the device HT1....so i know it detects it.
any suggestions?
Click to expand...
Click to collapse
ADB and fastboot are different
do a
fastboot devices
and see if it returns the device HT1
you are in fastboot mode right?
i have that question too.
In the beginning steps on the htcdev site it says go to fastboot but how do i do that?
i would turn the device off
press power+volume down
and the device just turns on...
albaboi123 said:
i have that question too.
In the beginning steps on the htcdev site it says go to fastboot but how do i do that?
i would turn the device off
press power+volume down
and the device just turns on...
Click to expand...
Click to collapse
Boot up the phone. Go into settings, power, disable fastboot
Then try again
Sent from my HTC PH39100
The situation is like this,
first am new to the android world and i was reckless i know, but some help would be nice
Case:
-Device: Xperia X8
-Rom: Stock 2.1
-USB Debugging Enabled
-Root (SuperOneClick)
-BusyBox v1.18.4
-Bootloader locked ( default state didn't touch it so its locked i guess)
-No Recovery of any kind
-** Very Important to keep the files, so please no solutions includes wiping the internal memory
What happen:
i was using "Font installer" app to change fonts and accidentally replaced "ALL" the font files in "System/Fonts" and that led the device not to boot now stuck on "Sony Ericsson" black screen
So:
- I think i need a copy of the original "System/Fonts" of any Xperia X8, if you guys can upload?
- and i need to know how can i access the phone internal memory so i can replace the content of "System/Fonts" with the new files
Thanks In Advance
Restore via pcc
Sent from my E15i using xda app-developers app
ElmirBuljubasic said:
Restore via pcc
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
As i said "-** Very Important to keep the files, so please no solutions includes wiping the internal memory"
medomoo said:
As i said "-** Very Important to keep the files, so please no solutions includes wiping the internal memory"
Click to expand...
Click to collapse
Then I guess you are outta luck.. You have to re-flash your ROM. That'll delete data from internal memory. Data on SD Card will be safe..
May be you can use adb to push folder or files you want to its location. It will save your precious data.
Sent from my R800i using xda premium
creative_md said:
May be you can use adb to push folder or files you want to its location. It will save your precious data.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Thank you i will try that, but still i need the original "Fonts Folder", can any one please upload ?
Try to download any ftf file extract it then copy fonts folder from there
Sent from my R800i using xda premium
creative_md said:
Try to download any ftf file extract it then copy fonts folder from there
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Thanks, got the fonts folder still working on how to push it
tried adb, but i cant get root
After adb shell i get $ when i type su i get "[1] segment fault su"
i tried and i searched every where with no luck !! any help please
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
!!!!! Any Help !!!!!
1. Hope u have enabled usb debugging !
2. Go to recovery (if u have it,if not you are in the trouble)
3. Go to mount/storage
4. Mount system,data
5. Download Android Commander or QtADB !
6. Connect usb cable to pc and x8
7. Open Android Commander and QtADB
8 If phone is sucessfuly connected,u can copy Fonts folder from working rom and replace it with damaged fonts folder.
9. Reboot
10. Enjoy!:laugh:
2010matej said:
1. Hope u have enabled usb debugging !
2. Go to recovery (if u have it,if not you are in the trouble)
3. Go to mount/storage
4. Mount system,data
5. Download Android Commander or QtADB !
6. Connect usb cable to pc and x8
7. Open Android Commander and QtADB
8 If phone is sucessfuly connected,u can copy Fonts folder from working rom and replace it with damaged fonts folder.
9. Reboot
10. Enjoy!:laugh:
Click to expand...
Click to collapse
Reading would have saved you some precious minutes that you now will never get back:
medomoo said:
Case:
-Device: Xperia X8
-Rom: Stock 2.1
-USB Debugging Enabled
-Root (SuperOneClick)
-BusyBox v1.18.4
-Bootloader locked ( default state didn't touch it so its locked i guess)
-No Recovery of any kind
Click to expand...
Click to collapse
@medomoo - There might be a way to access the internal memory with specialized equipment, but don't quote me on that one. Go to a phone repair shop or try talking directly to Sony.
The only thing you can do by yourself now is close your eyes and lose the information. You screwed things up really badly with no backup and no recovery. Learn, let it go and move on.
Fortun said:
@medomoo - There might be a way to access the internal memory with specialized equipment, but don't quote me on that one. Go to a phone repair shop or try talking directly to Sony.
The only thing you can do by yourself now is close your eyes and lose the information. You screwed things up really badly with no backup and no recovery. Learn, let it go and move on.
Click to expand...
Click to collapse
Thank you, But why i cant get root access in ADB
Let's put it another way. When your PC freezes, is there anything you can do to manipulate the files? No. Let's take one step further: when you get the blue screen of death while starting the system, is there anything you can do to anything inside your harddrive? No.
It's the same with your phone. Your phone is freezed even before mounting all of the partitions fully and correctly. So, ADB will do nothing. In short, in this regard, there's nothing you can do.
So, take your phone directly to Sony or to a phone repair shop. Or just lose the information.
OK lets say am going to flash a new ROM,
BTW just to take a lesson from that:- what is the safety steps i should take to prevent situation like this from happening again etc what kind of recovery and what else than recovery i can do ??
Backup all apps through titanium backup. And always make nandroid backup through recovery. Its advantage is that if you messed with your phone(like in this case) you can recover backup and you get your old phone back (with data of any kind).
Sent from my R800i using xda premium
Thank god, its working now and didn't have to flash new ROM and all my files are save,
1- Got "Shell Root" with SuperOneClick v2.3.3
2- Used "Android Commander" to push the Original Fonts to its place. and done.
Thanks everyone
DO NOT USE THIS UTILITY ON THE LATEST 4.1.2 OTA UPDATE.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is ONLY for the DROID RAZR M XT907. Do NOT use this on an XT905!
DROID RAZR M Utility 1.20
Use a Download Manager such as "Orbit Download Manager" for best downloading results.
Mirrors:
Dev-Host
Batakang
Filesize: 595 MB (624,299,179 bytes)
MD5: 4867E801B70FCB54A33A1B7EC47BA6A6
- Windows Instructions
Extract .zip to its own folder on the Desktop.
Install the required drivers. The folder with the drivers is called "Drivers [WINDOWS ONLY]" and is included in the Utility folder.
Double click the ".bat" file. This will be called "WindowsUtility.bat" the image is just for reference.
- Mac & Linux Instructions
Extract the .zip to any folder you like, the /Downloads/ or /Desktop/ folder should work just fine.
Open a Terminal window. (On Mac: Applications > Utilities > Terminal)
Learn your 'sudo' password. This is almost always your Admin password on a Mac computer. On Linux you should already know what this is, its yours account password if your account is an admin as well.
Type the following code into the Terminal Windows, places where it says ***DRAG HERE*** are telling you to simply drag the folder there. For example: cd ***DRAG FOLDER HERE*** then press 'Enter' after each line.
Code:
cd ***DRAG UNZIPPED UTILITY FOLDER HERE***
chmod +x ./LinuxMacUtility.sh
bash ./LinuxMacUtility.sh
You will be asked for your sudo password at least once in the Utility process, so make sure you followed the instructions to learn it.
Functions of the DROID RAZR M Utility 1.20:
*These are not to be done in numerical order. Options 3,4, and 6 require Root Access.
Code:
1 Flash 4.1.2 Stock System, Kernel, and Radio (Data Wipe) [from AP Fastboot]
2 Flash 4.1.2 Stock Recovery [from AP Fastboot]
3 Flash TWRP 2.323 Custom Recovery by Hashcode - UNLOCKED BL REQUIRED [from Normal Boot]
4 Flash CWM Custom Recovery by Hashcode - UNLOCKED BL REQUIRED [from Normal Boot]
5 Motochopper Root Exploit by Dan Rosenberg [from Normal Boot]
6 Unlock Bootloader (Install Motopocalypse App) [from Normal Boot]
Number 1 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 System, Kernel, and Radio as well we wipe your data.
Number 2 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 Stock Recovery.
Number 3 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash TWRP Recovery by Hashcode.
Number 4 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash CWM Recovery by Hashcode.
Number 5 Explained -- This is Dan Rosenberg's root exploit called 'Motochopper'. This option requires your phone to be booted normally, with USB Debugging enabled.
Number 6 Explained -- This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader.
Remember, do not run this utility unless your phone is at 100% battery OR you have bought yourself one of Team Black Hat's Factory-Style Programming Adapters.
Thanks to Hashcode for CWM and TWRP. Thanks to Djrbliss for Motochopper and Motopocalypse!
Thanx a lot for the update. Please, tell where did you get stock images of 4.1.2 for Verizon Droid RAZR M. As i know sbf or xml is not released yet.
da900 said:
Thanx a lot for the update. Please, tell where did you get stock images of 4.1.2 for Verizon Droid RAZR. As i know sbf or xml is not released yet.
Click to expand...
Click to collapse
It will be on http://sbf.droid-developers.org/ soon enough. I don't need to share my sources, and doing so would ensure I couldn't get them early for you folks anymore who need them
Why not include TWRP 2.4?
scottocs said:
Why not include TWRP 2.4?
Click to expand...
Click to collapse
Many users on DroidRzr reported bugs on 2.4 and not on 2.323. When 2.5 launches I will update this tool
Sent from my Galaxy Nexus using Tapatalk 2
mattlgroff said:
Many users on DroidRzr reported bugs on 2.4 and not on 2.323. When 2.5 launches I will update this tool
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Seems as though it has been released.
http://teamw.in/project/twrp2
Well, maybe not for this particular device. I may have spoken too quickly.
scottocs said:
Seems as though it has been released.
http://teamw.in/project/twrp2
Well, maybe not for this particular device. I may have spoken too quickly.
Click to expand...
Click to collapse
Yup. It wasn't out last night, anyway. Hashcode is the one to watch for release rather than officially.
Sent from my Galaxy Nexus using Tapatalk 2
How long should the "sending system" step take? It's the first one when I try to flash 4.1.2 and it's taking a really long time
i'm using the this on a mac and i'm getting a couple of error messages, I was wondering if someone could point me in the right direction of fixing things.
I get this error when after i enter the commands listed to start the app:
32 bit Mac System
chmod: ./fastboot.osx32: No such file or directory
I select option 1 and this error comes up
sudo: fastboot: command not found
sudo: fastboot: command not found
sudo: fastboot: command not found
sudo: fastboot: command not found
sudo: fastboot: command not found
sudo: fastboot: command not found
i'm running this on a macbook w/ a C2D. that first error makes me think this might be meant for a newer Mac. Thanks in advance guys
Your directory doesn't exist where it's expected - you sure you're running it from the right place?
Sent from my XT907 on CM10 using Tapatalk 2
I'm just getting "sending system" hanging forever...I tried flashing 4.1.2 stock recovery too and same thing "sending recovery"
Does the rom selected on safestrap matter? I wouldn't think so
Not sure what's going on
Dyelon said:
I'm just getting "sending system" hanging forever...I tried flashing 4.1.2 stock recovery too and same thing "sending recovery"
Does the rom selected on safestrap matter? I wouldn't think so
Not sure what's going on
Click to expand...
Click to collapse
Need 2GB+ RAM free and not using USB 3.0 ports.
Sent from my Galaxy Nexus using Tapatalk 2
delete this
---------- Post added at 04:12 PM ---------- Previous post was at 03:40 PM ----------
Dyelon said:
delete this
Click to expand...
Click to collapse
thanks so much dude...I finally got it to work. I have a lot of android devices and I was using a different micro usb cable. Sorry about that.
you're the man!
only question I have now is...when booting the phone, safestrap isn't coming up anymore. does that mean the partition it created is wiped as well as the space it was taking up replenished to the stock ROM?
thanks again man
I tried following the instructions and this is all I get. phone was in AP Fast boot, I'm just trying to flash TWRP
ktracho13 said:
I tried following the instructions and this is all I get. phone was in AP Fast boot, I'm just trying to flash TWRP
Click to expand...
Click to collapse
Choose 3: TWRP...
Sent from my GT-P3113 on CM10.1 using Tapatalk HD
sloosecannon said:
Choose 3: TWRP...
Sent from my GT-P3113 on CM10.1 using Tapatalk HD
Click to expand...
Click to collapse
I did and it does nothing
ktracho13 said:
I did and it does nothing
Click to expand...
Click to collapse
Isn't option 3 done in normal boot not fastboot?
Sent from my XT907 using xda premium
---------- Post added at 01:03 PM ---------- Previous post was at 01:00 PM ----------
ktracho13 said:
I tried following the instructions and this is all I get. phone was in AP Fast boot, I'm just trying to flash TWRP
Click to expand...
Click to collapse
Yeah use normal boot with USB debugging enabled. Not fastboot
Sent from my XT907 using xda premium
Erisnoob said:
Isn't option 3 done in normal boot not fastboot?
Sent from my XT907 using xda premium
---------- Post added at 01:03 PM ---------- Previous post was at 01:00 PM ----------
Yeah use normal boot with USB debugging enabled. Not fastboot
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
thanks for the help I managed to flash TWRP is it normal the whenever I plug the phone to the computer it immediately reboots into TRWP ?
oh and before rebooting it says "AdB shell has been granted permission"
Will either Option 1 or 2 allow me to update to 4.1.2 without wiping my data? Id like to update, but OTA require i put all the bloatware back. Id like to just flash 4.1.2 without having to redo my phone.
It's a data wipe. You could flash just the radio, boot image etc... Those are extracted and available on another forum. Or you could reinstall the bloat as system apps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This root are universal (for any ROM/Build), it's possible install and unlock DM-Verity V2, in any partition with only flash the file, and modify any partition of the device, this file are ported from Huawei Mate 9, and tested from me, it's fully working, included Kang-Vip ROM's
Requisites:
Bootloader Unlock
Custom Recovery
Installation Method:
Download file
Copy to External SD Card
Reboot to Recovery
Backup your actual BOOT
Install downloaded .zip
Rebot device
Profit!!
*In case of no appear SuperSU app download from Google Play*
Compatibility:
Huawei Mate 9
Huawei P10
Huawei P10+
Download:
2.79: https://mega.nz/#!BY91gIBZ!CjhTxoJIIHjNh_B3Hbmj477qxQ7fZE9VWeItnOgrmfk
Regards
Thanks for this mate; illa try when I get home
Not sure if the OP has English, limitation but the above file and method WORKS on VKY-L29 P10 Plus.
FYI:
* Download the ZIP file (don't unzip) and place on the root of your SD card
* Boot into TWRP (hold up and power buttons for ~6 secs)
* Select INSTALL and navigate to the .ZIP file on the root of your SD card
* After approx 1 or 2 mins, REBOOT the phone
If done successfully like me, it should boot normal. Make sure to go to GOOGLE PLAY and install PHH's Superuser. I've then selected "Superuser Access" over APPS and ADB. I then grant Superuser access to the app itself. Just to verify, i downloaded ROOT CHECKER app and verified successfully.
RoOSTA
Hey mates, I really didn't get it.
Does this method grant a REAL ROOT (system-editing ROOT), or not?
I need to know it before do everything: I don't want to root my device without become THE GOD OF TEH DEVICE
you read?
"it's possible install and unlock DM-Verity V2, in any partition with only flash the file, and modify any partition of the device"
mocassino said:
Hey mates, I really didn't get it.
Does this method grant a REAL ROOT (system-editing ROOT), or not?
I need to know it before do everything: I don't want to root my device without become THE GOD OF TEH DEVICE
Click to expand...
Click to collapse
mocassino said:
Hey mates, I really didn't get it.
Does this method grant a REAL ROOT (system-editing ROOT), or not?
Click to expand...
Click to collapse
To clear up the confusion... If you were to push a system ROM update via Huawei, for example, it will likely REMOVE root and possibly relock the boatloader.
On an older stock ROM, I was boot unlocked with TWRP installed. After a OTA update though, TWRP was removed and boot relocked. So yeah. You can edit the system, but it's not 100% permanent if you were to flash an update.
Really just want to Xposed now!
RoOSTA
BadWolfYe said:
you read?
"it's possible install and unlock DM-Verity V2, in any partition with only flash the file, and modify any partition of the device"
Click to expand...
Click to collapse
then ok, finally I get it. Thanks
---------- Post added at 08:55 AM ---------- Previous post was at 08:52 AM ----------
roosta said:
To clear up the confusion... If you were to push a system ROM update via Huawei, for example, it will likely REMOVE root and possibly relock the boatloader.
On an older stock ROM, I was boot unlocked with TWRP installed. After a OTA update though, TWRP was removed and boot relocked. So yeah. You can edit the system, but it's not 100% permanent if you were to flash an update.
Really just want to Xposed now!
RoOSTA
Click to expand...
Click to collapse
well, actually it's seems peculiar to me that I can push an official update via OTA having the device rooted (or not? It's my first Huawei, on other phones I couldn't update with a modifyed device)
OTA or via firmware finder. Either way
BadWolfYe said:
Compatibility:
Huawei P10
Download:
2.79: https://mega.nz/#!BY91gIBZ!CjhTxoJIIHjNh_B3Hbmj477qxQ7fZE9VWeItnOgrmfk
Regards
Click to expand...
Click to collapse
Great, it works. We have full access to the system. Thank you.
roosta said:
Not sure if the OP has English, limitation but the above file and method WORKS on VKY-L29 P10 Plus.
FYI:
* Download the ZIP file (don't unzip) and place on the root of your SD card
* Boot into TWRP (hold up and power buttons for ~6 secs)
* Select INSTALL and navigate to the .ZIP file on the root of your SD card
* After approx 1 or 2 mins, REBOOT the phone
If done successfully like me, it should boot normal. Make sure to go to GOOGLE PLAY and install PHH's Superuser. I've then selected "Superuser Access" over APPS and ADB. I then grant Superuser access to the app itself. Just to verify, i downloaded ROOT CHECKER app and verified successfully.
RoOSTA
Click to expand...
Click to collapse
What do you mean with PHH's?
Wasn't it clearly stated as a SuperSU root (chainfire?) I'm confused...
BadWolfYe said:
This root are universal (for any ROM/Build), it's possible install and unlock DM-Verity V2, in any partition with only flash the file, and modify any partition of the device, this file are ported from Huawei Mate 9, and tested from me, it's fully working, included Kang-Vip ROM's
Requisites:
Bootloader Unlock
Custom Recovery
Installation Method:
Download file
Copy to External SD Card
Reboot to Recovery
Backup your actual BOOT
Install downloaded .zip
Rebot device
Profit!!
*In case of no appear SuperSU app download from Google Play*
Compatibility:
Huawei Mate 9
Huawei P10
Huawei P10+
Download:
2.79:https://mega.nz/#!BY91gIBZ!CjhTxoJIIHjNh_B3Hbmj477qxQ7fZE9VWeItnOgrmfk
Regards
Click to expand...
Click to collapse
Thanks its working fully root.
P10 PLUS VKY-L29
it requires SD card?
juntulis said:
it requires SD card?
Click to expand...
Click to collapse
In instructions i say : "Copy to External SD Card"
BadWolfYe said:
In instructions i say : "Copy to External SD Card"
Click to expand...
Click to collapse
Because internal storage doesn't work?
Jesus man, just follow instructions. If there was a more easy option, i'm sure it was mentioned.
Thanks by the way for this thread! worked perfectly!
nbyz said:
Jesus man, just follow instructions. If there was a more easy option, i'm sure it was mentioned.
Thanks by the way for this thread! worked perfectly!
Click to expand...
Click to collapse
Jesus dude, not everyone has "External SD card". All i'm asking is it possible to install from internal storage?
I don't need this drama.
juntulis said:
Jesus dude, not everyone has "External SD card". All i'm asking is it possible to install from internal storage?
I don't need this drama.
Click to expand...
Click to collapse
No it's POSSIBLE.
No data in RECOVERY.
juntulis said:
Jesus dude, not everyone has "External SD card". All i'm asking is it possible to install from internal storage?
I don't need this drama.
Click to expand...
Click to collapse
Yes, it's possible to root even if you don't have an external SD.
For me, I can't access Internal storage from TWRP to navigate to the SuperSU zip because it's encrypted for me.
You can flash it from your PC using ADB. Connect your phone to PC and open up CMD from the folder where you have ADB and Fastboot.
Boot into TWRP on your P10. Go over to Adcanced > ADB sideload > Swipe to start sideload.
Now, go over to CMD on your PC and type in "adb sideload (FILE NAME).zip"
Also guys chill. There is no instruction for Internal storage, that's why juntulis is asking
For anyone who rooted their phone : does Viper4Android work with this ?
Please tell me where to take the original oeminfo TWRP backup to P10 plus VKY AL00C00?
I have inherited a Galaxy Tab S2 that appears to have been modified a few times (TWRP 3.1.0-1 already installed).
My goal was to restore it to factory/"new" conditions before attempting to add Magisk.
I tried to wipe Data. Cache, and Dalvik in TWRP and got the following error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have what I believe is the stock firmware T813XXU2BRB2_T813XAR2BRB2_HOME.tar from sammobile, but I was hesitant in attempting to flash it with Odin with these other issues.
Edit: Thinking I maybe need to format/data
Any advice on proceeding?
Let me know if there is other useful info I can provide.
Update:
I used TWRP to format/data and used Odin 3.13.1 to flash T813XXU2BRB2_T813XAR2BRB2_HOME.tar, which flashed successfully.
Tablet Rebooted and eventually Android(7.0) started.
Everything seemed okay so I wanted to check the stock Android recovery.
booting to Android Recovery the tablet tries the following;
1) Installing system update...stays there for about a minute or so.
2) No Command error shows up....stays there for about a minute or so.
3) Then eventually the stock Factory Android Recovery starts.
This is repeatable anytime I try to boot to Android Recovery.
If this was not happening I would be semi confident that I had achieved the factory/"new" conditions that I was looking for prior to attempting to proceed with Magisk installation.
Ill continue reading the forum looking for similar issues, any help would be appreciated.
Update #2
After reading some articles on similar problems I thought Id try a few things.
Seemingly I have "fixed" it.
I used Odin 3.13.1 to again flash my stock rom T813XXU2BRB2_T813XAR2BRB2_HOME.tar, which flashed successfully.
Rebooted to OS to check to see if there was any new problems.
Booted into Android Recovery [had the same issue with the system updates and the No Command Error] eventually Android Recovery started and then I Factory reset.
Rebooted to OS to see if any new issues.
Booted to Download mode and flashed TWRP 3.1.0-1 with Odin 3.13.1 with Auto Reboot unchecked. Flashed Successfully
Rebooted Directly into TWRP Formatted Data. Successfully
While still in TWRP I installed the no-verity-no-encrypt_ashyx zip successfully.
While still in TWRP I installed Magisk-v16.0 successfully.
Rebooted, and everything seems to work Magisk is functioning properly.
I imagine a lot of this was unnecessary, but it was hard to know where to start since I wasnt sure what was done to the tablet in the first place.
Crossing my fingers I dont encounter some future issue complicated by all this
[Update 7/27/18:]
Problem: After Adding Magisk, Screen Mirror to TV would not work. It tries to connect and it says "Wi-Fi Direct and Smart View cannot both be on at the same time" then disconnects.
Thought a System Update might help (since I had not updated yet from the stock rom)
System Update would not work through Tablet's System Update "Unrecognized Device".
Using Smart Switch I was able to update the tablet, however this reversed the flashed TWRP, (I hoped that the Smart Switch would fix the issue with Stock Android Recovery but it did not)
So I reflashed TWRP and rebooted to check if Screen Mirroring, worked no problem.
Rebooted to TWRP, reformated, re-install no-verity-no-encrypt_ashyx zip, and reinstall Magisk.
Rebooted, but Screen Mirror now no longer works.
Looking around to see if any others have had this issue before asking about it in separate post. (Logging it here if problem is related to all this and I need to reference all that happened)
Learningthecurve said:
Everything seemed okay so I wanted to check the stock Android recovery.
booting to Android Recovery the tablet tries the following;
1) Installing system update...stays there for about a minute or so.
2) No Command error shows up....stays there for about a minute or so.
3) Then eventually the stock Factory Android Recovery starts.
:
Click to expand...
Click to collapse
Absolutely normal.
Will do this every time you boot to stock recovery.
Stock recovery is intended for installing stock updates.
It will search for the update, not find one, display no command as there is no update and eventually show the menu.
ashyx said:
Absolutely normal.
Will do this every time you boot to stock recovery.
Stock recovery is intended for installing stock updates.
It will search for the update, not find one, display no command as there is no update and eventually show the menu.
Click to expand...
Click to collapse
Thanks a bunch for the verification.
Now I can concentrate on this screen mirroring issue.
The two devices I have with Magisk both have the same issue still trying to determine if anyone else has had this issue I'll prolly start a new thread there once I wrap my head around it as best I can.
Thanks again!
[Update: It appears the screen share is a known issue. Looking into modifying build.prop wlan.wfd.hdcp=disable gonna digest all I can before diving in]
[Update: Seems I just need to edit the build.prop to add that line " wlan.wfd.hdcp=disable" gave ES File Explorer Superuser access with Magisk....however I cant save it says "read only"....*burp* more figuring to do]
Learningthecurve said:
Thanks a bunch for the verification.
Now I can concentrate on this screen mirroring issue.
The two devices I have with Magisk both have the same issue still trying to determine if anyone else has had this issue I'll prolly start a new thread there once I wrap my head around it as best I can.
Thanks again!
[Update: It appears the screen share is a known issue. Looking into modifying build.prop wlan.wfd.hdcp=disable gonna digest all I can before diving in]
[Update: Seems I just need to edit the build.prop to add that line " wlan.wfd.hdcp=disable" gave ES File Explorer Superuser access with Magisk....however I cant save it says "read only"....*burp* more figuring to do]
Click to expand...
Click to collapse
You have to mount system as writable.
Tbh ES file explorer isn't the greatest root file explorer.
ashyx said:
You have to mount system as writable.
Tbh ES file explorer isn't the greatest root file explorer.
Click to expand...
Click to collapse
Thanks ,
Looking around with the words I searched for it seemed others used SuperSU to root and mounted the system as writable and then saved the modified build.prop.
I was trying to avoid the SuperSU route because of Magisk. ( was not sure if I could root it that way and then modify build.prop and then uninstall SuperSU for Magisk to still function and the modification to maintain)
What I tried was this.....
First I installed busybox giving SU rights with Magisk.
Then I used the "Terminal Emulator" app to try the command;
Code:
su
mount -o rw,remount /system
(no errors)
Retried editing the build.prop with ES File Explorer (would love a suggestion for a radical Alternative ) still a no go;
Tried going into the TWRP Terminal and tried the same command;
No errors but Still a no go.
Then I tried using the "BuildProp Editor" app enabled superuser with Magisk to edit the build.prop. Seemingly that saved. (Though I knew something was strange now, as I could not open the build.prop with Es File Explorer anymore.
I rebooted and tried to screen mirror. No Luck.......
I will continue looking around just worried that Im wasting time looking in the wrong direction, and that Im missing something super easy..