Hi everyone. My aim here is to present a more clear Tutorial... not sure if i'll succeed, but i want to try. :good: Good Luck. Your results may be different.
A word of Caution: These steps will soft brick the phone and erase all data from your phone. Proceed with caution.
A huge thanks to:
emowing
quyvinh
jemmini
John Hale
kingroot
I refered to these posts when I was rooting:
http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
Download the BLU Vivo XL Backup from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip . This is required to unbrick the phone.
WARNING: THE METHOD I FOLLOWED WILL ERASE ALL DATA ON THE PHONE. I really didn't care for the data on the phone so I didn't create a backup. You could google for steps to make a backup before continuing.
I did these on a Windows 7 machine. I didn't take any screenshots. This was totally random effort.
1. Ensure ADB Universal Drivers, adb.exe and fastboot.exe are installed. Use google search. I used this one http://rootjunkysdl.com/?device=Amazon Fire 5th gen. Even though it is for Amazon 5th gen Fire tablet, it worked for BLU Vivo XL
2. Enable 'Developer Options'
3. Enable 'USB Debugging'
4. Connect the phone to the computer.
If you are doing this for the first time then...
The phone will show up as a new 'cd' drive
Open that and you should see the software to install official drivers for the phone
Install the drivers using that software.
If you have previously connected the phone then it will show up like a 'USB flash storage' device with 2 partitions - Phone and SD Card5. Run 'adb.exe' in command prompt ( i assume you know how to do this)
6. Run adb devices and make sure that adb is able to communicate with the phone.
At some point, there will be a pop up on the phone with a key to enable the computer to securely connect to the phone. I don't know what this is called , but it is needed. Make sure you choose to remember this key permanently on the phone.
7. Root the phone with 'Kingroot' (Yes, this is odd, but this is required to get the TWRP recovery to load)
The reason i say this is needed is because without the root when I tried to install the TWRP recovery i got the error saying that there is no root access and therefore TWRP recovery file cannot be copied to the phone
[a] go to kingroot (dot) net and get the latest kingroot apk
try to root with kingroot. the first time i did this it didn't work. kingroot app said there is 'root' method available but it couldn't root.
[c] i uninstalled kingroot
[d] then i installed purify from play store
[e] rebooted the phone
[f] installed kingroot again and tried root again and this time it worked. (go figure...)
[g] so YMMV.
if you rooted successfully with Kingroot, then you can continue, otherwise.... try again till you can root with kingroot
8. reboot the phone
9. Go to developer options and enable the option - 'Enable OEM Unlock'
CAUTION: The next steps will soft brick your phone.
10. Run adb.exe. check connectivity using command 'adb devices'
11. Run command 'adb reboot bootloader' (this will put the phone in fastboot mode)
12. Make sure the TWRP recovery is in the same folder as the adb.exe file. (get the twrp recovery from here http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601)
13. Run command 'fastboot oem unlock'. At this point, there will be a prompt on the phone to confirm the action. Read it carefully, it clearly says that this process will wipe all data.
14. Press 'volume up' on the phone to confirm. It should take a few seconds. Then the phone will become unresponsive. Pressing volume up/down buttons or power button doesn't do anything.
15. Run command 'fastboot reboot-bootloader'
16. Run command 'fastboot flash recovery recovery.img'
17. Run command 'fastboot reboot'. When the phone is rebooting press volume up. If everything went well, This will put the phone in TWRP recovery mode.
18. When the phone enters TWRP recovery mode, it'll ask for 'write permissions'. I swiped to enable the write permissions.
19. At this point, the phone has no OS.
20. On the PC, extract the files downloaded from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip
21. With the phone connect to the PC and adb running. Run command adb devices. The phone must be listed as 'xxxxxxxxxxxxxxxxx recovery'
22. You will have to push the back up files to twrp backup using adb
23. The general command is 'adb push <local> <remote>'. This is what i did for each of the files. Be patient, this will take time.
adb push "C:\boot.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/boot.emmc.win
adb push "C:\logo.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win
adb push "C:\logo.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win.md5
adb push "C:\nvram.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win
adb push "C:\nvram.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win.md5
adb push "C:\secro.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win
adb push "C:\secro.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win.md5
adb push "C:\system.ext4.win000" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000
adb push "C:\system.ext4.win000.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000.md5
adb push "C:\system.ext4.win001" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win001
24. Once all the files are copied to the phone. Go to TWRP Restore option and then do a restore from the backup you just uploaded 2016-03-05.
25. After the restore is successfull and complete, TWRP will automatically ask to install 'SuperSu'.
26. Choose 'yes' and install SuperSu
27. TWRP will recover the phone and root the phone with SuperSu
If all of the above worked then install Xposed as per instructions in http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
GOOD LUCK !!! :good::good::good:
Please help me on rooting my Blu vivo XL I upgraded it to Android 6.0 and now it does not root. Please help.
hamilLewiston said:
Hi everyone. My aim here is to present a more clear Tutorial... not sure if i'll succeed, but i want to try. :good: Good Luck. Your results may be different.
A word of Caution: These steps will soft brick the phone and erase all data from your phone. Proceed with caution.
A huge thanks to:
emowing
quyvinh
jemmini
John Hale
kingroot
I refered to these posts when I was rooting:
http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
Download the BLU Vivo XL Backup from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip . This is required to unbrick the phone.
WARNING: THE METHOD I FOLLOWED WILL ERASE ALL DATA ON THE PHONE. I really didn't care for the data on the phone so I didn't create a backup. You could google for steps to make a backup before continuing.
I did these on a Windows 7 machine. I didn't take any screenshots. This was totally random effort.
1. Ensure ADB Universal Drivers, adb.exe and fastboot.exe are installed. Use google search. I used this one http://rootjunkysdl.com/?device=Amazon Fire 5th gen. Even though it is for Amazon 5th gen Fire tablet, it worked for BLU Vivo XL
2. Enable 'Developer Options'
3. Enable 'USB Debugging'
4. Connect the phone to the computer.
If you are doing this for the first time then...
The phone will show up as a new 'cd' drive
Open that and you should see the software to install official drivers for the phone
Install the drivers using that software.
If you have previously connected the phone then it will show up like a 'USB flash storage' device with 2 partitions - Phone and SD Card5. Run 'adb.exe' in command prompt ( i assume you know how to do this)
6. Run adb devices and make sure that adb is able to communicate with the phone.
At some point, there will be a pop up on the phone with a key to enable the computer to securely connect to the phone. I don't know what this is called , but it is needed. Make sure you choose to remember this key permanently on the phone.
7. Root the phone with 'Kingroot' (Yes, this is odd, but this is required to get the TWRP recovery to load)
The reason i say this is needed is because without the root when I tried to install the TWRP recovery i got the error saying that there is no root access and therefore TWRP recovery file cannot be copied to the phone
[a] go to kingroot (dot) net and get the latest kingroot apk
try to root with kingroot. the first time i did this it didn't work. kingroot app said there is 'root' method available but it couldn't root.
[c] i uninstalled kingroot
[d] then i installed purify from play store
[e] rebooted the phone
[f] installed kingroot again and tried root again and this time it worked. (go figure...)
[g] so YMMV.
if you rooted successfully with Kingroot, then you can continue, otherwise.... try again till you can root with kingroot
8. reboot the phone
9. Go to developer options and enable the option - 'Enable OEM Unlock'
CAUTION: The next steps will soft brick your phone.
10. Run adb.exe. check connectivity using command 'adb devices'
11. Run command 'adb reboot bootloader' (this will put the phone in fastboot mode)
12. Make sure the TWRP recovery is in the same folder as the adb.exe file. (get the twrp recovery from here http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601)
13. Run command 'fastboot oem unlock'. At this point, there will be a prompt on the phone to confirm the action. Read it carefully, it clearly says that this process will wipe all data.
14. Press 'volume up' on the phone to confirm. It should take a few seconds. Then the phone will become unresponsive. Pressing volume up/down buttons or power button doesn't do anything.
15. Run command 'fastboot reboot-bootloader'
16. Run command 'fastboot flash recovery recovery.img'
17. Run command 'fastboot reboot'. When the phone is rebooting press volume up. If everything went well, This will put the phone in TWRP recovery mode.
18. When the phone enters TWRP recovery mode, it'll ask for 'write permissions'. I swiped to enable the write permissions.
19. At this point, the phone has no OS.
20. On the PC, extract the files downloaded from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip
21. With the phone connect to the PC and adb running. Run command adb devices. The phone must be listed as 'xxxxxxxxxxxxxxxxx recovery'
22. You will have to push the back up files to twrp backup using adb
23. The general command is 'adb push <local> <remote>'. This is what i did for each of the files. Be patient, this will take time.
adb push "C:\boot.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/boot.emmc.win
adb push "C:\logo.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win
adb push "C:\logo.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win.md5
adb push "C:\nvram.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win
adb push "C:\nvram.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win.md5
adb push "C:\secro.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win
adb push "C:\secro.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win.md5
adb push "C:\system.ext4.win000" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000
adb push "C:\system.ext4.win000.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000.md5
adb push "C:\system.ext4.win001" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win001
24. Once all the files are copied to the phone. Go to TWRP Restore option and then do a restore from the backup you just uploaded 2016-03-05.
25. After the restore is successfull and complete, TWRP will automatically ask to install 'SuperSu'.
26. Choose 'yes' and install SuperSu
27. TWRP will recover the phone and root the phone with SuperSu
If all of the above worked then install Xposed as per instructions in http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
GOOD LUCK !!! :good::good::good:
Click to expand...
Click to collapse
..
is this post is about rooting on marshmallow or on lollipop? thank you
Yes
Sent from my chronos_ace using XDA Free mobile app
Yes, is it for marshmallow? Or yes, is it for lollipop? Or does it work for both? Please clarify.
Please help ME my phone vivo v 5 plus root How To
Gungho-sd said:
Yes, is it for marshmallow? Or yes, is it for lollipop? Or does it work for both? Please clarify.
Click to expand...
Click to collapse
From what I've read this would only work for Lollipop, as apparently kingroot no longer works on Marshmallow.
Related
Hello All!
After much frustration with setting up ADB i finally got it working. Everyone said its simple and takes minimal knowledge but when things dont work, nothing really worked. Anyways after 2 hours of research trying to get ADB to work i finally got it all working and wanted to share my knowledge to anyone else that needed help.
This Guide is for windows only. If you are using Mac OS X please go here: ADB For Dummies
If you are using Linux please go here: [HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
Like My Guide(s)? Donate
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
A Rooted HTC Dream (Google G1)
--------------------------------------------------------------------------
Setting up the Android SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\platform-tools
Now,
1. Run SDK Manager.exe located in the android-sdk-windows folder
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
For Android SDK 1.5r7+
1. Run SDK Manager.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\platform-tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
--------------------------------------------------------------------------
Droid Explorer by Camalot
Droid Explorer is a Windows software that will download, install, and setup the android SDK for you all in under a minute so you are ready to go. I use this on a daily basis. This amazing piece of software has tons of plugins and a built in file explorer for all your files on your phone! All you gotta do is download, install, and go!
Download Droid Explorer - Here
Install the program, and let it setup the SDK files for you
Connect your phone
Enjoy!
--------------------------------------------------------------------------
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
--------------------------------------------------------------------------
When Typing just adb in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb root - restarts adb with root permissions
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PDP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
--------------------------------------------------------------------------
Commands that you should know
adb push - Insert file to phone such as Stock.apk to /data/app_s
Code:
adb push <pathtofile.apk> <file system location> - Example: adb push c:\app.apk /data/app
adb pull - Remove file from phone such as Stock.apk from /data/app_s
Code:
adb pull <pathtofile.apk> <path where you want to save it>- Example: adb pull /data/app/Stock.apk C:\
adb install - Install app to phone
Code:
adb install <path to file> - Example: adb install c:/apps/apps2sd.apk
adb uninstall - Uninstall app from phone
Code:
adb uninstall <name of application> - Example: adb uninstall linda.apk
For more ADB Commands go - Here
--------------------------------------------------------------------------
Thats it for ADB! Congrats and if you have any questions please ask me or if anything is missing or not correct please tell me. I got all of this from research and personal experience.
[GUIDE] Fastboot for Noobs
Fastboot
Like My Guide(s)? Donate
Things you need:
New SPL - Download
New Radio - Download
Your Current ROM - CyanogenMod 3.6
SD Card Reader
Rooted G1 Phone
Computer
USB Cable
Patience
---------------------------------------------------------------------------------------
Install Radio FIRST
Download the Radio Update
Rename it to update.zip
Remove your SD Card from your phone and place it in your SD Card Reader
Put the update.zip at the root of your SDcard (root = not in any folder)
Insert your sdcard back into the phone
Turn off your phone (Hold power and press Power Off)
Hold the Home button and then press the power button (Keep holding power)
You will now enter recovery
Open up your keyboard and press Alt-S
Let it finish the update
When done reboot by pressing Home and Back
You should be able to access your Home screen (If its stuck on the Google G1 screen dont panic, just remove your battery for now)
---------------------------------------------------------------------------------------
Installing the new SPL
Note: To update you must have a PVT board. To Check go into fastboot (Power and Camera and check)
Take your SD Card out again and plug it into the pc
Remove the update.zip that you put in there
Download your current Rom or any other ROM that you want. I suggest CyanogenMod 3.6
Download the SPL Update
Rename the SPL Update to update.zip
Remove your SD Card from your phone and place it in your SD Card Reader
Put the update.zip at the root of your SDcard (root = not in any folder)
Insert your sdcard back into the phone
Turn off your phone (Hold power and press Power Off) or put your battery back in and turn it on
Hold the Home button and then press the power button (Keep holding power)
You will now enter recovery
Open up your keyboard and press Alt-S
Let it finish the update
Now it will reboot on its own back to recovery
Reboot again by pressing Home + Back
Your phone will be stuck on the T-Mobile G1 Screen (Again DONT FREAK)
Remove the battery from your phone
Remove your SD Card and plug it back into your computer
Take the ROM that you downloaded and rename it update.zip
Remove the update.zip that was on your SD Card and put this new one it
Put the battery back into your phone
Enter recovery (Home + Power)
Press Alt+s to update
Let it finish
Press Home + Back to reboot
Thats it! You now have your new SPL and Radio
---------------------------------------------------------------------------------------
Getting into Fastboot
Turn off your phone
Hold the back button and keep holding it while turning your phone back on
You should see 3 Android guys on skateboards
You should now be in Fastboot mode!
---------------------------------------------------------------------------------------
Setting up fastboot to work with your computer
Plug your phone in to your computer through USB
You should get a popup that your computer found the ADB Device for fastboot
When it asks you for drivers, make sure u select the option to locate the drivers from your computer yourself
Since you already have your Android 1.5r2 SDK installed, the drivers are in the same place where the ADB drivers are
C:\android-sdk-windows-1.5_r2\usb_driver
Make sure you choose the correct folder depending on your OS
Press ok to install the drivers
Fastboot should now be up and running
---------------------------------------------------------------------------------------
Make sure Fastboot is working
Open up Command Prompt
type the following
Code:
cd C:\android-sdk-windows-1.5_r2\tools === Press Enter
fastboot devices === Press enter, your device should be listed
fastboot shell === You should see a # in the next line
type fastboot and press enter for general commands
---------------------------------------------------------------------------------------
When Typing just fastboot in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
For more fastboot Commands go - Here
---------------------------------------------------------------------------------------
Congrats! You now have Fastboot and ADB up and running!!!
----------------------------------------------------------------------------
Disclamer: I am not liable to any damage that happens to your phone. This is just a guide which you have chosen to follow, so please do not blame me for any damaged phones or bricks.
Nandroid Backup and Restore
Whats is a Nandroid Backup?
Like My Guide(s)? Donate
Nandroid Backup is a tool allowing all rooted g1 users to create a full system backup and restore which, when flashing and testing different roms can be very useful.
----------------------------------------------------------------------------
What You Will Need
A Rooted G1 phone, I suggest with the latest SPL (Guide above to install latest Radio and SPL)
Cyanogen's Pimped Out Recovery Image 1.4 - Download (IMG)
An SD Card with 100mb of free space
A Computer
SD Card reader or USB Cable
----------------------------------------------------------------------------
Installing the New Recovery Image
Download the recovery image from above, you will want the Download (IMG) download
Place the cm-recovery-1.4.img file in the root of your SD Card (Root = not in any folder)
Go back to your phone (Dont forget to unmount)
Open terminal and type in the following
Code:
su (wait for a screen to popup and press "allow")
flash_image recovery /sdcard/cm-recovery-1.4.img
If you have problems with a "no space on device" error, try using fastboot and erasing first:
Code:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
----------------------------------------------------------------------------
Creating a Backup using Nandroid 2.1
Boot up your phone in recovery (Turn off, then turn on while holding Home button)
You will now see your new Cyanogen 1.3.1 + JF recovery screen (YAY!!! )
Scroll down to "nandroid v2.1 backup" and press on it to create your Backup
Let it work, it should take a minute or so
Once its done, your backup is complete and is saved on your sdcard in the "nandroid" folder
Recovering to Your Nandroid Backup
Option 1 (Without a Computer)
Note: This recovery will only recover your latest nandroid backup (the one with the newest timestamp)
Make sure u made a backup and its in the nandroid folder on your sdcard
Boot up your phone in recovery (Turn off, then turn on while holding Home button)
Scroll down to "restore latest backup" and press on it
Let it work
Once its done reboot your phone and you backup will now be restored!
Option 2 (With a computer)
Note: With this option, you can use any nandroid backup that you have made, not just the latest one
1) First go in to your tools folder where you put your SDK 1.5r2 (C:\android-sdk-windows-1.5_r2\tools as reference)
2) Take the files adb.exe fastboot.exe and AdbWinApi.dll (found here - http://sharebee.com/16a06ebb) and place them in C:\WINDOWS\system32
3) Download the Nandroid Backup and Restore GUI made by Markazeh - Here
Extract the folder to your desktop or where ever you can easily find it (I put mine in the SDK folder for easy access)
4) You will need 4 files: Boot.img, System.img , Data.img, and Recovery.img
Place those 4 files in the same folder as the Nandroid Recovery GUI folder you just extracted in step 3
5) Boot your phone into fastboot mode (Turn off the G1 and turn on while holding the BACK button. If you have an older SPL then hold the CAMERA button and press POWER)
6) Once in fastboot (you should see a white screen with three androids on skateboards) plug your phone to your computer via USB. You might have to press the BACK key to turn it into FASTBOOT mode, or follow the on screen prompts.
NOTE: If you dont have the drivers installed please look one post above to setup fastboot
7) Open NANDROID_Recovery_GUI.exe, everything on the left hand side should be "found!"
8) Choose an option from the right to Restore All, Restore all except Recovery, or Restore Data Only. Let the program do its thing.
Once its done you can reboot and all your info from your backup should be restored!
----------------------------------------------------------------------------
Congrats! You now Backed up your phone and will/have restored it!
----------------------------------------------------------------------------
Disclamer: I am not liable to any damage that happens to your phone. This is just a guide which you have chosen to follow, so please do not blame me for any damaged phones or bricks.
Credit:
Haykuro
Cyanogen
JacHero
NeoBlade
Markazeh
makethetick
XDA Community for your support and help
If i have forgot anyone, i am sorry, please tell me and i will add you
Excellent Guide bro. Although I have no need for it, still A++. Might want to include how to do a nandroid restore just a suggestion!
[EDIT]: I think this guide is worthy of a sticky! What do you guys think? ^^
You are the man!!!
Short simple and to the point!!!
0nly if all the guides were like this...
Thanks man!
not sure if this is the right spot or not but ever since I flashed from cy36 to 361 I keep losing my adb connection I have to g1s and while I'm working on one the other one isn't even connected to the computer so I just flashed the hero theme on one and plugged it in usb and tried to do the clock switcher didn't work so I go do a cmd and do an adb devices and there's nothing listed then I do an adb shell and it says error device not found but the computer sees it and the adb driver is loaded along with the mass storage driver and haven't had any problems until now.
PlatinumMOTO said:
not sure if this is the right spot or not but ever since I flashed from cy36 to 361 I keep losing my adb connection I have to g1s and while I'm working on one the other one isn't even connected to the computer so I just flashed the hero theme on one and plugged it in usb and tried to do the clock switcher didn't work so I go do a cmd and do an adb devices and there's nothing listed then I do an adb shell and it says error device not found but the computer sees it and the adb driver is loaded along with the mass storage driver and haven't had any problems until now.
Click to expand...
Click to collapse
You might want to try reinstalling the drivers and the USB Storage devices. That fixed it for me
Did you follow the "Preparing your phone for ADB" steps? and do ^ that suggestion first. lol
Mikey1022 said:
Did you follow the "Preparing your phone for ADB" steps? and do ^ that suggestion first. lol
Click to expand...
Click to collapse
yes I did I've had adb since sdk 1.0 and never had a problem like I said I actually have 1.0 and 1.5 on my computer so that when I root or re root other g1s I do adb but I noticed adb only works on it's version if I had a 1.5 g1 then the 1.0 won't work and same with the other way but that's not the problem I think I found it it's the clock switcher with 361 of Cyan because now I deleted it and restarted and it works just fine and I just tried to do the clock switcher and now it doesn't recognize either g1 again.
push apk via abd while in recovery mode?
Is it possible to use ADB to push apk files to the phone when the phone is in recovery mode? I tried and it didn't work (the files I was trying to replace weren't overwritten), and I'm wondering if it's because I did something wrong, or if it just doesn't work. I have adb working fine otherwise, have used it a bunch, including to push files while the phone was booted normally.
Specifically, I want to push the calendar.apk and calendarprovider.apk (I like the 1x4 calendar widget better than the 2x2). I want to do this in recovery mode so that the calendar isn't running when the file gets overwritten. I keep having calendar problems after pushing the 1x4 widget, and I think the problems are due to the calendar being active when the file gets replaced.
ADB Commands...
First I would like to say I think the guide is great. Though I don't have a lot of use for it, but I have some suggestions to make:
1. List some ADB commands and what they do, specifically how to use them, and what you would use them for. This forum has taught me so much about my phone and linux, but sometimes it was a slow learning process. Working the ADB push/pull feature was confusing when I first started using it.
2. Nandroid Back-ups. I still don't think I am using it correctly. I know there is a guide, but it still seems confusing. Maybe dumb it down a little.
3. Maybe more information on fastboot. I'm not sure exactly what it is or does, seems like just another version of recovery terminal, which from everything I have learned so far, if you can't get to your recovery terminal, you probably won't be able to get to your fastboot either.
ccunningham83 said:
Maybe more information on fastboot. I'm not sure exactly what it is or does, seems like just another version of recovery terminal, which from everything I have learned so far, if you can't get to your recovery terminal, you probably won't be able to get to your fastboot either.
Click to expand...
Click to collapse
Actually, you can access fastboot from the bootloader, so it's available even if the recovery console isn't.
heldc said:
Is it possible to use ADB to push apk files to the phone when the phone is in recovery mode? I tried and it didn't work (the files I was trying to replace weren't overwritten), and I'm wondering if it's because I did something wrong, or if it just doesn't work. I have adb working fine otherwise, have used it a bunch, including to push files while the phone was booted normally.
Specifically, I want to push the calendar.apk and calendarprovider.apk (I like the 1x4 calendar widget better than the 2x2). I want to do this in recovery mode so that the calendar isn't running when the file gets overwritten. I keep having calendar problems after pushing the 1x4 widget, and I think the problems are due to the calendar being active when the file gets replaced.
Click to expand...
Click to collapse
In recovery, nothing is mounted. So in order to push and overwrite the calender and calenderproviders, you have to do this in recovery/adb shell
mount /system/app
After that, You should be able to push the files + overwrite them =]. QQ why do you want to do this inrecovery and not when the phone is turned on and fully functional?o_o
but how many times is bootloader available when recovery console isn't? I understand they are different, but from everything I have seen, if you can get one, you can get the other and if you can't get one, you cant get the other either.
ccunningham83 said:
First I would like to say I think the guide is great. Though I don't have a lot of use for it, but I have some suggestions to make:
1. List some ADB commands and what they do, specifically how to use them, and what you would use them for. This forum has taught me so much about my phone and linux, but sometimes it was a slow learning process. Working the ADB push/pull feature was confusing when I first started using it.
2. Nandroid Back-ups. I still don't think I am using it correctly. I know there is a guide, but it still seems confusing. Maybe dumb it down a little.
3. Maybe more information on fastboot. I'm not sure exactly what it is or does, seems like just another version of recovery terminal, which from everything I have learned so far, if you can't get to your recovery terminal, you probably won't be able to get to your fastboot either.
Click to expand...
Click to collapse
If you type "adb" in terminal you get a whole list of the options and what they do Also what part of nandroid backup don't you understand? Its just booting into recovery and alt+b. I assume you mean nandroid restores right? Drop me a PM maybe I can help you
ccunningham83 said:
but how many times is bootloader available when recovery console isn't? I understand they are different, but from everything I have seen, if you can get one, you can get the other and if you can't get one, you cant get the other either.
Click to expand...
Click to collapse
Its because the boot loader is dependent on the SPL and if you flash the "Danger" SPL which is basically the only one that causes problems, then you have a chance of bricking your phone. In that case, brick = no bootloader no recovery
ccunningham83 said:
but how many times is bootloader available when recovery console isn't? I understand they are different, but from everything I have seen, if you can get one, you can get the other and if you can't get one, you cant get the other either.
Click to expand...
Click to collapse
Well, actually, I recently had just this happen. My fiance got a g1, and somehow in flashing it for him, it ended up without a working recovery console. It wouldn't flash the recovery image from within the OS, so I had to use fastboot to flash the recovery image. So, it's quite possible to have a bootloader and no recovery console.
alritewhadeva said:
In recovery, nothing is mounted. So in order to push and overwrite the calender and calenderproviders, you have to do this in recovery/adb shell
mount /system/app
After that, You should be able to push the files + overwrite them =]. QQ why do you want to do this inrecovery and not when the phone is turned on and fully functional?o_o
Click to expand...
Click to collapse
Ah ha, that's likely the problem, thanks!
Like I said, I want to overwrite a system app, the calendar. Every time I've done this with the phone "fully functional", the app ends up constantly force closing. I suspect this might be due to corruption from overwriting the app while it's running. I'm hoping that if I replace the app when the OS isn't on, the replacement app will work properly.
No problem You could also try replacing the calender app in a ROM and resigin it and then flash it. Have you tried rebooting after replacing the Calender app when the phone is I quote from myself " fully functional "?
I need to get fastboot working to flash the 2708+ radio/hboot combo, for a rom I want to try. No devices show up under fastboot devices (from command prompt), but it does show up under adb devices. I don't have sdk properly installed, for some reason it wont take on my pc. It was a lengthy process getting adb to work a few months ago, I don't even remember what I did. Please help.
make certain the phone is in fastboot and not hboot mode by hitting the back button
you can flash the radio in recovery,attention it has chance to be bricked.
Ok i just recently installed adb for the same reason, i had trouble at first but then i found this video which made everything really easy.
http://www.youtube.com/watch?v=Bg-cGTZE2XI&feature=related
Now adb works on my computer perfectly
once u install adb fastboot is already there, all u have to do is install the correct drivers for fastboot. So this is what you do:
1. turn off your phone and then turn it back on using the back and home button
(this will boot you into bootloader)
2. Now it should some information and it should say FASTBOOT in green letters.
3. If it does, now plugin your usb to your phone and computer and now it will say FASTBOOT USB.
4. NOw that your phone is in fastboot, go to command prompt on your pc to lauch fastboot.
5.If you installed adb using the video above, type cd..
6. again type cd..
7. then type cd android
8. last type cd tools
9. To check if your phone is connected to your computer through fastboot, type fastboot devices.
10. It should show a long number and then connected, this is your device, if it doesnt show this u need to install the correct drivers for fastboot, if it does show your device then fastboot is working and you can use it.
11.If its not working, you need to install the correct drivers.
12. Keep your phone in FASTBOOT USB, Just leave it how it is.
13. Now on your pc, go to start.
14. right click on computer
15. click on properties.
16. click on device manager
17. now find your device, since it doesnt have the correct drivers it should be under other devices.
18. once you find it double click on it.
19. click update drivers, and choose the option that lets you choose the drivers.
20. your pc wiil scan for drivers and if you installed adb correctly, their should be adb interface drivers.
21. choose those drivers.
22. now wait for those drivers to install.
23. ANd there now u have the correct drivers for fastboot!
24. to check if it is working repeat steps 4-9
25. IF it does, You now have fastboot working on both your pc and device!
please hit the "thank you" button
FYI: I am not tech savy at all so bare with me if I sound like a noob/idiot.
I basically formatted my phone from TWRP and I'm thinking there isn't any ROM/UI/kernel?..ect. so it cannot start up (basically stuck on the htc loading screen). My computer detects it but not as a storage device and I can't seem to find a way to access it. I believe I have what i need on my computer but my issue is that i dont know how to get into the internal storage of my htc one because it cannot detect it as a storage device on my computer.
The only trace of it at all i seem to be able to find is in
Control Panel\Hardware and Sound\Devices and Printers
Its called "android 1.0" and when i click on it, it takes me to its properties from device manager.
It says Location: Port_#0001.Hub_#0008
I dont know if any of this info i gave is relevant, if not, let me know what ups.
ray408 said:
FYI: I am not tech savy at all so bare with me if I sound like a noob/idiot.
I basically formatted my phone from TWRP and I'm thinking there isn't any ROM/UI/kernel?..ect. so it cannot start up (basically stuck on the htc loading screen). My computer detects it but not as a storage device and I can't seem to find a way to access it. I believe I have what i need on my computer but my issue is that i dont know how to get into the internal storage of my htc one because it cannot detect it as a storage device on my computer.
The only trace of it at all i seem to be able to find is in
Control Panel\Hardware and Sound\Devices and Printers
Its called "android 1.0" and when i click on it, it takes me to its properties from device manager.
It says Location: Port_#0001.Hub_#0008
I dont know if any of this info i gave is relevant, if not, let me know what ups.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Here is some reading material for you
Bro..I completely understand your predicament..
Just do this step by step
1. Download minimal adb from the internet and install it on your PC.
2. Download twrp image from the internet.this is a recovery loader.
3.copy the image file into the install directory of minimal adb.
4.execute the minimal adb shortcut from your PC.it should open a command prompt.
5.connect your device to the PC via usb.
6. Type this command to check if your device is recognized. "Fastboot devices"
It should show you a device ID..if your device is connected and recognized
7.flash tarp image with this command "fastboot flash recovery <twrp.img>"
8.reboot your device..press and hold volume down at the sametime to get into bootloader.
9.enter recovery.
10.Download any custom rom from htconeroot.com.it will be a zip file.
11. Copy the zip into minimal adb install directory and run this command to push the zip onto your device. "adb push <image file>.zip any name.zip"
12. After this completes you should be able to see this image in the filemanager in twrp.
13.move the zip file into sdcard directory.
14.make sure all options are checked in the mount in twrp
15.install the custom rom from install option in tarp.
This is 3 frantic days of research on the internet bro..
I had a brick in my hand too..got it up and running VIPERONE ROM
Hope you get through this fine
Thank you, i really appreciate the effort! but im stuck on step 6/7. When i typed in fastboot devices, it didn't show any new id. and when i typed fastboot flash recovery twrp.img it says "waiting on device" so im guessing it still didnt detect it. any idea on why this might be happening? thanks
gowda-the-grear said:
Bro..I completely understand your predicament..
Just do this step by step
1. Download minimal adb from the internet and install it on your PC.
2. Download twrp image from the internet.this is a recovery loader.
3.copy the image file into the install directory of minimal adb.
4.execute the minimal adb shortcut from your PC.it should open a command prompt.
5.connect your device to the PC via usb.
6. Type this command to check if your device is recognized. "Fastboot devices"
It should show you a device ID..if your device is connected and recognized
7.flash tarp image with this command "fastboot flash recovery <twrp.img>"
8.reboot your device..press and hold volume down at the sametime to get into bootloader.
9.enter recovery.
10.Download any custom rom from htconeroot.com.it will be a zip file.
11. Copy the zip into minimal adb install directory and run this command to push the zip onto your device. "adb push <image file>.zip any name.zip"
12. After this completes you should be able to see this image in the filemanager in twrp.
13.move the zip file into sdcard directory.
14.make sure all options are checked in the mount in twrp
15.install the custom rom from install option in tarp.
This is 3 frantic days of research on the internet bro..
I had a brick in my hand too..got it up and running VIPERONE ROM
Hope you get through this fine
Click to expand...
Click to collapse
ray408 said:
Thank you, i really appreciate the effort! but im stuck on step 6/7. When i typed in fastboot devices, it didn't show any new id. and when i typed fastboot flash recovery twrp.img it says "waiting on device" so im guessing it still didnt detect it. any idea on why this might be happening? thanks
Click to expand...
Click to collapse
Ok..try this..
Press down on the power and volume down button to enter the default boot loader.
If you hv rooted your phone..it should be showing tampered at the top.
select the fast boot option..
Now connect your phone via usb..
The display name should change to "fastboot usb"
Then again open minimal adb and continue from step 6.
Make sure you have all the htc drivers for Windows installed on your PC.
Windows can automatically download these drivers for you if you don't have them..
All the best
Are you using Windows 8.1?
everything works now, thank you guys. You are all awesome!
somehow I managed to install the OTA MM update that I was holding off until I could unlock, root, blah, blah, blah.
I'm now on 20i.
And it responds to adb (v1.032) and fastboot commands from Terminal on my OSX MacBook Air.
Has anyone "authorized" (aka - fastboot oem unlock) their 811 and flashed TWRP from a Mavs Mac ?
Or do I need to go to my Bootcamp partition to accomplish?
Seems like to should work from Mavs direct, but …….
Bootcamp not needed.
system settings (tap on Build number until it says you’re a developer.)/developer/check oem unlock & USB debug
USB connect to Mac. I use Android File Transfer. I found it less annoying and very fast.
But it will not work with the LG drivers installed. aka LGUnitedMobileMacDriver_v4.23.zip, or LGMobileMacDriver_v5.2.zip, or LGBridge_Mac.dmg.
in Terminal:
adb devices - should reveal the devices serial - LGH811xxxxxxxxx. If not, your Mac and adb/fastboot are not set up properly.
adb reboot bootloader
fastboot devices - should reveal serial again. xxxxxxxx
fastboot oem unlock - this will WIPE the G4s internal SD that comes with the phone.
fastboot getvar unlocked - to confirm unlock
fastboot reboot - and set-up as a new device.
If you're on MM, and you set it up previously, restore should happen automatically upon reboot, after you enter your google or ID, etc.
If it seems to be taking too long, restart.
Make sure you recheck that USB debug is checked in developer options.
and then to flash TWRP and SuperSu so as to root.
Terminal:
adb reboot bootloader
fastboot boot (drag and drop the {I shortened the name of the file after duping} twrp.img into the Terminal window)
This will boot you into a temporary TWRP recovery. (v2.8.7.2)
Install twrp.img (select zip or img button bottom right)
Then install SuperSu 2.6.7.zip.
REBOOT SYSTEM
check root -
Terminal:
adb shell. should get #. if not - su. should get #.
troubleshooting.
May have to re-enter developer mode
sys settings/about/software/more/tap build number 7 times fast.
unplug USB.
Toggle USB debugging in Developer. Should get prompt about RSA.
re-plug USB
adb kill-server
adb devices
If TWRP isn't recognizing your b.u., write a new back-up. This creates the path TWRP wants to see. Copy your old b.u. into the new folder:
TWRP/BACKUPS/LGH811#########/2016-10-23--15-58-36_MRA58K
RenameÂ*the old b.u. the same as the new b.u. and toss the new one.
Reboot Recovery and you now should now able to to restore from the old b.u.
NOTE: Since I am a semi-amateur at unlocking/rooting, this is not independent development. Instead, I noticed these forums don't seem to have a single one-stop guide that lays out the process for safely rooting the latest (9.0.7) Oxygen OS 9.0.7. This process may seem obvious to experts, but for people who are rusty or new to this, I wanted a process that didn't require lots of extra cross-referencing and research. I hope this is ok.
Big thanks to Dameon87 who supplied the patched boot rom, and deserves all the credit for the actual hard work with the patched boot image.
STEP 1: PREPARATION
Check that your phone is on 9.0.7.
On PC: Download patched_boot-9.0.7.img and MagiskManager-v6.0.1.apk from Dameon87's thread ( https://forum.xda-developers.com/oneplus-6t/how-to/9-0-7-patched-magisk-boot-img-t3875498 ) . Download ADB Tools if you don't have them ( https://developer.android.com/studio/releases/platform-tools#download ) and extract to a folder. Copy patched_boot-9.0.7.img to your PC’s ADB root directory (the directory with fastboot.exe and adb.exe).
On phone: Boot into OOS. Navigate to Setup->About Phone. Tap Build Number until you turn on Developer Options.
On phone: Navigate to System->Developer Options. Enable OEM Unlocking and USB Debugging.
STEP 2: UNLOCKING
Connect your phone to your PC. Click ok on the OEM Debugging prompt on your phone.
On PC: Open a command prompt [Windows: Start->type "cmd.exe"], and navigate to the ADB tools directory. Run this command in the command prompt:
Code:
adb reboot bootloader
The phone should reboot to the bootloader.
On PC: When phone finishes rebooting to the bootloader, run this command in the command prompt:
Code:
fastboot oem unlock
IMPORTANT: ALL DATA WILL BE ERASED WHEN YOU DO THIS, INCLUDING ANY PERSONAL DATA, TEXTS, PHOTOS, MUSIC, ETC. If the phone has been used, please move your files off your device first! The phone will take some time to factory reset.
On Phone: Repeat Preparation Steps 3-4 to turn back on OEM Debugging in OOS.
STEP 3: INSTALLING MAGISK
On PC: Copy MagiskManager-v6.0.1.apk to the phone.
On PC: In the command prompt window, run this command (note this .img file should be in the adb.exe and fastboot.exe directory):
Code:
fastboot boot patched_boot-9.0.7.img
Phone will reboot.
On Phone: Use a file manager app to install MagiskManager-v6.0.1.apk (I use Astro or ES, but admittedly there are probably better ones out there).
On Phone: Open the Magisk Manager App, agree to the setup popup, and click install. When prompted, choose Direct Install.
On Phone: Reboot.
On Phone: In the OS, open Magisk Manager again and add MagiskHide exceptions.
This enabled all apps that I typically need SafetyNet for, including Pokemon Go, Netflix and Google Pay, as well as of course all root apps like TItanium Backup.
Again, apologies if this seems basic, but I hope this is useful for some who don't know all of the inner workings of android unlocking and rooting by heart. If you have any improvements, feel free to suggest them.
You need to change adb oem unlock to fastboot oem unlock. Otherwise good job!
Dameon87 said:
You need to change adb oem unlock to fastboot oem unlock. Otherwise good job!
Click to expand...
Click to collapse
Ah, thanks! Fixed.
Does OTA update lock bootloader?
BesoC said:
Does OTA update lock bootloader?
Click to expand...
Click to collapse
No it doesn't, the root will be lost though.
geminium said:
No it doesn't, the root will be lost though.
Click to expand...
Click to collapse
I'm also a semi amateur at unlocking/rooting so I'm the target audience of the OP.
Ready to get my hands dirty and try it out. Last time I rooted it was on my old phone before Magisk was a thing.
I ended up not updating out of laziness.
Does magisk make OTA updates / keeping the phone up to date easier?
What's the best method for doing so if you want to keep your phone rooted?
spudsrus said:
I'm also a semi amateur at unlocking/rooting so I'm the target audience of the OP.
Ready to get my hands dirty and try it out. Last time I rooted it was on my old phone before Magisk was a thing.
I ended up not updating out of laziness.
Does magisk make OTA updates / keeping the phone up to date easier?
What's the best method for doing so if you want to keep your phone rooted?
Click to expand...
Click to collapse
Well there's quite detailed procedure explained on the forum. You'll find easily...
In general, you have to restore images in magisk, then install OOS OTA update, then install magisk to inactive slot... It's one of the easiest steps for keeping root and be up to date .
I've been rooting for almost a decade and I am grateful for this. I don't know why some of these devs always assume you know when their talking about using a PC or running shell commands. Lol. Everyone started as a noob.
Sent from my OnePlus6TSingle using XDA Labs
ScaryBugThing said:
NOTE: Since I am a semi-amateur at unlocking/rooting, this is not independent development. Instead, I noticed these forums don't seem to have a single one-stop guide that lays out the process for safely rooting the latest (9.0.7) Oxygen OS 9.0.7. This process may seem obvious to experts, but for people who are rusty or new to this, I wanted a process that didn't require lots of extra cross-referencing and research. I hope this is ok.
Big thanks to Dameon87 who supplied the patched boot rom, and deserves all the credit for the actual hard work with the patched boot image.
STEP 1: PREPARATION
Check that your phone is on 9.0.7.
On PC: Download patched_boot-9.0.7.img and MagiskManager-v6.0.1.apk from Dameon87's thread ( https://forum.xda-developers.com/oneplus-6t/how-to/9-0-7-patched-magisk-boot-img-t3875498 ) . Download ADB Tools if you don't have them ( https://developer.android.com/studio/releases/platform-tools#download ) and extract to a folder. Copy patched_boot-9.0.7.img to your PC’s ADB root directory (the directory with fastboot.exe and adb.exe).
On phone: Boot into OOS. Navigate to Setup->About Phone. Tap Build Number until you turn on Developer Options.
On phone: Navigate to System->Developer Options. Enable OEM Unlocking and USB Debugging.
STEP 2: UNLOCKING
Connect your phone to your PC. Click ok on the OEM Debugging prompt on your phone.
On PC: Open a command prompt [Windows: Start->type "cmd.exe"], and navigate to the ADB tools directory. Run this command in the command prompt:
Code:
adb reboot bootloader
The phone should reboot to the bootloader.
On PC: When phone finishes rebooting to the bootloader, run this command in the command prompt:
Code:
fastboot oem unlock
IMPORTANT: ALL DATA WILL BE ERASED WHEN YOU DO THIS, INCLUDING ANY PERSONAL DATA, TEXTS, PHOTOS, MUSIC, ETC. If the phone has been used, please move your files off your device first! The phone will take some time to factory reset.
On Phone: Repeat Preparation Steps 3-4 to turn back on OEM Debugging in OOS.
STEP 3: INSTALLING MAGISK
On PC: Copy MagiskManager-v6.0.1.apk to the phone.
On PC: In the command prompt window, run this command (note this .img file should be in the adb.exe and fastboot.exe directory):
Code:
fastboot boot patched_boot-9.0.7.img
Phone will reboot.
On Phone: Use a file manager app to install MagiskManager-v6.0.1.apk (I use Astro or ES, but admittedly there are probably better ones out there).
On Phone: Open the Magisk Manager App, agree to the setup popup, and click install. When prompted, choose Direct Install.
On Phone: Reboot.
On Phone: In the OS, open Magisk Manager again and add MagiskHide exceptions.
This enabled all apps that I typically need SafetyNet for, including Pokemon Go, Netflix and Google Pay, as well as of course all root apps like TItanium Backup.
Again, apologies if this seems basic, but I hope this is useful for some who don't know all of the inner workings of android unlocking and rooting by heart. If you have any improvements, feel free to suggest them.
Click to expand...
Click to collapse
Can you elaborate a bit more on how you got Pokemon Go working.
OS. 9.0.2 Magisk v18. Successfully rooted.
I'm selecting Pokemon Go under Magisk hide. But it still detects it. PoKe will sometimes run for about 30 secs then it gives me the error incompatible os.
Sent from my [device_name] using XDA-Developers Legacy app
Ok I'm new to this as well..I'm trying to understand the patched boot img part...so do u need the patched boot img for whichever oos ur currently running so to install magisk cleanly is that it...also I can't find the tutorial on how to install the ota's after ur rooted to where everything doesn't get erased etc..I need sumone to point me in the right area to look..I found a lil bit on it once but now I can't seem to find it..thx to everyone in this great community for all the time and effort all put into this. It's so easy to overlook all the hard work that gets done behind the scenes..so I just thank u personally for what u do for us...