Related
After rootting my moto G around a month ago, the KitKat update has came out, I tried to update on my phone and there was an error, then I tried updating it from the PC, again another error. Then when I would turn my phone on it would turn off after around 1 minute after turning on, So I found a thread to install the update manually, then I had errors flashing partitions as said in the steps on this other website. I uplugged the phone as I kept getting errors, now when I try to turn it on it just gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. Even when I hold down the power button to turn it off, it just turns the screen black, vibrates, turns back on with the warning screen. I cannot enter fastboot with holding down power and the volume key. I am stuck here any tips or anyone know what is going on/ causing the error?
Did u got the phone completlely off? If not - try it and try to Boot in fastboot then.
Sent from my Moto G using xda app-developers app
pspuser97 said:
Did u got the phone completlely off? If not - try it and try to Boot in fastboot then.
Sent from my Moto G using xda app-developers app
Click to expand...
Click to collapse
I have managed to get it into fastboot just now by holding down the power and both volume buttons.But I still can't seem to get it working.
Luke1275 said:
After rootting my moto G around a month ago, the KitKat update has came out, I tried to update on my phone and there was an error, then I tried updating it from the PC, again another error. Then when I would turn my phone on it would turn off after around 1 minute after turning on, So I found a thread to install the update manually, then I had errors flashing partitions as said in the steps on this other website. I uplugged the phone as I kept getting errors, now when I try to turn it on it just gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. Even when I hold down the power button to turn it off, it just turns the screen black, vibrates, turns back on with the warning screen. I cannot enter fastboot with holding down power and the volume key. I am stuck here any tips or anyone know what is going on/ causing the error?
Click to expand...
Click to collapse
what model???
yiu have the usb drivers intalled??
alonsoch said:
what model???
yiu have the usb drivers intalled??
Click to expand...
Click to collapse
Its the vodafone UK moto G, yes I have the drivers installed.
fastboot oem fb_mode_clear
Try fastboot oem fb_mode_clear
i have same problem
I am also having same problem. did anyone found solution for this?
There can be many reasons for this: broken ROM, incorrect kernel etc. Unless you know specifically the last thing you changed; you are better off doing a factory reset and installing a new ROM in Recovery or flashing a firmware image via fastboot.
I am having this exact same issue. the phone is stuck on the unlocked bootloader screen. It is still responsive, I can get into the fastboot and even clockwork recovery mod but nothing i do will escapt the bootloop. I even tried a factory reset in Fastboot and Clockwork and the RSD lite method but it didnt work.
Go to the 'Restore Stock Firmware' thread and re-flash your firmware again. I've had bootloops before.
Sent from my Moto G on MoKee, using XDA app.
mej0248 said:
Go to the 'Restore Stock Firmware' thread and re-flash your firmware again. I've had bootloops before.
Sent from my Moto G on MoKee, using XDA app.
Click to expand...
Click to collapse
I did, I tried that method but when I get to step 3B I cannot get mboot or whatever to work. First it throws an error and asks for an obscure Adb.dll that i hunted down and put in its folder but then i click it to open and it flashes up for a second then closes. Excuse me while I go cry in a corner for a bit. :crying:
Deadboy90 said:
I did, I tried that method but when I get to step 3B I cannot get mboot or whatever to work. First it throws an error and asks for an obscure Adb.dll that i hunted down and put in its folder but then i click it to open and it flashes up for a second then closes. Excuse me while I go cry in a corner for a bit. :crying:
Click to expand...
Click to collapse
Bootloader screen is a boot animation http://forum.xda-developers.com/moto-g/general/guide-how-to-stuck-boot-animation-t2794208
And for restore stock firmware try inputting these commands manually
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
If all else fails check out my guide : http://forum.xda-developers.com/moto-g/general/unbrick-method-t2794271
NEED URGENT HELP
I accidentally wiped the internal storage of my Moto G XT1033 (dual sim variant), since the OS is lost now my phone is stuck at bootloader warning. I can access TWRP recovery. In device manager I can see Google Nexus ADB Interface. And in taskbar (safely remove hardware and eject media) phone is recognized as Eject XT1032. But in file explorer/My computer I can't see the phone. My phone drivers are installed.
I've tried adb shell command and I am getting this error:
C:\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
and with adb devices command following error:
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
(this line/area is blank)
C:\Minimal ADB and Fastboot>
Now how can I fix ADB or this problem? Please help
Juste300 said:
NEED URGENT HELP
I accidentally wiped the internal storage of my Moto G XT1033 (dual sim variant), since the OS is lost now my phone is stuck at bootloader warning. I can access TWRP recovery. In device manager I can see Google Nexus ADB Interface. And in taskbar (safely remove hardware and eject media) phone is recognized as Eject XT1032. But in file explorer/My computer I can't see the phone. My phone drivers are installed.
I've tried adb shell command and I am getting this error:
C:\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
and with adb devices command following error:
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
(this line/area is blank)
C:\Minimal ADB and Fastboot>
Now how can I fix ADB or this problem? Please help
Click to expand...
Click to collapse
If you have access to TWRP, then are you able to go into the Advanced menu and use the ADB Sideload feature to flash over a ROM from your PC? I had a problem while working with my phone the other day during its initial unlocking and flashing where I'd broken the system install but still had access to TWRP, and by swiping and enabling ADB Sideload, I was able to flash in a new ROM with my phone connected to my computer by running: adb sideload /path/to/rom.zip
Alternatively, you may be able to use the stock firmware restoration procedure detailed elsewhere in this forum to restore your stock firmware via fastboot.
Pardon me if I haven't fully grasped your issue. Hope this helps!
a_gert said:
If you have access to TWRP, then are you able to go into the Advanced menu and use the ADB Sideload feature to flash over a ROM from your PC? I had a problem while working with my phone the other day during its initial unlocking and flashing where I'd broken the system install but still had access to TWRP, and by swiping and enabling ADB Sideload, I was able to flash in a new ROM with my phone connected to my computer by running: adb sideload /path/to/rom.zip
Alternatively, you may be able to use the stock firmware restoration procedure detailed elsewhere in this forum to restore your stock firmware via fastboot.
Pardon me if I haven't fully grasped your issue. Hope this helps!
Click to expand...
Click to collapse
Thanks for the help. I tried ADB Sideload feature in twrp as well the adb sideload /path/to/rom.zip this command/feature was not working from the pc.
Anyways, I tried USB OTG method, copied CM nightly into my flash-drive then attached flash-drive + OTG cable with phone, at first OTG was not working don't know why it could not mount, I restarted phone, went into recovery and then I could installed rom from flashdrive. Finally my phone is working now
I am totally new to android and this rom rooting stuff. Moto G is my first android smartphone coming directly from iPhone 5 so I was scared like hell
If anyone failed with ADB Sideload method please try USB OTG method and your phone will work again. Hope this help others
same issue
Juste300 said:
Thanks for the help. I tried ADB Sideload feature in twrp as well the adb sideload /path/to/rom.zip this command/feature was not working from the pc.
Anyways, I tried USB OTG method, copied CM nightly into my flash-drive then attached flash-drive + OTG cable with phone, at first OTG was not working don't know why it could not mount, I restarted phone, went into recovery and then I could installed rom from flashdrive. Finally my phone is working now
I am totally new to android and this rom rooting stuff. Moto G is my first android smartphone coming directly from iPhone 5 so I was scared like hell
If anyone failed with ADB Sideload method please try USB OTG method and your phone will work again. Hope this help others
Click to expand...
Click to collapse
same issue but i dont know how to flash rom though pendrive i didnt find the files that i were in my pendrive in twrp menu
:crying:
shivamtyagi said:
same issue but i dont know how to flash rom though pendrive i didnt find the files that i were in my pendrive in twrp menu
:crying:
Click to expand...
Click to collapse
You first have to select the usb storage in TWRP because TWRP detected internal storage. U can even mount usb otg from TWRP options. after selecting usb then u can see the files in ur usb drive.
I'm stuck on the same Warning screen, it is not a bootloop since the phone just seems to freeze but after a minute I get the windows sound as if you conected something via USB, but the warning screen stays, I've let it for hours and I've flashed stock roms. Even when you flash a no warning boot logo.bin the screen shows again even when mfastboot shows as succesful flash. Out of ideas now, please help
Code:
Model XT1068
Thanks
Thanks
Solution for MotoG locked in bootloader,
I think you must have tried to install another kernel version or so. If you have installed cyanogen try resinsallting the lasted update by going into custom recovery and flashing the latest update in the cmupdater file. Worked for me ! Lets hope that it works for you too. All the best !
I unlocked my new Moto G 4g xt 1039 (Android 4.4) without problems, but i cannot get it to accept any recovery i try to install. I tried manual adb with CWM and TWRP. I also tried the Moto Tool AIO and Easy Recovery.
All of them failed to flash the recovery except once when the recovery was flashed, but after booting it, it did not react to keypresses and touch.
I'm on Windows 64bit nad flashing every other device i have and had wasn't a problem.
Does anyone have an idea. Every thread regarding the device was more or less outdated so help would be appreciated. I like my devices rooted.
Just a short update and push ? Chainfire root worked. Still no success with recovery though.
ppzoid said:
Just a short update and push ? Chainfire root worked. Still no success with recovery though.
Click to expand...
Click to collapse
Are you using a recovery built for peregrine?
Try one of the TWRP versions by @Somcom3X found here:
http://forum.xda-developers.com/mot...ection-somcom3xs-experimental-corner-t2996266
Yes, i've also tried to flash one of @Somcom3X recoveries, too.
The problem seems to be one of my previous attempts to flash a recovery, because i get two messages on the phone in fastboot mode when trying to flash a recovery:
cmd : getvarartition-type:recovery
cmd : getvaar:max-download-size
I'm pretty sure there should be at least two more lines after that, when sucessfully flashing. To me it seems as if the recovery partition seems to be broken. Any idea how to fix it. If iit is the problem at all.
I already tried reinstalling the stock recovery with Moto Tool AIO. Iget the following ooutput on the phone:
cmd : getvarartition-type:recovery
cmd : getvaar:max-download-size
cmd : download:00a00000
cmd : flash:recovery
bab check failed for recovery
Have you tried booting the image? Fastboot boot xxx.img
Sent from my XT1045
I tried now. the upper third of the screen is white and the two lower thirds are blue for a moment and fade to black with backlight on.
Update: For reasons beyond my knowledge it works. I cannot get it to boot to recovery from the fastboot menu, but it works with adb command boot recoveryxxx.img and from within advanced boot menu.
Friends, made unlocking the bootloader and used the kingo root and the procedure was successful
XT1039
Android 4.4.4
Hi,
My Moto G XT1032 was on 5.0.2 when I finally decided to root it. I followed the instructions here (reddit.com/r/MotoG/comments/22mimr/the_guide_to_rooting_the_motog_with_a_howto) and all was going well until right at the end after I installed the supersu zip and rebooted.
Right now, every time I try booting up my phone, it shows the Moto G logo (without the bootloader warning since I flashed the original logo), the Motorola animation, and then my screen goes black. I don't however think it's off, since when I plug my phone into my computer, it's eventually detected (but nothing is there when I open the internal storage; likewise, 'adb devices' reveals nothing attached).
When I use volume down + power, I can reach the fastboot screen, but selecting recovery only brings me to a screen with the text 'no command'. The only strange thing I can recall during the entire root process is that when I was in CWM and making my backup image, the screen was flickering slightly.
Does anyone know what I can try at this point?
Thanks for your time and any help you can provide,
indavidual
indavidual said:
Hi,
My Moto G XT1032 was on 5.0.2 when I finally decided to root it. I followed the instructions here (reddit.com/r/MotoG/comments/22mimr/the_guide_to_rooting_the_motog_with_a_howto) and all was going well until right at the end after I installed the supersu zip and rebooted.
Right now, every time I try booting up my phone, it shows the Moto G logo (without the bootloader warning since I flashed the original logo), the Motorola animation, and then my screen goes black. I don't however think it's off, since when I plug my phone into my computer, it's eventually detected (but nothing is there when I open the internal storage; likewise, 'adb devices' reveals nothing attached).
When I use volume down + power, I can reach the fastboot screen, but selecting recovery only brings me to a screen with the text 'no command'. The only strange thing I can recall during the entire root process is that when I was in CWM and making my backup image, the screen was flickering slightly.
Does anyone know what I can try at this point?
Thanks for your time and any help you can provide,
indavidual
Click to expand...
Click to collapse
You can try reflashing the ROM or restore stock. http://forum.xda-developers.com/showthread.php?t=2542219
dominati said:
You can try reflashing the ROM or restore stock. http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Unfortunately, flashing anything doesn't seem to work (with my cmd open, whatever commands I type give me "error: device not found"). Is there anything else I can try?
indavidual said:
Unfortunately, flashing anything doesn't seem to work (with my cmd open, whatever commands I type give me "error: device not found"). Is there anything else I can try?
Click to expand...
Click to collapse
With the phone off, hold the power and volume down buttons simultaneously for 5 seconds to access the bootloader. From there you can you fastboot commands to restore stock. Find your stock firmware here http://www.filefactory.com/folder/c6cdedc45a775d27
Follow the steps in the guide I posted originally.
Edit: You could also reflash recovery via fastboot. fastboot flash recovery recovery.img
Also the line on your screen is do to Lollipop bootloader. The recovery you are using is probably for KitKat bootloader. There may not be a Lollipop bootloader compatible recovery available for you device yet.
dominati said:
With the phone off, hold the power and volume down buttons simultaneously for 5 seconds to access the bootloader. From there you can you fastboot commands to restore stock.
Follow the steps in the guide I posted originally.
Edit: You could also reflash recovery via fastboot. fastboot flash recovery recovery.img
Also the line on your screen is do to Lollipop bootloader. The recovery you are using is probably for KitKat bootloader. There may not be a Lollipop bootloader compatible recovery available for you device yet.
Click to expand...
Click to collapse
I ended up just flashing cwm, clearing everything, then re-installing super su, and it works Thanks a bunch for your help!
Hi all. So my stock opo somehow got bricked overnight while charging. It's completely stock and I have no idea why.
Status of my problem:
-Stuck on Android boot screen.
-Able to access fastboot.
-Can't access recovery mode
-No TRWP
-it's still locked
-Tried unlocking with fastboot oem unlock cmd / toolbox but it just reboots back to android stuck screen after its done but its still locked after checking with fastboot oem device-info cmd.
*USB debugging not enabled (cant enable it cuz i cant go in my phone duh)
-Cm11 33r I think...
-Installed android adb on device manager
But couldn't detect it on the list ("adb devices" cmd)
-Able to detect serial using fastboot device cmd tho.
-Tried universal adp, adb bootloader driver, Samsung adb driver, composite driver and it still won't detect it on list.
-Tried using another usb port.
-computer doesn't detect phone unless I go on fastboot or hold power+up volume for 10 sec (this shows QHUSB_BULK)
-Tried using msm9874downloadtool.exe with cm 11, doesn't do anything even tho it's completed and it's green.
-Tried using msm9874downloadtool.exe with color os but it doesnt work as well, in fact, it made my screen have multiple grey lines vertically across my screen and no fastboot display or android display.
-Tried just flashing Cm11 33r images but it won't work cuz I'm locked.
-Tried unlocking but goes back to my other problem of device not being on the list and not having usb debugging enabled.
Tldr;
Phone stuck on Android boot screen
USB debugging not enabled
Phone is not unlocked so I can't flash anything
Thanks for your time and effort. I really need help.
I still need help guys plzzz. Thankss
Have you tried getting into download mode? I think you power it off. Connect to USB and hold vol down? Or vol down + power. Something like that. Once in DL mode, flash it. There's a tutorial somewhere.
Sent from my A0001 using Tapatalk
ackliph said:
Have you tried getting into download mode? I think you power it off. Connect to USB and hold vol down? Or vol down + power. Something like that. Once in DL mode, flash it. There's a tutorial somewhere.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
download mode? you mean fast boot? power + down doesnt load anything. Power + up goes into fastboot mode.
And i cant flash anything because you have to unlock the phone first. But mine is not unlocked. And i cant unlock it with fastboot oem unlock cmd because all it does it reboots my phone. Yes i checked if im unlocked after that with fastboot oem device-info.
First try to go to recovery by pressing volume down+ power button at the same time and then clear data and factory reset. This will wipe out ur data on phone but u can revive ur device by flashing stock rom using flashing tolls available... Check youtube videos for flashing tools.
Once you clear the data and factory reset from recovery mlde then ur device will be at the state where there is no OS in it n just a stock kernel. Give it a try and let me know
I can't get into recovery. Power + down only stays at android boot screen.
Have the exact same issue. Did you find a fix???
Even if your bootloader is not unlocked you can flash stock rom. Use oneplus one flashtool and flash cm11s. There are plenty of videos available on net for these problem, just go through them or try the hard bricked video to solve your problem. I hope it helps you. I lost my one device because of a silly mistake so i know the pain.
I've tried flashing stock rom. Cm11 33r. But it keeps telling me I'm locked.
put it on fastboot mode, download the stock rom from this:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Choose carefully between 16gb or 64
unzip the file and click on the flashall.bat or something like that , it's a script and it will flash everything
and you should be good
you will loose all your data, i don't know if you dont flash userdata and you remove it from the file and remove it's line from the script, maybe you wont loose your data, but try it
if you want i can help you through teamviewer
My note 6 pro suddenly started doing boot loop. I tried to revive it by flashing stock firmware but nothing seems to help. It has unlocked bootloader, with TWRP installed. This is what I tried:
Put phone in fastboot mode, I do see the fastboot image.
Computer recognizes the phone. 'fastboot devices' shows correct device.
Using MI Flash tool to flash 10.3.6 global fastboot image. It takes about 160 seconds to flash all the partitions. The phone will reboot at the the end of the flash. Flash tool doesn't say "successful" though. Its status is still "flashing".
No other errors. When the phone restarts, it is still stuck in the boot loop. Interesting thing is, if I press volume + button and power button, I see TWRP flash for a quick second on the screen then boot again. Looks like the recovery image wasn't flashed properly.
Looked at the logs. Nothing strange. Also tried to run 'flash-all.bat' in a command line (not sure if we are supposed to do that), but all the fastboot flash commands look OK.
Anything else I can do to revive this phone?