I've read most of the x722 forum,and it's going aroumd in circles, people asking the same questions, multiple misconceptions and ambiguous answers.
So:
Le eco le pro 3 is called x720 and has snapdragon 821, this thread is for le eco le pro 3 elite which is called x722 and has a snapdragon 820
Stock roms are 20s and 26s, they come with eui, android version 6
Many phones come with modified 20s or 26s whih excludes some chinese app and add gapps
stock 26s has a locked bootloader, information about stock 20s is scarce
batyan has posted a a dev rom which you can flash with the official stock recovery, as a result you can unlock your bootloader. Ie. you get an unlocked bootloader
it is recommended to flash batyan's dev rom before trying to flash twrp regardless of the rom your phone came with(you shouldn't be able to flash anything if your bootloader is locked, but I've read about bricks, so maybe some factory roms allow flashing custom recovery but will then brick because the flashed recovery is not official)
if you flash twrp and try flashing a stock rom after that, you get brick because the stock rom includes a locked bootloader that won't like that you have twrp instead of stock recovery
unbrick: there is a qfil rom for x720, but will not work on x722, maybe it will with some modifications. No qfil for x722 has been released yet.
No info at rifraf or other jtag boxes. Maybe someone will think of a jtag method to unbrick.
x720 and x722 share kernels or so it seems, their respective cpus are snapdragon 821 and 820, the difference comes from a gpu blob and some configs which include the name of the cpu
you can use twrp from CrisbalGreece or use the x720 one, but you need to extract a part of it, since it somehow differs
people are reporting problems related to cameras, deep sleep, slow ui, bad cpu governors, no se linux, no encryption, ir port, bad connectivity, quick charge, leds, buttons, fingerprint reader
Let's keep things simple, if you notice anything wrong or want to add something, please comment.
My next intention is to clarify what are the limitations imposed on custom roms, can we get official support for them, how are they build, etc. We need tutorials on how to build twrp and the custom roms and what makes them custom.
randxor said:
I've read most of the x722 forum,and it's going aroumd in circles, people asking the same questions, multiple misconceptions and ambiguous answers.
So:
Le eco le pro 3 is called x720 and has snapdragon 821, this thread is for le eco le pro 3 elite which is called x722 and has a snapdragon 820
Stock roms are 20s and 26s, they come with eui, android version 6
Many phones come with modified 20s or 26s whih excludes some chinese app and add gapps
stock 26s has a locked bootloader, information about stock 20s is scarce
batyan has posted a a dev rom which you can flash with the official stock recovery, as a result you get an unlocked bootloader
it is recommended to flash batyan's dev rom before trying to flash twrp regardless of the rom your phone came with
if you flash twrp and try flashing a stock rom after that, you get brick because the stock rom includes a locked bootloader that won't like that you have twrp instead of stock recovery
unbrick: there is a qfil rom for x720, but will not work on x722, maybe it will with some modifications. No qfil for x722 has been released yet.
No info at rifraf or other jtag boxes. Maybe someone will think of a jtag method to unbrick.
x720 and x722 share kernels or so it seems, their respective cpus are snapdragon 821 and 820, the difference comes from a gpu blob and some configs which include the name of the cpu
you can use twrp from CrisbalGreece or use the x720 one, but you need to extract a part of it, since it somehow differs
people are reporting problems related to cameras, deep sleep, slow ui, bad cpu governors, no se linux, no encryption, ir port, bad connectivity, quick charge, leds, buttons, fingerprint reader
Let's keep things simple, if you notice anything wrong or want to add something, please comment.
My next intention is to clarify what are the limitations imposed on custom roms, can we get official support for them, how are they build, etc. We need tutorials on how to build twrp and the custom roms and what makes them custom.
Click to expand...
Click to collapse
Hi. Incorrect 5 and 6.
5. All EUI roms come with locked bootloader. Stock 26S (and official WIXCNFN5802005041S) prevent you from unlocking, others (20S) NO.
5.1 The only way to get out of an official rom that does not let unblock bootloader, is to install another official rom that allows it (official is NOT via fastboot). Currently the only official rom that exists, which allows unlock, is 01D, but when there is another one, it can be used as well.
6. This is incorrect. You can install TWRP from any ROM that allows you to unlock bootloader. There is no danger in installing twrp as long as it is compatible with X722. The roms that do not allow unlocking (26S stock) simply prevents you from installing anything that is not official, there is no danger because it DOES NOT LEAVE YOU.
There is a fake legend about X722. The only danger is to install an incompatible rom that prevents you from accessing recovery (which is difficult) or install 26S stock (or official WIXCNFN5802005041S) from TWRP or other recovery other than the official one.
Greetings.
F.J.V said:
Hi. Incorrect 5 and 6.
5. All EUI roms come with locked bootloader. Stock 26S (and official WIXCNFN5802005041S) prevent you from unlocking, others (20S) NO.
5.1 The only way to get out of an official rom that does not let unblock bootloader, is to install another official rom that allows it (official is NOT via fastboot). Currently the only official rom that exists, which allows unlock, is 01D, but when there is another one, it can be used as well.
6. This is incorrect. You can install TWRP from any ROM that allows you to unlock bootloader. There is no danger in installing twrp as long as it is compatible with X722. The roms that do not allow unlocking (26S stock) simply prevents you from installing anything that is not official, there is no danger because it DOES NOT LEAVE YOU.
There is a fake legend about X722. The only danger is to install an incompatible rom that prevents you from accessing recovery (which is difficult) or install 26S stock (or official WIXCNFN5802005041S) from TWRP or other recovery other than the official one.
Greetings.
Click to expand...
Click to collapse
Thanks for reading it and takig the time to comment.
5. Basically speaking, I don't see any mistakes in my information. To unlock, you need batyan's rom. (as there is no other official rom that allows unlocking).People have reported possible issues with unlocking on factory 20s regardless of whether their phones came with 20s modified or stock. I don't want to make guarantees based on blacklist. Ie. Tell people that if the version is not X it's all good, since there are many versions those phones come with.
6. I don't see how your information differs with mine.
Hello, there is only one point where I disagree with you. What you say about points 5 and 6 DOES NOT HAVE ANYTHING TO SEE, with what I say.
You say in 5)batyan has posted a a dev rom which you can flash with the official stock recovery, as a result you can unlock your bootloader. Ie. you get an unlocked bootloader
I say in 5) All roms come with locked bootloader. 26S stock DOES NOT let unlock.
You say in 6)it is recommended to flash batyan's dev rom before trying to flash twrp regardless of the rom your phone came with(you shouldn't be able to flash anything if your bootloader is locked, but I've read about bricks, so maybe some factory roms allow flashing custom recovery but will then brick because the flashed recovery is not official)
I say in 6) DO NOT install 01D to install TWRP. It is unnecessary and wasted time.
Now, if you keep thinking we say the same, it seems perfect .
Greetings.
F.J.V said:
Hello, there is only one point where I disagree with you. What you say about points 5 and 6 DOES NOT HAVE ANYTHING TO SEE, with what I say.
You say in 5)batyan has posted a a dev rom which you can flash with the official stock recovery, as a result you can unlock your bootloader. Ie. you get an unlocked bootloader
I say in 5) All roms come with locked bootloader. 26S stock DOES NOT let unlock.
Click to expand...
Click to collapse
So what about this user, who reports that his device is already unlocked in fastboot mode without him having to do anything? Is it actually unlocked or no? https://forum.xda-developers.com/showpost.php?p=75160935&postcount=46
You say in 6)it is recommended to flash batyan's dev rom before trying to flash twrp regardless of the rom your phone came with(you shouldn't be able to flash anything if your bootloader is locked, but I've read about bricks, so maybe some factory roms allow flashing custom recovery but will then brick because the flashed recovery is not official)
I say in 6) DO NOT install 01D to install TWRP. It is unnecessary and wasted time.
Greetings.
Click to expand...
Click to collapse
EDIT: Whoops, wrong information. It wasn't you that said that, but another user.
Also, can I flash stock ROMs through TWRP or no? Why? Say I want to go from LineageOS to Banggood 20s, or Gearbest 20s.
I'm really confused here.
Can you confirm that regardless of the rom, trying to unlock the bootloader will not lead to brick? And that if it says that it's unlocked, it's really unlocked?
Can you confirm that you can flash twrp only if it's unlocked? Because if you're able to flash twrp with a locked bootloader it's obvious that you will get a brick.
sk8223 said:
So what about this user, who reports that his device is already unlocked in fastboot mode without him having to do anything? Is it actually unlocked or no? https://forum.xda-developers.com/showpost.php?p=75160935&postcount=46
But apparently some 20s ROMs don't allow unlocking. Like the Banggood 20s ROM. You said this yourself: https://forum.xda-developers.com/showpost.php?p=74893268&postcount=91
Maybe the Banggood ROM is based on WIXCNFN5802005041S. IDK.
Also, can I flash stock ROMs through TWRP or no? Why? Say I want to go from LineageOS to Banggood 20s, or Gearbest 20s.
I'm really confused here.
Click to expand...
Click to collapse
Well, I've mentioned it above. From what I've read it seems stock roms include bootloaders which are locked. Flashing with twrp will lead to having a locked bootloader plus tqrp and stock stuff. The locked bootloader will see that you have twrp instead of stock recovery and brick you. Bad bootloaders..
sk8223 said:
So what about this user, who reports that his device is already unlocked in fastboot mode without him having to do anything? Is it actually unlocked or no? https://forum.xda-developers.com/showpost.php?p=75160935&postcount=46
But apparently some 20s ROMs don't allow unlocking. Like the Banggood 20s ROM. You said this yourself: https://forum.xda-developers.com/showpost.php?p=74893268&postcount=91
Maybe the Banggood ROM is based on WIXCNFN5802005041S. IDK.
Also, can I flash stock ROMs through TWRP or no? Why? Say I want to go from LineageOS to Banggood 20s, or Gearbest 20s.
I'm really confused here.
Click to expand...
Click to collapse
Hi.
The bangood roms can be unlocked. I have never said that a bangood rom can not be unlocked, but I do not know if they ever change.
But that's not a problem, you can or can not, there is no danger to try. If you can not then and only then go through 01D first, there is no danger of brick.
I do not know if the ROM 26 of bangood that you mention came with bootloader unlocked or the user or someone unlocked it without realizing it. The important thing is that that rom can be unlocked, because it's not a 26S stock, it's a 26S modified. The bangood 26S does NOT have the problem of preventing the unlocking, at least until now, but as I said before, there is no danger, you can or can not, there is no danger of brick to try.
I have NEVER said that some bangood 20s can not be unlocked. I have the 20S of bangood and IF it can be unlocked, and IF you can install TWRP without first installing 01D.
I have commented that there are some 20S, that I do not know who sells them, but I do not think it is bangood, which does not allow unlocking, because it brings the same system as the 26S stock, it is also a 20S stock, it is not the modified 20S of bangood. That ROM I said it is the WIXCNFN5802005041S, that whenever stock has the same locking system as the 26S, but if it is not stock and have already modified it, I suppose they take away the blocking system.
I have a copy of that rom, but in fastboot format, and it comes with its own recovery, therefore if the rom exists, there may be terminals that have it installed. I do not publish it because it is able to brike a terminal if someone installs it without original recovery. But the fault is not TWRP is the very ROM that has that system of "protection" before modifications.
I hope it has been a little clearer.
Greetings.
P.D. The answer was from the previous quote, I see that something has changed but I guess it is understood
F.J.V said:
Hi.
The bangood roms can be unlocked. I have never said that a bangood rom can not be unlocked, but I do not know if they ever change.
Click to expand...
Click to collapse
Oh whoops, that wasn't you that I quoted! It was a different person. I apologize. I don't know why I didn't read the username.
Also, can you please confirm whether or not we can flash stock ROMs through TWRP? Does the stock ROM actually contain the stock bootloader, as randxor surmises?
Say, if we want to go back to a stock 20s ROM from a custom ROM. Thanks.
But the fault is not TWRP is the very ROM that has that system of "protection" before modifications.
Click to expand...
Click to collapse
I know this applies to the official 26s ROM, but not the stock 20s vendor ROMs from Banggood and the rest, right? So there's no issue flashing those through TWRP?
sk8223 said:
Oh whoops, that wasn't you that I quoted! It was a different person. I apologize. I don't know why I didn't read the username.
Also, can you please confirm whether or not we can flash stock ROMs through TWRP? Does the stock ROM actually contain the stock bootloader, as randxor surmises?
Say, if we want to go back to a stock 20s ROM from a custom ROM. Thanks.
I know this applies to the official 26s ROM, but not the stock 20s vendor ROMs from Banggood and the rest, right? So there's no issue flashing those through TWRP?
Click to expand...
Click to collapse
I can not keep responding, lack of time, but:
You can not install 26S stock or WIXCNFN5802005041S stock from twrp. It will cause brick, NOT DUE TO TWRP, the rom will.
YOU CAN NOT install TWRP in the 26S stock, BECAUSE YOU CAN NOT. Let's be clear, if you can not unlock bootloader you CAN NOT INSTALL TWRP. It's not that you should not, IT'S THAT YOU CAN NOT. If it is installed it IS NOT 26S STOCK is 26S modified and the bootloader is not blocked.
Let's be clear, I do not know in other terminals, but the LEECO LE PRO 3 ELITE if the bootloader can not be unlocked you CAN NOT INSTALL ANYTHING. YOU CAN NOT INSTALL TWRP, so there is no danger for trying, it will not leave you. You can only install an official ROM in zip format
Finally, the only official LEECOO ROMs I know (and which are in zip signed) are:
26S Stock
01D
WIXCNFN5802005041S stock (but this is not in zip signed, it is in fastboot format)
I do not know more official roms, of those 3 01D does not have the brick system, the other two SI.
As far as I know no terminal is sold with official ROM, except for one that came with WIXCNFN5802005041S. The others are not official, they are modified. Keep in mind that this terminal is not for sale outside China, therefore those that sell are modified to include languages.
With regard to returning to a stock 20S ... the only one I know is the stock WIXCNFN5802005041S so NO, but YES you can return without problems to a 20S like the banggood that is not stock.
If someone knows another stock that says so.
Greetings.
F.J.V said:
With regard to returning to a stock 20S ... the only one I know is the stock WIXCNFN5802005041S so NO, but YES you can return without problems to a 20S like the banggood that is not stock.
If someone knows another stock that says so.
Greetings.
Click to expand...
Click to collapse
Alright, so vendor ROMs are a-okay to be flashed through TWRP if you want to return to stock, but not official 26s (as we already know) or WIXCNFN5802005041S, which I think is a Chinese-only ROM? Either way, I won't mess about with either one. This phone bricks too easily. :/
Thanks!
So from all of this the implication is that you can try unlocking the bootloader, if unable => flash dev rom, after that unlock and flash twrp and off to custom rom.
Then how did people get bricks? Only flashing stock via twrp?
We need to gather info on different roms: bangood, aliexpress, gearbest, etc.
sk8223 said:
So what about this user, who reports that his device is already unlocked in fastboot mode without him having to do anything? Is it actually unlocked or no? https://forum.xda-developers.com/showpost.php?p=75160935&postcount=46
Click to expand...
Click to collapse
I see where the confusion resides. So I have changed the title and removed the word stock to include from Banggood.
When I received my phone and I checked, I saw it was on 26S. I thought that given the phone came with 26S, it should be the stock rom which LEECO itself has placed on it. I didn't know that companies like banggood would replaced the rom of LEECO with a modified version they have created (please correct me if I am wrong here).
I have not unlocked it nor have I used an update.zip file through recovery to make it 26S. It came like this. The bootloader appears to be unlocked out of the box from banggood vendor even if the rom shows 26S. The rom have gapps. So I assume that bangood must have installed a 26S rom with gapps which may be similar to CrisBalGreece's 26S version since LEECO STOCK (any version i.e., 20S or 26S) rom does not come with gapps.
If I understand correctly, if you install CBG's 26S on your mobile and check your bootloader through fastboot, you will see that it is unlocked (like in my case) and if you check your rom version, it will be 26S (like in my case). That is why I say that maybe the rom I have received from banggood may be similar to CBG's 26S EUI rom. Can someone who have flashed CBG 26S confirm that, please?
And if it is safe to flash TWRP on CBG's 26S, it should be safe to flash TWRP on my 26S rom. Does that make any sense?
I think this is what @F.J.V tried to explain. If the bootloader is not locked, there is no reason to install 01D since the purpose of 01D is to be used to unlock a locked bootloader only.
Cheers,
S
---------- Post added at 10:02 PM ---------- Previous post was at 09:38 PM ----------
randxor said:
So from all of this the implication is that you can try unlocking the bootloader, if unable => flash dev rom, after that unlock and flash twrp and off to custom rom.
Then how did people get bricks? Only flashing stock via twrp?
We need to gather info on different roms: bangood, aliexpress, gearbest, etc.
Click to expand...
Click to collapse
I am not sure, but I think when people got their phone, they wanted the latest version of the OS. So when they saw that leeco released a new rom which is 26S (this is the stock rom which needs to be renamed to update.zip and flashed through recovery) and they were on 20S or older. They flashed the 26S from leeco and now their bootloader becomes locked.
They want to flash twrp to use custom rom like PA or LOS, or other.
**** What do they do next?? Were they able to flash twrp or blocked bootloader does not allow twrp to be copied to device?****
This is the part which is confusing. The next step will either succeed or brick the phone. This is the information we need to gather from all people, either brick or not.
Cheers,
S
randxor said:
Then how did people get bricks? Only flashing stock via twrp?
We need to gather info on different roms: bangood, aliexpress, gearbest, etc.
Click to expand...
Click to collapse
EDIT: flashing 26s without the stock LeEco recovery in place causes a brick.
dakok summed up the different ROMs in an image here: https://forum.xda-developers.com/showpost.php?p=74010858&postcount=23
sk8223 said:
Because they flashed 26s, an official update. Just don't flash stock 26s. They got bricks because they updated to stock 26s and then flashed TWRP and then something through TWRP.
dakok summed up the different ROMs in an image here: https://forum.xda-developers.com/showpost.php?p=74010858&postcount=23
Click to expand...
Click to collapse
You still do not understand it
Brick occurs when:
Install 26S Stock from any ROM, and DO NOT HAVE THE ORIGINAL RECOVERY.
To install 26S Stock without causing brick, INSTALL FROM A ROM EUI through update.zip, AND THAT THE TERMINAL HAS RECOVERY ORIGINAL.
If you install 26S stock from any rom with a recovery other than the original ... brick.
And for the last time, if you have 26S Stock IT IS IMPOSSIBLE TO INSTALL TWRP, I think I have said it more than once
Greetings.
F.J.V said:
You still do not understand it
Brick occurs when:
Install 26S Stock from any ROM, and DO NOT HAVE THE ORIGINAL RECOVERY.
To install 26S Stock without causing brick, INSTALL FROM A ROM EUI through update.zip, AND THAT THE TERMINAL HAS RECOVERY ORIGINAL.
If you install 26S stock from any rom with a recovery other than the original ... brick.
And for the last time, if you have 26S Stock IT IS IMPOSSIBLE TO INSTALL TWRP, I think I have said it more than once
Greetings.
Click to expand...
Click to collapse
Alright, but in the end there's very little reason to install stock 26s to begin with. A very troublesome firmware that doesn't seem to bring any improvements to the table. Modded 26s seems to be better.
I wish a mod would sticky this information for others to see.
I am not convinced that flashing stock via twrp is the only way to brick and that you can't brick by say somehow flashing twrp with a locked bootloader.(which people are saying should be impossible), but what if one of the modified vendor roms still has sign checks for recovery, boot, etc. but it also allows flashing and says the bootloader is unlocked(maybe the checks are in the rom itself, so even if the bootloader is unlocked, the rom itself isn't)
Related
Been searching for weeks now...asked here on another forum but not really getting any answers.
Can someone who knows how to flash TWRP or CWM please, please, please come forth with an instruction or a link to instruction on how to do so?
Reason i want to flash a custom recovery is because my phone failed an update and is now stuck on recovery. I want to backup my data before flashing ROM.
Mind you, i didn't have bootloader unlocked prior to the failed update. I just had it rooted using king root. I am not sure if it is mandatory for bootloader to be unlocked before flashing any custom recovery. Is it???
If yes, then since OS isnt loading, i won't be able to "install" anything to unlock bootloader. Therefore, is there a way to "flash"-unlock bootloader in order to flash the custom recovery? Is there a way around flashing a custom recovery on a phone that doesn't have bootloader unlocked and is now stuck on the stock recovery?
Basically i just want to backup by data. It doesnt have to be through the flashing-custom-recovery-in-order-to-backup-data method. Any method that will do the job is perfectly fine with me . I am inquiring about this method because all my searches led me to only this solution? Any other solutions are welcomed.
Thanks in advance!
freefallin said:
Been searching for weeks now...asked here on another forum but not really getting any answers.
Can someone who knows how to flash TWRP or CWM please, please, please come forth with an instruction or a link to instruction on how to do so?
Reason i want to flash a custom recovery is because my phone failed an update and is now stuck on recovery. I want to backup my data before flashing ROM.
Mind you, i didn't have bootloader unlocked prior to the failed update. I just had it rooted using king root. I am not sure if it is mandatory for bootloader to be unlocked before flashing any custom recovery. Is it???
If yes, then since OS isnt loading, i won't be able to "install" anything to unlock bootloader. Therefore, is there a way to "flash"-unlock bootloader in order to flash the custom recovery? Is there a way around flashing a custom recovery on a phone that doesn't have bootloader unlocked and is now stuck on the stock recovery?
Basically i just want to backup by data. It doesnt have to be through the flashing-custom-recovery-in-order-to-backup-data method. Any method that will do the job is perfectly fine with me . I am inquiring about this method because all my searches led me to only this solution? Any other solutions are welcomed.
Thanks in advance!
Click to expand...
Click to collapse
First things first: What model is your phone? Is it the X2-CU (International), X2-EU (Russia, Europe and the Middle East), and the Vibe X2-AP (Indonesia, India, etc.) or the X2-TO (China Only). I can help you if it is the X2-CU or the X2-EU versions. Also, you DO NOT have to unlock the bootloader of this phone to install custom recovery. I know, it's weird, but it's true. If you tell me which model it is, I can give you the files needed to flash custom recovery. Good luck
Yoshi_Guy said:
First things first: What model is your phone? Is it the X2-CU (International), X2-EU (Russia, Europe and the Middle East), and the Vibe X2-AP (Indonesia, India, etc.) or the X2-TO (China Only). I can help you if it is the X2-CU or the X2-EU versions. Also, you DO NOT have to unlock the bootloader of this phone to install custom recovery. I know, it's weird, but it's true. If you tell me which model it is, I can give you the files needed to flash custom recovery. Good luck
Click to expand...
Click to collapse
OH BEAUTIFUL! Just when i was about to sink into depression. You are a life saver buddy!
It's X2-EU
Mine is X2-AP, can you give me the link to CWM Recovery?
Just a heads up. I've got my RMP since today. As a usual nexus user as I was, the first thing was to unlock the bootloader and flash whatever I can. My destination was -> unlocked bootloader -> smiui with root.
What happened it the following:
1) I unlocked my bootloader following guides (unofficial way)
2) Installed TWRP
3) Flashed SMIUI
And welcome brick. I was in emergency port (9003), and the only way to get the device running was the disasembe way. Well it worked. Now I'm on 7.2.3 with root, but guys - watch what you are flashing. This is my 3rd device (Desire HD, Nexus 4, and now RMP), and this was the first time that I had such a headaches.
SMIUi contains the locked bootloader file, so if by any chance you decide to unlock it by the unofficial way - don't flash it.
Read...read....read and one more time read there are many threads explaining how to do it without getting bricked .
Yup already lernt my lesson. Deleting emmc_appsboot.mbn from the archive before flashing is the right way.
Anyway, SMIUI is totally unusable on our devices. Flashed 6.4.21 and 6.4.14 - on both of them I get no sim/no wifi. Can't connect the device to the PC in file transfer mode also. Now I'm running xiaomi.eu 6.4.21 without issues.
ktomov said:
Yup already lernt my lesson. Deleting emmc_appsboot.mbn from the archive before flashing is the right way.
Anyway, SMIUI is totally unusable on our devices. Flashed 6.4.21 and 6.4.14 - on both of them I get no sim/no wifi. Can't connect the device to the PC in file transfer mode also. Now I'm running xiaomi.eu 6.4.21 without issues.
Click to expand...
Click to collapse
Hello ktomov,
I made the same mistake. I couldn’t wait 10 days for the official unlock so I used the unofficially unlocked bootloader. Then I flashed TWRP and a Xiaomi EU ROM thinking that it’s probably gonna be OK since that’s not an official Xiaomi ROM. Nope! Bricked my device and had to use the testpoint method.
Now my question for you is what to do if want to flash a Xiaomi EU ROM again in case I don’t get the official unlock permission (is it even possible that I don’t get it?). Do I just need to replace the emmc_appsboot.mbn in the ROM’s ZIP file? I’m asking because there is a huge thread on this forum on how to maintain future OTA updates with unofficial unlock and I’d rather just stick with a TWRP-compatible ROM.
just refer to this thread if you flash anything on a unofficially unlocked bloader and ALWAYS DELETE emmc_appsboot.mbn
http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
oh and as far as sMiui goes, dunno bout you, but it worked for me. it lags like hell, but it works. I had no issues with sim/wifi, and as far as MTP mode goes, disable adb in developer opts, that will trigger MTP mode. kinda annoying, but should work. same thing is happening on xiaomi eu and global roms too.
sikica133 said:
just refer to this thread if you flash anything on a unofficially unlocked bloader and ALWAYS DELETE emmc_appsboot.mbn
http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
Click to expand...
Click to collapse
Thanks. That should make sure I don’t hardbrick my phone and retain access to EDL mode. But my question is whether replacing the emmc_appsboot.mbn is all I need to do when flashing a TWRP compatible ROM. No other scripts or changes are necessary?
Hvala u svakom slučaju.
sikica133 said:
just refer to this thread if you flash anything on a unofficially unlocked bloader and ALWAYS DELETE emmc_appsboot.mbn
http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
oh and as far as sMiui goes, dunno bout you, but it worked for me. it lags like hell, but it works. I had no issues with sim/wifi, and as far as MTP mode goes, disable adb in developer opts, that will trigger MTP mode. kinda annoying, but should work. same thing is happening on xiaomi eu and global roms too.
Click to expand...
Click to collapse
Don't know what is going on with those roms, but for me sMiui 6.4.14 and 6.4.21 gives no-sim/no-wifi. Disabling dev still didn't got me to mtp. Haven't got such issues with xiaomi.eu roms though. 6.4.14 and 6.4.21 works like they should.
Filip013 said:
Thanks. That should make sure I don’t hardbrick my phone and retain access to EDL mode. But my question is whether replacing the emmc_appsboot.mbn is all I need to do when flashing a TWRP compatible ROM. No other scripts or changes are necessary?
Hvala u svakom slučaju.
Click to expand...
Click to collapse
Don't replace it. Just delete it from the archive prior flashing.
ktomov said:
Don't know what is going on with those roms, but for me sMiui 6.4.14 and 6.4.21 gives no-sim/no-wifi. Disabling dev still didn't got me to mtp. Haven't got such issues with xiaomi.eu roms though. 6.4.14 and 6.4.21 works like they should.
Don't replace it. Just delete it from the archive prior flashing.
Click to expand...
Click to collapse
Roger that!
So if you have unlocked the bootloader the unofficial way is there any way to flash a locked bootloader later on if for example you wish to give in you phone for repair at the service center?
devtherockstar said:
So if you have unlocked the bootloader the unofficial way is there any way to flash a locked bootloader later on if for example you wish to give in you phone for repair at the service center?
Click to expand...
Click to collapse
unlocking bootloader does not void your warranty
Note: You can try this with EU ROMs but I'm not sure if it will work, and won't be testing to see if it works, since I see no reason to flash EU ROMs anyways.
I knew this from day 1, but was switching between various LOS ROMs so didn't have much inspiration to make a guide. Now i'm switching back to Stock-based ROMs (due to other roms having no dolby, no voice capture,...), I'll be making a guide
I'm not responsible for bricked device.
This is a guide for those who are facing issues when trying to flash US, EU stock and stock-based ROMs on the chinese axon 7 (no signal, no wifi, worse battery, or simply not booting after splash screen). Since downgrading is also a part of this guide, I will also be covering how to downgrade Nougat 7.1.1 ROMs back to 6.0.1 Marshmallow.
Important thing to note:
You must be on B13, 6.0.1 marshmallow with stock recovery, and please, DO NOT UPDATE TO B10 China NOUGAT or anything above ! This will cause a lot of problem, as from what I've deduced, US B19 is based on the China B09 update, anything above B10 won't be backwards compatible. and will cause problems like not booting, (or no wifi, signal etc after you recover the boot partition through recovery)
Now, if you're already on Nougat and want to try this guide, downgrade back to Marshmallow using EDL. Try this guide:
- Download B13 EDL (credits to djkuz from 4pda), extract it
- Download and install the latest Xiaomi MiFlash (stable or beta)
- Turn off your phone, plug it in to your PC, Hold Power + Vol Up + Vol Down, go to device manager, look for the "Port" section, and you will see something like Qualcomm HS-USB QDLoader 9008., if you see it, proceed down below. If not try again.
- right click , open properties on the Qualcomm HS-USB QDLoader 9008, go to port settings, if you see the speed is at 9600 bits per second (bps), change it to 128000 (you can skip this step, but doing it will increase your flashing speed)
- Open MiFlash, press select and pick the folder you extracted a few steps ago.
- Press refresh, if you see your device appearing on the list, press flash. (if some random errors appear, unplug the device, plug it back and immediately press refresh and press flash)
- After flashing you'll be back on B13 China Marshmallow.
REMEMBER, DON'T OTA UPDATE IF YOU WANT A SMOOTH TRANSITION TO US ROMS:
Now, to the good part:
- Download the B09 China OTA package from here (credits to Demons-77)
- put the package into your EXTERNAL sd card, internal won't do.
- reboot to recovery (Power + Vol Up)
- select the option with the word "sd" on it
- now go and pick the package that you just put in
- It will begin flashing and after that, you will have B09 China Nougat
- reboot to bootloader and install recovery (fastboot flash recovery *your file name*)
- after that you can install any roms you like, no need to backup and restore the boot partition every time you flash a US ROM, and you won't encounter strange issues like no boot, no wifi, etc.
TL;DR for those who already know how to do most of these: go back to China Marshmallow through EDL, update to B09 China Nougat with stock recovery, install TWRP and then flash whatever US stock or stock-based roms you want (just like how you would with a US phone)
Does custom kernels work after installing US roms?
I want to have a magisk compatible rom but I don't want to install custom roms other than stock.
Chinese roms doesn't boot with these existing kernels in this forum.
otaconremo said:
Does custom kernels work after installing US roms?
I want to have a magisk compatible rom but I don't want to install custom roms other than stock.
Chinese roms doesn't boot with these existing kernels in this forum.
Click to expand...
Click to collapse
what do you mean by magisk compatible rom? I'm running the latest badboyz with magisk root here, no problems at all
spiwar said:
what do you mean by magisk compatible rom? I'm running the latest badboyz with magisk root here, no problems at all
Click to expand...
Click to collapse
Ok that's great. Last time I tried badboyz, I get issues with my signal keep restarting. I'm currently using chinese B01 mifavor5. all is well, just that I can't use magisk due to the stock kernel.
Thanks for your feedback OP.
Hi, great tutorial, but I got few questions. Now I'm on chinese nougat (B15) and if I downgrade to mm, will still I be able to do this operation? Can I relock bootloader on US rom? Because some apps like android pay, pokemon go and snapchat won't work.
@spiwar Mate I could kiss you right now. But could you just point me to one of the us stock ROMs to flash? (E.g, is this one alright - A2017UV1.1.0B19_StockSystem_by_DrakenFX.zip)
Is it safe to perform ota updates of the USA firmware on Chinese axons? Cheers
Fuilares said:
Hi, great tutorial, but I got few questions. Now I'm on chinese nougat (B15) and if I downgrade to mm, will still I be able to do this operation? Can I relock bootloader on US rom? Because some apps like android pay, pokemon go and snapchat won't work.
Click to expand...
Click to collapse
Downgrading IS a part of this operation if you're already on Nougat (you need to go back to MM before you can go B09 Nougat). Why relock your BL though? Magisk root can work with Android Pay, Pokemon Go AFAIK, not sure though (since I don't use any of those apps)
tigrey said:
@spiwar Mate I could kiss you right now. But could you just point me to one of the us stock ROMs to flash? (E.g, is this one alright - A2017UV1.1.0B19_StockSystem_by_DrakenFX.zip)
Is it safe to perform ota updates of the USA firmware on Chinese axons? Cheers
Click to expand...
Click to collapse
Yes that stock ROM will be okay. Personally I'm using the latest version of BadBoyz ROM.
No you can't. Because OTA updates requires the stock recovery, and your phone probably won't boot if you flash the US Stock recovery
otaconremo said:
Ok that's great. Last time I tried badboyz, I get issues with my signal keep restarting. I'm currently using chinese B01 mifavor5. all is well, just that I can't use magisk due to the stock kernel.
Thanks for your feedback OP.
Click to expand...
Click to collapse
Magisk won't work if you're using B10 Chinese as a base (as mentioned above), if you flash on B10 you'll have to flash the boot portion from the stock Chinese ROM for the US ROMs to even boot, and then you just lose magisk.
I see. Thanks for the tips. But I don't think I'll be coming back to b13 mm for that. I hate restoring data ang all the files in my internal storage.
Hi!
Could you please clarify me a doubt?
To follow this guide, must my device already be rooted?
Thanks!
Well, first part went well. After a lot of effort, because device was recognised as DFU. Anyway, I got it back to B13 with stock recovery.
On second part, when I try installing the FOTA update, it fails, giving me error: status 8. In update history, it says that the system package did not match the phone. Obviously I have A2017.
Any suggestions?
So I just unpacked my MOTO Z with great anticipation.
However, I immediately ran into the issue where I can't backup my old phone using TiBU and restore it on my new shining gadget. I was VERY unsuccessful rooting the device.
So I went all in and installed RR which I'm using on all other devices as well. Used this TWRP to do it.
While RR is working well, it doesn't have some of the nice things stock ROM had, like the keyboard adjustability, screen on on hand-over and some adjustments in the camera app. Doesn't really matter, but I'd like to give stock another try before I inevitably commit to RR which will no doubt improve in the mean time as well.
Now, for my problem:
Using the recovery mentioned above, I made a full backup of the phone before I messed with it. Now that same recovery doesn't properly restore that backup: the phone doesn't boot when I restore that backup. it never leaves the bootloader unlocked warning screen.
So I figured: bad backup, let's get a stock image. Eh, again no go: motorola doesn't even publish those. So I grabbed the XT1650-03_GRIFFIN_RETEU... from here.
That one again doesn't even fully flash: I tried partial flash (system partition + recovery partition) - which flashed but didn't boot; then tried full flash, starting with the gpt.bin - but this one didn't even flash. reported some errors and that was it.
So, while not bricked, I'm far from any degree of control over my new phone. I'd like to improve that!
Any advice?
@velis74 to flash firmware you must use adb/fastboot. Is that what you mean by "flashed"?
lollyjay said:
@velis74 to flash firmware you must use adb/fastboot. Is that what you mean by "flashed"?
Click to expand...
Click to collapse
Yes, "flashing" of the "stock image" I tried to do with fastboot - that series of commands flashing one partition after another with images in the archive. I just didn't want to list all those commands in the post because there's more than 20...
If you´ve already updated your Stock, untouched and locked ROM from Marshmallow to Nougat, then you won't be able to Flash back to Marshmallow Stock ROM, because your Bootloader was already updated to Nougat. That's why the whole process fails. Since there's no official RETEU Nougat Stock ROM yet, use the RETBR one. It's practically the same and works as it should: https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
But keep in mind that you won't be able to relock your bootloader, since Motorola/Lenovo haven't released signed Nougat Stock ROMs yet.
doree said:
If you´ve already updated your Stock, untouched and locked ROM from Marshmallow to Nougat, then you won't be able to Flash back to Marshmallow Stock ROM, because your Bootloader was already updated to Nougat. That's why the whole process fails. Since there's no official RETEU Nougat Stock ROM yet, use the RETBR one. It's practically the same and works as it should: https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
But keep in mind that you won't be able to relock your bootloader, since Motorola/Lenovo haven't released signed Nougat Stock ROMs yet.
Click to expand...
Click to collapse
Yep, was just about to post how this thread helped. I'm back at stock and seriously contemplating not rooting. I pretty much only need it for one app where I forgot the password and they make it REALLY hard to reset it
I don't know why I saw everywhere that, to update from 10.0.3.0 Global Stable to Beta 8.10.25, you could only do with unlocked BL (even using XiaoMiTool it says that).
This is because I can say that I was able to do the update, not via OTA (it fails with an error message explained below) or via EDL, but via other method with a locked BL, no root and no custom recovery. To clarify, I'm using a Global Version of the Mi 8, with the Chinese Version i'ts probably not possible but I'm not sure since I did not test it, but from what I read it's not safe.
So here's what I did:
I used Xiaomi ADB: ht tp://ww w.xiaomit ool.co m/adb (just aggregate to make a link, I can't post links yet), and just install and follow the steps on the site and you are good to go
In the process, the first time it logged an error on the console that already happened when I tried to update via OTA updater (something like "Your android version is different from the current one and bla bla bla...") but right in the next attempt was successfull (the attempts are done automatically). Also, nothing was erased during the process, all data was kept which is nice
Link for the ROM: htt p://bigo ta.d.miui.co m/8.10.25/miui_M I8Global_8.10.25_f598e a6e8b_9.0.zip (no spaces ofc)
dugapila said:
i don't know why i saw everywhere that, to update from 10.0.3.0 global stable to beta 8.10.25, you could only do with unlocked bl (even using xiaomitool it says that).
This is because i can say that i was able to do the update, not via ota (it fails with an error message explained below) or via edl, but via other method with a locked bl, no root and no custom recovery. To clarify, i'm using a global version of the mi 8, with the chinese version i'ts probably not possible but i'm not sure since i did not test it, but from what i read it's not safe.
So here's what i did:
I used xiaomi adb: Ht tp://ww w.xiaomit ool.co m/adb (just aggregate to make a link, i can't post links yet), and just install and follow the steps on the site and you are good to go
in the process, the first time it logged an error on the console that already happened when i tried to update via ota updater (something like "your android version is different from the current one and bla bla bla...") but right in the next attempt was successfull (the attempts are done automatically). Also, nothing was erased during the process, all data was kept which is nice
Click to expand...
Click to collapse
although you have successfully do it., it was still a very risky move. If you brick the phone with bootloader locked, it will be very troublesome procedure afterwards. I do not encourage people to risk their phone. Just unlock your phone bootloader first. A month wait worth more then bricking your phone with locked bootloader>
AzleeKarliff said:
although you have successfully do it., it was still a very risky move. If you brick the phone with bootloader locked, it will be very troublesome procedure afterwards. I do not encourage people to risk their phone. Just unlock your phone bootloader first. A month wait worth more then bricking your phone with locked bootloader>
Click to expand...
Click to collapse
I don't know why it's risky. As long as i have global version and flash an official mi ROM (with version equal or greater than what I have, even if it's beta version) I think I'm fine, why do you think it's risky?
dugapila said:
I don't know why it's risky. As long as i have global version and flash an official mi ROM (with version equal or greater than what I have, even if it's beta version) I think I'm fine, why do you think it's risky?
Click to expand...
Click to collapse
If you bricked your phone with Locked BL , you may not be able to revive it thru flashing since it may not allow flashing other firmware or recovery like TWRP. Also, ARB may brick your phone if you flashed old version.
Tried. Didn't work for me
engineer000 said:
If you bricked your phone with Locked BL , you may not be able to revive it thru flashing since it may not allow flashing other firmware or recovery like TWRP. Also, ARB may brick your phone if you flashed old version.
Click to expand...
Click to collapse
I flashed to a newer version ofc (even so because it's from Android 8.1 to 9) and you are always allowed to flash and official ROM, even if everything goes wrong, flash back to the Global stable. The tool also notifies and doesn't proceed to flash the ROM if all attempts are tried and unsuccessful.
With things like custom recoveries is where you brick your phones, cause people either don't download and official ROM or something goes wrong and with unlocked BL you're getting screwed...
Also to wait like 25 more days to unlock BL I was like damn it let's try this method and voilá
ricpicpr said:
Tried. Didn't work for me
Click to expand...
Click to collapse
What version are you on? And are you global or chinese version?
Exactly the same of you. From Global 10.0.3 to Developer 8.10.25. My Mi 8 is official global version with locked bootloader (for now, i have to wait the last 10 days)
ricpicpr said:
Exactly the same of you. From Global 10.0.3 to Developer 8.10.25. My Mi 8 is official global version with locked bootloader (for now, i have to wait the last 10 days)
Click to expand...
Click to collapse
I have 30 days to wait because I already unlocked one device on my account. And same as you I can't flash by this method.
8.11.1 beta full ROM update
This was officially suspended for our device, but I'll post it anyway for those that want it.
http://bigota.d.miui.com/8.11.1/miui_MI8Global_8.11.1_ed2903c393_9.0.zip
Flash at your own risk...
dugapila said:
I flashed to a newer version ofc (even so because it's from Android 8.1 to 9) and you are always allowed to flash and official ROM, even if everything goes wrong, flash back to the Global stable. The tool also notifies and doesn't proceed to flash the ROM if all attempts are tried and unsuccessful.
With things like custom recoveries is where you brick your phones, cause people either don't download and official ROM or something goes wrong and with unlocked BL you're getting screwed...
Also to wait like 25 more days to unlock BL I was like damn it let's try this method and voilá
Click to expand...
Click to collapse
if camera is better in 8.10.25 than the stable, I may try this. can you confirm if camera is better or not? Thanks
engineer000 said:
if camera is better in 8.10.25 than the stable, I may try this. can you confirm if camera is better or not? Thanks
Click to expand...
Click to collapse
I don't know. Maybe on the front camera it's better stabilized for photos but other than that I don't notice anything special. I use the Google Camera anyways (link for that: https://www.celsoazevedo.com/files/android/google-camera/f/MGC_6.1.009_MI8_V1a.apk), it's much better, even more for low-light situations (although the latest version still has some bugs and missing some features that I hope will be addressed in the future)
ricpicpr said:
Exactly the same of you. From Global 10.0.3 to Developer 8.10.25. My Mi 8 is official global version with locked bootloader (for now, i have to wait the last 10 days)
Click to expand...
Click to collapse
I don't know then. Maybe if you try one more time. I don't think it will brick anyways because if the process fails, then the command line of the tool will say it can't do it and will not flash, at least afaic.
I will wait for a new ota then will immediately flash the beta?