Related
I've seen posts requesting "how to" and posts of problems attempting to root after installing the 5.1 OTA update. This post outlines the steps to root with an UNLOCKED BOOTLOADER.
NOTE: This will only work if your bootloader is already unlocked. It is based on -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 but slightly updated.
Don't know if your bootloader can be unlocked? see -> HERE
Requirements...
the latest TWRP fastboot IMG file (Alternate Link) UPDATE: There is an issue with TWRP 2.8.7.0 (SEE THIS POST Thanks @jodaboda ). Please use TWRP 2.8.6.0 for now!
the latest Installable ZIP of SuperSU (Alternate: http://download.chainfire.eu/supersu )
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools will likely work, but Moto's fastboot is always suggested!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The steps...
NOTE: replace TWRP.IMG in the below steps, with the name of the file you downloaded!! Example: twrp-2.8.6.0-ghost.img
NOTE: failure to perform these steps EXACTLY as written can result in the apparence of the Android in distress (logo with Exclamation mark) with the caption "No Command" and the inability to enter recovery, OR it will enter STOCK recovery even though you have flashed TWRP!
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you downloaded your TWRP.IMG file.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery TWRP.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device should enter TWRP.
If your device is not rooted, TWRP may prompt you to root now or install SuperSU. Do it.
Use the menu options to Reboot to system.
You will likely be prompted to UPDATE SuperSU. Please update it, and reboot.
IF TWRP doesn't prompt you to root/install SuperSU.... (more exact instructions coming later...)
With your phone booted normally, connect it via USB cable to your PC.
Drag/Drop the SuperSU.zip you downloaded onto the phone's internal storage
Reboot the phone into TWRP
Use the menu option to install zip, navigate to and select the SuperSU zip.
Boot to System.
EDIT: 9-17-2015 edited first TWRP link.
KidJoe said:
I've seen posts requesting "how to" and posts of problems attempting to root after installing the 5.1 OTA update. This post outlines the steps to root with an UNLOCKED BOOTLOADER.
NOTE: This will only work if your bootloader is already unlocked. It is based on -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 but slightly updated.
Don't know if your bootloader can be unlocked? see -> HERE
Requirements...
the latest TWRP fastboot IMG file (Alternate Link)
the latest Installable ZIP of SuperSU (Alternate: http://download.chainfire.eu/supersu )
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools will likely work, but Moto's fastboot is always suggested!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The steps...
NOTE: replace TWRP.IMG in the below steps, with the name of the file you downloaded!! Example: twrp-2.8.6.0-ghost.img
NOTE: failure to perform these steps EXACTLY as written can result in the apparence of the Android in distress (logo with Exclamation mark) with the caption "No Command" and the inability to enter recovery, OR it will enter STOCK recovery even though you have flashed TWRP!
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you downloaded your TWRP.IMG file.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery TWRP.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device should enter TWRP.
If your device is not rooted, TWRP may prompt you to root now or install SuperSU. Do it.
Use the menu options to Reboot to system.
You will likely be prompted to UPDATE SuperSU. Please update it, and reboot.
IF TWRP doesn't prompt you to root/install SuperSU.... (more exact instructions coming later...)
With your phone booted normally, connect it via USB cable to your PC.
Drag/Drop the SuperSU.zip you downloaded onto the phone's internal storage
Reboot the phone into TWRP
Use the menu option to install zip, navigate to and select the SuperSU zip.
Boot to System.
Click to expand...
Click to collapse
I still haven't unlocked my Bootloader (being on 5.1). In the linked post it's been mentioned that "TWRP custom recovery for KitKat" - my question is, is there a TWRP Custom Recover for OTA 5.1 update? And I'm on XT1052, same procedure follows?
Do you know where I can find mfastboot for Mac OSX?
kidjoe, your a priceless resource!
i installed an older verison of twrp and had all the issues you speak off, installed 2.8.6 with success but would not root upon reboot, installed the super su zip in op via twrp, one last thing i had to enter the super su app and tap enable superuser and now all is good:good::good
Thanks, worked like a charm
Thanks.. It's been ages since I used I last used adb commands and flashed something. I couldn't figure out how to boot into recovery.
Vampirexox said:
I still haven't unlocked my Bootloader (being on 5.1). In the linked post it's been mentioned that "TWRP custom recovery for KitKat" - my question is, is there a TWRP Custom Recover for OTA 5.1 update? And I'm on XT1052, same procedure follows?
Click to expand...
Click to collapse
twrp-2.8.6.0-ghost.img works on Lollipop too. (just used it last night on my sister-in-law's GSM Dev Edition XT1053 that got the lollipop update)
jay_em said:
Do you know where I can find mfastboot for Mac OSX?
Click to expand...
Click to collapse
Here is a copy on my Box 'drive':
https://app.box.com/s/5nlgy2avccupw4box8z2be50ezt4qn7p
EDIT: I just got an e-mail saying it had been downloaded. :good:
---------- Post added at 08:54 AM ---------- Previous post was at 08:45 AM ----------
kyzn said:
Thanks.. It's been ages since I used I last used adb commands and flashed something. I couldn't figure out how to boot into recovery.
Click to expand...
Click to collapse
EDIT: [If you are still running the stock Recovery] You can also use:
Code:
adb reboot recovery
When you see the horizontal robot hold the Volume Up key for 3 seconds and then tap Power and the Recovery Menu will display.
Thanx for this how-to. Everyone has been getting confused in root process for 5.1 although it is nearly same as 4.4.4.
Sent from my XT1052
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
jodaboda said:
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
Click to expand...
Click to collapse
I had the same issue with my XT1053. Following your advice did the trick. Not being able to modify my dpi since upgrading has been killing me. Its the only thing i really want root for. Thanks for everything both you and op!
jodaboda said:
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
Click to expand...
Click to collapse
Ahh... 2.8.7 wasn't out when I tried.. 2.8.6 was the latest at that time. Maybe there is a bug in 2.8.7 that will get fixed in future versions?
Sunshine unlocked bootloader
Does anyone know if there are any issues resulting from a Sunshine unlocked bootloader? I saw one post that had a warning but it was a warning because there was no information at the time. Has this change?
i installed TWRP successful, but after normal reset, TWRP is gone, it's only stock recovery (Android down image). Please help me. My phone is running 5.1 update OTA, unlocked bootloader
md07 said:
i installed TWRP successful, but after normal reset, TWRP is gone, it's only stock recovery (Android down image). Please help me. My phone is running 5.1 update OTA, unlocked bootloader
Click to expand...
Click to collapse
When you say "installed TWRP successful"... do you mean that fastboot didn't error? or that fastboot completed the install, you did a mfastboot reboot-bootloader, and tried entering TWRP but it still gave you the "dead android" image?
Is there any unofficial way to unlock bootloader?
Sent from my Nexus 7 using Tapatalk
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
djibril13 said:
Is there any unofficial way to unlock bootloader?
Click to expand...
Click to collapse
Sunshine... IF you're phone has never been upgraded to 4.4.4.
BUT if you can get unlock code from Moto, while it can void your warranty (depending on your local laws), that is FREE, and the best way.
SX86 said:
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
Click to expand...
Click to collapse
help me understand your situation...
You are doing.. Mfastboot flash recovery -> mfastboot reboot-bootloader -> you get battery charging screen rather than fasboot/bootloader menu/screen?
or ??
SX86 said:
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
Click to expand...
Click to collapse
after flashing did you but to recovery befour booting system? with my experience i had to boot to recovery first befour system
Hey guys. I've tried everything, and I'm stuck. Never had so much trouble doing something so basic. No idea where it's going wrong.
Here's the basic timeline:
1. Bought phone
2. Unlocked/rooted/flashed TWRP
3. Tried CM13 for a bit, clean flash +supersu
4. Tried Exodus for a bit, clean flash + supersu
5. Tried community build of 3.0.1, clean flash +supersu
6. Wanted OTA update, so dirty flashed community build to remote root, OTA update ended up replacing TWRP with stock recovery
7. I want to go back to exodus, and can't for the life of me get TWRP back on
Here's what I've tried:
1. Basic steps on any website to download adb drivers etc.
2. Tool box from XDA
3. Factory reset then try all of the above again
Issues:
When I try to fastboot flash recovery [file] I get error: cannot load 'recovery.img' I've tried renaming it to twrp.img as I've seen suggested in some places, no help. I've ensured that the image file is in the same folder as the command prompt. I have used the Grarak TWRP file as well as 3.0.2 and 2.8.7 as suggested on some other sites.
Things I'm noticing:
When I try the fastboot devices command, it only recognizes my device when in fastboot mode, but not when loaded normally. In fastboot mode I can issue commands to reboot, get info, etc. but once loaded it's all gone.
I haven't seen that prompt that comes up to authorize a computer RSA code for USB debugging (yes, USB debugging is enabled in developer options, and yes, I have tried changing the USB settings from charging, to MTP, PTP, even MIDI.)
When I use the device-info prompt I get the following results:
Device Tampered: false
Device Unlocked: true
Device is_verified: false
Charge screen enabled: false
Display panel:
console_locked: 1
exec_console_unconsole: 0
Any and all suggestions would be greatly appreciated!
Hi, Here's what i believe you need to do. If you have the correct twrp recovery img file and all you need is to just flash it to get custom recovery in order to continue enjoying your custom roms, then this will fix your problem.
1. make sure you have all the necessary adb, fastboot drivers installed and that if you run the command 'fastboot devices' fastboot can see your Oneplus device.
2. if fastboot can see your oneplus device, then worry not. use the following command to flash your custom twrp recovery.
3. Rename your recovery file to just recovery nothing else attached.
4. boot your phone into fastboot, open the folder where you have your recovery file and hold down the shift key and rightclick anywhere in the folder and select the option that says 'Open command Window Here'
5. this will load fastboot. after fast boot loads, enter the following commands :
fastboot devices (this will display your device, once your device is showing, then worry not)
6. the next command is to flash your custom recovery image. so u need to enter exactly the following :
fastboot flash recovery recovery.img (this will then flash your custom recovery. make sure you name it just recovery)
7. after flashing your recovery, enter : fastboot boot recovery.img (this will boot you into twrp recovery mode)
let me know if this helps. Cheers!!
Try to flash Hybrid recovery using fastboot. --> http://forum.xda-developers.com/oneplus-2/general/recovery-twrp-3-0-2-hybrid-supports-oos-t3362904
Hello. I wanted to return to stock x720 ROM. Followed that guide;
https://forum.xda-developers.com/le-2/how-to/guide-unlocking-rooting-restoring-to-t3515555
Used files from here;
https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
Now my phone have stock recovery, stock bootloader, still AICP ROM. In bootloader I see blank list. ROM stuck on load. What can I do?
Ooo...kay. List was clean, but did fastboot oem unlock-go and fastboot boot twrp.img ... So, I'll try to flash again AICP temporary.
I wonder if you tell me how to return to stock x720 version...
Finally got it. If sbd is in the same situation; Go to bootloader (power and volume -), turn on "Minimal ADB and Fastboot", type "fastboot flash recovery twrp.img" (image of TWRP should be downloaded and put into "Minimal ADB and Fastboot" installation folder with name as same as the text of command), phone now should show TWRP. Go Advanced -> ADB Sideload, type "adb sideload aicp_zl1_n-12.1-NIGHTLY-20170516.zip" (zip of OS should be downloaded and put into "Minimal ADB and Fastboot" installation folder with name as same as the text of command). It should let you turn on system. If it is, you should send to phone all files to good restore phone again (twrp, kernel, OS).
Dude, THANK YOU SO MUCH. I accidentally wiped my internal storage (because i wasn't paying attention at all) and completely erased everything. You saved me. i was able to flash a rom with your help and now everything's great again. So, THANK YOU!!! :good:
That's why I left what to do Have a nice day.
https://forum.xda-developers.com/showpost.php?p=72553639&postcount=37
I wanted to create a guide which is as simple as rooting a OnePlus 3T. I don’t know if it will work with the OnePlus 3. I’m not responsible for anything. You’re doing it on your own risk, so only do it if you know what you will do, now! It may brick your device.
This is the way it worked for me. I do not guarantee it will work for you!
READ THE WHOLE INSTRUCTIONS FIRST BEFORE YOU DO ANYTHING
What we do:
- Flash TWRP
- Flash an old version of OOS
- Enable dm verity
- Relock the bootloader
- Flash the latest stock rom
What you need:
- Computer (Windows 7 or 10)
- USB Cable
- about 1 hour of your lifetime
YOU WILL LOOSE ALL YOUR DATA - ALSO THE INTERNAL STORAGE WILL BE DELETED (pics, music and all the stuff stored there)
Download to your computer:
Latest TWRP for OnePlus 3T
https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
and
latest OOS from OnePlus for your 3T
http://downloads.oneplus.net/
THE USB DRIVERS MUST BE INSTALLED ON YOUR COMPUTER
Download to the phone:
4.0.2 OOS Stock rom (post #2)
https://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308
Flash TWRP:
1. Start your phone in fastboot mode (don’t connect to your PC yet!)
2. Open CMD as Admin (Windows start-menu - type “cmd”, right-click, run as administrator)
3. connect your phone
4. rename the file to “recovery” (don’t type “recovery.img” manually, only “recovery”)
5. type command “fastboot devices” -> device will be listed
6. command “fastboot flash recovery C:\Users\...\recovery.img” (the path where it’s stored)
7. done -> boot to recovery
8. disconnect your phone - leave CMD open
Flash OOS 4.0.2
1. Go into TWRP
2. wipe “System, Data, Cache, Dalvik”
3. Install OOS 4.0.2
4. reboot into fastboot
Enable dm-verity:
1. connect your 3T when it’s back in fastboot
2. type in CMD “enable dm-verity”
3. done - keep CMD open and the phone connected
Relock the bootloader:
1. type in CMD “fastboot OEM lock”
2. Warning message on your phone will pop up -> choose “yes” on your phone by using the volume buttons to lock the bootloader (keep CMD open)
Update to the newest OOS via “sideload”:
1. VOL down to boot into recovery
2. choose “Install from ADB”
3. “Upgrade Android from USB?” -> “Ok”
4. rename the OOS zip file to "update"
5. type in CMD “adb sideload C:\Users\...update.zip”
6. done
7. reboot the device - it will take about 10 minutes, DO NOT INTERRUPT THE PROCESS
Finish
Take your time! Don't do it if you're in a rush.
Please give me feedback if it worked for you or if I have to change something.
enable dm-verity doesnt work
"enable is not recognised..."
chowchillacharlie said:
enable dm-verity doesnt work
"enable is not recognised..."
Click to expand...
Click to collapse
Did you check if the device is listed in fastboot?
You can also try the command "disable" and then "enable"
Sometimes you may need to do it first, even if it's disabled
Thanks for your threat. I tried this but had to do a couple things differently.
I think enabling/disabling dm-verity works only with old firmware.
What I used:
* 4.0.2 firmware from this threat https://forum.xda-developers.com/oneplus-3t/how-to/firmware-modem-collection-flashable-zips-t3565535
* latest oneplus recovery and rom https://downloads.oneplus.com/
* the recovery can be downloaded from a link on the bottom of the rom download site.
I started with twrp and a custom rom.
You need usb debuging enabled and adb and fastboot installed
What I did:
* I did a Nandroid backup, and copied the sdcards content to my computer, because the following completely wiped my phone
"adb pull /sdcard /path/to/my/drive/"
* flash 4.0.2 firmware, with trp
enter adb sideload mode in twrp and
"adb sideload firmware.zip"
* fastboot flash oneplus recovery
"fastboot flash recovery recovery.img"
* using onplus recovery and sideloading installed latest oneplus rom
enter adb sideload and
"adb sideload oneplusrom.zip"
* did a factory reset in oneplus recovery and cheked if my phone would boot
* entered fastboot mode
"fastboot oem disable_dm_verity", then "fastboot oem enable_dm_verity"
"fastboot oem lock"
after that my phone got wiped again, and the next boot took a long time
Then the phone was completely stock
Wanted to post to say thanks to roor7 and WhataHulk - had a rooted 3T I wanted to sell following an upgrade (best price requires the phone to have no sign of root!), and this was the only method that worked for me to enable dm-verity.
As a quick note, I followed roor7's guide, but got the same error message as chowchillacharlie. After sme playing about I found the simplest soultion was using the CMD line provided towards the end of WhataHulk's guide, i.e. - "fastboot oem disable_dm_verity", then "fastboot oem enable_dm_verity". For me, roor7's guide swapping the type "enable dm-verity" in CMD with "fastboot oem enable_dm_verity" worked a treat.
Sorry if that is all incredibly obvious to most people!
Thanks again gents.
I've seen alot of guys here who are encountering problems while flashing custom roms.Make sure you have backed up all your data before starting the procedure.
This method is also valid for those who are coming straight from the Stock rom.
Prerequisites :
•Unlocked Bootloader
•ADB and Fastboot Files
•Desired Custom Rom
•Copypartitions file
•TWRP image
•TWRP installer - Download and move it to Internal Storage
•A USB C-Type Cable and some Brain.
•Magisk [Optional]
•Fresh Gapps ARM64 (I'd recommend Mini)
Installation :
#1. Back up all your data or simply move everything to your PC.
#2.Boot your phone into Bootloader Mode [Power button + Volume Down] or Enable Debugging mode,And run this Command ''adb devices''- To ensure that the device is connected,then ''adb reboot bootloader''.
#3.Move the ''twrp.img'' file to the ''adb" folder of your PC.
#4.You'll see 3-4 files along with twrp.img file you just copied there[adb folder], Simply Click Shift+Right Click anywhere in that blank space,then click on Open Powershell Window here or Open Command Prompt Window.
#5.Attach your phone to the PC,you'll hear a sound,yet run this Command "fastboot devices" to ensure that the device is connected properly [Device ID will appear]
#6.Now you're supposed to temporarily boot TWRP in order to permanently flash the Custom Recovery.So to do this ,Run this Command while the device is connected to the PC in fastboot mode > "fastboot boot twrp.img '' [After Typing fastboot boot, simply drag twrp.img file into the PowerShell or Command prompt window to Complete the Command ''fastboot boot twrp.img'',it may look like ''fastboot boot C://adb/twrp.img''.
#7.After Booting Temporarily into TWRP,Swipe for Modifications,Locate and install TWRPinstaller.zip,this will permanently install TWRP as your Recovery.
#8.After installing TWRP,Return to the home screen of TWRP and Reboot into Recovery from there.[Permanently Flashing incase you don't need hassles with computer flashing]
#9.After booting again into TWRP,Click on Wipe>Format User Data>Type Yes>Go to Home screen Reboot into Recovery.
#10.After booting again into TWRP,Click on Wipe>Advanced Wipe> [Tick on Dalvik/Art Cache,Cache, System,Data] > Wipe it off.
#11.Go back to the Home Screen of the TWRP,Reboot into Recovery.
#12.Now Push copypartitions.zip file to your phone from your PC,then flash it via TWRP,then again,Reboot your phone to Recovery.
#13.Now Push the Desired Custom rom you would want to install on your G7 river from the PC> Install it> After the Installation Finishes,Reboot your phone to the Bootloader mode from TWRP [As the the Recovery will be replaced by the Custom Rom's Recovery,hence, TWRP will be removed].
#14.Once in the Fastboot Mode,run the command in PowerShell or CMD, "fastboot boot twrp.img"
#15.After booting again into TWRP,Push Gapps File into your phone and install it Accordingly,After the installation Finishes,Wipe Dalvik Cache,Come back to the Home screen of TWRP,Reboot > Power Off in TWRP,then manually Power it On,After powering it On,the rom may prompt you for a factory reset,that's it. You've successfully installed Custom Rom along with the Google Apps without Messing with the partitions.
#16.Now, Finally Boot your phone into Bootloader mode, run the command "fastboot boot twrp.img" and install TWRPinstaller.zip,this will again permanently install TWRP as your recovery.
#17.You may root your phone by installing Magisk or Flash any other zip without the need of temporarily booting TWRP,as you've flashed it permanently. Simply Reboot to Bootloader then Boot into Recovery.
Errors and Fixes:
#1.If you encounter any problem while flashing zips from the internal storage, simply move all the zips to the MicroSD or USB OTG and flash it from there.
#2.If your TWRP isn't reading the internal storage properly or isn't responding well,simply reboot your phone again to the Bootloader mode,again boot twrp.img and try again,this should do the thing.
#1.copy-partitions-AB.zip
#2.twrp-3.3.1-0-river.img
#3.twrp-installer-3.3.1-2-river.zip
Find these files on the internet or XDA forums as I can't Post links yet,Happy to help!
Simplify and Clarify
Thanks @deathcruizer for the your procedure. It rescued me in a jam. The critical items for me that you noted were that the Custom ROM replaced TWRP with its own Recovery and that a Factory Reset was required.
I wanted to simplify and clarify your key points for those already setup with fastboot and familiar with TWRP. Generic filenames mentioned should be replaced by the actual full name; eg, twrp-3.3.1-2-river.img.
1. Backup partitions in TWRP just in case for a restore. And Data will be needed later.
2. Move all zip files needed (ROM, Gapps, copy-partitions, twrp-installer, Magisk, etc.) to internal storage or USB OTG. Move twrp.img on PC to a convenient location for fastboot.
3. Enter fastboot boot twrp.img to temporarily use TWRP.
4. Flash copy-partitions.zip, reboot, and flash custom ROM.zip.
5. In TWRP, choose Reboot to the Bootloader mode, not Recovery. TWRP has been removed and replaced by the custom ROM's Recovery.
6. Enter fastboot boot twrp.img to temporarily use TWRP again. Install Gapps.zip, wipe caches, and then Power Off.
7. Manually Power On to the Custom ROM. Accept its Factory Data Reset option.
8. Boot into Bootloader Mode, enter fastboot boot twrp.img again, and use this temporary TWRP to install TWRP permanently using twrp-installer.zip.
9. Reboot and begin a minimum setup of the Custom ROM.
10. Reboot to TWRP and restore the Data partition.
11. G7 River is back with its apps, desktop layout, settings, icons, etc., on the new Custom ROM.
Hey guys, your tutorial is great and very informative. I do however have a recurring problem with installing any custom rom. No matter which one I choose, I have no LTE and occasionally the phone randomly reboot if I unplug my phone. Has anyone encountered this? I've followed all applicable steps for properly installing a custom rom, and am pretty use to it as I've always flashed roms on as many phones as I could. Any help or guidance would be appreciated. Thanks in advance
What model phone, to be clear?
Moto g7, xt19621. I tried to flash lineage again today to no avail. Twrp then copy. Zip. Reboot. Lineage. Wipe dalvic. Reboot. Previously tried wiping system and starting from scratch. Copy. Zip and start from scratch. Clean flash. Dirty flash. I've been able to get it to work properly maybe 2 or three times since having the phone and trying different roms. Basically always having to revert back to stock after a multitude of attempts. I've never had this much trouble flashing with a phone.
---------- Post added at 12:45 AM ---------- Previous post was at 12:27 AM ----------
Do I need to flash stock to the 9eiginal firmware or something? I tried the stock room from August 2019, and kind 9f same issues. Device kinda bugged out.
If you're going to do a full article, always be sure to check and double check your process before sharing. The A/B slots on this device CAN cause mucho mucho errors if the user is unfamiliar or does not alternate correctly (TWRP can select boot slot, yes, but doesnt always work the right way), they can end up with a bricked device. I am excited to see a full guide be posted but for other people's sake, I recommend maybe clarifying the A/B details. I, personally, have yet to find a good A/B tutorial, and how they work during installs, online but if there is one and someone wants to share the link I'd sure appreciate it! Thanks and goodluck!
---------- Post added at 02:02 AM ---------- Previous post was at 01:49 AM ----------
trentag1988 said:
Moto g7, xt19621. I tried to flash lineage again today to no avail. Twrp then copy. Zip. Reboot. Lineage. Wipe dalvic. Reboot. Previously tried wiping system and starting from scratch. Copy. Zip and start from scratch. Clean flash. Dirty flash. I've been able to get it to work properly maybe 2 or three times since having the phone and trying different roms. Basically always having to revert back to stock after a multitude of attempts. I've never had this much trouble flashing with a phone.
---------- Post added at 12:45 AM ---------- Previous post was at 12:27 AM ----------
Do I need to flash stock to the 9eiginal firmware or something? I tried the stock room from August 2019, and kind 9f same issues. Device kinda bugged out.
Click to expand...
Click to collapse
back up phone if you have third party backup application
(not absolutely necessary BUT, I always remove my security and google account before going into fastboot)
reboot to fastboot or power off phone and boot to fastboot by holding down the volume down+power
"fastboot set_active b"
"fastboot boot (drag your twrp img file from it's location to the command window) so that it reads sort of like "fastboot boot c:\path-to-twrp.img"
1. now install copy-partitions.zip
2. "Format, Advanced", type "yes" then back to TWRP main screen
3. install ROM of your choice (if installing Lineage, skip step 4)
4. install twrp-installer.zip (make sure you're using the zip format, not img)
5. "adb reboot bootloader"
"fastboot set_active a" (because when you installed the ROM, the device installed it to the inactive slot, in this instance that slot would be "a"
ADV: you may get a message indicating you're already on slot a, which is fine. 9 out of 10 times the device changes slot automatically after you reboot
post-ROM-install
6. from TWRP home choose "Advanced, ADB Sideload", check the two boxes and"adb sideload c:\path-to-gapps" (you'll need ARM64 gapps for this device)
7. IF you want magisk, from TWRP home choose "Advanced, ADB Sideload", check the two boxes and "adb sideload c:\path-to-magisk.zip"
8. "adb reboot bootloader"
9. "fastboot -w"
10. For whatever reason, magisk never stays on my device but I just install the apk and install it from the app.
Hope this doesn't annoy anyone and proves helpful.
@clinton I am definitely going to try this particular method. Setting B as active first is the one thing I have not done. I would like to point out that I am about to do fastboot boot twrp.img , however when installing the provided zip, my phone makes a weird noise on every screen tap. Like odd feedback from the speaker. If I use just lineage recovery that installs from the rom, it doesn't do that. Another thing that happens now - every lineage install goes fine until first boot. As soon as I sign on to WiFi and it tries to activate the radio, device just shuts down. Has anyone had this happen to them?
I am still experiencing the same issues. flashed back to original firmware and had no LTE. didn't resolve when flashing a custom rom. Flashed to latest stock rom and everything went through properly (LTE, no random reboot after unplugging), attempted rigmarole for flashing custom rom, same issues. x over signal bar and reboot as soon as I unplug the device. I have basically given up at this point, going to have a go at it again when stock android 10 update happens Thank you, guys, for all the help and tutorials. Big hugs, take care