Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.
treysky54 said:
Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.
Click to expand...
Click to collapse
Why can't you just flash SuperSu or Magisk via twrp?
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.
gwardsc65 said:
Why can't you just flash SuperSu or Magisk via twrp?
Click to expand...
Click to collapse
gwardsc65 said:
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.
Click to expand...
Click to collapse
Sorry mate, not the way it works on this device (3rd gen HDX). Bootloader must be unlocked to obtain root on any custom ROM based on Android 5+. There are no (reasonable) workarounds or exceptions.
treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
Expected symptom when attempting to secure root on a bootloader locked HDX.
Ahhh... so it somehow got locked back and need to redo the procedure?
treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
No need to restore stock. Use MTP in TWRP to transfer (push) a KitKat based custom ROM zip to device, install and then go through bootloader unlock procedure. Suggest using Fire Nexus as the interim ROM as it is self contained with GApps and SuperSU built in.
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
---------- Post added at 03:38 AM ---------- Previous post was at 03:37 AM ----------
treysky54 said:
Ahhh... so it somehow got locked back and need to redo the procedure?
Click to expand...
Click to collapse
That's what the symptoms suggest. What makes you believe the device was properly unlocked sometime in the past?
treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
Can I do it without TWRP????
Related
Dumb question- If I've used CF-Auto-Root to initially root my N10, what's the best way to update to SuperSU 2.35? I haven't installed a custom recovery, so can I use stock recovery to simply flash the 2.35 zip file?
dberthia said:
Dumb question- If I've used CF-Auto-Root to initially root my N10, what's the best way to update to SuperSU 2.35? I haven't installed a custom recovery, so can I use stock recovery to simply flash the 2.35 zip file?
Click to expand...
Click to collapse
I've asked this very question in Chainfires main SuperSU XDA thread. Hopefully we can get some clarity.
I updated my SuperSU today. It requested to update the su binary.
Standard method didn't work, custom recovery option (I forgot I haven't yet installed TWRP) got me an unbootable tablet. The only thing that worked was fastboot mode.
I tried pretty much everything and ultimately I was left with two options:
Re-flash lollipop / factory reset
Install latest TWRP
I tried the latter first and luckily ended up with normally working tablet. I had to re-launch the su binary update procedure, but that really wasn't a problem given that I just made the tablet work again
velis74 said:
I updated my SuperSU today. It requested to update the su binary.
Standard method didn't work, custom recovery option (I forgot I haven't yet installed TWRP) got me an unbootable tablet. The only thing that worked was fastboot mode.
I tried pretty much everything and ultimately I was left with two options:
Re-flash lollipop / factory reset
Install latest TWRP
I tried the latter first and luckily ended up with normally working tablet. I had to re-launch the su binary update procedure, but that really wasn't a problem given that I just made the tablet work again
Click to expand...
Click to collapse
Interesting but I wonder what state your boot.img is in. I downloaded and examined the SuperSU v2.35 update flash file. I did not see anything to indicate that it backs out whatever non-stock boot.img changes were introduced. There was a "clean-up" comment which was intriguing.
As my tablet works well I'll wait for a while to see if I get any definitive response to my post. If not I'll likely use fastboot to re-install the stock boot.img and TWRP (which is already installed on my N10) to flash SuperSU v2.35 file.
Glad to read your tablet is in good shape.
I updated Binary via twrp and get fcs for all Google apps. Tried to clear Cache of everything, also wiped it: nothing changes. Going to reflash lollipop
Hey does anyone know how to do this? I can't find any stock system or recovery images. I'm trying to make my device fully stock again (re-enabling encryption) so I can file a warranty claim. Would booting into fastboot and restoring using the LG Mobile Support Tool (http://www.lg.com/us/support/software-firmware-drivers) be all I need to restore back? Thanks!
darkghost568 said:
Hey does anyone know how to do this? I can't find any stock system or recovery images. I'm trying to make my device fully stock again (re-enabling encryption) so I can file a warranty claim. Would booting into fastboot and restoring using the LG Mobile Support Tool (http://www.lg.com/us/support/software-firmware-drivers) be all I need to restore back? Thanks!
Click to expand...
Click to collapse
The only way known so far to return to stock is to flash these IMG files in TWRP. As for re-enabling encryption that's something I have no idea of but these images system and boot should bring you back to stock. https://build.nethunter.com/misc/us996/v10d/?C=N&O=D by jcadduono
OneDon said:
The only way known so far to return to stock is to flash these IMG files in TWRP. As for re-enabling encryption that's something I have no idea of but these images system and boot should bring you back to stock. https://build.nethunter.com/misc/us996/v10d/?C=N&O=D by jcadduono
Click to expand...
Click to collapse
Thanks!
deleted
Did this work? I have a V20 US996 (unlocked, not US Cellular) that I'd like to return to stock, after something has corrupted somewhere, making it hard for me to flash kernels, su binaries, and the like. Isn't LGUP preferred at this point? Would flashing from TWRP bring it back to stock? I'd think that the custom recovery would still be intact when you're done. I can't seem to get LGUP to even start on my PC, let alone get it to recognize my phone.
DrPhant0m said:
Did this work? I have a V20 US996 (unlocked, not US Cellular) that I'd like to return to stock, after something has corrupted somewhere, making it hard for me to flash kernels, su binaries, and the like. Isn't LGUP preferred at this point? Would flashing from TWRP bring it back to stock? I'd think that the custom recovery would still be intact when you're done. I can't seem to get LGUP to even start on my PC, let alone get it to recognize my phone.
Click to expand...
Click to collapse
Going back to complete stock I would suggest using LG's tools. After flashing back to stock you can re-lock the bootloader which should clear the boot-up warning.
If you want to try and just recover from bad flashing, and you have access to TWRP, you can try to flash the zip from here: https://forum.xda-developers.com/v20/how-to/us996unlocked-twrp-flashable-10f-t3544573
That should bring you back to 100% stock, minus recovery, and then automatically install SuperSU. I'll most likely be adding a zip without the automatic installation of SuperSU so that users can have a choice on what SU they want to use.
McNutnut said:
Going back to complete stock I would suggest using LG's tools. After flashing back to stock you can re-lock the bootloader which should clear the boot-up warning.
If you want to try and just recover from bad flashing, and you have access to TWRP, you can try to flash the zip from here: https://forum.xda-developers.com/v20/how-to/us996unlocked-twrp-flashable-10f-t3544573
That should bring you back to 100% stock, minus recovery, and then automatically install SuperSU. I'll most likely be adding a zip without the automatic installation of SuperSU so that users can have a choice on what SU they want to use.
Click to expand...
Click to collapse
I'm actually trying to get MagiskSU working, so that I can be SafetyNet compliant for snapchat, androidpay, and concur (business expense app). I'd prefer to stay on the WETA rom for the extra tweaks. Lots of users post pics of MagiskSU working in WETA, but it seems they're all on other carriers with carrier-specific models. I'd think that the US996 would be EASIER to work with. Any suggestion? Thanks for the reply!
DrPhant0m said:
I'm actually trying to get MagiskSU working, so that I can be SafetyNet compliant for snapchat, androidpay, and concur (business expense app). I'd prefer to stay on the WETA rom for the extra tweaks. Lots of users post pics of MagiskSU working in WETA, but it seems they're all on other carriers with carrier-specific models. I'd think that the US996 would be EASIER to work with. Any suggestion? Thanks for the reply!
Click to expand...
Click to collapse
MagiskSU is actually the reason I want to upload the zip(s) without the automatic SuperSU. (Allow users to pick between SuperSU & MagiskSU). I started using Magisk so that I can bypass SafetyNet. Unfortunately I've only used the stock ROM so I don't have many tips for getting MagiskSU working on WETA. I assume it's pre-rooted with SuperSU so I would say performing a full un-root within the SuperSU app and then flashing the Magisk zip in recovery could get you up and running with Magisk. It's also worth nothing that I've only been successful with v11.6 of Magisk on the stock ROM. v12.0 causes an unstable system.
McNutnut said:
MagiskSU is actually the reason I want to upload the zip(s) without the automatic SuperSU. (Allow users to pick between SuperSU & MagiskSU). I started using Magisk so that I can bypass SafetyNet. Unfortunately I've only used the stock ROM so I don't have many tips for getting MagiskSU working on WETA. I assume it's pre-rooted with SuperSU so I would say performing a full un-root within the SuperSU app and then flashing the Magisk zip in recovery could get you up and running with Magisk. It's also worth nothing that I've only been successful with v11.6 of Magisk on the stock ROM. v12.0 causes an unstable system.
Click to expand...
Click to collapse
There is a v13 of Magisk that's out if you go to their git.
WETA has an AROMA installer, and you can choose to NOT install superSU. However, when I do that, the phone won't boot. It just sits there for 20min+ (flashing the rom with supersu takes about 5min to boot). The same non-booting issue used to happen when trying to update the binary, but I flashed something that fixed that. (I flashed so much stuff and something worked... I wish I knew which it was). However, SuperSU is like burned into my ramdisk or something, and it can't come out. When I tried to do the full unroot in SuperSU, it either fails, or the phone won't boot. But, there are options along that way that I don't know what to pick. Can you suggest what to do? Here... let me elaborate:
SuperSu v2.82 > "Full Unroot" > Continue (warning that some kernels auto-root. I'm on konverged... not sure if that's good or bad for this)
Attempt to Restore boot image? > YES
Attempt to restore stock recovery image? YES or NO?
.......YES "Uninstallation failed."
.......NO "Uninstallation failed."
Attempt to Restore boot image? > NO
Phone reboots within seconds... then sits and sits until I pull the battery.
....I then have to dirty-flash my ROM with superSU to get it to boot to the OS.
Helpful others with more knowledge than I have suggested that my problems are due to the latest version of TWRP corrupting ramdisk because of bad compression. Most of this is over my head when it comes to the actual development of recoveries, kernels, etc.
DrPhant0m said:
There is a v13 of Magisk that's out if you go to their git.
WETA has an AROMA installer, and you can choose to NOT install superSU. However, when I do that, the phone won't boot. It just sits there for 20min+ (flashing the rom with supersu takes about 5min to boot). The same non-booting issue used to happen when trying to update the binary, but I flashed something that fixed that. (I flashed so much stuff and something worked... I wish I knew which it was). However, SuperSU is like burned into my ramdisk or something, and it can't come out. When I tried to do the full unroot in SuperSU, it either fails, or the phone won't boot. But, there are options along that way that I don't know what to pick. Can you suggest what to do? Here... let me elaborate:
SuperSu v2.82 > "Full Unroot" > Continue (warning that some kernels auto-root. I'm on konverged... not sure if that's good or bad for this)
Attempt to Restore boot image? > YES
Attempt to restore stock recovery image? YES or NO?
.......YES "Uninstallation failed."
.......NO "Uninstallation failed."
Attempt to Restore boot image? > NO
Phone reboots within seconds... then sits and sits until I pull the battery.
....I then have to dirty-flash my ROM with superSU to get it to boot to the OS.
Helpful others with more knowledge than I have suggested that my problems are due to the latest version of TWRP corrupting ramdisk because of bad compression. Most of this is over my head when it comes to the actual development of recoveries, kernels, etc.
Click to expand...
Click to collapse
I doubt I'll try v13 unless there's a real reason for it (haven't looked at the changes yet). Since I'm stable on v11.6 I'm not too inclined to attempt to upgrade again (since v12 kept crashing the SystemUI).
Have you tried choosing not to install SuperSU in WETA and then flashing the Magisk zip right after completing the WETA install (before attempting to boot system)?
Another idea is to flash a stock boot image (since the one in WETA is modified slightly), flash WETA with kernel and SuperSU options turned off, and then flash Magisk.
McNutnut said:
I doubt I'll try v13 unless there's a real reason for it (haven't looked at the changes yet). Since I'm stable on v11.6 I'm not too inclined to attempt to upgrade again (since v12 kept crashing the SystemUI).
Have you tried choosing not to install SuperSU in WETA and then flashing the Magisk zip right after completing the WETA install (before attempting to boot system)?
Another idea is to flash a stock boot image (since the one in WETA is modified slightly), flash WETA with kernel and SuperSU options turned off, and then flash Magisk.
Click to expand...
Click to collapse
no luck. Unless I have the wrong boot.img (I was given one earlier in trying to troubleshoot).
I flashed a boot.img that was supposedly for my phone, then flashed WETA with no kernel, no SU. Then I flashed Magisk. It flashed... but the phone wouldn't boot.
I restored the boot partition from my initial TWRP backup and tried flashing WETA again... followed by Magisk. This time, Magisk failed to run because it said SuperSU was already patched (I made the TWRP backup after installing SuperSU) and it couldn't flash.
I tried flashing WETA with the kernel, but no SU... and then immediately following it with flashing Magisk, and it wouldn't boot.
I should probably start a new thread, or post in the WETA thread. I got a little off-topic here. I initially just wanted to see if there was any advice on returning to stock on my US996.
Thanks for the suggestions
DrPhant0m said:
no luck. Unless I have the wrong boot.img (I was given one earlier in trying to troubleshoot).
I flashed a boot.img that was supposedly for my phone, then flashed WETA with no kernel, no SU. Then I flashed Magisk. It flashed... but the phone wouldn't boot.
I restored the boot partition from my initial TWRP backup and tried flashing WETA again... followed by Magisk. This time, Magisk failed to run because it said SuperSU was already patched (I made the TWRP backup after installing SuperSU) and it couldn't flash.
I tried flashing WETA with the kernel, but no SU... and then immediately following it with flashing Magisk, and it wouldn't boot.
I should probably start a new thread, or post in the WETA thread. I got a little off-topic here. I initially just wanted to see if there was any advice on returning to stock on my US996.
Thanks for the suggestions
Click to expand...
Click to collapse
You're welcome! Sorry it didn't work. I do know it takes a few minutes for it to boot up the first time, but I imagine you waited pretty long. I have heard of phones taking 10-15 minutes to boot up after flashing.
I did add US99610h stock firmware to my thread at https://forum.xda-developers.com/v20/how-to/us996unlocked-twrp-flashable-10f-t3544573 if you want to return to the newest stock firmware of the US996.
I hope you are able to get Magisk installed as it's nice to get past SafetyNet. Good luck!
Good morning, I wanted to know if I can upgrade to Android 7.1.2 beta with root and custom recovery installed. Do I have to remove them before upgrading or the upgrade will remove them automatically ? Will my device even boot if I update with root and custom recovery?
Thanks
Nope. Cant with custom recovery..
SkyGO said:
Good morning, I wanted to know if I can upgrade to Android 7.1.2 beta with root and custom recovery installed. Do I have to remove them before upgrading or the upgrade will remove them automatically ? Will my device even boot if I update with root and custom recovery?
Thanks
Click to expand...
Click to collapse
Your phone will boot loop if you don't go back to stock recovery first. I tried just to see what would happen and that's what happened. People who tried to flash it with Flashify reported no success.
SkyGO said:
Good morning, I wanted to know if I can upgrade to Android 7.1.2 beta with root and custom recovery installed. Do I have to remove them before upgrading or the upgrade will remove them automatically ? Will my device even boot if I update with root and custom recovery. Thanks
Click to expand...
Click to collapse
Stock ROM? Important information you omitted. From a guy who always runs the latest stock ROM rooted and custom recovery here's how you do it: You do not have to remove them first, and although they (SU & kernel) will be overwritten with the new boot.img, it is very easy and straightforward. You need the TWRP flashable (beta) OTA zip file, in the OP here. Put the latest SU and your custom kernel on the device root, or wherever. (should already be there) and then reboot to TWRP recovery. Select "Install" and then select the OTA you downloaded above, and tap "Add more zips". Next you want to add the latest SU zip (2.79 SR3) and last add your kernel. Mine is EX. Once you have queued all 3 zips, in less than a minute you will be back up and running 7.1.2 , rooted and with kernel. Even if you flash each file individually you will still be ok. (OTA, SU, Kernel). See the same thread further down... Credit for the TWRP flashable OTA goes to @Displax.
I have a Moto G4 Athene (not Plus, and not Play).
I did the following:
unlocked bootloader
flashed TeamWin recovery
installed SuperSu 2.79 SR3 from TeamWin install
The phone no longer boots. Just a black screen. Flashing notification light if put on USB.
I can still get into the bootloader, and from there into TeamWin recovery, but I'm not having any luck beyond that.
Sadly, I didn't create a backup.
I tried installing LineageOS 14.1, pushing with ADB in recovery, and then installing with TeamWin. Even though I can add the file to the phone and I can run the install, a reboot returns a black screen.
Any advice? I'm afraid this isn't looking too good.
By the way, you can just work with twrp after installing that... stock recovery (fastboot adb) doesn't belong anymore. At first I would suggest that you post the details which are shown in your bootloader.
Furthermore I would recommend just to flash stock rom and testing that case.
Sent from my Moto G (4) using XDA Free mobile app
Ferwerda said:
I have a Moto G4 Athene (not Plus, and not Play).
I did the following:
unlocked bootloader
flashed TeamWin recovery
installed SuperSu 2.79 SR3 from TeamWin install
The phone no longer boots. Just a black screen. Flashing notification light if put on USB.
I can still get into the bootloader, and from there into TeamWin recovery, but I'm not having any luck beyond that.
Sadly, I didn't create a backup.
I tried installing LineageOS 14.1, pushing with ADB in recovery, and then installing with TeamWin. Even though I can add the file to the phone and I can run the install, a reboot returns a black screen.
Any advice? I'm afraid this isn't looking too good.
Click to expand...
Click to collapse
First of all, if you read their corresponding threads, you need to do the following when rooting:
- Unlock bootloader/flash TWRP (you did)
- Flash a custom kernel (Vegito or ElementalX)
- And then wipe ART/Dalvik Cache
Second, for LineageOS- you cannot dirty flash custom ROMs, EVER EVER EVER! By this I mean you have to wipe system/data/cache/dalvik etc.- you can ignore Internal Storage and the SDCard/OTG.
You may (should) have to flash the Moto G4 Nougat radio that's floating around XDA somewhere. LOS worked fine for me without doing that, but I know other ROMs require it.
Finally, as a quick heads up, all Moto G4 Plus ROMs work fine with the G4, including any stock ROMs/backups.
Edit: I heavily suggest Magisk or phh SU over SuperSU- Magisk allows you to use SnapChat and Pokemon Go, and phh's is open source.
Thanks for the responses.
I was able to restore the phone with a stock rom I found on these boards. After that, I received two OTA, one to 6.0.1 and then the current to 7.0.0.
I have the same problem than you... Can you send me the link that you use to fix it?
Ferwerda said:
Thanks for the responses.
I was able to restore the phone with a stock rom I found on these boards. After that, I received two OTA, one to 6.0.1 and then the current to 7.0.0.
Click to expand...
Click to collapse
raulcalaca said:
I have the same problem than you... Can you send me the link that you use to fix it?
Click to expand...
Click to collapse
Just flash ElementalX 1.04 kernel (after flashing SuperSu or Superuser or Magisk) when trying to root STOCK Nougat 7.0 as it's designed to thwart any root attempt.
Ferwerda said:
Thanks for the responses.
I was able to restore the phone with a stock rom I found on these boards. After that, I received two OTA, one to 6.0.1 and then the current to 7.0.0.
Click to expand...
Click to collapse
can you please give the step by step guide you followed to recover your phone!!!
I'm on Android 10. I unlocked the bootloader.. easy.. I downloaded the corresponding file for my device, software channel, version. Ran the boot img through magisk manager. So I have the patched boot img. Before I go further with trying to flash it through fastboot, I was wondering would this successfully root my device? I'm hesitant because I haven't came across anyone discussing there success in doing this with Android 10. I really don't want to proceed until I know I'm ok to go ahead. Thoughts?
Install Twrp, flash Magisk latest zip through twrp, done
HueyT said:
Install Twrp, flash Magisk latest zip through twrp, done
Click to expand...
Click to collapse
Sorry to butt in but that did not work for me. Rooting with magisk removed my installed twrp. Could that be a bug in android 10 or latest magisk?
fastboot flash recovery twrp.img should permanently install twrp recovery into op7t and Magisk flash should not replace it. If you flash oos10 after that then stock recovery will replace twrp recovery
HueyT said:
fastboot flash recovery twrp.img should permanently install twrp recovery into op7t and Magisk flash should not replace it. If you flash oos10 after that then stock recovery will replace twrp recovery
Click to expand...
Click to collapse
I was busy with other things and only just came back to this topic. I agree with you, HueyT, Magisk rooting
(which I do according to the Magisk directions which say to patch the boot.img and then flash it)
should not remove the permanent twrp installation on my phone. But it does
remove it on my phone! I've tried it repeatedly.
What I end up with is a rooted Moto G7 running android 10 and when I :
—power off completely
—volume down + power takes me to the stock recovery (not twrp)
—in that stock recovery if I go to the 'recovery' option I get the open android with red exclamation mark. Happens every time.
—long power hold then reboots phone to rooted android 10.
What I have not tried yet is to permanently install twrp again and then, in twrp install Magisk 23 zip. Maybe that will allow me to keep twrp installed.
Do you think so?
It is just frustrating because this is my main phone and I can't afford to mess it up.
Any other suggestions on how to keep twrp installed on the Magisk rooted phone greatly appreciated.
Thanks for replying.
Definitely
HueyT said:
Definitely
Click to expand...
Click to collapse
Which I interpret as you agreeing I should try installing the Magisk zip from within twrp.
(That is not what the Magisk instructions say to do).
I will try that later today when I get a chance.
I have also not flashed copypartitions.zip. Should I?
Definitely
HueyT said:
Definitely
Click to expand...
Click to collapse
A man of few words...
Yep
maybeme2 said:
Which I interpret as you agreeing I should try installing the Magisk zip from within twrp.
(That is not what the Magisk instructions say to do).
I will try that later today when I get a chance.
I have also not flashed copypartitions.zip. Should I?
Click to expand...
Click to collapse
That worked.
Rooting by installing Magisk.zip from within TWRP allowed me to both root and retain the TWRP installation.
Thank you HueyT.
NP
It's been two years but I did try injecting Magisk from within TWRP. I've also downloaded "factory" images and rooted those, them installed them. If I remember right, I did the injection method with this G7. It's the best way IMHO because the installed image is tailored your your device.
Over the last two years, the Pie around here has been fantastic.
shadow460 said:
Over the last two years, the Pie around here has been fantastic.
Click to expand...
Click to collapse
You can say that again. I've had several system crashes with 10, something I've never had with pie. Even after clearing cache, updating all apps, etc. So has my wife on her own unrooted G7 which just accepted Moto's own ota update to 10.
I do have a TWRP nandroid backup that I did just before flashing 10 and I've often considered going back to pie. But I worry about 'something' else going wrong like it did when moving to 10. It's my main phone and I can't afford to go through all I went through moving to a rooted 10. Wish I hadn't bothered.