Hi,
I own a 2013 Moto G, using CM13 the very first nightly.
But then I tried flashing the CM12 Snapshot, now its in
a bootloop, ADB says its unauthorized, but I cant change any settings because
its in a bootloop. When I try to use adb sideload and flash the roms again
adb stucks at 47% and doesnt move on.
Any ideas?
Im Using Minimal ADB
Greetz
Related
Moto G is not recognized as a adb device when in fast boot.Its recognizable when the device is powered on. What are the chances that i screwed down my phone ?
ravz68 said:
Moto G is not recognized as a adb device when in fast boot.Its recognizable when the device is powered on. What are the chances that i screwed down my phone ?
Click to expand...
Click to collapse
Adb can be used when you're phone is on. When in fastboot (bootloader) you begin using "fastboot _______". In this case: fastboot devices
Tapatalked with Boost Mobile Moto G (xt1031). Running Android 5.1 on CM12 by Meticulus.??the smoothness
dirty_smurf45 said:
Adb can be used when you're phone is on. When in fastboot (bootloader) you begin using "fastboot _______". In this case: fastboot devices
Tapatalked with Boost Mobile Moto G (xt1031). Running Android 5.1 on CM12 by Meticulus.the smoothness
Click to expand...
Click to collapse
ACtually, the phone was powering off automatically when i booted it up. Since then i have been trying to flash roms which didnt work until i flashed a Brazillian ROM which booted it up.But i havent been able to find it in fastboot devices now. Finally i wanna settle for a CM11 with philz. But unable to detect it,how can i change the recovery.?
ravz68 said:
ACtually, the phone was powering off automatically when i booted it up. Since then i have been trying to flash roms which didnt work until i flashed a Brazillian ROM which booted it up.But i havent been able to find it in fastboot devices now. Finally i wanna settle for a CM11 with philz. But unable to detect it,how can i change the recovery.?
Click to expand...
Click to collapse
For flashing recovery use either of the two
If you can boot into OS then download flashify app
Or use fastboot command
fastboot flash recovery recovery.img
Sent from falcon
PRESS THANKS IF HELPED?
ADB commands work when the phone is booted and USB debugging has been enabled.
Fastboot and mfastboot commands only work when the phone is in fastboot mode.
hi guys, I wonder if anyone can help
I have been going through various tutorials on this forum for the past 3 weeks and still stuck in same position.
My moto g had cyangenmod 11 and working fine until it droppped, I rebooted and it was stuck in bootloop.
1) I have tried to reflash - nothing changes
2) Tried different rom via adb push and sideload - nothing changes. Adb push command works but rom.zip fle is not visible on sdcard
i tried "adb push rom.zip /sdcard/" which shows 100% transfer
3) Tried to go back to stock using mfastboot - files get installed without errors but I end up with the cyangenmod bootloop screen staring at me (lol)
4) I can get into custom reocvery and have verison 6.0.4.5 - even when I try falshing different recovery..nothing changes
5) once I boot into bootloader..the command "adb devices" does not return anything so I assume usb debugging is disabled. I can't enable it as the phone does not go past bootloop screen.
6) I pulled all data from the phone and it still has all photos and videos so userdata erase commands are not working.
7) I have tried locking the bootloader using mfastboot and i get the following " sst lock failure"
Its almost like the memory has been locked and cannot be changed even though fast boot shows files being written to it.
If this is knackered, i might as well through it away as I have lost hope.
Also the bootloader is version 40.19, I have tried updated using BUT+1.29 but update fails.
Have you solved the problem? I came up with the same problem with my N910P.
Hi,
i own a oneplus one and flashed Cyanogenmod 13 with ADB sideload in TWRP with no errors. But now i tried to reboot and got the message: No os installed! Are you sure you wish to reboot?
Is there hope for recover?
I have successfully installed CM 14.1 for moto x 2014, while trying to get pixel nav bar I made a mistake with SystemUI.apk and entered infinite bootloop. Now I can't enter recovery mode and flash CM again. Help
KeyserSoze6 said:
I have successfully installed CM 14.1 for moto x 2014, while trying to get pixel nav bar I made a mistake with SystemUI.apk and entered infinite bootloop. Now I can't enter recovery mode and flash CM again. Help
Click to expand...
Click to collapse
Does adb recognize the device? If so, you can always try adb reboot bootloader or recovery. Have you tried to switch it completely off for a while (around 10-20 mins) and trying to boot into bootloader?
RAZERZDAHACKER said:
Does adb recognize the device? If so, you can always try adb reboot bootloader or recovery. Have you tried to switch it completely off for a while (around 10-20 mins) and trying to boot into bootloader?
Click to expand...
Click to collapse
Adb recognised, thanks for helping
KeyserSoze6 said:
Adb recognised, thanks for helping
Click to expand...
Click to collapse
Take the zip file from your rom and adb push the systemui to the respective directory
I am having moto g3 xt1550 bought in India. I have previously gone to Lineage os 14.1. But it was not allowing Jio calls when data is off.
I went back to stock rom XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55-2_cid7_subsidy-DEFAULT_CFC.xml.zip.
First I tried to flash twrp. It showed "no command" error when trying to go to recovery mode. Howeverafterstudying in net, after flash, instead of rebooting, I went to recovery it worked.
However, after flashing superSu, reboot led to hanging motorola screen.
This is first failure.
Second I copied from net boot.superboot.img.
I tried fastboot boot boot.superboot.img.
This did not show any error. But rootchecker says error in root
Third I tried directly adb root.
It gave error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb root
adbd cannot run as root in production builds
Hence I could not pull, edit and push.
Any solution will be appreciated.
Sorry, I am very confused by what your saying... why don't you just reflash the stock image with fastboot to get it working, then start over, backing up in TWRP first?
acejavelin said:
Sorry, I am very confused by what your saying... why don't you just reflash the stock image with fastboot to get it working, then start over, backing up in TWRP first?
Click to expand...
Click to collapse
Thanks for your response. I tried and succeeded in making work both stock rom and as well LOS 14.1 06 Jul2017 rom.