I have a Moto G Play 2021 (XT2093-4) (another one), that I made a mistake to relock the bootloader after I had it unlocked. I don't have access to the OS on the phone anymore. Previously I had the treble floss installed on it. I don't have TWRP installed. The only thing I have access to is fastboot. I realise I might have completely bricked this phone but I thought I ask here to see if there is any way to unlock the OEM again just using the fastboot.
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
strumcat said:
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
Click to expand...
Click to collapse
Thanks, but I think my phone is completely messed up now. If you can believe it, I can't even get to recovery mode. I can get to fastboot and then find the recovery mode and click to go to it but then it just starts the fastboot again. I'm basically stuck in fastboot forever. It's just weird cause there's nothing wrong with the hardware. Thanks again.
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
strumcat said:
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
Click to expand...
Click to collapse
Sorry for the really late reply. I tried what you said, but it fails right at the (fastboot flash partition gpt.bin) command and the output I get is:
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) flash permission denied
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
It keeps saying flash permission denied. I have another exact same phone with an unlocked bootloader and I did the same on that one and I was able to flash a stock ROM to it. I've tried every RETCA and RETUS on this site: https://mirrors.lolinet.com/firmware/motorola/guamna/official/ but it fails with the same error. I'm going to try all the rest later but it's a lot to download for now.
Thanks again for the help!
Related
I was messing with my old tracfone and trying to install a custom ROM on it. I pressed wipe on TWRP and selected advance wipe and selected everything for factory defaults. After this, I restarted and my phone is stuck on the LG logo and won't go past it. I can't even get back into TWRP by spamming the volume up button. I also have a backup image, but what's the point if I can't access TWRP? Any help is appreciated.
Thanks
Wipe doesn't restore factory defaults, it removes everything. If you wiped system partition there's no Android on your phone, thus no system to boot. If that's the case, you can try to reflash twrp or install original firmware
minimale_ldz said:
Wipe doesn't restore factory defaults, it removes everything. If you wiped system partition there's no Android on your phone, thus no system to boot. If that's the case, you can try to reflash twrp or install original firmware
Click to expand...
Click to collapse
I'm not sure how to reflash TWRP because I used android terminal to install it.
kchesley said:
I'm not sure how to reflash TWRP because I used android terminal to install it.
Click to expand...
Click to collapse
If so, you need a PC, if it's Windows then download this tool - it's a system-wide fastboot that lets you flash software on your phone. It should also download drivers.
If everything goes OK, boot your phone into bootloader (you need to find the right key combination to do that, could be (phone off) power button+ volume down held for about 5-10 seconds, but I don't really know how it's like with this particular phone).
Go to the folder where you've got your TWRP, hold shift and press right mouse button. From context menu choose "open command window here"
In command window enter:
Code:
fastboot devices
if it returns your phones serial number it's OK, if it doesn't - you probably don't have proper drivers so look for them
If everything is OK enter:
Code:
fastboot flash recovery your-twrp-image-name.img
If this step is OK you can reboot:
Code:
fastboot reboot-bootloader
In the bootloader there should be an option to enter recovery mode which is now TWRP. From there you can flash some ROM.
Alternatively you can get ffactory firmware and flash it with fastboot (that's actually a better option to start with).
I hope that helps
minimale_ldz said:
If so, you need a PC, if it's Windows then download this tool - it's a system-wide fastboot that lets you flash software on your phone. It should also download drivers.
If everything goes OK, boot your phone into bootloader (you need to find the right key combination to do that, could be (phone off) power button+ volume down held for about 5-10 seconds, but I don't really know how it's like with this particular phone).
Go to the folder where you've got your TWRP, hold shift and press right mouse button. From context menu choose "open command window here"
In command window enter:
Code:
fastboot devices
if it returns your phones serial number it's OK, if it doesn't - you probably don't have proper drivers so look for them
If everything is OK enter:
Code:
fastboot flash recovery your-twrp-image-name.img
If this step is OK you can reboot:
Code:
fastboot reboot-bootloader
In the bootloader there should be an option to enter recovery mode which is now TWRP. From there you can flash some ROM.
Alternatively you can get ffactory firmware and flash it with fastboot (that's actually a better option to start with).
I hope that helps
Click to expand...
Click to collapse
Thanks for the help, but unfortunately, I think that the phone is junk. My phone can't get into boot-loader for whatever reason, and I heard some people post that the phone was designed to make the boot-loader non-accessible. I already tried to flash it with ADB while it starts up, but no device is detected (no USB debugging I guess). So unless I can flash the phone while It's on the LG logo, I can't do nothing.
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
levijoseph said:
When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked.
Click to expand...
Click to collapse
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Ashwinrg said:
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
Okay, so that did work, and I was able to enter fastboot mode. However, once I scrolled down to "recovery mode" and tried to enter, I got the same "no command" screen.
rolland.arriza said:
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Click to expand...
Click to collapse
I used the official moto g4 root guide on this website to root my phone and I'm pretty sure I booted, not flashed, the recovery img (mine is named twrp-3.0.2-0-athene). So, I tried using the command you provided to flash the recovery img and I got a < waiting for any device > message in the command prompt. My phone is plugged in and my recovery img is in the adb / fastboot folder. Any idea what this means? Thank you for the help guys
edit: If it helps to know this, my phone has usb debugging enabled and it is recognized by my pc. I type adb devices and my moto g4 serial number does indeed show up.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Ashwinrg said:
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Click to expand...
Click to collapse
Did all that, getting:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'recovery.img'
Also, per the suggestion of other users on these forums, I tried to hold down power and press volume up during the "no command" screen after attempting to enter recovery. That sent me into Android Recovery but it's not the twrp platform I used when originally rooting my phone.
How did you unlock the bootloader? have you tried: fastboot oem unlock?
You need to "allow oem unlocking" on developer options (which I guess you already did). Then reboot in bootloader: (a) adb reboot bootloader. In fastboot, you need to unlock the bootloader first: (b) fastboot oem unlock (or unlock-go). Then you can try to flash that recovery.img: (c) fastboot flash recovery "name of the file.img"
edit: fastboot oem unlock restores the device to factory settings. You need to configure and enable again "usb debugging" and "oem unlocking" (which are disabled by default). You can then proceed to fastboot flash
Hi guys,
So I rooted my swift 2x but now I want to unroot it so I can use baking apps. Trouble is I'm having difficulty unrooting.
My method for root was
> Unlock bootloader
> Install TWRP
> Install Supersu
But now I can't unroot. I've tried unrooting via the supersu app but on one try it errored out and nothing changed and on another try when the phone rebooted it got stuck on the white wileyfox screen.
I've also tried to install the reocer image from here https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101 via twrp but then once I reboot after installation from TWRP it gets stuck on the white wileyfox screen after seeing messages that the device is corrupt on a previous screen.
What can I do to unroot?
Thanks!
Return to stock via fastboot... it will fix everything. I had to leave LineageOS because nothing I tried would allow me to use my Banking app now they've really tightened security, thanks to Google's CTS. Shame.
(LOL on the "baking app")
EDIT: This Thread has all the files except the latest. Flash TOS319I and let the phone OTA to TOS373J.
Since you have already done this I thought maybe you might be able to help me with an issue I am having
From your thread I have used the first part of the following thread https://forum.xda-developers.com/showpost.php?p=72827221&postcount=7 - to fastboot "Android_7.1.2_Wileyfox_Swift2_2017_09_07 TOS249H - Signed Fastboot" -
Everything went as it should have (or so it appeared) but when I went to reboot, the new Wiley Fox logo appeared and then looped system errors i.e. "Unfortunately, system UI has stopped" , Unfortunately, the process com.android.phone has stopped etc
Can you give any insight as to my next move please? Would appreciate a noob response
PhilosAnthropos said:
Since you have already done this I thought maybe you might be able to help me with an issue I am having
From your thread I have used the first part of the following thread https://forum.xda-developers.com/showpost.php?p=72827221&postcount=7 - to fastboot "Android_7.1.2_Wileyfox_Swift2_2017_09_07 TOS249H - Signed Fastboot" -
Everything went as it should have (or so it appeared) but when I went to reboot, the new Wiley Fox logo appeared and then looped system errors i.e. "Unfortunately, system UI has stopped" , Unfortunately, the process com.android.phone has stopped etc
Can you give any insight as to my next move please? Would appreciate a noob response
Click to expand...
Click to collapse
Sounds like a problem easily fixed by doing a factory reset, have you tried that?
Just went today to try and factory reset through adb but now there is an "error:no devices found" - exactly the same conditions as yesterday
PhilosAnthropos said:
Just went today to try and factory reset through adb but now there is an "error:no devices found" - exactly the same conditions as yesterday
Click to expand...
Click to collapse
Hmm, is USB debugging on?
USB debugging is needed for adb commands. This setting you find in developer settings and to find and access developer settings you need to tap the version/build number 7 times.
How to Enable USB Debugging Mode on Android <- Check the bottom one #4
Once you do an adb command your phone may prompt you with a connection to pc message to confirm, go ahead and confirm it and do the adb command again.
But.. you need only to get into recovery mode and from there you select and confirm "wipe data/factory reset" and "wipe cache partition". You don't have to do an adb command.
https://www.hardreset.info/devices/wileyfox/wileyfox-swift-2-plus/recovery-mode/ <- I am actually not 100% sure if 5 and 6 are accurate but anyhow this should give you good enough idea on how to access the recovery mode. If in case you not already know this.
All your data will be wiped, make sure to do backup of things you don't want to lose.
May aswell also refer you to my post here, it's just an easy way of doing a fastboot flash.
RavZ75 said:
Hmm, is USB debugging on?
USB debugging is needed for adb commands. This setting you find in developer settings and to find and access developer settings you need to tap the version/build number 7 times.
How to Enable USB Debugging Mode on Android <- Check the bottom one #4
Once you do an adb command your phone may prompt you with a connection to pc message to confirm, go ahead and confirm it and do the adb command again.
But.. you need only to get into recovery mode and from there you select and confirm "wipe data/factory reset" and "wipe cache partition". You don't have to do an adb command.
https://www.hardreset.info/devices/wileyfox/wileyfox-swift-2-plus/recovery-mode/ <- I am actually not 100% sure if 5 and 6 are accurate but anyhow this should give you good enough idea on how to access the recovery mode. If in case you not already know this.
All your data will be wiped, make sure to do backup of things you don't want to lose.
May aswell also refer you to my post here, it's just an easy way of doing a fastboot flash.
Click to expand...
Click to collapse
I flashed stock via fastboot - But it got stuck on Wiley fox logo with process com.android.phone has stopped etc - hence it is not possible to go into the phone and turn on USB debugging, but it was on before I started the process - and I cant really do anything to the phone until I am able to get the PC to recognise the phone again
PhilosAnthropos said:
I flashed stock via fastboot - But it got stuck on Wiley fox logo with process com.android.phone has stopped etc - hence it is not possible to go into the phone and turn on USB debugging, but it was on before I started the process - and I cant really do anything to the phone until I am able to get the PC to recognise the phone again
Click to expand...
Click to collapse
oh I see, and you've tried factory reset and cache wipe from recovery?
That guide I linked to says volume up + power button but I belive it actually is volume down + power button that needs to be pressed, like this. Try both ways, you don't need connection to pc for booting into recovery mode.
But this is different if you have bootloader unlocked, with bootloader unlocked you will be greeted with this (making use of warj04's pic) when you power on your device.
At this screen you press the volume buttons to change boot option from "Start" to "Recovery". Press power button to confirm boot into recovery and your device will reboot and boot into recovery.
This screen will appear a second time before booting into recovery but you need not do anything else, wait 5 seconds or press power button to start boot.
RavZ75 said:
oh I see, and you've tried factory reset and cache wipe from recovery?
That guide I linked to says volume up + power button but I belive it actually is volume down + power button that needs to be pressed, like this. Try both ways, you don't need connection to pc for booting into recovery mode.
But this is different if you have bootloader unlocked, with bootloader unlocked you will be greeted with this (making use of warj04's pic) when you power on your device.
At this screen you press the volume buttons to change boot option from "Start" to "Recovery". Press power button to confirm boot into recovery and your device will reboot and boot into recovery.
This screen will appear a second time before booting into recovery but you need not do anything else, wait 5 seconds or press power button to start boot.
Click to expand...
Click to collapse
I have the bootloader unlocked and it behaves how you have described it but when I try and go into recovery from the options menu (power + volume down) it momentarily goes to a Wiley fox screen, then the loader (the image you added above), and then for a split second the green robot, then the screen blacks-out altogether. From the options menu I can also go to fastboot which also gives me the option to go into recovery but the same sequence starts as described before - recovery appears to be unavailable?
PhilosAnthropos said:
I have the bootloader unlocked and it behaves how you have described it but when I try and go into recovery from the options menu (power + volume down) it momentarily goes to a Wiley fox screen, then the loader (the image you added above), and then for a split second the green robot, then the screen blacks-out altogether. From the options menu I can also go to fastboot which also gives me the option to go into recovery but the same sequence starts as described before - recovery appears to be unavailable?
Click to expand...
Click to collapse
Yea by now I recommend you to redo the flash through fastboot again, In the thread post you linked to I only see 3 lines of fastboot flash cammands.
To fully fastboot flash a rom there needs to be a few other lines aswell, I'll list all the lines here.
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
Lastly, "fastboot reboot" to reboot your device.
RavZ75 said:
Yea by now I recommend you to redo the flash through fastboot again, In the thread post you linked to I only see 3 lines of fastboot flash cammands.
To fully fastboot flash a rom there needs to be a few other lines aswell, I'll list all the lines here.
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
Lastly, "fastboot reboot" to reboot your device.
Click to expand...
Click to collapse
You were a great help, thanks - I didnt think this was going to end well. I was wondering if I re-lock the bootloder will that intermitent screen dissapear? If so, How do I re-lock it?
PhilosAnthropos said:
You were a great help, thanks - I didnt think this was going to end well. I was wondering if I re-lock the bootloder will that intermitent screen dissapear? If so, How do I re-lock it?
Click to expand...
Click to collapse
Yes that screen will go away if you re-lock bootloader and if there isn't a dm-verity issue present.
To fix dm-verity issue you need USB debugging on and this command:
Code:
adb reboot "dm-verity enforcing"
If there is no dm-verity issue, great. No need for this command then.
The unlock and lock bootloader commands you do in fastboot.
The unlock commands are:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
So the re-lock commands are as simple as this:
Code:
fastboot flashing lock
fastboot flashing lock_critical
I am glad I could be of help
Hello, i have my phone Huawei P20 Lite wich is bricked with Phone Locked and FRP lock. I tried to write recovery with fastboot but always receive 'Command not allowed'. It's because my bootloader isn't unlocked...
when i want to power on it's stuck on 'Attention! Please install the update again'
If anyone know how to solve that, please leave an answer there!
orpheum123 said:
Hello, i have my phone Huawei P20 Lite wich is bricked with Phone Locked and FRP lock. I tried to write recovery with fastboot but always receive 'Command not allowed'. It's because my bootloader isn't unlocked...
when i want to power on it's stuck on 'Attention! Please install the update again'
If anyone know how to solve that, please leave an answer there!
Click to expand...
Click to collapse
Hi there
Have you tried to go to eRecovery through power on and Volume+ buttons?
Yes
ars_chelsea said:
Hi there
Have you tried to go to eRecovery through power on and Volume+ buttons?
Click to expand...
Click to collapse
yes, but is stucked on Huawei logo..
orpheum123 said:
yes, but is stucked on Huawei logo..
Click to expand...
Click to collapse
Hallo there
Ok! So you can't really have an unlock code? Cause that would help a lot more... Anyway as for now from all cases I have seen you are telling me this is the hardest one. Altough there is one more chance that you should try.
If you have the stock recovery .img or a TWRP recovery .img you might be able to boot to it and do a hard reset which fixes your issue.
First download the adb tools from here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then extract it to a random folder.
After you have the stock or TWRP recovery .img just copy it to this folder and open it.
If you don't have the stock recovery, I have a link to it here:
https://mega.nz/#!SR9RzKST!dhXS0yC-p_SvWu-SYYLaop1aRFzSulLVrnSXCVVJiGI
Then press shift + right click on the mouse, it should show an option called "Open a Powershell Window here in case you have Windows 10, or "Open a CMD window here" (on windows 8 and below) click that and a window will appear.
Next, if you are on windows 10 and the window says Windows Powershell type ".\fastboot boot imagenamehere.img" if not and you are on Windows 8 or below type "fastboot boot imagenamehere.img".
Where "imagenamehere" is your image name such as recovery.img or twrp.img or usually on this stock recovery recovery_ramdisk.img.
It should boot into recovery
That way you can factory reset if on stock recovery of course.
Either way you gotta lose all your data right now, there's just no way around it without losing data.
Cheers and best of hopes,
AS
ars_chelsea said:
Hallo there
Ok! So you can't really have an unlock code? Cause that would help a lot more... Anyway as for now from all cases I have seen you are telling me this is the hardest one. Altough there is one more chance that you should try.
If you have the stock recovery .img or a TWRP recovery .img you might be able to boot to it and do a hard reset which fixes your issue.
First download the adb tools from here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then extract it to a random folder.
After you have the stock or TWRP recovery .img just copy it to this folder and open it.
If you don't have the stock recovery, I have a link to it here:
https://mega.nz/#!SR9RzKST!dhXS0yC-p_SvWu-SYYLaop1aRFzSulLVrnSXCVVJiGI
Then press shift + right click on the mouse, it should show an option called "Open a Powershell Window here in case you have Windows 10, or "Open a CMD window here" (on windows 8 and below) click that and a window will appear.
Next, if you are on windows 10 and the window says Windows Powershell type ".\fastboot boot imagenamehere.img" if not and you are on Windows 8 or below type "fastboot boot imagenamehere.img".
Where "imagenamehere" is your image name such as recovery.img or twrp.img or usually on this stock recovery recovery_ramdisk.img.
It should boot into recovery
That way you can factory reset if on stock recovery of course.
Either way you gotta lose all your data right now, there's just no way around it without losing data.
Cheers and best of hopes,
AS
Click to expand...
Click to collapse
will not work, because:
"downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.510s"
bootloader are locked, cant do anything!!
Arnys said:
will not work, because:
"downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.510s"
bootloader are locked, cant do anything!!
Click to expand...
Click to collapse
Yeah you are right, my bad :/
I have a simple one, have you tried "fastboot reboot recovery" via the same command line as well? I know it's obvious but that should work for you...
If it doesn't please send me the error code.
Cheers,
AS
I'm also having almost the same issue. My p20 lite is locked to Japan AU network and frp lock but it's not bricked. I want to use it here in Philippines that's why I'm planning to install a stock rom which will work here. Can you help me?
Hello, I have the exact same problem the guy above has, and I tried "Fastboot reboot recovery" and it still didn't work, I believe because of my cellphone. Do you have any more advice?
contact me i will try help
Hi kikson112!
If You are able to help in such problem I would like to ask You for help as well.
My case look similar.
My P20 lite with no reason (nothing I know) got locked . the screen is black and when I try to unlock it shows only time and weather in uper right corner. It looks like it would stuck in flipcover mode but I never had one.
I tried to reset it , reboot it but nothing help.
I tried to connect by Hisuite to download My data but it is not in debugg mode so I cannot connect.
During reset it looks like it is not loading the system.
When I connect my bluetooth headset it connects.
It is playing the alarm in the morning.
But I cannot do anything. The screen does not respond.
Any ideas what could I try to get My data would be apprieciate.
Hi kikson112!
If You are able to help in such problem I would like to ask You for help as well.
My case look similar.
My P20 lite with no reason (nothing I know) got locked . the screen is black and when I try to unlock it shows only time and weather in uper right corner. It looks like it would stuck in flipcover mode but I never had one.
I tried to reset it , reboot it but nothing help.
I tried to connect by Hisuite to download My data but it is not in debugg mode so I cannot connect.
During reset it looks like it is not loading the system.
When I connect my bluetooth headset it connects.
It is playing the alarm in the morning.
But I cannot do anything. The screen does not respond.
Any ideas what could I try to get My data would be apprieciate.
Click to expand...
Click to collapse
hi, for rescue data use converter to connect a mouse in usb port should work, in this case posible digitizer can be just broken, try download software math to ur phone and write it over sd card by 3 buttons (vol - vol + pwr) and post here if any changes
Umm, you can try to get Huawei to do it or youcan buy an unlock key to flash the stuff.
I think there is a special Huawei Flash mode but I don't remember how to access it anymore because I was a Huawei employee and I knew how before but I forgot. Sorry!
hi all, i have the same problem...Huawei logo...
I connect the mobile phone to the PC, press volume - and power and enter "Fastboot & Rescue Mode".
Phone locked
FRP lock
I try to give the command from the terminal, fastboot boot recovery_ramdisk.img, and I have the following messages:
F: \ P20 \ platform-tools_r29.0.5-windows \ platform-tools> fastboot boot recovery_ramd
isk.img
<waiting for any device>
Sending 'boot.img' (32768 KB) OKAY [0.963s]
Booting FAILED (remote: 'Command not
allowed ')
fastboot: error: Command failed
Then try Volume+ buttons, but it restarts showing the initial logo, without going to eRecovery
hi all, i have the same problem...Huawei logo...
I connect the mobile phone to the PC, press volume - and power and enter "Fastboot & Rescue Mode".
Phone locked
FRP lock
I try to give the command from the terminal, fastboot boot recovery_ramdisk.img, and I have the following messages:
F: \ P20 \ platform-tools_r29.0.5-windows \ platform-tools> fastboot boot recovery_ramd
isk.img
<waiting for any device>
Sending 'boot.img' (32768 KB) OKAY [0.963s]
Booting FAILED (remote: 'Command not
allowed ')
fastboot: error: Command failed
Then try Volume+ buttons, but it restarts showing the initial logo, without going to eRecovery
Click to expand...
Click to collapse
is fastboot working and upgrade mode ?
First time poster.... please go gentle on me. Not entirely new to custom roms and TWRP, but really stuck here. I am trying to install a CrDroid ROM. Phone is not networked locked and brand new. What I managed to do so far:
1. Reset the phone
2. reboot into Recovery (Mi Recovery)
3. Wipe data
4. Unlocked the phone (using offical Mi Unlock)
I then proceeded to boot into Fastboot and flashed the TWRP (twrp-3.7.0_12-0-onclite), renamed to recovery. But after flashing and rebooting I can only get into Fastboot, or boot it normally. Holding down the Volume+Up and Power button doesn't get me anywhere but Fastboot. (Same for Volume-Down and Power Up). I tried both un-pluggin the phone from the PC immediately after flashing is finished, and using Fastboot Reboot command, but all to no avail. Its Fastboot or normal boot only.
I also tried whats suggested here upto the vbmeta image, but didn't make a difference. When sending the 'fastboot boot recovery.img' command, I get the following error:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.939s]
booting...
FAILED (remote: unknown reason)
finished. total time: 1.502s
Trying this guide for a 'custom' boot image from this page also didnt help
Really hoping there is a way to get this resolved. But totally stuck here. Have access to both Mac OS and Windows 10. If anyone can point me in the right direction it would be wonderful!
Ok, small update - in hope to help others...
I went ahead and used 'XiaoMiTool V2'to see if it might help to load a different ROM. When starting the app, I choose the 'Bricked' device option, even it wasnt bricked. I choose the Global ROM 12. (The phone showed up as unknown and I didnt sign in with the Mi Account).
After the new ROM was on it, phone started normally and went through the setup. Had to re-enable Developer Options, USB Debugging, but even so it still didnt work - installing the TWRP just kept bringing me back to Fastboot.
However, the TWRP from this page did work: https://twrp.me/xiaomi/xiaomi-mi439.html
I also took no chances and held the Volume up button pressed and with the Command window open and 'fastboot reboot'typed out, hit the Enter key at the same time as pressing the Power button on the phone.
Worked for me!
Try to install PitchBlack Recovery it's very compable PBRP-pine-3.1.0 _OFFICIAL
Timesnaps said:
First time poster.... please go gentle on me. Not entirely new to custom roms and TWRP, but really stuck here. I am trying to install a CrDroid ROM. Phone is not networked locked and brand new. What I managed to do so far:
1. Reset the phone
2. reboot into Recovery (Mi Recovery)
3. Wipe data
4. Unlocked the phone (using offical Mi Unlock)
I then proceeded to boot into Fastboot and flashed the TWRP (twrp-3.7.0_12-0-onclite), renamed to recovery. But after flashing and rebooting I can only get into Fastboot, or boot it normally. Holding down the Volume+Up and Power button doesn't get me anywhere but Fastboot. (Same for Volume-Down and Power Up). I tried both un-pluggin the phone from the PC immediately after flashing is finished, and using Fastboot Reboot command, but all to no avail. Its Fastboot or normal boot only.
I also tried whats suggested here upto the vbmeta image, but didn't make a difference. When sending the 'fastboot boot recovery.img' command, I get the following error:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.939s]
booting...
FAILED (remote: unknown reason)
finished. total time: 1.502s
Trying this guide for a 'custom' boot image from this page also didnt help
Really hoping there is a way to get this resolved. But totally stuck here. Have access to both Mac OS and Windows 10. If anyone can point me in the right direction it would be wonderful!
Click to expand...
Click to collapse
You are trying to install onclite (Redmi 7) recovery on pine (Redmi 7A) ???
mi439 TWRP works for me as well & even successfully flash the rom/gapps. but when it comes to rooting with Magisk, i failed to flash nor install it properly. hope someone/somebody would make a tutorial for flashing/installing Magisk.