Database Develop

Problem when rooting Custom Rom

Hi guys!
I received my Nexus yesterday en immediately rooted and unlocked the device. No problems so far.
I want to install a the cyanogen custom rom on my nexus but get stuck in the recovery step.
I have used the tutorial from Theunlockr . com (unfortunately I cant insert a link here because Im a new member)
Because I already rooted and unlocked my Nexus I started with ''III. Flash the Custom ROM''. I managed to start up the bootloader and click on 'Recovery'. Here the problems start, after clicking on 'recovery' a screen with a yellow exclamation shows up. (see attachment for screenshot)
Can somebody help me with flashing my Nexus with a custom rom? Thanks in advance!

Try to run "fastboot boot recovery.img" and see if that works. (Something like that anyway)
This was what I did for all my time using Amon's 1.5.3 recovery. Now that I'm on 1.6.0, I can use the normal recovery. That worked perfectly for me anyway. I also would always boot to that screen when attempting the normal recovery via the phone.

Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' on my Mac?
I am quite an android-noob.

Stinosss_31 said:
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' ?
I am quite an android-noob.
Click to expand...
Click to collapse
So am I
To run fastboot, you should simply go find the Android SDK download. Once you've downloaded that, make your way to the tools folder. Place the recovery image in that folder and then Shift+Right Click in the window. You click the option to bring up a command prompt.
In that Command prompt, type flashboot devices and verify the PC sees your phone. If so, then you can do the Flashboot command. Though you may need USB drivers. If you do need them, they're somewhere in this forum, but I've completely lost track of them.
P.S. if my initial command doesn't work... You might need to try "fastboot boot recovery recovery.img"
(Note... Don't try "Flashboot".. That was a typo )

Stinosss_31 said:
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' ?
I am quite an android-noob.
Click to expand...
Click to collapse
got this info from the same site you posted, you just skipped the step before you started to flash the rom altogether.
II. Flash a Custom Recovery Image
1. Download the Nexus One Amon Ra Recovery Image below:
Nexus One Recovery Image (Link under Download in the first Post)
2. Save the recovery image file inside the superboot folder you used to root the phone.
3. Turn the phone off and then plug it in via USB cable.
4. Turn it on by holding down Power and the Trackball to get into fastboot mode.
5. Open a command prompt and type the following with hitting enter at the end of each line:
cd\
cd c:\superboot
fastboot-windows devices
*this is to check that the computer can see the phone (a serial should pop up if it can)
6. Then type:
fastboot-windows flash recovery recovery-RA-nexus-v1.5.3.img
7. This should flash the recovery image onto the phone.
Click to expand...
Click to collapse
The recovery img is in this thread
http://forum.xda-developers.com/showthread.php?t=611829
Click to expand...
Click to collapse
Also, you don't really need the android sdk for flashing the recovery img, but it's a good idea to download it for future use.

Can ANYONE just stop answering threads that are in wrong sections?

lazinase said:
Can ANYONE just stop answering threads that are in wrong sections?
Click to expand...
Click to collapse
Why? So that it gets moved and answered anyway? The sooner the guy gets helped out... The sooner the post gets buried.
A mod will be by to do their duty later. As the community, we may as well help in the mean time.
Man, oh man. Niceness has really lost some popularity in the virtual world, hasn't it...

Stinosss_31 said:
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' on my Mac?
I am quite an android-noob.
Click to expand...
Click to collapse
If you use a Mac, you don't deserve help. Bootcamp Windows and we'll talk.

grainysand said:
If you use a Mac, you don't deserve help. Bootcamp Windows and we'll talk.
Click to expand...
Click to collapse
great help!
for a mac just use ./fastboot-mac in the terminal

Like they said, sounds like you are missing recovery. Just do the step two, you skipped it. Why flame people? He is new, might as well help, instead of making this thread longer by telling him to post in right section.
Besides, he did find tutorials and followed them, he didn't come here completely unprepared and expecting people to walk him through. We all make mistakes sometimes, specially when dealing with something we are new to, he simply skipped a step.

MOD EDIT - Thread moved to Q&A

[Q] Bricked phone?

I think I may have bricked my phone. It's a rooted htc hero cdma. I'm running cyogenmod on it and it was working fine, until using metamorph to apply some changes to the theme.
I went to reboot, and it now it won't load past the htc screen. Even when i try the key combination to put it into recover mode. I didn't install a nandroid backup, and i'd be fine with just completely wiping my phone. can someone please help me?

Have you tried flashing the ROM back over itself without wiping? Try that first, and if that won't work, do a full format and reflash the ROM and you should be good to go.
And just an FYI, you really can't fully brick your phone by flashing a ROM or theme. You can always get it back.

Do what ranger suggested.
To elaborate, I *think* as long as your phone turns on, it is not bricked. Specifically, as long as you can boot to recovery you can do whatever you need to do, be it make fixes or start from scratch again. (I think even if you can't boot to recovery, but it turns on, you can run the RUU ). The only way to brick is to flash a wrong/corrupt radio or anything below the radio level.

Wipe then reboot and wait. When you change the framework, initial boot takes longer.
Sent from my HERO200 using XDA Premium App

I can't even get to the recovery mode screen. it'll only take me to where i can select hboot, fastboot, or wipe. nothing else will load up past that.

What key combination are you using? Hold home then depress end key/power key until phone vibrates.
Sent from my HERO200 using XDA Premium App

Load the fast boot ruu flash
Done
zbach said:
I can't even get to the recovery mode screen. it'll only take me to where i can select hboot, fastboot, or wipe. nothing else will load up past that.
Click to expand...
Click to collapse
Sent from my HTC Hero CDMA using XDA App

mahalocat said:
Load the fast boot ruu flash
Done
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
I can't select that option. Sorry for being kind of new at this, it just loads a bunch of green letters down really quick, telling me it can't find HERCIMG.zip/HERCDIAG.zip files. under that, it says no image or wrong image?

zbach said:
I can't select that option. Sorry for being kind of new at this, it just loads a bunch of green letters down really quick, telling me it can't find HERCIMG.zip/HERCDIAG.zip files. under that, it says no image or wrong image?
Click to expand...
Click to collapse
I am guessing you're not s-off, try this:
http://forum.xda-developers.com/showthread.php?t=958968

il Duce said:
I am guessing you're not s-off, try this:
http://forum.xda-developers.com/showthread.php?t=958968
Click to expand...
Click to collapse
I don't see the command to run "fastboot oem rebootRUU"

zbach said:
I don't see the command to run "fastboot oem rebootRUU"
Click to expand...
Click to collapse
It's a cmd prompt for windows. Open your command prompt from windows, with the phone plugged in usb, and then follow the steps in the OP of that thread.

il Duce said:
It's a cmd prompt for windows. Open your command prompt from windows, with the phone plugged in usb, and then follow the steps in the OP of that thread.
Click to expand...
Click to collapse
it keeps telling me fastboot is an unrecognized command. i have to be doing something wrong here.

zbach said:
it keeps telling me fastboot is an unrecognized command. i have to be doing something wrong here.
Click to expand...
Click to collapse
did you do the adb command first, like it says?

il Duce said:
did you do the adb command first, like it says?
Click to expand...
Click to collapse
yeah, it won't recognize that either. i'm selecting the right path to my C drive too. the driver just isnt recognized :/

You have to go further than just the C drive you have to specify the path all the way to the android-sdk-windows directory. If your on Vista, find the folder, hold the shift key and right click. Then select open a command line here.
EDIT: Yeah you need the drivers installed as well.
I had this happen to me a week ago. Luckily the phone rebooted and I was able to re-flash another recovery using the terminal emulator.

wild1z said:
You have to go further than just the C drive you have to specify the path all the way to the android-sdk-windows directory. If your on Vista, find the folder, hold the shift key and right click. Then select open a command line here.
EDIT: Yeah you need the drivers installed as well.
I had this happen to me a week ago. Luckily the phone rebooted and I was able to re-flash another recovery using the terminal emulator.
Click to expand...
Click to collapse
okay, i'm in now. i'm on the rebootRUU black and silver screen on my phone, but when i go to flash another .zip file, it says can't upload. do i need to download one from somewhere, or place it in a different folder?
I'm on my computer working through my command prompt by the way.

zbach said:
okay, i'm in now. i'm on the rebootRUU black and silver screen on my phone, but when i go to flash another .zip file, it says can't upload. do i need to download one from somewhere, or place it in a different folder?
I'm on my computer working through my command prompt by the way.
Click to expand...
Click to collapse
I've never actually done this fyi, but I think you need the RUU from htc.com, it would probably be under support, then hero cdma? DL that, and input the command "fastboot flash zip correctnameofhtcRUU.zip" in your cmd.

okay, i found and am currently downloading the file. so i should just have to root it to my SD, then flash it, right?
I'm really hoping this works.

il Duce said:
I've never actually done this fyi, but I think you need the RUU from htc.com, it would probably be under support, then hero cdma? DL that, and input the command "fastboot flash zip correctnameofhtcRUU.zip" in your cmd.
Click to expand...
Click to collapse
still nothing. it only tells me its and error, and cannot load the .zip file.

zbach said:
still nothing. it only tells me its and error, and cannot load the .zip file.
Click to expand...
Click to collapse
I don't know where the file should be located, but your posts in the other thread will yield better answers, jason knows the way better than me, given he started the thread. Wait for his response. I assume the error has something to do with where you have the ruu and what path you need to specify in the cmd. Wish I could be of more help. Once you fix it and get back to rooted and such, I HIGHLY recommend you get s-off, its basically like idiot-proofing your phone (no offense) so you can fix anything.
sent from a series of tubes.

[Q] Flash back to Stock

Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.

samwathegreat said:
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.
Click to expand...
Click to collapse
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.

samwathegreat said:
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.
Click to expand...
Click to collapse
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.

samwathegreat said:
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.
Click to expand...
Click to collapse
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.

samwathegreat said:
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.
Click to expand...
Click to collapse
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.

Awesome!

samwathegreat said:
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.
Click to expand...
Click to collapse
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!

boss. said:
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!
Click to expand...
Click to collapse
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:

samwathegreat said:
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:
Click to expand...
Click to collapse
Re-did the whole thing from scratch again and now all problems are solved. Really appreciate the help my friend!
Sent from my SM-N9005 using XDA Free mobile app

[Q] Nexus 6 stuck in bootloop

Hey sorry guys for being such a newbie here....need some help.
1. Ran the Nexus 6 1 click unroot kit
2. Somehow I screwed it up and now can't get past the teamwin blue screen just keeps popping back up.
3. I have a mac and have watched countless videos on reflashing factory image and nothing seems to be working.
Any ideas?

nickb2005 said:
Hey sorry guys for being such a newbie here....need some help.
1. Ran the Nexus 6 1 click unroot kit
2. Somehow I screwed it up and now can't get past the teamwin blue screen just keeps popping back up.
3. I have a mac and have watched countless videos on reflashing factory image and nothing seems to be working.
Any ideas?
Click to expand...
Click to collapse
Are you familiar with fastboot? If not, go here:
http://forum.xda-developers.com/showthread.php?t=3006500
I don't use Mac so I'm not sure exactly how the commands get typed but you should try:
fastboot format cache
fastboot format userdata

Evolution_Freak said:
Are you familiar with fastboot? If not, go here:
http://forum.xda-developers.com/showthread.php?t=3006500
I don't use Mac so I'm not sure exactly how the commands get typed but you should try:
fastboot format cache
fastboot format userdata
Click to expand...
Click to collapse
So, I tried doing it...on a mac you need to put ./then your fastboot
Here's what I get....
AdminisatorsAir:~ Nick$ ./fastboot format cache
-bash: ./fastboot: No such file or directory

nickb2005 said:
So, I tried doing it...on a mac you need to put ./then your fastboot
Here's what I get....
AdminisatorsAir:~ Nick$ ./fastboot format cache
-bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
Do you have the Android SDK installed or minimal fastboot tools?
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
Does your device serial number come up when you type fastboot devices?

Evolution_Freak said:
Do you have the Android SDK installed or minimal fastboot tools?
Click to expand...
Click to collapse
So, I had the SDK installed or thought I did...went to tools and then android clicked that and it keeps telling me java runtime environment isn't installed and to please install. I did it 3 times and still nothing when click android to try to get the sdk.

nickb2005 said:
So, I had the SDK installed or thought I did...went to tools and then android clicked that and it keeps telling me java runtime environment isn't installed and to please install. I did it 3 times and still nothing when click android to try to get the sdk.
Click to expand...
Click to collapse
Navigate to the platform-tools folder and open a command window there. Also, if that doesn't work, in the fastboot thread I linked, is a method to install fastboot and ADB system wide. Is that an option?

Well while evolution_freak helps you out, I'd like to chime in and say that I always stayed away from any 1-click anything, as well as any auto ROM/recovery updater.
You never know if you downloaded the wrong file
and then I just imagined hundreds of lines of code pouring into my poor little phone and how it would be screaming inside ):
I've seen lots of hard bricks happen from 1-click packages, learning how to do things the dirty way is more fun anyway!

Evolution_Freak said:
Navigate to the platform-tools folder and open a command window there. Also, if that doesn't work, in the fastboot thread I linked, is a method to install fastboot and ADB system wide. Is that an option?
Click to expand...
Click to collapse
This is my "tools" folder from the SDK I downloaded.

nickb2005 said:
This is my "tools" folder from the SDK I downloaded.
Click to expand...
Click to collapse
Now here's what happens when I click the android, I assume I want to install all 16 packages here? My question is where do I go from this step?

nickb2005 said:
Now here's what happens when I click the android, I assume I want to install all 16 packages here? My question is where do I go from this step?
Click to expand...
Click to collapse
Forgot the image...

nickb2005 said:
Forgot the image...
Click to expand...
Click to collapse
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378

Evolution_Freak said:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Click to expand...
Click to collapse
Thanks, maybe you can explain to me. In the image I attached it asks for password, but it won't let me type my computer password at all. Anyway to actually type it so it doesn't keep telling me incorrect password?

nickb2005 said:
Thanks, maybe you can explain to me. In the image I attached it asks for password, but it won't let me type my computer password at all. Anyway to actually type it so it doesn't keep telling me incorrect password?
Click to expand...
Click to collapse
I tried another guide to get adb and fastboot working. However, now it's showing my device isn't attached although it 100% is.

nickb2005 said:
Thanks, maybe you can explain to me. In the image I attached it asks for password, but it won't let me type my computer password at all. Anyway to actually type it so it doesn't keep telling me incorrect password?
Click to expand...
Click to collapse
I've never encountered this, again I don't have Mac. I'm guessing you couldn't get the simple ADB and fastboot tool to install, from the other thread?
I haven't had my morning coffee yet, so bare with me.

Evolution_Freak said:
I've never encountered this, again I don't have Mac. I'm guessing you couldn't get the simple ADB and fastboot tool to install, from the other thread?
I haven't had my morning coffee yet, so bare with me.
Click to expand...
Click to collapse
I know, it's early :/ im going on like 5 hours trying to fix this thing. I followed this guide: http://forum.xda-developers.com/showthread.php?t=1917237
I got adb and fastboot in the folder, but whenever I type ./adb devices it shows nothing is connected yet I am connected via USB and the phone shows me that.

nickb2005 said:
I know, it's early :/ im going on like 5 hours trying to fix this thing. I followed this guide: http://forum.xda-developers.com/showthread.php?t=1917237
I got adb and fastboot in the folder, but whenever I type ./adb devices it shows nothing is connected yet I am connected via USB and the phone shows me that.
Click to expand...
Click to collapse
Did you install the drivers?

Evolution_Freak said:
Did you install the drivers?
Click to expand...
Click to collapse
On a mac you don't need to install the drivers it said that was windows only when I tried clicking it in the SDK manager. Weirdly enough last night when I first tried this it actually showed something connected. So I am not sure what happened between then and now.

nickb2005 said:
On a mac you don't need to install the drivers it said that was windows only when I tried clicking it in the SDK manager. Weirdly enough last night when I first tried this it actually showed something connected. So I am not sure what happened between then and now.
Click to expand...
Click to collapse
Again, I'm sorry for my lack of knowledge with Mac.

Evolution_Freak said:
Again, I'm sorry for my lack of knowledge with Mac.
Click to expand...
Click to collapse
Oh no problem at all..I know your trying to help me. I shouldn't of been trying to do this and now I don't have a phone at all.

nickb2005 said:
On a mac you don't need to install the drivers it said that was windows only when I tried clicking it in the SDK manager. Weirdly enough last night when I first tried this it actually showed something connected. So I am not sure what happened between then and now.
Click to expand...
Click to collapse
Try this, power off your nexus and manually boot it to bootloader. Hold power down and press volume up. Once it boots to bootloader, connect to your computer.
---------- Post added at 08:05 AM ---------- Previous post was at 08:04 AM ----------
See if it is detected then and try the command: fastboot devices

Booting TWRP through fastboot doesn't work

Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is going wrong here!

Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.

ptn107 said:
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.
Click to expand...
Click to collapse
Thanks for your reply, the file sizes are correct, I tried these from twrp download page: twrp-3.2.3-1-payton.img (29.5M) and twrp-3.2.3-0-payton.img (25.9M) - same result.

Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?

gee one said:
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?
Click to expand...
Click to collapse
Will give this a try tomorrow, thanks a lot!
Edit: Still no luck. Tried it with linux mint and even there the same sh!t... wtf

Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?

Neffy27 said:
Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?
Click to expand...
Click to collapse
Latest drivers from Motorola Device Manager are installed and phone is properly recognized in device manager (used usb 2.0, 3.0 and 3.1 ports, nothing changes, same behavior). I tried it now with mfastboot but still nope..

Are you using minimal or full sdk (by Google) platform tools?

Neffy27 said:
Are you using minimal or full sdk (by Google) platform tools?
Click to expand...
Click to collapse
Minimal, I have also a Moto G5 and I don't face this kind of problems - only with Payton.

I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.

Neffy27 said:
I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.
Click to expand...
Click to collapse
Unfortunately still no progress with full sdk and latest platform-tools, I'm giving up (for now).. I don't get it man, I'm not able to do anything in bootloader... for example when I try "fastboot flash partition gpt.bin" it freezes at sending OR it throws instant failed, the bootloader log menu shows that something is downloading but nothing happens... I relocked the bootloader (locking and unlocking is no problem) again and I am going to use it for a while... otherwise I will do a mistake somewhere and will brick it... Thanks for taking the time to help me haha

I'm having this same exact issue, just got this phone (XT1900-1) for my wife and she wants a custom rom, my own phone booted into twrp no problem.

https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Maybe try the fastboot in that link. I read through the thread and no specific reason why they suggest that version but it allowed people to flash back to stock. I used it last week to go back to stock before Lineage.

No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.

Sorry, beyond my expertise. Maybe it's USB c port on the phone issue? Intermittently dropping the connection? Or have to tried flashing the 8.1 sick from the thread I posted? Maybe the factory ROM is messed up some how. I honestly don't know and those suggestions aren't based in any real knowledge.

Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?

Slayer5934 said:
No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.
Click to expand...
Click to collapse
Had exactly the same behavior like you (especially Edit 3), I tried it on a different computer from 2013 with usb 2.0 ports and it worked..
No other cable, no usb port, no adb and fastboot changes and no other drivers - just put all the stuff on a other computer and run the commands from there :good:
ptn107 said:
Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?
Click to expand...
Click to collapse
Yeah, I'm on 1:7.0.0+r33-2 too.. I guess it has something to do with my mainboard or usb controller, weird weird weird

A different pc solved the issue.. wtf.. thank you..

I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.

dirktacular said:
I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.
Click to expand...
Click to collapse
Yeah I wish we knew the exact problem and solution but you might just be stuck trying new computers for eternity sadly..