Stuck at flashing - really need some advice - Xiaomi Redmi Note 3 Questions & Answers

Hey there!
I'm using the Redmi Note 3 Pro for a few months now with CM. Since CM is a bit buggy for me and I would love to try out the new MIUI 8, most preferred the official global release.
But unfortunately I'm struggling, nearly fighting , with my device for a few days now. Problem is that I can't get anything to work properly on my device.
Here is what I did (Phone is of course offically unlocked) :
Downloaded the latest MIUI 8 global from the official site. First mistake was to take the wrong version. I allways thought that my device is a kenzo. But it's a kate. OK, so I tried to use the global version for the special edition. When I flash the zip via TWRP everything seems to go normal but in the end the process stops at "package_extract_file took 00s". I let the flash process run over night, so there is definitely a freeze at that point. This step stayed for over 8 hours.
Strange thing here is that the process looks exactly the same, regardless what image (kenzo or kate) I choose.
After the TWRP attempt I tried to flash the fastboot image via MiFlash. Here is the problem a different one: MiFlash won't allow kenzo images. So far so good. But when I take the kate fastboot image the process fails when flashing system.img (file too large). I found out that using a custom rom like CM changes the system-partition size (system1 and system2 merged to system?) for more space. But I don't know how to fix that.
Now I'm pretty clueless and not sure what to do. Is there a way to get MIUI running or am I forced to use CM? What can I do? I am very thankful for every hint or advice you can give me. Thank you!

Have u ever tried using edl mode ?

No, edl mode is new to me.

Try flashing the Fastboot ROM uisng Mi Flash Tools with your phone in EDL Mode.
See this.
http://xiaomitips.com/guide/how-to-put-redmi-note-3-into-edl-mode/

Yeh Use edl ....you'll be fine

THANK YOU VERY MUCH EVERYONE
EDL worked like a charm. Should have asked earlier
Thanks guy!

Related

Help with replacing Redmi Note 3 pro Vendor Rom (out of ideas)

Hi guys, so my new Redmi Note 3 Pro (3GB Ram/ 32Gb rom) came in the mail today. I was excited because I want to give this phone to my father and I know its a good phone since I have one myself, running CM13. However, my problem is that I am unable to access EDL mode . I did adb command to run "adb reboot edl" and it just restarted the phone. I even did the volume combination keys and I am still unable to access EDL mode. I went the extra mile to even unlock the bootloader officially so it should be at a good start right now as it is. I suddenly realized that I might have a vendor rom running on my new Redmi Note 3 Pro. I looked up everywhere on google and none of the tutorials help me get rid of the vendor rom to flash back to official rom. Many of the threads from MIUI havent helped me. I was hoping if anyone could help me revert back to stock MIUI, doesn't matter which (developer, stable, china developer, etc.) I have took some screenshots from the phone to show you what vendor rom I am currently running and plus some of the errors I have came across while trying to go back to stock MIUI. I have done the whole flashing and unlocking bootloader before so i know the process and im not afraid to take instructions. Any help guys, I would really appreciate it!
Edit: Yes, i have also disabled my signature drivers while doing all of this.
did you try this method. forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
V-incent said:
did you try this method. forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Click to expand...
Click to collapse
I have. It is like as if the phone came with no EDL partition or something. I don't think that's possible. But yes I have tried that method, it was fastboot v2. Not sure what version that one is but I believe they operated the same way.
I'm open to the idea of rooting the phone with this pre-installed Vendor Rom and from there I can wipe it and flash CM13 since my bootloader is already unlocked. However I'm not sure if there a case for rooting and installing TWRP on vendor roms for Redmi note 3
Transfer latest global rom on the phone and use updater to flash?
HParra97 said:
I'm open to the idea of rooting the phone with this pre-installed Vendor Rom and from there I can wipe it and flash CM13 since my bootloader is already unlocked. However I'm not sure if there a case for rooting and installing TWRP on vendor roms for Redmi note 3
Click to expand...
Click to collapse
I can try help you. Please, send me PM
privateriem said:
Transfer latest global rom on the phone and use updater to flash?
Click to expand...
Click to collapse
Yeah I've tried that /: apparently those who have a fake Rom (Vendor Rom) cannot update via OTA by the updater app
Its not adb reboot edl.
Search n download fastboot reboot edl zip in miui forum.
Reboot edl will work from fastboot.
You do not have the Snapdragon Redmi Note 3. You have the Mediatek version as evident from your screenshot saying the processor type as "Octa-Core". The EDL mode does not work on Mediatek devices, as far as I know. You can follow this guide for MediaTek devices.
It's the non-pro version with mediatek chipset
You have been fooled
ayush3051 said:
You do not have the Snapdragon Redmi Note 3. You have the Mediatek version as evident from your screenshot saying the processor type as "Octa-Core". The EDL mode does not work on Mediatek devices, as far as I know. You can follow this guide for MediaTek devices.
Click to expand...
Click to collapse
nguyenlucky said:
It's the non-pro version with mediatek chipset
You have been fooled
Click to expand...
Click to collapse
I see. Thanks guys for helping me notice that.

