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!
Related
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.
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.
DirtyHennessy said:
I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.
Click to expand...
Click to collapse
Thanks! I will try that.
Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Have you made sure to update your radio, bootloader and vendor to the most recent version? Make sure to also try flashing twrp again but do everything through fastboot flash commands on your pc.
Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Flash root in TWRP before your first boot into the stock rom. On Nougat 7.0+, stock recovery replaces TWRP on boot if you do not. This solves both of your problems. When you clean flash and install a custom rom, with or without root, TWRP will remain. If you just use stock unrooted, then you should flash root before first boot each month when you update.
Sent from my Nexus 5X using Tapatalk
SuperSu 2.80 & 2.81 broke root for most phones - including mine. I had to flash 2.79 SR3 to get root again. Chainfire released 2.82 this morning but I haven't tried it yet.
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
If you boot to twrp first time mount system and use the filemanager to delete recovery-from-boot.p under system. Use magisk instead of supersu for root.
Okay, so i flashed the stock firmware (flash all but storage) that I found on xiaomifirmware.com (September security patch) onto my phone. I did this because I rooted my device previously and installed TWRP but I was unable to install OTA updates and so I decided to revert back.
In the process, I somehow ended up soft bricking my phone and that's why I had to flash the stock firmware via fastboot.
The problem is, ever since then, my device shows up as unverified on Google Play. My OEM is locked and all settings were set to stock.
Furthermore, when I decided to root it again using Magisk, I was unable to pass SafetyNet, regardless of however much I tried any of the solutions found via Google search.
So how do I fix this?
Same issue with Play Store! even I flashed Rom using FastBoot. got into bootloop because of Substratum Theme engine. The factory version of Play Store shows Device Certified but after It gets updated, it shows uncertified!
So I just got my Nexus 6p today and I've tried rooting this thing but it just kept making me stuck on the google logo. I successfully unlocked the bootloader and installed TWRP but everytime I installed from ZIP SuperSU or Magisk it would keep getting me stuck on the google logo. I've tried this several times because I could still go to bootloader. I've flashed the stock image a couple of times and reinstalled TWRP but I just can't get it to root.
Edit: I have flashed to stock and I'm on 6.0. I haven't tried reinstalling TWRP but the bootloader is unlocked and everything else is stock.
Edit 2: I just flashed TWRP and now I'm stuck on the google logo. Wtf is this??
nemesis101x said:
So I just got my Nexus 6p today and I've tried rooting this thing but it just kept making me stuck on the google logo. I successfully unlocked the bootloader and installed TWRP but everytime I installed from ZIP SuperSU or Magisk it would keep getting me stuck on the google logo. I've tried this several times because I could still go to bootloader. I've flashed the stock image a couple of times and reinstalled TWRP but I just can't get it to root.
Edit: I have flashed to stock and I'm on 6.0. I haven't tried reinstalling TWRP but the bootloader is unlocked and everything else is stock.
Edit 2: I just flashed TWRP and now I'm stuck on the google logo. Wtf is this??
Click to expand...
Click to collapse
Could be because you are on older version of Android. Did you make sure you are on the correct bootloader? Anyways I found with stock you must complete the initial setup then you can go back and root later. I've had success with Magisk 16.0 on nougat and Oreo so don't see why it wouldn't work on marshmallow.
Exodusche said:
Could be because you are on older version of Android. Did you make sure you are on the correct bootloader? Anyways I found with stock you must complete the initial setup then you can go back and root later. I've had success with Magisk 16.0 on nougat and Oreo so don't see why it wouldn't work on marshmallow.
Click to expand...
Click to collapse
What is a 'correct bootloader' anyway? I am on the latest bootloader and flashed latest factory images and still bootlooping, can't even make it to recovery mode (flashed 4-cores TWRP after I flashed stock).
Gamool said:
What is a 'correct bootloader' anyway? I am on the latest bootloader and flashed latest factory images and still bootlooping, can't even make it to recovery mode (flashed 4-cores TWRP after I flashed stock).
Click to expand...
Click to collapse
Ok sorry you said 6.0 in comment that's why I asked about bootloader. Also thought was just the root giving you a hard time not the dreaded bootloop that some 6Ps get.
So I had done an OTA update from rooted a11 to a12 and told magisk to reinstall after OTA. Everything was fine, I had a12 rooted and all my apps requiring root worked. I even thought that OnePlus had disabled the unlocked bootloader message too. Fo a month I felt like I had the perfect setup.
Then one morning I woke up to a notification from OnePlus updater there was a small update, but the system didn't say anything had been installed. I wondered if it was one of the live updates that I'd heard about for years so just to be safe I reinstalled magisk, both direct and OTA (dumb move I know) rebooted and soft bricked to recovery. I thought that magisk may have broke the bootloader so I grabbed the stock A12 (C11) boot image and rooted it on another phone and flashed to my OP8pro. This made it boot straight to fastboot mode 100% of the time. At this point I was lost and nuked my phone by MSM'ing it to 11.0.4.4 to at least get it back to a usable state.
Also I noticed that while I was in fastboot that I couldn't flash some partitions, but issuing the unlock and unlock_critical commands resulted with "already unlocked".
So I'm wondering what is the process of rooting OOS A12 if what the normal process soft bricks the phone?