Database Develop

Lollipop OTA Update via ADB - Keep Data - Restore Root

Just thought I'd share, might help someone. This is for Nexus 7 previously bootloader unlocked and rooted (and whatever else, like xposed) going from 4.4.4 to 5. If you're not on 4.4.4 and bootloader unlocked get there first. Obviously you need usb debugging on.
You also need some form of adb and fastboot. I used Minimal ADB from here:
http://forum.xda-developers.com/showthread.php?t=2317790
What I Did:
- Got the Lollipop OTA from the links posted everywhere by now, including the second sticky here in General.
Put a copy in the adb/fasboot folder in Windows, and renamed the file to updatelollipop.zip to make it easier to handle.
Tried old style of updating: Uninstall Xposed, flash Xposed Disabler, flash OTA zip from custom recovery. Failed. Tried again, failed again.
But this was expected, as I'd read that the way lollipop updates is different from all previous updates and will fail at the slightest discrepancy in system partition.
So, need clean system.
- Got the Stock 4.4.4 firmware from Google: https://developers.google.com/android/nexus/images
Inside the firmware file found the system.img and recovery.img images.
Put these two files in the same folder as minimal adb and fastboot.
- Got into bootloader.
if powered off hold power and volume down keys. if booted up in Minimal ADB command prompt window type:
adb reboot bootloader
- flashed stock system and recovery
fastboot flash system system.img
fastboot flash recovery recovery.img
- Got into stock recovery
In bootloader, scrolled to select recovery, then with "No Command" showing held power and clicked volume up.
Select apply update from adb. Screen says to type adb sideload update from computer.
Ran into a hiccup. ADB would not recognize my N7. typing "adb devices" returned empty result. Booted up into Android, computer and adb recognized device fine. typed adb reboot bootloader, and in bootloader adb no go.
So while connected to computer in bootloader mode, went into Device Manager in Windows. Sure enough there was unknown device called grouper. Promptly update the driver. I used driver files from the Wugfresh toolkit I had installed. The device was recognized as Google Galaxy Nexus ADB device. Didn't matter to me as long as it was recognized as ADB. If you want official drivers you can get them from Asus here: http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2
- Back into ADB sideload screen in N7 stock recovery.
typed adb sideload updatelollipop.zip
Let the ADB push the file, then stock recovery did the update. no issues. back in recovery might as well erase cache partition.
Root then. Could use Wugfresh NRT but decided to go manual.
UPDATE: As of SuperSU 2.27 Beta, flashing SuperSU from custom recovery is enough to gain root on Lollipop 5.0. Root kernel is no longer needed!
Old fashioned root failed works now: get the latest twrp recovery (copied it into adb folder, renamed it to twrprecovery.img), get the latest superSU (put it anywhere in N7 internal storage), flash the latter with the former:
In command prompt, typed fastboot boot twrprecovery.img
this temp booted twrp. promptly went to install, found superSU zip, flashed it.
Booted into Android, Lollipop looks nice, but No Root.
Again, not surprised, had already read lollipop needs modified kernel for root. Looked in the Wugfresh NRT files, had two candidates, modified boot img and root kernel img. not sure the difference, but the two files had different file sizes, and I had read somewhere that modified kernel would keep most of the security features of stock kernel, only modifying permissions needed for root, so decided to go with the kernel img file. Copied it over to adb fastboot folder, renamed it rootboot.img
- got back into bootloader. in command prompt typed
fastboot flash boot rootboot.img
Rebooted into Android, had root! Great. Notice didn't need to flash superSU a second time.
To check if root works fine, just open superSU app. If it opens fine then you're good. Root apps will ask for root, and granting will work fine, but that doesn't mean the apps will be able to use root for the simple reason that they might need to be updated. for example, es file manager asked for root, was granted, but root directories showed empty. clearly needs an update. Tried Total Commander, gave root, worked fine. So apps ability to use root in lollipop will vary based on their need to be updated to work.
thanks as always to Wugfresh and Chainfire.

"Unknown Device" when USB Debugging On
Speaking of root apps needing update, one app that needed updating if you use it, is Adbd Insecure. Why am I singling it out? Because it had me running around in circles trying to figure out why Windows was claiming my N7 was an Unknown Device.
Thing is, I installed adbd insecure long ago set on auto start, and it's useful for when it's needed, but I had completely forgotten about it now when trying to figure out the driver issue. Turning off USB debugging Windows happily recognized MTP, but who wants debugging off, it's a bad idea.
After twirling in circles finally decided to check if Windows would recognize bootloader and recovery mode. Sure enough, everything was good there. Rebooted into Android and noticed ADB was recognized briefly upon startup before it went away. That got me suspicious which led me to the culprit. So, yeah, save yourself some trouble and update that app, if you have it running.

razr i kitkat root method via twrp

