GUIDE to go from BUGGY VENDOR ROM with UNLOCKED BOOTLOADER to 8.8.9 XIAOMI.EU - Xiaomi Mi Max 3 Guides, News, & Discussion

GUIDE to go from BUGGY VENDOR ROM with UNLOCKED BOOTLOADER to 8.8.9 XIAOMI.EU:
Download 8.8.9 xiaomi.eu from one of these 3 links: 1) https://www.androidfilehost.com/?w=files&flid=280379 2) https://sourceforge.net/projects/xi...s/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/8.8.9/ 3) http://miui.dedyk.gq/8.8.9/xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1.zip
1) Flash China Beta 8.8.9 with Mi Flash Tool using the option "Clean All" (DO NOT choose 'Clean All and Lock'). Links and instructions below:
a) China Beta 8.8.9: bigota.d.miui.com/8.8.9/nitrogen_images_8.8.9_20180809.0000.00_8.1_cn_7bfe310762.tgz
b) Mi Flash Tool:
1b) download link: https://xiaomiflashtool.com/download/xiaomi-flash-tool-20180528
2b) instructions on how to use: https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool
3) Let your China rom boot up, then login to your Mi Account (if you haven't made one yet, make it here: https://global.account.xiaomi.com/pass/register).
4) Once logged in, go to Settings>Additional Settings>Developer Options>Turn ON USB Debugging, Install via USB, and USB Debugging (Security Settings).
5) Download Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790. Extract it to your desktop so you can use it from there easily and rename the folder to ADB.
6) Download TWRP Recovery: https://eu.dl.twrp.me/nitrogen/twrp-3.2.3-0-nitrogen.img.html. Rename it to recovery.img and place it in your ADB folder.
7) Open cmd (Windows Command Processor/command prompt) within ADB folder or navigate there directly by opening cmd and enter the following steps: cd C:\Users\WhateverYourUsernameIs\Desktop\ADB (this puts you in the ADB folder).
8) Turn your phone off. Boot your phone back into FASTBOOT MODE (press and hold VOLUME DOWN and POWER for 6-8 seconds), then plug it into your computer. In cmd, enter the following:
fastboot format userdata, then flash TWRP using the following commands: fastboot flash recovery recovery.img, then boot to recovery using the following commands: fastboot boot recovery.img
9) Changing file system from ext4 to f2fs is NOT NECESSARY, but I included it in case you run into errors, so skip to the WIPE portion of this section: In TWRP, change your file system from ext4 to f2fs: Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > F2FS. Once changing the file system to f2fs, you must go back (back button at the bottom) and reboot to recovery in the REBOOT section of TWRP: Reboot>Reboot to Recovery. Once you're booted back into recovery, mount all your partitions: Mount>Check All Partions. Then go back, select WIPE>Advanced Wipe> select Data, Dalvik Cache and Internal Storage (System should NOT be wiped).
10): Transfer 8.8.9 xiaomi.eu rom from your pc to phone's internal storage and install in TWRP: INSTALL>Zip>Select 8.8.9 xiaomi.eu rom>Flash it.
11) REBOOT. The phone should boot without issue and your bootloader should stay unlocked.
12) Enable VoLTE: Once everything is set up, go to dialer and enter the following: *#*#86583#*#*
If you get this encryption issue after flashing: "Encryption was interrupted and can't be completed after reboot" then look at:
https://xiaomi.eu/community/threads...ed-and-cant-be-completed-after-reboot.45640/, thanks @erwinsie :highfive:
IF YOU WANT ROOT:
1) Download Magisk 17.1 Stable: https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip
2) Reboot to Recovery : Turn off phone, press and hold VOLUME UP + POWER for 6-8 seconds until you see the phone boot into TWRP. Select INSTALL>Zip>Magisk-v17.1.zip>Flash it and reboot.
Thanks and credit to: @omer919 and @martin.burgas - I used some of your install ideas to help everyone :highfive:.
If you have any further questions, suggestions, or anything you'd like to add, just let me know. Thanks.

May I ask why do you change the partition formatting from ext4 to f2fs as it is not necessary?

dogiex said:
May I ask why do you change the partition formatting from ext4 to f2fs as it is not necessary?
Click to expand...
Click to collapse
You don't need to. @martin.burgas did it I believe because he ran into some errors. I know that people get sd card corrupted on ext4 when they install gsi roms, so maybe he was future proofing in case shifting over to an android gsi rom? I'm not 100% sure. Maybe @omer919 or @martin.burgas can answer better.

And please don't call 9.6.4 fake... Call it first release, buggy whatever but not fake b/c it isn't...
Forum is full with confusing info and people...

nijel8 said:
And please don't call 9.6.4 fake... Call it first release, buggy whatever but not fake b/c it isn't...
Forum is full with confusing info and people...
Click to expand...
Click to collapse
My mistake due to helping someone that called it that, but I fixed it. Thanks for the reminder.

Not being argumentative - just curious. When some resellers began shipping the Mi Max 3 two months ago with the 9.6.4 "global" ROM (in Chinese retail boxes), Xiaomi had not yet released an international/global variant of the phone. The only version was the CN (China) variant. Xiaomi did not even list the Mi Max 3 at the time on its global web site. Two months later Xiaomi released the international variant of the phone for the first time outside mainland China - in Hong Kong, then Singapore, the Philippines, and finally Malaysia. These international variants of the phone are sold with the 9.6.7.0 "global ROM" and they come in boxes with English labeling, clearly marked with the red "Global" factory sticker. So where did the 9.6.4 "vendor/global" ROM which clearly has a broken modem because of all the complaints about phone call connectivity come from? If it isn't from Xiaomi what would you call it?
---------- Post added at 08:42 PM ---------- Previous post was at 08:39 PM ----------
Thank you for this excellent guide. I adopted this approach after much trial and error when my phone arrived last month. This guide would have saved me hours of pulling my hair out. I've stayed on xiaomi.eu 8.8.9 since.

