Develop Bugs

Incomplete install of Nougat 7.1.1

Today i tried to update my Nexus 5x from Android 6.0.1 to Nougat 7.1.1.
I hadn't followed any update nor tried to modify in any way my phone since last June, when I installed for the first time my first ROM, so i just downloaded the latest version of Nougat, installed the sdk and TWRP on my device and wiped all the data without any backup.
Obviously without Android my phone couldn't turn on, and after various tries, i placed into the internal memory all the .img of nougat, and installed manually one by one the: 1.Vendor, 2.System, 3.boot.
I couldn't find a place where to install manually the reaming: cache, recovery, user data.
Is there any way i can check if i missed any step, or i was supposed to install these other .img somewhere else, or i did everything in the correct way?? (My phone at the moment seems to work fine, it's syncing my account, and all the apps seems to work)

Also to specify, my original intent it was to attempt a factory reset, to erase previous ROM, kernel, Root and various bad configuration that made my phone slow. I just would like to make sure my phone is as new, with no old configuration.
On the startup tho it still had the previous wallpaper and icon distribution over the screen.
Did i do a factory reset or not?

SordiSpicci said:
Today i tried to update my Nexus 5x from Android 6.0.1 to Nougat 7.1.1.
I hadn't followed any update nor tried to modify in any way my phone since last June, when I installed for the first time my first ROM, so i just downloaded the latest version of Nougat, installed the sdk and TWRP on my device and wiped all the data without any backup.
Obviously without Android my phone couldn't turn on, and after various tries, i placed into the internal memory all the .img of nougat, and installed manually one by one the: 1.Vendor, 2.System, 3.boot.
I couldn't find a place where to install manually the reaming: cache, recovery, user data.
Is there any way i can check if i missed any step, or i was supposed to install these other .img somewhere else, or i did everything in the correct way?? (My phone at the moment seems to work fine, it's syncing my account, and all the apps seems to work)
Click to expand...
Click to collapse
Use a computer and fastboot to do this upgrade. Follow section 11 of my guide to upgrade successfully to stock March 7.1.1 N4F26T. Boot into TWRP to perform a factory reset then reboot into the bootloader to install each img.

SlimSnoopOS said:
Use a computer and fastboot to do this upgrade. Follow section 11 of my guide to upgrade successfully to stock March 7.1.1 N4F26T. Boot into TWRP to perform a factory reset then reboot into the bootloader to install each img.
Click to expand...
Click to collapse
Thanks a lot! that's the post i was looking for

weird thing happend to my pixel xl. it could't update/flash from lower build to 8.1

I've tried to solve this issue over one week now. Just couldn't figure out why it nearly drives me crazy.
It works fine under 7.1.x and 8.0. OTA function works fine under 7.1.x to 8.0. flash to stock image (below 8.1) doesn't show any problem.
1.When I OTA from 8.0 to 8.1,the phone can receive OTA and download and install, it seemed no problem at this procedure. When I clicked restart to complete OTA , it booted to Google with white background and return to boot interface three or four times and get into system, there is still old build there.
2. Flash factory image (8.1), click flash all , the whole procedure seems working properly, when it booted up , screen switched Google image and boot image several times and endend up with a laid down robet and saying NO COMMAND. I've been searching this for days . Have tried as many as method as I can find to flash it to 8.1 . The only result is showing up no command. I v tried sideload OTA.img, the same result . Also tried to switch slot to reflash stock image . Always same result. Keep telling me NO command . I'm so desperated .
The problem I state above only happens when I try to update/flash from lower build to 8.1.
BL unlocked.
Does anyone have the same issue and have solution about it ?

You need to flash whichever factory image you want to both A and B slots with a recent new ADB setup to go backward in versions.

Im guessing youre trying to avoid wiping internal storage and thats why you want to patch with OTA. you might have to bite the bullet and just back everything up and run the latest factory img to get you on the update without issues going forward.
I always recomend when versions change like 7.1.2 to 8.0 to 8.1 to factory reset everything so you dont have to trouble shoot issues later in life.

Im guessing youre trying to avoid wiping internal storage and thats why you want to patch with OTA. you might have to bite the bullet and just back everything up and run the latest factory img to get you on the update without issues going forward.
I always recomend when versions change like 7.1.2 to 8.0 to 8.1 to factory reset everything so you dont have to trouble shoot issues later in life.

SynisterWolf said:
Im guessing youre trying to avoid wiping internal storage and thats why you want to patch with OTA. you might have to bite the bullet and just back everything up and run the latest factory img to get you on the update without issues going forward.
I always recomend when versions change like 7.1.2 to 8.0 to 8.1 to factory reset everything so you dont have to trouble shoot issues later in life.
Click to expand...
Click to collapse
Thanks for the post .
I was not trying to avoid wipe internal storage , just because flash to stock image failed

Safe to Flash Backwards? (8.1 to 7.1.2)

I Flashed March Factory Image, but since my Call Recorder App no longer works correctly I'm hoping to go to 7.1.2 and it should work once more!
However before I did that I figured I'd ask just to be safe...
Is it safe to go from 8.1.0 (OPM1.171019.021, Mar 2018) to 7.1.2 (NJH47F, Aug 2017) ? (I'll be doing the wipe, so it's nice n clean...)
My device is the Google Pixel XL (Verizon with UnLocked Bootloader)
Thanks!

If you perform wipe (keep "-w" in flash-all script in factory image, as default) there shouldn't be any problem.
But just because you have the march 8.1, I'd suggest you to try april 8.1 image before downgrade. Maybe that fixes the problem itself.
Edit: users say you'd better flash nougat image on both slots. But some users say they're stuck in a bootloop.
But here I found a potentially useful post where they talk about flashing also 8.0
Maybe could help in case of a bootloop situation.

IIRC, the factory image checks for a compatible bootloader, If the bootloader has been updated by the 8.1.0 update, or any inbetween, the 7.1.2 factory image may fail for not having a compatible bootloader.
If it does, you should be able to get around this by pulling the bootloader out of the 7.1.2 factory image, and FASTBOOT FLASH bootloader_a (and bootloader_b) [bootloader image file]

OmniROM stuck at boot animation load screen

Moto G Stylus Metro PCS brand:
I'm brand new to this subject so please forgive any ignorance. I'm decent with linux but new to android stuff.
Tried flashing the latest weekly build of OmniROM - now seems to be stuck at boot screen and won't go past. I am coming from latest OTA update from Motorola.
Phone was not rooted prior to starting this.
I also accidentally wiped slot A with my factory image on it (oops).
TWRP did not ask for any decryption key so I ran:
fastboot erase userdata
and this seemed to fix errors that I was getting while flashing with respect to denying access.
What I've done:
-Unlocked bootloader
-Installed TWRP 3.5.0-10 from the g-stylus forum.
-wiped and formatted via TWRP
-flashed 5/23 weekly build of OmniROM
Now no matter what I do or what slot I flash to it will not get past the Omni boot load animated screen. I've run this for almost 2 hours and nothing happens.
Any ideas?
Thanks!

nutsnax said:
Moto G Stylus Metro PCS brand:
I'm brand new to this subject so please forgive any ignorance. I'm decent with linux but new to android stuff.
Tried flashing the latest weekly build of OmniROM - now seems to be stuck at boot screen and won't go past. I am coming from latest OTA update from Motorola.
Phone was not rooted prior to starting this.
I also accidentally wiped slot A with my factory image on it (oops).
TWRP did not ask for any decryption key so I ran:
fastboot erase userdata
and this seemed to fix errors that I was getting while flashing with respect to denying access.
What I've done:
-Unlocked bootloader
-Installed TWRP 3.5.0-10 from the g-stylus forum.
-wiped and formatted via TWRP
-flashed 5/23 weekly build of OmniROM
Now no matter what I do or what slot I flash to it will not get past the Omni boot load animated screen. I've run this for almost 2 hours and nothing happens.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Weekly builds may be unstable. I'm actually curious on how you got a hold of such build for the this device. Most, if not all ROMs are unofficial for the stylus and updates for each rom varies by contributed developers.....
However, you say you're decent with Linux. I'm sure there's some developers here that would help you with various tools to learn on how to make your own version of any type of OS.
As for OmniRom, I'd probably ask @vache for some help, for he has his own unofficial version.
Also, I recommend that you have the latest platform tools and the moto software tool if you don't have these yet...

nevermind I got it working. I was flashing p2pstate.bin directly (somehow this works?) when instead I was supposed to extract the image files and flash the respective files.
Seems to boot up now. Thanks!

nutsnax said:
nevermind I got it working. I was flashing p2pstate.bin directly (somehow this works?) when instead I was supposed to extract the image files and flash the respective files.
Seems to boot up now. Thanks!
Click to expand...
Click to collapse
That's good you got it to work. One developer once told me, when all else fails, think outside of the box. You'll eventually get it to work somehow

I have your solution cuz I went through the same thing.. you have to start out with stock Android 10 so you have to be bootloader unlocked and rooted that way you can downgrade your software and it's only the super images that you have to downgrade.. so just flash your supers and you'll be fine but they have to be stock Android 10 it doesn't matter what firmware version because you're keeping the same modem file

Help Needed - Reverting back to stock from Lineage - Google Pixel XL Marlin

So after years of never needing to create an account.....I am stuck. Hoping yall can help me out.
I HAD lineage OS installed and everything was working fine. I wanted to revert back to stock so that I could get the google photos unlimited upload back.
I HAD lineage recovery installed but now I am soft-bricked and cant get into recovery.
My bootloader is unlocked and fastboot is working.
When recovery was working, I tried to install the full OTA and that failed so that lead me to the Full Factory Image.
I try to run the flash-all.sh script and it does all sorts of failing. (See flashAllLog.txt) I believe the crux of this is:
When I installed LineageOS, my phone started identifying as a Pixel 3 which was strange but whatever. When I am trying to run this flash-all basically it says that my bootloader is newer and it needs an older version.
So then I thought well maybe I need to erase the slots (eraseLog.txt). Those all worked fine but I still couldnt flash all
So then I was thinking maybe if I just flash the bootloader manually (manualBootFlashLog.txt). But that failed as well.
Am I just boned here or is there an android wizard out there who can point me in the right direction. Please let me know of ANY other information I could possibly provide

Here are 4 options, there's more even tedious stuff you could try but Id start with these
1.) Have you tried to just use fastboot to BOOT into the recovery.img file from the factory image zip (not flash it) and then you can sideload the OTA from there?
2.) You can also try to edit the flash-all file so it doesn't re-flash the bootloader. Just flash system, data partitions etc.
3.) Try another factory image. I assume you tried to flash the latest Android 10 full factory image, maybe try an older one? Maybe even Android 8 or 9 and the just take the OTA update in settings.
4.) Also can try to boot (not flash) lineageos recovery to see if you can at least flash back into LineageOS (or maybe a different custom ROM, PixelExperience for example enables the unlimited Google Drive storage) to get a working device again.