New Realme UI can't be unlocked! - Realme 2 pro Questions & Answers

I don't know whats happening. But there is an issue regarding bootloader unlocking on new Realme UI version RMX1807EX_11_F.11 build.
I get error from cmd while flashing command: Flashboot flashing unlock and it shows FAILED(no errors) in 0..08 secs. I don't know what happens while i do it. After Upgrade to Android 10 stock i got this problem. Previously i was able to use in-depth test app which worked fine on Android 9, but not working on Android 10 Realme UI v.1. Please Help if someone knows about this.

GokulGiga7 said:
I don't know whats happening. But there is an issue regarding bootloader unlocking on new Realme UI version RMX1807EX_11_F.11 build.
I get error from cmd while flashing command: Flashboot flashing unlock and it shows FAILED(no errors) in 0..08 secs. I don't know what happens while i do it. After Upgrade to Android 10 stock i got this problem. Previously i was able to use in-depth test app which worked fine on Android 9, but not working on Android 10 Realme UI v.1. Please Help if someone knows about this.
Click to expand...
Click to collapse
yes same problem. help us someone .

GokulGiga7 said:
I don't know whats happening. But there is an issue regarding bootloader unlocking on new Realme UI version RMX1807EX_11_F.11 build.
I get error from cmd while flashing command: Flashboot flashing unlock and it shows FAILED(no errors) in 0..08 secs. I don't know what happens while i do it. After Upgrade to Android 10 stock i got this problem. Previously i was able to use in-depth test app which worked fine on Android 9, but not working on Android 10 Realme UI v.1. Please Help if someone knows about this.
Click to expand...
Click to collapse
Check here
https://forum.xda-developers.com/realme-2-pro/help/bootloader-unlock-problem-t4167125

Related

Report Your Problems with the Official ASUS Bootloader Unlock Tool Here

There's a bunch of threads about the bootloader unlock tool existing, not any real place to aggregate reports of problems with it. So, if you've attempted to unlock your bootloader using the official ASUS tool and are having problems, please post your situation.
Reported instances:
myself
DeathStolas
ASUS_Khang
Rattraps123
m3t4lw01f
creison
both are experiencing bootloader unlock limbo. The tool seems to have worked, but going into fastboot shows two progressive screens:
1) Unlock Successfully reboot in 5 seconds
2) FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Clearing the cache goes through the loop again. Mind you, this loop only happens when you're trying to get to the bootloader. If you go to recovery or normally boot, you won't have any issues.
However, any commands sent via fastboot fail, so the bootloader is still locked. Attached is an image of the second bootloader screen.
ASUS_Khang is already getting in touch with technical folks to investigate as well, but I figure it best to see if anyone else is having issues with the official tool.
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...

			
				
I have to laugh at the fact that someone on XDA unlocked the bootloader successfully with none of these problems and then ASUS give an "Official Unlock Tool" that screws up the phone of any who uses it... In the words of Alanis Morrisett - "Isn't it Ironic"...
m3t4lw01f said:
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...
Click to expand...
Click to collapse
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Same problem here. I used the official unlocker tool and it did what it said it was going to do, but... I got the mythical "Bootloader 5 sec reboot".
asus is working on a fix.
playingmax said:
asus is working on a fix.
Click to expand...
Click to collapse
I'm sure that they are, but it would be interesting to see a source for that claim.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
m3t4lw01f said:
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
Click to expand...
Click to collapse
Sounds good. Can't wait till this is all sorted out and I can continue on with installing Cyanogenmod for my SO. She is really excited since it's her first Android phone.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
here you go
http://myzen.asus.com/2015/10/13/official-bootloader-unlock-for-zenfone-2-is-now-available/
look at Khang Thai (ASUS REP) reply. they are working on a fix.
Kona67 said:
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Click to expand...
Click to collapse
Same issue ... I tried without a pin .. now added a pin and it asked me for it when trying to run the app again ... but that didn't help !
Help Ausus!!!
Mine says unlock failed rebooting in 5,4,3,2,1.
any way to relock bootloader as zenfone 6,5,and 4 have
When the 5 second bootloader issue is fixed you should hear about it here first, we have an Asus employee helping us: http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
https://fsfe.org/news/2012/news-20121106-01.en.html
Enviado do meu iPhone usando o Tapatalk
Looks like a user has solved the 5 second reboot issue. Check out the rather convoluted method here: http://forum.xda-developers.com/showthread.php?p=63498472

