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.

Soft bricked phone? Can't install recovery and can't install a rom

Okay so I got my oneplus 3t today and I updated it to Nougat via the ota file all good so far. I then decided that I wanted to install a custom rom so I downloaded twrp supersu etc everything needed to root and install the rom. Here's where it went wrong in knowingly I downloaded the wrong twrp flashed it and it would just hang at the flash screen for twrp. Anyway after hours of trying to install a recovery I managed to get a stock one to semi work, now it turns out I don't know how I did it but my phone won't even boot it just turns on and goes straight to fastboot mode. I managed to get a stock recovery semi working but it won't let me install the stock rom from internal storage and I've tried updating through adb and it will hang at a random percentage for a good 20 mins and then just fail. Really need some help here it would be great, thanks

Hi,
If you can get into fastboot mode then the best recourse is through there. Hope you properly OEM unlocked your device.
First of all, you MUST have the latest adb/fastboot binaries and FOR SURE have the correct drivers.
Follow the links on this XDA article to download the latest adb and fastboot binaries: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads
This is the link for the Windows binary: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract all the contents of the zip file in a folder on your PC.
Then, also make sure to have THE CORRECT twrp, 3.0.2.0 or 3.0.3.0. This is the link but currently it is down: https://twrp.me/devices/oneplus3t.html
Download THE IMAGE, NOT FLASHABLE ZIP and put it in the same folder as the android platform tools above.
Finally, download the latest complete 3T firmware from OnePlus from this link: http://downloads.oneplus.net/devices/oneplus-3t/
I STRONGLY recommend not to use an update zip, even a full ROM update zip as that one might not include certain firmware images.
Put THE ZIP on the same folder as the others, DO NOT EXTRACT ANYTHING.
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
After that, enter TWRP's Wipe menu and wipe system, data and cache.
Finally, use TWRP's Advanced menu and enter adb sideload mode. Once there slide that slider to the right to enable adb mode and return to your PC and enter the following command in the command prompt:
adb sideload OnePlus3TOxygen_28_OTA_029_all_1612131737_17e7161d2b234949.zip (assuming you downloaded the 3.5.4 binary from OnePlus).
TWRP should properly flash the OnePlus ROM and hopefully, return you to proper function. You can then update back to Nougat.
Hope that helped!

Yeah that sorted it thanks a lot

Use the emergency tool for OP3T and start from scratch:
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/

@KeyperOS
I'm trying to follow this guide, but did you miss something out here?
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
Click to expand...
Click to collapse
Once I do "fastboot boot twrp" and get a success, then what?
Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own.
If so, how do I do this?
Thanks,

jackmacbunton said:
Yeah that sorted it thanks a lot
Click to expand...
Click to collapse
Glad that sorted it out
PugRallye said:
@KeyperOSI'm trying to follow this guide, but did you miss something out here?
Once I do "fastboot boot twrp" and get a success, then what? Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own. If so, how do I do this? Thanks,
Click to expand...
Click to collapse
My instructions while detailed are not step-by-step. I expect the person reading them to have their PC configured correctly and at least a vague idea of what they're doing.
So, assuming you put the correct TWRP image (my command uses the name of the image for TWRP 3.0.3.0, you MUST alter it to reflect the actual image's filename if it's not that) on the same folder as the fastboot binary then yeah, the command
fastboot boot twrp-3.0.3-0-oneplus3t.img
should have made your phone reboot and enter into the TWRP image that you had on your PC.
If it didn't then you did sth else wrong before that.
Either you didn't OEM unlock your phone when you still could or you didn't use the android platform tools that I linked or you don't have the correct ADB drivers installed on your PC.
Start from there.
Hope that helped!

Thanks for your help @KeyperOS - I know where I went wrong...
To save some time, when I tried to reboot into TWRP, I typed "fastboot boot " then I dragged and dropped the TWRP img file onto that line in the cmd window (rather than typing the filename manually) - when you do that, it appears to include the full path to the img - it was that that was causing the problem.
When I typed the TWRP filename manually, it worked.
The only thing that caught me out was after I'd installed the ROM (via adb sideload) I tried to reboot the device from TWRP recovery - this seemed to just hang. In the end I just powered off the phone using the power key, then powered it back up as per usual.
Checked that the phone booted to the first of the setup screens, then powered off/booted into fastboot mode, relocked the bootloader and it seems to be OK.
I'm now back on 3.5.4 again, which was what I was trying to do...
4.0.0/1 had felt a bit laggy, and I'd sensed some issues with wifi and BT, I can now run 3.5.4 and see how it compares - was I just imagining it?
Thanks again for the guide and your help - I really appreciated it