Redmi note 3 stuck in boot animation

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.

(Almost) bricked Oneplus X: cannot unlock bootloader, cannot install OS

Hi all,
tl;dr: Tried to hard unbrick my Oneplus X, which was partly succesful (no OS is installed in the process, while there should be). I am now stuck with no OS and only the Oneplus recovery. I want to install an OS, but it says my bootloader is locked. To unlock it, I need an OS ==> vicious circle.
Full story below:
Recently I've decided to reinstall LineageOS on my Oneplus X because I had quite some problems with it (battery drain, apps crashing, wifi slow to connect, ...). I've done it like 5 times before on this device for various reasons, so I didn't expect any problems. I had LineageOS 14.1 and TWRP 3.0.3 installed. When I wiped everything, I wanted to flash the ROM I had ready using TWRP. However, gave an error number 7, saying that the ROM is not compatible for the device, which I am sure was. Remembering I had a similar issue a while back, I installed flashed an updated version of TWRP (3.2.2) using TWRP itself. That was successfull, but here's where the trouble began.
I noticed that TWRP didn't recognise any storage (Internal storage, SD card and USB-OTG all showed up as 0 MB) any longer. Neither could I mount any of the storages. I've tried a lot of things to solve this. After a while, I decided that the only hope left was the 'mega unbrick guide' (https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/) which claims to be able to recover any device, unless it has a hardware problem. I got good hope as I got near the end of the guide. The last step says 'Disconnect phone from PC and boot into system', but here I got stuck on the Oneplus boot logo, making me think that there is no OS installed on the device.
I can still access the recovery using power button and volume down, but the recovery that the mega unbrick guide installs, is the limited Oneplus recovery. It allows to install a ROM from the local storage, or from USB using adb sideload. When I try option 1, nothing happens, no new screen opens or anything. When I try option 2, I enter the adb sideload mode which would normally allow me to sideload a ROM using my pc. My pc confirms I'm in adb sideload mode, and I try to sideload a ROM. It starts fine, but after a few seconds, it says 'Installation failed'. I've tried stock OOS, latest OOS as well as LineageOS 14.1 that was installed before.
Another thing that I can do in the Oneplus recovery is rebooting into fastboot mode, where I should be able to flash the recovery of my choice. Again, my phone confirms I'm in fastboot mode and I try to flash or boot TWRP recovery, but I get the message: 'FAILED (remote: Device not unlocked cannot flash or erase)'. Okay, seems like the bootloader is still locked, so I should just go and unlock it using 'fastboot oem unlock'. This gives the message: 'FAILED (remote: oem unlock is disabled)'. I've been searching around a lot on the internet, and it seems like the only way to enable oem unlock, is in the OS itself in the developer settings. But the problem is, I have no OS and cannot install one because the bootloader is not unlocked... So I'm stuck in this vicious circle.
I've been searching on the internet for hours and starting to lose hope. At this point, I would be happy if I can just have any OS (OxygenOS or LineageOS or something else) running. If I have that, I should be able to take it from there.
Any help is much appreciated. Thank you very much.
Kind regards,
Jeroen
Bump
Update:
Oneplus support could solve the problem for me! 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 hope I can also help other people with the same problem.
Japeroen said:
Update:
Oneplus support could solve the problem for me! 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 hope I can also help other people with the same problem.
Click to expand...
Click to collapse
Greatly appreciate your feedback here. I think that I am in the same situation you were. Used what you suggested - using MSM v2.1 that you provided with the system.img, non-hlos and userdata.img from MSM v2.0. The process ends with "Download Complete" written in green but when I check "Verify" it fails exactly @system.img, userdata and non-hlos. I can't boot recovery either after these.
Do you have any clue as to why it is so?
gabytzu338 said:
Greatly appreciate your feedback here. I think that I am in the same situation you were. Used what you suggested - using MSM v2.1 that you provided with the system.img, non-hlos and userdata.img from MSM v2.0. The process ends with "Download Complete" written in green but when I check "Verify" it fails exactly @system.img, userdata and non-hlos. I can't boot recovery either after these.
Do you have any clue as to why it is so?
Click to expand...
Click to collapse
As far as I know, I haven't used the "Verify" button. Right after the green "Download Complete" line, I booted into the OOS stock recovery by pressing volume down and power button (I think? Not sure anymore, I always forget it). From there, I could install OOS with a official ROM image.
Are you sure you moved the correct files from V2.0 to V2.1? The way I knew which files to move, is by first starting the V2.1-program without any added files. Then it told me 'system.img missing' (or something like that), so I knew I had to add that. After adding that, I ran the program again and added the next file it said it was missing etc etc.
Sucks to hear your recovery process doesn't go as "smooth" (it's all relative of course) as mine.
Japeroen said:
As far as I know, I haven't used the "Verify" button. Right after the green "Download Complete" line, I booted into the OOS stock recovery by pressing volume down and power button (I think? Not sure anymore, I always forget it). From there, I could install OOS with a official ROM image.
Are you sure you moved the correct files from V2.0 to V2.1? The way I knew which files to move, is by first starting the V2.1-program without any added files. Then it told me 'system.img missing' (or something like that), so I knew I had to add that. After adding that, I ran the program again and added the next file it said it was missing etc etc.
Sucks to hear your recovery process doesn't go as "smooth" (it's all relative of course) as mine.
Click to expand...
Click to collapse
Hah, did not expect an answer, I've seen your thread on oneplus forums as well, glad you were so quick to answer here. I've found the MSM2.1 uploaded in a google drive with all the files afterwards, after some long hours of searching too. Anyway, I still can't adb sideload anything, the storage seems 'corrupted' to say the least, but there are imporvements from MSM v2.0 and v3.0 flahses. The recovery menu works flawlessly now, no artifacts or freezes, also the phone 'almost' booted. It went to the "Updating android apps" thing.
I don't really know what to do next. Recovery does not help me at all. I can't sideload anything, it renders a "protocol fault" error. Internal storage has 2 empty folders within and that's about it. Also the bootloader is locked now and I can't make any use of fastboot mode.
gabytzu338 said:
Hah, did not expect an answer, I've seen your thread on oneplus forums as well, glad you were so quick to answer here. I've found the MSM2.1 uploaded in a google drive with all the files afterwards, after some long hours of searching too. Anyway, I still can't adb sideload anything, the storage seems 'corrupted' to say the least, but there are imporvements from 2.0 and 3.1 flahses. The recovery menu works flawlessly now, no artifacts or freezes, also the phone 'almost' booted. It went to the "Updating android apps" thing.
I don't really know what to do next. Recovery does not help me at all. I can't sideload anything, it renders a "protocol fault" error. Internal storage has 2 empty folders within and that's about it. Also the bootloader is locked now and I can't make any use of fastboot mode.
Click to expand...
Click to collapse
Haha I know the feeling! But thanks to e-mail notifications.
I also thought that my storage was corrupted at first, given the symptoms I described in my first post, so I didn't expect my OPX to be revived, but hey it's still alive now.
I also had the locked bootloader-thing. The way I could unlock it, is by first installing OOS using the stock recovery (which was installed using the tool), then unlocking it in OOS, so I could install another recovery and eventually another OS.
I'm afraid I already explained the problems I encountered and the procedure I followed pretty detailed. If you have anything that deviates from this, I'm sorry to say that I can't really help you with that, even if I wanted to. Did you perform the exact steps I mentioned (including the V2.1-tool that I linked to)? What exactly do you mean with the "3.1 flash"?
It's also already 2 months ago, so I don't even know exactly what I've done apart from what I've described...
Japeroen said:
Haha I know the feeling! But thanks to e-mail notifications.
I also thought that my storage was corrupted at first, given the symptoms I described in my first post, so I didn't expect my OPX to be revived, but hey it's still alive now.
I also had the locked bootloader-thing. The way I could unlock it, is by first installing OOS using the stock recovery (which was installed using the tool), then unlocking it in OOS, so I could install another recovery and eventually another OS.
I'm afraid I already explained the problems I encountered and the procedure I followed pretty detailed. If you have anything that deviates from this, I'm sorry to say that I can't really help you with that, even if I wanted to. Did you perform the exact steps I mentioned (including the V2.1-tool that I linked to)? What exactly do you mean with the "3.1 flash"?
It's also already 2 months ago, so I don't even know exactly what I've done apart from what I've described...
Click to expand...
Click to collapse
It was a typo, I meant v2.0 and v3.0(for oneplus 3). The op3 unbrick guide suggested that the v3.0 might work for oneplus x as well, so I tried that out too.
Anyway, I've done the process a couple more times and the phone booted untill you set the device up, when you are finished it just reboots. I can see the lock screen, I can't bring down the upper bar or enter the settings, if unlocked it prompts me to the first time set up and upon it's completion the phone reboots. I wiped cache,data did a factory reset. Now it's back with the recovery menu artifacts and not booting anymore either. I will use that tool a couple more times then I am done until further suggestions from this forum. After all, my life does not depends on reviving it, I was gonna give it to my brother, who shattered his phones' touchscreen, until he repairs his. Thank you again for replying, no need to reply to this, unless it can help my case.