frcraig said:
Not being argumentative - just curious. When some resellers began shipping the Mi Max 3 two months ago with the 9.6.4 "global" ROM (in Chinese retail boxes), Xiaomi had not yet released an international/global variant of the phone. The only version was the CN (China) variant. Xiaomi did not even list the Mi Max 3 at the time on its global web site. Two months later Xiaomi released the international variant of the phone for the first time outside mainland China - in Hong Kong, then Singapore, the Philippines, and finally Malaysia. These international variants of the phone are sold with the 9.6.7.0 "global ROM" and they come in boxes with English labeling, clearly marked with the red "Global" factory sticker. So where did the 9.6.4 "vendor/global" ROM which clearly has a broken modem because of all the complaints about phone call connectivity come from? If it isn't from Xiaomi what would you call it?
---------- Post added at 08:42 PM ---------- Previous post was at 08:39 PM ----------
Thank you for this excellent guide. I adopted this approach after much trial and error when my phone arrived last month. This guide would have saved me hours of pulling my hair out. I've stayed on xiaomi.eu 8.8.9 since.
Click to expand...
Click to collapse
From all my reading of different forums including this one, I came to the conclusion that the 9.6.4.0 just like many beta/leaked roms was from a Xiaomi direct source, but simply incomplete or compiled in a similar fashion to nightly roms. Things that are early or beta are released beforehand to also build sales whether they are broken or not - take a look at all of us that bought actual Chinese handsets compared to official global ones; in addition, updates are readily available from xiaomi sources - how else would a guide like this or fixes by developers be possible? No one even knew if there would be an official global version 100% until only recently. Even Honor was thought to have a Global version of the Honor Note 10 coming at Berlin, but that never happened. A lot of these resellers use/swap/reuse similar people/companies - that is a fact. Take a look at all the Chinese phones, cases, screen protectors, etc out there that are identical copies.
TLDR: 9.6.4.0 - official but broken because it was an incomplete nightly/beta similar to what Nijel said above. It was released for sales and weighing the international market (my opinion). It worked.
You are most welcome :highfive:. Part of me wanted to do this sooner, but wasn't sure how much it was needed until now. I hope it helps future users and if anyone finds any better methods or tweaks to this guide, let me know and I'll gladly adjust it accordingly.

nijel8 said:
And please don't call 9.6.4 fake... Call it first release, buggy whatever but not fake b/c it isn't...
Forum is full with confusing info and people...
Click to expand...
Click to collapse
9.6.4.0 was originally called a 'Global ROM', it was not the authentic Global ROM from Xiaomi therefore it WAS a fake Global ROM. It is as simple as that.
Omer919's first language might not be English but his use of the word 'fake' was not incorrect.

I'm missing something??
I received two days ago one of this phones, ublocked and with 9.6.4.0(OEDMIFD).
I upgrade with internal updater to 9.6.6.0(OEDMIFD) without problem and use the phone one day
next day I install TWRP and go to las xiaomi.eu v10 version -> xiaomi.eu_multi_MIMAX3_8.9.20_v10-8.1.zip
I am using the phone one and looks everything ok
Is there a problem with these steps , is dangerous? The only thing is that now I have ARB activated, is ok??
Thanks a lot

Wam7 said:
9.6.4.0 was originally called a 'Global ROM', it was not the authentic Global ROM from Xiaomi therefore it WAS a fake Global ROM. It is as simple as that.
Omer919's first language might not be English but his use of the word 'fake' was not incorrect.
Click to expand...
Click to collapse
Aaah, omer919... All confusing/incorrect info here came from his copy/paste abilities from Xiaomi forums...
Read the next post below yours! If 9.6.4 was fake and not leaked from Xiaomi then it wouldn't be possible to update to 9.6.6 with the built-in MIUI updater, would it? Updater and the stock recovery as part of the updae process connects to 4 Xiaomi servers and verifies both currently running rom and the one to be installed. How about that for an argument...
9.6.4 is Xiaomi's first beta global rom for Max 3 for internal testing and retailer got hads on it before global device release period... Devices that are selling with 9.6.4 pre-installed and unlocked are fake global versions, not the rom. Simple as that.

jamarita said:
I received two days ago one of this phones, ublocked and with 9.6.4.0(OEDMIFD).
I upgrade with internal updater to 9.6.6.0(OEDMIFD) without problem and use the phone one day
next day I install TWRP and go to las xiaomi.eu v10 version -> xiaomi.eu_multi_MIMAX3_8.9.20_v10-8.1.zip
I am using the phone one and looks everything ok
Is there a problem with these steps , is dangerous? The only thing is that now I have ARB activated, is ok??
Thanks a lot
Click to expand...
Click to collapse
MIMAX3_8.9.20 have some bugs, best rom for now is 8.8.9 older but dont have bugs and dont have ARB. When You install 8.9.20 You activated ARB and if You want to update ROM You have to use only higher number, so You have to wait for new releases of xiaomi.eu.

jamarita said:
I received two days ago one of this phones, ublocked and with 9.6.4.0(OEDMIFD).
I upgrade with internal updater to 9.6.6.0(OEDMIFD) without problem and use the phone one day
next day I install TWRP and go to las xiaomi.eu v10 version -> xiaomi.eu_multi_MIMAX3_8.9.20_v10-8.1.zip
I am using the phone one and looks everything ok
Is there a problem with these steps , is dangerous? The only thing is that now I have ARB activated, is ok??
Thanks a lot
Click to expand...
Click to collapse
You are ARB activated, but you'll l be fine. Just don't flash any version before your current one or you'll risk bricking your device. If you run into any trouble post here, and we'll help you. Do me a favor and edit your post because you should never quote the first large OP (original post). Thanks :highfive:

nijel8 said:
...
Read the next post below yours! If 9.6.4 was fake and not leaked from Xiaomi then it wouldn't be possible to update to 9.6.6 with the built-in MIUI updater, would it? Updater and the stock recovery as part of the updae process connects to 4 Xiaomi servers and verifies both currently running rom and the one to be installed. How about that for an argument...
9.6.4 is Xiaomi's first beta global rom for Max 3 for internal testing and retailer got hads on it before global device release period... Devices that are selling with 9.6.4 pre-installed and unlocked are fake global versions, not the rom. Simple as that.
Click to expand...
Click to collapse
Let's not start employing argumentum ad hominem or getting bogged down in semantics. It really is quite straight forward.
1. The original retailers were touting this leaked/early beta ROM as a genuine Xiaomi sanctioned, official Global ROM. Let me repeat that again as it is salient point.
The original retailers were touting this leaked/early beta ROM as a genuine Xiaomi sanctioned, official Global ROM
2. Dictionary definition of "Fake"; "a thing that is not genuine."
3. Therefore your point that the word 'Fake' was incorrectly used is a fallacy itself. This is my only point.
4. You can sidetrack all you want and talk about issues that I am not referring to in order to obfuscate the simple issue here; there was nothing wrong with the use of the 'fake', contrary to what you stated.

This thread is not about the namoe of rom but about flashing working properly rom, so it isnt important how people call this rom. Focus on rly helpfull solution...

opasha said:
You don't need to. @martin.burgas did it I believe because he ran into some errors. I know that people get sd card corrupted on ext4 when they install gsi roms, so maybe he was future proofing in case shifting over to an android gsi rom? I'm not 100% sure. Maybe @omer919 or @martin.burgas can answer better.
Click to expand...
Click to collapse
Yes, I changed the file system not to get any errors. I red that some users encounter error 4 , when trying to wipe data, cache and etc. in TWRP and that switching to f2fs fixes the problem. In the main post, just one thing should be changed - if someone changes the file system from ext4 to f2fs, then need to hit back button and then Reboot and choose Recovery, so to reboot TWRP after changing the file system, then follow the rest of the guide.

martin.burgas said:
Yes, I changed the file system not to get any errors. I red that some users encounter error 4 , when trying to wipe data, cache and etc. in TWRP and that switching to f2fs fixes the problem. In the main post, just one thing should be changed - if someone changes the file system from ext4 to f2fs, then need to hit back button and then Reboot and choose Recovery, so to reboot TWRP after changing the file system, then follow the rest of the guide.
Click to expand...
Click to collapse
Thanks, Martin :highfive:. I edited Step 9 of the guide to reflect what you said. If it's worded incorrectly, let me know.

