There are probably already a couple guides up, but I wanted to post about how I went about doing this and have everything working. It may not work for everyone, but for me, it worked the first time.
0: Yep, there is a step zero here. :good: BACKUP YOUR PHONES INTERNAL STORAGE! IT WILL NEED TO BE WIPED FOR THIS TO WORK!
1: Flash factory image of 8.1 WITH the "-w" (wipe) command (LINK HERE)
2: Allow the system to boot. (optional: complete setup wizard and update apps)
3: Connect the phone to a PC and copy the TWRP 3.1.1-1 ZIP installer to internal storage (or download it via browser) (LINK HERE)
4: Download Magisk 14.3 using a PC or the phones browser, to internal storage (LINK HERE)
5: Reboot into bootloader (using the POWER + VOL-DOWN combo)
6: Fastboot BOOT TWRP 3.1.1-1 (LINK HERE)
Code:
fastboot boot twrp-3.1.1-1-fastboot-marlin.img
7: Once TWRP has booted up, flash the TWRP ZIP installer from step 3 (do NOT reboot to the OS yet)
8: Reboot directly to RECOVERY
9: Flash Magisk v14.3 from step 4
10: Reboot to Android and you're done!
Working TWRP and fully working root!
Only issue I'm having so far with TWRP is that MTP doesn't work. I can't transfer files to/from the phone while connected to a PC. That's why the file transfers have to happen while booted into Android. A TWRP update will likely fix this.
Hello, I followed these steps and all is working great, now I have activated fingerprint lock on my device and pin code, TWRP tells me that the pin is wrong when I go in to the recovery ? Any ideas, I did the procedre twice from stock and twrp tells me that the pin is wrong every time
Known issue on 8.1. Twrp is not working properly.
Just don't use pin or pattern at all.
mikaole said:
Known issue on 8.1. Twrp is not working properly.
Just don't use pin or pattern at all.
Click to expand...
Click to collapse
I need security on my phone, I would rather just wait for the TWRP update and/or actual 8.1
kingbri said:
I need security on my phone, I would rather just wait for the TWRP update and/or actual 8.1
Click to expand...
Click to collapse
At the rate TWRP gets updated, you'd have to wait till December for that. And sometime in December, 8.1 Final is supposed to be out.
Not sure if it works, but you could try disabling security, use TWRP for whatever you need, then enable security again when you're done.
So when you say flash with wipe command. You mean flash the flash all with -w tacked on the end?
Mckillagorilla said:
So when you say flash with wipe command. You mean flash the flash all with -w tacked on the end?
Click to expand...
Click to collapse
Yes, in other words: do not edit flash-all.sh.
Mckillagorilla said:
So when you say flash with wipe command. You mean flash the flash all with -w tacked on the end?
Click to expand...
Click to collapse
? No to editing file. The file flash-all.bat already has the -
w command in it. (use Flash-all.sh if you use Apple).
The reason post #1 instructs to wipe with the -w command is because some are used to removing the -w to preserve user data when flashing. For this root solution that won't work.
Born<ICs said:
? No to editing file. The file flash-all.bat already has the -
w command in it. (use Flash-all.sh if you use Apple).
The reason post #1 instructs to wipe with the -w command is because some are used to removing the -w to preserve user data when flashing. For this root solution that won't work.
Click to expand...
Click to collapse
worked perfectly for me ... no errors so far.
Let me rephrase. I wiped the phone, went back to 7.1.2, took 8.1 OTA now I want to root without wiping. Is this possible?
The second try, I hate the scrolling that is within apps. Looks like I might be going back to Nougat.
Scottay5150 said:
Can I root the OTA developer preview after a complete flash/wipe?
Click to expand...
Click to collapse
Yes, I am rooted and on it. Same procedure.
Working for me on Pixel non XL swapped the file for sailfish versions
I forget if I install TWRP to does this wipe the whole device?
TonikJDK said:
Yes, I am rooted and on it. Same procedure.
Click to expand...
Click to collapse
Thanks.
I mention that this method also works on Pixel Sailfish, except that it has to use twrp img and zip for Sailfish.
Any reason why I shouldn't just sideload the zips in TWRP? I did it just to test and things seem to be working so far without wiping the device.
Here's a stupid question- does the bootloader need to be unlocked? I'm carrier locked and want to be rooted with TWRP.
hooks024 said:
Here's a stupid question- does the bootloader need to be unlocked? I'm carrier locked and want to be rooted with TWRP.
Click to expand...
Click to collapse
On the Pixels yes you need to be bootloader unlocked to root.
mikaole said:
Known issue on 8.1. Twrp is not working properly.
Just don't use pin or pattern at all.
Click to expand...
Click to collapse
having same problem (says wrong pin), why do almost all guides that for Pixels you need to set up a pin in order to flash TWRP/root properly? Confused.
eddi0 said:
having same problem (says wrong pin), why do almost all guides that for Pixels you need to set up a pin in order to flash TWRP/root properly? Confused.
Click to expand...
Click to collapse
The phone is encrypted, it needs a PIN to authenticate to the OS to decrypt.
I actually had to factory reset it and NOT use a pin for it to work properly (after factory reset go into settings>security>none for screen lock). I know in the past a pin was required but as the second post states Magisk 14.3 is not playing nice with 8.1 beta.
Related
Android N Preview npc56p (flashable & image with no encryption and dm verification)
This thread is for the first Android N Preview.
For Android N Preview 2 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **** The following are instruction for installing Android N Preview image released by Google on 3/9/2016. After the installation you will have TWRP recovery 3.0.0-1 and the data partition will be erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery
1- You need to have TWRP installed on your phone.
2- Download this flashable zip.
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N. If your internal storage is unencrypted before flashing it remains unencrypted. Your TWRP is also upgraded to 3.0.0-1.
Method 2: Flash update using a computer
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.0-1.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root
To obtain root after installing this update you should flash SuperSU 2.70 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726. Note that at least at the moment (as of SuperSU 2.70) the root method is a hack solution which requires a lot of further refinement. Many programs are still unable to acquire root and mount the system partition for R/W. However, it is possible to install the android terminal emulator, do an su, mount /system as rw, and do all the modifications within the terminal emulator. Of course you can always use TWRP to modify the system, for which you don't even need to root the device.
Hot dog! First for once... Thanks!
Sent from my Nexus 6 using Tapatalk
#2
will this wipe internal storage ? or only data partition?
For anyone interested...
I enrolled in the Developer Beta program and the OTA worked for me even though I was rooted with SuperSU v2.68.
However, despite installing TWRP 3.0.1 and then SuperSU v2.68 again, root doesn't stick. Fortunately the only critical previously-root-only app I want is a firewall, and Netguard doesn't need root. I can live for a while without Double Tap To Wake, Wakelock detector, Quick Reboot, etc. And the only app that seems to crash is BBC Radio Player, though BBC News and iPlayer still seem ok (warning about libraries, but still plays). And Battery Bot Pro seems to have lost its status bar display...
So it does pretty much what the warnings say - it's stable but not everything will work.
so if i flash this i will still have twrp once rebooted?
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
It would be nice moving forward if Google just made SuperSU/root part of their factory image under developer options. So once you enable developer option, there's a little toggle next to OEM unlock that says "root/SuperSU".
Would make life much easier.
simms22 said:
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
Click to expand...
Click to collapse
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
The zip doesn't include stock recovery so if you flash everything according to the instructions you will have twrp at the first reboot.
This kernel worked great thanks. I'm still decrypted and didn't have to wipe internal storage. I didn't run the .bat I manually flashed the img files. Wiped data with TWRP.
so can we flash this via twrp?
omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
no, those are IMG format, flash via fastboot.
I'd wait for root ready then flash...
omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
It literally says right next to the link, "Note that it is NOT a flashable zip."
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
it says twrp recovery in title, so I was wondering....
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
chapelfreak said:
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
Click to expand...
Click to collapse
I flashed that boot img and now i am encrypted and boot-looping. No access to SD card.
Does this build have new bootloader and radio? If so, is it backward compatible to Marshmallow roms or do we need to flash back M bootloader and radio to get M roms work?
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
I lold at this. :laugh::laugh::laugh::laugh:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
kclive said:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
Click to expand...
Click to collapse
Toggle on and off airplane mode. Turn off wifi and see if it works. I was at work and had to do this a few times
Flashed phh kernel (su-noverity - 3rd one) and installed this superuser. I now have root working.
I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
I have only tested this with the device: (Honor 8 FRD-L09)
If anyone got this working on other devices please leave a comment so I can add it to this list for other people to see.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this with OldDroids TWRP or with surdu_petrus TWRP: Link(36.2MB) and Link(24,2MB)
1- Flash OldDroids or surdu_petrus TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid, surdu_petrus and phhusson
thierrybla said:
I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this only with OldDroids TWRP: Link(36.2MB)
1- Flash OldDroids TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid and phhusson
Click to expand...
Click to collapse
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM
omartins said:
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM
Click to expand...
Click to collapse
I have only tested it on the FRD-L09
I can't say for sure if it works on the others, I'm sorry.
If you got this working on a different device please let me know.
Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?
david320te said:
Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?
Click to expand...
Click to collapse
Yes SuperSU doesn't work as far as I know you need Phh Superuser.
But if you already have nougat 7.0 B380 you can just begin at the boot.img installing step and it should work for you too.
Good luck!
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The difference is that the TWRP that I linked can flash .img 's
wich you need to flash the boot.img
Try to get back in TWRP and start at step 1 just do the whole guide then your phone should boot again
david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Q: Why does booting take so long?
A: Because of the decryption process which need to finish
its work before twrp tries to access /data partition.
Click to expand...
Click to collapse
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.
N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
You are right it is for P9 but it worked for me regardless though :fingers-crossed:
david320te said:
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.
Click to expand...
Click to collapse
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot bootloader),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.
N01tra said:
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot fastboot),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.
Click to expand...
Click to collapse
I had the same as you describe here but I fixed it by flashing the 2 files I posted up here (a and b)
After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/
david320te said:
After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/
Click to expand...
Click to collapse
I'm glad to hear it works! :highfive:
TWRP backups never worked for me I always just flash it clean and then have titanium backup do the rest
Have a nice day
Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.
fourcc said:
Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.
Click to expand...
Click to collapse
Hey,
Your question is not stupid I can see why you are confused but everytime I tried to root or preroot something it didn't work for me I also run 380 and once I tried the prerooted 378 made by atariii it worked so there is no reason te be skeptical because I was in the same situation as you and this worked for me just give it a try you won't be disappointed
Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!
fourcc said:
Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!
Click to expand...
Click to collapse
Tell me how it went !
Goodluck!
Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!
fourcc said:
Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!
Click to expand...
Click to collapse
that's fine too I'm glad it worked good for you!
Have a nice day!
Just updated with the February full image using fastboot, editing out the -w from flash-all.bat. Fastboot booted TWRP, and then queued up TWRP, Kernel, Magisk and let all 3 rip. No hitches and back up running rooted and everything working normally. Be sure and read the entire Security Bulletin as there were loads of functional updates not always a part of the monthly updates. :good:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Tb0n3 said:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Click to expand...
Click to collapse
Give Deuces script a try. It has helped a lot of people recover their device from similar situations.
I haven't tried it on Feb update though.
You can get it from Development section. Good luck.
Tb0n3 said:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Click to expand...
Click to collapse
what do you mean "because unlock_critical reset?"
Tb0n3 said:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Click to expand...
Click to collapse
Did you ever unlock critical before you tried the update? Or did this happen after the update?
Can someone here confirm the correct way to upgrade from rooted Jan security update without losing data? Would I
reflash stock recovery
fastboot OTA img
fastboot boot twrp.img
flash twrp.zip
flash kernel
flash magisk last?
Or can I use the full image from the dev site, remove the -w and run the flash-all.bat, then use the steps above? Same result, or is one better than the other? Am I missing any steps here?
Is xposed module working on Feb update?
RampageRR said:
Can someone here confirm the correct way to upgrade from rooted Jan security update without losing data? Would I
reflash stock recovery
fastboot OTA img
fastboot boot twrp.img
flash twrp.zip
flash kernel
flash magisk last?
Or can I use the full image from the dev site, remove the -w and run the flash-all.bat, then use the steps above? Same result, or is one better than the other? Am I missing any steps here?
Click to expand...
Click to collapse
See the OP. Use the full image then add back recovery,kernel,magisk in that order. Yes magisk last.
v12xke said:
Just updated with the February full image using fastboot, editing out the -w from flash-all.bat. Fastboot booted TWRP, and then queued up TWRP, Kernel, Magisk and let all 3 rip. No hitches and back up running rooted and everything working normally. Be sure and read the entire Security Bulletin as there were loads of functional updates not always a part of the monthly updates. :good:
Click to expand...
Click to collapse
Quick question - I have performed the flash-all part and at the end it rebooted and everything is fine (except for no root) - it asks for the encryption password and it works with my normal password.
Then I boot TWRP with "fastboot boot twrp-3.2.1-0-taimen.img" and that again works just fine but only to the point where it asks for the password - which here is NOT working? Just a few hours ago the same twrp was working fine with the exact same password (since I did a full backup in advance), and the password is obviously working fine in Android itself, it is only in TWRP where is no longer working???
xclub_101 said:
Quick question - I have performed the flash-all part and at the end it rebooted and everything is fine (except for no root) - it asks for the encryption password and it works with my normal password. Then I boot TWRP with "fastboot boot twrp-3.2.1-0-taimen.img" and that again works just fine but only to the point where it asks for the password - which here is NOT working? Just a few hours ago the same twrp was working fine with the exact same password (since I did a full backup in advance), and the password is obviously working fine in Android itself, it is only in TWRP where is no longer working???
Click to expand...
Click to collapse
I don't really know what went wrong. What do you mean it asks for the encryption password?? If you have some kind of boot encryption set, maybe that is is. My encrypted unit never asks me for a password. I have an unlock screen PIN and that is all. When I flash-all, I wait for the flash to finish (knowing it will reboot) and at the right time hold the volume down button to get me right back into the bootloader. I do not allow it to boot into the OS until I fastboot boot twrp and have never had TWRP refuse my password. Maybe it has something to do with you allowing it to boot into the OS first? Anyway from that "booted" instance of TWRP, I then queue up twrp.zip, kernel.zip, magisk.zip and once they are added, I let TWRP flash all 3. You may want to take this over to the TWRP thread where others have had the PIN issue as well. Some are confirming temporarily removing your PIN/fingerprints fixes it. I have never removed my PIN or fingerprints before or after flashing?
v12xke said:
I don't really know what went wrong. What do you mean it asks for the encryption password?? If you have some kind of boot encryption set, maybe that is is. My encrypted unit never asks me for a password. I have an unlock screen PIN and that is all. When I flash-all, I wait for the flash to finish (knowing it will reboot) and at the right time hold the volume down button to get me right back into the bootloader. I do not allow it to boot into the OS until I fastboot boot twrp and have never had TWRP refuse my password. Maybe it has something to do with you allowing it to boot into the OS first? Anyway from that "booted" instance of TWRP, I then queue up twrp.zip, kernel.zip, magisk.zip and once they are added, I let TWRP flash all 3. You may want to take this over to the TWRP thread where others have had the PIN issue as well. Some are confirming temporarily removing your PIN/fingerprints fixes it. I have never removed my PIN or fingerprints before or after flashing?
Click to expand...
Click to collapse
Yes, it is quite weird.
A few more questions - when you boot your normal Android - do you first get a question about any password there? Since if you don't - your system probably uses the default Android encryption password (which last time when I was looking was literally "default_password" without the quotes).
Why do you still need to flash the kernel - are you using a custom kernel?
xclub_101 said:
Yes, it is quite weird.
A few more questions - when you boot your normal Android - do you first get a question about any password there? Since if you don't - your system probably uses the default Android encryption password (which last time when I was looking was literally "default_password" without the quotes). Why do you still need to flash the kernel - are you using a custom kernel?
Click to expand...
Click to collapse
I never get prompted for a password upon booting, and my phone is encrypted. I think you are probably on to the real reason your twrp is not accepting your PIN. Older Nexus phones had boot encryption with a password but since the Pixel line I thought it was removed? When discussing this further in the TWRP thread I think you should be comparing notes with others on this boot encryption, because I don't have it. I'm reading something now about direct boot and fbe.
Yes I use a custom kernel, always have. I like being able to monitor and control my system and gestures, vibration, etc. I like the kernel monitor (and battery monitor) that goes along with EX Kernel. Highly recommended. Good luck to you.
i sideloaded the update to my verizon version pixel 2 xl, and havent noticed anything, mainly just a run of the mill security update. i read that pixel core has been extended to a few apps.
v12xke said:
I never get prompted for a password upon booting, and my phone is encrypted. I think you are probably on to the real reason your twrp is not accepting your PIN. Older Nexus phones had boot encryption with a password but since the Pixel line I thought it was removed? When discussing this further in the TWRP thread I think you should be comparing notes with others on this boot encryption, because I don't have it. I'm reading something now about direct boot and fbe.
Yes I use a custom kernel, always have. I like being able to monitor and control my system and gestures, vibration, etc. I like the kernel monitor (and battery monitor) that goes along with EX Kernel. Highly recommended. Good luck to you.
Click to expand...
Click to collapse
Thank you for the info!
The encryption is still a weird point - and I believe is still linked by default to the "screen lock password" as described at https://www.xda-developers.com/how-to-manually-change-your-android-encryption-password/ - but I am not yet convinced that I should remove my existing password since the system is telling me that removing it will remove all fingerprints that I have added and mark the system as unsecure for Pay.
What I wonder is if I should go ahead with just writing Magisk without decrypting the user data partition - after all Magisk should not be touching either the system nor the user data partition, so it could work just fine?
Did they remove the setting to turn on Pixel Visua Core in Developer settings?
xclub_101 said:
Thank you for the info!
The encryption is still a weird point - and I believe is still linked by default to the "screen lock password" as described at https://www.xda-developers.com/how-to-manually-change-your-android-encryption-password/ - but I am not yet convinced that I should remove my existing password since the system is telling me that removing it will remove all fingerprints that I have added and mark the system as unsecure for Pay.
What I wonder is if I should go ahead with just writing Magisk without decrypting the user data partition - after all Magisk should not be touching either the system nor the user data partition, so it could work just fine?
Click to expand...
Click to collapse
I guess my question is why do you have an encryption password at boot? My phone boots up to a lockscreen. I enter my PIN and that's it. Maybe I'm misunderstanding and you are calling my PIN your boot encryption password.... do you then have a lockscreen and enter a separate PIN? As for Magisk it doesn't decrypt the data partition or anything else. I always install it by flashing the zip file in TWRP and you have no options there. It just does it's thing and installs Magisk Manager as an app, so when you boot up System, MM is in your app drawer. You can configure it from there. My setup has always passed SafetyNet but I don't use/want Pay.
v12xke said:
I guess my question is why do you have an encryption password at boot? ...
Click to expand...
Click to collapse
Good question - I would normally expect that to be required when Android itself needs to decrypt first time after boot the user data partition? Which up to that point during the boot process is not otherwise needed?
The fact that on some systems is not required suggests to me that Android (like maybe also TWRP) first tries "default_password" and that works?
Mikulec said:
Did they remove the setting to turn on Pixel Visua Core in Developer settings?
Click to expand...
Click to collapse
yes.
djkinetic said:
i sideloaded the update to my verizon version pixel 2 xl, and havent noticed anything, mainly just a run of the mill security update. i read that pixel core has been extended to a few apps.
Click to expand...
Click to collapse
Its quite a bit more than the run of the mill security update.
visual core is now extended to any app, not just a few (so long as they target API level 26, Oreo).
i sideloaded the update like I always do. All updated normally and all functioning as expected. After sideloading the update I booted the twrp-3.2.1-0-taimen.img, it booted and when I entered my pin, which i have been using, in TWRP it would not accept my pin. I rebooted into the boot.img 3 times same issue. I removed my pin and TWRP functioned as expected. I installed TWRP.zip and rebooted recovery. Back in TWRP flashed Kernel, and Magisk and no issues. This was the first time I had issues entering my pin on booting TWRP.img
Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?
Tiemichael said:
Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?
Click to expand...
Click to collapse
Hey!
Following the official Magisk procedure works, at least for me.
You just have to be careful to restore backup image before starting the OTA download and installing to second slot (After OTA) before rebooting.
Reading this thread:
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
I found there’s a lot of confusion (I was confused also and made a few mistakes), but my conclusions are:
- That method is to be used just ONCE in order to gain root, and not every month.
- Always try to use your own patched image if you have the opportunity
- You have to use “fastboot BOOT” and not “fastboot FLASH” when first rooting, otherwise you won’t be able to restore boot image and OTA will fail
- Follow official procedure as a cooking recipe
If you don’t want to root using a patched boot image, you can also use latest TWRP (As of now latest is recovery-3.2.1-2-oreo.img)
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
And boot to TWRP image in order to install Magisk ZIP (did this yesterday and also worked), but the update via OTA method should be the same.
Best regards.
Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me
Keeping phone to stock and not rooting for only one OTA in more than a month? I think its not worth it!!
I always root my phone and when OTA arrives i just flash twrp version of it and root it again ?
Siebenmik said:
Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me
Click to expand...
Click to collapse
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?
I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..
_mysiak_ said:
I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..
Click to expand...
Click to collapse
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?
Tiemichael said:
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?
Click to expand...
Click to collapse
Yes, exactly. I didn't have any issue with OTA installation yet.
Tiemichael said:
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?
Click to expand...
Click to collapse
I forgot saying that using restore image in magisk didn't work. Even though I didn't flash the patched boot.
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where to enable secured startup?
Skeuomorphic said:
Where to enable secured startup?
Click to expand...
Click to collapse
create a pattern from security setting and it will prompt to enable secure startup.. just press yes..
coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Finally a different answer, I have secure boot disabled maybe this is the reason ending into bootloop for past 3 montly security updates. Will try this for May update.
coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....
Tiemichael said:
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....
Click to expand...
Click to collapse
Settings->Security & Location->Screen lock->Pattern
This what was working for me just now:
Detailed steps performed 20.4.2018:
Backup Titanium
Backup Magisk Modules
Switch on Secured Booting (e.g. Pin) => not same a normal pin!
Open Magisk
Uninstall Magisk
Restore Images
Start OTA update
Downlowd
Step1
Step2
Go Back to Magisk
Install to 2nd slot
Reboot
It was working ... very easy!
I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.
I didn't update my phone for a very long time, then I decided to finally go for the latest MIUI on my Mi Max and basically I flashed full new ROM via fastboot & MiPhone.
You can see detailed description here: https://forum.xda-developers.com/showpost.php?p=78050983&postcount=41
I think it should work with other Xiaomi phones too but please correct me if I'm wrong
The only difference is that I had SuperSu before, but maybe with Magisk it's the same to do - also correct me if i'm wrong
quetzalcoatl2435 said:
I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.
Click to expand...
Click to collapse
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
H.A.L. 9000 said:
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.
Click to expand...
Click to collapse
freekarol said:
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Click to expand...
Click to collapse
Yeah, but you need a PC for this. If I need access to a PC every time there's an OTA update, might as well download and flash a full ROM. ?
Official Magisk OTA guide works anytime anywhere, no PC needed.
This guide is now obsolete. Please check my new guide. It has a custom recovery for this device as well as a rooting guide. Refer to this guide only for installing adb and unlocking bootloader.
This rooting guide is for the Lenovo Tab M10 X505X only.
I plan to work on a custom recovery for this tab as well and probably a custom rom in the future.
So please consider donating so that I can keep up the work.
Donations
Google Pay
This will work only on the version "TB-X505X_S001037_200718_ROW". Check it in the Settings > System > About Tablet > Build Number. If it is the newer "X505X_S001038_200819_ROW", do a factory reset and make sure it is the "TB-X505X_S001037_200718_ROW" before proceeding.
Once a custom recovery is made, OTA updates can be applied without losing root. So do not update the tablet until a custom recovery is developed for the device. I plan to develop a custom recovery for it as soon as possible, so please support me.
Anything that goes wrong in this tutorial is not my responsibilty. Proceed at your own risk.
Downloads
patched_boot.img
Step 1. ADB and Fastboot Installation [If adb and fastboot are already installed, skip to Step 2]1. Download the platform tools for your OS from this link.
2. Extract the zip file and place the contents in a folder "platform-tools".
3. To confirm if adb is working, open a command prompt "platform-tools" and run the following command.
Code:
adb version
If it returns the adb version, its done.
Step 2. Unlocking BootloaderWe have to unlock the bootloader inorder to root the device.
Warning: Unlocking bootloader wipes data on the device. It is recommended to backup your data. Proceed at your own risk.
1. Now in the tab, goto Settings > System > About Tablet. Multiple tap the "Build Number" till the developer options are enabled.
2. Goto the developer options and turn on the "OEM unlocking".3. Power off the device.
4. Turn it on by holding Power Button + Volume Down. Once the screen turns on. leave the power button but continue holding the Volume Down button until the fastboot mode is shown.
5. Now open a command prompt in "platform-tools" and now run the following command:
Code:
fastboot oem unlock-go
Your Bootloader is now succesfully unlocked.Step 3. RootingNow to root the tab, download the "patched_boot.img" from the top of this post. Copy the file to the "platform-tools" folder.
Make sure the tab is still in the fastboot mode. Otherwise go back into the fastboot mode as instructed before.
Now run the following command:
Code:
fastboot flash boot patched_boot.img
Congratulations, you have rooted your tab.:highfive:
To complete the process, run the following command.
Code:
fastboot reboot
Once the tab turns on, goto this link and download the latest version of Magisk apk and install it. It is required to control the root privileges for other apps.That's all. You now have a rooted tab.:victory:
If this helped you, hit the thanks button.
And keep tuned for new stuff that are to come for this device.
Thanks for this thread for the TB-X505X.
Shamil Niyas said:
I plan to work on a custom recovery for this tab as well...
I plan to develop a custom recovery for it as soon as possible...
Click to expand...
Click to collapse
Have a look at this post for a TWRP that works with the TB-X505F. It might work for the TB-X505X, provided the X505X uses the SDA429 soc. That version of TWRP is unofficial and does not decrypt the data partition.
If the X505F version of TWRP works for you, then you won't need to patch the boot image - you can just install the Magisk update.zip in TWRP. This saves you from having to release a new patched boot image every time there's an OTA.
Shamil Niyas said:
Once a custom recovery is made, OTA updates can be applied without losing root.
Click to expand...
Click to collapse
With the TB-X505F/L, TB-X605F/L and TB-X705F/L we've found that you need to uninstall Magisk to apply OTAs. This is because Lenovo's OTA updater scripts verify you have unmodified boot, system, vendor and firmware partitions. So make sure you backup these partitions as stock.
Yahoo Mike said:
Thanks for this thread for the TB-X505X.
Have a look at this post for a TWRP that works with the TB-X505F. It might work for the TB-X505X, provided the X505X uses the SDA429 soc. That version of TWRP is unofficial and does not decrypt the data partition.
If the X505F version of TWRP works for you, then you won't need to patch the boot image - you can just install the Magisk update.zip in TWRP. This saves you from having to release a new patched boot image every time there's an OTA.
With the TB-X505F/L, TB-X605F/L and TB-X705F/L we've found that you need to uninstall Magisk to apply OTAs. This is because Lenovo's OTA updater scripts verify you have unmodified boot, system, vendor and firmware partitions. So make sure you backup these partitions as stock.
Click to expand...
Click to collapse
I gave a look at the TWRP image. Unfortunately, X505X does not boot into the recovery image. It would have been great if it worked. I guess it is because of the different processor, as you mentioned.
It is the same for X505X as well. OTA cannot be applied without uninstalling Magisk. So I guess OTAs are a no-go until a custom recovery is developed. The latest update is also just a boot image patch. So there is no way to use magisk on that.
Thanks for the advice.
But i updated to android 10 S001122_200915
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Excuse me if this was asked before. Is there a rooting method for TB-X505F? It's the model that is sold in Europe. I'm thinking of buying this.
ShAd0W_z0nE said:
Excuse me if this was asked before. Is there a rooting method for TB-X505F? It's the model that is sold in Europe. I'm thinking of buying this.
Click to expand...
Click to collapse
This post has instructions for the X505F, under "How do I root my device?".
cYBER~VeTeRaN said:
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Click to expand...
Click to collapse
I'm currently working on the twrp for this device. Once it is finished it should be able to root without downgrading.
cYBER~VeTeRaN said:
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Click to expand...
Click to collapse
Hello cYBER-VeTeRaN,
I have compiled a TWRP for X505X. You can find it here. Install the magisk zip from TWRP and you should be able to root your tablet regardless of the verison.:victory:
Hit the thanks button.
Shamil Niyas said:
Hello cYBER-VeTeRaN,
I have compiled a TWRP for X505X. You can find it here. Install the magisk zip from TWRP and you should be able to root your tablet regardless of the verison.:victory:
Hit the thanks button.
Click to expand...
Click to collapse
Thanks sir. Great job and I'm also from kerala, nice to meet you
Good afternoon.
I have this version ( Build number TB-X505F_S001142_210804 ROW ) of Android on my Lenovo TB X505F.
Can you tell me if this method works with this version of Android?
jsvenancio said:
Good afternoon.
I have this version ( Build number TB-X505F_S001142_210804 ROW ) of Android on my Lenovo TB X505F.
Can you tell me if this method works with this version of Android?
Click to expand...
Click to collapse
[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD
This version of TWRP works on the Lenovo TB-X505F (wifi). For the TB-X505X, see this thread. For the TB-X605F/L, see this thread. For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC. #include...
forum.xda-developers.com
Twrp for x505f
Umm where it says to download my os there is no link provided. Same goes for fastbook it takes me tomyour old guide and then there is no link where a person would think they would find it. Am I stupid and missing something or all the links broke/missing ?
I'd prefer to be stupid.... Just saying..
tombaldwin6 said:
Umm where it says to download my os there is no link provided. Same goes for fastbook it takes me tomyour old guide and then there is no link where a person would think they would find it. Am I stupid and missing something or all the links broke/missing ?
I'd prefer to be stupid.... Just saying..
Click to expand...
Click to collapse
Check his new guide, just flash twrp and flash magisk from there
Guys, I am stuck in a Bootloop after i tried that with the patched boot img. Can someone help?
Tamiiiiiii812 said:
Guys, I am stuck in a Bootloop after i tried that with the patched boot img. Can someone help?
Click to expand...
Click to collapse
Download rom, extract boot.img from it and flash it. Makw sure you download the right version.
You can find the rom here:- https://mirrors.lolinet.com/firmware/lenovo/Tab_M10_HD/TB-X505X/
cYBER~VeTeRaN said:
Download rom, extract boot.img from it and flash it. Makw sure you download the right version.
You can find the rom here:- https://mirrors.lolinet.com/firmware/lenovo/Tab_M10_HD/TB-X505X/
Click to expand...
Click to collapse
OMG IT WORKED. Thank you.
Thanks bro. I found what I needed..
Shamil Niyas said:
1. Download the platform tools for your OS from this link.
Click to expand...
Click to collapse
yeah, where is the link?
Booe said:
yeah, where is the link?
Click to expand...
Click to collapse
Just search for platform tools and download it.
Guys, i tried the above mentioned method but my device is showing (can,t load android system. your data my be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device) after performing a factory data reset the device reboots and the welcome menu shows up after 15-30 seconds the device automatically shut down and again shows the same message (can,t load android system. your data my be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored onnn this device). this goes again and again......