I was trying to follow the steps in this guide - https://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308 - and I got hung up at step #7. After flashing the twrp recovery in fastboot, I could not get it to boot into twrp recovery.
Code:
fastboot boot twrp.img
That returned with
Code:
[email protected]:~/$ sudo fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.069s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.089s
And when I tried to reboot it took me into what I thought was the stock recovery warning me that my device was unlocked and not to be trusted and gave me the options to power off, restart, recovery or fastboot. Fastboot takes me to the fastboot mode. Recovery takes me back to this same screen warning me that it isn't to be trusted. Powering off and restarting either take me back to the warning screen or simply give me a blank screen and the white led on.
I don't know where to go from here. I've downloaded the stock rom but I don't think I can flash that from fastboot and I can't get connect to the phone with adb because I can't boot the phone.
Does anyone have any suggestions? Aside from to stop messing with stuff when I don't fully understand what I'm doing that is...
Thanks for any help!
Jono
Go back to fastboot and try booting the stock recovery. Then choose to update worry ADB sideload. That worked for me, but I'm still having issues with TWRP.
Thanks for the reply! When I try that it just takes me back to the screen that says it can't be trusted because it's unlocked and 5 seconds later if I haven't pushed the volume keys it shows the oneplus logo for a second and then the screen goes blank and the white LED comes on.
solved
Ok, I managed to flash the stock recovery; which I downloaded from oneplus directly. I'm a new user here so it won't let me post a link but they do provide a download for the stock recovery there.
At that point I was able to reboot into recovery, and now I can get it to start up again. Here's what I did in case anyone needs help.
Code:
[email protected]:~/$ sudo fastboot devices
[sudo] password for jono:
bb1c12d3 fastboot
[email protected]:~/$ sudo fastboot flash recovery recovery_OBT7.img
target reported max download size of 442499072 bytes
sending 'recovery' (22237 KB)...
OKAY [ 0.555s]
writing 'recovery'...
OKAY [ 0.171s]
finished. total time: 0.725s
[email protected]:~/$ sudo fastboot boot recovery_OBT7.imgdownloading 'boot.img'...
OKAY [ 0.544s]
booting...
OKAY [ 0.322s]
finished. total time: 0.865s
Hope that helps anyone else. After I did that it rebooted and took me through the whole setup procedure. I'm going to hold off on trying to root this thing for now.
Related
I followed mike1986 "complete flashing guide"
s I unlocked bootloader - OK unlocked
then I do boot recovery to make nandroid backup first:
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.193s]
booting...
OKAY [ 0.001s]
finished. total time: 1.194s
so I try flash recovery:
fastboot flash recovery recovery.img
sending 'recovery' (9840 KB)...
after that my phone stuck in fastboot mode, it's screen is turned ON all the time, I can't even turn it OFF
Do i bricked my phone, please help
zukers said:
I followed mike1986 "complete flashing guide"
s I unlocked bootloader - OK unlocked
then I do boot recovery to make nandroid backup first:
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.193s]
booting...
OKAY [ 0.001s]
finished. total time: 1.194s
so I try flash recovery:
fastboot flash recovery recovery.img
sending 'recovery' (9840 KB)...
after that my phone stuck in fastboot mode, it's screen is turned ON all the time, I can't even turn it OFF
Do i bricked my phone, please help
Click to expand...
Click to collapse
Hold down the power button and vol down button untill the phone reboots to the bootloader again. Make sure its in fastboot mode and type
Code:
fastboot erase cache
Then type
Code:
fastboot flash recovery recovery.img
Then
Code:
fastboot reboot-recovery
Hopefully it will boot into recovery.
zukers said:
fastboot boot recovery.img
Click to expand...
Click to collapse
only works on hboot 1.44.
as mentioned above hold POWER + VOLDOWN (under a bright light), when it reboots let go of POWER but keep holding VOLDOWN, once in bootloader follow steps above to flash recovery
i think "fastboot reboot-recovery" doesn't work (at least for me), so do a "fastboot reboot-bootloader" then enter recovery.
zukers said:
I followed mike1986 "complete flashing guide"
s I unlocked bootloader - OK unlocked
then I do boot recovery to make nandroid backup first:
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.193s]
booting...
OKAY [ 0.001s]
finished. total time: 1.194s
so I try flash recovery:
fastboot flash recovery recovery.img
sending 'recovery' (9840 KB)...
after that my phone stuck in fastboot mode, it's screen is turned ON all the time, I can't even turn it OFF
Do i bricked my phone, please help
Click to expand...
Click to collapse
I had the EXACTLY same error as you. Didn't know what caused it. After about 20 attemps I finally managed to flash it. I changed the USB Port several times... But I didn't do any other things. Just try and try and try again. And whenever your screen freezes, do what @nkk71 said.
Volume down + Power button for several seconds...
OK, I have resolved my problem, thanks all of You.
Hi all - I'm not entirely stupid, but I'm probably doing something basically wrong here.
I'm trying to convert my Chinese CRR-UL00 to something a bit more western, but still with dual SIMs, so converting it to Middle East/Africa model seems like a good idea. I'm not interested in root or even a custom recovery in the long term. I just want to change regions.
I have been trying to follow the instructions both here and elsewhere but am getting stuck early in the process. I've tried a bunch of different things so my phone may be in an odd state.
I have, I believe, unlocked the bootloader via DC-Unlocker. When I reboot into the bootloader (using adb reboot bootloader) I get a white screen with a header that says "Fastboot&Rescue mode", an Android icon, and "Phone Unlocked" in red underneath.
Attempting to flash a TWRP recovery.img using fastboot doesn't seem to have any effect, even though fastboot reports it has successfully transferred the image. Trying to boot into recovery - either using adb/fastboot or vol+/power keys results in the phone hanging at the Huawei logo at bootup. I've also tried to flash back a "stock" recovery.img. At no time have I been able to get the fastboot menu on the phone - it's either the white screen with no options, or the phone hanging at the Huawei logo.
Despite all this the phone will still operate normally! When operating normally the phone now reports its running CRR-UL00C00B172.
Any ideas what I'm doing wrong? What recovery.img should I use?
Thanks for any help!
WD
I'm not home right now but from memory the one I've used was named somthing like TWRP-2.8.7.0-Carrera.img
Thank you for the quick reply. I've had some time to have another go at this. Still can't seem to get TWRP recovery onto the phone...
It seems to flash...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp3.img
target reported max download size of 471859200 bytes
sending 'recovery' (24454 KB)...
OKAY [ 0.532s]
writing 'recovery'...
OKAY [ 0.242s]
finished. total time: 0.787s
but then rebooting and holding down various keys to get into Recovery, I either get a hang at the Huawei logo, or I eventually end up back at the stock recovery. (I think if it boots to the full OS it overwrites any TWRP recovery)
What is the actual key combo to get into recovery? Various web pages report different combos:
- vol+ and vol- and power
- vol+ and power
- ?? something else
Many thanks,
wd
wonky donkey said:
Thank you for the quick reply. I've had some time to have another go at this. Still can't seem to get TWRP recovery onto the phone...
It seems to flash...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp3.img
target reported max download size of 471859200 bytes
sending 'recovery' (24454 KB)...
OKAY [ 0.532s]
writing 'recovery'...
OKAY [ 0.242s]
finished. total time: 0.787s
but then rebooting and holding down various keys to get into Recovery, I either get a hang at the Huawei logo, or I eventually end up back at the stock recovery. (I think if it boots to the full OS it overwrites any TWRP recovery)
What is the actual key combo to get into recovery? Various web pages report different combos:
- vol+ and vol- and power
- vol+ and power
- ?? something else
Many thanks,
wd
Click to expand...
Click to collapse
- flash stock recovery
- boot device normaly
- go into developersettings and look for OEM-Unlock
- if available, enable it. if not go to fastboot mode and use "OEM-Unlock" command with code again. (sometimes the bootloader isn´t unlocked fully on first try)
- then try to flash TWRP 2.8.7.0
- fastboot reboot
anyway whats your current build?
i can only access recovery via. "adb reboot recovery" command
Thanks for the help. Clearly I'm doing something wrong.
On rebooting normally after flashing recovery I don't see an OEM-unlock option in Developer Options. Attempting to fastboot oem unlock again gives me failed, already unlocked.
I've tried four different downloads of TWRP recovery from different places, I've even tried different adb/fastboot binaries to make sure that's not the issue. The TWRP recovery images I have are:
25,040,896 bytes (three different downloads, and I've seen one or two sites that claim this is only for the L09 version)
25,378,816 bytes (from a random Chinese web site that says its for the CRR-UL00 B131)
I'm on CRR-UL00C00B172. I wonder if I need to flash everything back to something earlier? (e.g. I have a full download of UL00C00B153).
wd
OK, success!
At some point I ended up in stock recovery and it suggested to download and install UL00C00B131. (why B131? Maybe because at some point I had been using the Chinese download with B131 on it?). Did so.
adb reboot bootloader
relock and unlock to confirm unlock is definitely working in fastboot
fastboot reboot
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
adb reboot recovery
...now I'm into TWRP!
Thanks all for your help.
wd
...and now I've got it localised to MEAFNAF (C433) - so still dual SIM but with Google Play by default etc. Running CRR00-UL00C433B146 which is available from Huawei.
I followed these instructions. (based on the original Russian post but much better than Google Translate
At the end, the install of update.app hung at 90%. Using vol+/power to get into recovery dropped me into a Chinese recovery (probably from the recovery.img I flashed back to remove TWRP). Factory resetting from recovery resulted in booting to the full OS, but I didn't get the option to enter a Google ID in setup and the full OS was dog slow with a black home screen.
Doing another factory reset, I was then asked for a Google ID during setup, and this time resulted in a fully functioning Googley OS.
I understand I won't get OTA updates as I've changed my localization, so I'll keep an eye out for the final Marshmallow release from Huawei's web site.
I hope this thread is useful to others.
wd
To start, I have no knowledge on rooting other than simply using ODIN on one of my older Samsung devices.
I had got a Moto E5 Play the other day and decided to root it today. It was difficult finding a tutorial, but I found this one (https://www.rootingtutorials.com/android-rooting/root-moto-e5-play/)
I downloaded the Minimal ADB and Fastboot tool, and flashed the custom ROM that the post recommended me to do. Then downloaded Magisk and I couldn't install it directly as noted in the guide and after some research found out I had to flash it manually, but I only had the stock recovery for some reason. Found another tutorial from this website (https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323)
I flashed the no-verity kernel and now my phone is in a boot loop. I freaked out and wiped the data and factory reset it. Now when I turn on my phone it says "bad key" in the top left corner and then it goes to the screen before the boot animations and stays there (motorola logo and powered by android at the bottom)
I am an idiot and shouldn't have done this. Is there anything I can do to fix it?
j256 said:
To start, I have no knowledge on rooting other than simply using ODIN on one of my older Samsung devices.
I had got a Moto E5 Play the other day and decided to root it today. It was difficult finding a tutorial, but I found this one (https://www.rootingtutorials.com/android-rooting/root-moto-e5-play/)
I downloaded the Minimal ADB and Fastboot tool, and flashed the custom ROM that the post recommended me to do. Then downloaded Magisk and I couldn't install it directly as noted in the guide and after some research found out I had to flash it manually, but I only had the stock recovery for some reason. Found another tutorial from this website (https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323)
I flashed the no-verity kernel and now my phone is in a boot loop. I freaked out and wiped the data and factory reset it. Now when I turn on my phone it says "bad key" in the top left corner and then it goes to the screen before the boot animations and stays there (motorola logo and powered by android at the bottom)
I am an idiot and shouldn't have done this. Is there anything I can do to fix it?
Click to expand...
Click to collapse
Restore the stock firmware using the instructions here: https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901
konradsa said:
Restore the stock firmware using the instructions here: https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901
Click to expand...
Click to collapse
Thanks for replying.
I can't do this because I hard reset the phone and USB debugging is no longer on. "adb devices" recalls back nothing and inputting something like "adb reboot recovery" comes back with "no devices/emulators found".
Tried to input "fastboot flash partition gpt.bin" and get back:
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.047s
What can I do?
j256 said:
Thanks for replying.
I can't do this because I hard reset the phone and USB debugging is no longer on. "adb devices" recalls back nothing and inputting something like "adb reboot recovery" comes back with "no devices/emulators found".
Tried to input "fastboot flash partition gpt.bin" and get back:
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.047s
What can I do?
Click to expand...
Click to collapse
Did you boot the phone into fastboot mode? You don't need debugging on for fastboot.
The ,"bad key" is normal.
Looks like the wrong firmware or your bootloader is still locked
j256 said:
To start, I have no knowledge on rooting other than simply using ODIN on one of my older Samsung devices.
I had got a Moto E5 Play the other day and decided to root it today. It was difficult finding a tutorial, but I found this one (https://www.rootingtutorials.com/android-rooting/root-moto-e5-play/)
I downloaded the Minimal ADB and Fastboot tool, and flashed the custom ROM that the post recommended me to do. Then downloaded Magisk and I couldn't install it directly as noted in the guide and after some research found out I had to flash it manually, but I only had the stock recovery for some reason. Found another tutorial from this website (https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323)
I flashed the no-verity kernel and now my phone is in a boot loop. I freaked out and wiped the data and factory reset it. Now when I turn on my phone it says "bad key" in the top left corner and then it goes to the screen before the boot animations and stays there (motorola logo and powered by android at the bottom)
I am an idiot and shouldn't have done this. Is there anything I can do to fix it?
Click to expand...
Click to collapse
you need to download 'lenovo moto smart assistant. when you opened the application you need to go to the rescue page. then click on moto phone and select your model. once the download is completed you need to click on rescue and the rescue will begin. after the rescue is completed you can boot your phone like it usually does.
This thread is one and half years old.
Sent from my jerry_cheets using XDA Labs
hi have a bricked p8 lite in front of me. when i start the phone im in rescue mode and get the rror:
func no 7(teeos image)
error no 1(security verify failed)
with power button + vol+ i cant boot into recovery. phone does nothing. just blinks red.
booting into fastboot is possible. bootloader is apperently locked(phone locked). if its possible to install twrp with a locked bootloader then ive done so via this tutorial. if not, am i f+++ed because huawai doesnt give out unlock codes?
i guess it doesnt work with a locked bootloader:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp1.img
target reported max download size of 471859200 bytes
sending 'recovery' (31572 KB)...
OKAY [ 0.828s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.830s
is it possible to reboot into recovery via fastboot? fastboot reboot recovery dosnt seem to work.
any suggestions what i could try next?
with locked bootloader, you're pretty fu****d... but, some third party app/sites give bootloader codes for some money... had something similar long time ago, fortunately for me, I had my bootloader unlocked... I guess there aren't other solutions... and from fastboot, you can't go to recovery...
---------- Post added at 10:13 ---------- Previous post was at 10:10 ----------
k2828 said:
hi have a bricked p8 lite in front of me. when i start the phone im in rescue mode and get the rror:
func no 7(teeos image)
error no 1(security verify failed)
with power button + vol+ i cant boot into recovery. phone does nothing. just blinks red.
booting into fastboot is possible. bootloader is apperently locked(phone locked). if its possible to install twrp with a locked bootloader then ive done so via this tutorial. if not, am i f+++ed because huawai doesnt give out unlock codes?
i guess it doesnt work with a locked bootloader:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp1.img
target reported max download size of 471859200 bytes
sending 'recovery' (31572 KB)...
OKAY [ 0.828s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.830s
is it possible to reboot into recovery via fastboot? fastboot reboot recovery dosnt seem to work.
any suggestions what i could try next?
Click to expand...
Click to collapse
okay found this, you can try it... I too got my code this way, but back then Huawei was open to unlocking bootloaders, now cannot say... but you can still try
unfortunatly the led just blinks red when i press all 3 buttons. flashing a stockrom or parts of via fastbootin locked bootloader also isnt possible i guess?
today i unlocked ale-l21 with dc-unlocker for 4 euros.
You need to install stock android 5 and root it with kingroot, then open a bash terminal and get the bootloader code with grep, there's a tutorial on how to do all of this, and it's free. This should also unbrick your phone. If you have an sd card you should be fine. If not, you may encounter complications but you should be able to do it too.
(I'm with Google Translate)
Hello I have a Xiaomi Redmi 10C device and I tried to install a recovery but I did it wrong and I installed it on the boot partition the device when it turns on stays a while on the screen with the xiaomi logo and then goes to the loading screen puando finishes loading the screen turns black and the loading screen returns as well as a loop I need help and is no longer What to do
When flashing the recovery in the boot it tells me this:
Sending 'boot_a' (131072 KB) OKAY [ 3.108s]
Writing 'boot_a' OKAY [ 0.479s]
Finished. Total time: 3.633s
If Fastboot mode is possible:
Downloaded the Fastboot rom identical to the one on the device and extract the boot.img from the images folder then flash it with a fastboot cmd.
NOSS8 said:
If Fastboot mode is possible:
Downloaded the Fastboot rom identical to the one on the device and extract the boot.img from the images folder then flash it with a fastboot cmd.
Click to expand...
Click to collapse
now the device is in bootloop showing the logo of Xiaomi and android and the screen turns on and off but I can still access to the Fastboot so I'm going to try it