I current have Pixel Experience.
I wanted to go back to Stock Rom and upgrade to Stock Oreo via OTA.
I followed the steps in this guide
https://forum.xda-developers.com/g5-plus/how-to/how-to-revert-oreo-custom-rom-to-stock-t3842658
However, after doing everything my device would not boot and stuck in, "Your device has been unlocked and can't be trusted"
Also, i'm getting "ID: bad key" instead of "N/A" that I was getting. It well then move to a screen titled "Erasing" with some floating circles and start the whole process over.
I have a full recovery backup but the adb sideload is failing. Any help is appreciated. Thanks!
Related
I've gone through all the steps to root, unlock, backup using cwm, but i keep on coming up with issues on bootup after updating via fastboot. any ideas? when it does properly boot up it shows the updated M screen, and the att screen, but then stalls out. also, I've seen 2 android warning screens, one with the android guy and a white triangle with a yellow exlamation point in it, and also have seen the android guy on its back with a red shaded triangle with a black exlamation point in it.
any help would be greatly appreciated.
I have 2 Atrixs, one was at 2.3.4 and the other was 2.3.6, both are experiencing the same problems
android system recovery attempt at applying update failed due to e:signature verification failed
If you're going to flash raw images via fastboot, the order shouldn't really matter. Just make sure you wipe everything before flashing.
wiping down the cache was what i did, at least thats what the cwm instructions were telling me. At that point i rebooted and entered into fastboot, flashed the files in the exact order displayed over at andriod police, rebooted, and stalled out during boot up at the att screen.
Since the files were flashed and should be there on the atrix, what would you suggest i do?
I selected to install 4.4 from my OTA notification and after it restarted my phone and then had the animation of an Android working it then went to the black screen with the white "Google" and it has been stuck there ever since. I held down the power key for ten seconds and it restarted and seems to be stuck in a bootloop. I tried entering recovery but i get a broken android animation saying i believe "no command"
So what can I do?
My phone was stock, so this should have been a simple update right?
I am pretty much a noobie.
I followed a step by step set of instructions for sideloading the update via a zip file, but when I get to the point I need to enter recovery mode nothing happens, i cant get to where i need to be. And my computer doesnt see my phone anymore when I plug it in via USB
Any advice would be greatly appreciated
thanks
Sideload the flashable zip of stock rom or any rom with the same android version in recovery ( guide )
Then flash back stock factory images (optional) ( guide ).
You can also refer this thread here.
Good luck.
So I was on mm with unlocked bootloader and i tried to update to nougat through the stock recovery but no luck (error status 7 or something like that) and i was like ehh screw it fastbooted twrp and flash supersu. that's when everything went side ways. bootlooped right after i clicked reboot system. it apeard a message saying that something DRM i didn't may atenction to it and something in red right before the asus image. can anyone help me out?
You skipped a step, you need to flash the no-verity file. You'll still have that DRM bootup screen but it'll be with yellow text.
https://forum.xda-developers.com/showthread.php?t=3569926
So I was trying to install the new Oreo beta, and couldn't get into TWRP, and couldn't get it to flash it either. So I tried to reinstall the stock recovery by using flashall, but during the process I accidentally disconnected my phone. For a while I was stuck in a bootloop, but I've gotten it to the point where I actually get in. But it still says my device is corrupted and cannot be trusted and may not work properly. Does anyone know how to fix this? The phone is functional, but I worry that it will fail to boot when I'm not near a computer.
Edit: Problem solved, realized I needed to flash the full stock.
that message comes up when bootloader is unlocked
For that specific boot message (I believe it's a red screen) you have to use invisiblek's boot fix.
Look at his page https://mata.readthedocs.io/en/latest/ at the very bottom and follow the instructions.
Quick Question
Ellises said:
For that specific boot message (I believe it's a red screen) you have to use invisiblek's boot fix.
Look at his page https://mata.readthedocs.io/en/latest/ at the very bottom and follow the instructions.
Click to expand...
Click to collapse
Do I fastboot flash this boot image then the stock boot image or just over top of the stock boot image? Also the boot fix image is only ~26mb while the stock boot image is ~65mb?
Got an H910 which has been fine for the longest time. It was running LOS17.1 with nothing else besides magisk installed. It was also the official release.
A week ago i decided I wanted LOS18.1 instead, but I got multiple E1001 errors unable to modify System partition.
Someone suggested I went back to stock and root again or something, so i flashed Kitkat zip and have since been stuck on an endless loop of "no command" recovery mode.
my device is still being picked up as US996, but despite all my attempts I can't seem to be able to flash anything. LGUP always succeeds but the second the devide reboots the "erasing.." screen is shown for a split second before going into an endless loop of turning on and off the screen with "no command", and still showing as US996.
in theory fastboot was already unlocked but I don't think it's the case anymore after the kitkat file thing.
I'm currently out of ideas. Am I missing something?
Any help would be appreciated.
Hzlph said:
Got an H910 which has been fine for the longest time. It was running LOS17.1 with nothing else besides magisk installed. It was also the official release.
A week ago i decided I wanted LOS18.1 instead, but I got multiple E1001 errors unable to modify System partition.
Someone suggested I went back to stock and root again or something, so i flashed Kitkat zip and have since been stuck on an endless loop of "no command" recovery mode.
my device is still being picked up as US996, but despite all my attempts I can't seem to be able to flash anything. LGUP always succeeds but the second the devide reboots the "erasing.." screen is shown for a split second before going into an endless loop of turning on and off the screen with "no command", and still showing as US996.
in theory fastboot was already unlocked but I don't think it's the case anymore after the kitkat file thing.
I'm currently out of ideas. Am I missing something?
Any help would be appreciated.
Click to expand...
Click to collapse
Did you flash the nougat kdz in the dirtysanta root guide? I had a kernel crash problem and started over to fix, but I didn't flash a KitKat ROM in LGUp