Bootloader locked. Can't flash roms. Stuck on oneplus logo

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!

Custom ROM installation Problems on P20 Lite

Hello developers,
I bought a Huawei P20 lite a few days ago after verifing, that lineage is possible to install on those phones.
Now, after struggling for 3 days to install lineage, I decided to post here.
First some information about my phone:
Device: Huawei P20 lite dual SIM, 4GB RAM, 64GB internal (ANE-L21, i guess?)
Fastboot Info (I ran those commands when creating this post):
fastboot oem get-build-number: ANE-LX1 9.1.0.257(C432E6R1P7) (from what I understood, ANE-LX1 and ANE-L21 Firmwares are the same?)
fastboot oem get-product-model : ANE-LX1
fastboot getvar version: FALED, Command not allowed
fastboot getvar vendorcountry: HW/EU
When I got the phone, I got my bootloader unlock code first.
I then successfully updated the phone to the newest version (the official Huawei approach, using HiSuite).
After that, I unlocked the bootloader with no problems and flashed TWRP.
I needed to try a few versions to find one that's working as the official ones for that phone kept freezing, I finally found one by Pretorian08 that's working).
Then I formatted to get rid of encryption, did the wipe procedure, cleared the cache, data and system partition and installed the newest lineage build and GAPPS.
After rebooting, the Phone showed me the usual "your device has been unlocked and can't be trusted"- dialog, and tried to boot then.
From here on, nothing happened.
I tried every build I could find, including the most actual one from tonight (lineage-16.0-20201214-nightly-anne-signed.zip).
Some builds would reboot after some time and show the shortened warning message, then boot directly into Recovery.
I totally bricked my phone somewhere on the way (multiple times I think), but could unbrick it by flashing rescue_recovery_kernel, rescue_recovery_ramdisk and rescue_recovery_vendor with appropriate img files extracted from a "Anne-L01 Anne-L21 9.1.0.132(C432E5R1P7T8)" - Firmware and then going back to zero by installing a stockrom via dload and unlocking the bootloader again.
I then tried several other custom Roms, but the outcome is always the same: The phone just freezes with the warning message still visible while trying to boot up, or it boots into TWRP.
ROMs I've tried (I'll write the filenames to provide more info):
- Havoc OS-v3.2-20200215-ARM64AB-GSI.img
- Resurrection Remix ARM64_AB_20191205.img (this is the only custom ROM that will do ANYTHING at all: It will show the Red RessurectionMix Bootlogo, but sadly it won't boot past that point)
- Treble AOSP losq-v224-201017-arm64-bvN.img
With the above 3, installing GAPPS is not possible because "not enough free space in system partition"
- Every possible lineage build for that phone
As stated before, I'm struggling with the phone for 3 days now, so I followed a whole bunch of threads and advices, flashed multiple firmware files using different methods and tried like 7 different TWRP versions. With other words: I did a lot of things, which yould possibly mess up the phone and maybe I did something wrong at some point.
Maybe, I flashed a wrong Firmware while trying to unbrick or something like that. Can you guys help me understand what I'm doing wrong?
I don't like it if people post questions in a forum and then don't share what they figured out, so I'll post 's a little update after 6 days:
Here's a serious advice, if you're considering to buy this phone because there are lineage builds available: forget it.
I mean in most cases it seems to work somehow (from what I read), but from my experience I can say now, that there are phones where it apparently just doesn't work.
I've wasted over one week of my holiday working nonstop on that phone, I've downloaded about 50GB of different firmware files, recoveries, patches and custom Roms and flashed my firmware like 40 times. Best thing I could archieve is an indefinitely looping bootlogo in AOSP, lineage won't even get to that point.
I've tried every lineage build available, i've tried EMUI versions from 9.1.0.0X up to 9.1.0.200 (it is stated multiple times that the .200 will definitely work), no chance. I even tried a rollback to EMUI 8 via Hisuite and using old lineag builds in the end.
The fact that I didn't get any advice in this forum leads me to the conclusion, that no one has an Idea on what the problem is here either.
As I don't feel good with using a phone that still has original google stuff and huawei spy/bloatware installed, the only option that is left to me is just throwing it away and using some old phone. That's sad and a real waste of material and time, as the phone is brand new, but using the stockrom is no option to me. I really don't know what went wrong, I've already successully installed lineage (and cyanogenmod before) on more than 8 other devices, always without any problems.
So even if you (think you) know what you're doing, I can't recommend buying this device with the intention of using lineage.
user_name_duplicate said:
So even if you (think you) know what you're doing, I can't recommend buying this device with the intention of using lineage.
Click to expand...
Click to collapse
P20 lite is not so bad, maybe you are doing something wrong...
I've installed without problems Havoc, LOS 16.0, LOS 17.1unofficial, AOSP 10, losq-v224-201017 etc. etc...
P.S.: If you "hate" Google and Google's bloatware (like me ) only, you can simply rebrand your phone to chinese Nova 3e.
Or, choose Custom ROM based on Stock with KangVip settings , stable enough to be used as your daily driver." ( e.g. https://forum.xda-developers.com/hu...m-emui-8-0-kangvip-p20-lite-catuva21-t3813564
https://forum.xda-developers.com/hu...-emui-8-0-0-huawei-p20-lite-dual-sim-t3813604) . Using KangVip settings you can disable completely GAPPs .
(My primary phone is at the moment Mate 10 lite rebranded to chinese Maimang 6 (to get away from GAPPS ) . Among other things, better battery life, lower data consumption (using FUT) etc.)
Hi -Alf-, thank you for replying.
-Alf- said:
P20 lite is not so bad, maybe you are doing something wrong...
Click to expand...
Click to collapse
You're right, it's not the phone, it's me. I guess I am doing something wrong, but I don't have the slightest clue what that is.
Any suggestions?
I've already invested a lot of time and have more or less resignated, but thanks to covid lockdown I'm basically trapped inside the house and might aswell give it another try.
Rebranding is an option, you're right. I already have downloaded a nova 3e Firmware, if nothing else works, I might try that.
Also, I'll have a look at the KangVip Roms, haven't heard of them before.
But to be honest, I think I wouldn't be satisfied with those options, at least not for a long time.
Getting lineage running on that phone is a task, the problem solver inside me is really commited to accomplish, because that was the intention I bought the phone with. Also, not being able to accomplish something that hundreds of other people already have done and that is proven to work is driving me nuts. I wouldn't have bothered trying to get it working for 10 days otherwise.
Unfortunately, availability of custom ROMs for Kirin devices is scarce.
Try Havoc 2.9 (requires EMUI 8)
Havoc 2.9
Hi -Alf-,
-Alf- said:
Try Havoc 2.9 (requires EMUI 8)
Click to expand...
Click to collapse
Tried that now, after downgrading to EMUI 8 via HiSuite, I did exactly what you wrote in that thread. The outcome is the same as with every other ROM I've tried: I see the "your device has been unlocked and can't be trusted" screen, then after a while it tells me that "my device is booting now" and just does nothing except rebooting every 10 or so minutes.
Luckily those devices seem to be fairly indestructible, as long as the Bootloader is open and FRP is disabled, so I'll give it some more tries.
-Alf- said:
Unfortunately, availability of custom ROMs for Kirin devices is scarce.
Click to expand...
Click to collapse
I bought the phone because I thought it was officially supported:
LineageOS Downloads
download.lineageos.org
Was that assumption wrong, is there some hint or exception, that I'm not seeing?
The phone was delivered some weeks late because the seller was out of stock. I guess it came directly from china. Is it possible, that I got a new hardware revision, which is not yet supported?
user_name_duplicate said:
I guess it came directly from china. Is it possible, that I got a new hardware revision, which is not yet supported?
Click to expand...
Click to collapse
It may be a fake, try to verify the authenticity on linked website
imei24
user_name_duplicate said:
I guess it came directly from china
Click to expand...
Click to collapse
Exactly, I saw for example Huawei P20 Pro with MediaTek proc.
Btw., I have installed this Havoc 2.9 three times without problem, so it's really very strange...
In fastboot mode run commands :
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
fastboot oem get-build-number
fastboot getvar vendorcountry
fastboot oem get-product-model
fastboot getvar rescue_version
and post the results please.
Some might fail, so don't worry about it.
You can also download "Device Info HW" apk and check your SoC (Kirin 659) Vendor (HiSilicon), ABI (arm64-v8a) etc.
On imei24, the device is listed as "Huawei P20 Lite" for both imeis, blacklist status is "clean". Recognized Serial is the same for both Imei numbers.
Only thing that's not clear to me is the warranty status:
Warranty start: 2018/7/23
Warranty end: 2018/8/6
So it can't be that new, at least not factory new, right?
I bought it on real.de, so I have no further information where it comes from. China was just my assumption because they where out of stock and delivered 2 or 3 weeks late. I can't really imagine that real is selling fake phones (on purpose). That really wouldn't help their image if people found out.
I ran the commands you provided:
fastboot oem oeminforead-CUSTOM_VERSION: FAILED
fastboot oem oeminforead-SYSTEM_VERSION : ANE-LX1 8.0.0.180(C432)
fastboot oem get-build-number : ANE-LX1 8.0.0.180(C432)
fastboot getvar vendorcountry: hw/eu
fastboot oem get-product-model: ANE-LX1
fastboot getvar rescue_version: rescue0.6
I will download the Device Info apk as soon as my device boots again (I will reflash the stock image once again).
Edit: Device Info HW is telling me I'm using a Kirin 659 SOC.
Okay, most of custom ROMs require lower build number, that's why I wrote that I tested Havoc 2.9 on .126. If you are running latest build number, it may cause your problems.
IMO it is time to clean your phone, extract from Oreo firmware (it doesn't matter which build number) ramdisk.img , kernel.img, recovery_ramdisk.img and erecovery_ramdisk.img and transfer to the SD card.
Download .126 Service ROM
8.0.126
unpack it and transfer dload file to the SD Card (without unpacking it)
Install
TWRP
over eRecovery, boot into TWRP, select Flash image and flash 4 files. Go back to main TWRP's panel > Reboot > Power Off.
Use three button combo to flash the ROM. This process will erase all your data and lock the bootloader again!!!
Unlock BL and try Havoc 2.9 . It must work!
Good luck.
Edit: I found on my MEGA :
https://mega.nz/#!o8FUVR6T!-1fl6TviRtgGbssuG9LgyssCJg4dwxa84luJmrnvSCg
https://mega.nz/#!gkdgnLBa!O8LVZF4J0NiEB78c9z4_FxASN0vWx3rOAIQdmhApAOQ
https://mega.nz/#!xpViTTSC!Q_5ieeEL0gpKROj35cvjc_TRddmkFTMsIxvOT6lS23Y
https://mega.nz/#!EhM2lZqK!yphxvKNUQueIryop44DmPflp7Iwi9c8ExeaCRqA-iY4
Hello Alf, thanks for your last reply!
Downgrading worked, that was the last thing I've tried before christmas.
I wanted to continue today, but found this thread you've posted in.
I thought I'd give it a try and now I'm running on lineage (which is what I initially wanted), sadly only the 15.1 version, but I don't need the newest version.
WiFi is working and, until now, it's running stable. I've installed 8.1. nano gapps (might try pico in the future) and magisk v21.
Maybe I'm lucky and in the next few weeks or months I'll find a working build of an android pie lineage.
I think with installed TWRP it should now be possible, to do a complete backup, mess around with the system (i.e. upgrade Android/Flash ROMs) and then restore it to my now working state, is that correct?
If that's the case, I'll try some other ROMs, including the havok ROM I've already downloaded.
Which partitions must be included in my backup to perform such operations?
For anyone else encountering my problem, here is what finally did the trick:
Code:
- downgrade to .126, following alfs procedure
- Flash TWRP by pretoriano80 (on recovery_ramdisk partition)
- do a wipe (format data to get rid of encryption, then via advanced wipe format cache partitions and system)
- install lineage 15 (link), last build is from 2020-10-27, so it's not an abandoned build
- install GAPPS 8.1
- install magisk v21
- wipe cache/Dalvik
- boot to system
Booting for the first time took a few minutes, but since then, it's running smooth and without any problems.
The only thing that's still an enigma to me is, why the LOS builds I initially tried (with EMUI 9.0.0.200) didn't work, even though other people don't seem to have a problem with ANE-LX1 and LOS16. If anyone is reading this and has an answer to that question, please post!
For now, I'm happy with LOS 15. Thank you many many times, Alf! Greetings to Melmac!
user_name_duplicate said:
Thank you many many times, Alf!
Click to expand...
Click to collapse
No problem...
user_name_duplicate said:
Greetings to Melmac!
Click to expand...
Click to collapse
I'm currently struggling with the same issue. Tried every combination of TWRP with lineage 16 and gapps. Some roms I can get to boot but then not enough space for h gapps. I have tried to wipe system, data and cache to resize system partition which ends up in phone booting directly to TWRP. Other times I get to warning screen and end up with boot - loop. So I'm well a are off your frustration. However I have decided that I'm not gonna settle for version 15. I'm trying for 17 but much have to settle with lineage is 16..

Categories

Resources