[Blocks OTA's!] Full root for Nook Tablet. [11/20/11] [Permanent root!] - Barnes & Noble Nook Tablet

Note from developer: If you want to block OTA updates, just use the adb hijack app once (click the button on it once) and then you can run the OTA block part of this script and every other mod for it. The hijacker is right below this V
If you already ran this script but want to apply the mods from an update to the script: Just use this method to be able to rerun the script
NOTE: Anyone who is having problems with drivers, http://forum.xda-developers.com/showthread.php?t=1363652 <-- That explains the two most common problems.
Step by step video from my friend Albert to gain root access:
http://www.youtube.com/watch?v=1zbT1Fj38nE
This also includes a gApps install section in it incase you decide you want to run that.
You may NOT use the included script in your work without atleast asking me as of now, this may change in the future but I dont want to have to hop from thread to thread just to offer support when I can keep the answers organized for all to find. So please just ask first.
Thanks.
Information:
I have gotten zergRush to work on the nook tablet as well as created a batch script for you to run to allow you to root your tablet. This does NOT unlock the bootloader software/hardware checks this is just so you can remove whatever unnecessary crap you wish to get the **** off your device.
Features:
Root (obviously)
Gapps install
De-bloat menu
System mods (New gallery, email, keyboard, and live wallpaper support)
Launcher install (Choice of 3!)
Homecatcher installer (if you install a launcher in the previously mentioned feature)
Root check
USB Vendor ID check.
Needed files for root:
You need drivers first:
http://dl.dropbox.com/u/15069134/usbdrivers.zip
here is an app to pull up usb debugging menu
http://li362-167.members.linode.com/gapps/non_google/tgps_launcher.apk
Code:
<robertely> Also note, that while that box will remain checked, the setting is not persistant.
<robertely> So you have to flick the top 'Usb Development' box twice to get it working.
Download Link for rooting script:
http://dl.dropbox.com/u/15069134/Nook&Zergy.zip
Code:
MD5sum
5df962260797ec4e3d80e107bca1fdb2
How to get adb debugging enabled:
Download the apk provided in the second download link to be able to access the menu *if you're just installing an app the first time, it will pull up the menu anyway but this is more for AFTER you have root as a convienance to access usb debugging and whatnot. Just try to install the apk *or open it if you already set unknown sources* and you will get a prompt to allow non-market apps. Click settings then you should be able to see "Unknown sources" check that followed by going into "Development" and check the 2 "Usb Debugging" boxes and uncheck "auto mount" then your nook tablet is ready to be used in debugging mode.
Instructions to root:
1. Download the "usbdrivers" zip
2. Download the "Nook&Zergy.zip"
3. Extract both to a folder C:\ntroot\
4. Now you should see the following files and folders inside c:\ntroot:
5. Run "runmefirst.bat" and follow the instructions.
6a. When the batch file opens the device manager, If you don't see a broken device icon next to "NOOK Tablet" then you may have some other generic drivers taking over. Not sure how to remove them so you will have to move to another PC that has never had a tablet hooked up and start over.
6b. If you do see NOOK Tablet with a broken device icon.. then right click and choose "update driver". Choose "Let me specify where the driver is" and browse to the c:\ntroot\usbdriver folder and hit ok. It should install and you can click "OK" to the warning about unsigned drivers.
7. Run "NookandZergy.bat" and follow the instructions
7a. If you see a long string of numbers/letters it's your device
Now you should have root.
How to Unroot and Undo system mods: Check out this thread:
Code:
Changelog:
7.5: Added file to block OTA's directly instead of needing titanium backup and did a few script fixes as well as added brianf21's hiddensettings app.
7.0.1: Fixed minor bug where systemui mod was not being properly installed (wrong command was used) NOTE: You will get force closes from the systemui until the script finishes and reboots your tablet.
7.0: Allowed recognition of users that used ADB Hijacker app to allow for system mods to occur even if you didnt choose them with the script originally
6.0: Added ricochet1k's SystemUI mod to have perm back / menu button on status bar + have N automatically redirect to home on first click
6.0: (continued) fixed the sdcard check for users since Zerg causes auto unmount of the sdcard
5.2: Added check for sdcard to install files
5.0.1: Added option for access to the titanium backup and push them to sdcard even if you are already rooted
5.0: Added Titanium backup as well as files needed to block OTA's
4.7: New Market added (3.4.4)
4.6: Added permissions fix.
4.5.5: (Debloater): Added Extreme Debloater option
4.5: Debloated updated to be a customized menu (Has a menu included now) [URL="http://forum.xda-developers.com/showpost.php?p=20229004&postcount=625"]found here[/URL]
4.1: Removed bugs
4.0: Included de-bloater and launcher install (you get to choose!)
3.5: Updated to check for proper USB Vendor ID as well as check for root.
3.0: Updated to include system app replacements (Keyboard, Email, Gallery) As well as adding live wallpapers for other launchers. You need to choose to run this part of the script same as gApps.
2.7: Updated Gapps to latest [9/30/2011]
2.5: Fixed a few minor typo's/bugs with the script
v2.1: Added usb vendor id addition to adb_usb.ini
v2.0: Rewritten script to allow for more user choices; added Gapps installer (thanks anlog); Added busybox installer apk and debug menu puller (allows you to access debugging menu)
v1.1 Updated superuser apk
v1.0: Official release
v.75: Updated to install SU and superuser.apk
v.5: Initial release
Code:
Credits:
Gojimi for his HomeCatcher.apk
Developers of ADW launcher for their APK
Developers of Go launcher for their APK
Syndicate Apps for their Honeycomb Launcher
anlog for finding out how to get nook color drivers to work and general testing
Team Revolutionary for their exploit
B&N for using android like good little sheep
suicideclown for bearing with me while I tried to get it to work on his computer until anlog found the driver fix.
Dsstrainer for the simplified instructions.
How to do it manually instead of running the Nook&Zergy.bat file (for linux or mac users or someone who wants to do it all manually)
Install drivers and follow instructions up until running the batch file then do the following commands in order:
Code:
adb push zergrush /data/local/zergy
adb shell "chmod 755 /data/local/zergy;cd /data/local/;./zergy"
adb wait-for-device install Superuser.apk
adb remount
adb push su /data/local/tmp/
adb shell cd /data/local/tmp;chmod 777 su;cd /;mount -o remount,rw -t rootfs rootfs /;
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
Wanna buy me a coffee or something pretty for christmas?
Unroot method can be found here
Rooted nook tablet using my method
Taken from inside of barnes and noble;
{
"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"
}

Indirect said:
Alright, I know you all are going to say "We cant find usb debugging" but allow me to assist you. I found that it's in the development menu of where you enable side-loading of applications so just check that then get the zergrush exploit ran using this.
*I do not own a nook tablet so I cannot check, I just learned alot about it tonight while at a barnes and noble store and the guy who worked there was cool enough to try and help root it with me but since you need adb permissions to run the exploit, I couldn't do anything.
Download Link:
http://dl.dropbox.com/u/15069134/Nook&Zergy.zip
Click to expand...
Click to collapse
Wouldn't still need adb drivers to work in order to do this exploit? If both are possible, I'll gladly buy a nook tablet in order to see if it works (because I intended to buy one anyway if it got root).

I think it might use the nook color drivers but again, I can't test so if anyone has the specific drivers, post them.

Very interesting. I hope someone tries this soon.
Sent from my Samsung Legendary 4G, a Universe UTES phone, running "two.three.five"

I am willing to give this a try tonight. want to get in touch? If it works I will record video.

suicideclown said:
I am willing to give this a try tonight. want to get in touch? If it works I will record video.
Click to expand...
Click to collapse
Thanks. Let us know how it goes!
Sent from my Nook Tablet using Tapatalk

Yeah, add me on Gtalk.
[email protected]

Indirect said:
Yeah, add me on Gtalk.
[email protected]
Click to expand...
Click to collapse
I'll help out as well.
gtalk: [email protected]

I tried this quickly and cannot get it working, i have usb debug enabled however the first problem is that the device does not show up in ADB Devices. Second problem or at least i think it might be is that it defaults in to usb storage mode and while plugged in it cannot be altered from that mode. If someone could create a toggle app to change the default i believe this might help. As for the drivers i am looking and will report back later.

ITFloater said:
I tried this quickly and cannot get it working, i have usb debug enabled however the first problem is that the device does not show up in ADB Devices. Second problem or at least i think it might be is that it defaults in to usb storage mode and while plugged in it cannot be altered from that mode. If someone could create a toggle app to change the default i believe this might help. As for the drivers i am looking and will report back later.
Click to expand...
Click to collapse
People hit a wall here last night on irc, May want to hop in #nookcolor to chat about it.

*cough* http://dl.dropbox.com/u/15069134/add-ons.zip *cough* Put that into your android sdk directory and you have the drivers.

Very nice
Sent from my BNTV250 using Tapatalk

905 views, someone must've tried this by now
Sent from my Samsung Legendary 4G, a Universe UTES phone, running "two.three.five"

You need to add the Nook Tablet USB vendor-id to adb_usb.ini, otherwise adb will not see the device. Do not know what the Nook Tablet vendor-id is, but you can find it with serveral utilities.

I just added a zip that I found to add usb vendor ID and gives you the drivers.

Crap...
I got into the application settings menu and was able to allow sideloading, but the window closed before i could turn on usb debugging. I can't figure out how to get back into the menu, since when I try to install an APK it actually does it now instead of spitting out an error.
Looks like I'm going to have to factory reset. I'll try the root right after that and report results here...
BTW, are those drivers 32-bit or 64-bit?

WAIT here is an app to pull up usb debugging menu
http://dl.dropbox.com/u/15069134/me.tennkia.apr-1.apk

Indirect said:
I just added a zip that I found to add usb vendor ID and gives you the drivers.
Click to expand...
Click to collapse
i got USB debugging enabled (i sideloaded AnyCut and put a shortcut to Development on my home screen)
but i cant get adb to recognize my NT... already edited adb_usb.ini with 0x2080 as vendor id.

http://legacyschool.us.to/nookdev/nookcolor-easyADB.exe
^ use that

Indirect said:
http://legacyschool.us.to/nookdev/nookcolor-easyADB.exe
^ use that
Click to expand...
Click to collapse
no dice, still not recognizing NT

Related

<[TOOL 7/13]> Jeremy's Fre3vo Sticky-Root Windows/Linux/Mac v2.5

This script will run on Windows, Linux and Mac. No longer do you have to worry about having adb in your path, as i have included the binaries for all the operating systems.
The Linux and Mac script will automatically detect what O/S your using and use the correct binary.
You should be all set right out of the box, as long as you have the adb drivers installed for your device if you are in Windows. Linux/Mac users need not worry about the drivers.
COMING SOON.
overclocking capability and more
For Windows Users:
1. REBOOT YOUR PHONE BEFORE RUNNING
2. Extract the zip.
3. Make sure your drivers are installed.
Youtube Video from a user
http://www.youtube.com/watch?v=ZcWqeYQjjk0
older version of the script but same principal
4. Run Root.bat
5. Select your device
6. Hit #1
7. Profit!!!
Drivers For Windows:
Evo3D 32-bit Windows drivers:
Download HERE
Evo3D 64-bit Windows drivers:
Download HERE X64
For Linux/Mac Users:
1. REBOOT YOUR PHONE BEFORE RUNNING
2. Extract the zip.
3. Enter the directory.
4. Set the script permissions to allow it to execute.
Code:
chmod +x root
5. Plug in your device.
6. Run the script.
Code:
./root
7. Select your device.
8. Select #1
9. Profit!
Notes:
After the script starts all you have to do is choose option #1
The script remounts the file system R/W by itself. The other options are just there for convenience if you were to need to remount for hackery. sorry for the confusion.
All files are included including Fre3vo, su, busybox and superuser.apk
I get absolutely no superuser force closes with this. Titanium backup works perfectly. This is also the newest version of the superuser beta.
I have tested these scripts on my phone 10x each, 20 reboots if your counting If you are having problems REBOOT the phone to wipe all the changes you may have made with other scripts/errors.
Also if you install the Terminal Emulator from the market and type "su" you will get a superuser pop up to allow permissions and you will get a root prompt in the Terminal.
Let me know how it works for you.
Changelog:
v2.5
[Linux/Mac] Auto-detect Os
[Linux/Mac] Linux and Mac binaries now included so no more adb having to be in your PATH
v2.4
[Linux/Mac] Fix stupid error on my part in linux script
v2.3
[Linux/Mac]
[Windows]
Script Tweaks
New sticky temp root method (Installs to /vendor/bin/)
v2.2
[Linux/Mac]
[Windows]
HTC Sensation Support!
v2.1
[Linux/Mac] script tweaks
[Windows] rewrote script & added tools
v2.0
[Linux/Mac] rewrote script & added tools
[Windows] SORRY WINDOWS USERS NEW SCRIPT ISNT DONE FOR WINDOWS YET
v1.1
[Windows] Added Windows .bat
v1.0
[Linux/Mac] Initial Release
[Windows] Release SOON!
Download it here
http://dl.dropbox.com/u/11406774/Jeremy_Fre3vo2.5.zip
------Linux
{
"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"
}
------Windows
Dam sweeeet
Can someone make one for a win XP setup
I plan on making a .bat soon but if someone that knows what they are doing wants to try to convert it over for me ill update the op. I use my only windows computer to watch netflix on my tv. LOL
Pew Pew
I got Linux but how do I run this one tho?
Sent From My "Desperate For Root" 3VO...
You Sir are Amazing. Thank You. (Moves my own script into trash =) )
Eagerly awaiting a .bat file for this.
I *THINK* this should work for Window users... I made it really quick like and haven't even tested it myself..
Put this in the SDK folder "platform-tools" and run it as Admin. Make sure you extract all of the files to the root directory of the platform-tools folder and it should work.
platform-tools > root.bat
platform-tools > bin
platform-tools > apk
That should be your folder structure.
Let me know if it works
I got a mac, but from reading the OP it says I need ADB in my path? Not sure exactly what that means...
Stericson said:
I *THINK* this should work for Window users... I made it really quick like and haven't even tested it myself..
Put this in the SDK folder "platform-tools" and run it as Admin. Make sure you extract all of the files to the root directory of the platform-tools folder and it should work.
platform-tools > root.bat
platform-tools > bin
platform-tools > apk
That should be your folder structure.
Let me know if it works
Click to expand...
Click to collapse
Testing now.. ill edit once it (hopefully) completes
EDIT:
steps one thru 3 work great...
cant seem to 4 to work... any ideas?
**************
Your choices:
**************
(1) Set PATH variable for SDK platform-tools directory
(2) List devices found by adb
(3) Temp Root your Evo3d or Sensation with Fre3vo
(4) Install su, Superuser.apk and busybox
(5) Mount /system as R/W
(6) Mount /system as R/O
(7) Check mount points
(8) ADB Shell
(9) Exit
Type choice number: 4
********** su, Superuser.apk and busybox ***********
---------------------------------------------------------
Mounting /system as R/W
mount: Read-only file system
Done!!
---------------------------------------------------------
Installing su and busybox
failed to copy 'bin/su' to '/system/bin//su': Read-only file system
Unable to chmod /system/bin/su: Read-only file system
link failed File exists
failed to copy 'bin/busybox' to '/system/bin//busybox': Read-only file system
Unable to chmod /system/bin/busybox: Read-only file system
[1] Segmentation fault busybox --instal...
Done!!
---------------------------------------------------------
Installing Superuser
failed to copy 'apk/Superuser.apk' to '/system/app//Superuser.apk': Read-only fi
le system
Done!!
---------------------------------------------------------
Installing user and group
cannot create /system/etc/passwd: read-only file system
cannot create /system/etc/group: read-only file system
Unable to chmod /system/etc/passwd: No such file or directory
Unable to chmod /system/etc/group: No such file or directory
Done!!
---------------------------------------------------------
Complete, Press ENTER to return back to the main menu
Click to expand...
Click to collapse
Not sure what I'm doing wrong, copied all the folder elements into c:/android-sdk-windows/platform-tools, ran root.bat, pressed 3, waited until process finished, then pressed 4, installation says Okay. I see SU.apk installed on my phone but whenver I open up any rooted apps, it says cannot find root.
EDIT: this is through the windows version of the script.
Hmmm... I just tried it and it worked for me first go....using adb shell, do you have root?
Stericson said:
Hmmm... I just tried it and it worked for me first go....using adb shell, do you have root?
Click to expand...
Click to collapse
I'm retrying, let me test again after reboot.
fowenati said:
I got a mac, but from reading the OP it says I need ADB in my path? Not sure exactly what that means...
Click to expand...
Click to collapse
here is the mac binary for adb.
what you have to do is copy it into the /usr/bin/ folder.
Code:
sudo cp adb /usr/bin/
you need to make sure you are in the directory that adb is in when you execute that.
spunks3 said:
Testing now.. ill edit once it (hopefully) completes
EDIT:
steps one thru 3 work great...
cant seem to 4 to work... any ideas?
Click to expand...
Click to collapse
try using step 5 first then step 4?
EDIT: Well you shouldn't have to do that...try running step 3 again and show us the output?
Stericson said:
try using step 5 first then step 4?
EDIT: Well you shouldn't have to do that...try running step 3 again and show us the output?
Click to expand...
Click to collapse
my first time 3 worked okay i believe.
when i adb shell i get #
rebooting and trying again
This is my setup. Fresh reboot, fresh file extraction (directly from your .zip into platform-tools). Failed.
http://i642.photobucket.com/albums/uu150/Deflectant/Cropped.png
This picture is cropped, much easier to read.
EDIT: root.bat is in c:/android-sdk-windows/, I cropped it out of the picture though.
SuperUser keeps crashing for me....that might be the problem...
Thanks J.eremy. You asked to let you know how it went in your OP, so I'm reporting back. It worked excellent and quick, as advertised. Couldn't have been simpler, thanks. I've had it running for about an hour now, and have had no super user FC. How long have you had this lasting so far? Prior to this, I would only be able to go about a half hour or so before i got FC on super user, and would have to start over again. Is something different here? It seems to be sticking far longer...at least so far.
k2buckley said:
Thanks J.eremy. You asked to let you know how it went in your OP, so I'm reporting back. It worked excellent and quick, as advertised. Couldn't have been simpler, thanks. I've had it running for about an hour now, and have had no super user FC. How long have you had this lasting so far? Prior to this, I would only be able to go about a half hour or so before i got FC on SU, and would have to start over again. Is something different here? It seems to be sticking far longer...at least so far.
Click to expand...
Click to collapse
Your welcome
it lasts me until reboot every time normally, im pretty sure the main problem with some other scripts are they are not setting the permissions right and not modifying the passwd and group files correctly.
no f/c on my end either
spunks3 said:
my first time 3 worked okay i believe.
when i adb shell i get #
rebooting and trying again
Click to expand...
Click to collapse
yea Stericson is right, looks like the batch file isn't auto mounting the /system as R/W.
gonna go take a look at it now
Overstew said:
This is my setup. Fresh reboot, fresh file extraction (directly from your .zip into platform-tools). Failed.
http://i642.photobucket.com/albums/uu150/Deflectant/Cropped.png
This picture is cropped, much easier to read.
Click to expand...
Click to collapse
interesting...your picture shows it cannot find /bin/fre3vo
either it cant find the folder, or it cant find the file....

