Related
I got a new Thunderbolt and it came with 2.11.605.9 on it and would not downgrade no matter what I tried.
All these instructions and links came from several different posts on various forums.
This is the combination of things that worked for me to gain root access to the device.
The information and links I take no credit for.
Hope this helps someone as it has helped me.
I did not loose my data with this.
The text in purple are links to needed files, just put http:// in front of them.
Unlock the bootloader
htcdev.com/bootloader
Install Clockwork
• Get fastboot and adb tool for windows here: forum.xda-developers.com/attachment.php?attachmentid=630611&stc=1&d=1308537076
• Get Fastboot and adb for linux here: forum.xda-developers.com/attachment.php?attachmentid=630613&stc=1&d=1308537331
• Obtain clockworkmod recovery:
• HTC Thunderbolt/Mecha cwm-4.0.1.4-mecha.img: downloads.unrevoked.com/recoveries/cwm-4.0.1.4-mecha.img
• md5 : 7990c4d2a5967c0e2c694ba75a65b99d
• Move the recovery.img above to the same directory/folder/map as fastboot and navigate there with an open cmd prompt (WIN) or terminal (LINUX).
• Put the phone is Fastboot USB mode
Type adb devices and press enter. This should output your phones serial number
Type adb reboot bootloader and press enter. This will boot you into the fastboot screen (white with colored letters)
• Type fastboot flash recovery recovery_name.img replacing recover_name with the name of the file you wish to flash and press enter. <<< from a command line (use root for Linux- sudo ./fastboot flash recovery recovery_name.img)
Install the su package
goo-inside.me/superuser/su-3.0-efgh-signed.zip
1. Copy su-3.0-efgh-signed.zip to your sdcard root
2. Start clockworkmod recovery :
---A. Unplug USB
---B. Turn the device off
---C. Hold volume down button (HOLD IT) and press power
---D. Hboot will start. Navigate to recovery with the vol down button. Press power to select and enter recovery.
3. Select "install zip from sdcard"
4. Then select "Choose zip from sdcard"
5. Then select "su-3.0-efgh-signed.zip"
6. Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
7. Then go back
8. Then reboot.
9. You're rooted!
Install Superuser from the market.
Install SuperManager from the market.
Install Busybox from the market.
Install Terminal Emulator from the market.
You can flash ROMs in the same manner the SU package was flashed.
If you want to edit / change system files you can su then remount the FS to rw with the following command within terminal or adb shell :
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
snaganalf said:
I got a new Thunderbolt and it came with 2.11.605.9 on it and would not downgrade no matter what I tried.
All these instructions and links came from several different posts on various forums.
This is the combination of things that worked for me to gain root access to the device.
The information and links I take no credit for.
Hope this helps someone as it has helped me.
I did not loose my data with this.
The text in purple are links to needed files, just put http:// in front of them.
Unlock the bootloader
htcdev.com/bootloader
Install Clockwork
• Get fastboot and adb tool for windows here: forum.xda-developers.com/attachment.php?attachmentid=630611&stc=1&d=1308537076
• Get Fastboot and adb for linux here: forum.xda-developers.com/attachment.php?attachmentid=630613&stc=1&d=1308537331
• Obtain clockworkmod recovery:
• HTC Thunderbolt/Mecha cwm-4.0.1.4-mecha.img: downloads.unrevoked.com/recoveries/cwm-4.0.1.4-mecha.img
• md5 : 7990c4d2a5967c0e2c694ba75a65b99d
• Move the recovery.img above to the same directory/folder/map as fastboot and navigate there with an open cmd prompt (WIN) or terminal (LINUX).
• Put the phone is Fastboot USB mode
Type adb devices and press enter. This should output your phones serial number
Type adb reboot bootloader and press enter. This will boot you into the fastboot screen (white with colored letters)
• Type fastboot flash recovery recovery_name.img replacing recover_name with the name of the file you wish to flash and press enter. <<< from a command line (use root for Linux- sudo ./fastboot flash recovery recovery_name.img)
Install the su package
goo-inside.me/superuser/su-3.0-efgh-signed.zip
1. Copy su-3.0-efgh-signed.zip to your sdcard root
2. Start clockworkmod recovery :
---A. Unplug USB
---B. Turn the device off
---C. Hold volume down button (HOLD IT) and press power
---D. Hboot will start. Navigate to recovery with the vol down button. Press power to select and enter recovery.
3. Select "install zip from sdcard"
4. Then select "Choose zip from sdcard"
5. Then select "su-3.0-efgh-signed.zip"
6. Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
7. Then go back
8. Then reboot.
9. You're rooted!
Install Superuser from the market.
Install SuperManager from the market.
Install Busybox from the market.
Install Terminal Emulator from the market.
You can flash ROMs in the same manner the SU package was flashed.
If you want to edit / change system files you can su then remount the FS to rw with the following command within terminal or adb shell :
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
Click to expand...
Click to collapse
Sent from my ADR6400L using XDA App
i used these steps and I still have s on. When I tried to flash a new rom it gets stuck at the htc boot screen. Any help would be great!
I think I would use the downgrade to .5 then revolutionary from there..
something like this http://forum.xda-developers.com/showthread.php?t=1401959
z71kris said:
I think I would use the downgrade to .5 then revolutionary from there..
something like this http://forum.xda-developers.com/showthread.php?t=1401959
Click to expand...
Click to collapse
I tried this just now but when it goes through the integrity check it does not give me the option to update.
Yes, if you can downgrade at all do it that way. It's much simpler. If you aren't familiar with linux the above will be a hassle for you.
Reason being is, you have to remount the file system to read write every time you want to make a change. It resets to read only on reboot. Thus the s-on.
the weird thing is I already have a rooted devices cause I have the cwm recover still loaded on my device. Just can not flash anything over it. Im on windows 7 right now but I dual boot my laptop with linux mint.
I haven't tried to flash a ROM yet. I just wanted access to some system files so I could edit them.
But according to the post I got the Clockwork info from the below steps should work to flash ROMs.
1. Copy <ROMname>.zip (where <ROMname> is the name of the ROM zip file) to your sdcard root
2. Start clockworkmod recovery :
---A. Unplug USB
---B. Turn the device off
---C. Hold volume down button (HOLD IT) and press power
---D. Hboot will start. Navigate to recovery with the vol down button. Press power to select and enter recovery.
3. Select "install zip from sdcard"
4. Then select "Choose zip from sdcard"
5. Then select "<ROMname>.zip"
6. Then select "Yes - install <ROMname>.zip" to confirm
7. Then go back
8. Then reboot.
I don't know however if the ROM has to be signed.
need a hero
I followed this guide and every other guide to root my phone. I could not downgrade the way the other guides told me to the 2.11.605.5 at all. I followed this guide and when i was in the bootloader i did the whole fastboot flash and it worked but now my phone still says s-on (strange thing is that I have the clockwork recovery). I can flash any rom but nothing will take and I either go into bootloop or will not boot past splash screen. I need a true hero to save the day. It is my only phone and means of communication.
Did you get SU and busybox installed?
I'm not sure, I can't boot in any rom so if it was in the su.zip this guide linked me to yes, if not i didn't. Could this be the problem? Can I fix it through h-boot or recovery?
The method I used will allow root access but does not give you s-off.
I'm still looking for what has to be done for that.
apparently you have to have s-off in order to flash a ROM.
I was able to flash skyraider and now have my phone up and running. I updated superuser, installed Rom manager and flashed clockwork recovery. My phone still says s-on and will not boot any bamf 3.5 roms or the eternity rom, so I'm still kinda confused as to why. I would love to have a sense 3.5 Rom but I'm stumped...
That is strange, being able to flash one ROM but not others.
I still think it's got to do with the s-on/s-off.
Supposedly ICS is coming for the T-Bolt soon.
I'm hoping it won't be locked down like 2.11.605.9 is.
i rooted as soon as rooting was available, no downgrading or anything, it was easy as pie. js
Have you tried going to revolutionary's site after the OP method and try to get s-off... HTC method will not give you s-off & is not a true rooting tool..
Big thanks to the OP for putting this together!
This was the only way for me to gain root on a factory flashed 605.9 phone.
EDIT: i'm a linux user so i thought i would share what i did to get root. it's basically what the OP did with a linux twist.
1) Get Fastboot and adb for linux here: forum.xda-developers.com/attachment.php?attachmentid=630613&stc=1&d=1308537 331
2) Extract the zip to your home directory.
3) open a terminal and issue the following command: sudo chmod 777 fastboot adb
4) Unlock the bootloader using this site: htcdev.com/bootloader
5) you will need to register/login to use the unlocking features of this site.
6) once logged in follow the "unlock device" links to get to the instructions. use these instructions to put the phone into fastboot mode and connect it to the computer. you can ignore the rest of the instructions as most of them are for windows. just click through until you get to the part about submitting an "unlock token".
7) with the phone in fastboot mode and connected to the computer issue the following command in a terminal: sudo ./fastboot oem get_identifier_token
8) copy this token into the submit box and edit to make it look similar to the example on the same page. submit the token and you'll get an email with a file "Unlock_code.bin"
9) save "Unlock_code.bin" to your home folder then issue the command: sudo ./fastboot flash unlocktoken Unlock_code.bin
10) download clockwork recovery to your home folder from here: downloads.unrevoked.com/recoveries/cwm-4.0.1.4-mecha.img
11) issue the command: sudo ./fastboot flash recovery cwm-4.0.1.4-mecha.img
12) Download and install the superuser package
goo-inside.me/superuser/su-3.0-efgh-signed.zip
1. Copy su-3.0-efgh-signed.zip to your sdcard root
2. Start clockworkmod recovery :
---A. Unplug USB
---B. Turn the device off
---C. Hold volume down button (HOLD IT) and press power
---D. Hboot will start. Navigate to recovery with the vol down button. Press power to select and enter recovery.
3. Select "install zip from sdcard"
4. Then select "Choose zip from sdcard"
5. Then select "su-3.0-efgh-signed.zip"
6. Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
7. Then go back
8. Then reboot.
s off??
mechanizedmedic said:
Big thanks to the OP for putting this together!
This was the only way for me to gain root on a factory flashed 605.9 phone.
EDIT: i'm a linux user so i thought i would share what i did to get root. it's basically what the OP did with a linux twist.
1) Get Fastboot and adb for linux here: forum.xda-developers.com/attachment.php?attachmentid=630613&stc=1&d=1308537 331
2) Extract the zip to your home directory.
3) open a terminal and issue the following command: sudo chmod 777 fastboot adb
4) Unlock the bootloader using this site: htcdev.com/bootloader
5) you will need to register/login to use the unlocking features of this site.
6) once logged in follow the "unlock device" links to get to the instructions. use these instructions to put the phone into fastboot mode and connect it to the computer. you can ignore the rest of the instructions as most of them are for windows. just click through until you get to the part about submitting an "unlock token".
7) with the phone in fastboot mode and connected to the computer issue the following command in a terminal: sudo ./fastboot oem get_identifier_token
8) copy this token into the submit box and edit to make it look similar to the example on the same page. submit the token and you'll get an email with a file "Unlock_code.bin"
9) save "Unlock_code.bin" to your home folder then issue the command: sudo ./fastboot flash unlocktoken Unlock_code.bin
10) download clockwork recovery to your home folder from here: downloads.unrevoked.com/recoveries/cwm-4.0.1.4-mecha.img
11) issue the command: sudo ./fastboot flash recovery cwm-4.0.1.4-mecha.img
12) Download and install the superuser package
goo-inside.me/superuser/su-3.0-efgh-signed.zip
1. Copy su-3.0-efgh-signed.zip to your sdcard root
2. Start clockworkmod recovery :
---A. Unplug USB
---B. Turn the device off
---C. Hold volume down button (HOLD IT) and press power
---D. Hboot will start. Navigate to recovery with the vol down button. Press power to select and enter recovery.
3. Select "install zip from sdcard"
4. Then select "Choose zip from sdcard"
5. Then select "su-3.0-efgh-signed.zip"
6. Then select "Yes - install su-3.0-efgh-signed.zip" to confirm
7. Then go back
8. Then reboot.
Click to expand...
Click to collapse
will this get s off? I dont think it does I did this with windows 7 and it didnt seaem to work
I think this is solved
topdogle1 said:
will this get s off? I dont think it does I did this with windows 7 and it didnt seaem to work
Click to expand...
Click to collapse
There is a thread about not having to downgrade that I was able to use to get s off in the Thunderbolt forums. search "Downgrade to get S-off is now unneccessary":laugh:
LaBlondeJames said:
There is a thread about not having to downgrade that I was able to use to get s off in the Thunderbolt forums. search "Downgrade to get S-off is now unneccessary":laugh:
Click to expand...
Click to collapse
This post HTCDev unlocks, but sadly does not S-OFF.
tool in sig but if you did this and unlocked you will have to wipe data to use it. (email me for instructions)
Hey folks,
I´ve ran my MZ601 xoom on EOS builds over the last 1,5 years.
Obviously its unlocked and rooted. Currently its running CWM Recovery 4.0.0.4
Now I want to go back to stock to install the latest official updates to get the updated drivers for the UMTS radio/modem module.
After that I want to unlock and get root again to use any of the lastest custom Roms again.
Switching to a touch based recovery would be nice too.
I surfed around a bit and I´m rather confused which steps I need to perform in order to do this.
I guess I need to remove root and lock the bootloader again before I can install official updates ?
Could someone please toss me in the right direction? Maybe some step-by step list?
You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloaderThen run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot rebootYou'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldThen select reboot in ClockworkMod recovery and boot as normal.
If you are unable to use adb in recovery, then you can enable this through Windows by doing the following:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Finally, run:
adb reboot recoveryIf ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.
Wow, what a detailed guide
Thank you sir
No problem!
Let me know how it goes, hopefully shouldn't have any problems.
Resetting worked great :good:
Right now I´m in an OTA marathon
all that unlock, root and recovery stuff sounds familiar so I don´t expect any problems.
Thanks so far :good:
alecbond said:
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldThen select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recoveryIf ClockworkMod touch recovery is still there then all is good!
Click to expand...
Click to collapse
Ok, so this is not working
after I flash touch recovery and do thta reboot thing I can enter touch recovery, thats fine.
Flashing universal root, fine.
THEN,
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
gives me error since in recovery mode there ist no adb connection
Whatever when I choose to reboot the system, recovery warns me that it will get overwritten by boot and ask me to disable this.
Shall I do this?
EDIT: Nevermind, I decided to be a little brave and just confirmed that message.
Now touch clockwork seems to be persistent and I´m a happy Xoomer again
Sorry, I had meant to reply during my lunch break.
Edit: Realised the time on the second of your posts, so wouldn't have been much help on my lunch anyway
Well I believe I just learned something new!
Either that or I'd forgotten it asked.
I assume it disables the action rather than deletes those files.
My method was just so you can use the reverse rename in future to re-enable the overwrite on boot.
In future, not that you'll necessarily ever need this information, you can enable adb in recovery through windows by doing the following
When in recovery and connected to your PC, open Device Manager, find your phone, usually under 'Other Devices'.
Then right click > Update driver > Browse my computer > Let me pick from list > Pick your phone (either one if there's two shown)
Should confirm driver installed then adb should work.
I didn't include the above previously as I couldn't remember having to do it personally.
Glad to hear all is well though!
alecbond said:
You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloaderThen run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot rebootYou'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldThen select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recoveryIf ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.
Click to expand...
Click to collapse
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
XxLordxX said:
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
Click to expand...
Click to collapse
No problem, I'd be honored!
===============================================================================
TUTORIAL REVISED AND WRITTEN BY @parcek
===============================================================================
FURTHER UPDATED FOR ROOTING NOOBS: 10 Steps
Two Methods: Windows and Linux
Originally posted by @brad2192: https://forum.xda-developers.com/android/development/lg-aristo-2-root-t3746425
Credit to @tecknight for updated files: https://forum.xda-developers.com/showpost.php?p=76837384&postcount=2
@brad2192: Updated Tutorial due to people using TWRP (the original tutorial was released before TWRP was released for this device)
1) Backup all apps and data using LG Backup phone apps
2) Enable USB debugging and Unlock OEM. There are two methods in which you will to accomplish this:
First Method: Smartphone GUI
A) On your Lg Aristo 2 Smartphone go into General Tab (If in Tab View), If in list view, scroll down towards System section
"System Settings > About Phone > Software Information > Click on "Build Number" 10 times.
Now go to "System Settings > About Phone > Developer Options > Enable OEM unlock."
and also "System Settings > About Phone > Developer Options > Enable USB debugging."
Second Method: Windows Command Prompt or Linux Terminal:
Windows:
B) Click and drag "adb" file into command prompt and type "reboot bootloader" after it. Press enter.
Click and drag "fastboot" file into command prompt and type "flashing unlock" after it. Press enter.
Linux:
C)Type in your terminal "adb reboot bootloader" and press enter.
Type in your terminal "fastboot flashing unlock."
NOTE: Below has the information which will teach you how to download ADB and FASTBOOT.
3) Download the following:
Updated - TWRP
Updated - Magisk
(Add this file into your phone's SD Card.)
Updated - boot image
Update: Windows:
B)This is how you download ADB and FASTBOOT for Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
4) Open Command Prompt. Then click and drag the adb file (from the latter download link a.k.a platform-tools) into command prompt then press space and type "reboot bootloader" after and then press enter OR power down phone and hold volume down while plugging in USB)
5) Open Command Prompt. Then click and drag the fastboot file (from the latter download link a.k.a platform-tools) into command prompt and then type "flash recovery" after it and then click and drag "newtwrp.img" into command prompt and press enter.)
6) Open Command Prompt. Then click and drag fastboot (from the latter download link a.k.a platform-tools) into command prompt and then type "flash boot" after it and then click and drag "bootimglistedabove.img" into the command prompt after and then press enter) then follow step 7).
Update: Linux:
C) Depending on kernel, for this sake we will use a debian based kernal.
This is how you download ADB and FASTBOOT for Linux: Open terminal and type: "Sudo apt-get install adb && sudo apt-get install fastboot"
4) Open terminal and type: adb reboot bootloader
5) Open terminal and type: fastboot flash recovery (and then click and drag newtwrp.img onto the terminal) and hit enter
6) Open terminal and type: fastboot flash boot (and then click and drag bootfilelistedabove.img onto the terminal) and hit enter
This applies towards both Windows and Linux: continuation after their last listed step written above.
Step 7) Remove battery from phone, in order to force a shut down.
8) Boot into Recovery-TWRP Mode.
How to boot into LG Aristo 2 TWRP Recovery:
a) The phone is off.
b) Hold the volume key and power key at the same time.
c) When the LG logo appears, let go of the power key (while still holding the volume down key) and then click and hold the power key once again.
d)You will be prompted to LG Aristo 2's stock recovery mode asking you if you are sure you would like to delete ur phone.
e) Go to the option "yes" and enter.
f) It will then warn you that can remove all data from your phone.
g) Go to the option "yes" and enter.
You will be in TWRP after this.
TWRP Mode:
9) In TWRP go to "Wipe > Format Data" and then type "yes" and confirm it. (Do not hit reboot, click back a few time and hit reboot > recovery)
10) In TWRP go to "Install > Select Storage" and select your SD Card. Then look for where you placed the "magisk" zip file. Install it.
Your phone is now rooted.
On TWRP menu: Reboot.
Restore your phone if you created an LG backup of your important files (like lets say contacts or applications).
-----------------------------------------------
If any mistakes were made and you phone becomes locked, here is how to go into download mode to repair your LG Aristo 2 into its default stock rom. Credit to @tecknight: https://forum.xda-developers.com/showpost.php?p=76837800&postcount=4
1) Power off phone.
2) connect usb to Lg Aristo 2 phone (without connecting the usb into the PC or laptop)
3) Hold volume up key and then connect USB into computer
4) download LG Bridge
5) detect phone
6) click on "Update Error Recovery"
Your LG Aristo 2 will be repaired and factory resetted.
-------------------------------------------------------------
What root means: In terms of PC language, Root means the superuser that has privileges to Add, Modify, and or Delete any kind of system files without prevention. Pretty much, it's like the actual Administrator account on a PC. Natively, whenever we buy a phone, it is as if to say, we are only using a guest account. Since the android OS is basically a Linux based computer (correct me if i am wrong) we can do anything we like... You want iOS emoji's on an android? A custom boot animation? Having root privileges allows you to go beyond your guest user restrictions because you then become the Admin.
Explaining the function of the provided Magisk app: It allows root privileges for programs intended for rooted phones.
There are other popular programs alternative of Magisk app, such as the SuperSU app: http://www.mediafire.com/file/2dljobq6yw93w76/UPDATE-SuperSU-v2.82-20170528234214.zip
--------------------------------
After being officially done setting up your rooted phone, make sure you disable OEM Unlock to avoid seeing the caution message before every boot.
--------------------------
How to backup your phone.
Also, using ADB, backup your phone.
Windows: Click and drag ADB file onto command prompt and paste " backup -apk -shared -all -f "C:\Users\UserName\Desktop\backupfilename.ab" "
Linux: Open terminal and type " adb backup -apk -shared -all -f "C:\Users\UserName\Desktop\backupfilename.ab" "
Update: For those who are encountering "Now unlock your phone and confirm operation" when typing the latter code, there is an alternative and much more easier and safer way to backup your phone.
Boot into TWRP and click on "backup" and then select what you would like to back up and then swipe to confirm the operation.
-----------------------------------------------------------------
Confirmed Successful rooting for LG Aristo 2 - June 2018
Thank You Brad and Tec!
Salam Aleykom.
You are a lifesaver my friend
Senorhamburgler said:
You are a lifesaver my friend
Click to expand...
Click to collapse
Brad I have a question, is there any way to get a custom ROM on this phone? If not how come? How does it all work?
And are you with Metro PCS as well? What apps can a safely delete to get this phone as close to a stock version of android as I can? Can I seriously just wipe out EVERY metro app? Hows your phone functioning?
tribal1209 said:
Brad I have a question, is there any way to get a custom ROM on this phone? If not how come? How does it all work?
And are you with Metro PCS as well? What apps can a safely delete to get this phone as close to a stock version of android as I can? Can I seriously just wipe out EVERY metro app? Hows your phone functioning?
Click to expand...
Click to collapse
Until there is a custom recovery built, we won't have custom roms. Dont wipe out every metro app. Anything you arent sure about, look up, or just freeze the app and test results. My phone is fine except SuperSU wont work properly due to the binary being occupied, but this is the best we have so far. I debloated no problem.
tribal1209 said:
Brad I have a question, is there any way to get a custom ROM on this phone? If not how come? How does it all work?
And are you with Metro PCS as well? What apps can a safely delete to get this phone as close to a stock version of android as I can? Can I seriously just wipe out EVERY metro app? Hows your phone functioning?
Click to expand...
Click to collapse
Senorhamburgler said:
Until there is a custom recovery built, we won't have custom roms. Dont wipe out every metro app. Anything you arent sure about, look up, or just freeze the app and test results. My phone is fine except SuperSU wont work properly due to the binary being occupied, but this is the best we have so far. I debloated no problem.
Click to expand...
Click to collapse
Root is the only thing needed, not a custom recovery. Apps like Magisk Manager can flash custom images. The reason there is no ROMs built for this device, I can tell you in my opinion there is no need for a Custom ROM. Magisk Manager has plenty of customizations available as well as many other root apps. Basically, custom recoveries are obsolete, it is not needed for gaining root access nor flashing files. Magisk can do it as well as Flashfire.
I need help.... Abd is not functioning it states "the term abd is not recognised as the nane of a cmdlet, function, scrip file of operable program."
Does not exist in current location.... Windows PowerShell does not load conmands by default...
MinaSaotome said:
I need help.... Abd is not functioning it states "the term abd is not recognised as the nane of a cmdlet, function, scrip file of operable program."
Does not exist in current location.... Windows PowerShell does not load conmands by default...
Click to expand...
Click to collapse
Hey man, I would press the Windows Key+R and type" "cmd"
Then, as long as your adb is located at C:\adb type: "cd C:\adb"
Then use adb, I hate how Windows 10 forces it on users!
Hey, I am so sorry to bother you but when I enter in the fourth step of your tutorial, it tells me "flash boot" command doesn't exist. Is there something I'm doing wrong?
---------- Post added at 01:15 AM ---------- Previous post was at 01:01 AM ----------
4btn said:
Hey, I am so sorry to bother you but when I enter in the fourth step of your tutorial, it tells me "flash boot" command doesn't exist. Is there something I'm doing wrong?
Click to expand...
Click to collapse
Okay, after messing around with it a few, I found that once it goes off into fastboot... my computer can't recognize it anymore?
brad2192 said:
Hey guys, spent a few hours figuring out how to root. Pretty Simple!
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
For those skeptical, proof of root here.
X-210 Stock .KDZ Backup HERE (Should not be needed.)
Click to expand...
Click to collapse
Do I need to unlock the bootloader first? I have it rebooted into fastboot and it's giving me instructions to do that, but won't let me push the boot image. If I do need to unlock it, does it wipe my device?
tge101 said:
Do I need to unlock the bootloader first? I have it rebooted into fastboot and it's giving me instructions to do that, but won't let me push the boot image. If I do need to unlock it, does it wipe my device?
Click to expand...
Click to collapse
Yes, that is what OEM unlock means. In doing so you do need to unlock the bootloader.
brad2192 said:
Yes, that is what OEM unlock means. In doing so you do need to unlock the bootloader.
Click to expand...
Click to collapse
Just wanted to make sure but does it wipe it?
tge101 said:
Just wanted to make sure but does it wipe it?
Click to expand...
Click to collapse
Yes, when you use "fastboot oem unlock" it unfortunately erases all data. One of our forum members is working on a TWRP at the moment that might be available today. You could wait to do this so you can create a backup.
brad2192 said:
Yes, when you use "fastboot oem unlock" it unfortunately erases all data. One of our forum members is working on a TWRP at the moment that might be available today. You could wait to do this so you can create a backup.
Click to expand...
Click to collapse
That'd be cool. But, wouldn't the bootloader still need to be unlocked for me to flash TWRP?
tge101 said:
That'd be cool. But, wouldn't the bootloader still need to be unlocked for me to flash TWRP?
Click to expand...
Click to collapse
I'm an idiot, yes LOL. Sorry, just got to work and I am tired you are correct. So, if you would like I suggest just using my tutorial. I believe there is ways of using LG backup to save most of your user data.
brad2192 said:
I'm an idiot, yes LOL. Sorry, just got to work and I am tired you are correct. So, if you would like I suggest just using my tutorial. I believe there is ways of using LG backup to save most of your user data.
Click to expand...
Click to collapse
All good, if I lose it I lose it. Is there a thread for the TWRP development?
I posted a test twrp on my blog for aristo 2
cannot open root_boot.img
hey maybe someone can help me out
previously already unlocked the bootloader on the phone so i skipped that step but i keep getting the error that it can not open root_boot.img
downloaded the file and moved into users/appdata/local/android/sdk/platform-tools
thats where adb.exe so i figured that is the adb folder maybe yes or no
could anyone help me out
greatly appreciate it
tge101 said:
All good, if I lose it I lose it. Is there a thread for the TWRP development?
Click to expand...
Click to collapse
Update: TWRP HERE
TJ-yesthelegend said:
hey maybe someone can help me out
previously already unlocked the bootloader on the phone so i skipped that step but i keep getting the error that it can not open root_boot.img
downloaded the file and moved into users/appdata/local/android/sdk/platform-tools
thats where adb.exe so i figured that is the adb folder maybe yes or no
could anyone help me out
greatly appreciate it
Click to expand...
Click to collapse
What are you typing into ADB to get that error?
Do you have to de-encrypt the phone for root? I am thinking of getting an Aristo2, currently using the MotoE4 (which I hate!), and rooting that requires de-encryption (I love encryption!). This is the MetroPCS version your talking about? Thank you...
This is the new official way to root the Razer! Please forget all older methods. If you follow this guide, you will not have problems.
Ok, so there isn't some file you download to fix the Wifi, but this is how you make it work, when you swear you've tried everything.
(Trust me you didn't even if you think you did.)
So I'm a very smart person and I realized why so many people are running into this problem. It's because they are used to a bad habit with the Pixel XL phones. I was a prior Pixel XL phone owner and the bad habit that I have and that you guaranteed failed to realize what you did if you have broken wifi was, you didn't flash the TWRP.zip version.
You see, with the Pixel XL, most people realized that flashing TWRP permanently was not required on the Pixel XL and therefore we only booted the TWRP.img image every time we needed to flash something. Well that flat out does NOT work here on the Razer phone and it's the reason everyone is having issues with Wifi not working after flashing Magisk. You see I figured out that TWRP.zip flashes itself onto the stock boot.img image, and when it does so, it does it in such a way that it appears stock still to Magisk. Magisk then happens to flash itself onto the image in a proper way. If you use just the stock boot.img image and flash Magisk onto it, it also detects it as a stock image, but something is bugged in the formatting which breaks Wifi. So you cannot just take a stock boot.img and flash magisk onto it and expect it to work.
In fact when you fastboot twrp.img && fastboot reboot, it literally overwrites the stock boot.img for one side. (Current slot that you are on.) Before factory images, you are then required to store the boot.img from the other slot you did not boot from. (This was what was not explained very well for the lamen to understand.) Before factory images, if you failed to do this, and flashed TWRP.zip then you basically no longer have a clean boot.img file on either slot. (Now that we have factory images, we can just extract boot.img from there and use only it.)
Therein lies the fix. You need to ensure that you have a clean boot.img from the factory images provided by Razer, you then need the TWRP.img and TWRP.zip versions. You also need Magisk v16. (Latest works great.)
Guide coming in a second, but for those who just need to reset and fix Wifi regardless of your current state here's how:
1.) Obtain boot.img from the latest Razer factory image. (If you are not already on the latest, best to just flash it using Razers guide to restore using factory image.) https://developer.razerzone.com/razer-phone-dev-tools/factory-images/
2.) Obtain TWRP.img and TWRP.zip from https://dl.twrp.me/cheryl
3.) Obtain Magisk from: https://forum.xda-developers.com/attachment.php?attachmentid=4427150&d=1519237503
4.) Now that you have all 3 files. I will explain twice to make this easy for the lamen depending on which slot you are starting out on.
5.) Push all 3 files to /sdcard by ensuring all 3 files are inside of your platform-tools folder with adb.exe and fastboot.exe, and with the following command: "adb push boot.img /sdcard", then "adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard", then "adb push Magisk-v16.0.zip /sdcard"
6.) Now boot into fastboot by doing: "adb reboot bootloader"
7.) It's always good to test if your drivers are working by doing: "fastboot devices" If you get a serial number then it's working fine, and use a good Grade USB-A to USB-C cable.
8.) Once in the bootloader and you see "Download Mode", type: "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot"
9.) You should now be in TWRP. Select the reboot button and check which slot you are on and follow instructions accordingly below: (Skip down to "Slot B Instructions" if you are starting out on Slot B.)
Slot A Instructions:
1.) Verify that you are in Slot A by going to Reboot, then viewing what slot you are currently on. It should say Slot A.
2.) Back out and go to "Install", then select "Install IMG" button at the bottom, then browse to the boot.img file.
3.) Select boot.img and swipe to install.
4.) Go back to the main menu, and select the "Reboot" button and change your slot to Slot B.
5.) Once verified it states Slot B, select Bootloader to go back to "Download Mode" This will force it to SlotB, and re-run "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot".
6.) Once there, to go the "Install" button, and select "Install IMG" button, and select and flash boot.img again. This will give you a clean boot.img on Slot B, as well as Slot A.
Your phone is now corrected, and you can do it the proper way.
7.) Doesn't matter which flash you are on now. Go to "Install" button in the main menu, and select "Install Zip", and select the TWRP-installer-3.2.1-0-cheril.zip file. Swipe to complete. This will PATCH BOTH Boot.img images! This is required!
8.) Reboot to System so that it can get a proper boot and verify that Wifi works. (It should if you followed instructions to the letter.)
9.) Once done, type: "adb reboot recovery". (IMPORTANT!!! DO NOT DO DOWNLOAD MODE AND BOOT THE TWRP.IMG as it will OVERWRITE ALL OF YOUR WORK THUS FAR!) This takes you straight to recovery without overwriting. Go to the install button and install a zip, and select the Magisk-v16.0.zip file, and reboot to System. Congratulations! It should be working, but we've only flashed one side, we want to cover both banks, so we need to flash magisk on the second bank as well. (This is optional, but nice to have in case your phone decides to switch banks due to some error and root will still work if you do continue.)
10.) If it is and you want to be more complete. Type: "adb reboot recovery". (IMPORTANT!!! DO NOT DO DOWNLOAD MODE AND BOOT THE TWRP.IMG as it will OVERWRITE ALL OF YOUR WORK THUS FAR!) go to the Reboot Button, and change your slot, then select "Recovery" to force a reboot to force the slot change. Then go to the Install Button and select Magisk-V16.0.zip and flash it over the boot.img from the new slot we just changed too.
Now both banks are flashed properly, and it doesn't matter which one you boot from, it should work with Wifi.
Slot B Instructions: (Skip if you started originally on Slot A, you are done.)
1.) Verify that you are in Slot B by going to Reboot, then viewing what slot you are currently on. It should say Slot B.
2.) Back out and go to "Install", then select "Install IMG" button at the bottom, then browse to the boot.img file.
3.) Select boot.img and swipe to install.
4.) Go back to the main menu, and select the "Reboot" button and change your slot to Slot A.
5.) Once verified it states Slot A, select Bootloader to go back to "Download Mode" This will force it to Slot A, and re-run "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot".
6.) Once there, to go the "Install" button, and select "Install IMG" button, and select and flash boot.img again. This will give you a clean boot.img on Slot A, as well as Slot B.
Your phone is now corrected, and you can do it the proper way.
7.) Doesn't matter which flash you are on now. Go to "Install" button in the main menu, and select "Install Zip", and select the TWRP-installer-3.2.1-0-cheril.zip file. Swipe to complete. This will PATCH BOTH Boot.img images! This is required!
8.) Reboot to System so that it can get a proper boot and verify that Wifi works. (It should if you followed instructions to the letter.)
9.) Once done, type: "adb reboot recovery". (IMPORTANT!!! DO NOT DO DOWNLOAD MODE AND BOOT THE TWRP.IMG as it will OVERWRITE ALL OF YOUR WORK THUS FAR!) This takes you straight to recovery without overwriting. Go to the install button and install a zip, and select the Magisk-v16.0.zip file, and reboot to System. Congratulations! It should be working, but we've only flashed one side, we want to cover both banks, so we need to flash magisk on the second bank as well. (This is optional, but nice to have in case your phone decides to switch banks due to some error and root will still work if you do continue.)
10.) If it is and you want to be more complete. Type: "adb reboot recovery". (IMPORTANT!!! DO NOT DO DOWNLOAD MODE AND BOOT THE TWRP.IMG as it will OVERWRITE ALL OF YOUR WORK THUS FAR!) go to the Reboot Button, and change your slot, then select "Recovery" to force a reboot to force the slot change. Then go to the Install Button and select Magisk-V16.0.zip and flash it over the boot.img from the new slot we just changed too.
Now both banks are flashed properly, and it doesn't matter which one you boot from, it should work with Wifi.
This is how you correct and ensure you are rooted if you screwed up.
--------------------------------------------------
Now for instructions to do it the clean way for the first time. (For those who did not muck up their phone and waited patiently to do it right the first time.)
1.) Type: adb reboot bootloader
2.) Type: "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot"
3.) Once booted into TWRP via the image. Push the 3 files: "adb push boot.img /sdcard", then "adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard", then "adb push Magisk-v16.0.zip /sdcard"
4.) Once pushed, on the phone, select the Install button, then select "Install IMG" button, and select boot.img, then swipe to install.
5.) Once installed, go back to the Install button, and then "Install Zip", then select TWRP-Installer-3.2.1-0-cheryl.zip and install the zip.
6.) This will Patch TWRP onto both boot.img's which should both be clean up to this point. (factory image shouldn't be required)
7.) Now that TWRP.zip has been installed to both boot.img's, you must reboot to SYSTEM!
8.) Once back in the phone verify Wifi still works, then do: "adb reboot recovery" (IMPORTANT!!! DO NOT DO DOWNLOAD MODE AND BOOT THE TWRP.IMG as it will OVERWRITE ALL OF YOUR WORK THUS FAR!)
9.) Once in recovery, go to the install button, and select Install Zip, and select Magisk-v16.0.zip.
10.) Once this is done, you should do this to the other Slot. To accomplish this without screwing it up, go to the Reboot button from the main menu and switch slots. Once slots are switched, select Recovery to reboot into recovery (even though you are already in Recovery, we need a reboot to force the slot change for it to flash the correct boot flash slot) and force a Slot swap.
11.) Now verify that the Slot swapped via the "Reboot" button, back out, and install, then install zip, and select Magisk-v16.0.zip again. and swipe to install.
12.) Reboot into System or swap slots if you want and reboot into System, it should work either way, and Wifi will work!
Congratulations!
I was one of the users who bricked their phones using the old guide but following this guide I am now rooted with Magisk. In order too boot I had to swap back to my original boot slot (A) before I could boot though
Thanks OP!
I'll try this after work today.
I'm one of the people who no matter how they installed Magisk or SU I'd lose WiFi. I sure hope this works! I will report back later.
YES! Twrp and rooted with WiFi working. Great work OP!
I refrained from rooting because of the numerous sour experiences.
This guide puts me at ease in now proceeding with root.
Good work OP
I've waited patiently but now confident to run through it thanks to your guide. Will do tomorrow. Thank you.
Thanks a lot for the instruction. This worked for me. As @PupPupG suggested, I had to swap back to original boot slot (A) before I could boot though or else it bootloops.
phone no longer recognises as been connected after rebooting into bootloader via command prompt
parky169 said:
phone no longer recognises as been connected after rebooting into bootloader via command prompt
Click to expand...
Click to collapse
Did you verify you have a functional ABD Composite driver in Device Manager? This sort of thing is almost always ADB Composite driver related if ADB works but fastboot does not. Check device manager and see if you have a device with a yellow asterisk next to it when you phone is connected and in Download mode. I use the Samsung ADB Composite drivers on all phones I've had and it work fine.
Hmm... I followed to the letter. On your last step. I switched back to A, then hit reboot to recovery (to then reboot system via recovery) and it switched to "Download mode".
It's still recognised in Fastboot, but it's stuck at download mode.
------------------------
P.s. to anyone else - don't do what I did. At the very last step, just boot it while it's still in slow B. Worked a treat.
Thank you my friend!
------------------------
omg... so... do NOT forget. If you start this BEFORE you have unlocked the bootloader, then unlocking it will ERASE ALL DATA (that's not my issue).
The issue with that is it reverts all system updates. So once I finally got back to my home screen with Magisk installed etc.... I immediately got a system update which I couldn't perform.
WOOP DE DOO!
Full flash of Global Image (goodbye Three!!) and running through the latter steps again. Should be me finally sorted.. (post midnight UK time)
----------------------
Nope. On switching to slot B (clean flash of global image), I get "Updater process ended with ERROR: 1; Error installing zip file '/sdcard/magisk.zip' "
It worked for slot_A... so not sure what's going on here?
----------------------
OK so slot A definitely works fine. But I can't get slot B to flash Magisk with the global image. It was actually working with the Three image, but I decided I wanted to make my phone unbranded during this process.
If any ideas on how to bypass the error for Magisk on install for Slot_B - let me know! Goodnight!
I have not been able to flash Magisk on partition B either. I get the same message. Not a big deal for me, as I can always flash the stock boot.img to get back up.
Can't detect devices
Hello, needed some input here on what to do. Mine is a fresh install, just bought the device, so it tried following the steps but got stuck very shortly after.
At first my PC didn't manage to find the device, so i installed the latest usb drivers and it worked. However, once i reboot it into bootloader,
adb devices / fastboot devices doesn't show anything connected. I opened device manager to find my Phone with (!) mark, so i tried installing the drivers manually for Android ADB Interface, Android Bootloader Interface, and Android Composite ADB Interface. Tried both 3 and tried to check for devices, but nothing showing up. If i do any commands it just says waiting for devices.
What should i do in this case? Thanks!
Mokonae said:
Hello, needed some input here on what to do. Mine is a fresh install, just bought the device, so it tried following the steps but got stuck very shortly after.
At first my PC didn't manage to find the device, so i installed the latest usb drivers and it worked. However, once i reboot it into bootloader,
adb devices / fastboot devices doesn't show anything connected. I opened device manager to find my Phone with (!) mark, so i tried installing the drivers manually for Android ADB Interface, Android Bootloader Interface, and Android Composite ADB Interface. Tried both 3 and tried to check for devices, but nothing showing up. If i do any commands it just says waiting for devices.
What should i do in this case? Thanks!
Click to expand...
Click to collapse
I have the exact same issue, word for word.
Mokonae said:
Hello, needed some input here on what to do. Mine is a fresh install, just bought the device, so it tried following the steps but got stuck very shortly after.
At first my PC didn't manage to find the device, so i installed the latest usb drivers and it worked. However, once i reboot it into bootloader,
adb devices / fastboot devices doesn't show anything connected. I opened device manager to find my Phone with (!) mark, so i tried installing the drivers manually for Android ADB Interface, Android Bootloader Interface, and Android Composite ADB Interface. Tried both 3 and tried to check for devices, but nothing showing up. If i do any commands it just says waiting for devices.
What should i do in this case? Thanks!
Click to expand...
Click to collapse
When you are in bootloader install the driver. Android ADB interface is the correct one. Once done restart your pc and check in cmd 'fastboot devices' and see if it shows your device serial number
i still have same problem as quite a few on here,device not showing once in download mode.i have been flashing roms and mods since htc wildfire so not new to this,but this is giving me a headache.if anyone has a solution please help thanks in advance
I think part of the problem is which version of the adb/fastboot/drivers you are using.. For the Razer phone they MUST BE the latest.. You need to get rid of the old ones and JUST install the newest from Google.. Dont use any of the "packages" on XDA as all the ones I've seen haven't been updated.
I had my laptop setup working adb/Fastboot/drivers that ran with my 6p fine but with razer phone I always had issues... Ie ADB would see it, but Fastboot wouldn't.. Fastboot commands would get stuck, or not even work, etc.. After much fighting I had to get the platform tools and drivers from Google directly and uninstall the previous versions of both,, did a fresh install of them and now have no problems.
D:\platform-tools>fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
error: cannot load 'twrp-3.2.1-0-cheryl.img': No such file or directory
Click to expand...
Click to collapse
I can't seem to boot to twrp.
Any thoughts? I'm already rooted via magisk but I need TWRP to do other stuff.
hi thanks everything worked great,only downfall is as soon as i rebooted there was a system update which i cant install now...never mind cant win them all.lets hope for some rom magic now..thanks again
@leapfrog2 Your twrp.img file is not in the same Directory as adb.exe and fastboot.exe
For anyone having driver issues. Use the latest Google usb drivers from google. Your phone is in fact two devices with only one active at a time. Adb driver is for when an OS has been loaded such as twrp or android itself. Fastboot driver is the Samsung USB driver is the one that works for this device when in fastboot or download mode provided by the google USB driver set. That's because this phone uses a Samsung bootloader chip same as the Galaxy notes do which also use download mode based bootloader's. (Except ours are unlockable.?)
For software: Use latest platform-tools from Google. Just Google search "platform-tools" then select Windows (unless on Linux) for adb.exe and fastboot.exe. Put all files mentioned in the OP in this same Directory.
Hello,
I'm posting this guide for those (like me) who can't do without TWRP on their device.
I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP: https://forum.xda-developers.com/t/twrp-3-4-0-0-for-sunfish-testing.4179101/
Credits to @Zackptg5 for his guide, from which I've started: https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
Credits to @topjohnwu for Magisk: https://github.com/topjohnwu/Magisk
DISCLAIMER: I don't take any responsibility if your phone explodes or anything... The guide is provided as is.
FIRST STEP: UNLOCKING THE BOOTLOADER
Download USB drivers for your phone here: https://androidfilehost.com/?fid=8889791610682922010
Download SDK Platform-Tools for Windows here: https://developer.android.com/studio/releases/platform-tools
Extract the SDK Platform-Tools to a directory of your choice.
Open your command prompt, change directory to where you extracted the Platform-Tools and type "fastboot". Depending on your Windows setup (I'm a linux guy, so I've used an ancient win8.1 installation in a VM...) you might receive a message of a missing dll (api-ms-win-crt-convert-l1-1-0.dll): if so, download and install the Universal C Runtime from https://support.microsoft.com/en-us...-windows-c0514201-7fe6-95a3-b0a5-287930f3560c
If you try the "fastboot" command once more, it should now work.
On your phone go to system settings -> About phone -> tap on 'Build number' several times until Developer Options is enabled.
Back out into settings and go to System -> Advanced -> Developer Options -> Enable 'OEM Unlocking'.
Switch off the phone.
Boot into fastboot by holding Vol Down + Power.
Plug the phone into a usb port of your pc.
In your command prompt type "fastboot devices". If there is no output, it means you have to install the USB driver. So, open "Device Manager" on your pc, right click on your Pixel 4A (should be on top of the list with a yellow exlamation mark) and update the driver choosing the USB drivers you previously downloaded. In Device Manger you should now read "Android Bootloader Interface", with no exlamation mark.
Now back to the command prompt, "fastboot devices" should now output a string with "fastboot" written next to it.
Now type 'fastboot flashing unlock' -> Follow prompt on the device to unlock the bootloader (note that this will FACTORY RESET the device).
The bootloader is now unlocked! You can now safely reboot (or it reboots on its own, I don't actually remember).
Note that after you unlock the bootloader you will see a reminder for a few seconds every time you reboot, reminding you that the phone is unlocked. That's normal and we have to live with that, as far as I know.
SECOND STEP: USING THE FACTORY IMAGE TO DOWNGRADE TO ANDROID 10
At present, TWRP is not available for Android 11. So we have to downgrade.
Download A10 factory image (version qd4a.200805.003) here: https://dl.google.com/dl/android/aosp/sunfish-qd4a.200805.003-factory-fac7c08d.zip
If you are paranoid like me, check the SHA-256 checksum of the download with some freeware hashing tool. The SHA-256 checksum should be: fac7c08d3d4cb92078fbcdbcc7e80fc4c438612a1a004d3d12814f51928458f3
Extract the files contained in the downloaded archive into the folder where your fastboot.exe is. To be clear, flash-all.bat should be in the same folder as fastboot.exe.
Place your phone in fastboot mode (Vol Down + Power).
Connect your phone to your PC.
In your command prompt type "fastboot devices" to make sure there is proper connection.
Double click "flash-all.bat".
The phone is going to reboot a few times. Just wait patiently until you read "Press any key to exit..." in the command prompt.
You've now downgraded to Android 10!
THIRD STEP: FLASHING A CUSTOM KERNEL AND TWRP
A custom kernel is needed for TWRP to work, because the stock kernel comes with no LZMA support. Just download the kernel provided by the same developer of TWRP (@nikamura): https://drive.google.com/file/d/1nuXc88t0Iokc0ha-AicOtZEUeGCGwQ-R/view?usp=sharing
And download TWRP, obviously: https://drive.google.com/file/d/1PZaU9PpYmdcAHlyi0zhNwEGnBsAHDW_E/view?usp=sharing
Place both the kernel and TWRP where your fastboot.exe is.
Note that since you just used the factory image you have to boot Android 10 at least once and run the first boot wizard, before you can flash the kernel and TWRP. Also, turn on "USB debug" in Developer Options (see "FIRST STEP" for how to reach Developer Options).
Now, connect your phone to your PC.
In your command prompt type "adb devices". Follow prompt on your phone to permanently allow the adb connection to your pc.
Type the following commands (without quotes):
"adb reboot bootloader"
"fastboot flash boot TKernel-sunfish_V0.1.img"
"fastboot reboot bootloader"
"fastboot boot sunfish_twrp201017-test5.img"
The phone should now boot into TWRP on-the-fly, but it's not been flashed yet.
Place TWRP file on your phone with the following command:
"adb push sunfish_twrp201017-test5.img /sdcard/"
Now in TWRP go to "Install" > "Install Image" > "sunfish_twrp201017-test5.img" > "Install recovery ramdisk" > Swipe.
Now back to the home of TWRP > "Reboot" > "Recovery".
The phone should now boot into TWRP! And this time it's properly installed (not just sideloaded).
You can now reboot into Android 10.
FOURTH STEP: ROOTING WITH MAGISK
Now, you need to grab your current boot image. To do this, boot into TWRP (Vol UP + Power) > "Backup" > flag only "Boot (64MB)" > "Options" tab > unflag "Enable compression" > "Backup" tab > Swipe.
Reboot to Android 10.
Disable "Automatic System Updates" in Developer Options.
Connect phone to PC.
If you browse your phone, in /sdcard/TWRP/BACKUPS/xxxxxxxx/xxxxxxx/ there will be a file named "boot.emmc.win". That's your boot image and you can rename it "boot.img". It should weigh exactly 64MB.
Download Magisk Manager apk (credits @topjohnwu): https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Copy Magisk Manager apk to your device.
Install Magisk Manager apk.
Open Magisk Manager. My locale is not English, so the following commands might slightly differ from what you will see, but still they should be easy to understand. Select 'Install' (Magisk) -> 'Select and Patch File' -> select your boot.img file -> 'Go!' -> it'll output the patched boot image to your Download folder.
Copy the magisk_patched_xxxxxx.img from Download folder to your pc, where your fastboot.exe is.
In your command prompt type:
"adb reboot bootloader"
"fastboot flash boot magisk_patched_xxxxxx.img"
"fastboot reboot bootloader"
You're now rooted!
Enter recovery to make sure TWRP is still working.
Reboot system.
Check in Magisk Manager the resulting installed version of Magisk is 21.4 (=rooted).
This worked great for me - thank you for the post!
Why would you patch the boot.img via Magisk Manager when you can just flash the Magisk v21.4 zip in TWRP?
I;m still confused AF why you would Patch the Boot.img with a working TWRP.img?
BTW: Are you passing safety net, not that it matters, but i figured i'd would on stock Android 10 at least....
Moto_Fan said:
Why would you patch the boot.img via Magisk Manager when you can just flash the Magisk v21.4 zip in TWRP?
Click to expand...
Click to collapse
Yes, that should supposedly work the same, although not personally tested.
Moto_Fan said:
I;m still confused AF why you would Patch the Boot.img with a working TWRP.img?
BTW: Are you passing safety net, not that it matters, but i figured i'd would on stock Android 10 at least....
Click to expand...
Click to collapse
Before flashing TWRP you need custom kernel.
Safetynet is ok, at the moment. Just need to flash this Magisk module: https://github.com/kdrag0n/safetynet-fix/
nor-ric said:
Yes, that should supposedly work the same, although not personally tested.
TESTED AND WORKED PERFECTLY!!!
Before flashing TWRP you need custom kernel.
Safetynet is ok, at the moment. Just need to flash this Magisk module: https://github.com/kdrag0n/safetynet-fix/
Click to expand...
Click to collapse
Yea, I already found out about the module, and it did indeed work and passed safety net after cts profile failed.
Now on too Pixel 4a #2 ON android 12 PDP1, too ROOT or NOT to ROOT??? We'll find out soon enough i guess???
nor-ric said:
Hello,
I'm posting this guide for those (like me) who can't do without TWRP on their device.
I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP: https://forum.xda-developers.com/t/twrp-3-4-0-0-for-sunfish-testing.4179101/
Credits to @Zackptg5 for his guide, from which I've started: https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
Credits to @topjohnwu for Magisk: https://github.com/topjohnwu/Magisk
DISCLAIMER: I don't take any responsibility if your phone explodes or anything... The guide is provided as is.
FIRST STEP: UNLOCKING THE BOOTLOADER
Download USB drivers for your phone here: https://androidfilehost.com/?fid=8889791610682922010
Download SDK Platform-Tools for Windows here: https://developer.android.com/studio/releases/platform-tools
Extract the SDK Platform-Tools to a directory of your choice.
Open your command prompt, change directory to where you extracted the Platform-Tools and type "fastboot". Depending on your Windows setup (I'm a linux guy, so I've used an ancient win8.1 installation in a VM...) you might receive a message of a missing dll (api-ms-win-crt-convert-l1-1-0.dll): if so, download and install the Universal C Runtime from https://support.microsoft.com/en-us...-windows-c0514201-7fe6-95a3-b0a5-287930f3560c
If you try the "fastboot" command once more, it should now work.
On your phone go to system settings -> About phone -> tap on 'Build number' several times until Developer Options is enabled.
Back out into settings and go to System -> Advanced -> Developer Options -> Enable 'OEM Unlocking'.
Switch off the phone.
Boot into fastboot by holding Vol Down + Power.
Plug the phone into a usb port of your pc.
In your command prompt type "fastboot devices". If there is no output, it means you have to install the USB driver. So, open "Device Manager" on your pc, right click on your Pixel 4A (should be on top of the list with a yellow exlamation mark) and update the driver choosing the USB drivers you previously downloaded. In Device Manger you should now read "Android Bootloader Interface", with no exlamation mark.
Now back to the command prompt, "fastboot devices" should now output a string with "fastboot" written next to it.
Now type 'fastboot flashing unlock' -> Follow prompt on the device to unlock the bootloader (note that this will FACTORY RESET the device).
The bootloader is now unlocked! You can now safely reboot (or it reboots on its own, I don't actually remember).
Note that after you unlock the bootloader you will see a reminder for a few seconds every time you reboot, reminding you that the phone is unlocked. That's normal and we have to live with that, as far as I know.
SECOND STEP: USING THE FACTORY IMAGE TO DOWNGRADE TO ANDROID 10
At present, TWRP is not available for Android 11. So we have to downgrade.
Download A10 factory image (version qd4a.200805.003) here: https://dl.google.com/dl/android/aosp/sunfish-qd4a.200805.003-factory-fac7c08d.zip
If you are paranoid like me, check the SHA-256 checksum of the download with some freeware hashing tool. The SHA-256 checksum should be: fac7c08d3d4cb92078fbcdbcc7e80fc4c438612a1a004d3d12814f51928458f3
Extract the files contained in the downloaded archive into the folder where your fastboot.exe is. To be clear, flash-all.bat should be in the same folder as fastboot.exe.
Place your phone in fastboot mode (Vol Down + Power).
Connect your phone to your PC.
In your command prompt type "fastboot devices" to make sure there is proper connection.
Double click "flash-all.bat".
The phone is going to reboot a few times. Just wait patiently until you read "Press any key to exit..." in the command prompt.
You've now downgraded to Android 10!
THIRD STEP: FLASHING A CUSTOM KERNEL AND TWRP
A custom kernel is needed for TWRP to work, because the stock kernel comes with no LZMA support. Just download the kernel provided by the same developer of TWRP (@nikamura): https://drive.google.com/file/d/1nuXc88t0Iokc0ha-AicOtZEUeGCGwQ-R/view?usp=sharing
And download TWRP, obviously: https://drive.google.com/file/d/1PZaU9PpYmdcAHlyi0zhNwEGnBsAHDW_E/view?usp=sharing
Place both the kernel and TWRP where your fastboot.exe is.
Note that since you just used the factory image you have to boot Android 10 at least once and run the first boot wizard, before you can flash the kernel and TWRP. Also, turn on "USB debug" in Developer Options (see "FIRST STEP" for how to reach Developer Options).
Now, connect your phone to your PC.
In your command prompt type "adb devices". Follow prompt on your phone to permanently allow the adb connection to your pc.
Type the following commands (without quotes):
"adb reboot bootloader"
"fastboot flash boot TKernel-sunfish_V0.1.img"
"fastboot reboot bootloader"
"fastboot boot sunfish_twrp201017-test5.img"
The phone should now boot into TWRP on-the-fly, but it's not been flashed yet.
Place TWRP file on your phone with the following command:
"adb push sunfish_twrp201017-test5.img /sdcard/"
Now in TWRP go to "Install" > "Install Image" > "sunfish_twrp201017-test5.img" > "Install recovery ramdisk" > Swipe.
Now back to the home of TWRP > "Reboot" > "Recovery".
The phone should now boot into TWRP! And this time it's properly installed (not just sideloaded).
You can now reboot into Android 10.
FOURTH STEP: ROOTING WITH MAGISK
Now, you need to grab your current boot image. To do this, boot into TWRP (Vol UP + Power) > "Backup" > flag only "Boot (64MB)" > "Options" tab > unflag "Enable compression" > "Backup" tab > Swipe.
Reboot to Android 10.
Disable "Automatic System Updates" in Developer Options.
Connect phone to PC.
If you browse your phone, in /sdcard/TWRP/BACKUPS/xxxxxxxx/xxxxxxx/ there will be a file named "boot.emmc.win". That's your boot image and you can rename it "boot.img". It should weigh exactly 64MB.
Download Magisk Manager apk (credits @topjohnwu): https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Copy Magisk Manager apk to your device.
Install Magisk Manager apk.
Open Magisk Manager. My locale is not English, so the following commands might slightly differ from what you will see, but still they should be easy to understand. Select 'Install' (Magisk) -> 'Select and Patch File' -> select your boot.img file -> 'Go!' -> it'll output the patched boot image to your Download folder.
Copy the magisk_patched_xxxxxx.img from Download folder to your pc, where your fastboot.exe is.
In your command prompt type:
"adb reboot bootloader"
"fastboot flash boot magisk_patched_xxxxxx.img"
"fastboot reboot bootloader"
You're now rooted!
Enter recovery to make sure TWRP is still working.
Reboot system.
Check in Magisk Manager the resulting installed version of Magisk is 21.4 (=rooted).
Click to expand...
Click to collapse
Would like to go this route for reasons you have stated above. Have a few questions:
1: If you use normally use Linux why did you use a Windows VM rather than simply do all operations in a Linux terminal?
2: After the above transition will SU required programs such as Titanium Backup and Adaway install and function as they have in the past? I had previously rooted current P4a and neither of the above programs would install?????
3: Will SuperSuperuser be installed under this environment?
I have rooted several devices in the past using varied methods and things seem to have changed drastically since my previous Nexus 6p
Thanks
CarlInMO said:
2: After the above transition will SU required programs such as Titanium Backup and Adaway install and function as they have in the past? I had previously rooted current P4a and neither of the above programs would install?????
Click to expand...
Click to collapse
I did the above steps and titanium backup, root explorer and other root apps work great.
CarlInMO said:
3: Will SuperSuperuser be installed under this environment?
Click to expand...
Click to collapse
You will NOT use a separate SU app - Magisk has a built-in SU interface that will pop-up and grant SU permission when an app asks for it - just like the old SU app used to do.
JohnC said:
I did the above steps and titanium backup, root explorer and other root apps work great.
You will NOT use a separate SU app - Magisk has a built-in SU interface that will pop-up and grant SU permission when an app asks for it - just like the old SU app used to do.
Click to expand...
Click to collapse
Thanks for the quick response, again!!! I like this phone but it looks at this point as if it has a rather small following here. Are you using the stock build or have you moved on to a custom ROM?
CarlInMO said:
Thanks for the quick response, again!!! I like this phone but it looks at this point as if it has a rather small following here. Are you using the stock build or have you moved on to a custom ROM?
Click to expand...
Click to collapse
Using stock android 10 image from google because TWRP and Edxposed are stable with android 10, not 11.
And what happens to root & TWRP after upgrade back to Android 11. I assume installed apps continue to operate OK
TWRP has now been modded and is working with A11! Details in the TWRP thread!