Database Users

How do I go from 5.1.1 on nexus 10 to Nougat?

I am not a programmer and have little knowledge about flashing the ROM so to make sure I understand what I need to do and the order it needs to be done.
My Nexus 10 works great still, I have not had a security update for 2 some years and am concerned about this. Last October I tried to upgrade to 6.0 but it would not recognize the new rom and I ended up going back to the original 5.1 rom.
What I need to know is how to do it in a way I can understand. I have seen a utube video of someone that has been able to do it. So I know it can be done. Just need to know how.
Thanks,
Mike B.

Assuming you have a PC use this tool to unlock then root and install a custom recovery
Next download a Nougat rom like Lineage
Also download gapps and SuperSU
Copy the rom, gapps, and supersu into a folder on your tablet
Now reboot the tablet into recovery and do a full wipe then from recovery
Flash the rom
Flash gapps
Flash SuperSu
Reboot to system and give it a few minutes on the first boot

TWRP fails to flash ROM (error 7) and asks for a password.

OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Code:
C:\Users\Fish\Downloads\ADB>adb devices
List of devices attached
e33edd51 sideload

MrGodMan said:
OK, so I totally ****ed up somewhere while trying to wipe and flash stock while I could only see half my screen. I now have a fully working screen but no system.
Current situation is if trying to boot phone normally I get stuck on ZTE logo.
If I press volume keys during boot I get to here; https://puu.sh/z7YQa/8de2adc04e.jpg
Selecting recovery takes me to TWRP which immediately asks for a password (that I never set up).
If I attempt to flash RR (which was previously installed) I get error 7. (Lineage OS has the same response) https://puu.sh/z81cA/6371d882cc.jpg
I can successfully flash the latest TWRP (twrp-3.2.1-0-ailsa_ii.img).
I've also tried flashing A2017_N_Modem.zip and ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip which appear to complete successfully.
TWRP ADB Sideload seems to work and my PC can see the phone (adb devices but I've not tried anything with that yet for fear of ****ing up further.
Click to expand...
Click to collapse
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.

Choose an username... said:
Look, you have an A2017G, right? Error 7 is caused by not flashing the universal bootloader. The password is because you forgot to flash magisk or supersu on the last rom's first boot.
Download 3 things: raystef66's TWRP flashable B09 bootstack and stocksystem zips (from the download center or the dedicated thread, but make sure that it's the TWRP flashable ones) and Magisk 15.2. Install the BOOTSTACK, then the ROM, then Magisk. After that go to Wipe, and FORMAT DATA (not wipe!). You'll lose your internal storage.
Click to expand...
Click to collapse
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?

MrGodMan said:
Thank you so much. Got that all done nicely and have a working stock ROM.
How would I now get from here back to RR?
Click to expand...
Click to collapse
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.

