Related
i had to find out if it will work followed this guide (https://www.xda-developers.com/flash-generic-system-image-project-treble-device) and it booted will try other project treble roms and report back here also eveything worked i didnt have a apk crash or force close the little time i used it also the camera apk worked great not as good as stock but not as bad as rros:laugh::laugh::laugh::laugh:
You flashed RR ph Treble or Lineage 15.1. How's the battery ? SOT? Does it support VOLTE?
Please Report
Honor 7x project treble
I flashed the Resurrection Remix phh-Treble and the LineageOS 15.1 phh-Treble will try the third and report back so far the battery life is normal haven't notice any abnormal drain and I can't confirm about the volte
dcraffam said:
i had to find out if it will work followed this guide (https://www.xda-developers.com/flash-generic-system-image-project-treble-device) and it booted will try other project treble roms and report back here also eveything worked i didnt have a apk crash or force close the little time i used it also the camera apk worked great not as good as stock but not as bad as rros:laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
Hi Dude, After seeing your message, I tried this on the Honor 7X BND AL10 with EMUI 8 (Manually updated) with the Lineage OS (ARM 64 A-ONLY DEVICE) using the fastboot method. I wiped everything including system and I tried with both stock recovery installed and Twrp recovery installed and I also tried wiping using fastboot "fastboot -w" command. After that I installed using the fastboot and it went well and shows as finished but when I tried to boot, it just doesn't boot at all. I don't even see the lineage OS boot logo or something and eventually it goes to Huawei E recovery.
Could you please tell me which version exactly you flashed like aosp or RR or Lineage and Arm 64 A-only device or AB-device etc... A lot of people would really appreciate that.
Thetpcguy said:
Hi Dude, After seeing your message, I tried this on the Honor 7X BND AL10 with EMUI 8 (Manually updated) with the Lineage OS (ARM 64 A-ONLY DEVICE) using the fastboot method. I wiped everything including system and I tried with both stock recovery installed and Twrp recovery installed and I also tried wiping using fastboot "fastboot -w" command. After that I installed using the fastboot and it went well and shows as finished but when I tried to boot, it just doesn't boot at all. I don't even see the lineage OS boot logo or something and eventually it goes to Huawei E recovery.
Could you please tell me which version exactly you flashed like aosp or RR or Lineage and Arm 64 A-only device or AB-device etc... A lot of people would really appreciate that.
Click to expand...
Click to collapse
im going to write a quick lil guide on how im doing this for you right now
.................................................HOW TO FLASH GSI ON HONOR 7X ................................
DO SO AT OWN RISK I HOLD NO LIABLILTY
LETS BEGIN
1 you must be on stock emui 8 you must not have a pin set or device encrypted or frp lock and boot loader must be unlocked
2 download one of the 3 images listed here ( https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ )
( i personally only tried the ( LineageOS 15.1 phh-Treble Thread) and the (Resurrection Remix phh-Treble Thread) ((((((download the a only arm64image))))))))
3 download the 8.1 pico gaapps package for arm64 found here ( http://opengapps.org/ )
4 now you must download this twrp i know it works from the honor 7x oreo twrp ill upload it or you can download it from the thread
5 flash the twrp twrp_ramdisk_oreo_7-4-18.img linked in fastboot then reboot recovery (note) there will be two recoverys i upload one needed to flash the (gsi) and the other twrpimgmount_ramdisk.img is used to flash (((twrp backup)) to go back to stock oreo as the first one wont boot once the (gsi) is flashed only the mount twrp.img will the( twrp_ramdisk_oreo_7-4-18.img) will boot with the stock emui beta for some reason
6 create full backup with the twrp_ramdisk_oreo_7-4-18.img flashed in step 5 (personally i backed up everything i could )
7 factory reset data using twrp
8 flash the (gsi) image u downloaded in step 2 to system image .......... tap install change the type from zip to image select the (gsi) and flash to system image partion
9 flash pico gapps 8.1 arm 64 ( the rest are to big o flash ))
reboot device tada you booted a stock (gsi)
i couldnt upload recoveries but they can be found here https://forum.xda-developers.com/devdb/project/?id=25826#downloads
to go back to stock emui fastboot recovery flash the twrpimgmount.img factory reset and restore backup some partions will fail like bdm image,, data,, the partions that do uncheck those and restore backup agin flash stock recovery (RECOVERY_RAMDIS.img) and factory reset and you will be on emui8 agin
let me know if you have any problems im going t ry the phh treble aosp (gsi) now
Thetpcguy said:
Hi Dude, After seeing your message, I tried this on the Honor 7X BND AL10 with EMUI 8 (Manually updated) with the Lineage OS (ARM 64 A-ONLY DEVICE) using the fastboot method. I wiped everything including system and I tried with both stock recovery installed and Twrp recovery installed and I also tried wiping using fastboot "fastboot -w" command. After that I installed using the fastboot and it went well and shows as finished but when I tried to boot, it just doesn't boot at all. I don't even see the lineage OS boot logo or something and eventually it goes to Huawei E recovery.
Could you please tell me which version exactly you flashed like aosp or RR or Lineage and Arm 64 A-only device or AB-device etc... A lot of people would really appreciate that.
Click to expand...
Click to collapse
Try Flashing AOSP 8.1 ARM64 A-Only device system.img as its more updated than lineage or RROS.
Only, A-Only system.img should work on our device as per treble wiki on github.
TrainerRed said:
Try Flashing AOSP 8.1 ARM64 A-Only device system.img as its more updated than lineage or RROS.
Only, A-Only system.img should work on our device as per treble wiki on github.
Click to expand...
Click to collapse
Hi, I already flashed the AOSP version and it's booted up and working fine but I wanted the lineageOS as it has all the built in customisations. I just don't know why the lineage os didn't work as it was reported above the it's working. Maybe it's the variant thing? I have BND AL-10. I don't know Anyway thanks!!
Thetpcguy said:
Hi, I already flashed the AOSP version and it's booted up and working fine but I wanted the lineageOS as it has all the built in customisations. I just don't know why the lineage os didn't work as it was reported above the it's working. Maybe it's the variant thing? I have BND AL-10. I don't know Anyway thanks!!
Click to expand...
Click to collapse
How is the rom ? Is it can be used as daily driver ?
You still using AOSP or back to EMUI already ?
If you don't mind can you write review of Whats working and Whats Not?
TrainerRed said:
How is the rom ? Is it can be used as daily driver ?
You still using AOSP or back to EMUI already ?
If you don't mind can you write review of Whats working and Whats Not?
Click to expand...
Click to collapse
I installed it without any gapps or anything just bare minimum just to see if it boots or not. Here is what I observed during my short stay:laugh:
1. There is no VOLTE
2. The camera is working
3. I can't talk much about battery but there is no crazy drain as such so yeah
4. I don't know why you said it's the latest but the security patch is the same based on March, 2018 and it's android 8.1
5. The launcher seemed like the ice cream sandwich (Took me back to good ol days)
6. It felt smooth and unusual lag
I can't say much and suggest whether or not you can use it as a daily driver when I never used it as a daily driver. It's your call.
Hit the "Thanks" button if you really feel like thanking me:good:
dcraffam said:
.................................................HOW TO FLASH GSI ON HONOR 7X ................................
DO SO AT OWN RISK I HOLD NO LIABLILTY
LETS BEGIN
1 you must be on stock emui 8 you must not have a pin set or device encrypted or frp lock and boot loader must be unlocked
2 download one of the 3 images listed here ( https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ )
( i personally only tried the ( LineageOS 15.1 phh-Treble Thread) and the (Resurrection Remix phh-Treble Thread) ((((((download the a only arm64image))))))))
3 download the 8.1 pico gaapps package for arm64 found here ( http://opengapps.org/ )
4 now you must download this twrp i know it works from the honor 7x oreo twrp ill upload it or you can download it from the thread
5 flash the twrp twrp_ramdisk_oreo_7-4-18.img linked in fastboot then reboot recovery (note) there will be two recoverys i upload one needed to flash the (gsi) and the other twrpimgmount_ramdisk.img is used to flash (((twrp backup)) to go back to stock oreo as the first one wont boot once the (gsi) is flashed only the mount twrp.img will the( twrp_ramdisk_oreo_7-4-18.img) will boot with the stock emui beta for some reason
6 create full backup with the twrp_ramdisk_oreo_7-4-18.img flashed in step 5 (personally i backed up everything i could )
7 factory reset data using twrp
8 flash the (gsi) image u downloaded in step 2 to system image .......... tap install change the type from zip to image select the (gsi) and flash to system image partion
9 flash pico gapps 8.1 arm 64 ( the rest are to big o flash ))
reboot device tada you booted a stock (gsi)
i couldnt upload recoveries but they can be found here https://forum.xda-developers.com/devdb/project/?id=25826#downloads
to go back to stock emui fastboot recovery flash the twrpimgmount.img factory reset and restore backup some partions will fail like bdm image,, data,, the partions that do uncheck those and restore backup agin flash stock recovery (RECOVERY_RAMDIS.img) and factory reset and you will be on emui8 agin
let me know if you have any problems im going t ry the phh treble aosp (gsi) now
Click to expand...
Click to collapse
Thanks for your detailed steps you documented.
But I did much simpiler. (but i did not flash gapps- so that would need to add some steps)
1. starting from stock EmUI 8 with stock recovery
2. Reboot to recovery perform factory reset.
3. when reset is done, while still in recovery plug in usb to phone and pc
4. select reboot, When screen goes off press and hold volume down. You will boot to fastboot
5. fastboot flash system C:\Users\Mr\Downloads\system-arm64-aonly.img
(your path to file will be different, unless you are also user "mr")
To return to stock do same steps but point fastboot flash to the stock emui system.img
Huawei camera works?
Which will you think better? Aosp lineages rr?
Thx
I tried flashing treble and lineage from twrp but neither worked on my bnd-l24. After flashing it just boots to the fastboot screen.
eskimowarrior7 said:
I tried flashing treble and lineage from twrp but neither worked on my bnd-l24. After flashing it just boots to the fastboot screen.
Click to expand...
Click to collapse
I have flashed to L24-- PHH RRos. It worked ok, gave a verdor image miss-match error.
did you factory reset before booting,
mrmazak said:
I have flashed to L24-- PHH RRos. It worked ok, gave a verdor image miss-match error.
did you factory reset before booting,
Click to expand...
Click to collapse
Yes, even tried the process a few more times. No luck.
eskimowarrior7 said:
Yes, even tried the process a few more times. No luck.
Click to expand...
Click to collapse
each time I started with flash stock recovery, then did factory reset
then from recovery reboot directly to fastboot
and fastboot flash system
mrmazak said:
Thanks for your detailed steps you documented.
But I did much simpiler. (but i did not flash gapps- so that would need to add some steps)
1. starting from stock EmUI 8 with stock recovery
2. Reboot to recovery perform factory reset.
3. when reset is done, while still in recovery plug in usb to phone and pc
4. select reboot, When screen goes off press and hold volume down. You will boot to fastboot
5. fastboot flash system C:\Users\Mr\Downloads\system-arm64-aonly.img
(your path to file will be different, unless you are also user "mr")
To return to stock do same steps but point fastboot flash to the stock emui system.img
Click to expand...
Click to collapse
Hi, Could you tell me which model and variant of Honor 7x you are using. I tried this on BND AL10 and it doesn't boot with all the stuff above. However, I could boot into AOSP GSI.
For BND AL10 users, Only the AOSP GSI is working but both the RR and the Lineage are not working. I tried all three with same method.
1. Wiped/ Factory reset
2. Installed using "fastboot flash system system.img"
I posted this message because I wasted a lot of time & data LOL so maybe this would be helpful to others. However, if somehow you manage to do it on AL10, please post it here.
Thetpcguy said:
Hi, Could you tell me which model and variant of Honor 7x you are using. I tried this on BND AL10 and it doesn't boot with all the stuff above. However, I could boot into AOSP GSI.
Click to expand...
Click to collapse
I'm using the L24
Thetpcguy said:
For BND AL10 users, Only the AOSP GSI is working but both the RR and the Lineage are not working. I tried all three with same method.
1. Wiped/ Factory reset
2. Installed using "fastboot flash system system.img"
I posted this message because I wasted a lot of time & data LOL so maybe this would be helpful to others. However, if somehow you manage to do it on AL10, please post it here.
Click to expand...
Click to collapse
Any updates if I can use it as my daily driver?
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?
What are the correct steps to upgrade from an oreo custom ROM to PIE custom ROM?
Didn't flash for some time and was wondering if things are changed since we now have treble en I read something about vendor images etc( I remembered them from my Nexus 5X).
What is the minimum required firmware for PIE?
Do I need to flash OOS first?
I know a clean flash is required, so my internal must be backed up.
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
casper_leeflang said:
What are the correct steps to upgrade from an oreo custom ROM to PIE custom ROM?
Didn't flash for some time and was wondering if things are changed since we now have treble en I read something about vendor images etc( I remembered them from my Nexus 5X).
What is the minimum required firmware for PIE?
Do I need to flash OOS first?
I know a clean flash is required, so my internal must be backed up.
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
Click to expand...
Click to collapse
The question is which rom do you want to install? A rom that includes everything like before treble or a generic system image that can only be used if you have specific partitions(treble)?
If it's the first one, just have a look at the rom threads and the instructions there.
You won't find gsi roms here cause they are device independent
strongst said:
The question is which rom do you want to install? A rom that includes everything like before treble or a generic system image that can only be used if you have specific partitions(treble)?
If it's the first one, just have a look at the rom threads and the instructions there.
You won't find gsi roms here cause they are device independent
Click to expand...
Click to collapse
Just a ROM that includes everything....thought msm xtended or AOSP Extended. In the first, only the recommended firmware is mentioned. In the last, it's just someone that cooks the ROM from source, but does not maintain it, there is nothing mentioned how to flash the ROM.
But as far as I understand now is:
Backup everything (including internal)
Flash PIE compatable Recovery
Flash latest firmware
Wipe system, data, cache
Format data
Install ROM + gapps
Nothing really new compared to upgrading another android version
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
casper_leeflang said:
Just a ROM that includes everything....thought msm xtended or AOSP Extended. In the first, only the recommended firmware is mentioned. In the last, it's just someone that cooks the ROM from source, but does not maintain it, there is nothing mentioned how to flash the ROM.
But as far as I understand now is:
Backup everything (including internal)
Flash PIE compatable Recovery
Flash latest firmware
Wipe system, data, cache
Format data
Install ROM + gapps
Nothing really new compared to upgrading another android version
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
Click to expand...
Click to collapse
You need to flash at first the firmware, then the new twrp, cause the new twrp checks if the firmware is up to date.
casper_leeflang said:
What are the correct steps to upgrade from an oreo custom ROM to PIE custom ROM?
Didn't flash for some time and was wondering if things are changed since we now have treble en I read something about vendor images etc( I remembered them from my Nexus 5X).
What is the minimum required firmware for PIE?
Do I need to flash OOS first?
I know a clean flash is required, so my internal must be backed up.
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
Click to expand...
Click to collapse
You probably don't have the Vendor partition yet so you need to create it. There's no getting around it.
Flash full 5.1.4 OOS zip. (You will lose TWRP)
Boot into OS and OTA to 9.0.4, or flash full zip manually
Fastboot flash latest codeworkx TWRP
Clean Install Custom ROM etc.
Done.
Dirk said:
You probably don't have the Vendor partition yet so you need to create it. There's no getting around it.
Flash full 5.1.4 OOS zip. (You will lose TWRP)
Boot into OS and OTA to 9.0.4, or flash full zip manually
Fastboot flash latest codeworkx TWRP
Clean Install Custom ROM etc.
Done.
Click to expand...
Click to collapse
So flashing only firmware + modem isn't going to create all partitions I need? First flashing OOS is the only way to go?
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
casper_leeflang said:
So flashing only firmware + modem isn't going to create all partitions I need? First flashing OOS is the only way to go?
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
Click to expand...
Click to collapse
Do what I suggest here https://forum.xda-developers.com/oneplus-5/help/upgrading-custom-oreo-to-pie-t3913224/post79161335 and tell if it's working or not. If not, give detailed steps what you flashed in which order.
casper_leeflang said:
So flashing only firmware + modem isn't going to create all partitions I need? First flashing OOS is the only way to go?
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
Click to expand...
Click to collapse
No. Flashing Firmware is not going to get the job done. 5.1.4 is mandatory to set up the Vendor partition and then you should be offered 9.0.4 via OTA.
Dirk said:
No. Flashing Firmware is not going to get the job done. 5.1.4 is mandatory to set up the Vendor partition and then you should be offered 9.0.4 via OTA.
Click to expand...
Click to collapse
He wants to install a custom rom not 9.0.4
strongst said:
He wants to install a custom rom not 9.0.4
Click to expand...
Click to collapse
So if I understand correctly, coming from custom oreo ROM to custom pie ROM, I only have to flash new firmware, flash pie recoveryf, ormat everything and start flashing ROM en gapps.
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
casper_leeflang said:
So if I understand correctly, coming from custom oreo ROM to custom pie ROM, I only have to flash new firmware, flash pie recoveryf, ormat everything and start flashing ROM en gapps.
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
Click to expand...
Click to collapse
Exactly!
strongst said:
Exactly!
Click to expand...
Click to collapse
I'm in the same boat, got super lazy for a while and busy with work so I've neglected mah phone. But it is time to update!
Thanks all for the helpful info.
casper_leeflang said:
So if I understand correctly, coming from custom oreo ROM to custom pie ROM, I only have to flash new firmware, flash pie recoveryf, ormat everything and start flashing ROM en gapps.
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
Click to expand...
Click to collapse
Do you have the Vendor partition? If not you do not understand correctly.
Regardless of whether your aim is to be on OOS or a Custom ROM, the most reliable way to create the vendor partition and have everything ready for a seamless Pie transistion is to follow the steps i already outlined.
Once you are on OOS 9.0.4 it's easy to fastboot flash the latest TWRP and install a Pie ROM with it.
If you have already set up the Vendor partition life is easier still.
Dirk said:
You probably don't have the Vendor partition yet so you need to create it. There's no getting around it.
1. Flash full 5.1.4 OOS zip. (You will lose TWRP)
2. Boot into OS and OTA to 9.0.4, or flash full zip manually
3. Fastboot flash latest codeworkx TWRP
4. Clean Install Custom ROM etc.
Done.
Click to expand...
Click to collapse
This is how it's done, truly. I followed this path generally an upgraded my phone yesterday.
To expand upon this a bit, let me give a few more links.
If you wish to keep your files, music & photos on your phone, disable any and all lock screen and security items in the system settings.
Next, you will need to first do your backup of applications using titanium backup.
You should also to do a full TWRP backup in case something goes sideways. Copy the TWRP to your computer just in case.
Get one of the Oxygen OS ROMs from this link:
https://forum.xda-developers.com/oneplus-5/how-to/index-oneplus-5-cheeseburger-t3810283/
Specifically, the Oreo 8.1 complete ROM from here: https://forum.xda-developers.com/showpost.php?p=76943616&postcount=5
OOS 5.1.4 will work. Stick with that exclusively. (From: https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265 : "OxygenOS 5.1.4 creates the /vendor partition which is needed by OxygenOS releases after OxygenOS 5.1.4 .")
Transfer that ROM to your internal SD card, maybe put it in a custom folder which says "ROMs".
Do a full wipe of your existing ROM installation: Data, cache, dalvik, & system.
Install the OOS ROM. (This will also over-write your current TWRP recovery.) Reboot when done.
Go through the basic set up steps, connect to Wi-Fi, and let it download the current OOS 9 [Android Pie] ROM. Reboot and let it do the upgrade.
After it updates it will reboot. Get the new OS minimally set up and running, then shut down.
Reboot the phone into fastboot / bootloader mode and connect to your computer.
Acquire TWRP 3.3 or later from Codeworkx here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
…or from BluSpark here:
https://forum.xda-developers.com/oneplus-5/development/kernel-t3651933
specifically: https://github.com/engstk/android_device_oneplus_cheeseburger/releases
Flash this recovery onto the phone.
Restart into this recovery. Acquire the ROM of your choice and place it into your ROMs folder.
Again wipe out the system, data, cache and dalvik partitions. Do not wipe out the vendor partition! You may brick the phone if you do that.
Install the ROM of your choice, plus any add-ons (magisk, custom kernel, etc.) and reboot.
Enjoy.
That should do it! That's what I did, and it works. :highfive:
CaptShaft said:
OOS 5.1.4 or 5.1.7, anything there will work.
...
Go through the basic set up steps, connect to Wi-Fi, and let it download the current OOS 9 [Android Pie] ROM. Reboot and let it do the upgrade. In the process of this upgrade to OOS 9, it will automatically generate the new vendor partition required as part of Android Treble. It will also put on the latest firmware.
...
Click to expand...
Click to collapse
Just in case somebody follow this, there are some wrong statements which can lead to issues.
Not in general can you flash either 5.1.4 or 5.1.7. If you never flashed 5.1.4, you can't flash 5.1.7, the update 5.1.4 is a prerequisite for 5.1.7,see below.
And no, OOS 9 android pie won't create the vendor partition, that is done by 5.1.4.
strongst said:
Just in case somebody follow this, there are some wrong statements which can lead to issues.
Not in general can you flash either 5.1.4 or 5.1.7. If you never flashed 5.1.4, you can't flash 5.1.7, the update 5.1.4 is a prerequisite for 5.1.7,see below.
And no, OOS 9 android pie won't create the vendor partition, that is done by 5.1.4.
Click to expand...
Click to collapse
I've edited my writeup to reflect these comments. Thanks!
my phone was running resurrection remix 7.1.2 with no issues i thinked of installing note 7 ported rom on my phone my phone has TWRP 2.8.7.0 installed with aroma support and my phone varriant is LTEXX i downloaded MAGMA NX and flashed it without any issue but after reboot it got in bootloop even it wont display boot logo i tried again wipping dalvik cache but still it wont boot up then i flashed phantom kernal and flshed magma again but no use, i also tried Note 7 port by Dark Lord having builtin kernel in rom it was also Aroma Supported it also installed without any error but after reboot from twrp it stuck in bootloop, kindly help me what can be the issue? how can this be solved
Usual reason .
User fails to read Op and fails to read the roms FAQS.
Especially the one regarding bootloop.
I Do Read Faqs & Requirement+ Tutorial
JJEgan said:
Usual reason .
User fails to read Op and fails to read the roms FAQS.
Especially the one regarding bootloop.
Click to expand...
Click to collapse
i always read faqs, requirments etc before flashing any rom, i downloaded rom which was for my phone and also flashed kernel given by developer of that rom but it stills fails to boot up after succesfull aroma installation i used twrp 2.8.7.0, i also followed tutorials on youtube which also failed.
Ripee & Lord Eko seniors members of xda told that i have a odd device when i was trying to flash twrp 3.0 it also wont boot up after flashing they said by device bootloader is stuck with LP bootloader and only way to flash newer android version is that you will have to flash modified version of twrp 3 by Ripee senior xda member which will only be able to flash Ressurection Remix OS 7.1.2 but will not be able to install or use newer version than Ressurection Remix.
then i thinked of installing MAGMA NX so i flashed twrp 2.8.7.0 from official twrp website as only this version supports aroma installation and was also suggested in tutorial but all what i got is after installation boot up fails and keep restarting.
Thanks for not posting that in OP.
kindly guide if i am doing wrong
JJEgan said:
Thanks for not posting that in OP.
Click to expand...
Click to collapse
i am not blaming developers or xda members i made a request to get help, kindly guide if i am doing wrong as i am not a developer but a normal user
That information in your original post was 100% missing is all i am saying .
help can only be given on the information provided .
<<which will only be able to flash Ressurection Remix OS 7.1.2 but will not be able to install or use newer version than Ressurection Remix.>>
Suggest you stick with that one or stock.
Alternative work through Magna faqs and instructions .
Even ask in the roms thread with full details .
etc etc
.** Keep current kernel option supported (Be sure Kernel installed before ROM installation)
After booting up in settings wizard, Be sure uncheck diagnostic data
FAQ 18
JJEgan said:
That information in your original post was 100% missing is all i am saying .
help can only be given on the information provided .
<<which will only be able to flash Ressurection Remix OS 7.1.2 but will not be able to install or use newer version than Ressurection Remix.>>
Suggest you stick with that one or stock.
Alternative work through Magna faqs and instructions .
Even ask in the roms thread with full details .
etc etc
.** Keep current kernel option supported (Be sure Kernel installed before ROM installation)
After booting up in settings wizard, Be sure uncheck diagnostic data
FAQ 18
Click to expand...
Click to collapse
1. Device Model (e.g. N900S)
Ans. SM-N9005
2. Bootloader and Baseband (whole code or last 3 characters: N9005XXSGBQA1 or QA1)
Ans. Bootloader: N9005XXSGBQD1
Baseband: N9005XXUGPQB1
3. Your recovery version (e.g. TWRP 2.8.7.0, philz 6.48.4,...)
Ans. TWRP 2.8.7.0
4. Wipes done in recovery before flashing.
Ans. Yes Dalvik, system, data, cache
5. Your choices in aroma installer:
a. Device model chosen
Ans: Samsung Note 3 International (SM-N9005/9006)
b. Kernel choice (or preinstalled)
Ans. guguodas R5
c. CSC choice
Ans. KSA
d. Debloatable apps
Ans. Default
e. SystemUI
ANs. Note 8/S8 Themed+Status Bar Hidden Button+Center Clock
f. UDS
Ans. UDS Uninstall
g. White/Green Battery
ANs. Green Battery
h. Launcher Choice
Ans. Default
i. Extra options (4G, dual stereo and etc)
Ans. Yes Checked All
j. Camera choice
Ans: Galaxy N7 Camera
k. Sound MOD
Ans. Xtreme|Viper|Dolby
l. NTP address
Ans. Pakistan
m. Root option
Ans. Magisk
n. Busybox option
Ans. Install
o. Xposed option
Ans. Uninstall all xposed
p. Wipe in aroma
4. Any other zips flashed?
Ans. NO
5. Any other modifications done?
Ans. No
That's not Faq. 18.
After reading so many guides and going through ROM threads, I've been left confused on how to flash my 6T with different ROMs and the best way of doing it without bricking the device.
Currently I am on rooted OOS 10.3.4 running Cleanslate Kernel. (TWRP 3.4.0)
So can anybody help me with these questions for which I am UNABLE to find any answers.?
1. What Fastboot Rom should I flash on my device if I cant find 10.3.4 fastboot. Can I flash 10.3.3 and proceed? Also, can I flash fastboot roms via TWRP without the need of turning on my PC.
2. A lot of people are suggesting downgrading TWRP to 3.3.x. How do I downgrade it? By merely running the .img file in the fastboot mode and flashing the zip?
3. Does TWRP 3.3.x have that AB partition thing where we have to flash everything TWICE to get the roms on both the slots? Or just a single swipe to install would do?
1. Use the SourceForge Link on the Fastboot Thread, even 10.3.5 is there. If you want though you can use 10.3.3
2. Just run the 3.3.1-32 installer from 3.4.x. I removed 3.4.x from my LOS Guide as it caused so many problems. The installer for -32 works properly and will still install in both slots. No need to do the install "ramdisk method."
3. No matter which version you choose your phone will still have a A/B partitions. You can't (well shouldn't) have OOS and an AOSP rom on each. Both partitions need to have the same type of ROM. It can cause weird problems if they are different. This is why on the initial install you flash the ROM twice. When you update your ROM, you only flash it once.
My Installing Lineage Guide works for many other custom ROMs, you might look through it. There is also a Cliff Notes version in Post 2 if you want something a bit shorter.