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

Installed wrong Vendor IMage? Phone apps keep crashing

I tried to install the newest Pure Nexus Rom with the newest vendor image, though I downloaded the newest image but the only one I have is the one that ends in D. Seems the newest ends in J. When I boot the phone after a couple seconds I keep getting pop up messages that tthe System UI has stopped . Is there a way to revert the changes? Or is there a way to download the right ROM or vendor image through USB and then reinstall? I hold the old ROM on my phone and deleted it, is there a way to recover the file in TWRP?

Novakingwai said:
I tried to install the newest Pure Nexus Rom with the newest vendor image, though I downloaded the newest image but the only one I have is the one that ends in D. Seems the newest ends in J. When I boot the phone after a couple seconds I keep getting pop up messages that tthe System UI has stopped . Is there a way to revert the changes? Or is there a way to download the right ROM or vendor image through USB and then reinstall? I hold the old ROM on my phone and deleted it, is there a way to recover the file in TWRP?
Click to expand...
Click to collapse
@Novakingwai
I don't think so the thread is closed, no support.
This thread has three 7.1.2 marlin factory images for April 2017:
Factory Images for Nexus and Pixel Devices
a. 7.1.2 (N2G47E, Apr 2017)Linkebc79a0b5015bd1d5d8d72c3a984cbf0de6e8d5bd26ab93fd2afcc9791199fc1
b. 7.1.2 (N2G47J, Apr 2017, Deutsche Telekom)Link503d88f556a481677ecaadb62e83fa3a2b73f103271b954f629838f45ea4168a
c. 7.1.2 (NHG47K, Apr 2017, Verizon)Linkfc027c3b428914d1a52fae80d88f5d3fd4f7ce9ac055edaa571ae5afcb85044d
Try 'a' if you are not on verizon or 'c'if you are on verizon.
Good lick!

Instant flash TWRP after OEM unlock

Just got Samsung Galaxy S9 yesterday, and wanted, of course, to install Lineage OS.
After some investigation I undestood that I need to wait 7 days after switching OEM Unlock in Developer options to flash unofficial recovery.
Fortunately found this video: https://www.youtube.com/watch?v=skyUCTs1cyI, followed instructions and it worked.
To be short:
1) Enable developers settings, and switch OEM unlock in it;
2) Turn phone to download mode, try to flash TWRP - it will be unsuccessfull with "Only official released binaries are allowed" (I've used heimdall on linux to flash);
3) Reboot phone into Android, disable automatic date and time and set it to round 10 days before security patch level (i.e. if your patch level is November 2019 you need to set date to 20-oct-2019);
4) Switch phone off, boot into Download mode again, flash TWRP again - now it would be successfull;
5) Reboot into TWRP not booting into Android (it will wipe recovery back), flash LineageOS / custom kernel / what do you want.
Tested on two different official firmwares (with 0ct 2019 and Nov 2019 patch levels) - it worked.
Also people in video comments say that it works for many Samsung phones.
Looks like universal backdoor in RMM check.
All credits go to https://www.youtube.com/channel/UCDq76mkkOcjn_3BDNyNtKOQ

FossaFX said:
Just got Samsung Galaxy S9 yesterday, and wanted, of course, to install Lineage OS.
After some investigation I undestood that I need to wait 7 days after switching OEM Unlock in Developer options to flash unofficial recovery.
Fortunately found this video: https://www.youtube.com/watch?v=skyUCTs1cyI, followed instructions and it worked.
To be short:
1) Enable developers settings, and switch OEM unlock in it;
2) Turn phone to download mode, try to flash TWRP - it will be unsuccessfull with "Only official released binaries are allowed" (I've used heimdall on linux to flash);
3) Reboot phone into Android, disable automatic date and time and set it to round 10 days before security patch level (i.e. if your patch level is November 2019 you need to set date to 20-oct-2019);
4) Switch phone off, boot into Download mode again, flash TWRP again - now it would be successfull;
5) Reboot into TWRP not booting into Android (it will wipe recovery back), flash LineageOS / custom kernel / what do you want.
Tested on two different official firmwares (with 0ct 2019 and Nov 2019 patch levels) - it worked.
Also people in video comments say that it works for many Samsung phones.
Looks like universal backdoor in RMM check.
All credits go to https://www.youtube.com/channel/UCDq76mkkOcjn_3BDNyNtKOQ
Click to expand...
Click to collapse
I used this method when i first got my S9+, and didn't want to wait, can confirm it works..

