hello,
I buyed a moto g, it's my first smarthphone... it's a XT1069 Dual Sim
I followed this tuturial http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245 ,
I get to unlock the bootloader, but when I get to this point
4. Flash Recovery through fastboot mode/bootloader mode
and Go into your adb+fastboot folder and Type in CMD prompt
Command :
Code: fastboot flash recovery TWRP2801-titan-motog-2014.img
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
RastaFATian said:
hello,
I buyed a moto g, it's my first smarthphone... it's a XT1069 Dual Sim
I followed this tuturial http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245 ,
I get to unlock the bootloader, but when I get to this point
4. Flash Recovery through fastboot mode/bootloader mode
and Go into your adb+fastboot folder and Type in CMD prompt
Command :
Code: fastboot flash recovery TWRP2801-titan-motog-2014.img
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
Click to expand...
Click to collapse
There's no need to make multiple topics, my friend...
Remember that the TWRP IMG file must be in the same folder as your Fastboot files.
So, you can copy TWRP2801-titan-motog-2014.img file to the directory where your Fastboot is.
Or, you can type the directories correctly. For example, if your TWRP2.8.0.1 IMG file is located on your Desktop:
So, your command should be: fastboot flash recovery C:\Users\"username"\Desktop\TWRP2801-titan-motog-2014.img
Instead of typing, you can also drag-and-drop the TWRP2801-titan-motog-2014.img file into the CMD window.
Got it?
rafaelbrunner said:
There's no need to make multiple topics, my friend...
Remember that the TWRP IMG file must be in the same folder as your Fastboot files.
So, you can copy TWRP2801-titan-motog-2014.img file to the directory where your Fastboot is.
Or, you can type the directories correctly. For example, if your TWRP2.8.0.1 IMG file is located on your Desktop:
So, your command should be: fastboot flash recovery C:\Users\"username"\Desktop\TWRP2801-titan-motog-2014.img
Instead of typing, you can also drag-and-drop the TWRP2801-titan-motog-2014.img file into the CMD window.
Got it?
Click to expand...
Click to collapse
I'm sorry about multiple topics... my bad.... but you can erase the other in general topic....
but to flash i need to be in recovery mode at boolloader, no?
i can do this command in bootloader menu?
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
Fastboot and recovery are two different things. If you can get to Fastboot (bootloader) mode you should be able to flash recovery from there as stated by rafaelbrunner.
Hi Guys !
I'm facing a problem on rooting my Moto G 2014.
I've easily unlocked the bootloader but i can't flash the TWRP recovery.
I've read everything I could read about the process and I think I'm doing it the right way (the recovery file in the adb folder, etc...) and everything seems to be ok.
I've just a purple line at the end of the TWRP flashing procedure saying:
Mismatched partition size (recovery)
This post says that it's not really a problem: http://forum.xda-developers.com/showpost.php?p=48294073&postcount=6
Then, when I reboot the recovery, the phone reboots and the system starts normally (instead of restarting with the custom recovery ?). When I switch it off and switch it on in recovery mode, I still have the stock recovery.
Tried several times with TWRP 2.8.0.1
I can't say if it's because of a problem with TWRP (it's said here that it is buggy) or because I'm doing something wrong that I don't succeed.
I saw that there was a 2.7.1.1 release of TWRP for Moto G 2014 but it's no more available anywhere for now. I would have liked to try it...
Do you know if there's some known issues about flashing the Moto G 2014 recovery or can you help in any way ?
Hi guys !
I'm still investigating my problem and still trying to root the phone.
Here is what I get with adb:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWAP2801 titan-motog-2014.img
target reported max download size of 536870912 bytes
sending 'recovery' (9738 KB)...
OKAY [ 0.344s]
writing 'recovery'...
OKAY [ 0.353s]
finished. total time: 0.700s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
error: device not found
C:\Program Files <x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
The device seems to be seen when it's about writing the file on the storage but it's no more found when it's about rebooting the recovery...
Can someone help ?
magmatik said:
Hi guys !
I'm still investigating my problem and still trying to root the phone.
Here is what I get with adb:
The device seems to be seen when it's about writing the file on the storage but it's no more found when it's about rebooting the recovery...
Can someone help ?
Click to expand...
Click to collapse
First of all Uninstall ur old Moto Usb Drivers and fastboot drivers and Reboot your Pc And Again Install Ur Usb Drivers.
2987
jbanti said:
First of all Uninstall ur old Moto Usb Drivers and fastboot drivers and Reboot your Pc And Again Install Ur Usb Drivers.
Click to expand...
Click to collapse
Hi !
Thanks for your answer !
What do you mean exactly ? I didin't have any "old Moto usb drivers before". I installed them for the first time few days ago to unlock my bootloader.
Do I still have to uninstall these drivers (that are not that old) and install again the same ones ?
magmatik said:
Hi !
Thanks for your answer !
What do you mean exactly ? I didin't have any "old Moto usb drivers before". I installed them for the first time few days ago to unlock my bootloader.
Do I still have to uninstall these drivers (that are not that old) and install again the same ones ?
Click to expand...
Click to collapse
You can use "adb reboot recovery" only if the phone is turned on in normal android os ( in bootloader mode it'll only recognize fastboot commands ), and you must be sure also to have debug usb option enabled under settings/developer settings.
1932
eskamhl said:
You can use "adb reboot recovery" only if the phone is turned on in normal android os ( in bootloader mode it'll only recognize fastboot commands ), and you must be sure also to have debug usb option enabled under settings/developer settings.
Click to expand...
Click to collapse
Hi eskamhl,
I warmly thank you for trying to help me.
I'had enabled usb debbug, no problem about that.
I"m not sure I understand what you mean when you say that the phone has to be " turned on in normal android os". I thought that the device had to started in recovery mode to install TWRP.
I tried to install TWRP with adb reboot recovery and with the phone turned on in normal android os.
adb says <waiting for device> when i paste and execute flash recovery TWRP2801-titan-motog-2014.img
magmatik said:
Hi eskamhl,
I warmly thank you for trying to help me.
I'had enabled usb debbug, no problem about that.
I"m not sure I understand what you mean when you say that the phone has to be " turned on in normal android os". I thought that the device had to started in recovery mode to install TWRP.
I tried to install TWRP with adb reboot recovery and with the phone turned on in normal android os.
adb says <waiting for device> when i paste and execute flash recovery TWRP2801-titan-motog-2014.img
Click to expand...
Click to collapse
Adb is one thing, fastboot is a different one.
If you give a "fastboot command" from the command prompt the phone must be in bootloader mode, instead if you give an "adb command" you must have the phone normally turned on.
Having said that, I didn't understand what's your problem... are you tryin' to boot into recovery mode or trying to flash twrp recovery?
It seems that you already flashed/installed a custom recovery ( TWRP ) from what you wrote, isn't it?
eskamhl said:
Adb is one thing, fastboot is a different one.
If you give a "fastboot command" from the command prompt the phone must be in bootloader mode, instead if you give an "adb command" you must have the phone normally turned on.
Having said that, I didn't understand what's your problem... are you tryin' to boot into recovery mode or trying to flash twrp recovery?
It seems that you already flashed/installed a custom recovery ( TWRP ) from what you wrote, isn't it?
Click to expand...
Click to collapse
That's the point, I'm trying to flash a custom recovery (TWRP) in order to be able to flash SU.
I'm sorry about my poor english. I'm french and I confess that I'm absolutely comfortable in english.
For now the only thing I succeeded to do is to unlock the bootloader.
What I understand is that I have now to install TWRP with adb, am I right ?
magmatik said:
That's the point, I'm trying to flash a custom recovery (TWRP) in order to be able to flash SU.
I'm sorry about my poor english. I'm french and I confess that I'm absolutely comfortable in english.
For now the only thing I succeeded to do is to unlock the bootloader.
What I understand is that I have now to install TWRP with adb, am I right ?
Click to expand...
Click to collapse
No, you're not
You already did the installation of the custom recovery since you said that you received this message "Mismatched partition size (recovery)", now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select ).
If it won't boot maybe you should check the md5 of the downloaded recovery .img, probably it's a corrupted download.
eskamhl said:
No, you're not
You already did the installation of the custom recovery since you said that you received this message "Mismatched partition size (recovery)", now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select ).
If it won't boot maybe you should check the md5 of the downloaded recovery .img, probably it's a corrupted download.
Click to expand...
Click to collapse
When I try to boot into recovery from the bootloader (what I already did before), the screen turns black, 1 sec later the led switch on for half a sec and nothing else happends.
So, as you say, the recovery I downloaded was maybe corrupted. I'll check.
Guys, I've found the solution !
I think everything was ok from the beginning. The only thing that I did not understand was that I have to press vol- in fastboot to focus on "recovery" and to press vol+ to launch the recovery.
I didn't read it anywhere, i just see this in this video : https://www.youtube.com/watch?v=jr14wNgazOw&hd=1 (see at 7"15).
Anyway, thank you for trying to help me and see you soon for all the good things coming for this phone !
magmatik said:
Guys, I've found the solution !
I think everything was ok from the beginning. The only thing that I did not understand was that I have to press vol- in fastboot to focus on "recovery" and to press vol+ to launch the recovery.
I didn't read it anywhere, i just see this in this video : https://www.youtube.com/watch?v=jr14wNgazOw&hd=1 (see at 7"15).
Anyway, thank you for trying to help me and see you soon for all the good things coming for this phone !
Click to expand...
Click to collapse
My friend... a few posts above
eskamhl said:
now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select )
Click to expand...
Click to collapse
I successfully installed twrp recovery system but I can't do any backup, the system reboot in the process...
eskamhl said:
My friend... a few posts above
Click to expand...
Click to collapse
You're right... my bad
Im trying to flash back to stock rom but the device is not responding, i already have try on mfastboot and on fastboot but it just say "waiting for device" when i try some comand, i have motorola drivers, i've tryed a program called PDAnet too, i have usb debug on, can someone help-me?
are you using Windows 7/8/10 ?
did you boot into bootloader mode?
(adb debug mode is for adb and bootloader mode is for fastboot)
interaction is: adb reboot bootloader (when device is on and adb debug is on)
zitronenmelissa said:
are you using Windows 7/8/10 ?
did you boot into bootloader mode?
(adb debug mode is for adb and bootloader mode is for fastboot)
interaction is: adb reboot bootloader (when device is on and adb debug is on)
Click to expand...
Click to collapse
i have tryed all, but no response, i give it up and install other custom rom but thanks for trying help
Hello, first off all I will thank all the help you can provide,
My problem, My urbane was running AW 2.0 but it made it laggy I unlock the bootloader and flash it with the 4 cores boot.img from this thread (I did not root or install twrp) then I realize OTA wont get into my urbane so I flash the stock boot.img from the same thread above, then uptade via OTA, all fife until here.
Then I try to reload the 4cores boot.img and my problems started. after this the watch wont start anymore and stay boot animation. but was responsive to adb reboot bootloader commands so I then flash stock boot.img but also didnt boot (even waiting over 20 mins) then as I had img files (BOOT, RECOVERY and SYSTEM to restore it to original AW v1.5 i tried flashing that boot.img from this thread the MM-boot.img flashed didnt help either. then I pressed the button for 20 secs and watch reload and even when it sounds how to is detected as USB on my computer and it is shown as "Android Bootloader Interface" on the device manager it never ever is shown under adb devices command. whatever I do it does not shown under devices attached so I can flash back factory boot, recovery and system images.
So if I start the watch stays forever on the boot animation, and if I swipe my finger at start to boot into bootloader is detected by windows as "Android Bootloader Interface" but "adb devices" command wont show the watch.
Help Please!!!!
Ale.
If manually start my device in bootloader it is detected by windows device manager, but when I type "adb devices" have nothing but if I set manually to bootloader then to recovery mode and then I select apply update from ADB, then watch is again detected by device manager, in this case and ONLY this case adb devices shows my watch but only as sideload ("my serial number" sideload) what can I do there? I cant use fastboot commands.
The things is that I think I wipe data and factory reset the watch and now I dont have adb debugging enable and cant so fastboot commands what can I do, please? is tehre a way to enable adb debugging without being able to boot the watch? can I sideload (as is the only way adb see my watch) the full "NXH19X_full_factory.zip" I tried "adb sideload NXH19X_full_factory.zip" but strat to write into the watch but gives error 21 and close after few seconds.
Please Help.
Ale.
**UPDATE**
Even when adb devices wont show my watch I was still able to flash factory images and is all working now.
This issue is over, close thread please and thanks.
I'm expecting the same simptoms and issues over here. All happens after to flash the 4 core img. Sudelly stucks. Please let me know if you have any news about
Hey guys,
I have a problem while trying to flash TWRP on my Xiaomi Mi5. TWRP was installed earlier and worked completly fine with flashing custom ROMs, flashing OpenGAPs or rooting the device but now for some reason TWRP got lost and the standard Xiaomi recovery is on the device again. Installed was MIUI 8 in the Dev-Version (weekly patches) for the last half year and was the last ROM flashed with TWRP.
And now comes the problem when i try to install/flash the twrp image via fastboot: If i reboot the device in fastboot mode it shows the following behaviour:
1. It show the fastboot logo on the screen for about 10-30 seconds before it reboots automaticly (doesn't matter if i connect it via USB before or while it shows the fastboot logo)
2. While it shows the logo on the screen and it is connected via USB it's not showing up in the console when i list the all connected fastboot devices
I can still use the devices standard recovery and the installed OS, just the fastboot part seems to be brocken. Am i missing a driver on my computer or something?
Has somebody else an idea how i can solve this automatic reboot in fastboot mode?
Edit: If this Thread belongs into another catagory, i apologize
Make sure minimal adb and fastboot are installed in your pc. After that, enable usb debugging from developer options and connect with your pc and let it there for a while to install drivers on your pc. Then go to twrp and your phone should no longer reboot after your connect usb. Flash twrp here.
Sent from my Xiaomi Mi5 using Tapatalk
SilverMarcs said:
Make sure minimal adb and fastboot are installed in your pc. After that, enable usb debugging from developer options and connect with your pc and let it there for a while to install drivers on your pc.
Click to expand...
Click to collapse
ADB and FASTBOOT installed -> checked!
USB-Debugging enabled -> checked!
Windows installing drivers automaticly -> unsure. Windows didn't installed anything it just notified me that there is a new USB-Device (Device is also showen as ADB-Device and appears in the list of connected adb devices)
SilverMarcs said:
Then go to twrp and your phone should no longer reboot after your connect usb. Flash twrp here.
Click to expand...
Click to collapse
To that: TWRP is not installed on the phone anymore. I just have the standard xiaomi recovery where i'm not able to flash a .zip or something. I can just wipe all my data there
The reboot behaviour also appears if i switch to fastboot via "adb reboot bootloader" command while spamming "fastboot devices" to check if it appears before it reboots.
The standard recovery is usable as it should be without any reboots only the fastboot mode seems brocken.
FrozenPie1 said:
ADB and FASTBOOT installed -> checked!
USB-Debugging enabled -> checked!
Windows installing drivers automaticly -> unsure. Windows didn't installed anything it just notified me that there is a new USB-Device (Device is also showen as ADB-Device and appears in the list of connected adb devices)
To that: TWRP is not installed on the phone anymore. I just have the standard xiaomi recovery where i'm not able to flash a .zip or something. I can just wipe all my data there
The reboot behaviour also appears if i switch to fastboot via "adb reboot bootloader" command while spamming "fastboot devices" to check if it appears before it reboots.
The standard recovery is usable as it should be without any reboots only the fastboot mode seems brocken.
Click to expand...
Click to collapse
Weird. Everytime this sorta problem happens to me, its because windows didnt have the drivers installed after you connect your pc with debugging enabled. So thats the only troubleshooting i did to fix things. And yeah it did show me drivers installed correctly after i connected phone with debugging enabled. Maybe for some reasonn those drivers arent being installed to windows. Give it more time maybe? [emoji23]
Sent from my Xiaomi Mi5 using Tapatalk
SilverMarcs said:
Weird. Everytime this sorta problem happens to me, its because windows didnt have the drivers installed after you connect your pc with debugging enabled. So thats the only troubleshooting i did to fix things. And yeah it did show me drivers installed correctly after i connected phone with debugging enabled. Maybe for some reasonn those drivers arent being installed to windows. Give it more time maybe? [emoji23]
Click to expand...
Click to collapse
It's not working on both Windows 10 Machines i have. I'll try to install Windows 7 on my Laptop (or in a VM) and look if that works when i'm home again
Edit: Well, now i'm totally confused... For some reason fastboot started working again this morning so i was able to flash TWRP again. Anyway thanks for the help
FrozenPie1 said:
Hey guys,
I have a problem while trying to flash TWRP on my Xiaomi Mi5. TWRP was installed earlier and worked completly fine with flashing custom ROMs, flashing OpenGAPs or rooting the device but now for some reason TWRP got lost and the standard Xiaomi recovery is on the device again. Installed was MIUI 8 in the Dev-Version (weekly patches) for the last half year and was the last ROM flashed with TWRP.
And now comes the problem when i try to install/flash the twrp image via fastboot: If i reboot the device in fastboot mode it shows the following behaviour:
1. It show the fastboot logo on the screen for about 10-30 seconds before it reboots automaticly (doesn't matter if i connect it via USB before or while it shows the fastboot logo)
2. While it shows the logo on the screen and it is connected via USB it's not showing up in the console when i list the all connected fastboot devices
I can still use the devices standard recovery and the installed OS, just the fastboot part seems to be brocken. Am i missing a driver on my computer or something?
Has somebody else an idea how i can solve this automatic reboot in fastboot mode?
Edit: If this Thread belongs into another catagory, i apologize
Click to expand...
Click to collapse
I too have the same problem..****
Install MiFlash on your PC and try again, the device will show up correctly on fastbook devices command. It was a USB drivers issue in my case.
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!