Error fastboot
I have a mi max 3, bootloader unlock and with the global version 9.6.4.0 . I am trying to install the eu version 8.8.9, but when i put the phone in fastboot and try to install the rom the phone turn the screen black and said press any button to shut down, so i cannot do anything.

yuoi said:
I have a mi max 3, bootloader unlock and with the global version 9.6.4.0 . I am trying to install the eu version 8.8.9, but when i put the phone in fastboot and try to install the rom the phone turn the screen black and said press any button to shut down, so i cannot do anything.
Click to expand...
Click to collapse
What step are you messing up on? Big difference in steps between fastboot and rom flashing. That's why I made numbers. Be more specific, otherwise, it's obvious you did it incorrectly.

opasha said:
What step are you messing up on? Big difference in steps between fastboot and rom flashing. That's why I made numbers. Be more specific, otherwise, it's obvious you did it incorrectly.
Click to expand...
Click to collapse
Step 2b the instruccions said that to flash the phone we need to put it in fastboot and when i try to install the china rom my phone turn black and said press any buttom to turn off. I dont know how to explain it well its seems that when the mi flash try to detect the phone something go wrong.

yuoi said:
Step 2b the instruccions said that to flash the phone we need to put it in fastboot and when i try to install the china rom my phone turn black and said press any buttom to turn off. I dont know how to explain it well its seems that when the mi flash try to detect the phone something go wrong.
Click to expand...
Click to collapse
Looks like a driver issue. Use mi suite instead: http://pcsuite.mi.com/

Related

