Hi,
I'm stuck on eRecovery because I forgot to re-flash the stock recovery (B360) before doing a Factory Reset. So now I'm stuck on eRecovery and I have no recovery or TWRP installed. When I flash the stock recovery or TWRP via fastboot it says "Command not allowed " so I think that USB Debugging is not enabled.
My question: How can I enable USB Debugging ?
(Mayen via fastboot ? How ?
Thanks
jacquesallet said:
Hi,
I'm stuck on eRecovery because I forgot to re-flash the stock recovery (B360) before doing a Factory Reset. So now I'm stuck on eRecovery and I have no recovery or TWRP installed. When I flash the stock recovery or TWRP via fastboot it says "Command not allowed " so I think that USB Debugging is not enabled.
My question: How can I enable USB Debugging ?
(Mayen via fastboot ? How ?
Thanks
Click to expand...
Click to collapse
have you solved this problem buddy? i ahve the same problem. what should we do?
I followed this tutorial: https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165/page5
Post #45
but it didn't worked for me because the tutorial asks to change the DNS of the wifi router and FirmwareFinderRewrite crashes on my PC (Asus Windows 7) But you can try. Now I have no other solution so I'm going to use DC-Phœnix to unbrick my phone.
jacquesallet said:
Hi,
I'm stuck on eRecovery because I forgot to re-flash the stock recovery (B360) before doing a Factory Reset. So now I'm stuck on eRecovery and I have no recovery or TWRP installed. When I flash the stock recovery or TWRP via fastboot it says "Command not allowed " so I think that USB Debugging is not enabled.
My question: How can I enable USB Debugging ?
(Mayen via fastboot ? How ?
Thanks
Click to expand...
Click to collapse
jacquesallet said:
I followed this tutorial: https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165/page5
Post #45
but it didn't worked for me because the tutorial asks to change the DNS of the wifi router and FirmwareFinderRewrite crashes on my PC (Asus Windows 7) But you can try. Now I have no other solution so I'm going to use DC-Phœnix to unbrick my phone.
Click to expand...
Click to collapse
thanks for replying,
i'll try it later this tutorial. so if i got failed like you, how to use dc unlocker? im so newbie here man.
ImHonor said:
thanks for replying,
i'll try it later this tutorial. so if i got failed like you, how to use dc unlocker? im so newbie here man.
Click to expand...
Click to collapse
https://www.******.com/recover-huaw..._Full_bricked_devices_no_fastboot_no_recovery
Related
I have read the tutorials and attempted to install TWRP to no avail. My computer does recognize my oneplus x when connected but it is not recognized when I tried adb? No device attached. I put the device in fastboot manually, but the computer still won't recognize it. I think maybe my first error was trying to flash the recovery with rashr. It said it was a successful flash, but when I boot into recovery the device just stays on the oneplus logo. It is rooted by kingroot. Any new ideas would be helpful.
Thank you!
kjtay said:
I have read the tutorials and attempted to install TWRP to no avail. My computer does recognize my oneplus x when connected but it is not recognized when I tried adb? No device attached. I put the device in fastboot manually, but the computer still won't recognize it. I think maybe my first error was trying to flash the recovery with rashr. It said it was a successful flash, but when I boot into recovery the device just stays on the oneplus logo. It is rooted by kingroot. Any new ideas would be helpful.
Thank you!
Click to expand...
Click to collapse
did you unlock your bootloader? If so did you get a chinese confirmation page for unlocking bootloader or english?
joho5 said:
did you unlock your bootloader? If so did you get a chinese confirmation page for unlocking bootloader or english?
Click to expand...
Click to collapse
Unlocked bootloader and the message was in English.
kjtay said:
Unlocked bootloader and the message was in English.
Click to expand...
Click to collapse
If it's not recognizing the phone then its a driver issue. Can you boot into Android?
joho5 said:
If it's not recognizing the phone then its a driver issue. Can you boot into Android?
Click to expand...
Click to collapse
I can boot into Android (if you mean just the phone booting). I installed drivers from that were on the phone and downloaded the drivers at my work computer. Both computers recognize the phone, but not in adb or fastboot.
Use the drivers in the thread a to root and unlock bootloader, it works
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
Dear All,
Please help, today i flash my device via twrp into xiaomi.eu global rom from cm13.
Flashing done succesfully, but my device can't boot into system and just stuck at cm logo.
When i press volume - and power button the phone are boot into fastboot mode with big cm logo.
When i press volume - and connect it to computer, it shown my phone are connected into diagnostic mode.
Please help how to unbrick this device. Thanks in advance.
Ps. Device unlock officially, twrp which i use to flash miui.eu rom is twrp with f2fs support. Seems that's i use wrong twrp version.
Edit: solved
https://www.youtube.com/watch?v=NNhdQT9Ivu0
Please google before you post threads..
abihary said:
Dear All,
Please help, today i flash my device via twrp into xiaomi.eu global rom from cm13.
Flashing done succesfully, but my device can't boot into system and just stuck at cm logo.
When i press volume - and power button the phone are boot into fastboot mode with big cm logo.
When i press volume - and connect it to computer, it shown my phone are connected into diagnostic mode.
Please help how to unbrick this device. Thanks in advance.
Ps. Device unlock officially, twrp which i use to flash miui.eu rom is twrp with f2fs support. Seems that's i use wrong twrp version.
Edit: solved
Click to expand...
Click to collapse
How did u solve it?
Rudraneil said:
How did i solve it?
Click to expand...
Click to collapse
I solved it follow guidance at this Link.
After my phone enter edl mode, i just simply flash it using miflash beta for windows 32 bit due to urgent situation. I still on personal trip during when this situation happened and can't access my pc and laptop.
abihary said:
I solved it follow guidance at this Link.
After my phone enter edl mode, i just simply flash it using miflash beta for windows 32 bit due to urgent situation. I still on personal trip during when this situation happened and can't access my pc and laptop.
Click to expand...
Click to collapse
You could just have rebooted ur phone to fastboot mode and unlock the bootloader using mi unlock too to make the phone workl
It would have been way easier
Rudraneil said:
You could just have rebooted ur phone to fastboot mode and unlock the bootloader using mi unlock too to make the phone workl
It would have been way easier
Click to expand...
Click to collapse
Unfortunately, my phone already entering diagnostic mode during that's time. Did miflash unlock can solved it?
Thoght that i am missing one important step after flashing those miui eu rom. Reboot to fastboot prior the phone reboot into system and unlock the bootloader.
Anyway, thanks for your info.
abihary said:
Unfortunately, my phone already entering diagnostic mode during that's time. Did miflash unlock can solved it?
Thoght that i am missing one important step after flashing those miui eu rom. Reboot to fastboot prior the phone reboot into system and unlock the bootloader.
Anyway, thanks for your info.
Click to expand...
Click to collapse
If you were using twrp alka and had unlocked officially, mi unlock could definitely save ur device
Hi, I tried root on my phone, I was on android nougat and I installed twrp, then perform a data factory reset and restart does not go from the boot screen and shows the legend "bad key", custom recovery works but not I get nothing, please help me!
Check this out
rolas96 said:
Hi, I tried root on my phone, I was on android nougat and I installed twrp, then perform a data factory reset and restart does not go from the boot screen and shows the legend "bad key", custom recovery works but not I get nothing, please help me!
Click to expand...
Click to collapse
I had the same problem and this post helped me.
samvictorino said:
I had the same problem and this post helped me.
Click to expand...
Click to collapse
Cmd does not recognize fastboot mode, usb debugging is disabled and I can not find a way to activate it, adb sideload from twrp works but will work from there?
rolas96 said:
Cmd does not recognize fastboot mode, usb debugging is disabled and I can not find a way to activate it, adb sideload from twrp works but will work from there?
Click to expand...
Click to collapse
Sorry, actually when I did it I accidentally wiped the system partition and this post helped me, not the previous one.
I didn't need to enable unknown sources or usb debug because there was no system to begin with. I hope it helps you.
rolas96 said:
Cmd does not recognize fastboot mode, usb debugging is disabled and I can not find a way to activate it, adb sideload from twrp works but will work from there?
Click to expand...
Click to collapse
Fastboot doesn't need USB debugging to be enabled. You have some other issue.
Sent from my XT1650 using Tapatalk
In twrp just ignore encrypt pass and not modify system allowed (slider)
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