Related
Notice: Rooting your device will break OTAs because they require an unmodified system, so you might want to check for updates before rooting your X. However, there is a workaround:
Boot into TWRP via step 5E below, but DO NOT flash it (step 5D)!!
Do a backup of your completely stock, unrooted ROM
Root the device by flashing SuperSU...zip
When an OTA hits, you can get it by doing this:
Boot into TWRP again without flashing it (same as step 1 above)
Restore your stock, unrooted ROM (from step 2 above)
Apply the update from stock recovery
Backup the unmodified ROM with the update if you want, then re-root as above.
Note: You will lose any changes, mods or app data since you did the backup, but hey, at least the OTA is applied.
If you get stuck with an update that won't flash and you haven't backed-up your unrooted ROM as above, look here:
[Guide] How to Install OTA's with TWRP, and please hit thanks for @SpiritBreak3r :good:
_____________________
Disclaimer: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try. If you get confused with terminology, try looking here for answers or Google it. If you get stuck, post a question in the thread—we're here to help you.
Preliminary steps
1. Make sure that your phone is always charged above 50%!!!
Running out of battery in the middle of flashing something could brick your phone.
2. Make sure that your computer can properly communicate with the device:
We will be issuing commands to the phone from your PC via the USB cable using Android’s SDK tools, in particular ADB and fastboot. If you have not done so already, you must install the following on your Windows computer for this to work:
Java runtime
The Universal Android ADB Driver for Windows.
SDK tools for Android (alternately just ADB & fastboot). Remember where this is installed on your harddrive for later!
You can verify the connection between your PC and phone by running the following procedure:
A. With the phone booted normally, connect it to your computer with the USB cable.
B. Enable Android debugging by going to Settings > About phone and tapping on “Build number” 7 times.
C. Go to Settings > Developer options and check “Android debugging”. A dialogue box will appear asking you to authorize your computer’s RSA fingerprint. Click “Always allow...”
{
"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"
}
D. Open a command prompt in Windows and navigate to the folder where you put SDK tools for Android (ADB & fastboot) above.
E. Type the following command:
Code:
adb devices
You should get a return like this:
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
3. Know how to enter “fastboot mode” on the OnePlus X
To root the device, you must be competent at booting it into fastboot mode. There are two ways to accomplish this:
Power off the phone. Then simultaneously hold down the volume up & power buttons until it vibrates. When done correctly, you will see the words “Fastboot Mode” on a black screen. If not, you dumb-thumbed it, and the device will boot normally into Android. Power off the device and try again.
With the phone running Android normally and Android debugging enabled (see above), open a command prompt in Windows, navigate to the folder where you installed SDK tools (ADB & fastboot) and type:
Code:
adb reboot bootloader
Rooting the OnePlus X
There are three essential steps to rooting the device:
Unlock the bootloader
Flash or boot into TWRP custom recovery [For OxygenOS 3.1.3 use TWRP blu_sp★rk r175]
Flash SuperSU...zip from recovery [For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta]
However, we're going to add a few more to protect your data and device in case something gets borked.
1. Backup your phone’s data
Unlocking the bootloader will involve doing a factory reset resulting in the loss of all accounts, emails, texts, apps and app data, pictures, music, etc. on the device. Move anything you need to keep onto your PC or a cloud service like DropBox.
2. Unlock the bootloader
2A.Go into Developer Options and enable bootloader unlocking
2B. Boot the device into fastboot mode. (Simultaneously hold down the volume up & power buttons until it vibrates.) You should see a black screen with the words “Fastboot Mode”.
2C. Plug in the USB cable.
2D. Verify that your device is connected with this command:
Code:
fastboot devices
You should get a return like the image above under Preliminary Steps
2E. Unlock the bootloader using the following commands:
Code:
fastboot oem unlock
The device will unlock the bootloader, erase all user data and reboot itself into Android. You will have to set up everything from scratch.
3. Re-enable Android debugging
3A. Re-enable Developer options by going to Settings > About phone and tapping on “Build number” 7 times.
3B. Go to Settings > Developer options. Check “Android debugging” and re-authorize your computer’s RSA fingerprint.
4. Download SuperSU zip
4A. Head over to Chainfire’s CF-Root thread and download the SuperSU access management tool from the “CWM / TWRP / MobileODIN installable ZIP” link. It will probably called something like UPDATE-SuperSU-v2.XX.zip. This zip file will root your device and install the SuperSU access management app in one smooth motion. Hit the thanks button for Chainfire or donate to his Paypal account and buy him a Coke.
NOTE: For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta
4B. Copy UPDATE-SuperSU-v2.XX.zip to your phone’s SD card.
5. Flash TWRP custom recovery
5A. Download TWRP recovery.
NOTE: For OxygenOS 3.1.3 use TWRP blu_sp★rk r175
5B. Place file you downloaded above to the location where you installed SDK tools (ADB & fastboot).
5C. Boot the device into fastboot mode and connect it to your computer with the USB cable.
5D. In this step, we will replace your stock recovery with TWRP recovery.
Note: This step is optional. If you want to root but preserve stock recovery, skip straight ahead to step 5E below. Thanks @rockuppl for the reminder. :good:
Open a command prompt in Windows and navigate to the folder where you installed SDK tools (ADB & fastboot). Type the following commands:
Code:
fastboot flash recovery twrp-3.0.0-0-onyx.img
5E. Reboot into TWRP recovery with the following command.
Code:
fastboot boot twrp-3.0.0-0-onyx.img
You should now see the custom recovery you just flashed, not the stock recovery.
6. Backup your stock ROM before making any changes
In TWRP press “Backup.” <--- See how simple this is???
Don’t be a noob—backup your device!!! Right now we don't have stock boot debuggable image files for the OnePlus X, so borking your device could leave you with a nice paperweight until we do. :crying: Restoring from a backup in recovery is easy, and only works if you've backed-up first
7. Root the device
7A. The device should still be in recovery from step 6 above. Go back to the main menu and press “Install,” find UPDATE-SuperSU-v2.XX.zip on the SD card, then flash it.
7B. Reboot the phone. It is now rooted!
7C. Go to the app drawer and open SuperSU. Update the binary if prompted. Its icon looks like this:
7D. Download and install Root Checker from the Play Store to verify that you have root access.
Yes I already own the phone and I see the bootloader unlock switch in dev options. I also checked the stock recovery which gives options to flash files from phone memory or otg. So it must be fairly easy. But I still don't want to risk it without it being tried and tested. If there were a custom recovery I could have also backed up the factory image. Only choice is to wait and see I guess
I could try today evening... will update here.
@CafeKampuchia
Is it ok to flash supersu.zip with stock recovery.
Before flashing supersu.zip, will unlock bootloader . Will follow the guide from oneplue two procedure to unlock..
Flashing supersu is safe on hundreds of devices, but I don't have the X so I can't say one way or the other.
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
CafeKampuchia said:
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
Click to expand...
Click to collapse
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Knockys said:
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Click to expand...
Click to collapse
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
CafeKampuchia said:
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
Click to expand...
Click to collapse
My bad then ahah
mjose said:
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Click to expand...
Click to collapse
Yes it fails on stock recovery, we'll have to wait for a custom one indeed...
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Savya said:
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Click to expand...
Click to collapse
Hey i need your help, i installed the custom recovery in Mandarin but i don't understand anything! Could you please tell me where i should go in this recovery to wipe dalvik cache and flash super su? Step by step? Thanks!
Works for me too ! I'll try to install Xposed now ahah !
Hope they'll release TWRP in English soon !
EDIT : Xposed installed and working ! For those who don't know how to do, see here
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
CafeKampuchia said:
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
Click to expand...
Click to collapse
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Savya said:
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Click to expand...
Click to collapse
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
ukanth said:
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
Click to expand...
Click to collapse
Just flashed it now!
Confirmed that its working and its in English!
Thanks a ton mate!
Also do i have your permission to post your link in the oneplus forums? As there are many users there too waiting for an english version.
@ukanth : shared the recovery on my post on the OP forums
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
/*
* Your warranty is (probably) now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about rooting
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* PLEASE READ THE ENTIRE THREAD BEFORE YOU DO ANYTHING!
*/
Please leave a reply if this worked or didn't work. I will be most grateful! Thanks
Hi there!
I present the best, the easiest (mm maybe not) and most proper way to root and flash a custom ROM on your Sony Xperia Z3 Tablet Compact!
Requirements:
- A basic understanding of Rooting and Android Development
- ADB and Fastboot (Have a google for Minimal ADB And Fastboot)
- A windows PC (I am not sure how to root with mac, although I am sure it is the same process)
- OEM Unlocking Enabled on your Device.
Don't know how to enable OEM Unlocking? Do this:
Settings -> About Device -> Tap Build Number 7 Times - Back -> Developer Options -> OEM Unlocking -> Enable
Also, if you ever get a message saying: Allow USB Debugging, do this:
{
"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"
}
We'll start with Unlocking your Boot loader. I might as well point out that this will remove ***ALL*** of your apps and files etc. I should also say that you will lose some capability features - such as the Camera may not be as good - although to be perfectly honest I haven't noticed any changes!
Lets start right away: Bootloader
What is your Bootloader?
Your bootloader is a part of your android device that when unlocked, allows you to do lots of things with it! This includes rooting (Like we are now :laugh, flashing recoveries and more.
Is it safe to do this?
As long as you follow my steps, you should be ok. But I have warned you.
Now head to here. This is the official Bootloader unlocking page. Scroll down to the device selection and put in "Z3 Tablet Compact"
Connect your tablet to your compter,
Do the steps it asks and... done!
Congratulations, your Bootloader is Unlocked!
It may seem silly, but for me, this is the only Hard part!
Now let's flash our TWRP!
Before you do this, make sure you have booted after unlocking your Bootloader. I dont know if it will make a huge difference, but I did it, so you should as well. It worked for me like that
What is TWRP
TWRP is a Custom Recovery
Wow, helpful. :laugh: What's a custom recovery?
As android central say:
In Android, recovery refers to the dedicated, bootable partition that has the recovery console installed. A combination of key presses (or instructions from a command line) will boot your phone to recovery, where you can find tools to help repair (recover) your installation as well as install official OS updates.
This means it is a way of changing things that you can't change if you are booted into System (System is Usual Home screen etc...)
Is TWRP Safe?
It's only ever as safe as you are! - Just make sure you flash (install) the right version!
We start by flashing TWRP.
Head to http://twrp.me and click on Devices. Find specifically YOUR version if the Tablet (scorpion_windy is the NON-LTE Version).
Download it.
Drag that file into an empty folder. Then in the address bar, type "cmd"
A black window should pop up.
In this window, type: adb devices
This should display your device.
Now type: adb reboot bootloader
You should now have a blue light on your device.
You cannot perform adb commands anymore! You now are in Fastboot mode. I dont need to explain that, but you need to know that!
Now type: fastboot flash boot twrp-xxxx-scorpion(_windy).img
Congratulations, TWRP Recovery is now Flashed!
(Provided it says everything is ok. )
Our last step is rooting This is an easy task, but requires TWRP - hence why we installed it.
Grab the latest copy of SuperSU from supersu.com - make sure you get the XPERIA SuperSu - and boot into twrp. (Booting into twrp can be done by mashing volume keys after holding down the power key and it vibrates haha). Press install and find your copy of SuperSU (which you should have loaded onto your tablet beforehand). Swipe to flash, and done!
If your tablet bootloops (doesn't turn on), Install a custom rom. I am currently using: this unofficial lineage (14.1).
To do this, boot into TWRP and press install. Find your Rom file (Like you did for Rooting) and swipe to flash. (Make sure you wipe data, system, cache and dalvik beforehand!). You can now reflash your SuperSU Zip and bam, rooted.
You may also want GApps (Google Apps). So head to opengapps.org and select the right package for you. When you flash GApps, make sure you do right after you flashed the rom (dont boot after flashing your rom.)
When I am flashing something I will normally do this:
TWRP -> Wipe -> Advanced Wipe -> System, Cache, Data, Dalvik Cache -> Back -> Install -> ROM -> Add more Zips -> GApps -> SuperSU -> Back -> Reboot -> Reboot system.
Hopefully, you should now be rooted with a custom rom and all. Enjoy!
I should point out that (At the time of writing this) I am only 12 years old. If I have made a few mistakes, please correct me! Thank you
MajorPlayz said:
Now type: fastboot flash boot twrp-xxxx-scorpion(_windy).img
Click to expand...
Click to collapse
That should be fastboot flash recovery twrp-xxxx-scorpion(_windy).img. As this is the most recent guide I'll post this here, yesterday I decided to wipe my tablet and it turned into a real pita, flashing the recovery partition flashed ok would was real problematic trying to get it to to boot for some reason and in trying to get it to boot I was flashing numerous different files to the phone, but as hate I doing things that way I soldiered on trying to find the cleanest solution and eventually managed it.
These are the steps that I used, my BL is already unlocked...
1. Full clean install of 291.
2. Run my stock kernel through PoC and Rootkernel.
3. Used Rootkernel to add SuperSU and TWRP to the kernel....so now I have a rooted stock 291 with TWRP 3.0.2-0 and my DRM keys intact. To enter TWRP I start pressing the vol+ repeatedly when a yellowish light appears.
XperienceD said:
That should be fastboot flash recovery twrp-xxxx-scorpion(_windy).img. As this is the most recent guide I'll post this here, yesterday I decided to wipe my tablet and it turned into a real pita, flashing the recovery partition flashed ok would was real problematic trying to get it to to boot for some reason and in trying to get it to boot I was flashing numerous different files to the phone, but as hate I doing things that way I soldiered on trying to find the cleanest solution and eventually managed it.
These are the steps that I used, my BL is already unlocked...
1. Full clean install of 291.
2. Run my stock kernel through PoC and Rootkernel.
3. Used Rootkernel to add SuperSU and TWRP to the kernel.
...so now I have a rooted stock 291 with TWRP 3.0.2-0 and my DRM keys intact. To enter TWRP I start pressing the vol+ repeatedly when a yellowish light appears.
Click to expand...
Click to collapse
Well actually I did fastboot flash boot twrp.img
This works perfectly fine for me
XperienceD said:
That should be fastboot flash recovery twrp-xxxx-scorpion(_windy).img. As this is the most recent guide I'll post this here, yesterday I decided to wipe my tablet and it turned into a real pita, flashing the recovery partition flashed ok would was real problematic trying to get it to to boot for some reason and in trying to get it to boot I was flashing numerous different files to the phone, but as hate I doing things that way I soldiered on trying to find the cleanest solution and eventually managed it.
These are the steps that I used, my BL is already unlocked...
1. Full clean install of 291.
2. Run my stock kernel through PoC and Rootkernel.
3. Used Rootkernel to add SuperSU and TWRP to the kernel.
...so now I have a rooted stock 291 with TWRP 3.0.2-0 and my DRM keys intact. To enter TWRP I start pressing the vol+ repeatedly when a yellowish light appears.
Click to expand...
Click to collapse
What's 291 sorry?
MajorPlayz said:
Well actually I did fastboot flash boot twrp.img
This works perfectly fine for me
Click to expand...
Click to collapse
Interesting, might have one last try then, strange though that it uses the same command as flashing the kernel.
MajorPlayz said:
What's 291 sorry?
Click to expand...
Click to collapse
The FW version.
XperienceD said:
Interesting, might have one last try then, strange though that it uses the same command as flashing the kernel.
The FW version.
Click to expand...
Click to collapse
Ok cool
XperienceD said:
Interesting, might have one last try then, strange though that it uses the same command as flashing the kernel.
The FW version.
Click to expand...
Click to collapse
I may be mistaken though, so if it bricks the device, use Sony's Emma flash tool
It's a pretty useful tool (if you don't have just Google: Sony Emma)
MajorPlayz said:
I may be mistaken though
Click to expand...
Click to collapse
Just tried it on the off chance it might work but doesn't, it just writes the recovery to the boot partition so will only boot to TWRP, just flashed the recovery partition again and now not getting any light. It's a strange one this, going to stick my method.
XperienceD said:
Just tried it on the off chance it might work but doesn't, it just writes the recovery to the boot partition so will only boot to TWRP, just flashed the recovery partition again and now not getting any light. It's a strange one this, going to stick my method.
Click to expand...
Click to collapse
Weird ?
I'm using the SGP612 So there might be a difference? I'm assuming your using 621 (You mentioned PoC)
My friend did the command but he told me that is what it was. I'll grab the full list of commands from him, but flashing twrp was definitely to boot!
Nevermind haha!
MajorPlayz said:
Weird
I'm using the SGP612 So there might be a difference? I'm assuming your using 621 (You mentioned PoC)
Click to expand...
Click to collapse
SGP611, I just don't get it.
XperienceD said:
SGP611, I just don't get it.
Click to expand...
Click to collapse
Weird
For those with any trouble and that can't flash twrp, a full procedure for injecting TWRP into the kernel is here:
https://forum.xda-developers.com/showpost.php?p=74528751&postcount=22
Just out of curiosity, about how much battery power does it take to flash the custom ROM to solve the bootloop problem (which happened to me) and are there any other ways of flashing a custom ROM that do not consume battery power?
Ishtvan said:
Just out of curiosity, about how much battery power does it take to flash the custom ROM to solve the bootloop problem (which happened to me) and are there any other ways of flashing a custom ROM that do not consume battery power?
Click to expand...
Click to collapse
Hi there, sorry for long reply - I've been inactive for quite a while as I didn't have a device to hack with. My tablet unfortunately died!
Anything done on a device, whether it be playing games, streaming media, or using TWRP Recovery will consume Battery.
The un-bootloop problem will take charge from your device, but it is safe to keep the device plugged in, charging, whilst you perform the commands.
If all else fails, use Emma as I mentioned before.
hi,
Following this "how-to" everything fine till end of bootloader unlock.
going under developper option, and can't find OEM unlock
trying to make :
Code:
fastboot flash boot twrp-3.0.2-0-scorpion_windy.img
[sudo] Mot de passe de youb*:*
target didn't report max-download-size
sending 'boot' (12372 KB)...
OKAY [ 0.410s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.413s
Trying under linux and then window 7, same error
I ticked usb debug and paired with my laptop.
don't know what to do now ( I'm under firm 23.5.A.1.291)
edit:
ok working, reflash same firmware (us version) and then flash this kernel
glimmling said:
Hi,
I made a boot.img for the SGP612 [6.0.1] [23.5.A.1.291] unlocked BL.
Sony RIC disabled
TWRP 3.0.2
(DRM fix)
Root and Xposed is NOT included. I recommend flashing Magisk v12 later in TWRP and enable Magisk Core Only Mode and Magisk Hide in the settings. Then it will pass the SafetyNet test and you can use su.
To flash the boot.img, put your SGP612 into fastboot mode (Volume Up + connect USB) and then run:
Code:
fastboot flash boot boot.img
If you have a backup of your TA partition, before you unlocked, see the rootkernel thread by tobias.waldvogel, how the DRM fix works.
Thanks to codfx for give me the idea for a SGP612 counterpart and to tobias.waldvogel for his tool :good:
Click to expand...
Click to collapse
from https://forum.xda-developers.com/z3-tablet-compact/development/kernel-t3472019/page2
hazote said:
hi,
Following this "how-to" everything fine till end of bootloader unlock....
Click to expand...
Click to collapse
Where you able to get this working?
Sorry for the very late reply.
Here you find some more details incl. Magisk root instructions: https://forum.xda-developers.com/showpost.php?p=78588234&postcount=14
Hello, i hope people will be able to help me, i've been stupid and tried rooting my tablet without the necessary knowledge , from what i understood i flashed twrp on boot instead of recovery and now i can't use my tablet at all.
Is there a way to get the old system back ?
lacarte said:
Hello, i hope people will be able to help me, i've been stupid and tried rooting my tablet without the necessary knowledge , from what i understood i flashed twrp on boot instead of recovery and now i can't use my tablet at all.
Is there a way to get the old system back ?
Click to expand...
Click to collapse
Have you tried Flashtool: http://www.flashtool.net/index.php ?
{
"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"
}
DISCLAIMER:
I'm not responsible for any damaged watches or other broken things! All of this is still heavily in development and mainly a developer release, not at all recommended for normal usage!
The following tutorial CAN brick your watch if you're not careful enough! Once again I'm not taking any responsibility!
This has only been tested on Android N so far, Android O is not yet fully tested!
---------------------------------------------------------
Please read before doing anything:
This is a port of TWRP for the Ticwatch E. Currently we're not able to boot it via fastboot (well, it technically does but there's an issue with the video driver) and when trying to flash it the watch will instantly flash the stock recovery over it upon reboot.
To avoid this we have to do a little workaround! Once you reboot your watch it'll restore the stock recovery again! After following these steps your watch will be stuck in a bootloop which we'll fix too tho.
Please keep the Changelog below in mind and read what's working and what's not before asking. We may or may not have seen this issue before already.
Files you'll need:
v003 of "TWRP for Ticwatch E" (and most likely S) - OneDrive Mirror
Stock Recovery for Ticwatch E (and most likely S) - OneDrive Mirror
ADB and Fastboot drivers installed (I recommend "15 Seconds ADB Installer")
Changelog:
Updated Instructions:
Slightly updated the instructions so you won't lose any data if you're already on an bootloader unlocked watch!
v003 (OneDrive Mirror):
Managed to make TWRP persistent! Check Instructions on how to.
v002 (OneDrive Mirror):
Now includes systemless root package inside the TWRP image so you're able to root your watch!
v001 (OneDrive Mirror):
Initial release, no ADB so far. Can't be booted from fastboot directly either due to weird fastboot behavior and has to be flashed first. However upon normal reboot Mobvoi decided to flash over the stock recovery again so we have to do a workaround.
Instructions:
The new Instructions by Luxios require a few less steps AND if you've already unlocked your watch before you won't even lose data!
Enable ADB in the Developer Settings
Once done connect your watch to your computer and do "adb reboot bootloader"
THIS WILL RESET YOUR WATCH:*Once in fastboot mode type "fastboot oem unlock" (if you already have an unlocked bootloader you [font=Verdana, Arial, Helvetica, sans-serif]can skip this[/font])
Follow the on-screen instructions on your watch to unlock it (if you already have an unlocked bootloader you can skip this)
Reboot via "fastboot reboot" and wait until Android Wear fully starts up
One started reboot to the bootloader via the same command as above
Once the bootloader shows up again type "fastboot flash recovery TWRP_TicwatchE_v003.img"
After that type "fastboot oem reboot-recovery" to reboot to the TWRP recovery
In order to make TWRP persistent you need to go to "Install" > "Install ZIP" > "supersu" > "TicwatchE_TWRP_keeper.zip" and flash it
Upon rebooting you may notice it'll get stuck in an infinite TWRP bootloop. To fix this boot into TWRP, then choose "Reboot" > "Bootloader", back in fastboot type "fastboot boot StockRecovery_TicwatchE.img" and wait a few seconds, a few reboots later Android Wear should start right up again.
If you want to root your watch reboot it once again with "adb reboot recovery" and go to the same folder as above, tho this time flash "SuperSU-2.79-wear_systemless.zip"
Unroot/Remove TWRP for Android O Update:
Go to this thread to also update directly to the last Android O update and revert all customizations: https://forum.xda-developers.com/sm...es/android-o-super-easy-ticwatch-e-s-t3789835
Have fun!
You're the best! I'm gonna try as soon as I can, and let you know.
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Piereligio said:
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Click to expand...
Click to collapse
If your bootloader is (or was) already unlocked you have to lock and then unlock it again for it to work.
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Piereligio said:
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Click to expand...
Click to collapse
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Sadly it looks like SuperSU failed to root. It gave a data partition mounting error at the end of the script, don't know if it is normal. TWRP isn't able to mount data either.
EDIT: Looks like I found a way to boot TWRP without having to lock/unlock bootloader.
Doing this, I managed to boot TWRP after setting the watch up, and in this way, it didn't fail to mount /data. Let's see...
EDIT2: now SuperSU still fails, but for a different reason. I'm gonna ensure that it failed though.
EDIT3: su command responded, so seems that root works. I'll do some more tests.
TWRP is now persistent! Check the updated guide
Rooting succeeded!
Seems like I managed to root the smartwatch using the version 2. For the moment I'm happy like this, next times I'll indeed use new procedures.
EDIT: Yes, I rooted it.
My steps (the ones on OP are the recommended ones):
-Bootloader unlock;
-Boot in Android Wear to enable ADB from Settings;
-Reboot in bootloader with "adb reboot bootloader";
-Flashed this TWRP v2;
-"fastboot reboot", then "adb reboot recovery" as soon as adb was detected while booting.
In this way I managed to avoid the system to flash stock recovery over TWRP.
By the way, I don't recommend my way of rooting it, it's less safe, just follow the updated instructions in OP.
Huge thanks to @EpicLPer
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
You can flash again the stock recovery with spflash tool.
EpicLPer said:
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
Click to expand...
Click to collapse
I really wish I knew what. All I did was flash a bad recovery, pretty sure something was was wrong with the ram disk. All I get is the splash logo for 3 seconds and a brief vibrate.
Luxios said:
You can flash again the stock recovery with spflash tool.
Click to expand...
Click to collapse
I think I need a scatter file to even get started. I've never used the tool so any other instructions would be greatly appreciated.
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
elios93 said:
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
Click to expand...
Click to collapse
I have the same problem...
EDIT: I have a Ticwatch S.
Niktendo said:
I have the same problem...
EDIT: I have a Ticwatch S.
Click to expand...
Click to collapse
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
elios93 said:
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
Click to expand...
Click to collapse
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
EpicLPer said:
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Click to expand...
Click to collapse
Can you get me the device tree or at least BoardConfig.mk used for this? I have a working watch (still working on recovering the old one) and I think I can get the rest of the partitions working but I would really like to avoid any more mistakes.
Luxios said:
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
Click to expand...
Click to collapse
That 'fastboot oem reboot-recovery' command sure is a nice find!
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
hassanabid94 said:
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
Click to expand...
Click to collapse
Maybe it's a specific developer unit. Don't do anything with it yet, we could loom further into this if it is something special.
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)
Hello,
I am new to phone rooting/modding, this is my first time trying to install a custom ROM (lineageOS) to my OnePlus 8 Pro.
First, I followed this guide for rooting, installing TWRP and then Magisk. The only different thing that I did was, when flashing TWRP, not usingfastboot flash recovery twrp-image-filename.img, but fastboot flash recovery_a/b twrp-image-filename.img, because I read that the former may lead to a boot loop.
Everything worked. Then I proceeded to Install LineageOS on instantnoodlep, where it said I needed to upgrade my stock OS to Oxygen 11/Android 11 first (it came with O10/A10). I did that successfully.
However, it turned out that O11/A11 had overwritten TWRP with the stock recovery. So I flashed TWRP again. This too was successful.
I decided not to install the LineageOS with the LineageOS recovery, as in the official guide, but through TWRP. I copied the LineageOS image to phone memory, booted to TWRP, selected Wipe and did a Factory Reset - Wipes Data, Cache and Dalvik (DID NOT choose Advanced Wipe, probably this was the problem?)
After the reset, I selected the LineageOS ZIP file and installed it.
After booting to system, LineageOS starts loading, but after 4-5 mins I see
QUALCOMM CrashDump Mode
--------------------------------------------------
Panic requested on external modem boot failure
mdm_force_reset
Any help for getting out of this?
It will be MUCH appreciated.
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
MaybeDontAsk said:
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
Click to expand...
Click to collapse
The unlock command would be:
Code:
fastboot flashing unlock
Thanks for the suggestions, I will try them when I get to my home PC, I'm at work now.
In the meantime: can someone explain to me what is the exact procedure for installing LineageOS with the latest TWRP image? More specifically, which options in "Advanced Wipe" should be checked, because in all the tutorials I found they were using old versions of TWRP which did not include the "system" option. Mine had it, so I decided not to use Advanced Wipe at all and use the default wipe options (this is also what they did in one of the tutorials). Could this be the cause for the crash dump error?
Also, I am kind of reluctant to re-lock the bootloader and go back to stock OxygenOS. I still have access to the (LineageOS) recovery mode (it overwrote TWRP). Can I try doing something from there, like maybe overwriting it with TWRP again, then wiping everything (the right way) and installing LineageOS again?
Well when ever I get a Qualcomm crash dump error I always like to go back to stock and re do everything fresh just in case something else goes wrong but if you just don't wanna go back to stock you can do this:
If you wanna overwrite lineage os recovery you can reboot into the bootloader, and just do fastboot flash recovery (drag and drop twrp image here)
So it will be something like:
Code:
fastboot flash recovery C:\Users\YourUsername\Desktop\(recovery name).img
Or if you have the twrp image in the same place at platform-tools you can do:
Code:
fastboot flash recovery (recovery.img)
Or a one time twrp boot:
Code:
fastboot boot C:\Users\YourUsername\Desktop\(recovery name).img
Or:
Code:
fastboot boot (recovery name).img
But like I said it's probably better to re-lock the bootloader to start fresh then you can unlock it again and do anything else. Good Luck.
Anyways in TWRP Navigate To:
Wipe>Advanced Wipe> Dalvik/Cache>Data>swipe to wipe
Go back to TWRP home
Advanced>Adb Sideload
Now in PC cmd do:
Code:
adb sideload (drag and drop lineage os zip here)
Hit Enter And Wait Until It Finishes Flashing
Now For The Google Apps (GAPPS):
Download Nik GAPP From:
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
Select "Download"
Then look through all packages and read what each one contains, I would go with either core or basic. But you may need another apps so just read and choose.
Once you choose, click "download now"
Navigate To Folder
Releases>NikGAPPS R if lineage is 18.1(Android 11)>Latest Version>then choose from here and download.
Back to TWRP
If the download for gapps Finished:
Navigate to:
Advanced>adb sideload
Back On CMD:
Flash Gapps:
Code:
adb sideload (drag and drop NikGAPPS zip)
once it finishes:
On TWRP go back to home menu and navigate to:
Wipe>Format Data>Type "yes">Hit Enter>Go Back To TWRP Menu>Reboot>System if it says "no rom is installed" just swipe to confirm reboot, Lineage OS Is Actually Already Flashed. Good Luck!
I know this is long but it's really not lol.
@MaybeDontAsk
Thanks a lot! I will try again via TWRP first. I don't want to re-lock the bootloader just yet, because I fear something may go wrong in the process and I may end up with a bricked phone AND a locked bootloader, and that will really be the worst scenario, from what I've read in forums.
As for the GAPPS part - I don't plan to install them. Just a LineageOS image will be fine.
Alright well hope everything goes well and yeah I also feared I may end up bricking my device with the msm download tool but I've already done it multiple times.
It has fixed a lot of issues for me wether it is that the device is booting straight into recovery or fastboot or that it's not even booting up!
Just something about TWRP: when I tried just booting to it, the phone froze on the "Fastboot Mode" splash screen and stopped there. So I had to use the flash option.
Also, about flashing: I should use
Code:
fastboot flash recovery (recovery.img)
and not
Code:
fastboot flash recovery_a (recovery.img)
fastboot flash recovery_b (recovery.img)
right?
Just double checking to make sure.
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
freeride01 said:
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
View attachment 5543241
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
Click to expand...
Click to collapse
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
MaybeDontAsk said:
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
Click to expand...
Click to collapse
Alright.
I gotta find a Windows PC though, I am on Linux/Fedora.
My OxygenOS before the wipe was 11.0.10.10.IN11BA, I guess from the list I should download "OOS 11.0.4.4", because its the latest.
I'll post again when there is some progress.
MaybeDontAsk said:
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Click to expand...
Click to collapse
OK, I got my hands on a Windows 10 PC. I downloaded and extracted the MSM tool and watched the video you linked.
There is no Win7 version of the .exe file, so I guess I'll use the "normal" one anyway.
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
freeride01 said:
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
Click to expand...
Click to collapse
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
MaybeDontAsk said:
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
Click to expand...
Click to collapse
Hi again,
I did the whole process again and when I did adb sideload I got this:
Code:
[[email protected] phone root]$ adb sideload lineage-18.1-20220214-nightly-instantnoodlep-signed.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Now what? There's a slide in TWRP that says "Swipe to start sideload", should I swipe it?
EDIT: Maybe Ishould use adb install as described here?
No, you need to reinstall the adb interface drivers, search up on how to do it on Linux.
Tht link you put is for installing apk directly from adb and not roms.
But adb seems to work, adb devices returns my phone ID.
It says something like "(Device ID) | Sideload?
If yes then reboot both the laptop/pc and phone.
Code:
[[email protected] phone_root]$ adb devices
List of devices attached
19356f32 recovery
(changed some digits in serial no. for privacy)