Team Win Recovery Project 3.0.2.0

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
I'm missing something or I'm just watching text? Lol @satana.nik.1996 I saw already this posted on 4PDA, it has idol3 detected on TWRP to install things instead of Ido?
EDIT: well indeed it works, and it is fast as ****, the problem it is only has russian language and i can't test if the twrp is ido or idol3
Enviado desde mi 6045B mediante Tapatalk
Any chance of getting for idol 347?
Thanks for the update! now has all the languages, anyways it had a less bug with other device name, just edited the initrd/default.prop and now all good, it is really really fast, it install roms and backups as twice the old speed lol
Guys, do you mind kicking me in the right direction to find this? Would like to try it out, but can't seem to find it on 4PDA... Thanks!
@kt-Froggy i don't know if i'm allowed to do this, but satanik if you want the link removed from here tell me lol
https://4pda.ru/forum/index.php?showtopic=753533&view=findpost&p=59165103 here is the first post, only russian lang
https://4pda.ru/forum/index.php?showtopic=753533&view=findpost&p=59176110 here is the translated one, but has the device as p839v55 instead of idol3
https://4pda.ru/forum/index.php?showtopic=753533&view=findpost&p=59196559 here is the one i edited from satanik to change the device to idol3
you need an 4PDA account (except for the translated p839v55 one), if @satana.nik.1996 wants to post it here i will do it too
panchovix said:
you need an 4PDA account
Click to expand...
Click to collapse
Thank you! No idea how I missed that in the ROM thread ("Прошивки")... Duh!
My Russian is a bit better than my English, and I do have an account on 4PDA.
Of course, thanks to @satana.nik.1996, too!
@kt-Froggy yeah you are lucky tho, i just use translate
4PDA has some goods Roms too, @andrejchern for example did AOSP_6045Y and Xperia_6045Y, they are really good for battery life (i'm using Xperia_6045Y now)
Can this one deal with encrypted partitions?
Twrp 3.0.2.0 for idol 3 [4.7] 6039 version
Hi!
This is TWRP 3.0.2.0 @santana.nik1996 version modded by me for Idol 3 [4.7] 6039 version!
[*]Micro SD_Card is the main partition.
[*] You can mount System, data, cache,Modem,Persist,USB-OTG,Internal SDCard (internal storage)
[*] It starts in MTP-ADB mode
twrp-3.0.2.0-satana.nik.1996_modded.img
https://mega.nz/#!lpBHkILJ
key: !2Jso7ocAqlb8YWtPI-30BY9DKXv-QK4sueDbEd2XzKE
If you want a easy way just download and execute this exe file!
twrp-3.0.2.0-satana.nik.1996_modded.exe
https://mega.nz/#!k1x3VJqa
key: !dic2Q_hrcIaDmqRjJ6sQ_-9i5lSUj0Q5mNItmAoxTKU
[TESTED AND WORKING!]
NOTE: There is a issue ( from default image), if TWRP enter in sleep mode ( lock screen ) it get issues, at start up go to settings -> screen -> unselect "Enable screen timeout" and everything will be fine.
@santana.nik1996 do you know how to fix this? Thanks! ( Great Job by the way! )
This is default version only change the mounting options, use the exe to install it!
twrp-3.0.2.0-satana.nik.1996.exe
https://mega.nz/#!M4A1QJAZ
key: !ZbmyJQ2guHkMT-bE6JQ9MGJvPpBG8astcePetZrqo-Q
Enjoy it!
.
Well since he posted the 4.7 already, i will post the one i modded for the 5.5 version, obs all the credits for satana.nik1996
This is TWRP 3.0.2.0 Santana.nik1996 edited for Idol 3 [5.5] 6045 Version, he posted one working already on 4PDA here https://4pda.ru/forum/index.php?showtopic=753533&view=findpost&p=59176110, but i just changed the p839v55 to idol3 (on default.prop in initrd)
as i said, very fast (the time to install roms is like 50% less more or something like that), tested to install multiple roms and no problems so far
the .img is here https://mega.nz/#!t54mgBbT!WcJiSByzyuTZFcRXOxXPSePKmioMOmiTU9TPfVbwW1k
Install from TWRP 3.0.0.0 or 3.0.1.0 with install image option, or if you are lucky via fastboot
PS: i suggest if this possible, to an admin, to move thsi thread from general to Android Development, if possible
Installed OK, but didn't have a chance to really test it yet... One little issue found so far - "Reboot Recovery" (from TWRP itself) doesn't seem to work... It boots straight to the OS. But I can reboot to recovery from the OS, and also by Pwr+VolUp from the "off" state, so not a big deal...
kt-Froggy said:
Installed OK, but didn't have a chance to really test it yet... One little issue found so far - "Reboot Recovery" (from TWRP itself) doesn't seem to work... It boots straight to the OS. But I can reboot to recovery from the OS, and also by Pwr+VolUp from the "off" state, so not a big deal...
Click to expand...
Click to collapse
Twrp 3.0.0-0 do the same, it doesn´t boot on recovery again, it starts O.S.
@kt-Froggy EDIT: my bad, yes you are right lol, anyways when you put reboot, just press vol + (without power) and no problem, on 3.0.1.0 this worked well
panchovix said:
Well since he posted the 4.7 already, i will post the one i modded for the 5.5 version, obs all the credits for satana.nik1996
This is TWRP 3.0.2.0 Santana.nik1996 edited for Idol 3 [5.5] 6045 Version, he posted one working already on 4PDA here https://4pda.ru/forum/index.php?showtopic=753533&view=findpost&p=59176110, but i just changed the p839v55 to idol3 (on default.prop in initrd)
as i said, very fast (the time to install roms is like 50% less more or something like that), tested to install multiple roms and no problems so far
the .img is here https://mega.nz/#!t54mgBbT!WcJiSByzyuTZFcRXOxXPSePKmioMOmiTU9TPfVbwW1k
Install from TWRP 3.0.0.0 or 3.0.1.0 with install image option, or if you are lucky via fastboot
PS: i suggest if this possible, to an admin, to move thsi thread from general to Android Development, if possible
Click to expand...
Click to collapse
Hi!
When it enter in lock screen by it selfe, can you unlock screen right or get issue?
.
persona78 said:
Hi!
When it enter in lock screen by it selfe, can you unlock screen right or get issue?
.
Click to expand...
Click to collapse
do you mean, when the phone locks itself (without using it for 1 for example), if i can unlock it without problems? if is that, i have no problems unlocking the screen
now if is other thing, i didn't understand it D:
After I just got done flashing 3.0.1.0 haha, I'll give this a go.
I have one question, what is the difference between flashing rom with 2.74 version and 3.0.0? Is it possible to flash any rom on 2.74 version? Can nougat be flashed with 2.74?
Sent from my 6045I using Tapatalk
panchovix said:
do you mean, when the phone locks itself (without using it for 1 for example), if i can unlock it without problems? if is that, i have no problems unlocking the screen
now if is other thing, i didn't understand it D:
Click to expand...
Click to collapse
Yes, if you wait 1 minute, it lock by himselfe then if i want to unlock it get all crazy and i must to reboot it.
.
persona78 said:
Yes, if you wait 1 minute, it lock by himselfe then if i want to unlock it get all crazy and i must to reboot it.
.
Click to expand...
Click to collapse
No problem here, i'm using now Xperia_6045Y (from 4PDA, it is based on 6045Y stock) and tested too on LineageOS13, and no problems, are you sure it is related to TWRP?¿
Maybe something is different between 6039 and 6045 in these aspect
---------- Post added at 07:03 PM ---------- Previous post was at 07:00 PM ----------
belkoo said:
I have one question, what is the difference between flashing rom with 2.74 version and 3.0.0? Is it possible to flash any rom on 2.74 version? Can nougat be flashed with 2.74?
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
sometimes some roms can be flashed on old TWRP versions, and i would say (i can't say this is true) N, if it is released, it will need atleast TWRP 3.0.0.0
for example in my old Moto G 4G (XT 1040), i couldn't flash AOKP 7.1.1 on TWRP 3.0.2.0, i needed to upgrade to TWRP 3.0.3.0

X720, X722 and X727 uses the same ROM?

hi guys, i have the X722, i can use ROMs of X727 and X720?
No the x722 has no custom ROMs. You'll soft brick the phone if you try to load any ROMs from other variants onto it, to my knowledge.
:crying::crying::crying::crying::crying::crying:
I try install Miui 8 rom... i forgot to do backup, and i try by fastboot install...
And now a has a hard brick... and i don't find any QFil file to bring my phone back...
:crying:
I also soft bricked my Le Eco Pro 3
vsrocha said:
:crying::crying::crying::crying::crying::crying:
I try install Miui 8 rom... i forgot to do backup, and i try by fastboot install...
And now a has a hard brick... and i don't find any QFil file to bring my phone back...
:crying:
Click to expand...
Click to collapse
Unfortunately, I also soft bricked my Le Eco Pro 3
I tried for 16 hours to resolve the issue and could not. However, after I did the research I now understand what I did wrong. Also, I got rid of the phone. Though I will probably order another one and be much more careful next time.
For anyone else reading this post : don't trust every comment here. Some people will give incorrect or incomplete info, such as advice to wipe the system to get around encryption.
* That's what I did and after successfully unlocking the boot-loader, I find that my system was somehow encrypted.. I did not encrypt my phone so I am not sure how this happened. In my haste, I did not create a recovery, I thought that is what the official Leeco twrp was for?
Options?
I too read about the Qfil tool, at the time I was having trouble downloading the files so I attempted to wing it... and failed.
I see now that I did not spend enough time on this complex option.
Update:
here is the exact instructions for using the Qfil method. ( this link provides step by step, and is tedious, but appears to work.
Sigh! I attempted to post a link and could not, due to being new on this site.
No doubt, I found the best instructions that I have seen yet on the Qfil Process.
Its on the unoffical Leeco Repair site : tora33 #comment-15320 this post is much more extensive than some other posts by Tora33 linked from XDA
Again, I can't post the actual link here! Just search for : unoffical Leeco Repair site : tora33 #comment-15320
Potential other options
J tag brick repair service website : brickedmyphone they charge $45 to repair a bricked phone.[/U
[*] This video seems very promising! Unfortunately, I wasn't able to find this video before now.
Since I am new here I am not allowed to help you by posting links!
search YouTube for How to unbrick any bricked letv phone without loosing data ( easiest way ) in Hindi.
Yes its in Hindi, but you will still understand because he used some English and it seems that he has built a fairly useful tool. Although, its still easy to get the gist of what he is telling us and he apparently built a program to repair a bricked Leeco phones, and he has other videos
[*] Finally Google : LeEco X820 Max 2 Super Unbrick Guide ( gizmochina. website) seems to be another complete solution.
I hope this helps you!
How to unbrick any bricked letv phone without loosing data ( easiest way ) in hindi.
https://www.youtube.com/watch?v=m0o4QtNXljg
1. He shows us that his phone is stuck on the logo and his recovery won't boot (it should start in 5 seconds).
2. He says to go to the stuck bootloader page, press the power on/off button and volume down button continuously to get into Download(?) mode.
3. Connect your phone to your PC and use your unbrick tool of choice. The tool linked in the video description is for the LeEco Le 2 x526, NOT the x720/x722/Le Pro3 models. So I wouldn't recommend you use it unless someone here can confirm that they used it with their Le Pro3 successfully.
4. Assuming this program works with all LeEco phones (not confirmed yet), continue with the process on your Le Pro3.
5. A cmd prompt will come up after you connect your phone and start the program. The instructions are in English. Choose an option--first install adb/fastboot drivers if you haven't already, then press 3 to Unlock the Bootloader. Check the bootloader's status by pressing 4. If it says "device unlock: true", it's unlocked.
6. Flash TWRP by pressing 5. I don't know which version of TWRP this program flashes, and whether or not it's compatible with the LeEco Pro3.
7. Then press 6 to reboot your phone into TWRP. You can now remove your cable and flash your ROM (most probably stock). Your phone is unbricked.
8. If your phone lost your data, you can connect via OTG storage and transfer ROMs and firmware/zip files to your phone using OTG. Reflash eUI 5.8 because 5.9 will most probably bootloader lock and brick your device again. Remember to select "swipe to allow modification" and "allow disable".
You might want to use the tool mentioned here to unlock the bootloader if the tool used in this Youtube video doesn't work (you'll have to add your phone's files to it though): https://forum.xda-developers.com/showpost.php?p=73988576&postcount=66
Also check this link (as tsongming mentioned): http://www.leeco.re/topic/1340-urgent-x800-no-turn-on-after-fastboot-process-rom/#comment-15320
tsongming said:
Unfortunately, I also soft bricked my Le Eco Pro 3
I tried for 16 hours to resolve the issue and could not. However, after I did the research I now understand what I did wrong. Also, I got rid of the phone. Though I will probably order another one and be much more careful next time.
Click to expand...
Click to collapse
Hey, good on you for figuring out what went wrong and sharing it with the rest of us!
Whatever you do, don't order a Chinese phone from like Gearbest, Geekbuying, Aliexpress, LightinTheBox, and all those other wholesale websites. They even shamelessly put their crappy vendor ROMs on Xiaomi phones. They put vendor ROMs on their phones that send data back to god-knows-which servers in China. Well, even OnePlus and LeEco do it natively, but I trust them over some shady wholesaler. If you absolutely want an LeEco, buy it through Amazon U.S. or Amazon India, Flipkart, etc. An official retailer is best.
Otherwise I recommend Motorola phones, even though I hate mine. They're generally cheap, they're stock, and they're a much safer option.
sk8223 said:
How to unbrick any bricked letv phone without loosing data ( easiest way ) in hindi.
1. He shows us that his phone is stuck on the logo and his recovery won't boot (it should start in 5 seconds).
2. He says to go to the stuck bootloader page, press the power on/off button and volume down button continuously to get into Download(?) mode.
3. Connect your phone to your PC and use your unbrick tool of choice. The tool linked in the video description is for the LeEco Le 2 x526, NOT the x720/x722/Le Pro3 models. So I wouldn't recommend you use it unless someone here can confirm that they used it with their Le Pro3 successfully.
4. Assuming this program works with all LeEco phones (not confirmed yet), continue with the process on your Le Pro3.
5. A cmd prompt will come up after you connect your phone and start the program. The instructions are in English. Choose an option--first install adb/fastboot drivers if you haven't already, then press 3 to Unlock the Bootloader. Check the bootloader's status by pressing 4. If it says "device unlock: true", it's unlocked.
6. Flash TWRP by pressing 5. I don't know which version of TWRP this program flashes, and whether or not it's compatible with the LeEco Pro3.
7. Then press 6 to reboot your phone into TWRP. You can now remove your cable and flash your ROM (most probably stock). Your phone is unbricked.
8. If your phone lost your data, you can connect via OTG storage and transfer ROMs and firmware/zip files to your phone using OTG. Reflash eUI 5.8 because 5.9 will most probably bootloader lock and brick your device again. Remember to select "swipe to allow modification" and "allow disable".
You might want to use the tool mentioned here to unlock the bootloader if the tool used in this Youtube video doesn't work (you'll have to add your phone's files to it though): https://forum.xda-developers.com/showpost.php?p=73988576&postcount=66
Also check this link (as tsongming mentioned): http://www.leeco.re/topic/1340-urgent-x800-no-turn-on-after-fastboot-process-rom/#comment-15320
Hey, good on you for figuring out what went wrong and sharing it with the rest of us!
Whatever you do, don't order a Chinese phone from like Gearbest, Geekbuying, Aliexpress, LightinTheBox, and all those other wholesale websites. They even shamelessly put their crappy vendor ROMs on Xiaomi phones. They put vendor ROMs on their phones that send data back to god-knows-which servers in China. Well, even OnePlus and LeEco do it natively, but I trust them over some shady wholesaler. If you absolutely want an LeEco, buy it through Amazon U.S. or Amazon India, Flipkart, etc. An official retailer is best.
Otherwise I recommend Motorola phones, even though I hate mine. They're generally cheap, they're stock, and they're a much safer option.
Click to expand...
Click to collapse
Thanks for the detailed steps, and providing the actual links, it will definitely help people.
Btw, I bought another LeEco Pro 3, from Amazon. At $199 its the best deal available for a device that has a Snapdragon 821processor, among all of its other features.
Right now, I am still using stock. Soon, I will unlock the bootloader, install TWRP, and root the phone.
I have become accustomed to the stock software and would stick with it for a while if it was running Nougat
To be honest, I am still a noob with installing custom ROMS, in case I ever decide to go back to stock, do you have a preferred method of backing up the stock software prior to installing a custom ROM?
I know that I can create a recovery within TWRP and back that up... us that sufficient enough, or is Titanium a better option?
Thanks again.
tsongming said:
Thanks for the detailed steps, and providing the actual links, it will definitely help people.
Btw, I bought another LeEco Pro 3, from Amazon. At $199 its the best deal available for a device that has a Snapdragon 821processor, among all of its other features.
Right now, I am still using stock. Soon, I will unlock the bootloader, install TWRP, and root the phone.
I have become accustomed to the stock software and would stick with it for a while if it was running Nougat
To be honest, I am still a noob with installing custom ROMS, in case I ever decide to go back to stock, do you have a preferred method of backing up the stock software prior to installing a custom ROM?
I know that I can create a recovery within TWRP and back that up... us that sufficient enough, or is Titanium a better option?
Thanks again.
Click to expand...
Click to collapse
The Le Pro3 is a great phone... on an official ROM, and if it's the x727 variant. The x720 variant is good too, but much harder to find a native SafetyNet ROM for it. Stock passes SafetyNet integrity checks. It's good that you bought it from Amazon. You'll most likely be getting a native SafetyNet-passing device and a decent warranty. Even on eUI, LeEco phones are viable. Especially if you're used to iOS. What I absolutely despise, though, are shop ROMs, and now I'm stuck with one. :crying:
Backing up stock? The moment you get the phone, set it up as normal but don't add any information if you don't have to to it. Like skip the Google account setup and whatnot (if you can). Unlock the bootloader & put TWRP on it. Make a Nandroid backup of your stock unmodified firmware. Heck, even just backing up your fully-setup ROM is fine. Just make sure you erase data, cache, etc. before flashing it (and remove the other ROM you're using).
Otherwise you'll find stock factory images for your device here on XDA if you need to go back. Download them before getting your phone if you don't want to wait.
I prefer Nandroid backups, but if you want to backup apps one by one, use Titanium Backup. I don't really like doing that anymore because Nandroids are more convenient, but if there's an app you absolutely need to add to all of your ROMs, then back up the app separately.
sk8223 said:
The Le Pro3 is a great phone... on an official ROM, and if it's the x727 variant. The x720 variant is good too, but much harder to find a native SafetyNet ROM for it. Stock passes SafetyNet integrity checks. It's good that you bought it from Amazon. You'll most likely be getting a native SafetyNet-passing device and a decent warranty. Even on eUI, LeEco phones are viable. Especially if you're used to iOS. What I absolutely despise, though, are shop ROMs, and now I'm stuck with one. :crying:
Backing up stock? The moment you get the phone, set it up as normal but don't add any information if you don't have to to it. Like skip the Google account setup and whatnot (if you can). Unlock the bootloader & put TWRP on it. Make a Nandroid backup of your stock unmodified firmware. Heck, even just backing up your fully-setup ROM is fine. Just make sure you erase data, cache, etc. before flashing it (and remove the other ROM you're using).
Otherwise you'll find stock factory images for your device here on XDA if you need to go back. Download them before getting your phone if you don't want to wait.
I prefer Nandroid backups, but if you want to backup apps one by one, use Titanium Backup. I don't really like doing that anymore because Nandroids are more convenient, but if there's an app you absolutely need to add to all of your ROMs, then back up the app separately.
Click to expand...
Click to collapse
Thank you for you very good detailed advice. Its truly appreciated.
I was decrying the shop ROM a lot but it's okay. I thought it'd be a lot worse than it is, but at least it lets me play the games I want to play on it without issue (so far...). I'm debloating it soon. Gonna remove all the LeEco apps. I hope kernel sources get released for the x722 but I ain't holding my breath.

Please Recommend Me The Top 2/3 Most Stable Slim Roms - New Axon 7 User!

I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264
kanej2006 said:
I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264
Click to expand...
Click to collapse
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !
raystef66 said:
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !
Click to expand...
Click to collapse
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:
kanej2006 said:
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:
Click to expand...
Click to collapse
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:
raystef66 said:
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:
Click to expand...
Click to collapse
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!
kanej2006 said:
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!
Click to expand...
Click to collapse
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.
raystef66 said:
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.
Click to expand...
Click to collapse
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
That depends. I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)
kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me
raystef66 said:
I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)
Click to expand...
Click to collapse
Will do. You are right, the toolkit automatically checks for the latest update and it finds version 3.1.1.0.
Choose an username... said:
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me
Click to expand...
Click to collapse
I did see on the forum users attempting to relock the bootloader and it worsened things, I will not attempt this.
Should be able to let you know tomorrow or the day after what version I get and hopefully when I successfully gain recovery and root access!
I just hope I don't get the dead microSD bug that many people have mentioned. Top of the range 64Gb/128Gb MicroSD cards can be costly so I would not like to have them corrupted!
@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.
If you want to try a more Android vanilla ROM, then I suggest AICP. Be sure to use the unofficial builds by genesixxbf3. They are very stable and have good features.
https://forum.xda-developers.com/axon-7/development/rom-aicp-12-1-t3611013
kanej2006 said:
@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.
Click to expand...
Click to collapse
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:
raystef66 said:
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:
Click to expand...
Click to collapse
Haha, no, not yet received! Where I am living at the moment, the weekend is Friday and Saturday, Sunday to Thursday work, strange but that's the way it is.
The seller estimates the item to arrive on Sunday or Monday, hopefully Sunday.
In the end the Netherland's sever finally managed to get me the 2.1Gb download complete. I did try others but were slower. Good thing in your rom you included the 3 different models for the Axon 7. I'm yet to see which one I receive!
Confirmed G version received.
kanej2006 said:
Confirmed G version received.
Click to expand...
Click to collapse
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.
raystef66 said:
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.
Click to expand...
Click to collapse
Not working, been trying for hours.
Not connecting despite all drivers installed, including Qualcom driver. Followed all instructions as stated. Stuck from number 20. When entering this command I get ''failed to connect''
When typing in adb devices it finds my device.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED
kanej2006 said:
Not working, been trying for hours.
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED
Click to expand...
Click to collapse
You're on nougat ? Look into about phone for that.
Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?
raystef66 said:
You're on nougat ? Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?
Click to expand...
Click to collapse
No, I am on stock MM.
kanej2006 said:
No, I am on stock MM.
Click to expand...
Click to collapse
Should work then.
Can you download recovery again. Check all characters if they're all written ok.
Sure the toolkit cannot bring enlightment too ?

Is it possible to unlock a P8 lite 2017 today ?

Hi,
I'm French and my level in english is not very high.
So I try to unlock my wife's phone but I havbe understood that it is no more possible with the classic way with huawei support.
Does exist another way tu do this ? Or is it definitivly impossible ?
No french forum can explain this.
As I can see many custom Roms here I keep a hope !
Hi, yes it should be still possible.
DC-Unlocker is what you need. The operation has a cost in credits, 4$ are necessary to unlock the device since it's the cost that DC asks from retrieve bootloader code from your device.
If you're definitely motivated to do it, it's your only chance but luckily it's an acceptable prize.
RedSkull23 said:
Hi, yes it should be still possible.
DC-Unlocker is what you need. The operation has a cost in credits, 4$ are necessary to unlock the device since it's the cost that DC asks from retrieve bootloader code from your device.
If you're definitely motivated to do it, it's your only chance but luckily it's an acceptable prize.
Click to expand...
Click to collapse
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
turboxav said:
Hi,
I'm French and my level in english is not very high.
So I try to unlock my wife's phone but I havbe understood that it is no more possible with the classic way with huawei support.
Does exist another way tu do this ? Or is it definitivly impossible ?
No french forum can explain this.
As I can see many custom Roms here I keep a hope !
Click to expand...
Click to collapse
What you mean by "unlock".
60nine said:
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
Click to expand...
Click to collapse
With my p10 lite with emui 8 it worked. So why not
0
yes
I Have unlock my phone yesterday with dc unlocker
Seppppx said:
You can downgrade (idk if it is possible from emui 8 I don't even own this phone) and then you can follow this tutorial to unlock your bootloader (FOR FREE) https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
Edit : found this guide with HiSuite it may work https://youtu.be/xFCLpgGZEJM
Click to expand...
Click to collapse
Yeah, but not for Huawei P8 Lite 2017 version... I found this to be possible just for older phones (like the original P8 lite) which can be downgraded to Android 5. Newer ones can't be flashed with unsigned firmware (= firmware which is not straight from damn Huawei who decided not to provide the bootloader codes in the first place) so the only way apparently is to use paid software like DC-Unlocker as stated in this official XDA thread --> https://www.xda-developers.com/huawei-honor-unlock-bootloader-fee/
60nine said:
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
Click to expand...
Click to collapse
Unlocked the bootloader yesterday! I have Huawei P8 Lite 2017 PRA-LX1 and had latest Emui 8 build on it... Bought the code for 4€ from DC-Unlocker, and required around 2 minutes for unlocking. You can follow this guide --> https://www.youtube.com/watch?v=4xYybHAlWaQ
I tried so hard to get the code for free, and I know modding should not cost people money. But at the end of the day, I think those 4 euros were worth it
Yeah,4 Euros is ok and the only method!!!
-CALIBAN666- said:
Yeah,4 Euros is ok and the only method!!!
Click to expand...
Click to collapse
And also worth it if we consider fact that our phone is now EMUI free. ?
DunoCZ said:
And also worth it if we consider fact that our phone is now EMUI free.
Click to expand...
Click to collapse
Dear all,
sorry in advance for the silly question but in this regard I am dumb as a brick.
I run DC Unlocker, got the phone unlocked but now the only thing I have is the stock boot telling me the phone is unlocked and therefore cannot be trusted. From there on, I do not know how to procede in order to install TWRP recovery + LineageOS 17.1. I tried to install TWRP but it only runs after a factory reset with the "stock" Huawei eRecovery and every time I reboot (I even got to the point of installing LineageOS via fastboot) it is always back to square one.
Again, sorry, but the last phone I "worked on" was an HTC Desire HD some 8 years ago, therefore you can guess I lost some years of advancements
Thank you for any help regarding the steps I am missing, links to guides much much appreciated.
Best and ciao from Italy
af1985 said:
Dear all,
sorry in advance for the silly question but in this regard I am dumb as a brick.
I run DC Unlocker, got the phone unlocked but now the only thing I have is the stock boot telling me the phone is unlocked and therefore cannot be trusted. From there on, I do not know how to procede in order to install TWRP recovery + LineageOS 17.1. I tried to install TWRP but it only runs after a factory reset with the "stock" Huawei eRecovery and every time I reboot (I even got to the point of installing LineageOS via fastboot) it is always back to square one.
Again, sorry, but the last phone I "worked on" was an HTC Desire HD some 8 years ago, therefore you can guess I lost some years of advancements
Thank you for any help regarding the steps I am missing, links to guides much much appreciated.
Best and ciao from Italy
Click to expand...
Click to collapse
Did you after fastboot oem unlock leave phone format yourself right?
DunoCZ said:
Did you after fastboot oem unlock leave phone format yourself right?
Click to expand...
Click to collapse
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Yeah I get it now, the problem is if you wanna go to twrp sometimes you have to press volume up and hold it until logo shows up, sometimes you had to hold both volume buttons etc. It's kinda wierd but the factory format from erecovery is in twrp disabled due to this because sometimes it wont let you boot until format (that triggers almost anything like fastly restarting to and from recovery etc.).
So keep calm it's "normal".
af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Just for your information, TWRP on this device is not fully supported. Every TWRP version you may find on XDA forums for this particular device is different. In my case TWRP back up doesn't work, wipe cache doesn't work, format data only breaks the system partition , flash GSI's from TWRP also doesn't work XDXD
The only thing I could do from TWRP was flash Magisk and hope that nothing will go wrong in the future ...XD got it? Flash and forget ???
Momin8454 said:
Just for your information, TWRP on this device is not fully supported. Every TWRP version you may find on XDA forums for this particular device is different. In my case TWRP back up doesn't work, wipe cache doesn't work, format data only breaks the system partition , flash GSI's from TWRP also doesn't work XDXD
The only thing I could do from TWRP was flash Magisk and hope that nothing will go wrong in the future ...XD got it? Flash and forget
Click to expand...
Click to collapse
Lol you are dumb...
DunoCZ said:
Lol you are dumb...
Click to expand...
Click to collapse
Well, I didn't had any knowledge of it. Turns out my EMUI version was more recent one that's why I had more issues with TWRP.
And I was just sharing my experience with Honor 8 lite.
DunoCZ said:
Yeah I get it now, the problem is if you wanna go to twrp sometimes you have to press volume up and hold it until logo shows up, sometimes you had to hold both volume buttons etc. It's kinda wierd but the factory format from erecovery is in twrp disabled due to this because sometimes it wont let you boot until format (that triggers almost anything like fastly restarting to and from recovery etc.).
So keep calm it's "normal".
Click to expand...
Click to collapse
Thank you for your support. To reinstate some order in the procedure, yesterday I reinstalled EMUI from eRecovery and now I am back to "zero-point-one", aka right after DC Unlocker: when I switch on the phone it says it is unlocked and then launches stock OS. From now on what should I do to have in the end LineageOS 17.1 installed? Again, thanks for your time
Some advice from a beginner
af1985 said:
Thank you for your support. To reinstate some order in the procedure, yesterday I reinstalled EMUI from eRecovery and now I am back to "zero-point-one", aka right after DC Unlocker: when I switch on the phone it says it is unlocked and then launches stock OS. From now on what should I do to have in the end LineageOS 17.1 installed? Again, thanks for your time
Click to expand...
Click to collapse
Hi!
So, I installed Lineage OS 17.1 on my sister's phone just two days ago, maybe I can give you some advice being myself a beginner. So, first of all, I guess you have enabled OEM unlock (otherwise you could not flash TWRP I guess? I don't think this is the point anyway) If not so, go to Developer Options --> Enable OEM unlock and you will see both the bootloader and FRP unlocked.
The try to follow the DarkJoker360's Lineage OS 17.1 install guide step by step (don't forget to flash the los_patches_prague.zip!). The right version of TWRP is important too for compatibility issues, so install the version he provided.
Anyway, as @DunoCZ pointed out, for entering TWRP recovery you have to press Volume UP button + Power button and keep them pressed until you get to the TWRP. Otherwise, what the device does is either booting up or go to the screen like "Press Volume UP for at least 3 seconds to go to erecovery" and if you do that, it will go into Huawei's own recovery.
Another thing is... Did you do a full wipe (system, data, cache, dalvik/art cache) in TWRP before trying to flash the new ROM? (don't just do the factory reset in Huawei's recovery, I read somewhere it doesn't wipe everything like the advanced one in the custom recovery)
af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Because as you wrote here, the stock OS booted up before you installed stock from again via Huawei erecovery. So my wild guess is that the wipe you did before flashing Lineage OS wasn't a full wipe?
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
By the way, after installing Lineage OS 17.1 I found out there were indeed some very important problems in the ROM as noticed by other testers too...
The reason why I changed the ROM on the device was mainly because of two reasons:
1) Short battery life
2) Not enough memory
And unfortunately, on Lineage OS 17.1:
1) Battery life not good enough. Unless you fix it by patching a new kernel, be always wary of apps running on your device etc., the battery ran short even after replacing the internal battery. Alas. Besides, I wanted something stable for my sis who threatened me to buy an iPhone if I couldn't fix her phone lol
2) Very big problem with memory: I couldn't find a way to write to the SD card as other users pointed out. It is read by the device, but apparently it is read only and even with root permissions I couldn't find a way to obtain write permission for the apps. Perhaps some options in fstab mount file should be changed, but honestly, I tried with my below-average knowledge of Linux and gave up :crying:
But then... I tried Lineage OS 15.1 and this one worked much, much better. Battery life is super good and has the adoptable storage option for the SD card! This way, instead of those 9 gigs of memory now the phone has more than 70! And honestly, this ROM solved both the most important problems of this phone
(PS: sorry for the long posts lol)
(PPS: if you decide to switch to 15.1, remember to decrypt the memory following this post otherwise you won't be able to install more that a bunch of apps on the phone. Besides, remember to flash Dil3mm4 's TWRP recovery)
Jujub said:
Hi!
So, I installed Lineage OS 17.1 on my sister's phone just two days ago, maybe I can give you some advice being myself a beginner. So, first of all, I guess you have enabled OEM unlock (otherwise you could not flash TWRP I guess? I don't think this is the point anyway) If not so, go to Developer Options --> Enable OEM unlock and you will see both the bootloader and FRP unlocked.
The try to follow the DarkJoker360's Lineage OS 17.1 install guide step by step (don't forget to flash the los_patches_prague.zip!). The right version of TWRP is important too for compatibility issues, so install the version he provided.
Anyway, as @DunoCZ pointed out, for entering TWRP recovery you have to press Volume UP button + Power button and keep them pressed until you get to the TWRP. Otherwise, what the device does is either booting up or go to the screen like "Press Volume UP for at least 3 seconds to go to erecovery" and if you do that, it will go into Huawei's own recovery.
Another thing is... Did you do a full wipe (system, data, cache, dalvik/art cache) in TWRP before trying to flash the new ROM? (don't just do the factory reset in Huawei's recovery, I read somewhere it doesn't wipe everything like the advanced one in the custom recovery)
Because as you wrote here, the stock OS booted up before you installed stock from again via Huawei erecovery. So my wild guess is that the wipe you did before flashing Lineage OS wasn't a full wipe?
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
By the way, after installing Lineage OS 17.1 I found out there were indeed some very important problems in the ROM as noticed by other testers too...
The reason why I changed the ROM on the device was mainly because of two reasons:
1) Short battery life
2) Not enough memory
And unfortunately, on Lineage OS 17.1:
1) Battery life not good enough. Unless you fix it by patching a new kernel, be always wary of apps running on your device etc., the battery ran short even after replacing the internal battery. Alas. Besides, I wanted something stable for my sis who threatened me to buy an iPhone if I couldn't fix her phone lol
2) Very big problem with memory: I couldn't find a way to write to the SD card as other users pointed out. It is read by the device, but apparently it is read only and even with root permissions I couldn't find a way to obtain write permission for the apps. Perhaps some options in fstab mount file should be changed, but honestly, I tried with my below-average knowledge of Linux and gave up :crying:
But then... I tried Lineage OS 15.1 and this one worked much, much better. Battery life is super good and has the adoptable storage option for the SD card! This way, instead of those 9 gigs of memory now the phone has more than 70! And honestly, this ROM solved both the most important problems of this phone
(PS: sorry for the long posts lol)
(PPS: if you decide to switch to 15.1, remember to decrypt the memory following this post otherwise you won't be able to install more that a bunch of apps on the phone. Besides, remember to flash Dil3mm4 's TWRP recovery)
Click to expand...
Click to collapse
Check out my SPECTRUM profile I wrote even simple tut how to flash kernel and enable adoptable storage

