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!
Related
Hello,
i flash os 3.0 and now I want to flash cm 13 because there is no audio tune or fx available in 3.0 , so when i try to flash cm13 zip it gave error 7 , please help
thank you in advance
Hello, if you are on OOS3 you need to flash old firmare (you'll find this in CM13 seraph's thread) and a OOS 2.x.x and cm13 compatible recovery
Reboot in twrp.
Backup everything and do a full whipe.
Flash oos 2.x
Put the phone in fastboot mode and flash twrp 3.0.0.x. (using fastboot commands).
Flash cm13 and gapps and supersu.
Reboot.
Done.
Verstuurd vanaf mijn ONE A2003 met Tapatalk
In the future, ignore these quadruple post like this one which has been answered 517 times, all in new post. Geese, doesn't anyone read more than the first three posts in each sub section nowadays ?
Word pooping seems to be a thing ?
I'm already try flash trough TWRP over leaked official nougat version.
Works fine just dalvik and cache wipe after flash.
this is international ver. (not like hydrogen Eng/Chinese only)
original post from official forum
https://forums.oneplus.net/threads/oxygenos-open-beta-1-n-for-oneplus-3t.482846/
If i were to flash over my stock OS, what do I need to delete (without losing pictures etc). I keep forgetting..
I have read that TWRP has some errors when flashing, not sure what this was.
vincedyne said:
If i were to flash over my stock OS, what do I need to delete (without losing pictures etc). I keep forgetting..
I have read that TWRP has some errors when flashing, not sure what this was.
Click to expand...
Click to collapse
Hi
You can try side-load, but you need backup for sure.
my device is root and bootloader is open and I have already Nougat beta ver. before there so my upgrade was quick and all files and settings remains.
hampik said:
Hi
You can try side-load, but you need backup for sure.
my device is root and bootloader is open and I have already Nougat beta ver. before there so my upgrade was quick and all files and settings remains.
Click to expand...
Click to collapse
Ahh. I'll look into this, thanks!
hampik said:
Hi
You can try side-load, but you need backup for sure.
my device is root and bootloader is open and I have already Nougat beta ver. before there so my upgrade was quick and all files and settings remains.
Click to expand...
Click to collapse
So you just flashed the zip in TWRP and SuperSU afterwards? Or did it take additional steps?
bmwbasti said:
So you just flashed the zip in TWRP and SuperSU aftwerwards? Or did it take additional steps?
Click to expand...
Click to collapse
No additional steps. Flash the zip, supersu and wipe cache and everything is working fine.
I'll give it a shot eventhough i'm still on 3.5.4 and not the leaked beta.
I'm guessing as this will have the original boot.img (kernel), as no custom Nougat kernels are yet built (have to wait on the source code) that it will once flashed Encrypt the phone again? Thus the need for the pin/password for twrp?
No point in flashing Open Beta; th official stable OTA is coming tonight too.
https://twitter.com/getpeid/status/815171834345885696
Deleted
So seems there are soon to be two channels beta and stable coming. Great stuff!
Are the sources for ROM and kernel up yet?
Can we side load this over the top of the leaked nougat ROM ?
Moderator Information,
Thread closed, we do not need multiple threads for this.
Hi everyone,
I have a little problem with fingerprint with these 2 roms.
Normally I could add 5 fingers but I can only 3 max. If I try to configure the last 2, all my fingerprints dont work at all.
Moreover I can't delete fingeprints. When I try, they come back.
That is an issue which not occur with 6.0 custom roms.
Someone know how to fx it?
Thanks.
I'd suggest flashing the stock nougat 93-11 or 93-14 firmware (e.g. from the guides section) to resolve your fingerprint issues. Once that's done, future installs of lineage and RR should have fingerprint support for more than 3 fingers.
Thanks for replying.
I have xt1642. Is there a stock firmware Nougat for this device? I didnt find it
Nicozyp said:
Thanks for replying.
I have xt1642. Is there a stock firmware Nougat for this device? I didnt find it
Click to expand...
Click to collapse
I've got an XT1642 (UK - retGB, EMEA baseband) and updated to Nougat 93-11 using the stock files on here okay (now running Lineage with 4 FPs set).
The ROM I used to upgrade was the one linked here: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-install-official-december-nougat-t3518262 This will bring you up to the official 93-11 update via installing from stock recovery - you need Marshmallow build 139-63/64 however.
However, you may like to try either of these guides as well: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
As long as you can successfully install a Nougat stock ROM onto your device, the updates should mean your fingerprint sensor works properly in the custom ROMs. Bear in mind that updating to Nougat may wipe your data and cause you to lose TWRP/root until you re-install them.
Last question: can I wipe system and internal storage before installing ressurection?
Nicozyp said:
Last question: can I wipe system and internal storage before installing ressurection?
Click to expand...
Click to collapse
Once you've installed Nougat (and I recommend installing TWRP too), if you wish to install Resurrection Remix, only wipe system, data, Dalvik and cache. Don't wipe internal storage, since that's where your ROM zip is stored!
Silesh's initial post on the RR version for Moto G4s has more information on this https://forum.xda-developers.com/moto-g4-plus/development/rom-resurrection-remix-n-5-8-0-t3507275
Unable to flash stock recovery => "image not signed or corrupt"
Nicozyp said:
Unable to flash stock recovery => "image not signed or corrupt"
Click to expand...
Click to collapse
The image is flashed. Boot into recovery and you'll realize.
Nicozyp said:
Unable to flash stock recovery => "image not signed or corrupt"
Click to expand...
Click to collapse
Which file are you flashing? Does it end in OKAY after that error?
EDIT - zeomal is too quick for me
Indeed it's ok.
For the moment I upgrade MM, then gonna flash stock Nougat.
So problem solved.
I've flashed RR and configured fingerprint ==> it works fine
Thanks for ur help and advices
fingerprint option is not displayed in my zuk z1
Hey I have installed official lineage-os on my zuk z1 handset but still I can't find fingerprint option in my zuk
What to do help me
Hey I am new to OnePlus 5 and currently on Official Open Beta 5 based on Oreo, encrypted by default, unlocked bootloader but not rooted.
I want to install custom rom based on Nougat, specifically xXx 4.8 rom 4.5.15 based on Nougat.
Can somebody please guide me step by step, how can I proceed, which recovery shall I use? And etc etc.
My firmware is updated to Oreo so how can I revert? if that matters and needed.
Shall I need to downgrade to nougat before proceeding?
Thanks & Cheers,
Sent from my ONEPLUS A5000 using Tapatalk
I can't do step by step but since nobody else has answered I will try to point you in the right direction . There are step by step flashing guides on XDA.
You want to install the latest version of Codeworks TWRP. After you install TWRP you will need to format the data on your phone because you are encrypted and moving from Oreo to Nougat. You can do this in the wipe data tab in TWRP but remember you need to format your data,not wipe. This will erase everything on your phone except TWRP. If you connect your phone to a computer it will be recognized like a memory stick and you can just copy and paste your ROM zip onto your phone. Then you can flash your ROM zip with TWRP.
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?