hello xda people,i thought i might share this with you since i've tested and done it myself about rooting kitkat eu update.My bootloader was factory locked and proceeded unlocking it and i barely managed to install Hazou's unoficial twrp recovery(see this thread:http://forum.xda-developers.com/showthread.php?t=2278483) wich was done via fastboot,but mostly even after the custom recovery install i didn't managed to get root on kitkat,so i've tried ChainsDD superSU update pack witch seems to resolve the problem because the update package installs the propper package according to system specs,so if anyone there wishing to root or doesn't quite figure out,here's an simple how to:
1Make sure you have all the drivers installed.
2install or download android sdk
3 from the sdk,copy on your desktop platform-tools (for easier job)
4 download recovery image from Hazou thread,see: http://forum.xda-developers.com/showthread.php?t=2278483 extract and place it on platform-tools folder you copied on your desktop
5in platform-tools folder open cmd line and enter your phone in fastboot
6type "fastboot devices" without quotes
7 if your device is listed,type: fastboot flash recovery recovery.img
8now after cmd confirms if the flash was succesfull, either head to recovery from fastboot mode and see if twrp is installed,if it does keep your phone connected to pc
9 download chainsDD superSU update to external sd,link to download https://drive.google.com/file/d/0B8m4rdNFVU4_YjV4X2gtUjNhZVE/view?usp=sharing
10 install via twrp,wipe davik+cache, reboot and enjoy

You can get the latest CWM / TWRP / MobileODIN installable ZIP from here. It has x86 support and works on the Razr i.

drunk_ryder24 said:
hello xda people,i thought i might share this with you since i've tested and done it myself about rooting kitkat eu update.My bootloader was factory locked and proceeded unlocking it and i barely managed to install Hazou's unoficial twrp recovery(see this thread:http://forum.xda-developers.com/showthread.php?t=2278483) wich was done via fastboot,but mostly even after the custom recovery install i didn't managed to get root on kitkat,so i've tried ChainsDD superSU update pack witch seems to resolve the problem because the update package installs the propper package according to system specs,so if anyone there wishing to root or doesn't quite figure out,here's an simple how to:
1Make sure you have all the drivers installed.
2install or download android sdk
3 from the sdk,copy on your desktop platform-tools (for easier job)
4 download recovery image from Hazou thread,see: http://forum.xda-developers.com/showthread.php?t=2278483 extract and place it on platform-tools folder you copied on your desktop
5in platform-tools folder open cmd line and enter your phone in fastboot
6type "fastboot devices" without quotes
7 if your device is listed,type: fastboot flash recovery recovery.img
8now after cmd confirms if the flash was succesfull, either head to recovery from fastboot mode and see if twrp is installed,if it does keep your phone connected to pc
9 download chainsDD superSU update to external sd,link to download https://drive.google.com/file/d/0B8m4rdNFVU4_YjV4X2gtUjNhZVE/view?usp=sharing
10 install via twrp,wipe davik+cache, reboot and enjoy
Click to expand...
Click to collapse
I like this method, you're always left with a fallback or the option to the Rom flash again or use an alternate when using recovery, I've started to prefer TWRP over clockwork recently

Stuck on Boot After installing SuperSU Binary [URGENT][Solved]

[Update]: Now it says no OS installed in TWRP. I think I have wiped the os by mistake. Just need to know how to install cm13 image using fastboot or ADB. Please help!
I wasn't aware if SuperSU works with CM13 and I installed the app, on request to update the binaries, I selected TWRP/CWM method because the normal mode didn't work. After the reboot the phone won't load into os, its stuck on the CM boot screen. I don't have a CM image on my sd therefore unable to flash again either. Is there a way to push files (cm img) to my phone? I have adb/adb over network enabled as well from developer options. I just need a way to put files into my sd card and flash using TWRP. Please help! this is urgent! :crying:
[SOLVED][HOW TO]
This is in a situation where you've messed up your system and don't have the image file stored in your sd card for quick flashing. Make sure you're using the latest USB drivers and ADB binaries 1.0.32+
- Get into TWRP
- Swipe to ADB Sideload and enable it
- On your desktop, open command and type "Adb sideload filename.zip" [Filename here is the filename of your flashable zip/rom]
- Once you the installation finishes, reboot twrp normally into system

dibyajyoti said:
I just need a way to put files into my sd card and flash using TWRP. Please help! this is urgent! :crying:
Click to expand...
Click to collapse
Have you tried enabling MTP in TWRP and using a computer to transfer the image over?
Contact me if you have any questions.

R55770 said:
Have you tried enabling MTP in TWRP and using a computer to transfer the image over?
Contact me if you have any questions.
Click to expand...
Click to collapse
MTP shows as enabled - But the device doesn't show up in my pc. I'm connected through USB in TWRP recovery. I have android debugging also enabled, when trying adb push command, it shows adb devices attached as empty.
[Update]: I am trying to push the file using ADB Sideload in TWRP, the error I get is my adb needs to be updated to 1.0.32. How do i get updated adb 1.0.32?
[Update 2]: So I managed to update by ADB on desktop, and push the zip file using adb sideload in twrp. The zip is being installed as I write this. Lets hope this works!
[Update 3]: Got the rom to install via ADB sideload, though all my apps and settings are gone Anyway, I got the phone back for immediate use. Phew!

dibyajyoti said:
MTP shows as enabled - But the device doesn't show up in my pc. I'm connected through USB in TWRP recovery. I have android debugging also enabled, when trying adb push command, it shows adb devices attached as empty.
[Update]: I am trying to push the file using ADB Sideload in TWRP, the error I get is my adb needs to be updated to 1.0.32. How do i get updated adb 1.0.32?
[Update 2]: So I managed to update by ADB on desktop, and push the zip file using adb sideload in twrp. The zip is being installed as I write this. Lets hope this works!
[Update 3]: Got the rom to install via ADB sideload, though all my apps and settings are gone Anyway, I got the phone back for immediate use. Phew!
Click to expand...
Click to collapse
Great. Thanks for letting us know.

sideload error no device

sorry if this is the wrong place...this is my problem
I got an old tablet off someone that i want to bring back to life, its an ares 8, model #NXA8QC116. unfortunately the sd card slot is broken so using it is out of the question..I have TWRP 3.0.2 on it and im trying to flash SU to it via "adb sideload."
when in system using "adb devices" it shows the device as well as in recovery mode, but when i try to use the sideload feature in TWRP i get a "ADB sideload failed no devices/emulators found error..if i try "adb devices here it does not show a device..im not sure if this is the problem. Also i cant FLASH SU BECAUSE IT IS NOT SHOWING UP IN twrp nor are any other zips which ive read is because of the encryption is still enabled? i have the disable encryption .zip but cant flash that eaither due to my same problem of .zips not showing up.
All the device drivers and adb+fastboot are setup properly as far as i can tell but i get the error no matter what i do.
my questions are..
1. is there and OTHER method i can use to flash SU.zip or the decryption.zip file without the use of an SD card?
2. does anyone have any ideas on how i can go about fixing the no devices/emulators found error while in sideload mode?
thank you very much for your anticipated reply!
1. is there any OTHER way to flash SU using

Lost root on Xiaomi Mi A1 after updating to Magisk 19.2

Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
Code:
- Device platform: arm64-v8a
- Existing zip found
- Copying image to cache
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!

maretodoric said:
Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!
Click to expand...
Click to collapse
I'm also getting same error how did you managed to find the solution...

maretodoric said:
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager.
[...]
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Click to expand...
Click to collapse
Similar problem here, but with Magisk 19.3.
Could you pass a link to patched boot image,you used? Can´t find it...
Thanks

I didn't download boot.img, it's best that you extract it yourself by using ADB.
Download adb software, there should be some tutorial here on forums how to find and get it (possibly https://forum.xda-developers.com/mi-a1/how-to/computer-setup-rooting-gcam-setup-t3731526) , but Windows 10 SHOULD natively have it (at least i did, i didn't have to install anything, already had ADB).
Now here comes the tricky part. I didn't remember this and i didn't write it down. When this happens again to me, i will be in huge .......
I'm sorry i can't help you, but try to google for info on how to extract boot.img from current installation using fastboot or adb.. not sure which, possibly fastboot.
Then you will have clean untouched boot.img from official repo. No need to wait for it to appear on xiaomi site.
If i find a tutorial, i will post it here. Please do the same if you find it before me.
GOT IT!!!
- Follow the previous tutorial if you do not have adb and fastboot, so you can install them. There should be plenty of tutorials how to install both of them
- After you installed it, download this version of TWRP https://dl.twrp.me/tissot/twrp-3.3.0-2-tissot.img.html to your desktop
- Connect your phone to your PC via USB cable
- Open command prompt (in Windows, hit CTRL+R then type in cmd)
- Change directory to desktop, for example type cd C:\Users\<username>\Desktop - replace "<username>" with your username ofcourse.
- Type adb reboot bootloader - it will boot to fastboot mode
- Once the phone is in fastboot mode, type fastboot boot twrp-3.3.0-2-tissot.img (keep cmd prompt open)
- It will boot into recovery, click on "Backup"
- Select "Boot"
- Click on Select Storage and there choose Internal Storage, click on OK
- Then on the bottom part of the screen, just swipe to right to extract boot.img (It should literally say "Swipe to Backup"). Pay attention to messages, it will display the directory where it will place the boot.img, but it will not be strictly named boot.img
- In my case, it's in Internal Storage/TWRP/BACKUPS/00bf23cc0904/2019-06-20-14-25-3_PKQ1/boot.emmc.win
You can either rename it to boot.img or just leave that name. But either way, open new magisk manager, select "Install" next to Magisk (not magisk manager), click on "Select and Patch a file", point to your new boot.img or boot.emmc.win.
Magisk will patch that image and show you the new location. Just download that file to your PC, on desktop, cmd again "adb reboot bootloader", and when it gets to fastboot mode, type "fastboot flash boot magisk_patched.img".
You should be good to go!