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
Related
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.
My bootloader is unlocked already, I deleted HTC Sync, debugging on, usb is in disk mode, etc. but for the life of me I can't get any recoveries to flash. I get the "Remote: not allowed" and if I try again it just gets stuck on sending recovery. It shows up as a fastboot device in cmd. Any suggestions?
Try the tool kit in development.
redmanjoey said:
My bootloader is unlocked already, I deleted HTC Sync, debugging on, usb is in disk mode, etc. but for the life of me I can't get any recoveries to flash. I get the "Remote: not allowed" and if I try again it just gets stuck on sending recovery. It shows up as a fastboot device in cmd. Any suggestions?
Click to expand...
Click to collapse
redmanjoey said:
My bootloader is unlocked already, I deleted HTC Sync, debugging on, usb is in disk mode, etc. but for the life of me I can't get any recoveries to flash. I get the "Remote: not allowed" and if I try again it just gets stuck on sending recovery. It shows up as a fastboot device in cmd. Any suggestions?
Click to expand...
Click to collapse
Are you in bootloader/fastbootusb?
BD619 said:
Are you in bootloader/fastbootusb?
Click to expand...
Click to collapse
Yes, I am in fastbootusb. The same thing happens on the toolkit. I doubt it is any kind of hardware defect, but the device is recognized in fastboot which is why I am SUPER confused. This is the first time I have ever run into an issue with fastboot.
redmanjoey said:
Yes, I am in fastbootusb. The same thing happens on the toolkit. I doubt it is any kind of hardware defect, but the device is recognized in fastboot which is why I am SUPER confused. This is the first time I have ever run into an issue with fastboot.
Click to expand...
Click to collapse
I initially had a bad download and had issues with both ways to flash. Redownloaded and it worked.
Also, with the tool I've had issues with usb switching from storage to media which affected even using adb to push files. Make sure that's not an issue with the push method.
Sent from M8 on XDA Premium APP
joshuaw84 said:
I initially had a bad download and had issues with both ways to flash. Redownloaded and it worked.
Also, with the tool I've had issues with usb switching from storage to media which affected even using adb to push files. Make sure that's not an issue with the push method.
Sent from M8 on XDA Premium APP
Click to expand...
Click to collapse
Are you implying the fastboot download was bad or the recovery? I tried three different recoveries now and none worked. I also tried using hassoon2000s method and just get an error saying device not found.
Also, I am using the fastboot file that came directly from HTC so I am really scratching my head right now...
redmanjoey said:
Also, I am using the fastboot file that came directly from HTC so I am really scratching my head right now...
Click to expand...
Click to collapse
It could be outdated.
Do you have android sdk on your PC?
If so make sure it's up to date.
If not get it HERE
redmanjoey said:
Are you implying the fastboot download was bad or the recovery? I tried three different recoveries now and none worked. I also tried using hassoon2000s method and just get an error saying device not found.
Click to expand...
Click to collapse
Just giving you my experience where there were a couple issues that made it seem like I was stuck. Take it or leave it I guess.
Sent from M8 on XDA Premium APP
joshuaw84 said:
Just giving you my experience where there were a couple issues that made it seem like I was stuck. Take it or leave it I guess.
Sent from M8 on XDA Premium APP
Click to expand...
Click to collapse
Sorry if I sounded mean or anything I was literally just asking which one you meant lol. I now realize "are you implying" does sound kinda snarky. Anyway, it must have been something with my computer because I did it on another computer and got it to work.
So the thread doesn't go to waste, if anyone is having issues try on another computer.
Okay, now trying to flash the stock recovery to get the phone exchanged for radio issues, I am running into the same problem. I tried both computers now. Hopefully I figure it out soon, had to activate an old blackberry for the time being.
"sending 'recovery' (16472 KB)...
FAILED (remote: not allowed)
finished. total time: 0.007s"
I have had the same problem before on a different phone. All you need to do is put it on the sd card and use the boot loader method. The phone will automatically find it and flash it. Then just remove sd card and delete file so it doesn't keep prompting to flash it every time you reboot.
{ParanoiA} said:
I have had the same problem before on a different phone. All you need to do is put it on the sd card and use the boot loader method. The phone will automatically find it and flash it. Then just remove sd card and delete file so it doesn't keep prompting to flash it every time you reboot.
Click to expand...
Click to collapse
To flash a recovery? Just rename the recovery as a radio file?
Yes. Go to http://forum.xda-developers.com/showthread.php?t=2696652 and all the info you need is there along with directions.
Alright so last night i was able to unlock my phone and root it no problem on my mac computer (which I regret and wish i did it on windows) but the phone worked great after. But after debating if I should unroot I went ahead and tried unrooting the phone but the phone would not activate, it became stuck in bootloader. Ive tried everything that I could look up online and even called google for help but they said to search online and ask the developers. Ive tried flashing the stock image back on but it wouldnt work, it kept saying ivalid boot image header fastboot reason fall-through from normal boot mode. I dont even think my computer is recognizing the phone anymore so I dont know how I would get back into terminal to flash anything. If anyone can help me I would appreciate it. I have no idea what to do now after trying for a whole day. Thanks all, hope someone can be a savior.
Firstly, if you want help... please please please use paragraphs and lines and not 1 blob of text. It makes it extremely difficult to know your problem.
Secondly, do not ever call Google or Motorola (or any manufacturer) or any carrier for help. What you do on XDA is not their problem, that is why there is a warning when you unlock the bootloader.
Third, if you're able to get into bootloader mode then you can fix your phone by flashing the stock images. You most likely had the wrong environment or it is not set up properly to flash the stock images.
If you don't feel comfortable doing this kind of stuff, stick to using the phone out of the box rather than tinkering with it.
zephiK said:
Firstly, if you want help... please please please use paragraphs and lines and not 1 blob of text. It makes it extremely difficult to know your problem.
Secondly, do not ever call Google or Motorola (or any manufacturer) or any carrier for help. What you do on XDA is not their problem, that is why there is a warning when you unlock the bootloader.
Third, if you're able to get into bootloader mode then you can fix your phone by flashing the stock images. You most likely had the wrong environment or it is not set up properly to flash the stock images.
If you don't feel comfortable doing this kind of stuff, stick to using the phone out of the box rather than tinkering with it.
Click to expand...
Click to collapse
Yea, my bad. I typed it in a hurry on my phone.
Bootloader is the only screen I am able to get into. Whatever option I choose and hit power, all it does is flash the screen and go back to bootloader.
The stock image I download was from the google developers page but it did not work.
Will anything even work if my computer doesn't recognize the phone? If so how would I go about doing it?
I used to this this years ago and never ran into problems, just for some reason when I tried to unroot it messed up.
Is there anyway to possibly delete the terminal so I could start over and re-root it??
Anyways thanks for your response.
Is the device recognized by the fastboot command when connected to either the mac or pc?
zylstrajs said:
Is the device recognized by the fastboot command when connected to either the mac or pc?
Click to expand...
Click to collapse
Not sure to be exact, if I just go into terminal and enter "adb devices" nothing will pop up but if I enter cd then space and drag the android file into it, it wont say my device number anymore it'll say device. I'm wondering if I could somehow delete my terminal and possibly start over?
dnasr87 said:
Not sure to be exact, if I just go into terminal and enter "adb devices" nothing will pop up but if I enter cd then space and drag the android file into it, it wont say my device number anymore it'll say device. I'm wondering if I could somehow delete my terminal and possibly start over?
Click to expand...
Click to collapse
Adb is for android. You want to use the command: fastboot devices
dnasr87 said:
Yea, my bad. I typed it in a hurry on my phone.
Bootloader is the only screen I am able to get into. Whatever option I choose and hit power, all it does is flash the screen and go back to bootloader.
The stock image I download was from the google developers page but it did not work.
Will anything even work if my computer doesn't recognize the phone? If so how would I go about doing it?
I used to this this years ago and never ran into problems, just for some reason when I tried to unroot it messed up.
Is there anyway to possibly delete the terminal so I could start over and re-root it??
Anyways thanks for your response.
Click to expand...
Click to collapse
If you want to start over you'd want to be flashing the stock images https://developers.google.com/android/nexus/images
Have your phone in bootloader mode (vol down + power)
Go into the directory with fastboot and type fastboot devices.
If your environment is set up properly then it should display your device as the output. From there you can flash back to stock.
dnasr87 said:
Not sure to be exact, if I just go into terminal and enter "adb devices" nothing will pop up but if I enter cd then space and drag the android file into it, it wont say my device number anymore it'll say device. I'm wondering if I could somehow delete my terminal and possibly start over?
Click to expand...
Click to collapse
what does it say why you type
>fastboot devices
zylstrajs said:
what does it say why you type
>fastboot devices
Click to expand...
Click to collapse
command not found, but all I did was open terminal and entered fastboot devices. Not sure if I should enter anything before it.
dnasr87 said:
command not found, but all I did was open terminal and entered fastboot devices. Not sure if I should enter anything before it.
Click to expand...
Click to collapse
You have to change directory to the folder that contains fastboot. Do you even have fastboot environment set up? You need that.
Google search on how to set it up before posting back. There are many guides on XDA on how to accomplish this.
Okay, your environment isn't set up ideally. Follow these instructions to install fastboot and adb on your PC.
http://forum.xda-developers.com/showthread.php?t=2317790
---
Once you've done and you get a reply to the following command, you can move on.
>fastboot devices
---
open the google factory image file (using something like 7zip) : shamu-lrx21o-factory-e028f5ea.tgz
There is a folder in the .tgz file. Extract the contents of that folder to the directory listed for your command prompt (where you successfully ran fastboot just before).
> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
>fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
>fastboot reboot-bootloader
---
The device will reboot. Don't close the terminal window. Now, extract the contents of image-shamu-lrx21o.zip to the same folder that you've been working in. The folder that contains the bootloader and radio files you just flashed.
---
>fastboot flash recovery recovery.img
>fastboot flash boot boot.img
>fastboot flash system system.img
Some time will pass, this img may be sent in parts.
>fastboot flash cache cache.img
>fastboot flash userdata userdata.img
>fastboot reboot
zephiK said:
You have to change directory to the folder that contains fastboot. Do you even have fastboot environment set up? You need that.
Google search on how to set it up before posting back. There are many guides on XDA on how to accomplish this.
Click to expand...
Click to collapse
I did when I rooted it then once it crashed I tried to start over but wiped my computer.. I'll re download and try again
zylstrajs said:
Okay, your environment isn't set up ideally. Follow these instructions to install fastboot and adb on your PC.
http://forum.xda-developers.com/showthread.php?t=2317790
---
Once you've done and you get a reply to the following command, you can move on.
>fastboot devices
---
open the google factory image file (using something like 7zip) : shamu-lrx21o-factory-e028f5ea.tgz
There is a folder in the .tgz file. Extract the contents of that folder to the directory listed for your command prompt (where you successfully ran fastboot just before).
> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
>fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
>fastboot reboot-bootloader
---
The device will reboot. Don't close the terminal window. Now, extract the contents of image-shamu-lrx21o.zip to the same folder that you've been working in. The folder that contains the bootloader and radio files you just flashed.
---
>fastboot flash recovery recovery.img
>fastboot flash boot boot.img
>fastboot flash system system.img
Some time will pass, this img may be sent in parts.
>fastboot flash cache cache.img
>fastboot flash userdata userdata.img
>fastboot reboot
Click to expand...
Click to collapse
I did it on my mac, if i try to connect my phone to a pc it wont recognize it because its stuck in bootloader. I have already tried connecting it
Why does this thread make me LoL so much?
This thread is all over the place. Are you using your PC or Mac right now to do this? If it is a PC, what does Device Manager say when you plug your phone in while its in Bootloader mode?
PaisanNYC said:
Why does this thread make me LoL so much?
This thread is all over the place. Are you using your PC or Mac right now to do this? If it is a PC, what does Device Manager say when you plug your phone in while its in Bootloader mode?
Click to expand...
Click to collapse
Im using mac right now. I want to start from scratch, not sure if possible. but nothing really shows when I connect the device. I think I wipe the software off my computer. Would I be able to start doing it all over on a pc even if its stuck on bootloader and computer wont recognize?
dnasr87 said:
Im using mac right now. I want to start from scratch, not sure if possible. but nothing really shows when I connect the device. I think I wipe the software off my computer. Would I be able to start doing it all over on a pc even if its stuck on bootloader and computer wont recognize?
Click to expand...
Click to collapse
Are you in the NYC area? I'd just come over with my laptop and do it for you.
PaisanNYC said:
Are you in the NYC area? I'd just come over with my laptop and do it for you.
Click to expand...
Click to collapse
Dude im in NH but at this point I will ship the phone to anyone who can fix it and I will pay you guys $100
PaisanNYC said:
Are you in the NYC area? I'd just come over with my laptop and do it for you.
Click to expand...
Click to collapse
dnasr87 said:
Dude im in NH but at this point I will ship the phone to anyone who can fix it and I will pay you guys $100
Click to expand...
Click to collapse
not necessary some one can just use hangouts remote desktop to help you i thinks that's what they use on xda assist
Acer ADB
Your PC might not be recognizing because you got the Acer ADB of doom...
Just roll back your driver.
dnasr87 said:
Dude im in NH but at this point I will ship the phone to anyone who can fix it and I will pay you guys $100
Click to expand...
Click to collapse
Don't send it to a stranger on the internet. You never know who is who behind a screen lol
Honestly bro, if i were close to you, I'd just do it for you. I have the stock image, drivers, and adb/fastboot all set up. i'm good at fixing things, horrible at explaining things.
I just bought a Nexus 6... Unlocked the bootloader and rooted the phone.... after realizing there were some issues with the phone I decided I would try and download the PURE rom for the phone... I installed TWRP recovery and tried to flash the image. When the phone booted back up it said that the data was corrupt, and to enter a password. Entering anything seemed to work and I would then reset the phone... but the same thing would come back up.
So I decided to try and wipe the phone again and re-install the ROM... after that it wouldn't load at all, came back with some kind of error.
Then I decided to do a full wipe of the phone and try and re-install the factory image... Problem is... I haven't tried to do anything with a phone in like 2 years and well... i'm having trouble on trying to figure out how I can restore the factory image. I have the SDK tools installed, the phone drivers are also obviously installed, but can someone help me try to reset to the factory image.
I only have like 3 hours to try and accomplish this from now because after this I have to get on a plane and won't be around and will also leave me without a phone... Can someone please help me as soon as possible? Thank you so much!! I could use somewhat detailed instructions but not crazy
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Try nexus toolkit by wugfresh can't go wrong. If you get error missing system.img while flashing go to options then flash then click force flash. The toolkit will download all needed steps and flash without a problem
dont use a toolkit. you are guaranteed to learn nothing, and doing it the right way is just as fast(and easy). plus, root toolkits mess up often. dong it right never messes anything up.
Nexus device can almost never be bricked, I say almost never because of the people variable, but if you can get it into bootloader mode it is easy to bring back. just follow the instructions above.
I agree that even though wugfresh tools is the best out there. I have used it before. You learn nothing about what needs to be completed.
I could never get the drivers to work for me in most cases. I use ubuntu and it always works running the manual commands.
Ok so I have tried to run the flash-all.bat file and it says in the command prompt it is an unrecognized command...
I'm assuming I must be missing part of the ADB tools? Ugh help!
jwleonhart said:
Ok so I have tried to run the flash-all.bat file and it says in the command prompt it is an unrecognized command...
I'm assuming I must be missing part of the ADB tools? Ugh help!
Click to expand...
Click to collapse
first thing to do in adb is run the command "adb devices" to make sure that adb sees your device, does adb see your device?
It says list of devices attached and then nothing....
Can someone give me a short step by step on what I need to do here? I'm really running low on time, this is really bad....
jwleonhart said:
It says list of devices attached and then nothing....
Can someone give me a short step by step on what I need to do here? I'm really running low on time, this is really bad....
Click to expand...
Click to collapse
wait.. you are flashing the factory img, you do not use adb for that. you boot into the bootloader then use fastboot for that. adb doesnt work in the bootloader anyways, use fastboot while youre in the bootloader, and type fastboot devices to make sure fastboot sees your device.
@simms22 is correct, tool kits make you learn nothing, and you get posts like this.
However if you are time contained. As much as it pains me to say this. Use the tool kit. And learn on a time when you can.
Download Wugs toolskit and flash back to stock images. And you'll be fine.
Update your SDK if u haven't already.
Unzip factory images and place in platform tools folder of SDK. (Unless you have environmental variables set correctly)
Open a command prompt from that directory (place cursor in empty space, hold shift and right click on mouse)
Boot into bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Sent from my Nexus 6
simms22 said:
dont use a toolkit. you are guaranteed to learn nothing, and doing it the right way is just as fast(and easy). plus, root toolkits mess up often. dong it right never messes anything up.
Click to expand...
Click to collapse
Different strokes for different folks!!!!
Sent from my SM-T310 using XDA Premium 4 mobile app
doing the following command in command prompt:
fastboot devices
it shows the following device:
ZX1G2224G5
I'm assuming that is the nexus 6...
So whats next on the list then?
I unzipped the factory image and using the flash-all.bat script it says fastboot is not a recognied command.
dparrothead1 said:
Different strokes for different folks!!!!
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
not really.
if you know anything about what you are doing, its one thing, use a toolkit, enjoy yourself. if you have no idea what you are doing, the root toolkit is by far the wrong way to go. as you will still know absolutely nothing, and will learn nothing. and pretty soon, when you have some simple maintenance to do, and you have no idea how, you start thread about having your device bricked. and im sure that you personally have not helped out hundreds that have started threads about having their device "bricked" after using a root toolkit. i have.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
jwleonhart said:
doing the following command in command prompt:
fastboot devices
it shows the following device:
ZX1G2224G5
I'm assuming that is the nexus 6...
So whats next on the list then?
I unzipped the factory image and using the flash-all.bat script it says fastboot is not a recognied command.
Click to expand...
Click to collapse
you probably have to unzip it twice, if there is another zip within that one zip. and you can try not using the word fastboot, as i also have ran into fastboot programs where it wasnt needed.
simms22 said:
not really.
if you know anything about what you are doing, its one thing, use a toolkit, enjoy yourself. if you have no idea what you are doing, the root toolkit is by far the wrong way to go. as you will still know absolutely nothing, and will learn nothing. and pretty soon, when you have some simple maintenance to do, and you have no idea how, you start thread about having your device bricked. and im sure that you personally have not helped out hundreds that have started threads about having their device "bricked" after using a root toolkit. i have.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
you probably have to unzip it twice, if there is another zip within that one zip. and you can try not using the word fastboot, as i also have ran into fastboot programs where it wasnt needed.
Click to expand...
Click to collapse
Friend, I'm way too old to get into an internet pissing contest!!! I realize I don't have 27,000+ post, but if you look at my thanks total, you will see that I've helped my share of members!!!! So don't tell me that I dont try to share my knowledge......have a good day and please don't respond to any more of my post!!!! Peace out!!
Sent from my SM-T310 using XDA Premium 4 mobile app
dparrothead1 said:
Friend, I'm way too old to get into an internet pissing contest!!! I realize I don't have 27,000+ post, but if you look at my thanks total, you will see that I've helped my share of members!!!! So don't tell me that I dont try to share my knowledge......have a good day and please don't respond to any more of my post!!!! Peace out!!
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
with a silly post like "Different strokes for different folks!!!!" you definitely arent posting like someone your age, as thats what a child would say. im not young myself. anywho, you can not tell me not to respond, lol. ill respond to anyone who posts as silly as you. i have nothing against you, nor are trying to get at you, im simply responding to your silliness.
OP... The password was a numerical representation of your pattern unlock since you were still encrypted. The key is in the first post of the TWRP thread.
Now...extract the factory image until you have boot.img radio.img system.img and recovery.img if there is a bootloader img flash that first.
Flash bootloader with fastboot flash bootloader bootloader.img
Reboot with fastboot reboot-bootloader
Flash boot system and radio respectively with fastboot flash boot/radio/system boot.img/radio.img/system.img one at a time.
Finish with fastboot reboot and you sgould be all set.
op got it flashed, and ended up flashing his rom as well. so, he was successful
I hope saying use a toolkit didn't start an argument, only said to use it because he had a time restraint..
jiv101 said:
I hope saying use a toolkit didn't start an argument, only said to use it because he had a time restraint..
Click to expand...
Click to collapse
no, it didnt start an argument. but he ended up doing it the right way, then flashed his rom. then flashed a different rom because his rom was so so. but really, even if theres a time restraint, if your driver is installed properly, it takes about 3-4 minutes to flash the boot.img
Purchased used moto g6 (xt1925-6) US unlocked version (that's what the rom says).
I'm a total noob with roms and recovery and so on. I'm hoping someone will tell me the steps briefly and I'll try to look up the detailed steps and try to restore the phone to factory settings.
Here is the situation at hand:
-Phone has twrp recovery (I need to restore the factory recovery. Weird thing is can't seem to find the file to download).
-Has bootloader unlocked (I would prefer to relock it). Not rooted.
-Rom says its the unlocked version (don't know if the phone was actually a different version or not). It receives notification and downloads ota updates but can't install updates.
-Phone was purchased used and it was a hobby fixer project for me. Now I would like to sort out the android end and get rid of it as long as its in perfect condition.
Thanks for helping out with the steps to achieve factory settings. Also, if there is a chance that the phone might have been a different version and it has flashed unlocked rom or something, what would it mean? Can it be restored to factory settings of the unlocked version? Are there any catches to it?
EDIT: I think I have mistakenly used the phrase recovery. The issue in that respect is twrp and I need to remove it and restore default mode so that its back to factory settings.
e4noob said:
Purchased used moto g6 (xt1925-6) US unlocked version (that's what the rom says).
I'm a total noob with roms and recovery and so on. I'm hoping someone will tell me the steps briefly and I'll try to look up the detailed steps and try to restore the phone to factory settings.
Here is the situation at hand:
-Phone has twrp recovery (I need to restore the factory recovery. Weird thing is can't seem to find the file to download).
-Has bootloader unlocked (I would prefer to relock it). Not rooted.
-Rom says its the unlocked version (don't know if the phone was actually a different version or not). It receives notification and downloads ota updates but can't install updates.
-Phone was purchased used and it was a hobby fixer project for me. Now I would like to sort out the android end and get rid of it as long as its in perfect condition.
Thanks for helping out with the steps to achieve factory settings. Also, if there is a chance that the phone might have been a different version and it has flashed unlocked rom or something, what would it mean? Can it be restored to factory settings of the unlocked version? Are there any catches to it?
EDIT: I think I have mistakenly used the phrase recovery. The issue in that respect is twrp and I need to remove it and restore default mode so that its back to factory settings.
Click to expand...
Click to collapse
Get the stock firmware from here and flash all of the partitions with either fastboot (commands are in the XML) or use RSDlite. Easy peasy
---------- Post added at 02:43 AM ---------- Previous post was at 02:39 AM ----------
Get RSDlite 6.2.4 from here
Or rsd light XML to batch to make a .bat file for fastboot.
If your using RSDlite and wiping data, select flashfile, if keeping data use servicefile.
madbat99 said:
Get the stock firmware from here and flash all of the partitions with either fastboot (commands are in the XML) or use RSDlite. Easy peasy
---------- Post added at 02:43 AM ---------- Previous post was at 02:39 AM ----------
Get RSDlite 6.2.4 from here
Or rsd light XML to batch to make a .bat file for fastboot.
If your using RSDlite and wiping data, select flashfile, if keeping data use servicefile.
Click to expand...
Click to collapse
Hey man, thanks for the quick steps. Feels like it'll take days to decipher the steps. But I'm on it.
e4noob said:
Hey man, thanks for the quick steps. Feels like it'll take days to decipher the steps. But I'm on it.
Click to expand...
Click to collapse
It really doesn't.
Install RSDlite on your PC.
Download the full firmware package.
Put phone in fastboot mode. Plug into PC. Open RSDlite.
Navigate to the firmware package.
RSDlite will extract it and everything.
RSDlite will ask either flashfile or servicefile
Flashfile wipes data, servicefile does not
Install (flash) package.
Done
Root if you want. Instructions are in the forum
Good luck!
madbat99 said:
It really doesn't.
Install RSDlite on your PC.
Download the full firmware package.
Put phone in fastboot mode. Plug into PC. Open RSDlite.
Navigate to the firmware package.
RSDlite will extract it and everything.
RSDlite will ask either flashfile or servicefile
Flashfile wipes data, servicefile does not
Install (flash) package.
Done
Root if you want. Instructions are in the forum
Good luck!
Click to expand...
Click to collapse
Thanks. That helps a lot.
e4noob said:
Thanks. That helps a lot.
Click to expand...
Click to collapse
Good luck!
madbat99 said:
Good luck!
Click to expand...
Click to collapse
Again, appreciate the help a lot.
So I just tried it out and rsd lite doesn't see the device. Phone has debugging enabled. I browsed around for solutions and followed some common steps. I checked with minimal adb fastboot command 'fastboot devices" and the phone's serial number pops up. Phone is detected by pc (win10) device manager when on fastboot mode. I have installed motorola device manager as well. But so far rsd lite doesn't see the device. Any ideas?
madbat99 said:
Good luck!
Click to expand...
Click to collapse
Hey man, any idea what might be the issue?
I just tried it out and rsd lite doesn't see the device. Phone has debugging enabled. I browsed around for solutions and followed some common steps. I checked with minimal adb fastboot command 'fastboot devices" and the phone's serial number pops up. Phone is detected by pc (win10) device manager when on fastboot mode. I have installed motorola device manager as well. But so far rsd lite doesn't see the device. Any ideas? I prefer to use rsd lite method for obvious reasons.
(Posting this question a second time. Hope I don't get banned or anything )
e4noob said:
Hey man, any idea what might be the issue?
I just tried it out and rsd lite doesn't see the device. Phone has debugging enabled. I browsed around for solutions and followed some common steps. I checked with minimal adb fastboot command 'fastboot devices" and the phone's serial number pops up. Phone is detected by pc (win10) device manager when on fastboot mode. I have installed motorola device manager as well. But so far rsd lite doesn't see the device. Any ideas? I prefer to use rsd lite method for obvious reasons.
(Posting this question a second time. Hope I don't get banned or anything )
Click to expand...
Click to collapse
Not sure on that. Did you get the RSDlite that I linked to? Some versions dont recognize device with Windows 10. But the version I linked works for me. In RSDlite, the imei shows n/a but it does show a fastboot device connected.
You have the phone in fastboot mode when connecting?
On that same page I linked, there is an XML to batch program as well. You can turn the XML file from the firmware package into a .bat file. Then you just have to run the .bat file and will run all of the fastboot commands for you (which is what RSDlite does with the XML file)
May be an option if you can't get RSDlite to recognize, but fastboot does.
madbat99 said:
Not sure on that. Did you get the RSDlite that I linked to? Some versions dont recognize device with Windows 10. But the version I linked works for me. In RSDlite, the imei shows n/a but it does show a fastboot device connected.
You have the phone in fastboot mode when connecting?
On that same page I linked, there is an XML to batch program as well. You can turn the XML file from the firmware package into a .bat file. Then you just have to run the .bat file and will run all of the fastboot commands for you (which is what RSDlite does with the XML file)
May be an option if you can't get RSDlite to recognize, but fastboot does.
Click to expand...
Click to collapse
Yes the same version. I have it on fastboot when connecting (also tried normal bootup and pc recognizes phone just fine). Good to know there is the bat file option for last resort. I'll try installing android sdk and may be it'll solve this driver issue. So I'll have to ask you for the steps to make the the bat file and how to make it work.
You could have also tried Lenovo Moto Smart Assistant. I've used it and it works pretty well.
Ragarianok said:
You could have also tried Lenovo Moto Smart Assistant. I've used it and it works pretty well.
Click to expand...
Click to collapse
What does it do and how do you use it?
e4noob said:
What does it do and how do you use it?
Click to expand...
Click to collapse
It has a Rescue function that returns the phone to stock firmware.
Here's the link if you want to try it:
https://support.lenovo.com/us/en/downloads/ds101291
It's fairly intuitive.
Ragarianok said:
It has a Rescue function that returns the phone to stock firmware.
Here's the link if you want to try it:
https://support.lenovo.com/us/en/downloads/ds101291
It's fairly intuitive.
Click to expand...
Click to collapse
I'm gonna try it out if it works for moto g6. Thanks, man.
Ragarianok said:
It has a Rescue function that returns the phone to stock firmware.
Here's the link if you want to try it:
https://support.lenovo.com/us/en/downloads/ds101291
It's fairly intuitive.
Click to expand...
Click to collapse
Hey man, its very intuitive. It worked in first try and phone is back to stock with stock recovery. Only issue I have is bootloader is unlocked. Should I use minimal adb fastboot to perform a relock command? Are there any other steps to it or just the command?
e4noob said:
Hey man, its very intuitive. It worked in first try and phone is back to stock with stock recovery. Only issue I have is bootloader is unlocked. Should I use minimal adb fastboot to perform a relock command? Are there any other steps to it or just the command?
Click to expand...
Click to collapse
You should be able to run "fastboot oem lock" to re-lock the bootloader.
You may get an error message though; something like "flash signed images" or something like that. Let me know if that happens.
Ragarianok said:
You should be able to run "fastboot oem lock" to re-lock the bootloader.
You may get an error message though; something like "flash signed images" or something like that. Let me know if that happens.
Click to expand...
Click to collapse
I'm getting a warning message that it erases all user data and instructing to rerun command to continue. Should I proceed?
e4noob said:
I'm getting a warning message that it erases all user data and instructing to rerun command to continue. Should I proceed?
Click to expand...
Click to collapse
Yup! That's completely normal.
e4noob said:
I'm getting a warning message that it erases all user data and instructing to rerun command to continue. Should I proceed?
Click to expand...
Click to collapse
Do you really need it locked?
Ragarianok said:
Yup! That's completely normal.
Click to expand...
Click to collapse
I'm getting this message.
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.010s]
finished. total time: 0.011s