[ROOT][WIN] GUI Tool for rooting the Motorola RAZR

This is my first attempt at creating something for users on xda, so be gentle .
Eternityproject has released a fine script for rooting our Motorola RAZR phones on the 4.0.4 update. As a windows-user that used to use batch scripts for everything I could not help but want some more output than just the [rebooting] echo's that the script print on the screen. As a bonus I thought it would be nice to see how long the script will take before my phone is rooted. I have made these wishes into an application, and pedrotorresfilho kindly allowed me to use their script in my application.
So what does it do?
It roots your Motorola RAZR and shows you what the script originally did. It also calculates how long your phone takes to reboot, and shows you how much time you have to get a nice cup of [insert drink here]. Or soda if you prefer that. In theory it is possible to root multiple phones at the same time, which saves time if you have to root 10 RAZRs at once (LOL... as if).
How does one use it?
- Install the program using Microsoft's Awesome ClickOnce distibution system
- Install the Motorola Drivers (Download MotoHelper from here)
- Enable 'Unknown Sources' (on your phone: go to settings, go to security, tick the box next to 'Unknown Sources') (needed to install supersu.apk)
- Enable 'USB Debugging' (on your phone: go to settings, go to developer options, tick the box next to USB Debugging) (needed to communicate with your phone over USB)
- When connecting your phone, please set the USB Mode to 'Media Sync - MTP', to be sure that mounting points won't interfere with the rooting process.
When the application is opened all the connected Android devices will be selected. This means that as soon as you press the 'Root' button, they will be rooted.
In principle the application does nothing more or less than the script. You don't have to have extensive knowledge of adb or android internals, it's just an app that shows the connected devices and a root button . If you are already rooted, it's easy to unroot using SuperSU.
{
"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"
}
Download links:
Open ClickOnce Application (works only if you have .NET 4.0 installed!)
Download page (use this if the above link does not work/you do not have .NET 4.0)
You can update by opening the application. If there is an update, you will be prompted to download the latest version.
Required:
Windows (with .NET Framework 4.0 Client Profile installed)
Motorola RAZR running ICS (other phones might work, but you will get a warning)
I ask all of you kindly NOT to mirror or reshare the application without my permission. Please share the ClickOnce Application link. Is assures that you are running the latest version!
Credits:
Eternityproject (pedrotorresfilho & kholk) - for writing the script
miloj - For finding the exploit binary to root the phone
Dan Wager - For creating AndroidLib, a .NET wrapper for ADB on Windows
Chainfire - For creating and providing SuperSu and his su binary - http://forum.xda-developers.com/showthread.php?t=1538053
Changelog:
1.0.0.6:
Added more strings to the logging output
Fixed the blocking of the root button if there are no devices selected
Added a splash screen to indicate that the application is actually loading
Changed the location where the splash as well as the credits/welcome screen appear
1.0.0.5:
added credits for Chainfires SuperSU and su
Removed the message that rooting was not successful
Added a few more messages about the script itself (in the script output)
Updated SuperSU and binary to 0.94 (su binary still says it needs to be updated )
1.0.0.4:
The application now properly disposes of the AndroidLib instance, disabled the CheckedItem event on the DeviceList because it was a tad buggy. This won't harm anyone.
1.0.0.3:
Enabled Microsoft ClickOnce Update deployment. If I fix a bug, you are able to update to a less buggy version
DJFliX said:
This is my first attempt at creating something for users on xda, so be gentle .
Credits:
Eternityproject (pedrotorresfilho & kholk) - for writing the script
minoj - For finding/creating the exploit binary to root the phone (please correct me if this is not correct)
Dan Wager - For creating AndroidLib, a .NET wrapper for ADB on Windows
Click to expand...
Click to collapse
+1 congratulations for this work
thanks
My Razr is already rooted, but I can test.
nespresso33 said:
My Razr is already rooted, but I can test.
Click to expand...
Click to collapse
I have sent you a dm .
Can you try with this root method. It's simpler.
http://dev.crackflasher.com/ROOT_TOOLS/razrs_edge_windows.zip
For guys already rooted that wanna test it, first unroot your phone:
Run SuperSU app and press 'full unroot'. If you have superuser app also installed remove it first.
Cheers
whirleyes said:
Can you try with this root method. It's simpler.
http://dev.crackflasher.com/ROOT_TOOLS/razrs_edge_windows.zip
Click to expand...
Click to collapse
Hmm... I will have a look at this. What are your reasons for using this except that it's simple? It's just a matter of preference, right?
pedrotorresfilho said:
For guys already rooted that wanna test it, first unroot your phone:
Run SuperSU app and press 'full unroot'. If you have superuser app also installed remove it first.
Cheers
Click to expand...
Click to collapse
Thanks man! Much appreciated!
Well, I tested the 2 versions ( I got a notification to update your tool ).
It is working great but the installer is strange, ( I had all requirements but for people which don't, it's not great ).
SuperSu and binary are not latest version. And I get at the end a message who say " the phone does not seem to have root" but I had root
nespresso33 said:
Well, I tested the 2 versions ( I got a notification to update your tool ).
It is working great but the installer is strange, ( I had all requirements but for people which don't, it's not great ).
SuperSu and binary are not latest version. And I get at the end a message who say " the phone does not seem to have root" but I had root
Click to expand...
Click to collapse
Yeah, the installer should be extra user friendly. I should probably just advice users to use the .application link. But the link will only work if .NET client profile is already installed. I'll adjust the message about root, It seems that the library that I use does not query root status from the phone, but rather from it's cache. Maybe I have to update the phone data before querying for root. Thanks for your feedback!
Edit: I am now uploading version 1.0.0.5, I added credits for Chainfires SuperSU, removed the message about the rooting. Too bad my connection is bad (3G in the mountains in La Palma) so bear with me while the updated version is uploaded. Should be up within about 10 minutes, users that already have the application installed will asked to update to the latest version.
nespresso33 said:
Well, I tested the 2 versions ( I got a notification to update your tool ).
It is working great but the installer is strange, ( I had all requirements but for people which don't, it's not great ).
SuperSu and binary are not latest version. And I get at the end a message who say " the phone does not seem to have root" but I had root
Click to expand...
Click to collapse
1. Installed and executed (had to confirm the download since google chrome didn't allow setup.exe files to be directly donwloaded)
2. Upon start it updated.
3. First run the app didn't recognized my connected Razr after changing USB to Media Device - MTP and enable USB debug.
3. Closed and reopened the app and it recognized and root went fine.
Notes: Application said to 'Refresh' when ADB has being enable, but theresn't a Refresh button.
Really nice!
pedrotorresfilho said:
1. Installed and executed (had to confirm the download since google chrome didn't allow setup.exe files to be directly donwloaded)
2. Upon start it updated.
3. First run the app didn't recognized my connected Razr after changing USB to Media Device - MTP and enable USB debug.
3. Closed and reopened the app and it recognized and root went fine.
Notes: Application said to 'Refresh' when ADB has being enable, but theresn't a Refresh button.
Really nice!
Click to expand...
Click to collapse
The refresh button is the button next to root . I'll put a tooltip on that button. Glad to hear all is fine. I'm uploading 1.0.0.5 to polish out the small annoyances and update SuperSU. Thank you so much for testing .
Edit: 1.0.0.5 is out . The download link is now public. Please leave suggestions and improvements in this topic or send me a DM. Thanks!

Unofficial TWRP Padfone X

Introduction:
The padfone X was released last friday and I wanted TWRP. As you may know; @Dees_Troy is on vacation. So, I hacked together this "repack" version which should have all features in order. One caveat with this version though, when launching recovery after it's installed, the screen must time out (2-minutes) before you can push power and see it.
Warning:
Even though you may simply be using your device and just running apps, you are modifying your device. There is no 100% back to stock. You can find a fastboot flashable stock recovery here, but there is no stock system. While this mod did not trigger a "modified status" on my device, I cannot guarantee the same for you. This is a very new device and unless you're one of the few, brave and anxious, it may be in your best interest to wait until a stock firmware update, back-to-stock flash, or even an official XDA-Developers forum has been created for this device.
you will need:
1.The Unofficial TWRP recovery image
2.SuperSU installed on your device
3.TowelRoot installed on your device. You will need to enable third-party sources.
4.Terminal access (pick the one you're more comfortable with)
4a.ADB
4b.Terminal emulator
installation:
If you chose to use ADB, then use these ADB Instructions. Otherwise skip down to Terminal Emulator Instructions.
ADB Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
navigate to the folder you downloaded ADB (and dll's if you're on windows) and execute the following command.
Code:
adb shell "curl 'https://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/recovery.img; su -c 'dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;"
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Terminal Emulator Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
Launch Terminal Emulator and copy-pasta the following into it.
Code:
curl 'https://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/TWRPrecovery.img; su -c 'dd if=/sdcard/TWRPrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Conclusion
Congratulations, you've got TWRP installed on your device. Now you can back up, restore, and install TWRP Flashable Zips. Please leave a comment and tell others how it worked. This worked great for me, Image below.
{
"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"
}
@Dees_Troy has a helpful suggestion:
Might be worth mentioning Settings -> Screen and lower the screen timeout to help get the screen up and running sooner
Whatever you do, don't turn off the screen timeout though
Click to expand...
Click to collapse
By turning down the screen timeout you only need to wait for two minutes, one time. Turn it down to 30 seconds to reduce the wait time.
Again, this is temporary for this unofficial build. I will update these instructions later when we have a proper solution to perform the needed hardware reset.
I can't wait to see development for this phone!!!! Thank you for all your hard work.
This is great, now all we need is a device thread.
What do we need to do , in order to get that going ? this device has great potential !!!
Adam have you put on the screen protector i saw you bought from ATT? i can't figure out how to properly place it because very time i go into tablet mode and i pull the phone out the phone protector always has a bubble or two from sticking to the tablet ... not sure if that makes sense lol
AdamOutler said:
Introduction:
The padfone X was released last friday and I wanted TWRP. As you may know; @Dees_Troy is on vacation. So, I hacked together this "repack" version which should have all features in order. One caveat with this version though, when launching recovery after it's installed, the screen must time out (2-minutes) before you can push power and see it.
Warning:
Even though you may simply be using your device and just running apps, you are modifying your device. There is no 100% back to stock. You can find a fastboot flashable stock recovery here, but there is no stock system. While this mod did not trigger a "modified status" on my device, I cannot guarantee the same for you. This is a very new device and unless you're one of the few, brave and anxious, it may be in your best interest to wait until a stock firmware update, back-to-stock flash, or even an official XDA-Developers forum has been created for this device.
you will need:
1.The Unofficial TWRP recovery image
2.SuperSU installed on your device
3.TowelRoot installed on your device. You will need to enable third-party sources.
4.Terminal access (pick the one you're more comfortable with)
4a.ADB
4b.Terminal emulator
installation:
If you chose to use ADB, then use these ADB Instructions. Otherwise skip down to Terminal Emulator Instructions.
ADB Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
navigate to the folder you downloaded ADB (and dll's if you're on windows) and execute the following command.
Code:
adb shell "curl 'http://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/recovery.img; su -c 'dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;"
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Terminal Emulator Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
Launch Terminal Emulator and copy-pasta the following into it.
Code:
curl 'http://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/TWRPrecovery.img; su -c 'dd if=/sdcard/TWRPrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Click to expand...
Click to collapse
Didn't work for me. Just look like in TE it kept looking for a response back from the server. I tried to download the img manually and looks like the server is down or something.
FUZER384 said:
Didn't work for me. Just look like in TE it kept looking for a response back from the server. I tried to download the img manually and looks like the server is down or something.
Click to expand...
Click to collapse
It's working now. Server was, in-fact down earlier.
As they (nearly) share the same hardware, do you think it would be possible to compile a working recovery from Asus PadFone Infinity 2 (A86) sources?
Here is a link: http://www.asus.com/Tablets_Mobile/The_new_PadFone_Infinity/HelpDesk_Download/
(or: http://dlcdnet.asus.com/pub/ASUS/Mo...dFone_Infinity/PadFoneT004-1012394-kernel.zip for a direct link)
As Asus has not released PFX kernel sources on their site, I think it could be useful.
Demazda said:
As they (nearly) share the same hardware, do you think it would be possible to compile a working recovery from Asus PadFone Infinity 2 (A86) sources?
Here is a link: http://www.asus.com/Tablets_Mobile/The_new_PadFone_Infinity/HelpDesk_Download/
(or: http://dlcdnet.asus.com/pub/ASUS/Mo...dFone_Infinity/PadFoneT004-1012394-kernel.zip for a direct link)
As Asus has not released PFX kernel sources on their site, I think it could be useful.
Click to expand...
Click to collapse
Not without a device in-hand. I won't try to troubleshoot without it.
However, I use mkbootimg_tools and it requires a Linux system, not windows.
to get reccovery.img
Code:
adb shell su -C dd if=/dev/block/platform/*/by-name/recovery of=/sdcard/recovery.img
adb pull /sdcard/recovery.img
to uncompile original boot.img
Code:
mkboot recovery.img oringialoutput
this opens recovery.img and creates a ramdisk from it which you can freely edit. Now, do the same with TWRPRecovery.img
you will copy the following folders from the TWRP ramdisk to the originaloutput ramdisk. but heed the notes here.
/sbin -- replace only recovery, but copy all files over to the new device.
/res and /etc -- do not replace files, but add in TWRP files to this and its subdirectories.
/supersu -- this does not exist on the new ramdisk, so just copy it.
you will have to navigate to originalrecovery/ramdisk/system, then copy /system/bin into /sbin, then delete /system/bin, finally link /system/bin to /sbin. the positioning is important and you cannot use fully qualified paths to link the files here. it must be linked to ../sbin, specifying one folder up, a folder called "sbin", not /home/username/whatever...
Code:
cd originalramdisk/system/
cp ./bin/* ..//sbin
rm -rf ./bin
ln -s ../sbin
And then you're ready to repack.
Code:
mkboot originalramdisk myNewRecovery.img[code]
now you can copy myNewRecovery.img to your SDCard and flash it using the DD method I showed in the OP.
Oh, I thought you had the device, my bad.
Also, sorry, this may be off-topic (but still related to PadFone and development), but how hard do you think it would be to port CyanogenMod to a PadFone? Not for the PadFone X but for another one, knowing that I managed to build a recovery from source and that it's working, but that I've never managed to make the compiled rom itself boot?
Demazda said:
Oh, I thought you had the device, my bad.
Also, sorry, this may be off-topic (but still related to PadFone and development), but how hard do you think it would be to port CyanogenMod to a PadFone? Not for the PadFone X but for another one, knowing that I managed to build a recovery from source and that it's working, but that I've never managed to make the compiled rom itself boot?
Click to expand...
Click to collapse
This is a Padfone X forum. I can't help you any more than I have. Locate a developer with a Padfone 2 and ask him questions. I gave you instructions to try to create your own. I cannot do more.
AdamOutler said:
This is a Padfone X forum. I can't help you any more than I have. Locate a developer with a Padfone 2 and ask him questions. I gave you instructions to try to create your own. I cannot do more.
Click to expand...
Click to collapse
It's for the PadFone Infinity and I already have a CWM working, my question was about building a ROM. Also it seems that no developer has this device, as it's never beed released in the US.
But no problem, thanks anyway.
Also, sorry but I might not have said it properly in my first post: I did not ask you to build a recovery PadFone Infinity 2 (I don't have this device), I just gave you the kernel source because I thought it could help you build a PadFone X recovery from those sources, as they are both similar in hardware and from the same manufacturer.
Can anyone tell me how to build a cwm recovery for Asus Zenfone 5 ?
I cant take the recovery.img from my system ...
So I seem to have really screwed something up with a few features by trying to save space by integrating various GApps updates to the ROM. I cannot get a keyboard at all during boot-up for any purpose (eg encryption, which my employer requires to use this on their networks).
I don't suppose anyone has a stock nandroid of /system on hand I could download?
EDIT: I see there isn't one yet, but if you make one, anyone, I'd be willing to host it on my Mediafire account.
EDIT 2: Where might I find this flashable stock recovery? I must be overlooking it.
EDIT 3: I see. The link to the unofficial TWRP points to the stock DD pull. I already have a DD pull I just did so ignore that question aboug stock recoveries.
Anyone else having SERIOUS device issues after flashing this?
EDIT: Not demanding updates/etc, just asking/inquiring.
I have ADB installed but running "adb devices" does not show any device connected. My windows 7 shows the storage (internal and external SD card) but windows does not recognize the "ASUS Android Composite ADB Interface".
Any advice where to find drivers for windows 7 for my Padfone X ?
Thanks !
JD
dorj1234 said:
I have ADB installed but running "adb devices" does not show any device connected. My windows 7 shows the storage (internal and external SD card) but windows does not recognize the "ASUS Android Composite ADB Interface".
Any advice where to find drivers for windows 7 for my Padfone X ?
Thanks !
JD
Click to expand...
Click to collapse
LOL! did you ever plug it into the computer? It has the drivers on it.
AdamOutler said:
LOL! did you ever plug it into the computer? It has the drivers on it.
Click to expand...
Click to collapse
For me they installed automatically
Sent from my ASUS PadFone X using XDA Free mobile app
Does anyone have new download link for twrp recovery , link is dead

How to root the Amazon Fire TV 2 box running latest software version 5.2.6.8

I can confirm that this process works on Update v5.2.6.8. Any other version beyond that your mileage may vary. "ADB debugging" and "Apps from Unknown Sources" should be enabled. I would like to thank the following members because without their resources this walkthrough wouldn't have been possible: @diplomatic for the exploit, @el7145 for leaving a cookie crumb trail of clues within his comments in this thread which I had to follow like the yellow brick road in order to repeat his success, @rbox for the custom recovery and pre-rooted image, and @AFTVnews.com because if it hadn't been for your article I probably would've never gotten my AFTV device rooted in time before the 5.2.6.9 OTA update. Oh, I almost forgot... and thanks @Chainfire for SuperSU . And also @teamfresno for the advice.
ACHIEVING TEMPORARY ROOT PERMISSIONS
1. Download and install ADB on your PC.
2. Download "mtk-su_r4.zip" and extract "arm64" folder in ADB install directory (C:\adb).
3. Run command below:
Code:
adb connect 192.168.0.XX
(IP address of your Fire TV device)
4. Transfer mtk-su to your /data/local/tmp folder:
Code:
adb push C:/adb/arm64/mtk-su /data/local/tmp/
5. Open an adb shell:
Code:
adb shell
6. Change to your tmp directory:
Code:
cd /data/local/tmp
7. Add executable permissions to the binary:
Code:
chmod 755 mtk-su
8. Run the exploit:
Code:
./mtk-su
NOTE – The following line should display:
New UID/GID: 0/e
9. Ensure that mtk-su succeeded in setting selinux to permissive by typing the following command:
Code:
getenforce
INSTALLING TWRP & SLOANE
1. Download rbox's TWRP custom recovery and the latest pre-rooted ROM from your PC and copy it to the root of a USB stick [or microSD card].
2. Connect the USB stick [or microSD] to your AFTV2.
3. Change to USB Storage directory:
Code:
cd /storage/usbotg/
NOTE – If recovery is on microSD
Code:
cd /storage/sdcard1
4. Run the zip file. This will automatically run SU:
Code:
sh /storage/usbotg/firetv2_recovery_v7.zip
If recovery is on microSD
Code:
sh /storage/sdcard1/firetv2_recovery_v7.zip
NOTE – It should print out a following lines:
Extracting unzip...
Remounting /system read-write...
Extracting...
Remounting /system read-only...
5. Reboot to Recovery:
Ctrl+C (closes out previously ran script)
Code:
adb reboot recovery
6. Your AFTV2 should reboot to a black screen displaying the Amazon logo, followed by a prompt stating that the device will automatically restart, but if not to unplug then re-plug the power source. It will not automatically restart, but DO NOT unplug the device yet.
{
"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"
}
7. If you copied the recovery and ROM onto a USB stick then you will need to disconnect it from the AFTV2, and connect a USB hub with at least 2 ports to the AFTV2, and connect both a USB keyboard and the USB stick to the hub at this time. If you copied the recovery and ROM onto a microSD then connect a keyboard to the empty USB port at this time.
8. Now unplug then re-plug the power source and you will be presented with the TWRP splash screen.
9. At the boot menu, press the RIGHT arrow key on the USB keyboard to boot into TWRP recovery.
NOTE – whatever you do DON'T let your AFTV2 idle for too long on the initial recovery boot menu screen or it will time out thus restarting, requiring you to repeat the prior steps.
10. Use the arrow keys to select the "Install" in TWRP.
11. "Select Storage", and choose the location where you stored the pre-rooted ROM.
12. Select "Swipe to Confirm Flash" to start the installation.
13. Select "Reboot System" once the file has finished installing in order to restart the AFTV2.
For those feeling a little adventurous/ambitious then feel free to follow this guide created by @g422 as he discuses where to go from here by delving into other avenues to truly tap into the power of your AFTV2 such as what's "Xposed" and the benefits it offers for rooting your device, and also how to backup your current Fire OS install using TWRP.
Also shouts out to @PhoenixMark who created a guide for Mac users based on my write-up as how to enable root here.
This will work if we have a bricked device stuck on the Amazon logo?
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Oh wow, looks like that exploit spread like wildfire!!
Wonder if anybody will see if this works for the firestickv2 (I don't trust myself to crack the case of mine open lol)
b0ricuaguerrero said:
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Click to expand...
Click to collapse
Worked like a charm on my fire tv 2, but I did notice voice control seems to be broken after achieving permanent root.
Anyone else experienced this????
Thank you for putting this guide together! Also thanks to @rbox for twrp and the rom!Finally got root on my Fire TV 2!
Sent from my SM-G9650 using Tapatalk
worked flawlessly on Amazon fire tv 2, the only thing i would say about the instruction for me was that usbotg was not recognised I only had sdcard0 (int storage) sdcard1 (sd card) apart from that great job thank you
ps there was an update waiting to install from amazon which i blocked, perhaps they are patching already
JUSTINMARMER said:
This will work if we have a bricked device stuck on the Amazon logo?
Click to expand...
Click to collapse
Idk. I think we're pretty much in the same boat now: https://forum.xda-developers.com/showpost.php?p=79063299&postcount=197
Delete... duplicate comment
b0ricuaguerrero said:
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Click to expand...
Click to collapse
Not a problem. Just giving back where I can
b0ricuaguerrero said:
Worked like a charm on my fire tv 2, but I did notice voice control seems to be broken after achieving permanent root.
Anyone else experienced this????
Click to expand...
Click to collapse
I don't use voice activation, voice assistants, etc. as a preference. I'm just paranoid like that
huffmybrd said:
Oh wow, looks like that exploit spread like wildfire!!
Wonder if anybody will see if this works for the firestickv2 (I don't trust myself to crack the case of mine open lol)
Click to expand...
Click to collapse
It's worth looking into. Since I currently own one as well I'll see a/b performing these same instructions and post my findings at some point in time.
salsoul said:
worked flawlessly on Amazon fire tv 2, the only thing i would say about the instruction for me was that usbotg was not recognised I only had sdcard0 (int storage) sdcard1 (sd card) apart from that great job thank you
ps there was an update waiting to install from amazon which i blocked, perhaps they are patching already
Click to expand...
Click to collapse
I tried both ways, with the microSD and USB so I know it works if you followed what was stated in the instructions to the T... I know that when I attempted the USB option the first time, I had forgot to plug the USB stick in which made it show up as USB (0) which is only logical explanation I can think of for what happened to you.
Krog18 said:
Thank you for putting this guide together! Also thanks to @rbox for twrp and the rom!Finally got root on my Fire TV 2!View attachment 4718781
Sent from my SM-G9650 using Tapatalk
Click to expand...
Click to collapse
Not a problem, glad I could help
This is fantastic work!!!
Do you know if root can be 'hidden' to Netflix app won't block it's use?
n8wwd said:
This is fantastic work!!!
Do you know if root can be 'hidden' to Netflix app won't block it's use?
Click to expand...
Click to collapse
Thanks, and unfortunately, no. SuperSU is the component that enables root which can be detected by apps that disengage user functionality when they discover root is enabled. I attempted to install Magisk v18.1 to counteract this side effect, but failed miserably w/ the end result to the point that my AFTV2 does a constant boot loop as recounted here. Magisk would be the only option I'm aware of to make root 'hidden', but it's not worth it at the cost of turning your device into a boot looping paper weight.
True. Nothing like having a 'brick on a rope' so to speak. That's not a 'deal breaker' as I subscribe to IPTV services that out performs it anyway. Do you know if Hulu does the same as Netflix? The missus may take exception if it killed that...
---------- Post added at 12:22 AM ---------- Previous post was at 12:20 AM ----------
I guess the main reason I'd want root access is to take all of the preloaded apps off for room, as well as have the ability to use the external storage within apps.
---------- Post added at 12:48 AM ---------- Previous post was at 12:22 AM ----------
well...I answered my own question..seems Hulu doesn't like it either...*sigh* Time to search for a box that can hide root so my wife won't blow a gasket....
Wait, we can't use Netflix if we are rooted? Yikes.
I've had no trouble with Netflix yet since I rooted this yesterday, but of course ymmv.
Sent from my SM-G9650 using Tapatalk
---------- Post added at 08:36 AM ---------- Previous post was at 07:44 AM ----------
urbanman2004 said:
Thanks, and unfortunately, no. SuperSU is the component that enables root which can be detected by apps that disengage user functionality when they discover root is enabled. I attempted to install Magisk v18.1 to counteract this side effect, but failed miserably w/ the end result to the point that my AFTV2 does a constant boot loop as recounted here. Magisk would be the only option I'm aware of to make root 'hidden', but it's not worth it at the cost of turning your device into a boot looping paper weight.
Click to expand...
Click to collapse
Damn, sorry to hear that. I imagine what happened is the result of magisk patching the kernel on a locked bootloader. I hope you're able to get it fixed. Good luck to you!
Sent from my SM-G9650 using Tapatalk
Krog18 said:
Damn, sorry to hear that. I imagine what happened is the result of magisk patching the kernel on a locked bootloader. I hope you're able to get it fixed. Good luck to you!
Sent from my SM-G9650 using Tapatalk
Click to expand...
Click to collapse
Thanks. You never know, somebody smart enough might actually come up with a tool capable of relieving my device from its eternal boot loop hell

How To Guide Rooting Zenfone 9 with Magisk

Guide has been reworked to be more clear and based on comments.
[Part One]
Backup Data
Update phone to latest version
[Part Two]
Download the Firmware for the Zenfone 9 https://www.asus.com/mobile/phones/zenfone/zenfone-9/helpdesk_download/​
Download Payload GUI. https://forum.xda-developers.com/attachments/payload-dumper-gui-v2-3-zip.5758127/ (Hermann2306 credit for mentioning)​
Extract the Payload Dumper GUI zip file, as well as the UL-ASUS Firmware zip file​
Run the Payload Dumper GUI program in the unzipped folder. A file explorer window will pop up; open the unzipped UL-ASUS Firmware folder and select the payload.bin file. Another file explorer window will pop up; select the UL-ASUS Firmware folder if not already selected, then click select folder in the bottom right.​
Click Dump on the Payload Dumper GUI Application. The files will be output to the UL-ASUS Firmware folder.​
[Part Three]
Download Magisk and install onto phone via APK. https://magiskmanager.com/downloading-magisk-manager/
Plug phone into computer and allow file transfer.
Within the UL-ASUS Firmware folder there will be a boot.img file. Move this file onto the phone.
Open the Magisk application and follow image below, select the boot.img to patch
{
"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"
}
A file will be output with magisk. Move this file back onto the PC, and rename to boot.img
[Part Four]
Unlock Zenfone 9 Bootloader. Asus provides a bootloader unlock tool on their website. Below is the link directly to the apk. https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/AsusUnlock_1.0.0.7_210127_fulldpi.apk
Install the drivers listed below for the phones recovery mode https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip (Asus Driver Xanker commented. Thank you again)
[Part Five]
Download Minimal ADB and extract files https://androidfilehost.com/?fid=962187416754459552
Move Boot.img file into Minimal ADB extracted folder.
Put Zenfone into recovery mode and connect to PC. Recovery mode can be achieved by turning off the phone and then powering on whilst holding the volume up button. Release when the ASUS logo pops on screen.
Run cmd-here.exe in the Minimal ADB folder; a command window will open
As a test run the command listed below and it should output a device fastboot devices
If that test succeeded run the final command to flash, fastboot flash boot boot.img
The command prompt command didn't run. Said it was not recognized. Is there a specific place the .exe need to be in the directory?
NVM...got it.
@BreadNoose Thanks for the write-up!!!
I just got the phone 2 days ago and have been trying to follow your steps but without success. I keep having issues with fastboot (I've probably spent 6+ hours on it; I also have a 9-5 job haha). The following are things I've tried:
*Btw, OEM unlock is not showing in Developers options. Download unlock app and I think my OEM is unlocked but in recovery it says "Yes" next to Bootloader thing.
-ADB works fine.
-Download Platform from Google.
-Tried ADB minimal from xda also.
-I tried three laptops, two windows 11 and the other windows 10. None of them recognize fastboot.
- When I go to device manager I see Asus phone listed with that yellow triangle sign and when I try to update the driver it either says drivers up to date or if I manually try to update it says some other error.
- Try different cables.
- I even disabled the driver signature in the restart menu but no success.
-I tried using Asus 8 drivers thinking that would help but nothing.
I wonder if it's just the Asus 9 driver that's the issue? What am I missing???
Any idea?
Thanks for any help you can provide.
bighit101 said:
@BreadNoose Thanks for the write-up!!!
I just got the phone 2 days ago and have been trying to follow your steps but without success. I keep having issues with fastboot (I've probably spent 6+ hours on it; I also have a 9-5 job haha). The following are things I've tried:
*Btw, OEM unlock is not showing in Developers options. Download unlock app and I think my OEM is unlocked but in recovery it says "Yes" next to Bootloader thing.
-ADB works fine.
-Download Platform from Google.
-Tried ADB minimal from xda also.
-I tried three laptops, two windows 11 and the other windows 10. None of them recognize fastboot.
- When I go to device manager I see Asus phone listed with that yellow triangle sign and when I try to update the driver it either says drivers up to date or if I manually try to update it says some other error.
- Try different cables.
- I even disabled the driver signature in the restart menu but no success.
-I tried using Asus 8 drivers thinking that would help but nothing.
I wonder if it's just the Asus 9 driver that's the issue? What am I missing???
Any idea?
Thanks for any help you can provide.
Click to expand...
Click to collapse
Had the same Problem, you have to use this driver:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip
The image version that I just downloaded seems to be at a higher version (WW-32.2030.2030.26 as opposed to WW-32.2004.2004.84 on my phone) and the phone doesn't have that version available (I haven't unlocked the bootloader yet). Should I update locally or download the earlier version of the image instead?
If your phone has the 2004 version installed extract the boot.img from the downloaded 2004 Payload.bin. Or you can update your phone and use the 2030 boot.img.
For me it works with the 2030 version. Root installed, everything ok (AdAway, Postbank (BankingApp)).
If you want to pass SafetyNet just install the magisk module from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.3.1 and reboot.
OK, rooted with no issues, I needed to install the asus drivers and had to reset a second time because the USB stopped working. However, I can't get Google wallet to work despite all other banking apps working as well as passing safetynet.
I dont use wallet, but if installed i can run it and start the setup, no errors.
Maybe try it with the use of denylist.
How to Hide Root from Apps via Magisk DenyList [Android 13]
In this comprehensive guide, we will show you the steps to hide root from apps and games using Magisk Denylist on Android 12.
www.droidwin.com
Hermann2306 said:
I dont use wallet, but if installed i can run it and start the setup, no errors.
Maybe try it with the use of denylist.
How to Hide Root from Apps via Magisk DenyList [Android 13]
In this comprehensive guide, we will show you the steps to hide root from apps and games using Magisk Denylist on Android 12.
www.droidwin.com
Click to expand...
Click to collapse
Doesn't work, the guide asks for denying google system apps which doesn't work because they are always off deny list (this is intended behaviour)
For the record, every other payment apps I am using, even the ones that check for safetynet are working. YASNAC returns a both pass basic.
Then i am sorry (Im too new to the whole android stuff, still learning)
Just for interest, can you start and configure wallet (error comes first if you want to pay)?
Hermann2306 said:
Then i am sorry (Im too new to the whole android stuff, still learning)
Just for interest, can you start and configure wallet (error comes first if you want to pay)?
Click to expand...
Click to collapse
Wallet is configurable, it's just that when you save your card details and it starts contacting the bank it would jump to an error saying that the system is modified.
Maybe try this? (I think you have already read/tried it)
[Magisk] Google wallet (pay) with magisk
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do: - Update Magisk to 25.2, Update magisk app to 25.2 as well - Rename Magisk app if you havent already - [ OPTIONAL ]...
forum.xda-developers.com
Does someone rooted a 16GB ram Zenfone 9? My software is 32.2004.2004.74.
Can not find this software at Asus website.
I have rooted the 16gb version (32.2030.2030.26).
Why dont make an update before root?
xanker said:
Had the same Problem, you have to use this driver:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip
Click to expand...
Click to collapse
OMG!!! Bro you are the MAN! (Sorry im so excited lol).
You literally saved me god knowns how many hours. It was the driver that were the issue. But whats weird is I went to asus site to download drivers before leaving a comment.
I'd really like to buy you a coffee (or adult beverage). Let me know your paypal/venmo.
Thanks again!
williamcll said:
OK, rooted with no issues, I needed to install the asus drivers and had to reset a second time because the USB stopped working. However, I can't get Google wallet to work despite all other banking apps working as well as passing safetynet.
Click to expand...
Click to collapse
Try this: https://github.com/kdrag0n/safetynet-fix
Veiranx said:
Try this: https://github.com/kdrag0n/safetynet-fix
Click to expand...
Click to collapse
Safetynet fix is running, it's just that it's not enough, still going through the prop fix.
bighit101 said:
OMG!!! Bro you are the MAN! (Sorry im so excited lol).
You literally saved me god knowns how many hours. It was the driver that were the issue. But whats weird is I went to asus site to download drivers before leaving a comment.
I'd really like to buy you a coffee (or adult beverage). Let me know your paypal/venmo.
Thanks again!
Click to expand...
Click to collapse
Glad I could help. I already drink enough coffee but you're welcome to donate to a children's charity.
xanker said:
Glad I could help. I already drink enough coffee but you're welcome to donate to a children's charity.
Click to expand...
Click to collapse
Yeah coffee is life!
You're too nice. Will donate in you're name.
Thanks man!!!

Categories

Resources