Hi,
my Note 5 (which is standard with latest software updates) hangs on the Mi screen when starts up. I can get it into FASTBOOT mode.
And when I connect to PC/Windows 10 and go through adb and enter this:
fastboot devices
gives this result:
fcef713c0904
But I'm not sure what to do now? I guess I need to flash some sort of recovery but not being super tech savvy I'm a bit nervous.
thanks Phillip
@phil170258
Edit: fastboot is recognicing your device, as far I understood what you mean you tried to unroot it and gave you bootloop, flash the boot image that you are using lastly through fastboot and see what happens
SubwayChamp said:
@phil170258
Edit: fastboot is recognicing your device, as far I understood what you mean you tried to unroot it and gave you bootloop, flash the boot image that you are using lastly through fastboot and see what happens
Click to expand...
Click to collapse
Hi,
thanks for your reply.
I wasn't trying to do anything with my phone (root or unroot) when it started this behaviour so I don't have a boot image to flash? And my phone doesn't have 'usb debugging enabled' but because it won't turn on I can't enable it.
So i need to do 'fastboot flash recovery twrp.img' but when I do this it says cannot load twrp.img no such file or directory.
Aaaaaah!
thanks, Phil
phil170258 said:
Hi,
thanks for your reply.
I wasn't trying to do anything with my phone (root or unroot) when it started this behaviour so I don't have a boot image to flash? And my phone doesn't have 'usb debugging enabled' but because it won't turn on I can't enable it.
So i need to do 'fastboot flash recovery twrp.img' but when I do this it says cannot load twrp.img no such file or directory.
Aaaaaah!
thanks, Phil
Click to expand...
Click to collapse
Then try first going to recovery stock manually and wipe data and try to boot.
There are many users reporting this kind of issues along the time (updating firmware, charging all the night, etc) so the best is enabling USB debugging if something goes wrong you´ll have more options to save your device.
I guess you have your bootloader locked and also for this reason you can no longer use fastboot mode to flash some file.
If the first doesn´t result then your last resource would be to flash a rom through test point method (if you have Redmi 5 Plus-Vince)
SubwayChamp said:
Then try first going to recovery stock manually and wipe data and try to boot.
There are many users reporting this kind of issues along the time (updating firmware, charging all the night, etc) so the best is enabling USB debugging if something goes wrong you´ll have more options to save your device.
I guess you have your bootloader locked and also for this reason you can no longer use fastboot mode to flash some file.
If the first doesn´t result then your last resource would be to flash a rom through test point method (if you have Redmi 5 Plus-Vince)
Click to expand...
Click to collapse
Wipe data worked!
Thanks, and yes, i will enable USB debugging
thanks, Phil
Related
My phone is stuck on bootloop. I have cyanogenmod 13 installed on my moto g 3rd gen(2015). I can't seem to get into my system recovery either, which is now twrp and it just shows the logo for twrp recovery. I also for some dumb reason disabled my usb debugging mode, so i can't flash my phone either. Help plzz
Maybe go to bootloader and reflash TWRP
minimale_ldz said:
Maybe go to bootloader and reflash TWRP
Click to expand...
Click to collapse
Doesn't work, can't connect to bootloader
znyght said:
Doesn't work, can't connect to bootloader
Click to expand...
Click to collapse
So, if you turn the phone off and then hold "power" and "volume down" untill it boots, nothing happens?
minimale_ldz said:
So, if you turn the phone off and then hold "power" and "volume down" untill it boots, nothing happens?
Click to expand...
Click to collapse
of course, it goes into bootloader but my PC can't recognize anything. So I can't flash anything. USB Debugging is disabled. If there was a way to force connect that would be great
znyght said:
of course, it goes into bootloader but my PC can't recognize anything. So I can't flash anything. USB Debugging is disabled. If there was a way to force connect that would be great
Click to expand...
Click to collapse
You don't need USB debugging to use fastboot when your phone is booted into bootloader. What you need there is a fastboot tool and drivers. I'm using this one:
http://forum.xda-developers.com/showthread.php?p=48915118
and if it doesn't install correct drivers for you, you can get them here:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
first thing to do is check what fastboot returns after this command:
Code:
fastboot devices
if it shows your device ID you're good to go
I'd suggest downloading stock firmware first and flashing it before messing with custom recovery. Just remember Motorola often updates bootloader with new firmware so don't flash anything older than you had on your phone before.
Good luck
EDIT: you can also use RSD Lite to flash a new software, it basically automates fastbooting proccess, so theres no risk of misspelling or doing other stuff wrong
EDIT2: firmware is here:
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
also, the OP (lost101) is a great, helpful guy who may give you some advice if you need
Thanks I'll give them a try
Originally Posted by minimale_ldz
You don't need USB debugging to use fastboot when your phone is booted into bootloader. What you need there is a fastboot tool and drivers. I'm using this one:
Click to expand...
Click to collapse
I've tried these but they didn't seem to work
I know there is few hundered threads with "unbrick" in title but I read them all and nothing seems to work.
Friend brings me kenzo that he gets since his cousin brick it while trying OTA.
When I power phone its start to load system and it has 3 stages:
1. Show screen with "powered by Android" and 3 dots in the bottom, usualy about 4 min and restart
2. After restart just get black screen with Mi logo in the middle, for about 30 sec and restart
3. Instead of Android with dots bottom have white line progres bar, it takes 4 to 5 min and restart again.
After that stage 2 and 3 repeat for long as you have nervs to wait .
Phone can get in recovery and fastboot mode. And when I put him in test mode just show test screen and cant do anything.
In fastboot mode MiFlash recognize phone but report "device is locked" (try with 20160401 and 20160830).
After that i put him in EDL mode (fastboot reboot-edl) and MiFlash report successful flash. But nothing changes.
I try flashing global stable v8.0.5.0, china stable v8.0.4.0, global dev v6.10.13 and at the end global stable v7.2.5.0.
Any idea welcome. Thx
Have you tried to unlock bootloader? Perhaps install TWRP and do a system/dalvik/cache wipe and install MIUI through that?
banana_bender said:
Have you tried to unlock bootloader? Perhaps install TWRP and do a system/dalvik/cache wipe and install MIUI through that?
Click to expand...
Click to collapse
Cant do that. Even unofficial unlock need phone to be working to enable USB debbuging and accept RSA kay from PC.
Edit: Right now looking for ways to edit boot.img to unlock bootloader in attempt to get any useful recovery.
you can try this guide to flash twrp altogether with rom. after flashing, directly boot to twrp and move to custom rom
abihary said:
you can try this guide to flash twrp altogether with rom. after flashing, directly boot to twrp and move to custom rom
Click to expand...
Click to collapse
I will try... but dont think it will do the job. Will post result little later.
EDIT
It dose not work, just as I think.
All that kind of method/advice need 2 things:
1. Enabled USB debbuging - You cant do that on bricked phone even if you edit boot.img ( ro.debuggable=1 ) because fastboot will not execute command since you will not have option to accept RSA kay from PC on your phone and complete that action.
2. Dev ROM - since you have to enable OEM unlock and that option you have only in dev ROMs. Even Xiaomi official unlock requires that you must do it on dev ROM and that is a reason for "stuck on 50% in unlocking".
I try all that I can think: edit boot.img file, use patch emmc_appsboot.mbn, use edited flash_all.bat and rawprogram0.xml, insert sTWRP and ZCX TWRP in fastboot ROM... and all combination of that. Did it on 7.2.5.0 and 8.0.5.0 stable and 6.8.18 dev (since its last 5.1 ROM that I have).
Most of this attempts ends with "3 stages" explained in the first post. Some just show Mi logo for few sec and restart, once even power off phone. And once I even get phone to go directly to sideload/recovery state showing picture of the phone and usb cable.
Only thing left now is to find info is there difference in accessing to EDL mode between software (reboot-edl), deep flash cable and testpoint. IMHO there is none or little difference. Since software and deep flash can be troubled with bad USB cable or connector or USB board in phone.
Hello guys, I am new here to XDA Developers, so here's my take on my phone's problem..
Long story short, I wanted to root my phone so I could enable the OTG option for my phone cuz I tend to get my storage filled up and use a USB to transfer files. So, I did root my phone, got its bootloader unlocked and successfully done the operation. I used the kiwi_twrp_3-21_recovery.img via ADB and Fastboot tool for this.
But when I used ADB and Fastboot to flash the boot-kiwi-marshmallow-otg,img file and restart it afterwards, the phone will go straight to eRecovery mode. Here I cannot download the recovery it wants because it always show download info fail of some sort and that I cannot debug the phone either. I do can get it to Fastboot mode but my computer won't detect it.. So my phone is basically a stone now. What should I do now? It is my first time so I don't wanna get busted, any help will be appreciated! Thanks!
For reference: I was using this this thread for OTG enabling feature:
https://forum.xda-developers.com/honor-5x/how-to/tutorial-enable-otg-honor-5x-t3322274
And for rooting process, I just watched this video:
https://www.youtube.com/watch?v=Y-2SWbInT6U
Kingofiron257 said:
Hello guys, I am new here to XDA Developers, so here's my take on my phone's problem..
Long story short, I wanted to root my phone so I could enable the OTG option for my phone cuz I tend to get my storage filled up and use a USB to transfer files. So, I did root my phone, got its bootloader unlocked and successfully done the operation. I used the kiwi_twrp_3-21_recovery.img via ADB and Fastboot tool for this.
But when I used ADB and Fastboot to flash the boot-kiwi-marshmallow-otg,img file and restart it afterwards, the phone will go straight to eRecovery mode. Here I cannot download the recovery it wants because it always show download info fail of some sort and that I cannot debug the phone either. I do can get it to Fastboot mode but my computer won't detect it.. So my phone is basically a stone now. What should I do now? It is my first time so I don't wanna get busted, any help will be appreciated! Thanks!
For reference: I was using this this thread for OTG enabling feature:
https://forum.xda-developers.com/honor-5x/how-to/tutorial-enable-otg-honor-5x-t3322274
And for rooting process, I just watched this video:
https://www.youtube.com/watch?v=Y-2SWbInT6U
Click to expand...
Click to collapse
Solutions:
1. Boot into recovery (Power + VolUp) and restore last backup (I really do hope you have a backup). It should be enough to restore just boot image. Mine ended in eRecovery few days ago after messing with Magisk and I've successfully recovered my device from there
2. Download original firmware, extract it, boot into fastboot (obv., try fixing it first, but you've flashed TWRP so it must work for other stuff, too) and just reflash original boot image
3. Download original firmware, extract it, boot into fastboot and reflash original recovery, then try eRecovery (this will probably wipe all your data, though)
There are tons of manuals how to extract Huawei/Honor firmware images (even a nice little program to do it for you), so I'd suggest searching around for that SW instead of asking how.
Kingofiron257 said:
Hello guys, I am new here to XDA Developers, so here's my take on my phone's problem..
Long story short, I wanted to root my phone so I could enable the OTG option for my phone cuz I tend to get my storage filled up and use a USB to transfer files. So, I did root my phone, got its bootloader unlocked and successfully done the operation. I used the kiwi_twrp_3-21_recovery.img via ADB and Fastboot tool for this.
But when I used ADB and Fastboot to flash the boot-kiwi-marshmallow-otg,img file and restart it afterwards, the phone will go straight to eRecovery mode. Here I cannot download the recovery it wants because it always show download info fail of some sort and that I cannot debug the phone either. I do can get it to Fastboot mode but my computer won't detect it.. So my phone is basically a stone now. What should I do now? It is my first time so I don't wanna get busted, any help will be appreciated! Thanks!
For reference: I was using this this thread for OTG enabling feature:
https://forum.xda-developers.com/honor-5x/how-to/tutorial-enable-otg-honor-5x-t3322274
And for rooting process, I just watched this video:
https://www.youtube.com/watch?v=Y-2SWbInT6U
Click to expand...
Click to collapse
what recovery do you have now?? can you access twrp? or you are left with emui recovery??
if you have emui recovery, just perform a dload flash
Looks like he solved it.
adriansticoid said:
Looks like he solved it.
Click to expand...
Click to collapse
We need his solution , the one he tried
gopinaidu77 said:
We need his solution , the one he tried
Click to expand...
Click to collapse
Let's wait for his post.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Let's wait for his post.
Click to expand...
Click to collapse
Its been long he replied. Omg ,what is going ?
Stop. Spamming. The. Thread. For. Points.
Hi guys, my redmi 5 plus is stuck on logo loading screen and i can only go for fastboot. Cannot neither turn off phone.
I tried with Mi Flash tool but program fail with "Can not find flash_all.bat". I tried different version of roms and Mitool, but still have this error. How can i repair my device? Thnak you all for the future responsed
Ps: sorry for my really bad english
I dont´know what you tried to do before to get this status or if you have an unlocked bootloader to perform some operation in fastboot mode. If you are in stock rom you can try enter to recovery and use MiAssistant feature is a kind of adb sideload in-built that you can use to reinstall again the rom onto your device. Here you will find some guide lines about this behind the concept http://www.xiaomitool.com/adb
SubwayChamp said:
I dont´know what you tried to do before to get this status or if you have an unlocked bootloader to perform some operation in fastboot mode. If you are in stock rom you can try enter to recovery and use MiAssistant feature is a kind of adb sideload in-built that you can use to reinstall again the rom onto your device. Here you will find some guide lines about this behind the concept http://www.xiaomitool.com/adb
Click to expand...
Click to collapse
You right sorry. I have Bootloader unlocked. My brick come becose of me trying to root the phone with "1clickrooter" for redmi5 plus. When phone rebooted on recovery he ask me for a password. No pin works on this pass requesto so i try to wipe cash, phone automatically reboot and stuck in logo screen. Cannot turn of or go to recovery, only action i can make is to go on fastboot mode.
So, i have news, i can go on recovery mode (recovery i have is called "Team Win Recovery Project 3.2.1.0"), but in order to make write action (now i can only read) request me a password, obviously neither 1 of my pass (sim pin/screen unlock) work.
Jackevolution said:
So, i have news, i can go on recovery mode (recovery i have is called "Team Win Recovery Project 3.2.1.0"), but in order to make write action (now i can only read) request me a password, obviously neither 1 of my pass (sim pin/screen unlock) work.
Click to expand...
Click to collapse
If you can reboot now to recovery twrp then just cancel when it prompts for a password and you have to format data in order to can reboot to system again
Jackevolution said:
You right sorry. I have Bootloader unlocked. My brick come becose of me trying to root the phone with "1clickrooter" for redmi5 plus. When phone rebooted on recovery he ask me for a password. No pin works on this pass requesto so i try to wipe cash, phone automatically reboot and stuck in logo screen. Cannot turn of or go to recovery, only action i can make is to go on fastboot mode.
Click to expand...
Click to collapse
SubwayChamp said:
If you can reboot now to recovery twrp then just cancel when it prompts for a password and you have to format data in order to can reboot to system again
Click to expand...
Click to collapse
Already done, now semms to be stuck on the same loading screen, baibe he installing apps? It taking sooo long...
i think this isn't working. It's just 20 minute that phone is stuck on "Mi" screen...
Nope, definetly not worked. There is a way to put filesin the phone from recovery?
Jackevolution said:
Nope, definetly not worked. There is a way to put filesin the phone from recovery?
Click to expand...
Click to collapse
Yes, you can reflash again the rom, put the rom zip in your adb folder and short the name as you can, and flash it using adb sideload, to do this tap on "advanced option" and then "adb sideload" in recovery menu and in adb terminal in your pc type adb sideload nameofrom.zip where nameofrom is te name of the rom, don´t forget the extension .zip as I wrote. TWRP will load the zip and flash it again and then you can flash Magisk to root device.
If you can´t see storage of device in your pc is cause it´s encrypted but you can perform adb sideload anyway
Jackevolution said:
Hi guys, my redmi 5 plus is stuck on logo loading screen and i can only go for fastboot. Cannot neither turn off phone.
I tried with Mi Flash tool but program fail with "Can not find flash_all.bat". I tried different version of roms and Mitool, but still have this error. How can i repair my device? Thnak you all for the future responsed
Ps: sorry for my really bad english
Click to expand...
Click to collapse
Look at the error you got every time "Can not find flash_all.bat" its mean that you are selecting invalid path, okay so here is correct method to flash via fast-boot method:
Download the latest fast boot rom zip one option is http://bigota.d.miui.com/V9.5.12.0....FA_20180525.0000.00_7.1_global_343bc5aaef.tgz
Unzip .tgz using winrar and the zip will be extracted in folder named as vince_global_images_V9.5.12.0.NEGMIFA_20180525.0000.00_7 inside this folder there will be another folder named same.
Open Mi Flash tool and click to select direct to folder vince_global_images_V9.5.12.0.NEGMIFA_20180525.0000.00_7 open the folder and then open the other folder click Ok (don't open the the images folder)
Connect your redmi 5 plus in fast boot mode and click refresh, then choose clean all and click Flash
I tried to root my phone using this guide, followed it down to the word and yet my phone's stuck in a bootloop. It keeps restarting to the Poco start screen.
Ive got the stock recovery, and for some odd reason fastboot commands work only in the "FASTBOOTD" screen and not the the "FASTBOOT" screen which you get from "adb reboot bootloader" command.
I try to shut it down and it boots up back again in the same screen and is stuck there.
Im clueless and I really dont know what to do. Some help would be greatly appreciated.
edit: I tried to use the stock recovery and wipe data. No progress.
I tried to connect the phone with the MIAssistant but the app doesnt recognise the device.
I tried using the MiFlash tool to flash the stock rom, it goes on infinitely. Im currently trying to use the SP Flash tool and MediaTek Bypass tool but I havnt got any progress yet.
I promise I'm never buying MediaTek devices ever again.
Careful with the Flash and Bypass tools, they can cause problems.
What can you achieve with the hardware buttons on the phone? Can you get it into recovery?
Fastbootd working but fastboot not sounds like a USB drivers problem - there are some driver options here.
aricooperdavis said:
Careful with the Flash and Bypass tools, they can cause problems.
What can you achieve with the hardware buttons on the phone? Can you get it into recovery?
Fastbootd working but fastboot not sounds like a USB drivers problem - there are some driver options here.
Click to expand...
Click to collapse
It was a driver issue, thanks for the link.
What I did to get out of the bootloop:
1. Download the latest Miui rom for your version, make sure it's the recovery version and not the fastboot one.
2. Press ALL the buttons, Vol+ Vol- and Power button to shut it down for a few seconds (assuming you can't switch it off as it keeps powering back up again).
3. After it's switched off, quickly press the power and vol- button until you see the FASTBOOT screen.
4. Connect with PC, make sure you have the proper drivers and have connected with the right USB port.
5. Download OrangeFox custom recovery. It is a unofficial custom recovery, so its stability is questionable. But it does the job here.
6. Copy the OrangeFox zip and the Miui rom file to your phone's SD card or any external storage which your phone can access.
7. In your PC, extract the OrangeFox zip folder in your platform-tools folder. (The folder where you run your cmd fastboot/adb commands)
8. Open up cmd, and enter the command:
fastboot flash boot recovery.img
9. Your phone should boot up to the OrangeFox recovery. If not switch the phone off (Step 2) and press power + vol+ button for booting up to the recovery.
10. Locate your OrangeFox zip installer file in the recovery and flash it.
11. Reboot to the recovery again.
12. Locate the Miui rom and flash that. Before swiping to flash the rom, there is a check box which says something like "flash OrangeFox once the rom has been flashed". If you want to keep OrangeFox as your recovery then check it, or else leave it unchecked. Flashing roms remove custom recoveries.
13. Your phone must reboot to miui.
NOTE: You can use fastboot commands to flash the rom but I'm not very familiar with fastboot commands (I actually forgot most of them). Hence I use the recovery method.
warhead1721972 said:
It was a driver issue, thanks for the link. Should I delete this post? It isnt much big of an issue imo.
Click to expand...
Click to collapse
Great, glad you got it sorted! No, leave it up, you never know someone might stumble across it and find it useful