FossaFX said:
Just got Samsung Galaxy S9 yesterday, and wanted, of course, to install Lineage OS.
After some investigation I undestood that I need to wait 7 days after switching OEM Unlock in Developer options to flash unofficial recovery.
Fortunately found this video: https://www.youtube.com/watch?v=skyUCTs1cyI, followed instructions and it worked.
To be short:
1) Enable developers settings, and switch OEM unlock in it;
2) Turn phone to download mode, try to flash TWRP - it will be unsuccessfull with "Only official released binaries are allowed" (I've used heimdall on linux to flash);
3) Reboot phone into Android, disable automatic date and time and set it to round 10 days before security patch level (i.e. if your patch level is November 2019 you need to set date to 20-oct-2019);
4) Switch phone off, boot into Download mode again, flash TWRP again - now it would be successfull;
5) Reboot into TWRP not booting into Android (it will wipe recovery back), flash LineageOS / custom kernel / what do you want.
Tested on two different official firmwares (with 0ct 2019 and Nov 2019 patch levels) - it worked.
Also people in video comments say that it works for many Samsung phones.
Looks like universal backdoor in RMM check.
All credits go to https://www.youtube.com/channel/UCDq76mkkOcjn_3BDNyNtKOQ
Click to expand...
Click to collapse
Doesn't work on SM-960W with Dec 1,2019 security patch. I set it to 11-20-2019 ,amd tried to flash but it was unsuccessful

fbarcenas said:
Doesn't work on SM-960W with Dec 1,2019 security patch. I set it to 11-20-2019 ,amd tried to flash but it was unsuccessful
Click to expand...
Click to collapse
Could you try it with earlier official firmware? Saw in comments to video, that it helps.

Increase the date rather than decrease

fbarcenas said:
Doesn't work on SM-960W with Dec 1,2019 security patch. I set it to 11-20-2019 ,amd tried to flash but it was unsuccessful
Click to expand...
Click to collapse
Pretty sure
---------- Post added at 08:24 PM ---------- Previous post was at 08:15 PM ----------
fbarcenas said:
Doesn't work on SM-960W with Dec 1,2019 security patch. I set it to 11-20-2019 ,amd tried to flash but it was unsuccessful
Click to expand...
Click to collapse
Thought you couldn't unlock Snapdragon S9 or is that only SM-960/5U?

I tried to flash TWRP to a S9plus with the information in this thread, but it does not work for me.
- G965F/DS
- heimdall v1.4.2
- TWRP twrp-3.3.1-0-star2lte.img
- I made a build of Lineage 15 for star2lte, but as this tries to extract some files from the Android 8 S9plus, that I do not have, replaced the missing files with placeholder files to get a build.
- I did OEM unlock, but have since then made a number of resets, OEM unlock does no longer show up in menu
- S9+ came with latest version of Android 9 and updated to 10 nearly immidiatly
- Downgraded to july 2019 version of Android 9 (modem to Android 8 latest version)
- shows security patch october 2019 in preferences
- set date to 20 sept 2019 -> heimdall says recovery upload successful, failed to receive session end confirmation
- set date to 22 oct 2019 -> heimdall says recovery upload successful, failed to receive session end confirmation
still no TWRP installed, still no way to flash Lineage

RMM STATUS, I can't unlock it. So I can't flash twrp to phone.

will this trigger knox?
mobile in video is triggered but maybe on a "clean" one not

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.

Question Flashed 13, can't go back to A12 and now soft bricked - HEAD request failed: Unknown network error

Per the title I tried to go to A13 to see if it would fix the low ringer volume on my Unlocked Pixel 6 Pro, or whether I have a hardware issue. It did not. I decided to go back to A12 and wait until the stable release and trying to flash via adb tells me I can't downgrade. When I try the Android Flash Tool and select the A12 build I need, it starts and then shows a "HEAD request failed: Unknown network error" and stops.
I'm soft-bricked now. I get a message that the device is corrupt and may not work properly, then the bootloader unlocked warning I've always gotten after I unlocked that. After that I At best I get to a white screen with the Google logo or bootloader mode.
Has anyone worked through this error or does anyone have a solution on how to recover my phone? Thanks!

Reflash A13 and make a backup then flash - wipe A12

Paz9 said:
Reflash A13 and make a backup then flash - wipe A12
Click to expand...
Click to collapse
Thanks - that's exactly what I did. I was traveling and trying to get my phone working again and you are on the right track. I got it fixed fairly quickly, but I left the thread open to give another instance of hope to folks who may stumble across this in the future. I'm guessing I was flashing the OTA image and not the factory image, and it was confusing because it would partially succeed and then fail with no obvious indication of the reason for the failure. I've since flashed the factory image several times and while it too has the .sig files missing errors that appears to be a non-issue, it works just fine and I'm back in business.

It may be related to what we seen today with A13 being released. The Bootloader cant be rolled back to earlier version.
Someone posted today they can get Android 12 installed back, AS LONG as they edit the factory image script to skip the bootloader flash part.

chaco81 said:
It may be related to what we seen today with A13 being released. The Bootloader cant be rolled back to earlier version.
Someone posted today they can get Android 12 installed back, AS LONG as they edit the factory image script to skip the bootloader flash part.
Click to expand...
Click to collapse
It's not, he was on the Android 13 beta and was trying to flash the full OTA when the recovery does not permit flashing a lower firmware than what is already running. He only had to instead flash the firmware from the bootloader to downgrade from the beta.
However yes, if you take the Android 13 release bootloader you cannot downgrade back to Android 12's bootloader. How long the Android 13 bootloader will continue to boot Android 12 or if they will put another antirollback measure in is unknown.