@PugRallye
Windows' command prompt has an autocomplete feature. If you want it to add the name of a file, type a couple letters and then present TAB, it's gonna complete the filename itself and if it's the wrong file you can keep tapping tab to cycle through all the options.
Really glad it worked out Btw [emoji4]
In my experience, 3.5.4 was great but 4.0 is a step up in both battery life, which IME is amazing and features, with it I almost didn't need root and certainly don't need xposed which was a first.

TWRP 3.0.2 for Acer Predator 8 ported by Ruben.

IMPORTANT NOTE ABOUT ROOTING:
After flashing TWRP 3.0.2, use the SuperSU 2.46 flashable zip, do NOT use latest version or will result in a bootloop. Good Luck and have fun with rooting.
REQUIREMENTS
1- Unlocked Bootloader (search on google if you dont know how to unlock)
2- Drivers and Adb/Fastboot commands knowledge
--------------------------------------------------------------------------------------------------------------------------------
New TWRP bugfix update! Now you can flash stock rom on TWRP without bricking! Download Page updated!
Bugs:
1- adb shell command needs to be sent before system partition is mounted or it will give an error, after doing adb shell you can mount system and do all the modifications you need.
2- You cant flash any img on twrp it gives an error, im trying to fix.
3- Backups do work, but everytime twrp restarts, the serial number folder seems to change (which means that on /TWRP/BACKUPS/serialnumber/backupsinside/ changes every reboot so you have to go get the backup inside the old serialnumber folder and put on the new serialnumber folder).
Im leaving an unsecured boot image because system does not boot android if anything seems changed. So please if system does not boot after flashing twrp/rooting, flash the unsecured boot img on fastboot
Steps to Install TWRP and root
1. Download and extrct the files: https : // drive. google . com/file/d/0BxzG5iupOOSKNTdlRC1Wd0VmTlk/view
2. Power off the tablet.
3. Enter fastboot mode by pressing the power button while holding down Vol -
4. Open up command prompt and navigate to the directory where fastboot.exe is located.
5. Pass the following commands:
fastboot flash boot unsecuredboot.img
fastboot flash recovery TWRP.img
6. Reboot into recovery (TWRP) and install SuperSU v2.46.zip ---
Continuation 6. Step by Step of Step 6 since people seem to have been running into issues with it:
After rebooting to TWRP and having SuperSU.zip in the tablet storage. Go on Install tab and press the supersu file and install/flash it then reboot the device.

[OFFICIAL] Motorola Edge 5G Racer TWRP

The developers have a lot going on at the moment, i know many have been asking for it, now that it is Official, i think it's safe enough for Public Use. I'm sure the DEVs will post a "more Official" Thread in the right spot. I did not post under Recovery because that is for DEV Use ONLY.
Official TWRP img and Installer zip : https://twrp.me/motorola/motorolamotoedge.html
***Dont forget to flash copy-partitions.zip if you are flashing a Custom ROM. The main device trees now include this, meaning it comes with MOST, NOT ALL, Custom ROMs. YOU WILL NOT BREAK ANYTHING, if the Custom ROM you are flashing already includes this and you flash the copy-partitions.zip. Better to be safe then sorry. This is required anytime you fastboot flash back to STOCK Firmware.INSTALL "Copy Partitions Zip" FROM POST #2
Installation:
NOTE: Your bootloader MUST be UNLOCKED before booting or installing TWRP If you already have TWRP installed: Download the latest zip and install the zip using TWRP, or flash directly the image directly to recovery in fastboot. If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have the latest fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader menu. Connect the device to your PC. Open a command window and run the following command from the proper location:
Zip method: fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. Use ADB or MTP to push the zip onto your device:
adb push path/to/twrp.zip /sdcard
Go to install and browse to the zip and install the zip. The zip will install TWRP on recovery partition of both slots.
Image Method: fastboot flash recovery_ path/to/twrp.img

