Hi, I'm trying to follow the instructions here to install Lineage OS on my OnePlus6T device: https://www.howtogeek.com/348545/how-to-install-lineageos-on-android/ but I've run into the following issue. It used to show "recovery_a" before but after a bunch of experiments where I switched the partition, I've finally managed to factory reset the device and re-trying the procedure from the start. "fastboot devices" is able to recognize the device fine. Can someone please help?
(base) ➜ fastboot flash recovery twrp-3.5.0_9-0-fajita.img
Sending 'recovery' (30980 KB) OKAY [ 0.667s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Flow the instructions on the twrp site, works flawless, read carefully and follow them.
OnePlus 6T (fajita)
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Thanks @saint6822, I was able to install the TWRP zip file after
fastboot boot twrp*.img
I then rebooted the device, however now I'm unable to get back into TWRP in order to continue the process of installing Lineage OS. Can someone point to the procedure to install Lineage OS once the TWRP zip file has been installed. I'm able to get into fastboot mode easily but can't boot into TWRP. Thanks!
vv_777 said:
Hi, I'm trying to follow the instructions here to install Lineage OS on my OnePlus6T device: https://www.howtogeek.com/348545/how-to-install-lineageos-on-android/ but I've run into the following issue. It used to show "recovery_a" before but after a bunch of experiments where I switched the partition, I've finally managed to factory reset the device and re-trying the procedure from the start. "fastboot devices" is able to recognize the device fine. Can someone please help?
(base) ➜ fastboot flash recovery twrp-3.5.0_9-0-fajita.img
Sending 'recovery' (30980 KB) OKAY [ 0.667s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Click to expand...
Click to collapse
That doesn't work, because there is no recovery partition, you never flash the the .img on these devices.... Only boot it. That is why there is an installer, it installs the recovery.
Don't use that guide, and back up your data if your phone still boots.
I have a guide here, for the 6T.
I will update it soon, as the latest version of TWRP does work fine with LOS 17.1 and 18.1, doesn't matter. So use the latest version of TWRP.
This post about making your own fastboot ROMs maybe helpful too. Just so you have the latest one. Just in case.
In the guide I I gave you it explains to install the zip file once in twrp after booting with the image to make it permanent. That's why I said follow it carefully. It does work. I am typing this on a 6t that I installed twrp on with that guide.
vv_777 said:
Thanks @saint6822, I was able to install the TWRP zip file after
fastboot boot twrp*.img
I then rebooted the device, however now I'm unable to get back into TWRP in order to continue the process of installing Lineage OS. Can someone point to the procedure to install Lineage OS once the TWRP zip file has been installed. I'm able to get into fastboot mode easily but can't boot into TWRP. Thanks!
Click to expand...
Click to collapse
I beg to differ the guide does work, he didn't follow it, it clearly says once in after booting with the image to flash the zip, thus making it permanent.
OhioYJ said:
That doesn't work, because there is no recovery partition, you never flash the the .img on these devices.... Only boot it. That is why there is an installer, it installs the recovery.
Don't use that guide, and back up your data if your phone still boots.
I have a guide here, for the 6T.
I will update it soon, as the latest version of TWRP does work fine with LOS 17.1 and 18.1, doesn't matter. So use the latest version of TWRP.
Click to expand...
Click to collapse
saint6822 said:
I beg to differ the guide does work, he didn't follow it, it clearly says once in after booting with the image to flash the zip, thus making it permanent.
Click to expand...
Click to collapse
I'm guessing you don't own a 6T? You can't do that on this device. That's immediately how I knew that guide was not right. *** Edit *** I'm just skimming that guide, it appears to say flash the .img file, which is what the OP tried to do. Does it actually say to flash a .zip file? Either way that generic guide is misleading to new users and leads to issues like this.
Another source then, the official maintainer of TWRP for the 6T,
6T TWRP Thread.
I use the old install instructions, and what I recommend, still: (from that thread)
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line (if you want to have it permanently you should flash the installer)
5. If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again
6. Enjoy it
Click to expand...
Click to collapse
Do NOT run fastboot flash, you can not flash the .img file. The OP is lucky it did not work. This used to result in the boot partition needing to be reflashed, and a phone that would not boot.
Edit: in fairness OhioYJ, you are clicking on the link I gave him TWRP's 6t specific site, not the one he was using? If you are and still can't read then see below.
I'm on a 6t typing this that I followed those instructions for. Fastbooted the image and then flashed the zip. So your lack of understanding and knowledge doesn't translate to something not working just your inept abilities to follow instructions. He didn't flash the zip simple as that. Feel free to hold his hand through what ever method you choose just understand blind leading the blind will be fun for you.
Edit: directly from page I gave,
"First download the TWRP zip file directly on your device. If you don't download the zip file to your device first for any reason, you will need to adb push the zip to the device because MTP is not currently working on the OnePlus 6T in TWRP. If you are unable to use adb, you can also use a USB stick with an OTG cable, if you have those handy. Power off the device. Hold volume up to get into fastboot mode. Run this command on your computer: fastboot boot twrp-3.2.1-0-fajita.img
In TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal."
OhioYJ said:
I'm guessing you don't own a 6T? You can't do that on this device. That's immediately how I knew that guide was not right. *** Edit *** I'm just skimming that guide, it appears to say flash the .img file, which is what the OP tried to do. Does it actually say to flash a .zip file? Either way that generic guide is misleading to new users and leads to issues like this.
Another source then, the official maintainer of TWRP for the 6T,
6T TWRP Thread.
I use the old install instructions, and what I recommend, still: (from that thread)
Do NOT run fastboot flash, you can not flash the .img file. The OP is lucky it did not work. This used to result in the boot partition needing to be reflashed, and a phone that would not boot.
Click to expand...
Click to collapse
saint6822 said:
Edit: in fairness OhioYJ, you are clicking on the link I gave him TWRP's 6t specific site, not the one he was using? If you are and still can't read then see below
Click to expand...
Click to collapse
Haha, I see where the confusion came in. I was referring to the OP link, not yours. I wasn't replying to you. I guess I should have quoted that post. That generic howtogeek article won't work on many devices, any of the ones I use on a regular basis actually.
All good, sorry for getting short with you. I'm old and crusty by nature.
OhioYJ said:
Haha, I see where the confusion came in. I was referring to the OP link, not yours. I wasn't replying to you. I guess I should have quoted that post. That generic howtogeek article won't work on many devices, any of the ones I use on a regular basis actually.
Click to expand...
Click to collapse
Just to be clear, I am able to install the TWRP zip file using the instructions from @saint6822 and @OhioYJ that have been
> adb reboot bootloader
> fastboot devices // To confirm device can be viewed
> fastboot boot twrp-3.5.0_9-0-fajita.img
Then I navigate the "Install" and locate the TWRP zip file, namely twrp-installer-fajita-3.2.3-2.zip and that installs fine. My problem arises after that, specifically after selecting Reboot and then Recovery the device reboots into the fastboot menu (i.e. the same menu I saw in the first step with "adb reboot bootloader").
I have no doubt TWRP has been installed on the device (per the installation messages appearing on the screen) but it does *not* boot back into it
Have you tried powering off and holding volume don't when you power it back on to enter recovery?
vv_777 said:
Just to be clear, I am able to install the TWRP zip file using the instructions from @saint6822 and @OhioYJ that have been
> adb reboot bootloader
> fastboot devices // To confirm device can be viewed
> fastboot boot twrp-3.5.0_9-0-fajita.img
Then I navigate the "Install" and locate the TWRP zip file, namely twrp-installer-fajita-3.2.3-2.zip and that installs fine. My problem arises after that, specifically after selecting Reboot and then Recovery the device reboots into the fastboot menu (i.e. the same menu I saw in the first step with "adb reboot bootloader").
I have no doubt TWRP has been installed on the device (per the installation messages appearing on the screen) but it does *not* boot back into it
Click to expand...
Click to collapse
I did, and it does go back to the same bootloader menu (as with "adb reboot bootloader")
The current slot is "B", hopefully that does not make a difference here. I'm also wondering if I should try different TWRP img and zip than above.
Those files worked for me, the latest LineageOs for Microg has it's own recovery (not twrp) you could try going fastboot the twrp.IMG, and from twrp and flash the OS zip before rebooting and call it done and give up on TWRP.
vv_777 said:
The current slot is "B", hopefully that does not make a difference here. I'm also wondering if I should try different TWRP img and zip than above.
Click to expand...
Click to collapse
vv_777 said:
Then I navigate the "Install" and locate the TWRP zip file, namely twrp-installer-fajita-3.2.3-2.zip and that installs fine.
Click to expand...
Click to collapse
Why are you installing such an old version? Is that a typo? That could be your problem. Have you tried the installer for 3.5.0_9-0?
Slot and name don't make a difference. I've never changed the name.
The TWRP site lists the old version at the top and you have to scroll down to the newer version I bet he's not the first to make this mistake.
OhioYJ said:
Why are you installing such an old version? Is that a typo? That could be your problem. Have you tried the installer for 3.5.0_9-0?
Slot and name don't make a difference. I've never changed the name.
Click to expand...
Click to collapse
saint6822 said:
The TWRP site lists the old version at the top and you have to scroll down to the newer version I bet he's not the first to make this mistake.
Click to expand...
Click to collapse
He's not. It took me a while to see it too.
Related
This is what I have done this afternoon.
Use at your own risk, I'm not responsible for any data losing.
Environment: Oneplus One with stock CM11s XNPH30O
Steps:
1. Apply cm-11.0-XNPH25R-bacon-signed.zip from stock recovery.
2. DO NOT BOOT TO OS when update is finished. After updated, press power button until screen off.
3. Boot to fastboot mode by holding 'Power' button & 'Vol UP(+)'.
4. In fastboot mode, boot to custom recovery by
Code:
fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://techerrata.com/browse/twrp2/bacon
5. Make a nandroid backup for data partition. (Optional)
6. Sideload OnePlusOne-BootUnlocker.zip http://forum.xda-developers.com/showpost.php?p=54251992&postcount=1
7. Reboot to bootloader(fastboot mode)
8. Extract cm-11.0-XNPH30O-bacon-signed-fastboot.zip and execute 'flash-radio.sh' to update radio and other binaries.
9. Flash 30O system partition only by
Code:
fastboot flash system system.img
(Don't flash userdata.img or userdata_64G.img or you'll lose all your data.)
10. Reboot. The Bootloader is unlocked.
Sorry for my bad english.
Sick man, gonna try this when i get home
I am running on 33R will this work ???
Or connect to PC.. Adb backup, root, then adb restore
Cool write-up! I re-wrote the guide for use over on the OnePlus forums: https://forums.oneplus.net/threads/...ck-the-bootloader-without-losing-data.103642/
ifg said:
This is what I have done this afternoon.
Use at your own risk, I'm not responsible for any data losing.
Environment: Oneplus One with stock CM11s XNPH30O
Steps:
1. Apply cm-11.0-XNPH25R-bacon-signed.zip from stock recovery.
2. DO NOT BOOT TO OS when update is finished. After updated, press power button until screen off.
3. Boot to fastboot mode by holding 'Power' button & 'Vol UP(+)'.
4. In fastboot mode, boot to custom recovery by
Code:
fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://techerrata.com/browse/twrp2/bacon
5. Make a nandroid backup for data partition. (Optional)
6. Sideload OnePlusOne-BootUnlocker.zip http://forum.xda-developers.com/showpost.php?p=54251992&postcount=1
7. Reboot to bootloader(fastboot mode)
8. Extract cm-11.0-XNPH30O-bacon-signed-fastboot.zip and execute 'flash-radio.sh' to update radio and other binaries.
9. Flash 30O system partition only by
Code:
fastboot flash system system.img
(Don't flash userdata.img or userdata_64G.img or you'll lose all your data.)
10. Reboot. The Bootloader is unlocked.
Sorry for my bad english.
Click to expand...
Click to collapse
Big thanks for this guide. You saved my life. And thanks also to developers for this MOD :good:
---------- Post added at 04:11 PM ---------- Previous post was at 04:05 PM ----------
Dibbyo123 said:
I am running on 33R will this work ???
Click to expand...
Click to collapse
Be sure to read the steps.
philicibine said:
Or connect to PC.. Adb backup, root, then adb restore
Click to expand...
Click to collapse
How would this be done by steps? I'm somewhat familiar with adb {I have the SDK installed and use it for fastboot) but coming from rooting and modding mostly Samsung devices I don't have experience with this method. Could you elaborate in another thread plz? Just the back up and restore part. I can manage the unlock and root.
erad1 said:
How would this be done by steps? I'm somewhat familiar with adb {I have the SDK installed and use it for fastboot) but coming from rooting and modding mostly Samsung devices I don't have experience with this method. Could you elaborate in another thread plz? Just the back up and restore part. I can manage the unlock and root.
Click to expand...
Click to collapse
i used the steps posted here. although they needed adapting for the one.
the bones of it is there though, so if you understand it, its easy to do.
Kind of went a different route but used this as a base and got it done. It was tricky but I'm unlocked, rooted, stock recovery and got most of my data back! Thanks for heads up philicibine and OP.
someone running on 33R succeeded with this MOD ???
Medosofts said:
someone running on 33R succeeded with this MOD ???
Click to expand...
Click to collapse
Yes. I was on 33R. Went to stock recovery and flashed 25R. Booted to fastboot and remotely ran twrp recovery and did a backup (in case) then flashed Bootloader unlock zip. While still in recovery, flashed 33R zip and SuperSU. I didn't extract any fastboot files, just used the flashable stock signed zip. All said and done, I had unlocked bootloader and root and back on 33R.
Now I was able to use Flashify app if I wanted a permanent custom recovery.
ralphwiggum1 said:
Yes. I was on 33R. Went to stock recovery and flashed 25R. Booted to fastboot and remotely ran twrp recovery and did a backup (in case) then flashed Bootloader unlock zip. While still in recovery, flashed 33R zip and SuperSU. I didn't extract any fastboot files, just used the flashable stock signed zip. All said and done, I had unlocked bootloader and root and back on 33R.
Now I was able to use Flashify app if I wanted a permanent custom recovery.
Click to expand...
Click to collapse
Hello did this wipe the device???
also were did you download the 33R from can you please provide me the link.
Thanks
Hilmesh said:
Hello did this wipe the device???
also were did you download the 33R from can you please provide me the link.
Thanks
Click to expand...
Click to collapse
This did NOT wipe my device. Look for the flashable (NOT fastboot) images in this thread.
http://forum.xda-developers.com/showthread.php?t=2857110
ralphwiggum1 said:
This did NOT wipe my device. Look for the flashable (NOT fastboot) images in this thread.
http://forum.xda-developers.com/showthread.php?t=2857110
Click to expand...
Click to collapse
Hello ,
I am on 33 R and downloading the flash-able zip from the thread you gave. The rest of items i have already downloaded (Please see attachment). Request you to please confirm that once my 33R download is complete am i ready to proceed??? (I also have the Complete SDK Package with me)
Also can you please list me the procedure step by step. This is my very first time doing it this way as i am used to rooting my S2 and that is a totally different method using ODIN.
Hope to receive your positive reply.
Ok. Done. It worked flawlessly on 33R. Followed all the steps as mentioned by @ralphwiggum1 (Thanks a lot mate . Also Thanks to @ifg for making the basic post to be followed. See attached Rootchecker image for proof.
Please note that this procedure worked for me on a totally unrooted & never before tried rooting device with 33R. Also my device info showed Tampered bit as True & unlock bit as False. You can check it by following this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Thanks to @Mnt-XDA.
Hilmesh said:
Ok. Done. It worked flawlessly on 33R. Followed all the steps as mentioned by @ralphwiggum1 (Thanks a lot mate . Also Thanks to @ifg for making the basic post to be followed. See attached Rootchecker image for proof.
Please note that this procedure worked for me on a totally unrooted & never before tried rooting device with 33R. Also my device info showed Tampered bit as True & unlock bit as False. You can check it by following this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Thanks to @Mnt-XDA.
Click to expand...
Click to collapse
Good job!
"As every guide is written with a Foreword so is this. Please try at your own risk. I am not responsible."
Next this is neither my guide nor my work. I went through all the threads as mentioned in the various links given below. All I did was follow procedure from whichever thread / post was related with my condition. Once I even got confused with too much information but then again as they if we don’t try we never know whether we would have failed or succeeded.
So I was able to do this only due the works of other people. All the credit & Thanks goes to them. I have tried and remembered and mentioned all the names. In case I have missed anyone please forgive me and point me the name and I will thank them too.
My Step by step procedure to root the device without wipe for devices who have never tried rooting their Oneplus One and are currently on 33R using the method mentioned in this thread,
Download the Recovery flashable zips of the complete ROMz - XNPH25R, XNPH33R
Follow the ADB & Fastboot Installation Procedure listed HERE(Also if you can then do read the complete post as it is very informative for Noobs like me )
Download the Oneplusone-bootunlocker.zip from HERE (Again if possible please read this complete thread too as it is also very informative)
Download the Supersu file from HERE
Download the custom recovery file from HERE
Copy both the Flashable zips, Bootunlocker, supersu files to your device
Switch off your device. And Then boot into STOCK RECOVERY by pressing the VOL DOWN & POWER key
Apply update – XNPH25R and then keep the power key pressed until the screen turns off. DO NOT REBOOT
Now boot to fastboot mode by holding the POWER button & VOL UP Key. Connect it to the PC and let it install all the drivers
Go to the SDK Installation in your PC, and within that go to the folder PLATFORM-TOOLS. Copy the “openrecovery-twrp-2.8.0.1-bacon.img” or latest file which you must have downloaded from the TWRP site
Within the directory Press the Shift Key and right click and you will get an option “Open command Prompt here” – Do it. Type in the command
Code:
Fastboot boot openrecovery-twrp-2.8.0.1-bacon.img
. Wait for 30 Seconds your device will enter into TWRP Custom recovery
Make a Nandroid backup (Optional)
Go to the install option within the recovery and select the Bootunlocker.zip. make sure the signature verification check box in unchecked. Apply the zip.
Now once again go into install option and select the XNPH33R zip and apply
I rebooted the device after Step 14 as I forgot to apply the supersu
Once again followed the same procedure to enter fastboot mode (Step 9) and loaded the custom recovery as mentioned in Step 11 and then applied the supersu zip as mentioned in Step 13. Again rebooted and device was successfully rooted with SuperSU
Next I wanted to flash Franco’s latest Kernel (franco.Kernel-nightly-r20.zip). Downloaded from HERE
Again put device in Fastboot mode (Step 9) and loaded Custom recovery (Step 11) and installed zip file using same procedure as Step 13
Wiped Cache & Dalvik Cache & Rebooted the device. No Issues. Franco Kernel was installed
Credits - I would like to thank everyone for helping me out. Full Thanks & Credits to @ifg (Guide for XNPH300), @Mnt-XDA (Bootunlocker.zip & a great thread about Reset Unlocker & Tamper Bit), @MICa.fighter (CM11S official & untouched image collection), @franciscofranco (Kernel for Oneplus One), Chromium (From Oneplus One Forum for a great guide on Everything Rooting for Oneplus One), @Chainfire (SuperSU), @ralphwiggum1 (for already trying it and clearing my doubts and giving me confidence to proceed)
Worked like a charm. Thanks!
Yeah, I really wish I found this post before I wiped my OPO, and lost another day reinstalling and configuring apps.
Hilmesh said:
"As every guide is written with a Foreword so is this. Please try at your own risk. I am not responsible."
Next this is neither my guide nor my work. I went through all the threads as mentioned in the various links given below. All I did was follow procedure from whichever thread / post was related with my condition. Once I even got confused with too much information but then again as they if we don’t try we never know whether we would have failed or succeeded.
So I was able to do this only due the works of other people. All the credit & Thanks goes to them. I have tried and remembered and mentioned all the names. In case I have missed anyone please forgive me and point me the name and I will thank them too.
My Step by step procedure to root the device without wipe for devices who have never tried rooting their Oneplus One and are currently on 33R using the method mentioned in this thread,
Download the Recovery flashable zips of the complete ROMz - XNPH25R, XNPH33R
Follow the ADB & Fastboot Installation Procedure listed HERE(Also if you can then do read the complete post as it is very informative for Noobs like me )
Download the Oneplusone-bootunlocker.zip from HERE (Again if possible please read this complete thread too as it is also very informative)
Download the Supersu file from HERE
Download the custom recovery file from HERE
Copy both the Flashable zips, Bootunlocker, supersu files to your device
Switch off your device. And Then boot into STOCK RECOVERY by pressing the VOL DOWN & POWER key
Apply update – XNPH25R and then keep the power key pressed until the screen turns off. DO NOT REBOOT
Now boot to fastboot mode by holding the POWER button & VOL UP Key. Connect it to the PC and let it install all the drivers
Go to the SDK Installation in your PC, and within that go to the folder PLATFORM-TOOLS. Copy the “openrecovery-twrp-2.8.0.1-bacon.img” or latest file which you must have downloaded from the TWRP site
Within the directory Press the Shift Key and right click and you will get an option “Open command Prompt here” – Do it. Type in the command
Code:
Fastboot boot openrecovery-twrp-2.8.0.1-bacon.img
. Wait for 30 Seconds your device will enter into TWRP Custom recovery
Make a Nandroid backup (Optional)
Go to the install option within the recovery and select the Bootunlocker.zip. make sure the signature verification check box in unchecked. Apply the zip.
Now once again go into install option and select the XNPH33R zip and apply
I rebooted the device after Step 14 as I forgot to apply the supersu
Once again followed the same procedure to enter fastboot mode (Step 9) and loaded the custom recovery as mentioned in Step 11 and then applied the supersu zip as mentioned in Step 13. Again rebooted and device was successfully rooted with SuperSU
Next I wanted to flash Franco’s latest Kernel (franco.Kernel-nightly-r20.zip). Downloaded from HERE
Again put device in Fastboot mode (Step 9) and loaded Custom recovery (Step 11) and installed zip file using same procedure as Step 13
Wiped Cache & Dalvik Cache & Rebooted the device. No Issues. Franco Kernel was installed
Credits - I would like to thank everyone for helping me out. Full Thanks & Credits to @ifg (Guide for XNPH300), @Mnt-XDA (Bootunlocker.zip & a great thread about Reset Unlocker & Tamper Bit), @MICa.fighter (CM11S official & untouched image collection), @franciscofranco (Kernel for Oneplus One), Chromium (From Oneplus One Forum for a great guide on Everything Rooting for Oneplus One), @Chainfire (SuperSU), @ralphwiggum1 (for already trying it and clearing my doubts and giving me confidence to proceed)
Click to expand...
Click to collapse
Excellent...well done and will help many!
Introduction
Hello everyone, this is a guide to assist you with customizing your Pixel 2! I will be going over installing fastboot and adb, unlocking your bootloader, how to flash the factory images for clean flashes and upgrades, and how to root. Please feel free to ask any questions if you need clarification. Enjoy!
This information has been distilled from Google's official factory image site and the Magisk thread.
Installing fastboot and adb
Thankfully, Google has provided just adb, fastboot, and systrace as a simple zip file, making this process super easy. You MUST be on at LEAST 26.0.2 for the commands in this guide to work. When in doubt, grab the latest copy and install them using the following instructions.
SDK Platform-Tools for Windows
SDK Platform-Tools for Mac
SDK Platform-Tools for Linux
Windows:
Unzip the folder somewhere on your hard drive.
Go to the folder containing the adb and fastboot files and type "cmd" in the path bar at the top.
A command prompt should open with the current folder showing on the prompt.
Type the following commands:
Code:
adb --version
fastboot --version
You should see some information appear. If that is the case, you were successful!
Mac/Linux:
Unzip the folder somewhere on your hard drive.
Navigate to that folder with your terminal.
Run the following commands:
Code:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin
sudo mkdir -p /usr/local/lib64
sudo install lib64/libc++.so /usr/local/lib64
Type the following commands:
Code:
adb --version
fastboot --version
You should see the version information, along with telling you they are installed to /usr/local/bin. If so, you were successful!
Unlocking the bootloader
WARNING: This WILL wipe your entire phone. Please make copies or backups of any important data. This can also go wrong rendering your device inoperable. Proceed with caution.
On your phone, open Settings, navigate to "System" then "About phone", and tap on the build number 7 times.
Go one menu up, click on "Developer options", and turn on USB debugging and OEM unlocking.
In your terminal, type the following command:
Code:
adb reboot bootloader
Run the following command:
Code:
fastboot flashing unlock
Follow the prompts on your device then reboot!
Flashing factory images
NOTE #1: You CANNOT downgrade factory images. Google has prevented users from doing so to keep them safe from vulernabilities that were patched. You should only upgrade or reinstall the current image.
NOTE #2: If you have mounted /system as rw at any point (like in TWRP), you must upgrade using the factory image method. OTAs will fail because they cannot verify the integrity of the disk since its verity data has been changed.
NOTE #3: Flashing the factory images requires an unlocked bootloader. Flashing the OTA zips does not (but if anything goes wrong, you may not be able to recover without an RMA).
Updating to a new release (factory image):
Download the latest factory image from Google's website.
Reboot into the bootloader:
Code:
adb reboot bootloader
Unzip the factory image.
Inside you will see a bootloader image, a radio image, an image zip file, and a couple of flash scripts.
If you are on Windows, open the "flash-all.bat" file in a text editor. If you are on Mac or Linux, open the "flash-all.sh" instead.
Remove the "-w" flag before the fastboot command towards the end of the file. This will prevent fastboot from formatting your device.
Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:
Windows:
Code:
flash-all
Mac/Linux:
Code:
./flash-all.sh
Reboot once it is finished!
Updating to a new release (OTA zip):
Download the latest OTA zip from Google's website
Reboot into recovery:
Code:
adb reboot recovery
Hold down the power button and push volume up
Select "Apply update from ADB"
Run the following command from the folder containing the OTA zip:
Code:
adb sideload <zip_name>.zip
Reboot once it is finished!
Clean flashing a factory image (wipe everything):
Download the latest factory image from Google's website
Reboot into the bootloader:
Code:
adb reboot bootloader
Unzip the factory image.
Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:
Windows:
Code:
flash-all
Mac/Linux:
Code:
./flash-all.sh
Reboot once it is finished!
Rooting with Magisk
NOTE #4: This section assumes you are not going to install TWRP. If you are, skip to the next section and just flash the latest Magisk zip after installing TWRP.
Download the Magisk zip from the official thread and install the manager from the zip.
Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Reboot into the bootloader:
Code:
adb reboot bootloader
Flash the boot image and reboot.
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Open Magisk Manager and you should be rooted!
Installing TWRP
NOTE #5: If you just want to temporarily boot TWRP to flash Magisk and your custom kernel, you can just skip flashing the installer zip in this process.
NOTE #6: TWRP can be unstable at times given the way that security has been set up on this device (lack of decryption, failing to boot, etc).
Download both the TWRP image and zip installer from the official site.
Temporarily boot the TWRP image.
Code:
fastboot boot <path_to_twrp_image>
Flash the TWRP installer zip.
Reinstall Magisk and your custom kernel if you had them.
Reboot and profit!
Common issues
Outdated fastboot/adb: This device requires the latest fastboot and adb binaries to work properly. A lot of common quick adb/fastboot installation guides link to installers that are old. Please manually install the latest using the information at the beginning of the thread!
Using a USB-3.0 or USB-C port: Some newer USB ports do not work with fastboot. Issues manifest as weird errors during a flash. Use a different USB cable/port.
Closing statements
If there are any procedures you would like to see added (like flashing a custom kernel or booting TWRP), I am happy to add them if requested. Also, when requesting help, please be as specific as possible where you get confused. I want this guide to be clear as possible.
Reserved
Reserved
Stuck on this step
Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:
How do I navigate in command prompt? When I typed flash-all, it said it is not a internal command etc. When I dragged and dropped flash-all into the command prompt, it said C:\Users\W Balls\Downloads\SAMPWND_SYSTEMROOT_ADB_FILES>"C:\Users\****** Jim\Downloads\walleye-opd1.170816.025-factory-4752baae\walleye-opd1.170816.025\flash-all.bat"
error: cannot load 'bootloader-walleye-mw8998-002.0059.00.img'
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
error: cannot load 'radio-walleye-g8998-00122-1708311414.img'
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.015s
W/ ( 6448): Unable to open 'image-walleye-opd1.170816.025.zip': No such file or directory
error: failed to open zip file 'image-walleye-opd1.170816.025.zip': I/O Error
Press any key to exit...
You are calling the flash-all.bat out of a differende directory (C:\Users\W Balls\Downloads\SAMPWND_SYSTEMROOT_ADB_FILES) therefore it can't find the system image files since they are located under C:\U sers\****** Jim\Downloads\walleye-opd1.170816.025-factory-4752baae\walleye-opd1.170816.025. Make sure you extract your image to that directory, open up a command promt and navigate to it with "cd C:\Users\W Balls\Downloads\SAMPWND_SYSTEMROOT_ADB_FILES" and call the flash-all.bat from there.
Check out this for basic command line stuff https://www.digitalcitizen.life/command-prompt-how-use-basic-commands
---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------
I tried this and it seems the magisk manager isn't able to download magisk on its own at least on my device:
Code:
DownloadManager: [356] Stop requested with status HTTP_DATA_ERROR: Unable to resolve host "forum.xda-developers.com": No address associated with hostname
DownloadManager: [356] Finished with status WAITING_TO_RETRY
EDIT: Seems like DNS66 was blocking the download patching was scucessfull now.
This is weird, can't I make 2 posts in a row??
Anybody figure out a solution for flashing when on MacOs High Sierra? Platform tools 26.0 1 was a fix for high Sierra, yet 26.0.2 seemed to have lost that commit, so fastboot doesn't work at all. Wondering if it's safe to use 26.0.1 on the pixel 2
nathanchance said:
Flashing factory images
Click to expand...
Click to collapse
First, thanks for putting this together. I've rooted using your method.
Regarding OTA updates: I've read that if we've rooted, we will need to un-root before we can receive an OTA update. Is this always true, or only if we've installed a custom recovery like TWRP? It would be really handy to have a guide on how to un-root, update, then re-root.
Related - let's say that for whatever reason, we have to flash an OTA update manually, rather than actually getting it OTA. Do we lose root by doing so?
Thanks!
JayBlack_686 said:
First, thanks for putting this together. I've rooted using your method.
Regarding OTA updates: I've read that if we've rooted, we will need to un-root before we can receive an OTA update. Is this always true, or only if we've installed a custom recovery like TWRP? It would be really handy to have a guide on how to un-root, update, then re-root.
Related - let's say that for whatever reason, we have to flash an OTA update manually, rather than actually getting it OTA. Do we lose root by doing so?
Thanks!
Click to expand...
Click to collapse
Magisk's OTA section should clear up some of your doubts: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
nathanchance said:
Magisk's OTA section should clear up some of your doubts: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Looks really straightforward, thank you! Might be cool to point to it in the OP. I bet I'm not the only one who was only vaguely aware of the impact that rooting has on how we get OTAs. Then again, maybe everyone else wants to run custom ROMs.
JayBlack_686 said:
Looks really straightforward, thank you! Might be cool to point to it in the OP. I bet I'm not the only one who was only vaguely aware of the impact that rooting has on how we get OTAs. Then again, maybe everyone else wants to run custom ROMs.
Click to expand...
Click to collapse
Good point, I'll add it here in a bit
Sent from my Pixel 2 XL using XDA Labs
OTA vs factory image
Howdy,
really appreciate @nathanchance for putting this together. Would you mind adding a few lines about the differences between OTA and factory images. As a layman i haven't got the foggiest idea which route to go and would appreciate some wisdom. Thanks!
Thank you so much for this guide but can anybody please explain how you can tell which image to patch ?
I am unable to get this to work magisk is showing this message: stock kernel cannot be patched please use a custom kernel
i downloaded: walleye-opd1.170816.010-factory-63083164.zip
unsure as to whether this is correct for my phone as they are quite a few and its unclear how to tell
i have a pixel 2 from the UK that was factory unlocked and i unlocked the boot loader
what am i doing wrong please help
tango650 said:
Howdy,
really appreciate @nathanchance for putting this together. Would you mind adding a few lines about the differences between OTA and factory images. As a layman i haven't got the foggiest idea which route to go and would appreciate some wisdom. Thanks!
Click to expand...
Click to collapse
The primary difference is that the OTA can be flashed on an unlocked bootloader and is designed not to wipe your phone.
UpGrad3 said:
Thank you so much for this guide but can anybody please explain how you can tell which image to patch ?
I am unable to get this to work magisk is showing this message: stock kernel cannot be patched please use a custom kernel
i downloaded: walleye-opd1.170816.010-factory-63083164.zip
unsure as to whether this is correct for my phone as they are quite a few and its unclear how to tell
i have a pixel 2 from the UK that was factory unlocked and i unlocked the boot loader
what am i doing wrong please help
Click to expand...
Click to collapse
Are you supplying the boot image to Magisk? Show me a screenshot of what Magisk says when it tries to patch.
Thanks @nathanchance for this. I'm not a technical person, but can follow directions. This is the 4th phone that I've rooted following directions of some very smart and talented people here on XDA. I don't do this kind of thing everyday, and am not up on programming or coding or whatever you guys call it now days.
All I ended up doing is taking the OTA from Google to the .025. Then followed the Magisk rooting instructions to get root. I had Unlocked it the first day I turned the phone on, I haven't put my SIM in yet, but will play around with it a little more, and finish setting it up,
Again, thanks for the GUIDE to this Pixel 2 phone.
nathanchance said:
The primary difference is that the OTA can be flashed on an unlocked bootloader and is designed not to wipe your phone.
Are you supplying the boot image to Magisk? Show me a screenshot of what Magisk says when it tries to patch.
Click to expand...
Click to collapse
That is what i get. I have even flashed the whole factory image to the phone and still get this
@UpGrad3 you need to extract the boot.img out of your zip (walleye-opd1.170816.010-factory-63083164.zip) file and process this one, I'll guess you tried with the whole zip?? Also you can "attach" pictures to the post and not include the full res with the image tags...
@drmason I did extract the img from the zip. I followed the instructions exactly which is why im so confused as to what is going on ? Ok sorry i will do in future.
Amended post
UpGrad3 said:
@drmason I did extract the img from the zip. I followed the instructions exactly which is why im so confused as to what is going on ? Ok sorry i will do in future.
Amended post
Click to expand...
Click to collapse
You got the boot.img from the zip file that was inside the zip file?
from https://forum.xda-developers.com/showpost.php?p=74429474&postcount=90
Step by step
1. Download and extract factory image. Mine was taimen-opd1.170816.010-factory-c796ddb4.zip
***2. Once extracted go into the folder and extract image-taimen-opd1.170816.010.zip.
There you will find the boot.img.
---------- Post added at 08:36 AM ---------- Previous post was at 08:27 AM ----------
nathanchance said:
Good point, I'll add it here in a bit
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
@nathanchance, one more suggestion for the OP: at one point I was looking at using the stock boot img and couldn't figure out how to get it. Later, I found the below post, where the first two steps are essentially "open the zip inside the zip for the boot.img" to extract the stock boot image. Maybe it's really obvious, but I didn't get it.
https://forum.xda-developers.com/showpost.php?p=74429474&postcount=90
@UpGrad3 you are using the latest Magisk Manager 5.4.1 for this?
JayBlack_686 said:
You got the boot.img from the zip file that was inside the zip file?
from https://forum.xda-developers.com/showpost.php?p=74429474&postcount=90
Step by step
1. Download and extract factory image. Mine was taimen-opd1.170816.010-factory-c796ddb4.zip
***2. Once extracted go into the folder and extract image-taimen-opd1.170816.010.zip.
There you will find the boot.img.
---------- Post added at 08:36 AM ---------- Previous post was at 08:27 AM ----------
this is where i was going wrong i was using a file that had bootloader in the name rather than going into the second zip and finding boot
@nathanchance, one more suggestion for the OP: at one point I was looking at using the stock boot img and couldn't figure out how to get it. Later, I found the below post, where the first two steps are essentially "open the zip inside the zip for the boot.img" to extract the stock boot image. Maybe it's really obvious, but I didn't get it.
https://forum.xda-developers.com/showpost.php?p=74429474&postcount=90
Click to expand...
Click to collapse
drmason said:
@UpGrad3 you are using the latest Magisk Manager 5.4.1 for this?
Click to expand...
Click to collapse
yes i was
although im now stuck on the bootscreen with the G any suggestions ?
Fixed.
incase it happens to anyone else. i restored the factory image again then started the root procedure. im now rooted and fully working
Note: I am no expert at this. I used this to get TWRP and root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader, which will delete all your data. Here's the instructions (If you need help, feel free to post a comment):
Download Magisk's installer zip on your phone from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (Google Pay only works with Magisk v19.0+)
Download arter97's kernel .img to your PC. This kernel currently is the only reliable way to get TWRP. https://forum.xda-developers.com/razer-phone-2/development/arter97-kernel-razer-phone-2-t3914996
Reboot your phone into bootloader mode (Turn off then back on while holding vol down).
Make sure your phone is recognized by Windows before proceeding. Follow this guide to setup the proper drivers and fastboot.
Flash arter97's kernel by running
Code:
fastboot flash boot arter97-kernel-*.img
If you run into any issues, then you will probably need to specify the slot to flash. Reboot back into your system.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a arter97-kernel-*.img
if _b use
Code:
fastboot flash boot_b arter97-kernel-*.img
Reboot to recovery (either through bootloader mode or hold vol up while rebooting).
Install the Magisk .zip from TWRP.
Be amazed by the possibilities.
Old instructions (Should always work to get root):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down) and run
Code:
fastboot flash boot patched_boot.img
.
If you run into any issues, then you will need to specify the slot to flash.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a patched_boot.img
if _b use
Code:
fastboot flash boot_b patched_boot.img
Reboot, and open up magisk manager to confirm everything is working. After an OTA update you may have to re-apply due to it using a different slot.
Note: the phone wasn't properly recognized by my computer when in bootloader mode so I had to install the Google adb drivers and manually set the driver used to Google Bootloader Interface (or something like that)
I found you needed to specify boot_a or boot_b specifically as the bootloader tended to mess up the suffix(it tried "bootb_b"????). So I had to first run "fastboot getvar all" to check the current slot.
I also found the commands are executed much more reliably if you enter the command first and press enter so fastboot goes into the "waiting for device" state and then boot into the bootloader and afterwards plug in the cable so fastboot executes the command as soon as it connects.
figured itd be as easy as that. this will be my first up to date device in years, att sending it to me in the mail. should get it by the 6th . but glad to see theres root! hopefully lineage to follow <3
Twiggy000b said:
figured itd be as easy as that. this will be my first up to date device in years, att sending it to me in the mail. should get it by the 6th . but glad to see theres root! hopefully lineage to follow <3
Click to expand...
Click to collapse
I know the feeling, my last device was the Nexus 5
my last "decent" device was the essential phone. then i went to the xperia xa2 ultra, then the iphone 6 then.... zte quest. -.-
CurtisMJ said:
I found you needed to specify boot_a or boot_b specifically as the bootloader tended to mess up the suffix(it tried "bootb_b"????). So I had to first run "fastboot getvar all" to check the current slot.
I also found the commands are executed much more reliably if you enter the command first and press enter so fastboot goes into the "waiting for device" state and then boot into the bootloader and afterwards plug in the cable so fastboot executes the command as soon as it connects.
Click to expand...
Click to collapse
Lol, bootb_b:laugh:. For me at least it worked fine without specifying the slot, though I may change the instructions to specify the slot
CalebQ42 said:
With the release of the factory images we can achieve root via Magisk boot image patching. Note: I am no expert at this. I used this to achieve root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader. Here's the instructions (If you need help, feel free to post a comment):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down and run `fastboot flash boot patched_boot.img`.
Reboot, and open up magisk manager to confirm everything is working.
Note: the phone wasn't properly recognized by my computer so I had to install the Google adb drivers and manually set the driver to Google Bootloader interface (or something like that)
I also tried to install some Android Pie GSIs, but none of them worked.
Click to expand...
Click to collapse
Does this destroy all data? Do I need to unlock bootloader? Does it matter where I place the boot.img on my device?
CalebQ42 said:
Lol, bootb_b:laugh:. For me at least it worked fine without specifying the slot, though I may change the instructions to specify the slot
Click to expand...
Click to collapse
Interesting. The bootloader isn't exactly what I'd call a masterpiece of coding (weird cause I still maintain the ROM is excellent) so it might have just been a momentary glitch.
---------- Post added at 10:54 PM ---------- Previous post was at 10:53 PM ----------
ctakah27 said:
Does this destroy all data? Do I need to unlock bootloader? Does it matter where I place the boot.img on my device?
Click to expand...
Click to collapse
Yes, yes and not really (you get a file chooser so you just need to locate it)
I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!
CalebQ42 said:
I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!
Click to expand...
Click to collapse
Good luck it's a easier process compare to years ago. I would do it but I have no need for root or custom recovery. If you fail on the TWRP I will do it in time for people.
Is this working on the AT&T version of this phone? Or would you need to flash the global firmware in order for this to work? Looking to upgrade to this phone and I want to be sure I can get root. The rest looks to be coming fairly quickly.
CalebQ42 said:
I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!
Click to expand...
Click to collapse
jonchance_84 said:
Is this working on the AT&T version of this phone? Or would you need to flash the global firmware in order for this to work? Looking to upgrade to this phone and I want to be sure I can get root. The rest looks to be coming fairly quickly.
Click to expand...
Click to collapse
They have the image for AT&T
EAIaIQobChMIwYzbk7j_3gIVRZRpCh0RMwdoEAEYASAAEgLPifD_BwE
Warrior1988 said:
They have the image for AT&T
EAIaIQobChMIwYzbk7j_3gIVRZRpCh0RMwdoEAEYASAAEgLPifD_BwE
Click to expand...
Click to collapse
I see the separate firmware. I'm only asking because of past shadyness from AT&T trying to tell manufacturers what to do. Years ago on my Xperia x10, if on AT&T firmware, you needed to flash the global generic firmware to get around their crap.
CalebQ42 said:
With the release of the factory images we can achieve root via Magisk boot image patching. Note: I am no expert at this. I used this to achieve root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader, which will delete all your data. Here's the instructions (If you need help, feel free to post a comment):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down) and run
Code:
fastboot flash boot patched_boot.img
.
If you run into any issues, then you will need to specify the slot to flash.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a patched_boot.img
if _b use
Code:
fastboot flash boot_b patched_boot.img
Reboot, and open up magisk manager to confirm everything is working. After an OTA update you may have to re-apply due to it using a different slot.
Note: the phone wasn't properly recognized by my computer so I had to install the Google adb drivers and manually set the driver to Google Bootloader interface (or something like that)
I also tried to install some Android Pie GSIs, but none of them worked.
Click to expand...
Click to collapse
Would this procedure be the same as far as mac/win?
I understand all of that, I am simply asking if someone has tried this with the AT&T variant yet. I want to know before I go order this phone.
I love a rooted phone, but as far as I know, if you unlock the bootloader, Netflix will no longer work in HD mode. To me, this is a deal-breaker. If anyone knows about a work-around, I'd love to know.
Razer phone 2 root
so im kinda new to rooting this type of phone and to the android boot scheme in general. i have a razer phone 2 and have attempted (febaly) to root it using this meathod. after installing the google adb drivers i was unable to see the device from my pc when it was in fastboot and unable to send commands, after installing the drivers again with windows update it ran even though no device was detected with this message
">fastboot flash boot patched_boot.img
Sending 'boot_b' (19268 KB) OKAY [ 0.523s]
Writing 'boot_b' OKAY [ 0.179s]
Finished. Total time: 0.718s"
it then blackscreened, i then tried a factory reset from recovery, and it is now in a bootloop... any advice?
update: no longer in boot loop but now is full blackscreen after a glitchy install screen
andy1011 said:
so im kinda new to rooting this type of phone and to the android boot scheme in general. i have a razer phone 2 and have attempted (febaly) to root it using this meathod. after installing the google adb drivers i was unable to see the device from my pc when it was in fastboot and unable to send commands, after installing the drivers again with windows update it ran even though no device was detected with this message
">fastboot flash boot patched_boot.img
Sending 'boot_b' (19268 KB) OKAY [ 0.523s]
Writing 'boot_b' OKAY [ 0.179s]
Finished. Total time: 0.718s"
it then blackscreened, i then tried a factory reset from recovery, and it is now in a bootloop... any advice?
update: no longer in boot loop but now is full blackscreen after a glitchy install screen
Click to expand...
Click to collapse
Since it's already wiped the easiest way to fix it is to probably flash the full factory image. Did you happen to update to the MR2 update prior to following this guide? Doing this on MR2 will soft brick. Not entirely sure in what way, but I assume it would be similar to what you experienced. If you were still on MR0 you can actually just fastboot flash the original kernel image to fix it. I just finished rooting MR2 so I'll post that next
CurtisMJ said:
Since it's already wiped the easiest way to fix it is to probably flash the full factory image. Did you happen to update to the MR2 update prior to following this guide? Doing this on MR2 will soft brick. Not entirely sure in what way, but I assume it would be similar to what you experienced. If you were still on MR0 you can actually just fastboot flash the original kernel image to fix it. I just finished rooting MR2 so I'll post that next
Click to expand...
Click to collapse
this is what im trying to do. however i have no way of flashing to the device as adb is unable to see the device.
andy1011 said:
this is what im trying to do. however i have no way of flashing to the device as adb is unable to see the device.
Click to expand...
Click to collapse
Adb and fastboot are separate things. You should only need download mode and fastboot. What are you trying to use ADB for? If in doubt, the guide on Razer's website should be quite sufficient
EDIT: You can get to download mode by holding Vol Down and Power Button while the device is off. You can force reboot by holding down power for approx 15s as well
Please help me I am stuck. My international version of one plus 6t after Rooting using the oneclick root tool here on XDA my device is rebooting and going into recovery mode - the TWRP isn't installed by itself. Please advise me on what to do. I have important data that i missed to backup so I dont want to do something stupid. Shall I install TWRP with the tool? Is there a way to run the device in safe mode? please advice
Here is a video of me trying to get into the system: https://youtu.be/WZKhjJhivmg
Here is a fastboot info:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No need to panic yet. I don't know about this tool, never used them. What I would do at this point personally is try and boot (BOOT) the TWRP IMG file. That is the first step in TWRP installation. This will get you into TWRP, with a USB cable hooked to the PC you should be able to transfer any data you need.
Then you can try and fix the issue, likely an easy fix. Might be as easy as flashing TWRP, rebooting to recovery and then Magisk. Or you might need to reflash the ROM, but if you do it as is, reflash TWRP, reboot to recovery, flash Magisk, boot, you shouldn't lose anything.
If you aren't sure at this point, ask, as you will lose data if you do the wrong thing. Also the MSM Tool (since I'm sure this will come up) should always be your last resort as that will lock your bootloader. So I always recommend the Fastboot ROM first before that, especially since you have Fastboot working, but try the other stuff first.
a4abbas said:
Please help me I am stuck. My international version of one plus 6t after Rooting using the oneclick root tool here on XDA my device is rebooting and going into recovery mode - the TWRP isn't installed by itself. Please advise me on what to do. I have important data that i missed to backup so I dont want to do something stupid. Shall I install TWRP with the tool? Is there a way to run the device in safe mode? please advice
Here is a video of me trying to get into the system:
Here is a fastboot info:
Click to expand...
Click to collapse
Just fastboot twrp on your phone. Install the installer again. Reboot and, you will be good to go.
OhioYJ said:
No need to panic yet. I don't know about this tool, never used them. What I would do at this point personally is try and boot (BOOT) the TWRP IMG file. That is the first step in TWRP installation. This will get you into TWRP, with a USB cable hooked to the PC you should be able to transfer any data you need.
Then you can try and fix the issue, likely an easy fix. Might be as easy as flashing TWRP, rebooting to recovery and then Magisk. Or you might need to reflash the ROM, but if you do it as is, reflash TWRP, reboot to recovery, flash Magisk, boot, you shouldn't lose anything.
If you aren't sure at this point, ask, as you will lose data if you do the wrong thing. Also the MSM Tool (since I'm sure this will come up) should always be your last resort as that will lock your bootloader. So I always recommend the Fastboot ROM first before that, especially since you have Fastboot working, but try the other stuff first.
Click to expand...
Click to collapse
scorpio76r said:
Just fastboot twrp on your phone. Install the installer again. Reboot and, you will be good to go.
Click to expand...
Click to collapse
Thanks for your reply.
Shall I use this tool here: https://forum.xda-developers.com/on...t-oneplus-6t-using-oneplus-6t-rooter-t3864238 to flash TWRP using this tool:
or you recommend using something else? and what point should I flash it? after going into stock recovery or fastboot screen? One more thing I almost forgot adding that my phone was already rooted but after doing OTA update and then I use the tool to root again which caused me to stuck in this loop of auto power off.
BTW I have set a password on my phone will that cause any issue accessing TWRP if I do manage to flash it? Please advice
a4abbas said:
Please help me I am stuck. My international version of one plus 6t after Rooting using the oneclick root tool here on XDA my device is rebooting and going into recovery mode - the TWRP isn't installed by itself. Please advise me on what to do. I have important data that i missed to backup so I dont want to do something stupid. Shall I install TWRP with the tool? Is there a way to run the device in safe mode? please advice
Here is a video of me trying to get into the system:
Here is a fastboot info:
Click to expand...
Click to collapse
Hello
Try this, it may help you out and you should have twrp back on your phone:
Download "minimal and adb fastboot" to your pc
Find this folder and open it and you should see twrp image in it, rename it "twrp. img"
In a blank space hold shift button and right click to bring up command window.
Once in this window, you should see fastboot. Type "fastboot boot twrp.img" and hit enter.
you should then have twrp on your phone.
Do this and let me know what happens :
Using 'tools' is a bad habit 'cause you don't know what they do.
Read in twrp thread how to install it manually.
The idea is to temporary boot twrp using the .img file in fastboot (fastboot boot twrp.img) then when you're in twrp flash the installer (file name ending with .zip)
Libraplum76 said:
Hello
Try this, it may help you out and you should have twrp back on your phone:
Download "minimal and adb fastboot" to your pc
Find this folder and open it and you should see twrp image in it, rename it "twrp. img"
In a blank space hold shift button and right click to bring up command window.
Once in this window, you should see fastboot. Type "fastboot boot twrp.img" and hit enter.
you should then have twrp on your phone.
Do this and let me know what happens :
Click to expand...
Click to collapse
Exactly, hopefully the member has the twrp installer on his pc so that it can be moved to the device and, installed to maintain twrp after a reboot.
---------- Post added at 11:36 AM ---------- Previous post was at 11:24 AM ----------
Striatum_bdr said:
Using 'tools' is a bad habit 'cause you don't know what they do.
Read in twrp thread how to install it manually.
The idea is to temporary boot twrp using the .img file in fastboot (fastboot boot twrp.img) then when you're in twrp flash the installer (file name ending with .zip)
Click to expand...
Click to collapse
The msm tool is a definite must have if you own a oneplus device. It has saved many lives here, lol
a4abbas said:
BTW I have set a password on my phone will that cause any issue accessing TWRP if I do manage to flash it? Please advice
Click to expand...
Click to collapse
As stated the tool is probably a bad idea. You should install ADB and Fastboot and use these yourself. The password is not an issue at all, TWRP will just ask you for a password and decrypt your data. You just need the correct version of TWRP for your ROM. Most likely you need:
TWRP 3.3.1-6, from here. As mentioned boot the img, using fastboot. Get your data, then try installing TWRP. Do not install the IMG, you install the zip.
Do not use OTA, with a modified device. Use the instructions for TWRP located here. Download the Zip, install in TWRP. Install TWRP again, reboot to recovery again, flash magisk again. The instructions say to uninstall Magisk, and it's probably a good idea to follow the instructions, but personally I never uninstall Magisk. However I don't have a bunch of a mods installed or anything like that.
I've experienced the same and it sounds like you rebooted to a slot without an operational OS
This is what I did. You can also use MSM recovery tool, very handy when you brick
install google SDK platform on your PC if you don't already have it
Download the latest TWRP zip installer and TWRP img boot image, rename them to TWRP.zip and TWRP.img respectively
I create a folder on my C: Drive as ADB and install the contents of the SDK there and the TWRP zip and TWRP img
you can also place your OOS version there, i name mine OOS_90XX.zip
while fastboot screen is open, connect your phone to your PC
Open Command Prompt window
type "cd \ADB"
"adb devices" to ensure that your phone is connected
"fastboot boot TWRP.img"
TWRP should boot
when in TWRP, go to advanced, then ADB sideload
swipe right to intiate sideload
Type "adb sideload TWRP.zip"
after sideload completes, reinitiate sideload
Type "adb sideload OOS9015.zip"
reboot to recovery
you can then reboot to the other slot, repeat steps above and reboot to system
Frozilla said:
You can also use MSM recovery tool, very handy when you brick
Click to expand...
Click to collapse
He's already said he wants to get data off of it. The MSM Tool will wipe the device, and lock the bootloader. The MSM Tool is a handy tool but it should always be a last resort. This device has a working Fastboot, it can very likely be fixed by many other options that don't include locking the bootloader.
OhioYJ said:
He's already said he wants to get data off of it. The MSM Tool will wipe the device, and lock the bootloader. The MSM Tool is a handy tool but it should always be a last resort. This device has a working Fastboot, it can very likely be fixed by many other options that don't include locking the bootloader.
Click to expand...
Click to collapse
Agreed, it's more of a last resort when the device is unresponsive. That's why i said handy when bricked. The steps that I laid out were intended for him to forego that and retrieve his info.
OhioYJ said:
He's already said he wants to get data off of it. The MSM Tool will wipe the device, and lock the bootloader. The MSM Tool is a handy tool but it should always be a last resort. This device has a working Fastboot, it can very likely be fixed by many other options that don't include locking the bootloader.
Click to expand...
Click to collapse
Agreed
Frozilla said:
Agreed, it's more of a last resort when the device is unresponsive. That's why i said handy when bricked. The steps that I laid out were intended for him to forego that and retrieve his info.
Click to expand...
Click to collapse
Yep, and those where great. I just wanted to make sure it was very clear to the OP that the MSM Tool would wipe his data as it would appear the OP is still learning this device, and the MSM Tool has become lots of people's go to, and while it's handy, it needs to be conveyed it should be used only after all other options have been exhausted.
OhioYJ said:
As stated the tool is probably a bad idea. You should install ADB and Fastboot and use these yourself. The password is not an issue at all, TWRP will just ask you for a password and decrypt your data. You just need the correct version of TWRP for your ROM. Most likely you need:
TWRP 3.3.1-6, from here. As mentioned boot the img, using fastboot. Get your data, then try installing TWRP. Do not install the IMG, you install the zip.
Do not use OTA, with a modified device. Use the instructions for TWRP located here. Download the Zip, install in TWRP. Install TWRP again, reboot to recovery again, flash magisk again. The instructions say to uninstall Magisk, and it's probably a good idea to follow the instructions, but personally I never uninstall Magisk. However I don't have a bunch of a mods installed or anything like that.
Click to expand...
Click to collapse
Yo
Thanks for the detailed instructions however the link you have given me only has IMG (twrp-3.3.1-6-fajita.img) Where do I get the TWRP ZIP file and when I follow the link the instructions are different:
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
8. Choose the recoveryimgfilename.img
9. Swipe to install
So I wonder where is the TWRP ZIP part?
I still couldn't find it
a4abbas said:
Yo
Thanks for the detailed instructions however the link you have given me only has IMG (twrp-3.3.1-6-fajita.img) Where do I get the TWRP ZIP file and when I follow the link the instructions are different:
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
So I wonder where is the TWRP ZIP part?
I still couldn't find it
Click to expand...
Click to collapse
There is a thread about twrp in ROM section everything is in there
a4abbas said:
So I wonder where is the TWRP ZIP part?
Click to expand...
Click to collapse
There are two links there, the top one is the IMG file the one marked "installer" is the ZIP file.
I honestly haven't looked at the instructions in quite some time. It appears the new instructions are to avoid the step rebooting to recovery and reflashing Magisk. As if you just flash the recovery ZIP it will wipe out Magisk. I always do the way I listed, I haven't tried it the "new" way. mauronofrio, the developer of TWRP for our device won't steer you wrong. You can do that if you want.
Striatum_bdr said:
There is a thread about twrp in ROM section everything is in there
Click to expand...
Click to collapse
Yes I am trying to follow the TWRP thread here, no where there is mention or link for TWRP.ZIP file the only instruct to flash the IMG file even at the last part. https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
8. Choose the recoveryimgfilename.img
9. Swipe to install
OhioYJ said:
There are two links there, the top one is the IMG file the one marked "installer" is the ZIP file.
I honestly haven't looked at the instructions in quite some time. It appears the new instructions are to avoid the step rebooting to recovery and reflashing Magisk. As if you just flash the recovery ZIP it will wipe out Magisk. I always do the way I listed, I haven't tried it the "new" way. mauronofrio, the developer of TWRP for our device won't steer you wrong. You can do that if you want.
Click to expand...
Click to collapse
Bummer! Sorry about that , just found it
OhioYJ said:
There are two links there, the top one is the IMG file the one marked "installer" is the ZIP file.
I honestly haven't looked at the instructions in quite some time. It appears the new instructions are to avoid the step rebooting to recovery and reflashing Magisk. As if you just flash the recovery ZIP it will wipe out Magisk. I always do the way I listed, I haven't tried it the "new" way. mauronofrio, the developer of TWRP for our device won't steer you wrong. You can do that if you want.
Click to expand...
Click to collapse
By the way, there is a button under the advanced section of TWRP that say "Fix Recovery Bootloop" I wonder if it can help in my case?
UPDATE: Finally I JUST TAP "Fix Recovery Bootloop" AND IT FIXED my **** bootloop and now i can access system without issues :good:
@OhioYJ Thanks so much for directions, Do you have Paypal/LTC/ETH address? I am gonna gift you some $ as appreciation
BTW I am trying to backup with TWRP however I am having "255" error during the backup of Data partition, any ideas how to fix that one?
a4abbas said:
@OhioYJ Thanks so much for directions, Do you have Paypal/LTC/ETH address? I am gonna gift you some $ as appreciation
Click to expand...
Click to collapse
No gift necessary, we're all here to learn and enjoy our devices.
a4abbas said:
BTW I am trying to backup with TWRP however I am having "255" error during the backup of Data partition, any ideas how to fix that one?
Click to expand...
Click to collapse
It most likely has to do with parallel apps / multiple users.
This post here, is from the TWRP thread. (It's at the top of the TWRP main thread, the DEV posted the link)
This post maybe helpful (The first method is what mauronofrio the DEV of our devices TWRP posted a link to, so that would most likely be the route to take)
Hey everyone,
I've been looking for options to Install a custom Rom or root since I bought the Tablet several month ago. It seems like there are some options for the Full Hd Version, but I have a hard time finding anything useful for the 125FU. Are there any recommendations like compatible GSI roms or TWRP/magisk?
Thanks in advance for your help!
You should just be able to install matiek form my understanding
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
holmesmalone said:
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
Click to expand...
Click to collapse
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
art99 said:
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
Click to expand...
Click to collapse
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
I installed corvus os gsi on it. i have no custom recovery.
peteonu said:
I installed corvus os gsi on it. i have no custom recovery.
Click to expand...
Click to collapse
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
holmesmalone said:
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
Click to expand...
Click to collapse
Agreed. I've been looking into compiling TWRP myself but this is all new to me. The only device with TWRP with this chipset is the Redmi 9. I've compared both boot.img's and they are both setup differently. If I had more knowledge ont he subject I could easily achieve this I believe.
If I have time I'll compare Gen 2 vs Gen 3 boot.img's, that may help understand the folder and file structure better.
holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
el7145 said:
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
Click to expand...
Click to collapse
The same process worked for me.
holmesmalone said:
The same process worked for me.
Click to expand...
Click to collapse
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
el7145 said:
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
Click to expand...
Click to collapse
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
holmesmalone said:
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
Click to expand...
Click to collapse
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
el7145 said:
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
Click to expand...
Click to collapse
LMSA. https://pcsupport.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
Use this tool. Install and explore the file and folder structure it creates. Interrupt the process before it flashes your tablet for it will erase the files you need from your computer if you don't. Use trial and error here.
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
el7145 said:
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
Click to expand...
Click to collapse
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Siege9929 said:
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Click to expand...
Click to collapse
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
el7145 said:
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
Click to expand...
Click to collapse
Manually selecting the "Android Bootloader" driver fixed it. Thanks!
I just got my TB125FU to replace my 7-year-old Google Pixel C on its last legs.
Its Hardware ID is USB\VID_0E8D&PID_201C&REV_0100
I found a pack of Mediatek drivers here.
It's a bloated pack, so I extracted just the files needed for the TB125FU and attached to this post.
Once installed, my tablet appeared with a "fastboot devices" command.
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
hugehead83 said:
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
Click to expand...
Click to collapse
just an fyi: thats not the most recent firmware, the lenovo rescue tool had the latest, which at the moment for my device a few days ago was TB125FU_S000118_220927_ROW