Choose an username... said:
Reading instructions is a start :laugh:
For real now: Get the ROM, the B15 universal bootloader (from the Lineage thread), get the latest modem file from the download center (B09 now for example), Magisk 15.2, GApps zip (unless you'll go microG) and be sure that you are on the latest TWRP or update to it.
Flash the bootloader and modem file (you'll have to install the modem as image i think). After you flash the bootloader your phone model becomes 'axon7' instead of 'ailsa_ii'; most custom roms use this to know whether you flashed it or not; and the region will be A2017U which is normal (it is based off of B15 for the U, don't panic). After that, flash the ROM and Magisk and GApps.
Click to expand...
Click to collapse
Perfection.
Everything works!

Downgrading firmware from Nougat to Marshmallow

Hi,
I have a Nexus 6P that has Android 7.1.2 (N2G47W) installed. I've just unlocked the bootloader, installed TWRP then installed Magisk 16.0 for root.
I'd like to next downgrade from Nougat to Marshmallow. Are there any steps to do so? Can I just boot to TWRP, and immediately install the factory image from https://developers.google.com/android/images#angler?
Or are there any additional steps I need to take?

@goister You can't with TWRP download marshmallow from Google API site. Maybe do a good wipe in TWRP before hand of course back up anything important on comouter. Then follow the hiesenberg guide for returning to stock. Your in luck cause I've read with being on the latest Oreo can no longer return to marshmallow or nougat though I haven't verified myself. Best of luck mate.

Exodusche said:
@goister You can't with TWRP download marshmallow from Google API site. Maybe do a good wipe in TWRP before hand of course back up anything important on comouter. Then follow the hiesenberg guide for returning to stock. Your in luck cause I've read with being on the latest Oreo can no longer return to marshmallow or nougat though I haven't verified myself. Best of luck mate.
Click to expand...
Click to collapse
Hi,
Not sure I get your post. My Nexus 6P is stock except for an unlocked bootloader, TWRP and Magisk root. Are you saying follow the guide at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 specifically step 10. How To Flash The Factory Images (And Return To Stock)?

goister said:
Hi,
Not sure I get your post. My Nexus 6P is stock except for an unlocked bootloader, TWRP and Magisk root. Are you saying follow the guide at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 specifically step 10. How To Flash The Factory Images (And Return To Stock)?
Click to expand...
Click to collapse
That's exactly what I'm saying unless you want to flash a marshmallow ROM. Then you can use TWRP but would still need 6.0 gapps and a computer to fastboot flash MM bootloader of that months build. MM vendor could be flashed by either fastboot or TWRP. Your best to download a MM build from Google site. Then unzip that folder and inside unzip again. You will get all the bootloader, vendor (radio optional) you will need for that months MM build. Then follow the guide from hiesenberg for returning to stock . Best to put all the images files and fastboot in the folder that is suggested in the guide . That way you can copy and paste the commands as written on the guide. There might be a flash all bat file you can use in the stock folder but not sure if MM had that I never used. If you have any more questions feel free to ask.

Yes I intend to flash the stock Marshmallow ROM from https://developers.google.com/android/images#angler specifically the latest one (MTC20L). My end goal is a rooted Nexus 6P with the MTC20L firmware. Wouldn't the stock Google build already have gapps? I don't intend to use a 3rd party ROM.

goister said:
Yes I intend to flash the stock Marshmallow ROM from https://developers.google.com/android/images#angler specifically the latest one (MTC20L). My end goal is a rooted Nexus 6P with the MTC20L firmware. Wouldn't the stock Google build already have gapps? I don't intend to use a 3rd party ROM.
Click to expand...
Click to collapse
Yes that's right gapps not needed with stock. Wasn't sure on your level of experience so mentioned that with a ROM you would need gapps of that android version . If I where you I would back up my phone completey and wipe everything in TWRP including internal before hand. So many times files get left behind especially using different versions of android to avoid any issues. Be warned though wiping internal includes pictures, downloads, music, documents etc.

Exodusche said:
Yes that's right gapps not needed with stock. Wasn't sure on your level of experience so mentioned that with a ROM you would need gapps of that android version . If I where you I would back up my phone completey and wipe everything in TWRP including internal before hand. So many times files get left behind especially using different versions of android to avoid any issues. Be warned though wiping internal includes pictures, downloads, music, documents etc.
Click to expand...
Click to collapse
Thanks. I've no issues wiping the phone as this is pretty much a fresh phone. There's nothing to even back up. The only thing I've done so far beyond rooting, was to import a certificate into /system. I suppose a factory reset would delete this certificate and bring it back to stock (but rooted)? Or should I wipe with TWRP instead?
Looking at the zip file of the stock ROM, here's what I see
bootloader-angler-angler-03.54.img
flash-all.bat
flash-all.sh
flash-base.sh
image-angler-mtc20l
radio-angler-angler-03.61.img
After wiping with TWRP, would I be able to run flash-all?
Edit: I've just TWRP wiped everything, and rebooted. However, the device is stuck at the initial "Google" screen with the lock icon at the button. How long is it supposed to take to boot up after a full TWRP wipe?

OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.

[Help] I can no longer access wifi after flashing TWRP

So i've exhausted almost every xda thread I can find, and finally decided to make a post myself. This is maybe the 6th or 7th time I've had to MSM tool my phone because I softbricked and could only access bootloader. I'm a newbie so you may need to go in detail in what I should do. All help is very appreciated.
I'm trying to flash a new ROM to my phone, the one in question is the latest nightly build of LineageOS: lineage-17.1-20200806-nightly-fajita-signed.zip, the ROM itself works fine, however, flashing TWRP after flashing this rom (even if I wipe dalvik/cache) I no longer am able to access wifi). I've flashed stock and started over about 5-6 times (from the very very beginning, including unlocking the bootloader) and I'll always end up with a wifi issue or a bootloop.
I've tried multiple different versions of twrp, including the unofficial 3.3.1-32 Q unofficial builds from this guide and both 3.4.0-0 and 3.4.0-1 from the official website, both leading me to the same results. (the unofficial build wouldn't decrypt, so I failed with that one).
I'll go through the steps I do in detail, and if anyone sees an issue with my process, please correct me.
1- enabled developer options
2- enabled usb debugging and oem unlocking in developer options
3- booted into bootloader with
Code:
adb reboot bootloader
4- checked to see if phone is connected and unlocked the bootloader with
Code:
fastboot oem unlock
5- set up my phone again, enabled dev options, and enabled usb debugging again.
6- booted into bootloader again
7- typed this into the terminal to temporarily boot TWRP
Code:
fastboot boot <recovery_twrp>.img
7.5- flash copy-partitions.zip from the LineageOS install guide
8- went to advanced>adb sideload>swiped then went on adb terminal to sideload TWRP installer
Code:
adb sideload <twrp-installer>.zip
9- went to menu>reboot>recovery
10- after rebooting went to wipe>factory reset slide>swiped slider
11- went back to menu>advanced>adb sideload>swiped then went on adb terminal to sideload (while checking wipe cache/dalvik)
Code:
adb sideload <lineageOS-rom-nightly>.zip
12- tapped reboot system
this is where things begin to go wrong:
- i notice that I can't boot into lineageOS, lineageOS claims android data is corrupted and needs to factory reset
- factory reset phone
- boots up fine, go through set up process (wifi works right now, only problem I notice is that within build settings, it shows a completely different phone number on my SIM card rather than the phone number I actually have, but it doesn't look broken or corrupted), enable usb debugging again, boot into bootloader
- type
Code:
fastboot boot <recovery-twrp>.img
- twrp loads up fine
- go to menu>advanced>adb sideload>swipe to begin sideload then type
Code:
adb sideload <twrp_installer>.zip
- reboot system
- boot process takes forever, (restarts 3-4 times) phone feels sluggish, and wifi will no longer work (data works fine)
- i give up and I MSM tool my phone.
I genuinely think this is because of TWRP, I read through a few xda threads claiming that the official 3.4.x builds had many issues, and therefore would reccomend using 3.3.x builds. I tried both from the official website and the unofficial TWRP by mauronofrio, where i get decryption problems on both of them. only 3.4.0-x TWRP builds would get me as far as flashing the rom. I've tried this process on both android 10.3.0 and 10.3.5
I genuinely would like some help. this phone is my daily driver and not being able to use TWRP (let alone properly flash a ROM) is a big problem that destroys what I loved about my phone in the first place. Thanks in advance.

I'm assuming this is not a TMobile 6T. With that assumption.
Try my LOS install guide. Note I couldn't get the 10.3.5. fastboot ROM to work. However if you are already on 10.3.5 stock, you are fine, just go with it. I updated manually to 10.3.5 using TWRP, and then used the latest weekly build and everything has been fine. Just go straight to the TWRP step. Other wise use the 10.3.4 fastboot rom. Cliff notes version in the second post.

https://forum.xda-developers.com/on...ash-magisk-t4022157/post81248271#post81248271
Follow this thread. If you're losing WiFi in stock from flashing twrp, there's way to prevent it

Extreme_Ninja2099 said:
https://forum.xda-developers.com/on...ash-magisk-t4022157/post81248271#post81248271
Follow this thread. If you're losing WiFi in stock from flashing twrp, there's way to prevent it
Click to expand...
Click to collapse
Im not rooted, im coming from unrooted 10.3.5

OhioYJ said:
I'm assuming this is not a TMobile 6T. With that assumption.
Try my LOS install guide. Note I couldn't get the 10.3.5. fastboot ROM to work. However if you are already on 10.3.5 stock, you are fine, just go with it. I updated manually to 10.3.5 using TWRP, and then used the latest weekly build and everything has been fine. Just go straight to the TWRP step. Other wise use the 10.3.4 fastboot rom. Cliff notes version in the second post.
Click to expand...
Click to collapse
this worked!! thank you so much for such a great guide!
I did one thing differently though, instead of using the fastboot rom or running it through scripts, I used the copy-partitions.zip file available on LineageOS' fajita install guide to make both partitions appear the same. I realized my mistake when I didn't flash the rom twice, as that's mandatory when it comes to A/B partitioned phones
Everything works smoothly! thanks!

One Plus 5 won't upgrade to new Android.

Hi
I fixed my oneplus 5 using MSMdownload tool. It put my phone on Android 7.1.1 with July 1st, 2017 security Patch and Oxygen OS 4.5.8, I have exhausted all the option to upgrade it to latest Android but it won't update. Every time I check for update it will show that it is up to date. I have also tried "local Upgrade" option but it shows installation failed.
Any work around this would be highly appreciated
Thanks
Aman

@lucider14 Just curious why you used the MSMDownloadTool from OxygenOS 4.5.8 and not the one for OxygenOS 9.0.11? You most likely won't see OTAs for Android 7 as it is now 4 Android Versions behind as of this week. Android 9.0.11 was the last official fully released OTA, OxygenOS 10.0.0 Hotfix is last official OTA OnePlus has released into the wild.

My phone waa bricked so had to use it. Please let me know if there is any workaround for this to update.

@lucider14 The workarounds I would try are:
Opt 1: Upgrade via zip file in Stock Recovery
Step 1: Download latest OTA from https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Step 2: Copy zip file to root of Phone storage
Step 3: Reboot into Recovery
Step 4: Install
Opt 2: Use Newer MSMDownloadTool:
Step 1: Download newest tool from here https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870
Step 2: Reboot phone into EDL
Step 3: Run newer MSMDownloadTool

card13;83478941 [user=11104643 said:
@lucider14[/user] The workarounds I would try are:
Opt 1: Upgrade via zip file in Stock Recovery
Step 1: Download latest OTA from https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Step 2: Copy zip file to root of Phone storage
Step 3: Reboot into Recovery
Step 4: Install
Opt 2: Use Newer MSMDownloadTool:
Step 1: Download newest tool from here https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870
Step 2: Reboot phone into EDL
Step 3: Run newer MSMDownloadTool
Click to expand...
Click to collapse
@lucider14 OOS 4.5.8 is pre-treble. You can't jump directly to Android 9 or 10. One of the OOS updates before Android 9 set up treble on our phones. I don remember exactly which one. You're best to use Opt 2 above, it will be easier.
Cheers!?

lucider14 said:
Hi
I fixed my oneplus 5 using MSMdownload tool. It put my phone on Android 7.1.1 with July 1st, 2017 security Patch and Oxygen OS 4.5.8, I have exhausted all the option to upgrade it to latest Android but it won't update. Every time I check for update it will show that it is up to date. I have also tried "local Upgrade" option but it shows installation failed.
Any work around this would be highly appreciated
Thanks
Aman
Click to expand...
Click to collapse
First,flash it 9.0.11 build and then OxygenOS 10.0.0 Hotfix..

And with https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater

I've had a similar problem and I thought I broke my phone, got pretty scared can't buy a new phone but need a newer android for my apps to work.
I came from freedom OS on android 7 so I never had the project treble on my phone and tried to flash new factory images, as a result, no newer TWRP recovery worked and I was unable to boot into anything other than the bootloader. I had the same error with Error 7, from what I can understand this is from a screwed up or non-existing "vendor" partition which says stuff like "this is a OnePlus 5" for newer factory images to install (factory image told me I didn't have a OP5), this never existed in android 7 or OOS 4.X.X. ScRuFFy7 is correct, the vender partition was created in OOS 5.1.4 (or OTA 037) and only when android is booting up, this took like 10 mins on mine. Once this vendor partition is correctly created you can flash newer TWRP recovery (I flashed 3.4.0) and newer factory images, like OOS 9.0.11 then to version 10. The built-in updater and stock recovery can update to the newer versions with the flashable zip files. For whatever reason OnePlus don't size the partitions in their zips so they make small changes from one version to the next so skipping specfic versions throws up errors in the future.
Screw it, I should document what I did in case I mess up my phone in the future and maybe be helpful to someone else in need, especially in this messed up and depressing time of the plague. But anyway this is what I did to get my phone back, I should point out I have no idea what I'm doing. Meaning I'm a N00b.
NOTE: this process Wipes all the data from the phone, so I hope you have backups right now.
Will need ADB, you can install This on windows, it's super easy and works thanks to mauronofrio. You can get the all in one tool too from here it's pretty handy and can format and decrypt from the bootloader, from mauronofrio? I think? This guy is pretty good. I got all old firmware from Here thanks to Some_Random_Username for the life line since OnePlus won't provide the old Zips anymore.
1) Boot to TWRP recovery if you have it installed (VOL DOWN + POWER). If not Boot to Bootloader (VOL UP + POWER) and flash TWRP Recovery. You can use TWRP 3.1.1 This one works on OOS 4.X firmware without giving me a Black Screen.
1a) To Flash the Recovery you can use the all in one tool to flash it or open up command prompt and use the Fastboot Flash [insert recovery file name here .img] command to flash it, you can find the FastBoot Flashing Method in the middle of this page for instructions.
2) Format Data. The Format Data button in TWRP recovery not the swipe to factory reset, because we're going back to scratch.
3) Flash OTA_006 (OOS 4.5.2) original firmware from the link above (says ota_006 in the middle of the loong file name)
4) Boot into android and use System Update in settings and stock recovery it just flashed to flash OTA_020 (OOS 4.5.15) by clicking on the cogwheel in the corner and choosing Local Update. [probably skippable I just wanted to make sure it works]
5) Boot into android again and install OTA_27 (OOS 5.0) with System Update again.
6) If it doesn't boot, go to Bootloader and flash TWRP. Once in the recovery and you go to install and if you find all the folders have random numbers and letters for names then the storage in encrypted.
7) Format to get rid of encryption (random name folders) then reboot to Recovery and Flash OTA_27 again and let it start fresh on OOS 5.0 to make sure it's still booting and working.
8) Once booted Flash OTA_037 (OOS 5.1.4) wait for vendor partition to be created (took 10 mins on my OP5), reboot to TWRP and format if folders are encrypted and reflash OTA_037 if needed.
Once booted into android this is the point where you should have the Vendor Partition already created by the factory image, you can go back into TWRP (flash TWRP if needed) and under Mount be able to see, mount/unmount a Vendor partition without errors. This should solve the Error 7 problem with factory images. A newer version of TWRP Recovery should work now, I installed 3.4.0 from mauronofrio Here. 3.4.0 works with android 10.0 so I was glad.
9) Boot android again and flash OTA_038 (OOS 5.1.5) just to make sure with stock recovery. [Probably skippable but I was a Paranoid Android at this point, just to make sure it still works]
10) Boot to android again and install OTA_042 (OOS 9.0.0) with System Update to keep making sure it works. [Again, I was Paranoid. Probably Skippable]
11) Boot to android again and install OTA_054 (OOS9.0.11) as last Android 9 update to have things set up ok.
12) Boot into Android again and install the latest android 10 from OnePlus (OTA_068) with System Update and the Stock Recovery, this is Android 10.0.0 and OOS 10.0.0. Things should work fine at this point but I doubt the check for update will get new oneplus updates. As of Sep 25, 2020 it is up to date. Technically.
I should add something else I discovered after. I found a flashable zip file from one of the lineage OS posts of a oneplus5_vendor_5.1.5.zip Here. You might be able to just use that to create the Vendor partition then just Flash one of the OOS 5.X Firmwares and go from there, I've not tried it so I'm not 100% sure but it's a possibility?
Hope this is helpful to someone at some point in time. for troubleshooting at least. Honestly really glad I have a working phone right now.