Moto_Fan said:
The developers have a lot going on at the moment, i know many have been asking for it, now that it is Official, i think it's safe enough for Public Use. I'm sure the DEVs will post a "more Official" Thread in the right spot. I did not post under Recovery because that is for DEV Use ONLY.
Official TWRP img and Installer zip : https://twrp.me/motorola/motorolamotoedge.html
***Dont forget to flash copy-partitions.zip if you are flashing a Custom ROM. The main device trees now include this, meaning it comes with MOST, NOT ALL, Custom ROMs. YOU WILL NOT BREAK ANYTHING, if the Custom ROM you are flashing already includes this and you flash the copy-partitions.zip. Better to be safe then sorry. This is required anytime you fastboot flash back to STOCK Firmware.INSTALL "Copy Partitions Zip" FROM POST #2
Installation:
NOTE: Your bootloader MUST be UNLOCKED before booting or installing TWRP If you already have TWRP installed: Download the latest zip and install the zip using TWRP, or flash directly the image directly to recovery in fastboot. If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have the latest fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader menu. Connect the device to your PC. Open a command window and run the following command from the proper location:
Zip method: fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. Use ADB or MTP to push the zip onto your device:
adb push path/to/twrp.zip /sdcard
Go to install and browse to the zip and install the zip. The zip will install TWRP on recovery partition of both slots.
Image Method: fastboot flash recovery_ path/to/twrp.img
Click to expand...
Click to collapse
Having a problem, even unlocking the bootloader. Unlock my device, doesn't show a blue button, and msg, says"it can't be unlocked" . In any case, I downloaded all the software that was on page, when I can figure this out.

reggjoo said:
Having a problem, even unlocking the bootloader. Unlock my device, doesn't show a blue button, and msg, says"it can't be unlocked" . In any case, I downloaded all the software that was on page, when I can figure this out.
Click to expand...
Click to collapse
If you can't go passed #1, don't go any further, but I can only recommend.

[Guide] How to install custom rom on android 11 and how to get TWRP + root on android 11

Foolproof method to install roms, twrp + root.
Read through the directions first before you start anything and your phone wont get bricked. Even if it does, you can use the msm tool guide that I linked below to restore it and get it prepped up for custom rom install again.
Pre-requisites:
1) Update to latest android 11 through software update.
2)Have oneplus drivers and adb/fastboot drivers installed
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Download TWRP unofficial for oneplus 7 pro android 11 here and move it into minimal adb and fastboot folder
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
3a)Download Magisk v23.0 if you want root
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
3b) Move custom rom into internal storage like download folder for custom rom install
if you have issues with fastboot not recognizing device or other driver issues, click this link https://www.droidwin.com/fix-android-device-not-showing-in-fastboot-mode/
*****Extra Steps Required for T-mobile variant for installing custom roms****
-I tried everything and couldnt get havoc os to install on my t-mobile variant. It would always end up in a bricked state. To get around this, you first need to convert it to international following this guide then follow steps below after you have kept updating it in system until there are no more updates available. https://forum.xda-developers.com/t/guide-how-to-convert-tmobile-op7-to-international.3935947/
Guide for installing custom rom over android 11
-unlock bootloader and enable usb debugging then connect phone- use this video on how to unlock bootloader but dont follow his other steps yet
-open up cmd in minimal adb and fastboot folder and type in adb devices and make sure phone shows up
-in cmd, type in "adb reboot bootloader"
-in cmd, type in "fastboot devices" and make sure phone shows up
-in cmd, type in fastboot boot "name of your twrp file"
It should boot into twrp. at this point, you should have your rom zip file in the internal storage
-install the custom rom.zip. In my case, i installed havoc 4.8. After thats done, go back to wipe and format data. For extra measures, go to wipe and advanced wipe and wipe dalvik cache, data and vendor then reboot.
-to get root, set up the phone and enable usb debugging again. Transfer magisk v23.0 to download. adb reboot bootloader and go into recovery if your rom has one(havoc has its own) or fastboot into twrp again and install magisk. At this point, you can also install twrp if you want. Follow the guide above to install the unofficial twrp.
Guide for installing TWRP and root on official android 11
-unlock bootloader and enable usb debugging then connect phone- use the video above on how to unlock bootloader but dont follow his other steps for twrp yet
-open up cmd in minimal adb and fastboot folder and type in adb devices and make sure phone shows up
-in cmd, type in "adb reboot bootloader"
-in cmd, type in "fastboot devices" and make sure phone shows up
-in cmd, type in fastboot boot "name of your twrp file"
It should boot into twrp. at this point, you should have magisk v23.0zip in your internal storage like in download folder if you want root
-go to advanced then flash current twrp
-then install magisk v23.0 and you're done