6.0 OTA issue - X Style (Pure) Q&A, Help & Troubleshooting

I recently got the OTA notice on my Pure so I returned to stock, took the update, set the phone up, fastboot flashed twrp 2.8.7.1 and have tried to install SuperUSER a couple different times. Each time I get to the Android bootup screen, not the new boot screen and it freezes there. Anyone have any ideas?

In order to get root on MM you currently (possibly permanently) need a modified boot/kernel. Chainfire talks a little about it HERE
A flashable zip with the modified boot.img can be found HERE

Related

KitKat to Marshmallow update diary, kept apps and settings, rooted

I managed to upgrade my Nexus 7 2013 LTE from KitKat to Marshmallow using factory images yesterday and took some notes. All apps and settings kept (or at least I haven't noticed any issues other than no Xposed) and rooted. I figured someone might find this useful.
So, short version: upgrading directly from 4.4.4 to 6.0 with factory images didn't work without wiping data and where's the fun in that? So I took a longer route and went 4.4.4->5.02->5.1.1->6.0.0. It's possible I could've gone from 5.0.2 to 6.0 or 4.4.4 to 5.1.1 directly but I'm not going to try and see if that's the case. Enjoying Marshmallow now.
Basically, I did the same thing for all three update steps:
Unpacked factory image, rebooted to bootloader, flashed bootloader, radio, system.img, boot.img, cache.img. I rebooted to bootloader after flashing bootloader and again after flashing radio, same thing the flashall.bat does. Don't know if it matters.
Booted to TWRP recovery, flashed supersu zip and renamed /system/recovery-from-boot.p to keep TWRP.
Booted system and grew some gray hairs while the boot animation went on and on until it finally got to the long "optimizing apps" phase.
For 6.0 I flashed a modified kernel and supersu beta 2.52.
So, enjoying Marshmallow now. No issues so far. Root cloak detectors seem to be becoming a plague and I've only used an Xposed module for that.

TWRP won't load after initial install, and root doesn't work.

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.

Motorola Moto X pure stuck on bootloop after failed root attempt, HELP!!

Hey everyone I just recently got a Moto X Pure with TWRP recovery already installed and the bootloader unlocked, unrooted. The phone was stuck on Marshmallow so I went to update and it would take me to TWRP recovery every time and when I reboot back into the system, I'm still stuck on Marshmallow. So I downloaded an app that would make me download OTA updates while still having TWRP recovery but it needed root access, which I didn't have. I tried all of the one-click root apps but non worked then I stumbled across an easy root method: ( oops it said I can't post links, but basically I downloaded a supersu zip and flashed it) which I followed very precisely and I'm pretty sure I did nothing wrong. But when I flashed the ZIP using TWRP and booted back into system it was stuck on the Motorola logo which I'm assuming is bootloop. I was going to download a stock recovery using fastboot but I discovered that it would relock the bootloader, which would render the device useless to me so I can't. I also tried wiping the Dalvrik Cache but it always failed. I'm new to all of this so please guys I'm desperate for help. Thanks in advance
You can flash with fastboot the newest stock(the same version or upper) without commands "...oem..." at start and the end.
Or
The newest downloadable without commands "..oem, bootloader, gpt, oem...". @Philo0o
BL will be still unlocked.
Do you have a tutorial on how to do that please?
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 @Philo0o
More accurately you need to flash boot.img which is the kernel , in the case where root was being installed using systemless mode.
Otherwise, if you tried an old SuperSU version (where systemless didn't existed or the ones that failed to detect to install using systemless method on this phone) you'll need to reflash the whole system partition (using Firmware system chunks or custom ROM zip file).

P9 Bootloop after installing 'Elite Kernel', but can still use ADB and fastboot

Hello. a little while ago I restored my Huawei p9 lite nougat L31C440B380 rom from a bootloop thanks to tw1st3d83's P9 Lite Toolkit but since then i haven't been able root it again properly using magisk and other supersu apps because when i boot up music and sound don't play on my apps and videos on apps don't work at all, yet when i unroot my phone works normally, which is strange as i've rooted many times before with no problems. I'd been having some issues with magisk then due to installing and then deleting the viper4arise mod as apps didn't show in my drawer and magisk modules as well as the manager started to malfunction frequently. I looked around for anything that might help me fix this and came across HassanMirza01's P9 Lite elite kernel (All Variants CxxB3xx Phh Superuser v9 version and MagiskSU v10 version based on the b380 Rom) and decided to try it out. I used a special modded version of oldroid's twrp (TeamElite) https://www.androidfilehost.com/?fid=889764386195914200 to flash the kernels, the phh Superuser 9 version, https://www.androidfilehost.com/?fid=529152257862726224 , and the magiskSU 10 version, https://www.androidfilehost.com/?fid...0096634768996. Because they were pre-rooted, I assumed at the time i'd be able to solve my root problem.
When i was using the kernel I noticed everything ran more smoothly than usual but sound and video still weren't working. Because the kernels were pre-rooted before i installed, i think they may have modified the boot image in such a way that even when i completely format data with twrp and do an advanced wipe, then restore the factory images including the stock boot image i extracted from the B380 rom it starts up normally but gets stuck on the loading screen. At first I thought it needed time to load so I left it to charge overnight as the battery was pretty low but i when i woke up the next morning it was still on the Huawei logo. i don't think the kernel has an uninstaller or if there's one i can flash that doesn't have root. If i flash the boot image that I patched earlier with magisk, everything loads fine but i'm still faced with the same problems with no video or sound. I've been thinking of just reflashing the stock images and then relock the bootloader so i can do three button "dload" method for a clean install of my B380 rom as i've tried to use it before and failed as i get this error message before it finishes:
write radio image...
32K crc checked failure
E:unknown command [errno]
update_huawei_pkg_from_ota_zip: update from zip failed
Updater process ended with ERROR: 7
But seeing as how the kernel has altered the boot image I can only use the boot image that I patched with magisk or supersu.
I'm definitely sure that the method won't be able to work on a phone that's rooted but what i'm more worried about is that something goes wrong and i end up in a bootloop with no way to use adb to unlock the bootloader or use recovery, pretty much bricking the device. I've looked around for other kernels i might be able to flash and restore my device like Smoky Kernel and Rusty Kernel but they didn't work at all as opposed to the Elite Kernel. Can I lock the bootloader with a rooted phone and my reinstall my stock rom with the three button method or is there another way i could go about this? I'm asking this way because every time i unroot with either magisksu elite kernel or my magisk boot image the phone will always bootloop. The TWRP version I'm on, 3.1.1-0 isn't very useful at the moment compared to when I was on MM because when I had a problem I just flash and forget, but as the stock rom has two files it's a bit harder for me to get the hang of it so i would be very grateful for where to go from here.

[VS995] Fails to completely boot after Super ROM load

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

Categories

Resources