I managed to install it, it got really tricky. The thing is that the new Lineageos releases somehow fail the verification on twrp and the old lineageos recovery. I found out after hours of investigating that you need the *new* Lineageos recovery to flash the new lineageos. I know, it's pretty absurd.
I extracted the boot.img from lineage-15.1-20180724-nightly-tissot-signed.zip extracting the payload.bin from the zip and using this tool https://androidfilehost.com/?fid=818070582850510260.
You can download the boot.img I extracted myself here: https://drive.google.com/file/d/1QftMHTXrINAOfr3Pcaqyux9nHRnGTnKl/view?usp=sharing
Put the phone on fastboot mode, connect via usb and type:
Code:
fastboot boot boot.img
while pressing the volume-up button to enter the Lineageos recovery.
From there do a factory reset, wipe system, and now you can flash lineage-15.1-20180724-nightly-tissot-signed.zip.
To flash it, it gets tricky. First of all you can't flash from the sdcard because it shows up an error. So you go to update, and press install from ADB or something like that. Now you have the phone on adb sideload mode.
Download https://developer.android.com/studio/releases/platform-tools. Adb from XDA's "Minimal ADB and Fastboot" doesn't work for some reason.
Unzip the file, open a command prompt on that folder and type:
Code:
adb devices
It has to show up as something like this:
Code:
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
xxxxxxxxxxx sideload
Where xxxxxxx is the phone id.
Then you can proceed to flash. Just type:
Code:
adb sideload lineage-15.1-20180724-nightly-tissot-signed.zip
Wait until it completes, it seems to freeze at 50% or so but wait some minutes until the progress bar on the recovery finishes and reboot.
Now you should be booting lineageos and set up it as usual. I hope this guide helped, took me some hours to figure it all out.
To install su addon, download it from https://mirrorbits.lineageos.org/su/20180718/addonsu-15.1-arm64-signed.zip, place the zip in your internal storage, download this recovery https://basketbuild.com/filedl/devs...ewolf/Recovery/tissot/twrp-3.2.2-1-tissot.img (thx nicknitewolf) and boot it via fastboot:
Code:
fastboot boot twrp-3.2.2-1-tissot.img
From there flash the su addon as usual and enjoy. Probably this method works also for opengapps/mindthegapps, i didn't have time to test it.
Rather, just use Abhishek's recovery image and twrp (V3.2.3) installer zip and get the job done.
Once you've installed the official LineageOS 15.1: Can you then update your system from Settings -> System -> About phone -> LineageOS updates without needing to ever flash something from TWRP again?
Related
Hey folks,
I´ve ran my MZ601 xoom on EOS builds over the last 1,5 years.
Obviously its unlocked and rooted. Currently its running CWM Recovery 4.0.0.4
Now I want to go back to stock to install the latest official updates to get the updated drivers for the UMTS radio/modem module.
After that I want to unlock and get root again to use any of the lastest custom Roms again.
Switching to a touch based recovery would be nice too.
I surfed around a bit and I´m rather confused which steps I need to perform in order to do this.
I guess I need to remove root and lock the bootloader again before I can install official updates ?
Could someone please toss me in the right direction? Maybe some step-by step list?
You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloaderThen run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot rebootYou'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldThen select reboot in ClockworkMod recovery and boot as normal.
If you are unable to use adb in recovery, then you can enable this through Windows by doing the following:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Finally, run:
adb reboot recoveryIf ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.
Wow, what a detailed guide
Thank you sir
No problem!
Let me know how it goes, hopefully shouldn't have any problems.
Resetting worked great :good:
Right now I´m in an OTA marathon
all that unlock, root and recovery stuff sounds familiar so I don´t expect any problems.
Thanks so far :good:
alecbond said:
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldThen select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recoveryIf ClockworkMod touch recovery is still there then all is good!
Click to expand...
Click to collapse
Ok, so this is not working
after I flash touch recovery and do thta reboot thing I can enter touch recovery, thats fine.
Flashing universal root, fine.
THEN,
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
gives me error since in recovery mode there ist no adb connection
Whatever when I choose to reboot the system, recovery warns me that it will get overwritten by boot and ask me to disable this.
Shall I do this?
EDIT: Nevermind, I decided to be a little brave and just confirmed that message.
Now touch clockwork seems to be persistent and I´m a happy Xoomer again
Sorry, I had meant to reply during my lunch break.
Edit: Realised the time on the second of your posts, so wouldn't have been much help on my lunch anyway
Well I believe I just learned something new!
Either that or I'd forgotten it asked.
I assume it disables the action rather than deletes those files.
My method was just so you can use the reverse rename in future to re-enable the overwrite on boot.
In future, not that you'll necessarily ever need this information, you can enable adb in recovery through windows by doing the following
When in recovery and connected to your PC, open Device Manager, find your phone, usually under 'Other Devices'.
Then right click > Update driver > Browse my computer > Let me pick from list > Pick your phone (either one if there's two shown)
Should confirm driver installed then adb should work.
I didn't include the above previously as I couldn't remember having to do it personally.
Glad to hear all is well though!
alecbond said:
You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloaderThen run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot rebootYou'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldThen select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recoveryIf ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.
Click to expand...
Click to collapse
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
XxLordxX said:
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
Click to expand...
Click to collapse
No problem, I'd be honored!
I'm not tech savvy when it comes to Android and I need some help to root my teen's Motorola Moto E 2015, preferably today.
I need to root it to then disable the guest account, so that when I install the ScreenTime app my son can't bypass it by using the guest account. That's a shortcoming of ScreenTime.
I read a bit about ROMs and would like to use CyanogenMod.
But other than my choice of ROM, I haven't found what I believe to be reliable instructions on what to do now step by step. I really do need idiot-proof step by step instructions.
Is there a super Android geek here who has time to take me through the process or offer advice and links to such sources?
Hello,
Welcome to XDA.
Try the thread linked below, there is a YouTube video in the first post that walks you through rooting your device.
http://forum.xda-developers.com/moto-e-2015/general/root-moto-e-2015-t3086819
If you have further questions about your device, try posting your questions in the forum linked below.
http://forum.xda-developers.com/moto-e-2015/help
The experts there may be able to help. Good luck.
Got this far
Found instructions on CyanogenMod Wiki - wiki.cyanogenmod.org/w/Install_CM_for_surnia[/url
but only got as far as step 5. What terminal on my computer? Command Prompt? I typed adb reboot bootloader into Command Prompt but it said adb command is not recognized.
Unlocking the device
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Enable OEM unlock in the Developer options settings on the device. (Note: Not all devices have this setting, so continue with next step if yours does not.)
4. Connect the device to the computer through USB.
5. From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
6. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
* If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
* If you see "no permissions fastboot", try running fastboot as root.
7. From the same terminal, type the following command to obtain your bootloader unlock code:
fastboot oem get_unlock_data
8. Visit the Motorola Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader.
9. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
10. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Installing recovery using fastboot
See All About Recovery Images for more information about custom recoveries and their capabilities.
1. Make sure your computer has working fastboot and adb.
2. Download recovery -- you can directly download a recovery image using the link below, or visit twrp.me to obtain the latest version of TeamWin Recovery Project for your device.
Recovery: Downloadmd5: 5fdfe1871589c0a152f3f7e541b6c892
3. Connect the Moto E 2015 LTE to the computer via USB.
4. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
5. Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloaderor by using the hardware key combination for your device while it is powered off.
6. Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
* If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
* If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
7. Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.imgwhere the latter part is the filename of the recovery image.
8. Once the flash completes successfully, reboot the device into recovery to verify the installation. Boot to recovery instructions: Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
* Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.
Installing CyanogenMod from recovery
1. Make sure your computer has working adb.
2. Download the CyanogenMod package for your device that you'd like to install to your computer.
Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.
3. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
* Using adb: adb push filename.zip /sdcard/
Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.
4. If you are not already in recovery, boot to recovery mode now.
* Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
5. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and then Factory Reset.
8. Select Install (if you're running Cyanogen recovery this is Apply Update).
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod the first and then install any subsequent packages on top of it).
12. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.
ipzma said:
Found instructions on CyanogenMod Wiki - wiki.cyanogenmod.org/w/Install_CM_for_surnia[/url
but only got as far as step 5. What terminal on my computer? Command Prompt? I typed adb reboot bootloader into Command Prompt but it said adb command is not recognized.
Unlocking the device
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Enable OEM unlock in the Developer options settings on the device. (Note: Not all devices have this setting, so continue with next step if yours does not.)
4. Connect the device to the computer through USB.
5. From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
6. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
* If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
* If you see "no permissions fastboot", try running fastboot as root.
7. From the same terminal, type the following command to obtain your bootloader unlock code:
fastboot oem get_unlock_data
8. Visit the Motorola Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader.
9. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
10. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Installing recovery using fastboot
See All About Recovery Images for more information about custom recoveries and their capabilities.
1. Make sure your computer has working fastboot and adb.
2. Download recovery -- you can directly download a recovery image using the link below, or visit twrp.me to obtain the latest version of TeamWin Recovery Project for your device.
Recovery: Downloadmd5: 5fdfe1871589c0a152f3f7e541b6c892
3. Connect the Moto E 2015 LTE to the computer via USB.
4. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
5. Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloaderor by using the hardware key combination for your device while it is powered off.
6. Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
* If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
* If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
7. Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.imgwhere the latter part is the filename of the recovery image.
8. Once the flash completes successfully, reboot the device into recovery to verify the installation. Boot to recovery instructions: Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
* Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.
Installing CyanogenMod from recovery
1. Make sure your computer has working adb.
2. Download the CyanogenMod package for your device that you'd like to install to your computer.
Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.
3. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
* Using adb: adb push filename.zip /sdcard/
Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.
4. If you are not already in recovery, boot to recovery mode now.
* Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
5. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and then Factory Reset.
8. Select Install (if you're running Cyanogen recovery this is Apply Update).
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod the first and then install any subsequent packages on top of it).
12. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.
Click to expand...
Click to collapse
Have you installed the adb/fastboot program? Do a Google search for adb/fastboot for windows. Then verify that you have your moto E USB drivers downloaded and installed. You should be able to enter adb commands when that is set up. To verify that adb is working and that your device is recognized you type: adb devices
That should give you a set of numbers and letters, if so then your device is recognized, continue with the commands from your guide.
The YouTube video will walk you through step by step with a visual guide instead of trying to make sense of written instructions, just emulate the operators' actions following the video and you can't go wrong.
Sent from my SCH-I535 using Tapatalk
ipzma said:
Found instructions on CyanogenMod Wiki - wiki.cyanogenmod.org/w/Install_CM_for_surnia[/url
but only got as far as step 5. What terminal on my computer? Command Prompt? I typed adb reboot bootloader into Command Prompt but it said adb command is not recognized.
Unlocking the device
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Enable OEM unlock in the Developer options settings on the device. (Note: Not all devices have this setting, so continue with next step if yours does not.)
4. Connect the device to the computer through USB.
5. From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
6. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
* If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
* If you see "no permissions fastboot", try running fastboot as root.
7. From the same terminal, type the following command to obtain your bootloader unlock code:
fastboot oem get_unlock_data
8. Visit the Motorola Bootloader Unlock website and follow the instructions there to obtain your unlock key and unlock your bootloader.
9. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
10. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Installing recovery using fastboot
See All About Recovery Images for more information about custom recoveries and their capabilities.
1. Make sure your computer has working fastboot and adb.
2. Download recovery -- you can directly download a recovery image using the link below, or visit twrp.me to obtain the latest version of TeamWin Recovery Project for your device.
Recovery: Downloadmd5: 5fdfe1871589c0a152f3f7e541b6c892
3. Connect the Moto E 2015 LTE to the computer via USB.
4. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
5. Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloaderor by using the hardware key combination for your device while it is powered off.
6. Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
* If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
* If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
7. Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.imgwhere the latter part is the filename of the recovery image.
8. Once the flash completes successfully, reboot the device into recovery to verify the installation. Boot to recovery instructions: Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
* Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.
Installing CyanogenMod from recovery
1. Make sure your computer has working adb.
2. Download the CyanogenMod package for your device that you'd like to install to your computer.
Optional: Download 3rd party applications packages, like Google Apps which are necessary to download apps from Google Play.
3. Place the CyanogenMod .zip package, as well as any optional .zip packages, on the root of /sdcard:
* Using adb: adb push filename.zip /sdcard/
Note: You can copy the .zip packages to your device using any method you are familiar with. The adb method is used here because it is universal across all devices and works in both Android and recovery mode. If you are in recovery mode, you may need to ensure /sdcard (sometimes called Internal Storage) is mounted by checking its status in the Mounts menu. If you have booted regularly, USB debugging must be enabled.
4. If you are not already in recovery, boot to recovery mode now.
* Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.
5. In Team Win Recovery Project, select menu choices by tapping on the appropriately labelled button.
6. Optional (Recommended): Select the Backup button to create a backup.
7. Select Wipe and then Factory Reset.
8. Select Install (if you're running Cyanogen recovery this is Apply Update).
9. Navigate to /sdcard and select the CyanogenMod .zip package.
10. Follow the on-screen notices to install the package.
11. Optional: Install any additional packages you wish using the same method (if you are installing multiple packages, install CyanogenMod the first and then install any subsequent packages on top of it).
12. Once installation has finished, return to the main menu and select Reboot, then System. The device will now boot into CyanogenMod.
Click to expand...
Click to collapse
Sorry, I meant to tell you that the command prompt is where you type your commands.
Sent from my SCH-I535 using Tapatalk
Scenario
You are rooted with systemless SuperSU.
You have untouched /system partition.
You have unlocked bootloader.
What you'd need
fastboot and adb from platform-tools.
tissot_images_xxx.tgz - Stock ROM for your current version (before the OTA).
cfar_xiaomi_mi-a1_tissot_xxx.zip - CF-Auto-Root package for your current version (before the OTA).
SR5-SuperSU-v2.82-SR5-xxx.zip or a later version
How to install OTA
Uninstall FlashFire if it's installed. It hijacks OTA installation but fails as the device is not (yet?) supported.
Start the OTA installation. (Settings > About phone > System update)
Restart the device. You'd get into a boot loop because of the patched boot image.
Hold down the power + volume down buttons to get into Fastboot mode.
Code:
fastboot getvar all
to find out the current active slot.
Extract boot.img from tissot_images_xxx.tgz.
Code:
fastboot flash boot_x boot.img
where x is the current active slot.
Code:
fastboot reboot
You'd see the update engine screen for a bit, and then it'd reboot again.
Once you're back in Android, you should see that you're on the latest version. (Settings > About phone)
How to root for both slots
Wait for "Finishing Android update..." to complete (if it's still not done yet).
Code:
adb reboot-bootloader
to get into Fastboot mode.
Code:
fastboot getvar all
to find out the current active slot.
Code:
fastboot set_active x
where x is the inactive slot.
Extract boot.img from cfar_xiaomi_mi-a1_tissot_xxx.zip.
Code:
fastboot boot boot.img
You'd see nothing happen for a while. Just be patient. It'd reboot automatically and it'd take a while.
WARNING: Do not flash this image. If you accidentally flash it, you can reflash the stock boot.img.
Click to expand...
Click to collapse
Once you're back in Android, you should see that you're on the old version. (Settings > About phone)
Install FlashFire.
Code:
adb push SR5-SuperSU-v2.82-SR5-xxx.zip /sdcard/
(adjust the filename accordingly).
Code:
adb shell "su -c 'echo BINDSBIN=true > /data/.supersu'"
to install SuperSU in SBIN mode. Recommended.
Run FlashFire. Add "Flash ZIP or OTA" action and select the SuperSU zip. Select Slot A.
Add "Flash ZIP or OTA" action and select the SuperSU zip. Select Slot B.
Wait for "Finishing Android update..." to complete (if it's still not done yet).
Hit the flash button. Wait while FlashFire does its job. Be patient. It might reboot a few times. Do not interrupt the process.
Code:
adb reboot-bootloader
to get into Fastboot mode.
Code:
fastboot getvar all
to find out the current active slot.
Code:
fastboot set_active x
where x is the inactive slot.
Code:
fastboot reboot
and you're done.
If you want to read this in Markdown: https://gist.github.com/teohhanhui/98810ee282292157e8290e7e3ed87537
References / Credits
Guide on how to root mi A1 all future updates
Root new OTA updates [September Update]
If you are on the OTA Oreo 8.1 and dont have root, here's how to do so:
First request: Anyone that knows someone that can help get us WFD (Wireless Display Casting) enabled that would be very helpful. If you edit build.prop you can get it to show wireless displays in the System/Connected Devices/Cast but force reboots for me when I try connecting to my HP Lapdock
Now to TWRP/MAGISK
Make sure you are on 8.1, Android debugging is enabled under developer options and bootloader unlocked (Warning if you're not when you do this it wipes data).
Download TWRP.img & TWRP.zip from https://dl.twrp.me/cheryl
Download the Magisk 16.3 from here: https://github.com/topjohnwu/Magisk/releases/download/v16.3/Magisk-v16.3.zip (SuperSU will not work on 8.1 so magisk is your only option)
Download latest Platform tools from Google here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Windows: In file explorer copy the twrp-installer-3.2.1-0-cheryl.zip to the sdcard of the Razer Phone
Windows: In file explorer copy the Magisk-v16.3.zip to the sdcard of the Razer Phone
Windows: Extract platform tools to any folder
Windows: Open a command prompt window at that directory
Windows: adb reboot bootloader
Windows: fastboot boot twrp-3.2.1-0-cheryl.img (This will boot to twrp without flashing) (DONT CLOSE, need it in a few minutes)
Razer Phone: Once in TWRP install zip twrp-installer-3.2.1-0-cheryl.zip then reboot to system after complete.
Windows: Once the Razer Phone has booted back up, go back to the command prompt window
Windows: Adb reboot recovery
Razer Phone: Once in TWRP install zip Magisk-v16.3.zip then reboot to system
All should be good, have not found any issues yet
I take no credit for any files in above tutorial, give credit where credit is due, donate a beer to those guys.
TWRP credit TWRP Team (https://twrp.me/)
Platform tools credit Google (Watch their ads on Youtube?)
Magisk credit Magisk team (https://github.com/topjohnwu)
It's wornking fine so far. Thanks
Thanks, it works.
Wow that was far easier than before thanks
Hm for me it doesn't work at this step: Windows: fastboot boot twrp-3.2.1-0-cheryl.img
It's just saying "Waiting for device"
Sideloading 8.1 and unlocking went smooth, debugging is enabled
SeriousFlash said:
Hm for me it doesn't work at this step: Windows: fastboot boot twrp-3.2.1-0-cheryl.img
It's just saying "Waiting for device"
Sideloading 8.1 and unlocking went smooth, debugging is enabled
Click to expand...
Click to collapse
I had the same problem, make sure the ADB interface driver is installed under device manager again as i think it clears it after windows reboot.
Had to manually edit it while unlocking the bootloader and it stayed on ADB bootloader interface when I had it reboot to bootloader again.
I'll try again tomorrow
Fixed the "waiting for device" "error" by selecting the older Android Bootloader Interface driver.
Now everything worked and my device is rooted!
Nice guide.
thanks for the quick and dirty guide, worked perfectly
Wondering if I'm missing something. Getting the error "FAILED (remote: BootCMD is not allowed in Lock State)" when attempting to boot the twrp image.
I have USB Debugging and OEM unlocking enabled.
PS: Found out the hard way, don't use the provided USB-C cable that came with your Razer phone, USB-A to USB-C cable recommended.
After installing twrp-installer-3.2.1-0-cheryl.zip mobile booting into TWRP only , can't boot into System!!
Installed the zip and Magisk Manager hangs and crashes. Anyone know what this could be?
Is that work without using boot.img file??
DarkestSpawn said:
If you are on the OTA Oreo 8.1 and dont have root, here's how to do so:
First request: Anyone that knows someone that can help get us WFD (Wireless Display Casting) enabled that would be very helpful. If you edit build.prop you can get it to show wireless displays in the System/Connected Devices/Cast but force reboots for me when I try connecting to my HP Lapdock
Now to TWRP/MAGISK
Make sure you are on 8.1, Android debugging is enabled under developer options and bootloader unlocked (Warning if you're not when you do this it wipes data).
Download TWRP.img & TWRP.zip from https://dl.twrp.me/cheryl
Download the Magisk 16.3 from here: https://github.com/topjohnwu/Magisk/releases/download/v16.3/Magisk-v16.3.zip (SuperSU will not work on 8.1 so magisk is your only option)
Download latest Platform tools from Google here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Windows: In file explorer copy the twrp-installer-3.2.1-0-cheryl.zip to the sdcard of the Razer Phone
Windows: In file explorer copy the Magisk-v16.3.zip to the sdcard of the Razer Phone
Windows: Extract platform tools to any folder
Windows: Open a command prompt window at that directory
Windows: adb reboot bootloader
Windows: fastboot boot twrp-3.2.1-0-cheryl.img (This will boot to twrp without flashing) (DONT CLOSE, need it in a few minutes)
Razer Phone: Once in TWRP install zip twrp-installer-3.2.1-0-cheryl.zip then reboot to system after complete.
Windows: Once the Razer Phone has booted back up, go back to the command prompt window
Windows: Adb reboot recovery
Razer Phone: Once in TWRP install zip Magisk-v16.3.zip then reboot to system
All should be good, have not found any issues yet
I take no credit for any files in above tutorial, give credit where credit is due, donate a beer to those guys.
TWRP credit TWRP Team (https://twrp.me/)
Platform tools credit Google (Watch their ads on Youtube?)
Magisk credit Magisk team (https://github.com/topjohnwu)
Click to expand...
Click to collapse
so i did this and here is my only question. Does flashing twrp and magisk inside twrp, install them into both slot a and b? or no. if no then is there a need to manually switch slots and reflash magisk for example?
iliais347 said:
so i did this and here is my only question. Does flashing twrp and magisk inside twrp, install them into both slot a and b? or no. if no then is there a need to manually switch slots and reflash magisk for example?
Click to expand...
Click to collapse
If memory serves I only flashed to the active Slot.
DarkestSpawn said:
If memory serves I only flashed to the active Slot.
Click to expand...
Click to collapse
I ser
Does this method cause a facotry reset?
This seems alot easier than the other methods.
ItzMar said:
Does this method cause a facotry reset?
This seems alot easier than the other methods.
Click to expand...
Click to collapse
It's that easy because of Oreo and the stuff that comes with it. If your bootloader is already unlocked it won't need a factory reset but if not unlocking your bootloader will erase all data on the phone.
Is it best to do with a SD card in the phone or can you do it without?
So doing this without an SD Card at the mo and I get the waiting on device when trying to do fastboot flash boot twrp-3.2.1-0-cheryl.img
Any help?
askylitangel said:
So doing this without an SD Card at the mo and I get the waiting on device when trying to do fastboot flash boot twrp-3.2.1-0-cheryl.img
Any help?
Click to expand...
Click to collapse
Having an sdcard in the device means nothing unless your trying to boot from sdcard...
You're stuck at that point because your fastboot drivers aren't installed or incorrectly. There have been many posts throughout the forum on troubleshooting the drivers, Google search.
Hi. I've just installed LineageOs 20 on my OP Nord, and it's great. The problem is that now some apps don't start at all because of SafetyNet. I have a non rooted phone.
There is a way to let them work again? Or I need to get back to stock rom again?
Thanks
The so-called SafetyNet makes apps unusable on rooted and some otherwise modified devices.
Yes, I know. Is there a way to make them work again? I have some banking apps that I need to use.
Re-flash Stock ROM.
Ok. I can do that with the same method that I used for the lineage os rom? And then I block the bootloader, right?
Re-flashing Stock ROM typically is done via ADB Sideload method. A factory data reset from the Recovery mode is advisable after successful flashing.
If you've TWRP installed:
1. From TWRP, go to Wipe and tap on Format Data. After that, type in YES in the space provided.
2, From TWRP, go to the Wipe section. Then performs a right swipe on the Factory Reset button situated at the bottom. Now, wait for the process to complete.
3. From the TWRP, go to Advanced and select ADB Sideload. Then perform a right swipe to start the Sideload process:
3.1 Now connect your device to the PC via USB cable.
3.2 In Windows OS shell type in CMD, and hit Enter, this will launch the Command Prompt.
3.3 Type in the following command in the CMD window to verify the ADB Sideload connection
Code:
adb devices
If you get the device ID followed by the sideload keyword, then the connection stands successful and you may enter the following command to install the Stock ROM
Code:
adb sideload <PATH-OF-STOCK-ROM-ZIP-FILE-HERE>
Now, wait for the process to complete.
4. From TWRP boot the device to the newly installed OS by going to Reboot > System
If you don't have TWRP installed:
1. Connect your device to the PC via USB cable.
2. In Windows OS shell type in CMD, and hit Enter, this will launch the Command Prompt.
3 Type in the following command in the CMD window to verify the ADB Sideload connection
Code:
adb devices
4. If you get the device ID followed by the device keyword, then the connection stands successful and you may enter the following commands to install the Stock ROM
Code:
adb reboot sideload
adb sideload <PATH-OF-STOCK-ROM-ZIP-FILE-HERE>
Now, wait for the process to complete.
HTH
Ok, I have the recovery made by the lineage os team, but I think the procedure is the same.
Thank you very much
Does the Pixel Experience Rom pass safety net?
You're told to re-flash STOCK ROM.