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
Related
So I flashed the first chinese CM13 build with fingerprint when there was no information about locking bootloader and about making a backup to restore, so I want to go back to MIUI but I don't have any backup to retore so I don't know how to do it, If anyone could tell me and the rest of the people that have done the same as me it would be so thankful.
bornthisjesus said:
So I flashed the first chinese CM13 build with fingerprint when there was no information about locking bootloader and about making a backup to restore, so I want to go back to MIUI but I don't have any backup to retore so I don't know how to do it, If anyone could tell me and the rest of the people that have done the same as me it would be so thankful.
Click to expand...
Click to collapse
just go to bootloader unlocked tutorial[not by mi provided offical tool] and flashed miui
First off, this is not the right forum to ask this questions. Second, if you didn’t make EFS backup I don’t think you can make phone calls, send/receive texts or use mobile data in the official MIUI any longer (someone correct me if I am wrong). You can either try a leaked and unstable MIUI (search for it in the forums) or use some new ROM with fingerprint support on this forum (Santhosh’s CM13, ROMs by Siddhesh.K15 and some others). If you are determined to use MIUI you will have to wait until Xiaomi releases an official marshmallow version.
Filip013 said:
First off, this is not the right forum to ask this questions. Second, if you didn’t make EFS backup I don’t think you can make phone calls, send/receive texts or use mobile data in the official MIUI any longer (someone correct me if I am wrong). You can either try a leaked and unstable MIUI (search for it in the forums) or use some new ROM with fingerprint support on this forum (Santhosh’s CM13, ROMs by Siddhesh.K15 and some others). If you are determined to use MIUI you will have to wait until Xiaomi releases an official marshmallow version.
Click to expand...
Click to collapse
I do have an EFS backup, it's the only one I have, not for the rest of partitions
bornthisjesus said:
I do have an EFS backup, it's the only one I have, not for the rest of partitions
Click to expand...
Click to collapse
Then you’ll be fine. If you unlocked officially, you can’t go wrong.
Filip013 said:
Then you’ll be fine. If you unlocked officially, you can’t go wrong.
Click to expand...
Click to collapse
I unlocked unofficially and after instaling CM13 everytime I want to unlock bootloader with Mi Unlock it gets stuck at 50%
bornthisjesus said:
I unlocked unofficially and after instaling CM13 everytime I want to unlock bootloader with Mi Unlock it gets stuck at 50%
Click to expand...
Click to collapse
Same with me
bornthisjesus said:
I unlocked unofficially and after instaling CM13 everytime I want to unlock bootloader with Mi Unlock it gets stuck at 50%
Click to expand...
Click to collapse
Hmm... Not sure exactly what tutorial @sankhauaa is referring to, but if you just flash any official fastboot, you’ll be fine. Of course in order to restore phone features you will have to install TWRP.
I hardbricked the phone after installing cm13, boot edl and flash fastboot rom, this is the way i've used and phone booted
Sent from my Redmi Note 3 using Tapatalk
I didn't make a backup. I flashed back to global stable 7.3.2.0. Then I went to the fastboot mode and unlocked my bootloader again. The phone worked fine with all phone calls, etc working
Filip013 said:
Hmm... Not sure exactly what tutorial @sankhauaa is referring to, but if you just flash any official fastboot, you’ll be fine. Of course in order to restore phone features you will have to install TWRP.
Click to expand...
Click to collapse
For revert back to miui follow thishttp://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
Hi everyone, im new to XDA. But that's kinda beside the point.
I have a Redmi Note 3 with Snapdragon 650 and 2gb ram 16gb storage. I wanted to install lineage os/R.remix because im kinda bored of miui and wanted nougat. I did the following steps to install.
1. Unlocked bootloader via no-permission or hack method.
2. Installed TWRP latest as of 10-6-2017 thru Fastboot.
3. Wiped cache,dalvik and data
4. Flashed R.Remix nightly 10-6-17 and then Gapps.
In this step, I had a problem. It was giving me error:7 (xiaomi.verify.modem) and so I modded the rom (updater-script) and worked. It had the animation loop soflashed NON-HLOS modem binary thru Fastboot and flashed the original signed ROM. But, the problem persists. It's stuck in the boot animation and looping infinitely. I left it for 30min-1hr and still loops. What do I do now? Please help me in this regard. Till then, MIUI again
bro you forgot to flash lazy flasher at first boot in rom after installing twrp.
dean [email protected]# said:
bro you forgot to flash lazy flasher at first boot in rom after installing twrp.
Click to expand...
Click to collapse
There's no need of lazyflasher on a custom Rom!
Do you want to know something else about what I did to solve the problem? Although I rolled back to miui bcos I needed my phone:good:
U need to update ur firmware. Download it from below link & follow the below steps.
https://www.androidfilehost.com/?fid=817550096634767927
Wipe system, Data, cache, Dalvik cache
Install above firmware
Install Custom Rom of ur choice
Enjoy
Let me know if it doesn't works
ExtGame said:
Hi everyone, im new to XDA. But that's kinda beside the point.
I have a Redmi Note 3 with Snapdragon 650 and 2gb ram 16gb storage. I wanted to install lineage os/R.remix because im kinda bored of miui and wanted nougat. I did the following steps to install.
1. Unlocked bootloader via no-permission or hack method.
2. Installed TWRP latest as of 10-6-2017 thru Fastboot.
3. Wiped cache,dalvik and data
4. Flashed R.Remix nightly 10-6-17 and then Gapps.
In this step, I had a problem. It was giving me error:7 (xiaomi.verify.modem) and so I modded the rom (updater-script) and worked. It had the animation loop soflashed NON-HLOS modem binary thru Fastboot and flashed the original signed ROM. But, the problem persists. It's stuck in the boot animation and looping infinitely. I left it for 30min-1hr and still loops. What do I do now? Please help me in this regard. Till then, MIUI again
Click to expand...
Click to collapse
Don't flash that miui firmware from post above, it will relock your bootloader because you are not officially unlocked.
Best way to go is to flash latest global dev fastboot rom, unlock officially. This way you will have no problems with flashing nougat custom roms.
So, should I install the latest global developer rom? I checked yesterday it was v7.6.7 while latest global stable was 8.2.4 which I have currently installed. I also checked via fastboot OEM device-info and, yeah, bootloader locked.:crying: So, I should install the dev. Rom and ask for permission and then unlock, like, the official way? I'm waiting for the reply. Make it clear and I'll try it. Thnx.
Edit : I also somehow got TWRP uninstalled:crying::crying: I don't know if this unexpected or was doomed to happen but yeah, again, just saying.
I just asked for permissions to unlock and..... Surprise!!! I got the permission in 5 minutes!!!
I feel kinda sad for the people who are waiting for more than 21 days...
Capt. John Yossarian said:
Don't flash that miui firmware from post above, it will relock your bootloader because you are not officially unlocked.
Best way to go is to flash latest global dev fastboot rom, unlock officially. This way you will have no problems with flashing nougat custom roms.
Click to expand...
Click to collapse
Okee, doin' it. I'll inform you later abt how its hapenning.
Good luck to me
ExtGame said:
Okee, doin' it. I'll inform you later abt how its hapenning.
Good luck to me
Click to expand...
Click to collapse
Good luck.
https://www.digitbin.com/unlock-bootloader-xiaomi/
https://www.howtogeek.com/240047/how-to-flash-twrp-recovery-on-your-android-phone/
https://forum.xda-developers.com/showthread.php?t=2317790
OMG OMG OMG IM TRIGGERED WHAT IS THIS??????!!!!!!!!!!!!!!
*calms down*
This MI Flash gets stuck at 99% even tho I got permissions (an SMS from MI) and shows current account not bound to device. What do I do? I also tried binding my account to phone by settings-->dev. options-->mi unlock which gave code 86012 and some Chinese characters which I honestly can't understand. I also tried installing global dev and doing the same thing but gives same 86012 and Chinese. Plzz help me in this regard. Would be greatly appreciated. Thanks.
Actually, nvm. I got lineage is installed and running on my phone by following a guide on how to install twrp without unlocking bootloader. Worked like a charm for me. I'm typing this now on lineage:silly: Anyways, thanks for the effort. Thread closed.
You could've just waited for 7 days and you would've unlocked your bootloader officially
how did it go buddy ?
ExtGame said:
Okee, doin' it. I'll inform you later abt how its hapenning.
Good luck to medid you falsh the custom rom , does it work cause i get stuck on bootanimation too
Click to expand...
Click to collapse
I am using it thru locked bootloader mrthod
ExtGame said:
OMG OMG OMG IM TRIGGERED WHAT IS THIS??????!!!!!!!!!!!!!!
*calms down*
This MI Flash gets stuck at 99% even tho I got permissions (an SMS from MI) and shows current account not bound to device. What do I do? I also tried binding my account to phone by settings-->dev. options-->mi unlock which gave code 86012 and some Chinese characters which I honestly can't understand. I also tried installing global dev and doing the same thing but gives same 86012 and Chinese. Plzz help me in this regard. Would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Same here please help
You can follow the tutorial on how to install lineage os with locked bootloader on redmi note 3. Works like a charm, i am using lineage os 14.1 with locked b.loader!!:good:
recommend you to wait for 5-7 days and unlock it officially...
So that you would never face problems in future.
Hello everyone, I and my father have the exact same phone (kenzo). The problem is that even though on mine everything works like a charm and I have changed a lot of roms, my father's phone every time I try anything goes soft bricked or have problems with signal and settings. Currently I have flashed via edl the Chinese Dev rom(5.1.1) with which everything works, besides the restrictions of the rom version(language, gapps). I must say that when I first install the Chinese Dev the Sim is not recognised or I have no signal. After the first update everything is ok and calling function works like a charm. After That I try to install twrp (zxc by ~xm) and restore a backup from the previous working installation, but the only I get is settings app fc and problems with calls. Neither of the two sides hear the other while in call. This occurred when I flashed a mm bootloader zip in order to boot to nitrogen is. (https://drive.google.com/file/d/0B3tM1cVKiyp6Q3RvNUtLdEp1Q3M/view ) The rom booted but I had no sound in calling, and the other side couldn't hear either. Any ideas?
Thanks for your time!
Aristalex said:
Hello everyone, I and my father have the exact same phone (kenzo). The problem is that even though on mine everything works like a charm and I have changed a lot of roms, my father's phone every time I try anything goes soft bricked or have problems with signal and settings. Currently I have flashed via edl the Chinese Dev rom(5.1.1) with which everything works, besides the restrictions of the rom version(language, gapps). I must say that when I first install the Chinese Dev the Sim is not recognised or I have no signal. After the first update everything is ok and calling function works like a charm. After That I try to install twrp (zxc by ~xm) and restore a backup from the previous working installation, but the only I get is settings app fc and problems with calls. Neither of the two sides hear the other while in call. This occurred when I flashed a mm bootloader zip in order to boot to nitrogen is. (https://drive.google.com/file/d/0B3tM1cVKiyp6Q3RvNUtLdEp1Q3M/view ) The rom booted but I had no sound in calling, and the other side couldn't hear either. Any ideas?
Thanks for your time!
Click to expand...
Click to collapse
Is ur device bootloader is unlocked ?
If yes then by which method u had unlocked by unofficial way or by official way?
Criston said:
Is ur device bootloader is unlocked ?
If yes then by which method u had unlocked by unofficial way or by official way?
Click to expand...
Click to collapse
I used to unlock it the official way. I found a post in the nitrogenOS thread that said that if the rom doesn't boot I should flash the zip that I have mentioned in my post. They said it was the mm bootloader. The zip contains a file named emmc_appsboot.mbn which is also on the unofficial unlock zip. So I suppose I unlocked it unofficially. I must say that every time after flashing fastboot rom the mi unlock said that bootloader was already unlocked.
Aristalex said:
I used to unlock it the official way. I found a post in the nitrogenOS thread that said that if the rom doesn't boot I should flash the zip that I have mentioned in my post. They said it was the mm bootloader. The zip contains a file named emmc_appsboot.mbn which is also on the unofficial unlock zip. So I suppose I unlocked it unofficially. I must say that every time after flashing fastboot rom the mi unlock said that bootloader was already unlocked.
Click to expand...
Click to collapse
U should unlock using the official way if u dont want to face any problem
And also if wanna Flash any custom rom first clean Flash miui using Mi flash tool and google how to Flash custom rom on kenzo
make sure u have backup of all ur files
Criston said:
U should unlock using the official way if u dont want to face any problem
And also if wanna Flash any custom rom first clean Flash miui using Mi flash tool and google how to Flash custom rom on kenzo
make sure u have backup of all ur files
Click to expand...
Click to collapse
Yes yes I know that with my kenzo everything works if I follow your advice. But with my father's one simply doesn't. I flashed the official miui with mi flash tool. The bootloader remained unlocked without reason. Also I tried clean flash and lock option on the tool without success. Then I wiped data and dalvik and cache and dirty flashed a miui custom rom over it. For the time being everything works perfectly except of the fingerprint sensor. Aida 64 recognize the fp, every other app not. Also I flashed radon kernel because I had settings app FC. That's all. I hope the info help you understand the situation that I am in, and find a way to make it respond as mine...
Mine and the other are exactly the same, they even had the same number on the sticker in the back and same fingerprint sensor. Mine takes every rom, unlock update without problems. My father's not. It is crazy...
Something really weird happened while I was installing roms. Someone how my OEM got locked and I flashed and voila stuck on the oneplus logo. I have my fastboot working properly also got twrp installed. The thing is that my bootloader is locked so i cant flash and I cant unlock bootloader because I cant flash and set oem unlock. I know this is ****ed up and also my volume up key is not working so we have to work without that. . Whenevr i turn on the device the powered by android quickly disappears and i am in the fastboot. If I do oem unlock it sends me to the recovery. I am not sure why i can't OEM unlock in fastboot. I don't care about data and stuff. Just want the phone working. The unbrick guide wants me to press the volume up key to get to the qualcomm flashing. Unfortunately i can't do that. Need of dire help please ;_;
I kind of have the same problem as of 2 days (see https://forum.xda-developers.com/android/help/bricked-oneplus-x-unlock-bootloader-t3816387), which is kind of strange, as I haven't read anywhere else about it on the internet.
I'll be following this topic.
Japeroen said:
I kind of have the same problem as of 2 days (see https://forum.xda-developers.com/android/help/bricked-oneplus-x-unlock-bootloader-t3816387), which is kind of strange, as I haven't read anywhere else about it on the internet.
I'll be following this topic.
Click to expand...
Click to collapse
I've solved it bud. IF you have a working recovery and bootloader. Flash the stock OS. It'll flash even though the bootloader is locked and then your can oem unlock and do whatever.
KenSha105 said:
I've solved it bud. IF you have a working recovery and bootloader. Flash the stock OS. It'll flash even though the bootloader is locked and then your can oem unlock and do whatever.
Click to expand...
Click to collapse
That's good news! But I think I've tried that, but had no succes. Can you link me the ROM you've flashed?
Japeroen said:
That's good news! But I think I've tried that, but had no succes. Can you link me the ROM you've flashed?
Click to expand...
Click to collapse
https://downloads.oneplus.com/oneplus-x/oneplus_x_oxygenos_3.1.4/
There.
KenSha105 said:
https://downloads.oneplus.com/oneplus-x/oneplus_x_oxygenos_3.1.4/
There.
Click to expand...
Click to collapse
Thank you. I've tried it, but the problem is that I'm stuck with the Oneplus recovery, as I've mentioned in my post. From there, I have 2 options to flash:
1) from internal memory. When I click this, nothing happens (no new screen or anything, nothing)
2) from USB (adb sideload). When I try to sideload the ROM using this option, it starts promising, but after a few seconds, it just says 'Installation failed' without any reason why. Just like for all other ROMS.
So... No progress here. I've also tried to flash the stock recovery (even though it should be on my phone already, maybe another version) using fastboot, but my OPX won't take it because the bootloader is still locked.
Last resort: I'll try the Oneplus live chat tomorrow, but I do not expect any useful information from that...
Japeroen said:
Thank you. I've tried it, but the problem is that I'm stuck with the Oneplus recovery, as I've mentioned in my post. From there, I have 2 options to flash:
1) from internal memory. When I click this, nothing happens (no new screen or anything, nothing)
2) from USB (adb sideload). When I try to sideload the ROM using this option, it starts promising, but after a few seconds, it just says 'Installation failed' without any reason why. Just like for all other ROMS.
So... No progress here. I've also tried to flash the stock recovery (even though it should be on my phone already, maybe another version) using fastboot, but my OPX won't take it because the bootloader is still locked.
Last resort: I'll try the Oneplus live chat tomorrow, but I do not expect any useful information from that...
Click to expand...
Click to collapse
Well guess what, they could solve it.
Or at least partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to 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?