Hi.
Is anyone else face this issue : I updated to EMUI 9.0 beta, but when I did a factory reset, my phone won't boot anymore. Can't access recovery, can't boot, only access fastboot.
The problem now is that I can flash a TWRP, but the phone is not booting on it... And no eRecovery too !! That's really bad. And now my phone is flagged as 9.0.0 firmware... Maybe it's my flashing problem.
If someone have an idea, I would be thankful \o/
Thanks !
EDIT : Ok, I just erase "userdata" (fastboot erase userdata) and then I was able to boot into TWRP ... My godness, finally
Thiphariel said:
Hi.
Is anyone else face this issue : I updated to EMUI 9.0 beta, but when I did a factory reset, my phone won't boot anymore. Can't access recovery, can't boot, only access fastboot.
The problem now is that I can flash a TWRP, but the phone is not booting on it... And no eRecovery too !! That's really bad. And now my phone is flagged as 9.0.0 firmware... Maybe it's my flashing problem.
If someone have an idea, I would be thankful \o/
Thanks !
EDIT : Ok, I just erase "userdata" (fastboot erase userdata) and then I was able to boot into TWRP ... My godness, finally
Click to expand...
Click to collapse
Could you please let me know how you fixed it?
I'm facing the same problem but my phone just doesn't want to boot into the recovery.
Related
Obtained phone with buggy touchscreen. Flashed CM to see if it fixed it. Didn't. Trying to go back to full stock for return
Recovered stock device via TWRP then installed what I thought was a stock recovery.img, except it wasn't - it was a CM recovery
The CM recovery only lets me boot to recovery or the bootloader - no other options are functional
In the bootloader the FRP is locked and doesn't let me flash TWRP or stock recovery
What should I do to replace the CM recovery with TWRP or stock when the FRP is locked?
THanks
funkyhunky said:
Obtained phone with buggy touchscreen. Flashed CM to see if it fixed it. Didn't. Trying to go back to full stock for return
Recovered stock device via TWRP then installed what I thought was a stock recovery.img, except it wasn't - it was a CM recovery
The CM recovery only lets me boot to recovery or the bootloader - no other options are functional
In the bootloader the FRP is locked and doesn't let me flash TWRP or stock recovery
What should I do to replace the CM recovery with TWRP or stock when the FRP is locked?
THanks
Click to expand...
Click to collapse
Go into developer options and enable OEM unlocking
---------- Post added at 02:26 AM ---------- Previous post was at 02:17 AM ----------
funkyhunky said:
Obtained phone with buggy touchscreen. Flashed CM to see if it fixed it. Didn't. Trying to go back to full stock for return
Recovered stock device via TWRP then installed what I thought was a stock recovery.img, except it wasn't - it was a CM recovery
The CM recovery only lets me boot to recovery or the bootloader - no other options are functional
In the bootloader the FRP is locked and doesn't let me flash TWRP or stock recovery
What should I do to replace the CM recovery with TWRP or stock when the FRP is locked?
THanks
Click to expand...
Click to collapse
I have just now read your post thoroughly you said that the touchscreenis buggy,is it twrp or in the system
If it's twrp don't worry I too have the same problem in the version I tried eg. 3.0.2.0,3.0.1.0,3.0.0.0
But if it's in system try factory resetting
And change smart power saving mode to performance
But to unlock frp(i suppose you have already unlocked your bootloader) just go into developer options and enable OEM unlocking option
Ok I got the stock recovery back:
I booted into the bootloader and used the local command window to fastboot boot a twrp image from my computer
With TWRP booted (but not installed) on my phone I put in a sd card with a stock recovery image, and used the booted TWRP to install the stock recovery
Unfortunately, I have not figured out how to relock the boot loader, but hopefully they overlook/don't care about that for a return - I did not root the phone
U can relock bootloader in honor5x
I think I have a similar problem. I bought new KIW-L24, I unlocked bootloader, flashed twrp to go to RR Nougat ROM. When I started Twrp to install ROM it said "Comparing tarz 2.2 to 2.5" so I read that I had update to MM.
I went to settings>updater and started update to M331 EMUI 4.0 ROM on the twrp recovery instead of stock recovery. I have M331 ROM now but I can't fastboot the TWRP recovery anymore. It sat twrp installed successful but the EMUI Stock recovery opens up when hitting Vol. + and Power instead of Twrp.
I noticed fastboot menu shows Phone unlocked but it does not say FRP Unlocked anymore. Does that prevent me from installing custom recovery now? Please...any help is appreciated.
cyrusalmighty said:
I think I have a similar problem. I bought new KIW-L24, I unlocked bootloader, flashed twrp to go to RR Nougat ROM. When I started Twrp to install ROM it said "Comparing tarz 2.2 to 2.5" so I read that I had update to MM.
I went to settings>updater and started update to M331 EMUI 4.0 ROM on the twrp recovery instead of stock recovery. I have M331 ROM now but I can't fastboot the TWRP recovery anymore. It sat twrp installed successful but the EMUI Stock recovery opens up when hitting Vol. + and Power instead of Twrp.
I noticed fastboot menu shows Phone unlocked but it does not say FRP Unlocked anymore. Does that prevent me from installing custom recovery now? Please...any help is appreciated.
Click to expand...
Click to collapse
Just delete the google account in your phone and do a factory reset. Later reboot but skip adding gmail . This will unlock frp .
gopinaidu77 said:
Just delete the google account in your phone and do a factory reset. Later reboot but skip adding gmail . This will unlock frp .
Click to expand...
Click to collapse
Can the frp relocking stop me from flahing twrp? Or is it this stock rom I am on? Do you know if other people have problems flashing twrp on L24 B311 MM update? Could I have caused my issue when I updated to the official rom using the twrp? I didn't think the update would work without stock recovery but it did. I did factory resets but I still can't install install any custom recovery. Can I go back to earlier stock rom?
I followed your instructions and deleted Google accounts and factory restored. I go to bootloader and it says Phone Unlocked but does not say FRP unlocked anywhere. I flshed twrp anyways and although cmd window shows it flashed OK when I reboot the stock EMUI Recovery opens again.
Edit: Now I use adb and mfastboot.exe to open twrp and do a backup. I don't know if I install a different rom if I will able to finally install twrp. I wonder if this 331 stock rom is the problem or FRP is issue here. Never had this problem with my Gold Honor 5X.
cyrusalmighty said:
I followed your instructions and deleted Google accounts and factory restored. I go to bootloader and it says Phone Unlocked but does not say FRP unlocked anywhere. I flshed twrp anyways and although cmd window shows it flashed OK when I reboot the stock EMUI Recovery opens again.
Edit: Now I use adb and mfastboot.exe to open twrp and do a backup. I don't know if I install a different rom if I will able to finally install twrp. I wonder if this 331 stock rom is the problem or FRP is issue here. Never had this problem with my Gold Honor 5X.
Click to expand...
Click to collapse
Plz boot recovery first and install recovery from twrp . This may do some help
gopinaidu77 said:
Plz boot recovery first and install recovery from twrp . This may do some help
Click to expand...
Click to collapse
Ok. Ive never done this this way. When installing Twrp image it asks where to install? Select Partition to Flash image: Boot, OEMinfo, or Recovery. Do I just press Recovery only?
cyrusalmighty said:
Ok. Ive never done this this way. When installing Twrp image it asks where to install? Select Partition to Flash image: Boot, OEMinfo, or Recovery. Do I just press Recovery only?
Click to expand...
Click to collapse
Select only recovery
ok I installed image, chose recovery, and installed superSU_2.46.zip but it still only boots up EMUI Stock recovery. Unfortunately its stuck in bootloop now so now I cant even adb/fastboot into twrp anymore. Now my only option is holding vol +- and Power to install update from sd card (dload folder). I just dont kmow what FW file to use.
cyrusalmighty said:
ok I installed image, chose recovery, and installed superSU_2.46.zip but it still only boots up EMUI Stock recovery. Unfortunately its stuck in bootloop now so now I cant even adb/fastboot into twrp anymore. Now my only option is holding vol +- and Power to install update from sd card (dload folder). I just dont kmow what FW file to use.
Click to expand...
Click to collapse
Fastboot boot recovery.img dint helped?
gopinaidu77 said:
Fastboot boot recovery.img dint helped?
Click to expand...
Click to collapse
I ended up trying everything. I held volume - and Power to force Fastboot&Rescue Mode. I did fastboot boot twrp_kiwi.IMG. When in Twrp I install twrp_kiwi.IMG (For permanent Install) but EMUi recovery still stays.
I believe the custom recovery is installing but NOT where it needs to install.(Probably a different partition). I noticed a erecovery when I extracted an update file with HuaweiExtractor with does program. I DID get out of Bootloop by applying update from SD card (Force Update Volume - and Plug in USB cable). I rolled the FW back to B130 Emui 3.1 Firmware. I still need to fash Twrp and update this phone now.
cyrusalmighty said:
I ended up trying everything. I held volume - and Power to force Fastboot&Rescue Mode. I did fastboot boot twrp_kiwi.IMG. When in Twrp I install twrp_kiwi.IMG (For permanent Install) but EMUi recovery still stays.
I believe the custom recovery is installing but NOT where it needs to install.(Probably a different partition). I noticed a erecovery when I extracted an update file with HuaweiExtractor with does program. I DID get out of Bootloop by applying update from SD card (Force Update Volume - and Plug in USB cable). I rolled the FW back to B130 Emui 3.1 Firmware. I still need to fash Twrp and update this phone now.
Click to expand...
Click to collapse
So the frp lock still exists is it?
gopinaidu77 said:
So the frp lock still exists is it?
Click to expand...
Click to collapse
Yes I think the FRP Lock is on. It only says: Phone Unlocked. Before it used to say hone Unlocked and FRP unlocked.
cyrusalmighty said:
Yes I think the FRP Lock is on. It only says: Phone Unlocked. Before it used to say hone Unlocked and FRP unlocked.
Click to expand...
Click to collapse
Have u removed gmail account ?
gopinaidu77 said:
Have u removed gmail account ?
Click to expand...
Click to collapse
Yes I had removed gmail account. I went to settings>accounts and deleted Google and all other accounts. Does FRP Unlock when you unlock Bootloader?
cyrusalmighty said:
Yes I had removed gmail account. I went to settings>accounts and deleted Google and all other accounts. Does FRP Unlock when you unlock Bootloader?
Click to expand...
Click to collapse
U can try that
Hi everybody,
I got my Swift 2 8 months ago and have finally decided to root it using TWRP. So I unlocked my bootloader and then installed TWRP using the official guide at https://twrp.me/devices/wileyfoxswift2.html. I also wiped my cache and dalvik cache.
However, now I have done this, whenever I try to boot, I receive both the amber and red warnings about corruption and then get stuck in a bootloop on the first black and white boot image.
Please can someone help me get back into android; if possible I would like root but in the end just a working phone.
Thanks.
As far as I know it's a dm-verity issue. There might be several ways to fix it but the only one I know is to flash Magisk from TWRP. I still run version 12 because 13.x won't install for me.
From my expierience, unlocking and locking bootloader will wipe your userdata , so backup! How I root mine is, first unlock through fastboot, than fastboot boot twrp, instead of flashing, flash magisk through twrp, than lock the bootloader again through fastboot. This keeps you from getting messages about corruption and has you rooted. Whenever I need twrp I just boot it instead of flashing it. I also made a backup using twrp, just to keep things safe and easy to restore...
Edit: To get out of bootloop you either do a factory reset or flash the image found in this forum using fastboot update...
You should have a look at this thread: https://forum.xda-developers.com/swift-2/how-to/marmite-wileyfox-ota-nougat-android-7-1-t3654999
I re-unlocked my device a few days ago after a long time of using MIUI. Unfortunately, I am now facing a peculiar problem I had not faced the previous time I unlocked my device.
I cannot seem to replace MIUI stock recovery with official TWRP.
If I use fastboot flash recovery xxx.img, the terminal does confirm that the action was successful. Yet, when I reboot into recovery, I am greeted by Mi-Recovery 3.0 instead of TWRP.
My initial thought was that maybe there was some restriction in MIUI that prevented the stock recovery from being replaced, so I flashed RR 5.8.5-FINAL. I still cannot flash TWRP.
Some other info:
The MIUI build I was on: MIUI 9 7.9.21 Global Beta
My phone: RN3 SD 2GB/16GB variant, Fpc fingerprint sensor
The temporary workaround I used to flash RR was directly booting into TWRP using fastbooot boot xxx.img
NOTE: I did a standard wipe (factory reset, followed by wiping System, Data and Cache) when I flashed RR.
As you might imagine, using fastboot to boot into TWRP every time I want to flash something is quite tiring and so if anyone can help me to permanently flash TWRP, I'd be really grateful. Thanks in advance.
PS: If this question has already been answered, then please guide me to the relevant thread and I will take down this one.
This problem also happened to my friend's Redmi Note 3 MTK. I don't know if it's going to work on KENZO or not.
The solution is to flash the TWRP recovery image through fastboot ==> Turn off the device by holding down the power button (DISCONNECT PHONE FROM PC) ==> Boot the recovery using button combinations
This should let you boot into TWRP and stays permanent after the first session
Flashing Through Fastboot/EDL Mode
Flashing Twrp through Fastboot is the permanent way of flashing the recovery...The method is very simple and can be done even on locked bootloader but the thing in locked bootloader is that once you have flashed the TWRP the internal storage is inaccessible because the data is encrypted so you need to wipe->format data ...then press "yes" ..by typing yes the internal storage will be formatted completely so make sure you have a backup ...and do copy the ROM file in SD card for flashing ...after wiping process press install then select SD card and flash the ROM and gapps and enjoy the TWRP...
Refer this link for flashing process youtu.be/rCONN1_IPuU(please add https:// before the link)
Hope this solves your problem...
same problem !! did you find any solution !!!
Hey guys ,
I unlocked bootloader and flashed official twrp via fastboot . I successfully booted into twrp but when I click reboot my phone stuck on mi boot logo . I personally tried many thing to tackle this problem. But every time I got same thing . Can anyone solve this ?
Redwolf twrp is working fine .
Yes, happend the same to me, basically what's happening is that your phone can't decrypt itself in the boot.
What's the fix? Flash twrp, go into it
Then wipe EVERYTHING,even format.
That will be you new partitions (new encryption) in your phone.
Then with everything formated, plug your phone in twrp and copy whatever you want, and viola.
You're done, copy the rom you want to flash and will boot.
Please let me know when your phone is fixed.
Or you can just root your device
I had the same issue as you yesterday.
You can try lazyflasher to prevent bootloop
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
AhmedRadowan25 said:
Do you have any suggestions on what I can do?
Click to expand...
Click to collapse
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
AhmedRadowan25 said:
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
Click to expand...
Click to collapse
Here's a complete explanation what I have done:
Initially, I was running stock MIUI with root access and TWRP recovery. However, I decided to switch to the Pixel Experience ROM. I downloaded the Pixel Experience Android 11 version and flashed it directly from TWRP since I didn't have access to a PC at that time. I only flashed the ROM file and didn't install the Pixel Experience recovery image, assuming that my TWRP would remain intact. But when I rebooted into recovery after the ROM installation, it booted into the Pixel Experience recovery instead. I couldn't find an option to flash the recovery image, only an option to apply an update through ADB sideload.
Fortunately, I managed to use a friend's computer and installed all the necessary ADB and Fastboot drivers. The computer could detect my phone in ADB sideload mode, but when I tried to boot into the bootloader, the PC couldn't detect my phone. Despite multiple attempts of booting into the Pixel Experience recovery and enabling ADB sideload, the PC couldn't recognize the fastboot mode. Strangely, every time I booted into the bootloader, my phone automatically powered off after displaying the Redmi logo. Holding the power button didn't help as it consistently powered off after showing the logo, without accessing the bootloader or recovery mode. I was afraid my phone had become completely unresponsive.
After numerous attempts, my phone unexpectedly booted into the bootloader again. This time, I connected my phone to another device using BugJagger, which successfully detected my phone. I used the command "fastboot flash recovery twrp.img" followed by "fastboot boot twrp.img" to open TWRP. However, I couldn't decrypt it using my password. I then flashed TWRP again and tried to boot into the system, but it always reverted back to the bootloader. I went back into recovery, selected partitions A to B, and flashed Magisk ZIP, DM variety ZIP, and LazyFlasher ZIP (without fully understanding their purpose).
Finally, my phone successfully booted into the system. However, upon rebooting into TWRP and then rebooting the system without any changes, my settings app and bluetooth stoped working. To resolve this, I had to boot into TWRP once again, format the data, and flash Magisk to restore normal operation.
alonsoj636MW said:
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
Click to expand...
Click to collapse
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
AhmedRadowan25 said:
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
Click to expand...
Click to collapse
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
Thank you very much.Flashing miui will solve all probem?what do you think?
AhmedRadowan25 said:
what do you think?
Click to expand...
Click to collapse
it should
at least when i mess up with my phone flashing stock fixes all problems
Hi mate! Did you resoved the problem? What about the rom? All good?
gabsvm1 said:
Hi mate! Did you resoved the problem? What about the rom? All good?
Click to expand...
Click to collapse
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
AhmedRadowan25 said:
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
Click to expand...
Click to collapse
No problem mate, besides that everything is working good? You have tried a13 roms before?
gabsvm1 said:
No problem mate, besides that everything is working good? You have tried a13 roms before?
Click to expand...
Click to collapse
No
Who told you to flash DM Verity and Lazy Flasher
We don't need these things in our device
Don't mess up with Active Slot
If you try to change your Active slot into Inactive slot, once you Reboot to system, you will go straight to fastboot
You need Android Bootloader Interface to detect your phone in bootloader and ADB Composite to detect your phone in ADB, such as : Google USB Driver r13
Why you don't ask before doing anything, we have global community chat in telegram, for sure, we will help you in possible way
I assume you need back to stock rom to fix this issue
hit me on tele t.me/super_img