Related
Hi Guys,
I have uploaded the latest Xperia Z1 firmwire (14.6.A.1.216). This is Customized India version of the firmware. Happy Flashing.
FTF: Stock Firmwire from Xperifirm
Google Drive:https://drive.google.com/file/d/0By3wU4_J-OtSc1AzX1VGVHBGaWM/view?usp=sharing
Mega Link:https://mega.nz/#!Zl5G2L7a!ApEVE_cnByb8d6mGrdkfHShuJG8fw-fJ0O_NCJQaLTc
PRE-Rooted Firmwire: Added, with Dual recovery and SuperSU V2.48. The Zip is signed
Google Drive:https://drive.google.com/file/d/0By3wU4_J-OtSTzZFNlBPanhBdTQ/view?usp=sharing
Mega Link:https://mega.nz/#!ZoI3kSZT!Ka2yNisE_vN2bcsTTNHxvkR5NzWQ--uuhTJcfnoA10M
credits:
Sony- obviously!!, for the awesome Xperia Z1 and this update
IaguCool -for Xperifirm
Androxyde & DoomLord-for Flashtool
zxz0O0-for PRF creator
Pre-Rooted Firmwire added!!
Google Drive links soon...
Procedure:
Full wipes
Flash preroot
Flash supersu
Flash xzdualrecovery
Or
Only wipes and flash prerooted zip
Enviado desde mi C6902 usando Tapatalk 2
@ismaelghr Only wipe and flash Pre-Rooted Firmwire
Is for c6903 to? Or is only to c6902?
Enviado do meu C6903 através de Tapatalk
@Botandroid Only C6902..
Good.
Needed help on flashing
hi. i am new to this flashing stuffs. i currently run on generic 4.4.2 rooted on my Z1. i am looking for Pre-rooted stock 14.6.A.1.216. can someone help me how to flash my mobile step-by-step?
Siddharth Mahendran said:
hi. i am new to this flashing stuffs. i currently run on generic 4.4.2 rooted on my Z1. i am looking for Pre-rooted stock 14.6.A.1.216. can someone help me how to flash my mobile step-by-step?
Click to expand...
Click to collapse
@Siddharth Mahendran You should have a Recovery installed on your phone before flashing a Pre-Rooted firmware...
Use Xperia [Nut]'s Dual recovery installer for Xperia Z1: http://nut.xperia-files.com/?ql=162303ad4b67ec4f7c00159b1de0e18807279c4a
If the Procedure hasn't changed(Becoz its been long since I used it), It should have .bat file or some kind of command line script. Have USB debugging and unknown sources enabled on your device. Connect your phone to ur PC and execute the bat file. It should search for the device and it will install the Dual Recovery.
Then, Copy the pre-rooted firmware that you downloaded from here into your phone. Reboot your phone, while booting the notification LED will light up, and then press Volume Down/Up button, based on the recovery you want. Then, wipe system, data, cache and dalvik cache using the option like wipe/format based on the recovery you are using. Then, Choose install->search for the Pre-rooted Firmware you copied,select it and Confirm installation. Once Completed, Reboot device.
Remember That, First boot will take a long time, be patient...
Backup all data before, trying anything on XDA!!!!
I am not responsible, if you do anything wrong or something went wrong in the Procedure!!!
Gladwin_Prince said:
@Siddharth Mahendran You should have a Recovery installed on your phone before flashing a Pre-Rooted firmware...
Use Xperia [Nut]'s Dual recovery installer for Xperia Z1: http://nut.xperia-files.com/?ql=162303ad4b67ec4f7c00159b1de0e18807279c4a
If the Procedure hasn't changed(Becoz its been long since I used it), It should have .bat file or some kind of command line script. Have USB debugging and unknown sources enabled on your device. Connect your phone to ur PC and execute the bat file. It should search for the device and it will install the Dual Recovery.
Then, Copy the pre-rooted firmware that you downloaded from here into your phone. Reboot your phone, while booting the notification LED will light up, and then press Volume Down/Up button, based on the recovery you want. Then, wipe system, data, cache and dalvik cache using the option like wipe/format based on the recovery you are using. Then, Choose install->search for the Pre-rooted Firmware you copied,select it and Confirm installation. Once Completed, Reboot device.
Remember That, First boot will take a long time, be patient...
Backup all data before, trying anything on XDA!!!!
I am not responsible, if you do anything wrong or something went wrong in the Procedure!!!
Click to expand...
Click to collapse
thanks. I will try this once the .zip file got downloaded
Gladwin_Prince said:
@Siddharth Mahendran You should have a Recovery installed on your phone before flashing a Pre-Rooted firmware...
Use Xperia [Nut]'s Dual recovery installer for Xperia Z1: http://nut.xperia-files.com/?ql=162303ad4b67ec4f7c00159b1de0e18807279c4a
If the Procedure hasn't changed(Becoz its been long since I used it), It should have .bat file or some kind of command line script. Have USB debugging and unknown sources enabled on your device. Connect your phone to ur PC and execute the bat file. It should search for the device and it will install the Dual Recovery.
Then, Copy the pre-rooted firmware that you downloaded from here into your phone. Reboot your phone, while booting the notification LED will light up, and then press Volume Down/Up button, based on the recovery you want. Then, wipe system, data, cache and dalvik cache using the option like wipe/format based on the recovery you are using. Then, Choose install->search for the Pre-rooted Firmware you copied,select it and Confirm installation. Once Completed, Reboot device.
Remember That, First boot will take a long time, be patient...
Backup all data before, trying anything on XDA!!!!
I am not responsible, if you do anything wrong or something went wrong in the Procedure!!!
Click to expand...
Click to collapse
@Gladwin_Prince Thanks bro. Changed to Android 5.1.1. I see no amazing features in lollipop.thats disappointing
gonna port needed apps
lol i softbrick my device!
I tried to flash stock ftf using flashtool but still no use!
restarts on booting! what to do now?
I mean which files i do include or exclude? and what to do when it ask to use fsc script found?
Nagesh_Noddy said:
lol i softbrick my device!
I tried to flash stock ftf using flashtool but still no use!
restarts on booting! what to do now?
I mean which files i do include or exclude? and what to do when it ask to use fsc script found?
Click to expand...
Click to collapse
Just use the latest Flashtool, it should solve all the problems with the fsc script... To recover your device from softbrick, don't exclude anything, make sure all wipes are checked and you are good to go. hope that helps.
Gladwin_Prince said:
Just use the latest Flashtool, it should solve all the problems with the fsc script... To recover your device from softbrick, don't exclude anything, make sure all wipes are checked and you are good to go. hope that helps.
Click to expand...
Click to collapse
I flashed .108 by flashtool with user-data.sin and exclude some items! rooted by rootkit! install nut recovery now again ready to flash pre-rooted .216!
tysm for firmware
Installed this and deodexed as well, xposed doesnt work. Any solutions?
Thanks.
timvonlee said:
Installed this and deodexed as well, xposed doesnt work. Any solutions?
Thanks.
Click to expand...
Click to collapse
Xposed works with .216 firmware. Running it myself.
Have you downloaded the correct 2 files for running xposed on lollipop?
motorazrv3 said:
Xposed works with .216 firmware. Running it myself.
Have you downloaded the correct 2 files for running xposed on lollipop?
Click to expand...
Click to collapse
Can you Give the link for correct xposed? i reverted back to 4.4.2 since xposed didnt work fo me
Siddharth Mahendran said:
Can you Give the link for correct xposed? i reverted back to 4.4.2 since xposed didnt work fo me
Click to expand...
Click to collapse
I think the system isn't getting mounted as rw, and since xposed installer writes to system, it is failing to install. Kindly tell me how to mount system as rw since even after deodexing it isn't getting mounted.
timvonlee said:
I think the system isn't getting mounted as rw, and since xposed installer writes to system, it is failing to install. Kindly tell me how to mount system as rw since even after deodexing it isn't getting mounted.
Click to expand...
Click to collapse
Sorry. idk about that.maybe senior members would help
Hi! can you update this with the the latest release 236?
Hi all.
I have the 935F International on it's way to me, delivering in the next day or so
By all accounts the 935F is already unlocked. To prepare, I have already downloaded Odin 3.11.1, CF's root file, TWRP twrp-3.0.2-2-hero2lte tar, and a custom ROM and bootloader/modem files.
I'm not a noob to flashing, just newish to Samsung.
What is the best way to start? Boot into stock, enable bootloader unlock on developer options, run Odin and flash TWRP, then CF's root file? Also, I want to run unencrypted - format data using advanced wipe 'yes' method?
The ROM states it sets root on installation. Do I then need to flash CF's root file?
Further, how are bootloader/modem tar files flashed? Is it as simple as selecting BL for bootloader, although I don't see anything for the modem??
Finally, what is the actual order of all this? I'm thinking: TWRP first, Format internal data second, CF root third, ROM flash from TWRP fourth, reboot to download mode from TWRP and then flash modem/bootloader last. Then reboot all together to set the phone up?
Thanks and any help is appreciated
1. Update to latest firmware
2. CF-Autoroot
3. TWRP
4. Flash no-verity-opt-encrypt.zip, wipe data.
5. Reboot recovery, mount system.
6. Wipe all except internal and external sd.
7. Flash your ROM
dynospectrum said:
1. Update to latest firmware
2. CF-Autoroot
3. TWRP
4. Flash no-verity-opt-encrypt.zip, wipe data.
5. Reboot recovery, mount system.
6. Wipe all except internal and external sd.
7. Flash your ROM
Click to expand...
Click to collapse
Thanks for the info :good:
When you say update to latest firmware this is Bootloader and Modem yes?
Steps 2 & 4 - just having done a little more research, are these outdated now?; as TWRP (latest) now fixes encryption and the ROM will inject (for a better term ) SuperSU when installing it? Or will this still need to be done irrespective of using the latest version of TWRP and ROM?
Cheers and thanks :good:
If you're not new to rooting and custom roms, pretty much all you need is to unlock OEM in Dev Options in Settings, Restart the device and hold Vol Down+Home+Power to get into Download Mode and press Up at the blue screen. Plug in your USB to your phone and run the tool on your PC.
Once Rooted, its business as usual. You don't need a guide to install TWRP, just install the Flashify app and let it do it for you, and then have no-verity-opt-encrypt.zip handy to flash. I know no-verity-opt-encrypt.zip is essential if you flash TWRP through ODIN, but not 100% sure if you should if you flashed TWRP through Flashify, I always flash no-verity-opt-encrypt.zip regardless so I unno.
Also if you find yourself in a semi-bricked situation where you can't figure out your problem, as long as you have Download Mode, you'll always have a way to get back to a working device. Samsung Smart Switch for Windows has an Emergency Mode that will revert your device back to Factory Conditions.
peteri8706 said:
Thanks for the info :good:
When you say update to latest firmware this is Bootloader and Modem yes?
Steps 2 & 4 - just having done a little more research, are these outdated now?; as TWRP (latest) now fixes encryption and the ROM will inject (for a better term ) SuperSU when installing it? Or will this still need to be done irrespective of using the latest version of TWRP and ROM?
Cheers and thanks :good:
Click to expand...
Click to collapse
I've been doing things this way since day 1 with no problems. My advice would be to do it the same way. I can assure you a solid install ;]
Yes, firmware is bootloader & modem. Great thread for this is here http://forum.xda-developers.com/s7-edge/how-to/official-stock-firmware-update-odin-t3335065
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app
SuperSUv2.82-EMUI5-noverity-Permissive.zip
from: https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
TWRP recovery
from: https://forum.xda-developers.com/p10-lite/development/beta-t3619496
Elemental V2
from: https://forum.xda-developers.com/p10-lite/development/rom-emui-5-1-huawei-p10-lite-dual-sim-t3733095
(unchanged for first screen, picked stock music and WAS-LX1 patch, unchanged for third screen)
Installed the above
Now I'm stuck in a bootloop(?)
It boots but after like 1 - 2 minutes it restarts itself
I tried let it restart itself a bunch of times and it just ends in Huawei's eRecovery
I only know the model for my phone: WAS-LX2 (no exact roms for LX2)
Hopefully someone can help <3
CheesyBen said:
SuperSUv2.82-EMUI5-noverity-Permissive.zip
from: https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
TWRP recovery
from: https://forum.xda-developers.com/p10-lite/development/beta-t3619496
Elemental V2
from: https://forum.xda-developers.com/p10-lite/development/rom-emui-5-1-huawei-p10-lite-dual-sim-t3733095
(unchanged for first screen, picked stock music and WAS-LX1 patch, unchanged for third screen)
Installed the above
Now I'm stuck in a bootloop(?)
It boots but after like 1 - 2 minutes it restarts itself
I tried let it restart itself a bunch of times and it just ends in Huawei's eRecovery
I only know the model for my phone: WAS-LX2 (no exact roms for LX2)
Hopefully someone can help <3
Click to expand...
Click to collapse
Elemental V2 already have preinstalled SuperSu. So if You try to root again your device will enter in bootloop. Those are parched stock roms and not compatibile with standard SuperSu or Magisk installers.
Regards
Alexxxx1 said:
Elemental V2 already have preinstalled SuperSu. So if You try to root again your device will enter in bootloop. Those are parched stock roms and not compatibile with standard SuperSu or Magisk installers.
Regards
Click to expand...
Click to collapse
I wiped data and did a factory reset and only installed the rom
Still does the same thing
CheesyBen said:
I wiped data and did a factory reset and only installed the rom
Still does the same thing
Click to expand...
Click to collapse
Than, u probably have Ext4 formated Data partition from some reason.... . You need to change from Ext4 in F2FS using Twrp..
Or use service rom to rollback to stock.
Edit. I ve just saw, dude....... use Twrp Elemental. You didnt followed basic instructions for flashing Elemental rom. You can not flash Elemental with other twrp.
All the best.
Alexxxx1 said:
Than, u probably have Ext4 formated Data partition from some reason.... . You need to change from Ext4 in F2FS using Twrp..
Or use service rom to rollback to stock.
Edit. I ve just saw, dude....... use Twrp Elemental. You didnt followed basic instructions for flashing Elemental rom. You can not flash Elemental with other twrp.
All the best.
Click to expand...
Click to collapse
I like did every combination I had at my disposal
I guess elemental v2 doesn't support lx2? I'll wait for v3 but it has been UPLOADING for like a week now
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?