Need help with Asus Zenfone 6

This is my first post on XDA and i am in desperate need of help. I own a Asus Zenfone 6. Recently i tried unlocking bootloader and installing TWRP recovery so that i can flash a custom ROM. It went horribly wrong and i bricked my device. I managed to unbrick it and revert to Stock ROM which i also upgraded to LOLIPOP using adb sideload. I also managed to root it and have super user access. The problem is that i cannot install a TWRP or any other recovery. When i try to install a custom recovery i get and error " cannot install unsigned image on secure device" which probably suggests that the boot loader is locked. I ran the commands to unlock the boot loader and they ran successfully but i am not sure if the bootloader is locked or unlocked.
I tried running fastboot oem devices but i get an error " Unknown Oem command".
It was after hours of troubleshooting that i decided that i am OK with stock LOLIPOP rom as long as i have a rooted device. It was after sometime that i noticed that the camera wasn't working. Also the flashlight wasn't working. I uninstalled the updates and flashlight was working. However the camera just gives me a black screen for some time after which it quits with an error message " Camera is used by another application. Please reboot your device and try again". I uninstalled the updates for Camera and reverted to a previous version by also removing the camera application using super user access. However for an older version i get an error " Camera not found". I have also tried installing other camera applications but none seem to work even after making them a part of system. Currently flashlight works but only under an older version , as soon as i update it stops working. I decided to lock the boot loader again as it was just not worth it. However after running the commands and locking the bootloader i still cannot get the camera to work. I tried in safe mode and the camera won't work there either.
When i go to recovery i just have four options, there is no install from internal storage or SD card which suggests i am on stock recovery.
Currently i just want my camera to work. I am OK with the stock ROM and recovery as long as i have a rooted device. I have spent hours researching and nothing seems to work. I am in desperate need of help. Some of the friends suggested to try my luck here. I would be indebted as i dont want to purchase another device just because i screwed my camera. Also when i was under kitkat i ran the SIMI test and was getting an error 1667 and 1668 for both cameras. The test is failing under LOLIPOP as well. I dont think its a hardware issue or maybe i am wrong. Any help would be appreciated.
Thanks.
Not even a single reply. DISAPPOINTED!
You need to Lock Bootloader then reflash the rom (wipe all) to fix it. Custom ROMs sometimes cause camera not working cuz there are some devices that have different camera.... Next time, just make sure you Lock Bootloader => Flash Stock recovery => Wipe => Flash Stock ROM
qureshiburhan92 said:
Not even a single reply. DISAPPOINTED!
Click to expand...
Click to collapse
NOT EVEN A REPLY BACK
But yeah that sounds like a roller coaster.
Just picked up the Zenfone 6 to see what I could do with it, I'm going to try to flash the RR rom on here.
Just something I noticed though, I did some research myself, and a couple of sites like this one (https://zenfones.gajetzki.com/) say that you should root your original stock before doing anything. Now this wasn't a requirement at all in my experience for all other phones so I'm a bit skeptical. Anyway I thought that may help in some way.
Good luck!
LGenius3 said:
NOT EVEN A REPLY BACK
But yeah that sounds like a roller coaster.
Just picked up the Zenfone 6 to see what I could do with it, I'm going to try to flash the RR rom on here.
Just something I noticed though, I did some research myself, and a couple of sites like this one say that you should root your original stock before doing anything. Now this wasn't a requirement at all in my experience for all other phones so I'm a bit skeptical. Anyway I thought that may help in some way.
Good luck!
Click to expand...
Click to collapse
Hey buddy.
Thanks for the reply.
I am on stock rom as well as recovery and i have already gone through all these steps. Bootloader is locked as well as far as i can tell but still the camera doesn't seem to work. I am literally out of ideas now. Any help would be great!
Thanks
may zenfone 6 with stock rom 3.24.40.87 can't be unlock,pleas help me
qureshiburhan said:
Hey buddy.
Thanks for the reply.
I am on stock rom as well as recovery and i have already gone through all these steps. Bootloader is locked as well as far as i can tell but still the camera doesn't seem to work. I am literally out of ideas now. Any help would be great!
Thanks
Click to expand...
Click to collapse
Sorry for the late reply, but I'll try to help as much as I can. First things first, I know there are two different models of the Zenfone 6, the A600CG and the A601CG, but apparently this shouldn't make a difference, but it could have in this case, after all they must have different names for a reason. Also, the support for the Zenfone 6 is pretty terrible in terms of custom roms and the such, so you may even be better off with the stock experience, just root it and you'll have all the functionality you could ever dream of.
If you're still keen for the custom roms and stuff maybe check out this thread:
https://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
Other than that, I guess Google is your friend, but so are we!
I haven't been able to hold onto my Zenfone 6, as it was a friends, so I no longer have it and never got the opportunity to have some fun with it, so I'm just going off my own experience with my HTC One M9, which is probably vastly different, but I suppose the process isn't too different. Nonetheless, I hope all goes well!

Huawei p8 lite ale 21 bricked

I can't do anything with my phone.
I tryed to get it clean but now nothing works. I cant get i into fastboot to fix it, and i don't have twrp on it i don't know what do do.
I always get the error "error: no devices/emulators found"
edit:
I got into fastboot but i still can't access the phone. I still get "error: no devices/emulators found"
NoNameID said:
I can't do anything with my phone.
I tryed to get it clean but now nothing works. I cant get i into fastboot to fix it, and i don't have twrp on it i don't know what do do.
I always get the error "error: no devices/emulators found"
edit:
I got into fastboot but i still can't access the phone. I still get "error: no devices/emulators found"
Click to expand...
Click to collapse
HI
Can you please send a photo? I could help you better :highfive:
hello there, I am having a problem with my Huawei P8 Lite, few months ago I Unlocked it booloader, Installed Twrp Recovery, Root it and then Upgrade it to
Marshmallow Stock ROM, EMUI 4.0, Build No. ALE-AL21C185B188, I am sure it was Offical Build,
When I bought it Box Packed, it was on Lollipop stock ROM, EMUI 3.0, Build No. ALE-AL21C185B188. On Marshmallow it was running smoothly, I did change the BootImage or Animation, but it was lacking some features, like Camera Fuzzy and no guest mode or so, then i installed Xposed to get more Features, and I guess then Substrance theme, there it got problem, so tried to reinstalled the ROM again after totally wiping. I just reboot it once I guess after flashing the ROM it just turns on show Boot Image, no further booting, just stuck at the screen, I tried again and again wiped it flashed it. But no Use, fortunately I boots into Twrp Recovery and Fastboot mode also, so I am sure there is absulotely a way to get it worked. But obviously I m not the engineer so I am calling u Guys to Plz help me Out. I tried whatever I could understand, I tried to get help from my local fone mechanics but they also just couldn't figured it out, as they are casual android dudes, not got intact with EMUI's. I would be very thankful if Anyone of uguys help me sort my problem, will b waiting for urs advisory and informative response.
Khugiani said:
hello there, I am having a problem with my Huawei P8 Lite, few months ago I Unlocked it booloader, Installed Twrp Recovery, Root it and then Upgrade it to
Marshmallow Stock ROM, EMUI 4.0, Build No. ALE-AL21C185B188, I am sure it was Offical Build,
When I bought it Box Packed, it was on Lollipop stock ROM, EMUI 3.0, Build No. ALE-AL21C185B188. On Marshmallow it was running smoothly, I did change the BootImage or Animation, but it was lacking some features, like Camera Fuzzy and no guest mode or so, then i installed Xposed to get more Features, and I guess then Substrance theme, there it got problem, so tried to reinstalled the ROM again after totally wiping. I just reboot it once I guess after flashing the ROM it just turns on show Boot Image, no further booting, just stuck at the screen, I tried again and again wiped it flashed it. But no Use, fortunately I boots into Twrp Recovery and Fastboot mode also, so I am sure there is absulotely a way to get it worked. But obviously I m not the engineer so I am calling u Guys to Plz help me Out. I tried whatever I could understand, I tried to get help from my local fone mechanics but they also just couldn't figured it out, as they are casual android dudes, not got intact with EMUI's. I would be very thankful if Anyone of uguys help me sort my problem, will b waiting for urs advisory and informative response.
Click to expand...
Click to collapse
Well,how did you install ROM?(fastboot or official recovery?)
and the ROM you installed is official android 6.0?
sorry for my bad english…
I flashed it through trwp recovery
Khugiani said:
hello there, I am having a problem with my Huawei P8 Lite, few months ago I Unlocked it booloader, Installed Twrp Recovery, Root it and then Upgrade it to
Marshmallow Stock ROM, EMUI 4.0, Build No. ALE-AL21C185B188, I am sure it was Offical Build,
When I bought it Box Packed, it was on Lollipop stock ROM, EMUI 3.0, Build No. ALE-AL21C185B188. On Marshmallow it was running smoothly, I did change the BootImage or Animation, but it was lacking some features, like Camera Fuzzy and no guest mode or so, then i installed Xposed to get more Features, and I guess then Substrance theme, there it got problem, so tried to reinstalled the ROM again after totally wiping. I just reboot it once I guess after flashing the ROM it just turns on show Boot Image, no further booting, just stuck at the screen, I tried again and again wiped it flashed it. But no Use, fortunately I boots into Twrp Recovery and Fastboot mode also, so I am sure there is absulotely a way to get it worked. But obviously I m not the engineer so I am calling u Guys to Plz help me Out. I tried whatever I could understand, I tried to get help from my local fone mechanics but they also just couldn't figured it out, as they are casual android dudes, not got intact with EMUI's. I would be very thankful if Anyone of uguys help me sort my problem, will b waiting for urs advisory and informative response.
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994/page84
NoNameID said:
I can't do anything with my phone.
I tryed to get it clean but now nothing works. I cant get i into fastboot to fix it, and i don't have twrp on it i don't know what do do.
I always get the error "error: no devices/emulators found"
edit:
I got into fastboot but i still can't access the phone. I still get "error: no devices/emulators found"
Click to expand...
Click to collapse
You know that you have to type 'fastboot devices' when you are in fastboot?

Need support on 7.1.2 for Y5 2017 mya-l22

I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again
fir1996 said:
I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again
Click to expand...
Click to collapse
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.
JudgeDread11 said:
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.
Click to expand...
Click to collapse
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!
Dylan2232 said:
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53
JudgeDread11 said:
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53
Click to expand...
Click to collapse
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.
Dylan2232 said:
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.
Click to expand...
Click to collapse
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying anything is learning how to backup and restore.
JudgeDread11 said:
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying any freething is learning how to backup and restore.
Click to expand...
Click to collapse
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.
Dylan2232 said:
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.
Click to expand...
Click to collapse
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.
hi , good news for Huawei y5 2017(MYA-L22) users.
Download latest lineage14.
visit to my blog.
cheers
https://p55novo.blogspot.com/2018/07...e-141-for.html
JudgeDread11 said:
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.
Click to expand...
Click to collapse
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.
Dylan2232 said:
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.
Click to expand...
Click to collapse
For rooting you need unlocked bootloader ( if you don't do ir then below won't work).
1)download the 4pda app from google play store and register an account .
2) download the TWRP.img file from 4pda website here is the link
https://4pda.ru/forum/index.php?showtopic=823938&view=findpost&p=74424572
3) enable developer mode in your phone by going to setting about phone , tap 6 times on the build number.
4)go to developer mode and enable usb debugging and oem factory unlock .
5) go to your pc install adb here link https://forum.xda-developers.com/showthread.php?t=2588979
6) now conect the phone to the pc and run cmd , type adb reboot bootloader . (Your device ahould restart and enter bootloader mode (white screen)).
7) now take the TWRP.img (must be copyied to desktop ) and type in cmd cd desktop.
8) type fastboot flash recovery TWRP.img (change the file name to TWRP ).
9) type fastboot reboot.
Now you have successfully install TWRP on your device.
Continue... If replied

After Pie: Bootloader unlocked & TWRP install didn't work

Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
cyrrel said:
Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
cyrrel said:
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
Click to expand...
Click to collapse
can you explain us the procedures that you have followed to downgrade. It would be really helpful. i have tried this
method but it didn't work for me. i am facing IMEI 0/no signal issues using this method.
Thanks
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
cyrrel said:
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
Click to expand...
Click to collapse
Are your imei & mac same as original? won't the imei/mac get affected by restoring someone else efs?
I don't know about mac, but imei is ok

Categories

Resources