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
Hi, can someone point me to the official guide/tutorial to move from 4.1.14 to oreo.
I'm unlocked and using twrp. Not sure which version.
I don't can about data loss...so a complete wipe and install is fine by me.
I see an official guide that keeps data, and refers to the official guide that doesn't...but I can't find it!
Oh, and I'm defo encrypted when I go into twrp, as it asks for my pin.
If you don't care bout data
flash Full OS zip from Codeworxx TWRP
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Currently running crDroid 3.8.8 (32-bit Android N) with encryption activated. Looking to jump to 64-bit Android O with encryption activated while maintaining the option to revert to my current setup should the need arise.
Here's how I currently understand the process, please correct/clarify where necessary:
1. Create a backup via current TWRP.
2. Save backup from step 1 to another media (i.e. desktop/cloud/etc.)
3. Update to 64-bit TWRP supporting encryption. Only working variant is GtrCraft twrp-3.2.1-1-potter_crypto.img: https://forum.xda-developers.com/showpost.php?p=75306024&postcount=76
4. Copy ROM and gapps zip to device
5. Wipe cache, system, & data
6. Flash ROM/gapps
7. Encrypt device
Questions:
1. Is the above accurate? If so, does this also apply to selinux enforcing ROMs?
2. Does the 64-bit TWRP change the partitioning of the device? If not, do I need to do step 2 above?
3. Does switching to a Treble variant change the answers to Questions 1-3?
Thanks for the help.
I'd advise you to stay on nougat roms for now, as oreo roms create problems when returning to fastboot stock, and make the switchafter Official Oreo comes out. If you really want to, backup your efs in twrp, and persist as a .img file by following this post.
1. Yes and yes
2.No. Save the backup somewhere else to be safe.
3. No, but I don't think encryption will work.
Appreciate the feedback.
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.
If you afraid to flash qpst rom, here a method which will update your baseband/bootloader without qpst tool.
1) flash vendor to factory ( if you already flashed factory to vendor )
2) flash zui 3.5.389 full ota which has firmware included ( not the deodexed one by hendibudi )
Link :https://drive.google.com/file/d/1knkZxUyLNZO7uS8u_CK7j4j5-UqqGs5l/view (don't reboot
3) flash hendibudi's twrp for zui and reboot to rom
( The step 2 will lock your bootloader/ update your firmware/ bootloader. So we need to unlock bootloader again. To avoid wiping of internal storage we use twrp recovery which will only wipe /data
4)unlock your bootloader by following this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/how-bootloader-zuk-z2-pro-t3415392
( You can use your old unlock image )
5) clean flash any nontreble rom( needed)
Reboot to rom.
6)Reboot to recovery, flash factory to vendor zip.
( Don't reboot )
7) install latest twrp from twrpbuilder.org for our device ( install--image -- select -- recovery-swipe to flash )
8) reboot to recovery
9) clean flash your fav 4.4. kernel ROMs.
Note:
I am not tested new twrp by twrpbuilder.org instead of hendibudi twrp at step 3.
If it doesn't encrypt internal storage, there is no need of step 5&7
I followed this and worked. Don't miss any steps
I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk
sandruman said:
I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk
Click to expand...
Click to collapse
You can request unlock .img again
The way I got it working was by
1. Flashing deodexed TWRP flashable ZUI 4.0.233 rom and then set it up along with magisk.
2. Flashed factory2vendor.zip
3. Flashed TWRP by z2_plus_treble-TWRP-3.2.2_kubersharma_v2.img available in his thread.
4. Clean Flashed AEX 5.8
5. After setup again in TWRP clean flashed a Beta version of AEX v6.0
6. Again after that clean flashed the Official version of AEX v6.0.
You can skip step 4 & 5. I followed those steps to avoid any Blue Screen issue recently reported by some users. I didn't face any Bootloader problem.
*Remember to use Kubersharma TWRP in step 3. I don't know why, but Treble TWRP compiled by Davide is not reading internal storage when flashed after ZUI deodexed.
*And I am not responsible for anything that happens during your adventures.
ShaktiSW said:
The way I got it working was by
1. Flashing deodexed TWRP flashable ZUI 4.0.233 rom and then set it up along with magisk.
2. Flashed factory2vendor.zip
3. Flashed TWRP by z2_plus_treble-TWRP-3.2.2_kubersharma_v2.img available in his thread.
4. Clean Flashed AEX 5.8
5. After setup again in TWRP clean flashed a Beta version of AEX v6.0
6. Again after that clean flashed the Official version of AEX v6.0.
You can skip step 4 & 5. I followed those steps to avoid any Blue Screen issue recently reported by some users. I didn't face any Bootloader problem.
*Remember to use Kubersharma TWRP in step 3. I don't know why, but Treble TWRP compiled by Davide is not reading internal storage when flashed after ZUI deodexed.
*And I am not responsible for anything that happens during your adventures.
Click to expand...
Click to collapse
Didn't you every flashed a 3.1+ zui via qpst before?
Because as far as i know the deodexed zui 4.0. 233 doesn't updates the bootloader
satyen_ said:
Didn't you every flashed a 3.1+ zui via qpst before?
Because as far as i know the deodexed zui 4.0. 233 doesn't updates the bootloader
Click to expand...
Click to collapse
I never needed to. And AEX 6.0 run pretty much smooth without blue screen issue. I just followed the above mentioned procedures.
Deleted.
senthamizhan said:
If you afraid to flash qpst rom, here a method which will update your baseband/bootloader without qpst tool.
1) flash vendor to factory ( if you already flashed factory to vendor )
2) flash zui 3.5.389 full ota which has firmware included ( not the deodexed one by hendibudi )
Link :https://drive.google.com/file/d/1knkZxUyLNZO7uS8u_CK7j4j5-UqqGs5l/view (don't reboot
3) flash hendibudi's twrp for zui and reboot to rom
( The step 2 will lock your bootloader/ update your firmware/ bootloader. So we need to unlock bootloader again. To avoid wiping of internal storage we use twrp recovery which will only wipe /data
4)unlock your bootloader by following this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/how-bootloader-zuk-z2-pro-t3415392
( You can use your old unlock image )
5) clean flash any nontreble rom( needed)
Reboot to rom.
6)Reboot to recovery, flash factory to vendor zip.
( Don't reboot )
7) install latest twrp from twrpbuilder.org for our device ( install--image -- select -- recovery-swipe to flash )
8) reboot to recovery
9) clean flash your fav 4.4. kernel ROMs.
Note:
I am not tested new twrp by twrpbuilder.org instead of hendibudi twrp at step 3.
If it doesn't encrypt internal storage, there is no need of step 5&7
I followed this and worked. Don't miss any steps
Click to expand...
Click to collapse
First of all, kudos for the great job! I'm anxious to test it.
But please forgive my stupidity.
Which hendibudi TWRP build you mean? I could only find a 3.2.1 but I'm not sure it can handle Treble.
renatohm said:
First of all, kudos for the great job! I'm anxious to test it.
But please forgive my stupidity.
Which hendibudi TWRP build you mean? I could only find a 3.2.1 but I'm not sure it can handle Treble.
Click to expand...
Click to collapse
Yes it doest support treble partition. But we need that twtp to avoid internal storage encryption problem.
So we can flash any non treble ROM, reboot yo ROM, reboot to recovery , flash factory to vendor zip, flash latest treble twrp, reboot to twrp then flash 4.4 ROMs.
My entire point is flashing vendor to factory and and full ota 3.5.389 zip will update bootloader, firmware ( it will work just as qfil flash )
My guide can be followed if someone having trouble with qfil . ( tested by at least 2 people )
Other steps are just to avoid encryption and internal storage wipe problems that may come after flash.
Hope it'll remove doubts
senthamizhan said:
Yes it doest support treble partition. But we need that twtp to avoid internal storage encryption problem.
So we can flash any non treble ROM, reboot yo ROM, reboot to recovery , flash factory to vendor zip, flash latest treble twrp, reboot to twrp then flash 4.4 ROMs.
My entire point is flashing vendor to factory and and full ota 3.5.389 zip will update bootloader, firmware ( it will work just as qfil flash )
My guide can be followed if someone having trouble with qfil . ( tested by at least 2 people )
Other steps are just to avoid encryption and internal storage wipe problems that may come after flash.
Hope it'll remove doubts
Click to expand...
Click to collapse
Thanks for your kindness!
Alright then, I'm next on line to test! I'll just backup (it sucks...) then I'll flash!
Out of luck, flashing via Mi Tool now...
renatohm said:
Out of luck, flashing via Mi Tool now...
Click to expand...
Click to collapse
What happened
senthamizhan said:
What happened
Click to expand...
Click to collapse
Blue screen. I'm stuck on Qfil too, it also resulted in blue screen. Starting from scratch.
renatohm said:
Blue screen. I'm stuck on Qfil too, it also resulted in blue screen. Starting from scratch.
Click to expand...
Click to collapse
There is baseband zip file of 3.5 zui (in guides and discussion section) you can flash that if you don't want to go through the long process of Qfil, I flash that zip and i am able to use 4.4 kernels
This will not lock your bootloader and can be flashed by official TWRP
satyen_ said:
There is baseband zip file of 3.5 zui (in guides and discussion section) you can flash that if you don't want to go through the long process of Qfil, I flash that zip and i am able to use 4.4 kernels
This will not lock your bootloader and can be flashed by official TWRP
Click to expand...
Click to collapse
Yes, that's the reason I tried this in the first place, but it didn't work for me.
Qfil did work, and I'm now on Bootleggers.
sandruman said:
I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk
Click to expand...
Click to collapse
Bro,if u had used your email address try checking in your inbox again for image, just search bootloader .
I've changed my mail with a Gmail one and it work. Now I've my unl files
Inviato dal mio Z2 Plus utilizzando Tapatalk
flash vendor to factory ( if you already flashed factory to vendor ) "
explain this line
In these forums there was a file for updating baseband to 1.70. I flashed it promptly and my phone also went into soft brick. Because accidentally my bootloader got locked and got revised also. By using certain key combinations I succeeded in again unlocking my bootloader without formatting my inner storage . now I am able to flash 4.4 ROMs. Without going through all the hassles of backup, formatting and again flashing twrp.
Your guide didn't work for me (but step 2 using your file didn't lock my bootloader). It would be nice if you gave direct link to items in your steps (for i.e factory to vendor.zip, twrp...). I guess I'll try using qfil unless someone has some tips... BTW I can't find a good qfil guide for 4.4 kernel roms, could anyone give me a link to a helpful thread for it if I can't get it working using this method?