[Guide] T-Mobile KB2007 11 Locked Bootloader to LOS 12

I just spent several hours working with a t-mobile variant (KB2007), with a locked bootloader that requires a key from oneplus - bought it from ebay on sale, only $200 after discounts. Nice, but who wants to fill out a form and wait a week? I have it running LOS 19 and wanted to share exactly how. It's easily to get it running 18, the first step here will get you to that. The gist is: Downgrade/convert to european, unlock bootloader, install los. I can see why there's a LOT of confusion with this phone, mainly because the install guide on LOS's site omits a few details.
1. Go here: https://forum.xda-developers.com/t/...m-unlock-or-bootloader-unlock-needed.4188491/
Grab that file and unzip it. Shut off your phone, hold volume up and down, insert usb and then let go of the volume keys. Or just reboot it with "adb reboot edl" if your phone is still plugged it. Make sure you have the driver installed! Chances are around 99% it will not be. What I did was unzip to C: and use that as the location. Then select "enum" and make sure your phone shows. Dont change any settings. Then start. It'll take 5 minutes.
2. Now you have the european version, it has much lower restrictions and gets rid of the annoying t-mobile screen. Now go online first (oem unlock will be greyed out and/or adb wont work until you do), enable developer mode, enable oem unlock, enable debug. Reboot into bootloader, unlock it with 'fastboot oem unlock'. Restart and let it do its thing.
3. So far so good, but you're on android 11 still. This doesn't help much, and if you try to use Oxygen Updater, it'll download a version of 12 that will relock it and bug you about a key when you try to unlock it again. Es no bueno!
Hit this thread: https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/
You want "Signed Flashable Zips" then "KB05BA Europe" the first two links for 19 are dead, so grab "KB2003_11_C.20". Transfer it to the root directory of internal storage of your phone, use the updater that lets you select local file. Somebody might want to upload it elsewhere?
4. Now you're on 19, and your bootloader is still unlocked. From here, follow the tutorial: https://wiki.lineageos.org/devices/kebab/install starting with Flashing Additional Partitions. You must also write "fastboot flash boot boot.img" or it will black screen when you reboot your phone's recovery a second time. It was very irresponsible of whoever wrote the tutorial to leave that piece of information out because a lot people complained. Somebody else figured this out, I'm not taking any credit for it but it was hard to find.
5. Ok so, sideload everything. Include mindthegapps and magisk (for some reason, I had to write magisk there, install the apk, and then write it again in recovery). Now you should be done. I've tested my network, 5g, sms, everything works fine for me. One issue: Holding vol up + power kicks me to bootloader, no idea why. Easily fixed by selecting recovery in the menu.
If something goes wrong and you softbrick, reinstall the first step.
Following
I have a KB2007, but am on Android 12 (KB2007_11_C.42). Will this work for A12?
xLoveHateLegend said:
I have a KB2007, but am on Android 12 (KB2007_11_C.42). Will this work for A12?
Click to expand...
Click to collapse
I'm also wondering this. I've been out of the rooting game for a few years and want to get back into it. Did you find an answer to your question?
I'm also wondering what the current instructions are for rooting on OOS12. I'm currently running C_43, latest security patch
kevinco1 said:
I'm also wondering what the current instructions are for rooting on OOS12. I'm currently running C_43, latest security patch
Click to expand...
Click to collapse
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
Will this process work for the OnePlus 8T+ 5G KB2007? I'm not 100% sure about the difference in the partition layout and or hardware (other than the 5G modem). According to GSM Arena, the only difference is the modem's enabled frequencies. https://www.gsmarena.com/compare.php3?idPhone1=10420&idPhone2=10512
karlnorth said:
Will this process work for the OnePlus 8T+ 5G KB2007? I'm not 100% sure about the difference in the partition layout and or hardware (other than the 5G modem). According to GSM Arena, the only difference is the modem's enabled frequencies. https://www.gsmarena.com/compare.php3?idPhone1=10420&idPhone2=10512
Click to expand...
Click to collapse
Same here again....does this work if you're on OS12?
karlnorth said:
Will this process work for the OnePlus 8T+ 5G KB2007? I'm not 100% sure about the difference in the partition layout and or hardware (other than the 5G modem). According to GSM Arena, the only difference is the modem's enabled frequencies. https://www.gsmarena.com/compare.php3?idPhone1=10420&idPhone2=10512
Click to expand...
Click to collapse
The hardware except 5G bands is basically the same, so rooting instructions for all 8T variant should work more or less equally.

Categories

Resources