I've spent the past few days trying to install the new Nougat update on my phone, and I finally managed to do it. I heard Magisk works for Nougat so I decided to use it as my root so i could back up my partitions and whatnot for the next update. I download the Magisk installer using the app, use fastboot to boot into TWRP, and flash the installer. All seemingly goes well, but when I reboot, nothing happens. I can access bootloader, I can access the stock recovery that's still loaded, but it will not start up, and any attempt to start it while the phone is plugged in leaves it in a black screen with the LED next to the fingerprint sensor consistently flashing. I'm no expert, but this doesn't seem good. Is it bricked? Is there an easy fix? So far I've tried using the recovery to wipe the cache and used TWRP to do a full factory reset, neither of which did anything. My Moto G4 Plus is an XT1644, and my model number was mpj24.139-64, which I'd assume means it is now npj24.139-64, but I have no way to check.
I feel like my best bet here is for someone else to extract their system, logo, boot, and all those partitions and I can just flash those in, but I honestly have no idea. This is my only phone by the way, so help would be muchly appreciated.
You need a custom Kernel first thing after re-flashing the stock, recommend ElementalX. Only after that you can root (I prefer the latest beta SuperSU, in systemless mode).
The stock Nougat is locked up pretty good.
Solved
No worries, managed to safely flash the stock rom I had for the previous version and re-update. Seems to work fine now.
Related
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 am no noobie when it comes to android rooting since I root and flash all of my android devices. But the axon 7 is a really tough son of a b*tch.
I got it brand new. Unlocked the bootloader then proceeded to update to marshmallow just so I can get nougat on my device. Then I installed TWRP so I can flash supersu, xposed and an audio mod zip. I believe this audio mod is what killed my devices since it was not booting into the os. Just stuck at the flashy axon booting screen. I booted into TWRP, deleted data, system and system storage and installed the nougat 2,6gb "update.zip" file. Since then the os is not booting at all, its just stuck at the booting screen, the warning because of the unlocked bootloader. And also, now, stock recovery is installed.
I have an idea how to fix this I am rather cautious so thats why Im asking the experts here first
EDIT: I have the 2017G Version
I have an A2017U, but if you can get your hands on an official Marshmallow zip, then that should hopefully let you boot. From there you can OTA update back to Nougat, then you just need to figure out how to install TWRP again.
Another recovery method is to flash EDL files with MiFlash while your phone is booted into EDL mode.
As for audio mods, I just use Arise, it's very comprehensive and has never bricked my phone.
I have an idea why you can't boot after flashing the Nougat zip: you triggered dm-verity. You must also flash a root zip that patches out the dm-verity. Or you can use @jcadduono's "no verity opt encrypt" zip as an alternative if you don't want to root. Your system and cache partitions should be formatted as ext4, and data should be F2FS. I recommend a full wipe of all partitions except the MicroSD.
GriechischerYoghurt said:
I am no noobie when it comes to android rooting since I root and flash all of my android devices. But the axon 7 is a really tough son of a b*tch.
I got it brand new. Unlocked the bootloader then proceeded to update to marshmallow just so I can get nougat on my device. Then I installed TWRP so I can flash supersu, xposed and an audio mod zip. I believe this audio mod is what killed my devices since it was not booting into the os. Just stuck at the flashy axon booting screen. I booted into TWRP, deleted data, system and system storage and installed the nougat 2,6gb "update.zip" file. Since then the os is not booting at all, its just stuck at the booting screen, the warning because of the unlocked bootloader. And also, now, stock recovery is installed.
I have an idea how to fix this I am rather cautious so thats why Im asking the experts here first
EDIT: I have the 2017G Version
Click to expand...
Click to collapse
If you still have TWRP, download Raystef66's B09 TWRP flashable Stocksystem and Bootstack, plus Magisk 15.2. Flash everything then wipe data.
What broke your device was probably Xposed.
Also, which audio mod are you talking about? Ainur, V4Android, V4ARISE, AK4490 patch, maybe some other?
Thanks for the help! i Managed to flash TWRP in EDL mode (black screen). Then I proceeded to flash nougat B9. I was up all night reading about it and searching tutorials how to flash stock from TWRP. I installed Bootstack and System, supersu 2.79 and xposed. First boot did not work but that was actually in the guide so I had to flash system and root again. My data partition is ext4 and everything works good now. I hope it wont make any problems.
The audio mod was "divine 10" or something. I will try the ones you have mentioned.
Thanks for all the help
GriechischerYoghurt said:
Thanks for the help! i Managed to flash TWRP in EDL mode (black screen). Then I proceeded to flash nougat B9. I was up all night reading about it and searching tutorials how to flash stock from TWRP. I installed Bootstack and System, supersu 2.79 and xposed. First boot did not work but that was actually in the guide so I had to flash system and root again. My data partition is ext4 and everything works good now. I hope it wont make any problems.
The audio mod was "divine 10" or something. I will try the ones you have mentioned.
Thanks for all the help
Click to expand...
Click to collapse
Xposed usually needs a 2 or 3 minute first boot for some reason, just sayin
Feel free to scold me, I'm not too upset but would like to fix the phone if it is possible.
Background - Phone is a Moto G4 16gb, XT1625, running android 7.0 nougat. Phone resets a lot so before replacing it I thought I would try rooting and loading a different ROM to see if it helped. I followed THIS guide:
https://theunlockr.com/root-motorola-moto-g4-moto-g4-plus/
I successfully unlocked and flashed TWRP recovery. I then tried to flash supersu v2.82 as a zip through TWRP, and upon completion the phone no longer boots up.
I can access the bootloader and and access TWRP recovery, but otherwise wiping data/factory reset or re-flashing supersu does nothing. I also tried flashing supersu as a systemless root install. I just get a black screen and a flashing white led at the bottom when charging/trying to power on. I only after the fact happened to read something about an elementalx kernel for nougat so I'm thinking maybe this was the problem.
I this a hard brick or a soft brick or just in an unbootable state? Is there a way to recover? Thanks.
Update, after playing around with it all morning I was able to get it back to booting by first flashing the el;ementalx kernel, then downloading and flashing the latest beta release of SuperSU, and then wiping dalvik cache. Not sure exactly which step cured it but in case anyone searches and finds this thread.
dskater411 said:
Update, after playing around with it all morning I was able to get it back to booting by first flashing the el;ementalx kernel, then downloading and flashing the latest beta release of SuperSU, and then wiping dalvik cache. Not sure exactly which step cured it but in case anyone searches and finds this thread.
Click to expand...
Click to collapse
Glad to hear you got your device fixed. For future reference, it's likely the ElementalX kernel that got you out - with stock Nougat on our devices, you can't root the stock Motorola kernel. You'll soft brick your device otherwise.
The problem with those guides is that they often don't mention that step - whilst the procedure may work for our devices with Marshmallow and Oreo, it just won't work for Nougat. Also, that article is over 2 years old, before we got Nougat onto our devices. If you wanted to flash a custom ROM, root is not needed, you just need an unlocked bootloader and TWRP.
As an aside, SuperSU is obselete, and likely abandoned by its developer. You may wish to flash magisk as your root solution, which would necessitate uninstalling SuperSU, reflashing the stock Motorola kernel and then ElementalX, then magisk.
After a painful rooting process, I finally achieved root with Magisk 19.1 and unlocked bootloader. I decided to load Super V20 ROM this morning but it has never finished the boot process. It's sticking on the Verizon boot animation. As far as the stock phone, I had version VS99510B and Android 7.0, running TWRP 3.2.1-0. When I went through the options in the Aroma loader for Super ROM, I don't think I chose anything crazy. I selected Magisk & MK2000 kernel (though, that didn't have any effect on the static screen; I was told it would).
After the first load attempt, I went back into TWRP, triple-wiped everything and reflashed again. Same effect. It just won't move past the Verizon boot animation. What could be the issue? Is there anything I can fix here or do I need to reload all the stock software? If that is the case, do I need to go back to 10B or would a newer version work better? I do intend to load a custom ROM at some point but I just want to get this phone functioning again.
Right now, I do have access to recovery (TWRP 3.2.1-0) so all is not lost. Got any help?
Thanks all.
LG V20 VS995, attempting Super V20 4.1 (8.2.18), Magisk 19.1, TWRP 3.2.1-0
Hi! I wanted to switch from Pixel Experience back to stock, I flashed V10.0.11.0 using the official fastboot image (I used flash_all.bat). However, when I try to install the August update using OTA, it always fails for no reason. I had TWRP and Magisk installed with Pixel Experience, but reflashing everything should have deleted those. Also, I didn't flash Magisk or TWRP. I didn't even boot temporary TWRP - everything should be completely stock, but the OTA still fails. What am I doing wrong?
Edit: Curiously, Google Play shows that my device is not certified. How the hell is my phone still not considered stock? I tried reflashing multiple times, and even locking the bootloader, but the OTA still fails, and the phone is still not certified!