Hello!
I have Nokia 5 TA-1053 which is restarting all the time. I'm trying to flash it with Ost (6.1.2) but it still stuck on reflash service bootloader. How can I fix it?
Thx in advance.
haller said:
Hello!
I have Nokia 5 TA-1053 which is restarting all the time. I'm trying to flash it with Ost (6.1.2) but it still stuck on reflash service bootloader. How can I fix it?
Thx in advance.
Click to expand...
Click to collapse
Service bootloader cannot be flashed because of restrictions during the update to a late Oreo version.
If you boot to phone recovery (stock version) and try to "upgrade" an Ota-zip before sept. 2018 the process will abort, but your bootloader will be set to a version your able to deal with OST.
Spartan42 said:
Service bootloader cannot be flashed because of restrictions during the update to a late Oreo version.
If you boot to phone recovery (stock version) and try to "upgrade" an Ota-zip before sept. 2018 the process will abort, but your bootloader will be set to a version your able to deal with OST.
Click to expand...
Click to collapse
I can't boot into recovery. Only Download mode.
Maybe it is caused by a blocked bootloader?
haller said:
I can't boot into recovery. Only Download mode.
Click to expand...
Click to collapse
Nokia 5s boot to recovery is a little bit tricky.
Try following:
1. Connect your phone to pc and head into download mode (type in Terminal on running system "adb reboot bootloader")
2. Typ there "fastboot reboot" in (windows) Terminal
3. During reboot hold the Power + Volume Up buttons until the phone vibrates
4. Release the Power button when phone vibrates, but keep holding Volume Up until you arrive at recovery
5. Now you should be in recovery mode
Spartan42 said:
Nokia 5s boot to recovery is a little bit tricky.
Try following:
1. Connect your phone to pc and head into download mode (type in Terminal on running system "adb reboot bootloader")
2. Typ there "fastboot reboot" in (windows) Terminal
3. During reboot hold the Power + Volume Up buttons until the phone vibrates
4. Release the Power button when phone vibrates, but keep holding Volume Up until you arrive at recovery
5. Now you should be in recovery mode
Click to expand...
Click to collapse
I managed to get into recovery with your advice. I uploaded by update "May 2018 TA-1053 OTA update" and then by ost ND1-3700-0-00WW-B03.
But it's still stuck on the bootloader.
I also flashed with december 2017 update zip and after that ost reboot my pgone again to download mode, but shows me battery voltage too low.
haller said:
... but shows me battery voltage too low.
Click to expand...
Click to collapse
This error is unknown to me in connection with OST. Maybe put the AC in and load it some time bevore another try would help?
Spartan42 said:
This error is unknown to me in connection with OST. Maybe put the AC in and load it some time bevore another try would help?
Click to expand...
Click to collapse
Ok. I tried few times and finally phone flashed and it's alive again
Thx for helping.
BR.
What exactly did you do? I'm having the same issue right now
hii. Can u tell me how u solve it ?
Related
So, I have a ZenFone 5 (A500CG) WW running on a stock-based custom Lollipop ROM (Recreated Remix-Leopard). In an attempt to return to KitKat in order to test some app, I accidentally flashed a bad fastboot.img file. All was too late after I pressed the ENTER key. Although the device still booted and could also enter the stock Recovery mode, attempting to boot into fastboot is a fail (stuck on ASUS logo.)
Now, after an attempt to fix it by ADB Sideloading ASUS' stock 3.24.x Lollipop firmware, my device is technically bricked. Trying to boot it only takes me to the "dead droid" screen (Recovery mode). Attempting to boot into Fastboot (whether Power + VolUp or Reboot to bootloader via the Recovery menu) is a failure. I remain stuck at the ASUS logo.
I've seen the tutorial about unbricking the ZenFone 5 without Fastboot and Recovery (even with ruined partitions) but I found it too bothersome. I'm thinking that since I still have the stock Recovery in my pocket, is there a way to at least restore Fastboot via Recovery? Or better yet, a one-mode solution to install stock ASUS firmware without having to downgrade the Recovery menu (because Fastboot is dead.) Thank you for any help.
to enter recovery mode, u can try key combination :
POWER + VOL UP... when your phone's vibrate, pres VOL DOWN until "dead droid" come, u must release all button then press and hold POWER, press VOL UP Once.
CrazeVjr said:
to enter recovery mode, u can try key combination :
POWER + VOL UP... when your phone's vibrate, pres VOL DOWN until "dead droid" come, u must release all button then press and hold POWER, press VOL UP Once.
Click to expand...
Click to collapse
I know that's how you get to Fastboot, but if you read my entire post, I wrote that I could not access Fastboot, whether through hardware (Power + VolUp) or through the Recovery menu's "Reboot to bootloader" option.
cnswico said:
I know that's how you get to Fastboot, but if you read my entire post, I wrote that I could not access Fastboot, whether through hardware (Power + VolUp) or through the Recovery menu's "Reboot to bootloader" option.
Click to expand...
Click to collapse
sorry, i just read that u want install stock fw. everything is ok if u can access recovery without any error...just sideload via adb (do downgrade/upgrade).
CrazeVjr said:
sorry, i just read that u want install stock fw. everything is ok if u can access recovery without any error...just sideload via adb (do downgrade/upgrade).
Click to expand...
Click to collapse
It's cool.
Yea. I tried doing that. Doesn't work:
I have the Recovery mode for 3.24 Lollipop FW. If I tried to install an older one (i.e. a KitKat stock ROM), it just throws me an error saying that I can only sideload an older FW. However, if I tried sideloading the same 3.24 FW, it just throws me an "Unknown command" upon the sideload reaching about 36%. It's always been like that, I can assure. I am very certain it is not caused by a faulty data connection.
Any way around this? Thanks!
cnswico said:
It's cool.
Yea. I tried doing that. Doesn't work:
I have the Recovery mode for 3.24 Lollipop FW. If I tried to install an older one (i.e. a KitKat stock ROM), it just throws me an error saying that I can only sideload an older FW. However, if I tried sideloading the same 3.24 FW, it just throws me an "Unknown command" upon the sideload reaching about 36%. It's always been like that, I can assure. I am very certain it is not caused by a faulty data connection.
Any way around this? Thanks!
Click to expand...
Click to collapse
try flash with 5.3.3.3 FW that's FW for downgrade all lolipop zenfone 5...
note : just make sure your 5.3.3.3 region (TW/WW/CH/CHT)
CrazeVjr said:
try flash with 5.3.3.3 FW that's FW for downgrade all lolipop zenfone 5...
note : just make sure your 5.3.3.3 region (TW/WW/CH/CHT)
Click to expand...
Click to collapse
Done, and BAM! Problem solved! Thanks!:good:
Hi all,
Please help me!
I think i messed up pretty badly here. I tried downgrading from Oreo to Nougat but I think I tried to install a wrong image. Now when i boot i get:
ERROR MODE
Attention! Please update system again
Error!
Fun NO : 15 (bl31 image)
Error NO : 1 (security verify failed)
I've tried the dload method but it doesn't even start. I boot it up holding power, vol+, vol-, and it gets stuck at "your device is booting now."
I can't access twrp, even after flashing it again.
I can get into fastboot and I've tried manually flashing images from an update.app, but after that, the same problem still persists. Trying to relock the boot loader gives an error "command not allowed"
Does anybody have any ideas?
yes i have same because battery is not dead still wait battery remain if dead then plug against work fastboot need firmware rollback version only C432B185 try HWOTA this is the best
Gamkutopolowk said:
yes i have same because battery is not dead still wait battery remain if dead then plug against work fastboot need firmware rollback version only C432B185 try HWOTA this is the best
Click to expand...
Click to collapse
So you're saying that I wait until my battery drains, then go into fastboot and roll back to C432B185? Maybe you could help me by outlining the steps to flash via fastboot?
flash via fastboot by HWOTA follow this link https://romprovider.com/2018/01/download-install-b185-nougat-update-huawei-p10-plus/
only method 1
Gamkutopolowk said:
flash via fastboot by HWOTA follow this link
only method 1
Click to expand...
Click to collapse
So i tried this method, but it didn't work. It flashes TWRP, and instructs me to disconnect the USB cable and boot into TWRP, but i can't boot into TWRP. It goes directly to the error message even when holding the buttons down.
because stuck in fastboot is freeze or corrupted still wait battery drains when dead battery hold vol down + plug USB then run in HWOTA...............
Gamkutopolowk said:
because stuck in fastboot is freeze or corrupted still wait battery drains when dead battery hold vol down + plug USB then run in HWOTA...............
Click to expand...
Click to collapse
So after waiting for the battery to drain, holding vol down, and plugging the USB, I'm back where I was before with being in fastboot. Running HWOTA results in the same problem for when it tells me to reboot to TWRP after install, the phone goes to error mode.
I'm pretty sure the bl31 image corruption is preventing me from booting into recovery.
try other methode if work or not run fastboot need files from huawei firmware extractor open Update.app save files boot.img + recovery.img + system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Test it
Gamkutopolowk said:
try other methode if work or not run fastboot need files from huawei firmware extractor open Update.app save files boot.img + recovery.img + system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Test it
Click to expand...
Click to collapse
Ok so i flashed boot.img, recovery.img, system.img all OKAY.
Reboot and i get the same error..
The problem is with the bl31 image, which is in ARM Trusted Firmware.
Maybe if i could figure out how to flash TRUSTFIRMWARE.img that would work. I tried this, but it doesn't work. I don't know the partition name.
fastboot flash trustfirmware
unknown partition 'trustfirmware'
Try HWOTA flash TWRP then hold power + vol up stay hold vol up long 15 seconds
Gamkutopolowk said:
Try HWOTA flash TWRP then hold power + vol up stay hold vol up long 15 seconds
Click to expand...
Click to collapse
Still goes straight to the error screen.
blahblah31415 said:
Still goes straight to the error screen.
Click to expand...
Click to collapse
Please show me your mobile
blahblah31415 said:
Ok so i flashed boot.img, recovery.img, system.img all OKAY.
Reboot and i get the same error..
The problem is with the bl31 image, which is in ARM Trusted Firmware.
Maybe if i could figure out how to flash TRUSTFIRMWARE.img that would work. I tried this, but it doesn't work. I don't know the partition name.
fastboot flash trustfirmware
unknown partition 'trustfirmware'
Click to expand...
Click to collapse
thank you sir u saved my phone from drowning just flashed this trustedfirmware and hurray my phone got out of error mode
Junaid Shafi said:
thank you sir u saved my phone from drowning just flashed this trustedfirmware and hurray my phone got out of error mode
Click to expand...
Click to collapse
How you did that?
blahblah31415 said:
Hi all,
Please help me!
I think i messed up pretty badly here. I tried downgrading from Oreo to Nougat but I think I tried to install a wrong image. Now when i boot i get:
ERROR MODE
Attention! Please update system again
Error!
Fun NO : 15 (bl31 image)
Error NO : 1 (security verify failed)
I've tried the dload method but it doesn't even start. I boot it up holding power, vol+, vol-, and it gets stuck at "your device is booting now."
I can't access twrp, even after flashing it again.
I can get into fastboot and I've tried manually flashing images from an update.app, but after that, the same problem still persists. Trying to relock the boot loader gives an error "command not allowed"
Does anybody have any ideas?
Click to expand...
Click to collapse
Hi
I have the exact same problem
After trying all of the methods I found (dload, HWOTA, TWRP, etc), I finally took the phone to the service center.
They told me it was an easy fix, then they called me and told me that probably they were going to replace the motherboard
I'm still waiting for them to call me for confirmation.
If you got any news on this, please keep posting
Thanks!
gonzalomorenorovetto said:
Hi
I have the exact same problem
After trying all of the methods I found (dload, HWOTA, TWRP, etc), I finally took the phone to the service center.
They told me it was an easy fix, then they called me and told me that probably they were going to replace the motherboard
I'm still waiting for them to call me for confirmation.
If you got any news on this, please keep posting
Thanks!
Click to expand...
Click to collapse
I actually ended up using dc pheonix to fix it. It worked perfectly. I had to pay about 15 dollars for credits. It used some sort of backdoor and flashed a new ROM from scratch.
blahblah31415 said:
I actually ended up using dc pheonix to fix it. It worked perfectly. I had to pay about 15 dollars for credits. It used some sort of backdoor and flashed a new ROM from scratch.
Click to expand...
Click to collapse
I tried DC Phoenix and It did not work. They returned me my money.
At the service center they finally replaced my motherboard, in warranty, even though the phone was unlocked and I bricked it completely
Please Help me...
I have already tried everything possible.
P8 lite only starts in the fastboot mode.
Error
Func NO : 9 (dsp image)
Error NO : 1 (security verify failed ! )
sorry for my english
Flash stock UPDATE.APP by putting it in the dload folder on the sd card and then holding vol- vol+ and power button to force the update.
Botar230 said:
Flash stock UPDATE.APP by putting it in the dload folder on the sd card and then holding vol- vol+ and power button to force the update.
Click to expand...
Click to collapse
not working.....
i flash system,cust,recovery,userdata,boot in fastboot
fastboot say Ok..
i flash dsp image, fastboot says error
phone starts only in rescue mode with
func no : 9 dsp image
error no : 1 security verify failed
or Fastboot mode
HELP me Please
and sorry for my english
BigH187 said:
not working.....
Click to expand...
Click to collapse
Can you give more details of how it is not working? Like does it even start to prepare update?
keikari said:
Can you give more details of how it is not working? Like does it even start to prepare update?
Click to expand...
Click to collapse
I flash all images with fastboot (many roms) fastboot say OK
cant enter Recovery or eRecovery.
push the power button, phone start in rescue mode.
nothing works ,only rescue mode and fastboot mode.
BigH187 said:
I flash all images with fastboot (many roms) fastboot say OK
cant enter Recovery or eRecovery.
push the power button, phone start in rescue mode.
nothing works ,only rescue mode and fastboot mode.
Click to expand...
Click to collapse
It should still be able to do force update or at least fail to do it. Make sure you have like >70% battery. Put UPDATE.APP in folder named dload in your sd-card and hold 'vol -, vol + and power.'
BigH187 said:
I flash all images with fastboot (many roms) fastboot say OK
cant enter Recovery or eRecovery.
push the power button, phone start in rescue mode.
nothing works ,only rescue mode and fastboot mode.
Click to expand...
Click to collapse
If your phone still boots in rescue mode, then I think the rom you've flashed is not compatible with your phone. As @up said, try to force an update.
Sent from my LG-K220 using XDA Labs
Botar230 said:
If your phone still boots in rescue mode, then I think the rom you've flashed is not compatible with your phone. As @up said, try to force an update.
Sent from my LG-K220 using XDA Labs
Click to expand...
Click to collapse
The only keyboard shortcut that works is v - and power for fastboot mode.
Ok ... and what could be the right rom?
The last Rom that worked was the slimrom Marshmallow for Ale-L21.
I believe singel sim
Thanks for help
BigH187 said:
The only keyboard shortcut that works is v - and power for fastboot mode.
Ok ... and what could be the right rom?
The last Rom that worked was the slimrom Marshmallow for Ale-L21.
I believe singel sim
Thanks for help
Click to expand...
Click to collapse
I came up with the following solution:
1. Flash TWRP (fastboot flash recovery <path>.img)
2. Type fastboot reboot and then unplug the usb cable as fast as you can and hold vol+ to boot into twrp.
3. Wipe -> Swipe to Factory Reset
4. Wipe -> Format Data
5. Download B896_update.zip
6. Advanced -> ADB Sideload -> Swipe to Start Sideload
7. adb sideload <path_to_b896>.zip
8. Once the process is finished, reboot the phone.
keikari said:
It should still be able to do force update or at least fail to do it. Make sure you have like >70% battery. Put UPDATE.APP in folder named dload in your sd-card and hold 'vol -, vol + and power.'
Click to expand...
Click to collapse
Hello, I have the same problem! I'll tell you in detail: the phone starts only in rescue mode ...
Nowhere to go just into the fast boot mode, please help me how to fix it!
(...The-PhoenixX...) said:
Hello, I have the same problem! I'll tell you in detail: The phone is loaded in mode always, after 3 buttons it is launched in the rescue mode, in recovery - the same problem! I ask to help or assist as it to correct!
Click to expand...
Click to collapse
Try this:
Botar230 said:
I came up with the following solution:
1. Flash TWRP (fastboot flash recovery <path>.img)
2. Type fastboot reboot and then unplug the usb cable as fast as you can and hold vol+ to boot into twrp.
3. Wipe -> Swipe to Factory Reset
4. Wipe -> Format Data
5. Download B896_update.zip
6. Advanced -> ADB Sideload -> Swipe to Start Sideload
7. adb sideload <path_to_b896>.zip
8. Once the process is finished, reboot the phone.
Click to expand...
Click to collapse
(...The-PhoenixX...) said:
Hello, I have the same problem! I'll tell you in detail: the phone starts only in rescue mode ...
Nowhere to go just into the fast boot mode, please help me how to fix it!
Click to expand...
Click to collapse
What were you trying to do when problem started. It probably won't do anything at your state, but have you tried to hold vol+ in fastboot mode, normally it should go to eRecovery.(not that you can do anything with it, but would be good to know)
Also try things with usb cable plugged and un-plugged this really makes difference in some cases.
keikari said:
It should still be able to do force update or at least fail to do it. Make sure you have like >70% battery. Put UPDATE.APP in folder named dload in your sd-card and hold 'vol -, vol + and power.'
Click to expand...
Click to collapse
Botar230 said:
Try this:
Click to expand...
Click to collapse
The problem is that in the recovery does not come
---------- Post added at 02:42 PM ---------- Previous post was at 02:38 PM ----------
keikari said:
It should still be able to do force update or at least fail to do it. Make sure you have like >70% battery. Put UPDATE.APP in folder named dload in your sd-card and hold 'vol -, vol + and power.'
Click to expand...
Click to collapse
keikari said:
What were you trying to do when problem started. It probably won't do anything at your state, but have you tried to hold vol+ in fastboot mode, normally it should go to eRecovery.(not that you can do anything with it, but would be good to know)
Also try things with usb cable plugged and un-plugged this really makes difference in some cases.
Click to expand...
Click to collapse
I uninstalled the firmware before the problem happened!
the loader is unlocked
(...The-PhoenixX...) said:
The problem is that in the recovery does not come
Click to expand...
Click to collapse
The recovery does not come? What do you mean?
My solution works only on P8 lite 2015 (that's the op's phone model).
(...The-PhoenixX...) said:
I uninstalled the firmware before the problem happened!
the loader is unlocked
Click to expand...
Click to collapse
How exactly you did it? That should never be necessary or good idea to do.(Unless you are only wiping partitions in recovery.)
Hey ... I've tried everything here and in other forums. No matter what I tried I can only boot the fastboot mode.
What the hell is actually a dsp.img?
BigH187 said:
Hey ... I've tried everything here and in other forums. No matter what I tried I can only boot the fastboot mode.
What the hell is actually a dsp.img?
Click to expand...
Click to collapse
I also have this problem
I got this error trying to change my data to f2fs and install MorfuZ V3.4
spend all afternoon without finding solutions
dload in microsd don't work i try with 4 firmwares
any help please?:crying:
...i try to flash ROM_MORFUZ_3.4_EMUI8_HONOR8LITE_BY_CATUVA21.ZIP
...now Can't recovery, can't fastboot...
Huawei Multi Tool don't runs
Huawei P8 lite ALE L21
EgonsS said:
...i try to flash ROM_MORFUZ_3.4_EMUI8_HONOR8LITE_BY_CATUVA21.ZIP
...now Can't recovery, can't fastboot...
Huawei Multi Tool don't runs
Huawei P8 lite ALE L21
Click to expand...
Click to collapse
The rom you've flashed is not compatible with P8 lite 2015. Unfortunately, you've probably hardbricked your phone - there is no way to fix it.
Hello guys,
I wanted to flash recovery, but i can't (as you can see in the picture).
I have unlocked bootloader (i used this method:https://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701).
I tried with other twrps, like elite twrp, twrp, and from the quide that i mentiond, that twrp too.
When i enter recovery:
What should i do?
HunXavar said:
Hello guys,
I wanted to flash recovery, but i can't (as you can see in the picture).
I have unlocked bootloader (i used this method:https://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701).
I tried with other twrps, like elite twrp, twrp, and from the quide that i mentiond, that twrp too.
When i enter recovery:
What should i do?
Click to expand...
Click to collapse
Hello,
if i'm correct you are still on android 6.x/emui 4.x.
You used SRKTool so why haven't used that tool to flash recovery too ?
It's included in the tool.
You need 3.0.2-0 for your android version.
If you want to flash it with fastboot, when finished
disconnect from pc and manually reboot recovery holding vol+ and power buttons.
Cheers
Dadditz said:
Hello,
if i'm correct you are still on android 6.x/emui 4.x.
You used SRKTool so why haven't used that tool to flash recovery too ?
It's included in the tool.
You need 3.0.2-0 for your android version.
If you want to flash it with fastboot, when finished
disconnect from pc and manually reboot recovery holding vol+ and power buttons.
Cheers
Click to expand...
Click to collapse
I'm on android 7.0, and emui 5.0.
That could caused the problem? When i turn on my phone it says: "Your device has been unlocked and can't be trusted".
Anyway thanks for helping!
**EDIT**
It somehow starterd to working, so sorry for wasting your time.
HunXavar said:
I'm on android 7.0, and emui 5.0.
That could caused the problem? When i turn on my phone it says: "Your device has been unlocked and can't be trusted".
Anyway thanks for helping!
**EDIT**
It somehow starterd to working, so sorry for wasting your time.
Click to expand...
Click to collapse
Aah ok android 7, so the TWRP 3.1.1-1 is fine ...
Maybe you should have tried with
> fastboot reboot recovery and disconnect from the PC.
Anyway you've solved then is ok ...
Greetings
HunXavar said:
**EDIT**
It somehow starterd to working, so sorry for wasting your time.
Click to expand...
Click to collapse
Which TWRP did you manage to install? I have the same problem.
radekg12 said:
Which TWRP did you manage to install? I have the same problem.
Click to expand...
Click to collapse
Android 6 > TWRP 3.0.2-0
Android 7 > TWRP 3.1.1-1
Ensure you have drivers installed in your pc.
Ensure you have OEM unlock and DEBUG USB enabled in developer option.
With fastboot: >>> fastboot flash recovery (name of recovery).img (ensure you put the recovery inside the fastboot folder)
>>> fastboot reboot recovery or shoutdown and reboot holding vol+ and power buttons (until it boots in TWRP).
Done.
Cheers
Thanks. I managed to get it working more przez less. Now i have two recoveries . One accessible while holding vol+ during power up and stock recovery when i press vol+ for 3s on "your device is unlocked and therefore it should not be trusted" screen.
So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?
Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
emiljano539 said:
Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
Click to expand...
Click to collapse
I can't boot into recovery, the error message pops up on the screen
lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
You have to boot to twrp from the bootloder screen.
Use this recovery to boot from pc and never Flash twrp on pie.
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
lvnatic said:
So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?
Click to expand...
Click to collapse
Again unlock boot loader.
lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"
emiljano539 said:
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"
Click to expand...
Click to collapse
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.
lvnatic said:
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.
Click to expand...
Click to collapse
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?
emiljano539 said:
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?
Click to expand...
Click to collapse
Yes, I also have a redmi note 5 Pro and a mipad 4 and both work well with ADB.
Try flashint stock on EDL mode.
Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!
Thanks for the Solution
Inferi0r said:
Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!
Click to expand...
Click to collapse
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.
yagya said:
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.
Click to expand...
Click to collapse
Thanks for this. This happened to me two weeks ago, had to completely flash stock rom and begin from zero. Hopefully others will see this and avoid starting fresh.