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
Related
Hello everyone ill cut right to the point i rooted my Zte source using Kingo root app about a month ago and everything was fine and 3 days ago i installed a boot animation through rom toolbox and my phone now will not boot up i get black screen with flashing red light when i try to go into recovery mode by pressing and holding power and vol + it vibrates but stays at black screen and shows up on my pc as ZTE Handset Diagnostic Interface(DFU) (COM5) what do i do? Can i reset my phone?
King-Reaper said:
Hello everyone ill cut right to the point i rooted my Zte source using Kingo root app about a month ago and everything was fine and 3 days ago i installed a boot animation through rom toolbox and my phone now will not boot up i get black screen with flashing red light when i try to go into recovery mode by pressing and holding power and vol + it vibrates but stays at black screen and shows up on my pc as ZTE Handset Diagnostic Interface(DFU) (COM5) what do i do? Can i reset my phone?
Click to expand...
Click to collapse
i say there is still hope. seems the only thing you messed up is the boot animation. according to this thread http://forum.xda-developers.com/showthread.php?t=2520309
you have fastboot for your device, so in theory, you could use a fastboot flash recovery command to install CWM, and use it to install a ROM
The French Tickl3r said:
i say there is still hope. seems the only thing you messed up is the boot animation. according to this thread http://forum.xda-developers.com/showthread.php?t=2520309
you have fastboot for your device, so in theory, you could use a fastboot flash recovery command to install CWM, and use it to install a ROM
Click to expand...
Click to collapse
how do i get fastboot to recognize my device? i have correct drivers for phone since my brother has same phone i got drivers off his phone but fastboot does not see my device adb does not see my device as well
King-Reaper said:
how do i get fastboot to recognize my device? i have correct drivers for phone since my brother has same phone i got drivers off his phone but fastboot does not see my device adb does not see my device as well
Click to expand...
Click to collapse
did you enable usb debugging?
The French Tickl3r said:
did you enable usb debugging?
Click to expand...
Click to collapse
the last time my phone would boot up yea usb debugging was enabled by now it wont boot so i cant check to make sure
i dont use the same device as urs but as far as my knowledge goes
ur phone has usb degubbing on ...jus gt in fastboot and figure out a way to install a custom recovery
then u can just wipe data and ull b good to go...no need of a new rom
search xda forum for ur cell to flash recovery via fastboot
:good:
MOHIT.S said:
i dont use the same device as urs but as far as my knowledge goes
ur phone has usb degubbing on ...jus gt in fastboot and figure out a way to install a custom recovery
then u can just wipe data and ull b good to go...no need of a new rom
search xda forum for ur cell to flash recovery via fastboot
:good:
Click to expand...
Click to collapse
but fastboot dose not see my device and i dont know how to make fastboot see my device
King-Reaper said:
but fastboot dose not see my device and i dont know how to make fastboot see my device
Click to expand...
Click to collapse
dude...1st of all fastboot is a boot mode...to get into it u have to use combination keys while booting, some times use usb cord
just google how to fastboot with the name of ur device ull gt it!
Hey guys sorry I've been busy my phone is fixed I just took it to cricket and told them a software update broke my phone so this thread can be closed thanks for everyone's help
Sent from my ZTE_N9511 using XDA Free mobile app
So, i installed Xposed, and like many people, i got stuck in the logo... No big deal there... Went to look for some help, and it said to go to fastboot, so I went, but it got stuck in the fastboot logo. Then I connected it to the computer and when I try to list the ADB devices I Ialways get an error saying the server is outdated...
I really need some help! I can't find anything online to help me!
Thanks in advance!
Edit: I submitted a bootloader unlock request to Xiaomi earlier today, but I can't see if its approved or not because phone doesn't work
well,
if you are in fastboot mode then the command is "Fastboot Devices", Not "adb Devices"
_____________________________________________
and about boot loop problem try to flash miui fastboot rom.
_____________________________________________
And about bootloader request problem you can go to edl mode and flash miui without any permissions
Thanks:good::good:
nishant2222 said:
well,
if you are in fastboot mode then the command is "Fastboot Devices", Not "adb Devices"
_____________________________________________
and about boot loop problem try to flash miui fastboot rom.
_____________________________________________
And about bootloader request problem you can go to edl mode and flash miui without any permissions
Thanks:good::good:
Click to expand...
Click to collapse
I tried, but i cant seem to go to edl mode through fastboot, any tips? and because of bootloader lock i cant flash fastboot rom with MI Flash
Edl mode needs a specific fastboot version.
For the Redmi Note 3 Pro / Special Edition
Download and extract this package on your PC.
Enter fastboot mode by holding Power and Vol- at the same time. Wait until the Mi Bunny appears, then connect the phone to the PC.
Run reboot.bat in the extracted package. A command prompt will appear. Press a key to reboot the phone to EDL mode.
Upon entering EDL mode, the screen should turn blank. The notification LED might be blinking red. Done.
To get out of EDL mode, hold the Power button for about 10 seconds.
Click to expand...
Click to collapse
Above quote taken from xiaomi reddit wiki.
If the above doesn't work, see the link for deep flash cable, shouldn't be need for kenzo/kate.
How you flashed/installed xposed on locked bootloader is another question?
You may need to update your adb/fastboot version + device drivers(adb)
corkiejp said:
Above quote taken from xiaomi reddit wiki.
If the above doesn't work, see the link for deep flash cable, shouldn't be need for kenzo/kate.
How you flashed/installed xposed on locked bootloader is another question?
You may need to update your adb/fastboot version + device drivers(adb)
Click to expand...
Click to collapse
Ok, so when i try to reboot in edl, it just reboots as normal after screen goes blank...
I installed Xposed with an APK
Sorry if i'm being annoying, but I just want this fixed
KaiZix said:
Ok, so when i try to reboot in edl, it just reboots as normal after screen goes blank...
I installed Xposed with an APK
Sorry if i'm being annoying, but I just want this fixed
Click to expand...
Click to collapse
Mate, watch any video on YouTube. You're not understanding from text instructions.
AtomR said:
Mate, watch any video on YouTube. You're not understanding from text instructions.
Click to expand...
Click to collapse
Can't find any... Recommendations?
EDL Mode: - https://www.youtube.com/watch?v=LDGViyDYPbU
If you can't get into EDL mode, you may need to use the deep flash cable method.
corkiejp said:
EDL Mode: - https://www.youtube.com/watch?v=LDGViyDYPbU
If you can't get into EDL mode, you may need to use the deep flash cable method.
Click to expand...
Click to collapse
I can't get into EDL mode, and I can't make/buy a deep flash cable... I'm getting really scared now...
About ADB, how can I fix it?
KaiZix said:
I can't get into EDL mode, and I can't make/buy a deep flash cable... I'm getting really scared now...
About ADB, how can I fix it?
Click to expand...
Click to collapse
Installing Mi Flash should have put the correct drivers on your PC.
But can be got from here: - https://xiaomifirmware.com/downloads/download-pc-drivers-xiaomi-redmi-note-3/
And I already linked adb/fastboot tools.
IF your comfortable opening your device, there is also a test point method you could try.
http://en.miui.com/thread-244814-1-1.html
Could not find a English video, so maybe try googling more and you might find one.
If not, you could ask at local repair shop, if they would fix it for you. Using Cable/ TP method.
Note for other readers:- MIUI roms need a special version of xposed, for it to work. And installing from an app would more than likely would have use the wrong version. Should never be done on a locked bootloader, only asking for trouble. (Rovo89 is currently trying to bring MIUI support to the official version for nougat roms)
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
What's needed:
latest Android Pie firmware for Xperia XZ1 (I used 47.2.A.4.41_R4C UK or any version of the 47.2.A.6.30) from XperiFirm
newflasher_v13 tool here
Minimal ADB and Fastboot
TWRP Recovery here
last Magisk.zip here
first copy Magisk.zip to the sd card and insert it into the device
Install TWRP:
launch flashtool and download the latest firmware 47.2.A.4.41_R4C with XperiFirm ....
follow the path C: users / name / .flashTool / firmwares / Download
locate the unzipped firmware, open the folder and delete all the .ta files; then open the boot and partition folders and do the same thing
search the internet or XDA newflasher_v13 tool and place all 7 files in the C: users / name / .flashTool / firmwares / Download / 47.2.A.4.41_R4C folder
connect the device in flash mode
launch the .exe command
press "n" and again "n"
finished the firmware flash unplug the phone
When the first ignition is finished, open the debug and connect the mobile phone to the PC
open the folder Minimal in the path C: Program / Minimal and paste in the folder the recovery.img, run cmd.exe type the following commands
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery namerecovery.img
fastboot reboot
finished the start of the phone, turn it off and go into recovery mode (volume down + power button)
flash Magisk from the sd
turn on the cell phone and the root is done
Special thanks
oF2pks for the TWRP
munjeni for the newflasher
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
I have pie stock...can i start guide from point 10 ?
lilbrat said:
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
Click to expand...
Click to collapse
look at this thread for backup/restore your DRM keys
lilbrat said:
So, what do we lose in this process? Granted it's been reported that the camera is working without the need for a DRM fix, but do we lose other things like video and sound enchantment options?
Click to expand...
Click to collapse
In my experience I can tell you that nothing is lost on the camera neither in the sound effects nor the color effects on the photos ...
ilblago81 said:
I have pie stock...can i start guide from point 10 ?
Click to expand...
Click to collapse
Absolutely yes
From the use I note that the recovery doesn't read the internal data, but only the sd card. I still don't understand if it's the firmware that has bugs or the twrp that still isn't calibrated for Adroid Pie.
Edit: I found in the XDA site the recovery for the new firmwre and everything works fine here
Would this work on SOV36 (AU XZ1)?
sinkoo1979 said:
Would this work on SOV36 (AU XZ1)?
Click to expand...
Click to collapse
Honestly I don't know, but if in your device install the firmware that we install in the g8341 means that you can. I'm thinking it's the same thing!
Sorry, but the requirement is always with unlocked bootloader?Thanks
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
dwang040 said:
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
Click to expand...
Click to collapse
Are your drivers properly installed reason I am asking is you're not getting a return when you type in fastboot devices, go back to you developer setting, revoke your debugging , then reinstall your drivers turn on USB debugging and see what happens?
lilbrat said:
Are your drivers properly installed reason I am asking is you're not getting a return when you type in fastboot devices, go back to you developer setting, revoke your debugging , then reinstall your drivers turn on USB debugging and see what happens?
Click to expand...
Click to collapse
Hmm, I think I know why it wasn't working? I got the xperia xz1 drivers off of the sony developer website, and I went to device manager and tried to do the legacy driver install, but I keep getting "This device cannot start (code 10)" Maybe that's the issue? And if so, am I installing it wrong or something?
dwang040 said:
Hmm, I think I know why it wasn't working? I got the xperia xz1 drivers off of the sony developer website, and I went to device manager and tried to do the legacy driver install, but I keep getting "This device cannot start (code 10)" Maybe that's the issue? And if so, am I installing it wrong or something?
Click to expand...
Click to collapse
What OS is on your computer?
lilbrat said:
What OS is on your computer?
Click to expand...
Click to collapse
Windows 10
dwang040 said:
Windows 10
Click to expand...
Click to collapse
Did you disable the driver verification signature?
(https://www.howtogeek.com/167723/ho....1-so-that-you-can-install-unsigned-drivers/) then reinstall min adb fastboot drivers and Sony companion and let it detect your phone..
chiacla said:
Sorry, but the requirement is always with unlocked bootloader?Thanks
Click to expand...
Click to collapse
you have to unlock the bootloader
dwang040 said:
Wait... I'm confused. I need an unlocked bootloader for this correct? Also, am I missing a step? I can't seem to unlock the bootloader. I have the key from Sony, but whenever I turn off the phone and try to enter bootloader mode (volume up + usb charger), the notification light turns blue, and that's it. Nothing appears on my screen, if I type fastboot devices, no devices appear as listed. And if I try to run the line of code, I'm just stuck "waiting for device" and nothing happens? Am I being stupid and missing something? Don't remember having this many issues with my htc m9.
Click to expand...
Click to collapse
did you install flashtool? did you install the drivers from the flashtool "drivers" folder? Did you unlocked the bootloader? ther'is no need to work on win10 signature
theflanker said:
did you install flashtool? did you install the drivers from the flashtool "drivers" folder? Did you unlocked the bootloader? ther'is no need to work on win10 signature
Click to expand...
Click to collapse
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
theflanker said:
you have to unlock the bootloader
Click to expand...
Click to collapse
He won't be able to unlock his bl till he figures out the issues with his drivers.. whether he uses the ones in flashtool, installs min adb and fastboot drivers or the android sdk..
---------- Post added at 05:34 PM ---------- Previous post was at 05:29 PM ----------
dwang040 said:
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
Click to expand...
Click to collapse
Once you get your driver's fixed, just follow the directions given by Sony.. Your phone screen will remain black as all info will be done on your computer..
dwang040 said:
I was under the impression that flash tool is used to get the latest version of the pi (which I already have as the update rolled out a few days ago)? Not for unlocking the bootloader? As for my bootloader, I'm stuck on that step. I'm following sony's steps on unlocking the bootloader, however, I'm stuck on the fastboot as my device isn't recognized. I guess I'll try again from the top, uninstall all the current drivers and reinstall them again.
I also want to add, whenever I plug my phone in into bootloader mode, the pc does recognize that a device is connected as the notification pops up, but again, "fastboot devices" returns nothing. Is there supposed to be a screen for the bootloader? Or is it just a black screen with the blue led?
Click to expand...
Click to collapse
Absolutely no, flashtool doesn't need to unlock the bootloader, rather serves to re-lock it in some xperia devices. To unlock it you have to use cmd commands in adb & fastboot, but you can find it here in the XZ1 section.
The cell screen remains black and a blue led appears if you connect in fastboot mode, if you connect in flash mode the screen remains black, but a green LED appears.
if you have problems with the recognition of the device on your PC I can link my guide, it's in italian but if you use google translator you understand it well here
arslancn said:
look at this thread for backup/restore your DRM keys
Click to expand...
Click to collapse
I've checked out the thread but it appears only a few with the xz1 have tried it and they didn't report the outcome, well except one who somehow managed to turn his device in an expensive paperweight.. But I will check it out this weekend..
Whenever I try to install anything or flash anything like a recovery on fastboot mode, even if I try to initialize it or plug it into the mi firmware flash program it turns black. When I type in fastboot devices it recognizes it. I have installed all the drivers, I tried using USB 2.0 ports I tried using USB 3.0 ports I tried using different cables and still nothing is working, I should mention that my bootloader is unlocked I was successful in unlocking it and installing TWRP , this only started happening when I removed TWRP by flashing an update then not patching the update so it got replaced by stock recovery then when I tried to reflash TWRP this started to happen. so now I'm stuck with a stock recovery and no way of flashing TWRP to make any kind of modifications. COULD it be I screwed up my bootloader when I flashed the zip? It's possible that the zip may have been of a older version....so I might have installed a older bootloader...I dunno.
But fastboot can detect your device?
ussualy stuck on recovery because arb, is your device poco f1 or mi8?
Darklouis said:
But fastboot can detect your device?
Click to expand...
Click to collapse
Yes! It makes no sense to me
samexex said:
ussualy stuck on recovery because arb, is your device poco f1 or mi8?
Click to expand...
Click to collapse
Poco, it's not stuck in recovery, it's just whenever I try to do anything in fastboot it's just goes black and says on the top corner press anything to reboot, so I can't flash TWRP I can't use miflash I can't do anything that requires fastboot
Aybouzaglou said:
Poco, it's not stuck in recovery, it's just whenever I try to do anything in fastboot it's just goes black and says on the top corner press anything to reboot, so I can't flash TWRP I can't use miflash I can't do anything that requires fastboot
Click to expand...
Click to collapse
Did you ever find a solution to your problem?
TrippyEngine said:
Did you ever find a solution to your problem?
Click to expand...
Click to collapse
Yes I installed the latest open beta with the stock recovery and it fixed the problem
Aybouzaglou said:
Poco, it's not stuck in recovery, it's just whenever I try to do anything in fastboot it's just goes black and says on the top corner press anything to reboot, so I can't flash TWRP I can't use miflash I can't do anything that requires fastboot
Click to expand...
Click to collapse
are u using ryzen cpu on your pc or laptop?
Aybouzaglou said:
Poco, it's not stuck in recovery, it's just whenever I try to do anything in fastboot it's just goes black and says on the top corner press anything to reboot, so I can't flash TWRP I can't use miflash I can't do anything that requires fastboot
Click to expand...
Click to collapse
This problem may happen when USB 3.0 port is used to connect the phone to PC.