Database Users

LG L5 philzmod error

hi guys
I installed (Kinguser) and root my phone via it , then I installed philz mod (philz v.6.0.img) using flash tools (rasher) to install new ROM .However, it doesn't work ,So I restored my old ROM and all files and my Device return as it was and No problems yet , then
when I was playing in the recovery (try all tasks) , I have press ( philz settings\rerootsystem(supersu)\yes), then tried to boot operating system (android), but the Device didn't boot it , when I run my Device it Automatically boot to recovery (philz) , I tried more than once , It always boot the recovery or didn't boot any thing (still show LG logo)
notes:
I have another same Device
my recovery version: cwm:v.6.0.4.8 \philz:v.6.27.5
I tried to restore Backup (from my another same Device),but didn't work​

hm,please say me what rom you installed (android version,romname,kernel),is your bootloader unlocked,etc!!!!

..
-CALIBAN666- said:
hm,please say me what rom you installed (android version,romname,kernel),is your bootloader unlocked,etc!!!!
Click to expand...
Click to collapse
ROM version: lollepop
kernel: (I don't think what was name, but it was for LG devise)
I don't know if my devise was unlocked bootloader, but before I install recovry I was unlooked bootloader and when I make backup file, the devise was unlooked bootloader(note:I make the backup from my another devise)
I don't think the problem in the ROM or the backup becuse the problem start when I press (reroot,,,,,)
I'm reedy for all athoer QQ
and that is my email:
[email protected]
And sry for printed mistakes

simply use the latest twrp2.8.6.0 recovery from aidasaidas75 than it should be fixed i think.
link to aidas thread below me,greeeeeeetz!!!!!
http://forum.xda-developers.com/opt...recovery-twrp-2-8-0-1-touch-recovery-t2877143

.
-CALIBAN666- said:
simply use the latest twrp2.8.6.0 recovery from aidasaidas75 than it should be fixed i think.
link to aidas thread below me,greeeeeeetz!!!!!
http://forum.xda-developers.com/opt...recovery-twrp-2-8-0-1-touch-recovery-t2877143
Click to expand...
Click to collapse
Ok, I download the file (trwp2.8.6.0.zip) and tried to install it via philz recovry (install zip/choose zip from strong sdcard /twrp.2.8.6.0-e612-aidasaidas75.zip/yes)
Then I get masseg (installation aborted)
Now, how I install twrp recovry??
Note:I tried download (twrp flshable.zip) and install it .and install complete then restart the recovry but nothing changed
wiating you

..
...

.
Guys
I need hellp :crying:​

AhMaD eLMoMaNi said:
Ok, I download the file (trwp2.8.6.0.zip) and tried to install it via philz recovry (install zip/choose zip from strong sdcard /twrp.2.8.6.0-e612-aidasaidas75.zip/yes)
Then I get masseg (installation aborted)
Now, how I install twrp recovry??
Note:I tried download (twrp flshable.zip) and install it .and install complete then restart the recovry but nothing changed
wiating you
Click to expand...
Click to collapse
I still wait for the solution, Please help me

try flash with latest cwm or with terminal emulator,in normal case it must work.

,
-CALIBAN666- said:
try flash with latest cwm or with terminal emulator,in normal case it must work.
Click to expand...
Click to collapse
that's hard for me , pleas tell me how i flash it useing terminal emulator when i cant open OS ?!!
is root Reason the problem ? because the problem start when I reroot the device using the recovery
when I reroot the device , when I restart it using recovery tell me [root access is missi] is the root necessary to operate OS ?
I tried press yes-apply root (/system/xbin,,,,,,ETC) and nothing changed
can you give me skype or facebook or any thing can we chat with it

[TUTORIAL] Easy way for UNLOCK Bootloader and flash TWRP 2.8.6.0 for MX4

All your actions with the phone is at your own risk. The authors are not liable. This is just your choice.
PLEASE read full instructions before you start.
RECOMMENDED ONLY FOR EXPERIENCED USERS.
This was tested ONLY on MEIZU MX4 and ONLY FIRMWARE 4.2.8.2A, ANY OTHER FIRMWARE/PHONE - YOU WILL RECEIVE BRICK PHONE.
(с)
ONLY FOR MEIZU MX4 AND ONLY FIRMWARE 4.2.8.2A. Don't use the that apk on Lollipop or your device will brick​
Hello everyone, i changed chinese apk for unlock bootloader, and replaced chinese recovery, on TWRP 2 8.6.0 recovery.
1. Download Flyme OS 4.2.8.2A stock firmware an official webpage Meizu
2. Flash it in stock recovery and select WIPE DATA
3. Get root permission
4. Download and install that APK - drive.google.com/open?id=0B_Gd_o_kBWgLNHFuZW5kMlFzV2s
5. Open that app, and provide root permission.
6. Press "Press to UNLOCK BootLoader" - and wait, you will see "Unlock Finished"
7. After, will be available recovery mode, and you press to "Enter Recovery Mode"
8. Your phone reboot and enters for normal recovery - TWRP 2.8.6.0.

Thanks for the great work!
At last we're getting closer to opening up our meizu phones.
Can the phone with this, unlocked bootloader flash "I" international roms from OTA?

How to relock?

ideosx5 said:
How to relock?
Click to expand...
Click to collapse
Reflash FLyme rom (with Flyme recovery, be carefull!)
Or flash stock uboot

Successfully upgraded MX4 "A" edition phone to "I" using following method:
Installed 4.2.8 "A" stock firmware.
1. Installed apk method unlock (this thread).
2. Downloaded 4.5.7 "I" firmware, extracted and created system.img using (linux):
$ sdat2img system.transfer.list system.new.dat system.img
for windows, see this guide from Meizufans.
3. Boot into fastboot mode (now unlocked) using "VOL -" + "POWER"
4. fastboot flash boot boot.img
WAIT
fastboot flash system system.img
WAIT
5.Reboot into recovery
6. Full wipe
7. Install super su
8. Reboot
VOILA - 4.5.7 "I"
Remember to block/deactivate system updates once system has booted for first time.

Is it possible for someone to upload recovery.img of TWRP please ? I'd like to try
---------- Post added at 10:16 AM ---------- Previous post was at 09:22 AM ----------
I got it, I'm fixing the splash screen dimensions ahah^^
---------- Post added at 11:03 AM ---------- Previous post was at 10:16 AM ----------
It was a little harder than I expected but it's here : http://www.mediafire.com/download/26b963db1k489db/new-recovery.img

Learnincurve said:
Successfully upgraded MX4 "A" edition phone to "I" using following method:
Installed 4.2.8 "A" stock firmware.
Click to expand...
Click to collapse
Good, but there is easy way download that rom, and install it for TWRP(select full wipe, include internal storage) - emmaus.pro/MX4_custom_roms/Flyme/4.5.7i_twrp.zip
and there all stock Flyme roms for twrp - emmaus.pro/?dir=MX4_custom_roms/Flyme
Author all rom "nikk3d" russian 4pda users - 4pda.ru/forum/index.php?showuser=2196261

And this method works even on newest firmware, let's say 4.5.6i downgraded to 4.2.8i via 4.0.4i? Or is a easy variant of previous method, patched uboot by meizu remains after 4.5.6i upgrade if i understand, no matter if you downgrate to Kitkat?

update for TWRP : http://www.mediafire.com/download/f6a65ccpgrfaopw/TWRPr5.img
Changelog :
I corrected "Select storage" position, corrected some shifts on the main screen

zaurikk said:
Good, but there is easy way download that rom, and install it for TWRP(select full wipe, include internal storage) - emmaus.pro/MX4_custom_roms/Flyme/4.5.7i_twrp.zip
and there all stock Flyme roms for twrp - emmaus.pro/?dir=MX4_custom_roms/Flyme
Author all rom "nikk3d" russian 4pda users - 4pda.ru/forum/index.php?showuser=2196261
Click to expand...
Click to collapse
I have an MX4 originally with Ubuntu touch, I tried to flash 4.5.7i from emmaus.pro.
It failed, updater binary error. I checked the recovery log and it says write error, no space left.
Does anybody have any clue?
Thanks,
Note: I already tried a wipe out (even internal storage). No issues with the cyanogenmod roms from emmaus.pro.

Is someone trying to make fom Meizu MX5?
Sent from my MX5 using Tapatalk

itresw said:
I have an MX4 originally with Ubuntu touch, I tried to flash 4.5.7i from emmaus.pro.
It failed, updater binary error. I checked the recovery log and it says write error, no space left.
Does anybody have any clue?
Thanks,
Note: I already tried a wipe out (even internal storage). No issues with the cyanogenmod roms from emmaus.pro.
Click to expand...
Click to collapse
i think, mx4 ubuntu touch version, and standard china version, - internal partitions(storage) name - different, so you gives write an error.

isko01 said:
Is someone trying to make fom Meizu MX5?
Sent from my MX5 using Tapatalk
Click to expand...
Click to collapse
Now it is impossible.

zaurikk said:
Now it is impossible.
Click to expand...
Click to collapse
Thanks for reply . Can I know how much is good Caynogenmod on MX4? Is everything working good?
Sent from my MX5 using Tapatalk

isko01 said:
Thanks for reply . Can I know how much is good Caynogenmod on MX4? Is everything working good?
Sent from my MX5 using Tapatalk
Click to expand...
Click to collapse
Yep, all needed function now it work - gsm module, wi-fi, bluetooth and etc.
The only problem, that ROM not officially for Cyanogen team, that rom created by ordinary users and updated 1-2 times on month.

i tried on M2 note, i suppose it bricked.is it possible earlier condition working?i look up some unbrick videos, can repairs make my phone working?thanks.

No way to unbrick it, this is for MX4 not M2 Note !!! You'll need to change the motherboard, sorry

zaurikk said:
Yep, all needed function now it work - gsm module, wi-fi, bluetooth and etc.
The only problem, that ROM not officially for Cyanogen team, that rom created by ordinary users and updated 1-2 times on month.
Click to expand...
Click to collapse
Thanks to all user's who making this for MX4. They are really engineers! I hope they will try for MX5.
Yes, the problem it is not official, and we cant get new update.
Why we don't write a email to Canynogen and tell them that we open the bootloader and put CM. But we want they make CM for MX4 and MX5, with new CM and updates?
Sent from my MX5 using Tapatalk

my meizu is bricked, ne response please help me

hi someone had tested this app already? is it surely gonna work??
and after i will unlock the bootloader i can instal any rom? like Mokee and CM12.1??

X800 Hard brick

Hello,
my brand new X800 hard bricked last night while flashing the first custom ROM: it ended the process in TWRP 3.0.1 and screen shut down never to light up anymore.
When I connect it to the PC it gets recognized as a Qualcomm device in 9008 state, I managed to find a lot of flashing tools which actually finds the COM port used by that but I don't have the RUU/Fastboot ROM/whatever files I need to revive the device. I read in LeMe USA forums that LeTV won't offer an unbrick tool (http://forum.le.com/us/index.php?th...back-to-life-a-hard-bricked-dead-x800-pro.264), can somebody help me out on that? I found this Chinese forum and you can see a screenshot of a "Letv flash tool"but I can't understand how to get that (http://bbs.ydss.cn/thread-627786-1-1.html).
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
http://www.androidbrick.com/download/letv_leeco_x800_x900_unbrick_files_qdloader_9008/ (they ask for a password?)
Thank you so much for your help.

le1 pro unbrick
contact me: [email protected]

teorouge said:
Hello,
my brand new X800 hard bricked last night while flashing the first custom ROM: it ended the process in TWRP 3.0.1 and screen shut down never to light up anymore.
When I connect it to the PC it gets recognized as a Qualcomm device in 9008 state, I managed to find a lot of flashing tools which actually finds the COM port used by that but I don't have the RUU/Fastboot ROM/whatever files I need to revive the device. I read in LeMe USA forums that LeTV won't offer an unbrick tool (http://forum.le.com/us/index.php?th...back-to-life-a-hard-bricked-dead-x800-pro.264), can somebody help me out on that? I found this Chinese forum and you can see a screenshot of a "Letv flash tool"but I can't understand how to get that (http://bbs.ydss.cn/thread-627786-1-1.html).
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
http://www.androidbrick.com/download/letv_leeco_x800_x900_unbrick_files_qdloader_9008/ (they ask for a password?)
Thank you so much for your help.
Click to expand...
Click to collapse
Fine, I got to download the files from another link!
Here you can find the recovery package, the flasher, qcom drivers and adb/fastboot+android drivers:
https://mega.nz/#F!h0AV3SiB!vq9S-E622UeKmU16USJNHA
Too bad I can't flash because I get an error (error.txt)
Code:
-p COM3 -f D:\qfil\Qfil\tmp\prog_emmc_firehose_8994_lite.mbn -x D:\qfil\unsparse.xml Version 2.2 Downloading flash programmer: D:\qfil\Qfil\tmp\prog_emmc_firehose_8994_lite.mbn Successfully open flash programmer to write: D:\qfil\Qfil\tmp\prog_emmc_firehose_8994_lite.mbn Waiting for flash programmer to boot Programming EMMC device using SECTOR_SIZE=512 <?xml version = "1.0" ?><data><configure MemoryName="emmc" ZLPAwareHost="1" SkipStorageInit="0" SkipWrite="0" MaxPayloadSizeToTargetInBytes="16384"/></data> ERROR: No response to configure packet Status: 21 (null)
More info and screenshots:
http://www.letv.re/topic/177-bricked-phone-x800/
-->01.png: my flasher config
--> 02.png: how my PC sees the X800
--> 03.png: some error I get AFTER flash fails
--> 04.png: flasher
--> 05+06-png: files in recovery package (Qfil***.zip)
--> 1/2/3/4.png: flashing istructions I can't speak any Chinese language, I really hope someone can translate the writings in the png's; of course I hope someone can help me even harder. Thanks!

Same problem.
I also have the same problem. I think Qfil rom was not correct. If the rom version is correct, it might work.

Hi, I have talked with cuoco92 (known ROM cooker) and he told me the reason for these bricks and how we maybe can unbrick them. For that we need the file emmc_appsboot.mbn from the LeTV X800 US version. Unfortunately there is nowhere to download the US firmware, and it seems that LeTV will also not help to share it. So that's why the only way is if someone is going to extract it from a working LeTV X800 US version.
The reason why the QFIL method doesn't work is that the firmwares files are only for the Chinese version, and that will not work on the US version. So the method will always fail. Actually I got a step further with the QPST/QFIL connection where it actually succeeded in connecting to the Sahara protocol, saying "Sahara protocol completed" and "Switch To FireHose" ** All is well ** SUCCESS!! but it all ended up with another error as it later again couldn't connect to the port, and I got Download Fail:FireHose Fail FHLoader Fail: Proess fail....
The reason for the brick in the first place is that all the guides on how to install TWRP etc. on the net are made for the Chinese LeTV X800, if someone tries it on the LeTV X800 US version it will end up bricking the phone completely. So beware if the guides doesn't specific say that it also works on the US version then don't try to flash or modify anything!

s7yler said:
Hi, I have talked with cuoco92 (known ROM cooker) and he told me the reason for these bricks and how we maybe can unbrick them. For that we need the file emmc_appsboot.mbn from the LeTV X800 US version. Unfortunately there is nowhere to download the US firmware, and it seems that LeTV will also not help to share it. So that's why the only way is if someone is going to extract it from a working LeTV X800 US version.
The reason why the QFIL method doesn't work is that the firmwares files are only for the Chinese version, and that will not work on the US version. So the method will always fail. Actually I got a step further with the QPST/QFIL connection where it actually succeeded in connecting to the Sahara protocol, saying "Sahara protocol completed" and "Switch To FireHose" ** All is well ** SUCCESS!! but it all ended up with another error as it later again couldn't connect to the port, and I got Download Fail:FireHose Fail FHLoader Fail: Proess fail....
The reason for the brick in the first place is that all the guides on how to install TWRP etc. on the net are made for the Chinese LeTV X800, if someone tries it on the LeTV X800 US version it will end up bricking the phone completely. So beware if the guides doesn't specific say that it also works on the US version then don't try to flash or modify anything!
Click to expand...
Click to collapse
OK, thanks for this Info. I will get my new LETV One Pro 01.06 or 02.06. I ordered it via efox-shop.com. And when I look at the images on their web site, i see a CE sign at the back. So if it is a US version and some could tell me how to extract this file without bricking it, I can do the extraction of this file "emmc_appsboot.mbn"...

Please note I had no issues flashing TWRP via fastboot, flashing supersu and xposed zips from TWRP and using xposed modules. Problems rise flashing ROMs since both official LeTV and custom ones have a firmware-update folder inside, I think if you delete that folder from zip you can flash ROMs just fine. On my HTC One m7, custom ROMs never have that folder.
EDIT: confirmed just now, erasing that "firmware-update" folder in the zip and flashing it you won't brick.
Inviato dal mio HTC One utilizzando Tapatalk

Same problem
Hi guys! I also bought my x800 via e-fox and was able to brick it using the wrong rom. I found some files on androidbrick with no password needed to download. Do you think they'll work? I wish i could paste link to the files but I can't since this is my first post on xda

Same problem here. Tried to flash the cuoco92 twrp recovery and got the penguin screen. I solved flashing the original twrp. After I tried to flash cuoco 92 rom but got the Black screen.

peppebi said:
Same problem here. Tried to flash the cuoco92 twrp recovery and got the penguin screen. I solved flashing the original twrp. After I tried to flash cuoco 92 rom but got the Black screen.
Click to expand...
Click to collapse
Which TWRP and ROM did you have installed?
Inviato dal mio Le X820 utilizzando Tapatalk

Cuoco92 said:
Which TWRP and ROM did you have installed?
Inviato dal mio Le X820 utilizzando Tapatalk
Click to expand...
Click to collapse
Hello cuoco!
I wrote to you on facebook as well.
I tried the last ROM in your download page and the twrp download ed from the same page.
---------- Post added at 05:48 PM ---------- Previous post was at 05:47 PM ----------
I flashed the twrp 3.0.2 downloaded from twrp page and this worked but after I bricked the phone with your rom because i think my phone is us versione.

peppebi said:
Hello cuoco!
I wrote to you on facebook as well.
I tried the last ROM in your download page and the twrp download ed from the same page.
---------- Post added at 05:48 PM ---------- Previous post was at 05:47 PM ----------
I flashed the twrp 3.0.2 downloaded from twrp page and this worked but after I bricked the phone with your rom because i think my phone is us versione.
Click to expand...
Click to collapse
I've uploaded the 13S for US version right now. You have installed that one?
Inviato dal mio Le X820 utilizzando Tapatalk

No the chinese One since i believed my phone was chinese and the rom backup could help me in case of failure. I never imagined i would brick the phone. What Can i do now? Is there any fix? Thank you.

First flashed twrp 3.0.2. than your rom 10s, then the screen went Black. My phone is an us version.

We're all in the same boat guys, waiting for some miracle to happen... But since it's mostly in LeEco/LeTV US hands I won't hold my breath, they told that MAYBE and IN THE FUTURE they would provide some help to us, ill fated users.
Inviato dal mio One utilizzando Tapatalk

@teorouge: Can I have the link to the Chinese FW you installed that bricked the phone? I have an extra device that I'm going to brick (already made a backup.img and have a US version prog_emmc_firehose_8994_lite.mbn), so I can try to help you guys. Let me know roughly the procedure (ex. Installed TWRP 3.0.2.0, transferred ZIP, installed, etc.).

viperdream26 said:
@teorouge: Can I have the link to the Chinese FW you installed that bricked the phone? I have an extra device that I'm going to brick (already made a backup.img and have a US version prog_emmc_firehose_8994_lite.mbn), so I can try to help you guys. Let me know roughly the procedure (ex. Installed TWRP 3.0.2.0, transferred ZIP, installed, etc.).
Click to expand...
Click to collapse
@viperdream26: I think it was .013S version from http://bbs.le.com/zt/eui/le_pro1.html I got TWRP 3.0.2 via fastboot flash recovery recovery.img, flashed SuperSu and Xposed zips and used the phone for a couple of days with no issues. The I decided to flash, I went into recovery and flashed the ROM zip but as soon as TWRP ended the process it didn't reboot as it usually does and screen went black, not to light up anymore in any way. Tried long pressing power (more than a minute each time...) and any volume button together but nothing happens. Finally tried QFIL way (and also letv_flash_tool.exe and any flasher out there) but I either get an error while flashing ("Device is not in firehose mode" in QFIL) or I miss some file to launch the process (with MiFlash and such). Thanks for any help you can give, just ask if you need more background!

@viperdream:
Thank you!
I had the .011 us version (but I didn't know my phone was US). I tried to install Cuoco92 TWRP 3.0.2 with the adb tool provided but when the phone reboot I got a black screen with a penguin. So I went on the official TWRP page and followed the procedure to install TWRP via ADB. It worked. After this I made a rom backup (including efs and everything else), wiped and installed Cuoco92 .013 rom and got the black screen.

peppebi said:
@viperdream:
Thank you!
I had the .011 us version (but I didn't know my phone was US). I tried to install Cuoco92 TWRP 3.0.2 with the adb tool provided but when the phone reboot I got a black screen with a penguin. So I went on the official TWRP page and followed the procedure to install TWRP via ADB. It worked. After this I made a rom backup (including efs and everything else), wiped and installed Cuoco92 .013 rom and got the black screen.
Click to expand...
Click to collapse
I got my LeTV One Pro yesterday. I wanted to install TWRP 3.0.2 only via the ADB procedure.
1. Downloaded the TEAMWin Code Name: x1 TWRP.img 3.0.2
2. adb reboot bootloader (Phone rebooted into the pinguin mode)
3. Then I wanted to execute the next command: fastboot flash recovery twrp.img: But the phone automatical reboots out of the Pinguin mode.
It stays there after the first adb command for approx: 3-5sec. before rebooting into normal mode.
So no chance to execute the described 2nd adb command to flash the recovery twrp image.
any ideas ?
BTW: My phone was delivered with a kind of international EUI 5.5.011S(Stable) OS and I could also select German as Default Language. Google Play Store and Apps were already installed. Android Version is 5.0.2. It seems thatz the describe procedures on the web are not functioning with this device. The OS has also no OTP Software Update menu, but I see with ES Explorer a inside the emulated storage folder 0 a log named "last_ota.log".

Did you try switching off your phone and turning it on long pressing power+ vol up to boot in bootloader? Or maybe it was vol down, sorry I bricked and I can't remember exactly which combination boots to recovery and which one to bootloader.
Inviato dal mio HTC One utilizzando Tapatalk

flashing roms with 4.4.x kernel without qpst

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?

[Recovery][MI 8 SE] TWRP Recovery Installer

Hi guys,
Easy way to flash TWRP from computer for Mi 8 SE.
Download suitable file from below.
Twrp 3.2.3-1227 Compatible with Android 9 (Beta v8.12.27 and upper versions)
https://www.mediafire.com/file/qtdm3qlivcn4gmw/MI8_SE_TWRP_Yukleme_Araci_81227.zip/file
Twrp 3.2.3-1102 Compatible with Android 8.1 (Lower versions than Beta v8.12.27)
https://www.mediafire.com/file/bsvuaxcg1vghayz/MI8SE_TWRP_Yukleme_Araci.zip/file
1. Your phone bootloader should be unlocked.
2. Make sure USB drivers are installed to PC.
3. Turn on USB Debugging. Settings - More - Developer Options - Usb debugging
4. Press Volume down + power button and reboot to fastboot mode.
5. Connect your USB cable to PC
6. Unzip downloaded package and run twrp-yukleme.bat file.
7. Press enter to continue. When it's done enter to exit program.
8-For steady TWRP install Magisk16.4 when you boot into TWRP.
Thanks to by.Trabzonlu from miuiturkiye

downloaded multiple times
unpacking gives a bug
I tried both links

olinen said:
downloaded multiple times
unpacking gives a bug
I tried both links
Click to expand...
Click to collapse
Thanks for your report.
Links and zips are updated. It should unzip fine now :good:

it's ok, just that I had to run the program first and only after that I joined the mobile in the fastboot. Otherwise, he made a mistake
Thx :good:

9
which TWRP u guys use to flash android 9 ? i always get bootloop
and most of the TWRP images here wont even boot for me

Alimataei said:
which TWRP u guys use to flash android 9 ? i always get bootloop
and most of the TWRP images here wont even boot for me
Click to expand...
Click to collapse
TWRP 3.2.3 12-17 works for android 9 ?

TacoNikky said:
TWRP 3.2.3 12-17 works for android 9 ?
Click to expand...
Click to collapse
1102 also works for Pie.

I try to install this recovery but nothing happens at all I have installed the rom miui.eu 10.2.2.0 apparently this rom mr deleted the recovery that had already installed before installing this rom:crying:

Have someone trying treble gsi rom? How to proper install? Thanks in advance.

TWRP-3.3.0-0423 whit magisk 19.0 root For Xiaomi mi8 SE
Download Link:
https://mega.nz/#!CrhTmKgY!PE7lXdLtCzPqYO55ulCx2faFLVqPi6mpXXaYOnbbB8s

Could it be possible that this TWRP will work on mi 9 se, too?
Sent from my [device_name] using XDA-Developers Legacy app

putti71 said:
Could it be possible that this TWRP will work on mi 9 se, too?
Click to expand...
Click to collapse
This is mi8se forum!! TWRP is specific for each phone (different kernel, processor...) so there's no way you could install this TWRP img on another phone than Sirius

Getting this error: FAILED (remote: Failed to load/authenticate boot image: Load Error)
Seems to install correctly but doesn't boot into it. Holding power on and volume up boots it back into fast boot. Any ideas?

Hi! Is there an updated twrp for miui 11 android 10. First time to install this.

greendra8 said:
Getting this error: FAILED (remote: Failed to load/authenticate boot image: Load Error)
Seems to install correctly but doesn't boot into it. Holding power on and volume up boots it back into fast boot. Any ideas?
Click to expand...
Click to collapse
Same as mine. How's your device now?
---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------
Hi guys. Im getting the error after flashing twrp. At first it works. I will flash rom so i reset it and wipe al data. But it didn't boot into recovery mode. It stays at fastboot. I just dl this installer from somewhere here in xda so i didint know thatmagisk should be flashed afterward. Pls help. I . getting error authentication failed

Trojan00 said:
Same as mine. How's your device now?
Click to expand...
Click to collapse
This was a long time ago now and I've since changed device. However, I seem to remember having to switch back to the original Chinese ROM and starting again. It allowed me to install the correct version of TWRP I think. But if you do go back, make sure you don't lock your device again like I did. I think there's a checkbox on the program that you have to use to put the Chinese ROM back on and you need to make sure it's ticked. Sorry if I'm not of much help but it was so long ago now that it's hard for me to remember.

greendra8 said:
This was a long time ago now and I've since changed device. However, I seem to remember having to switch back to the original Chinese ROM and starting again. It allowed me to install the correct version of TWRP I think. But if you do go back, make sure you don't lock your device again like I did. I think there's a checkbox on the program that you have to use to put the Chinese ROM back on and you need to make sure it's ticked. Sorry if I'm not of much help but it was so long ago now that it's hard for me to remember.
Click to expand...
Click to collapse
My fault is I didn't flash the magisk. I saw this link somewhere here in xda so I didn't know that magisk should be flashed. What twrp did you install?

Trojan00 said:
My fault is I didn't flash the magisk. I saw this link somewhere here in xda so I didn't know that magisk should be flashed. What twrp did you install?
Click to expand...
Click to collapse
These were the notes that I left myself:
After boot, go into Fastboot and flash recovery 3.2.3-1217 twrp
Using this, wipe everything apart from bottom box on advanced wipe. Do twice, reboot once in the middle.
Flash EU rom. Do the wipe it promts after install and boot up.
Then use fastboot to flash recovery TWRP-EU, and flash magisk (canary build) to keep twrp installed.
I'm not sure what version this TWRP-EU is, so I've just uploaded it to Google Drive for you here.
Hope this helps.

greendra8 said:
These were the notes that I left myself:
After boot, go into Fastboot and flash recovery 3.2.3-1217 twrp
Using this, wipe everything apart from bottom box on advanced wipe. Do twice, reboot once in the middle.
Flash EU rom. Do the wipe it promts after install and boot up.
Then use fastboot to flash recovery TWRP-EU, and flash magisk (canary build) to keep twrp installed.
I'm not sure what version this TWRP-EU is, so I've just uploaded it to Google Drive for you here.
Hope this helps.
Click to expand...
Click to collapse
Bro i downloaded the stock fastboot firmware. But in mi flash it says can not found file flash_all.bat