[Q] Deleted OS need help to push files to device - Nexus 5 Q&A, Help & Troubleshooting

I see that there are other threads for this and I have read through them but they don't seem to be helping. I was in the middle of using the Nexus Toolkit to install a Rom when the program temporarily booted TWRP after it removed old os and then it stopped working and I went to reboot from the temporary boot when it told me I had no OS. Because I do not have a ROM my computer does not detect ADB status so I cannot seem to get anytging on the device. I also can seem to get the sideload to work. I am not quite sure how to use the CMD for this and I have used other threads suggestions like starting cmd in the folder that has the rom i want to flash and the typing the adb commands but it doesn't seem to work. Can someone help please?

STOP USING TOOLKITS!
If you can't get adb to work, I suggest following this thread to get it working: http://forum.xda-developers.com/showthread.php?t=2588979

Thank you, but my adb drivers are installed. my device can only enter fastboot and recovery so even now with that tool I dont know how to install an os back on my device.

Just flash the images from fastboot. There are a thousand posts on how to do this here.
"fastboot flash system system.img"

Related

No boot or recovery img

last night i flashed an update of clockwork mod through rom manager. i then went to do a back-up of my current rom. the phone re-booted to the fastboot mode and now says no boot or recovery img. when i scroll to recovery and click it, the phone reboots right back into the bootloader. i am trying to flash a new recovery through adb but i cant get anything to connect. when i do "adb devices" in the command prompt i get the daemon started and list of devices but there are no devices listed. "fastboot devices" does nothing either. i have the android sdk loaded onto c:\ and the drivers seem to be installed correctly. when i rooted the phone i used a different pc that i dont have access to now. i also used pdanet for the drivers so i have never had the google drivers set up correctly. i type fastboot flash recovery recovery.img and it says "cannot load recovery.img" i have downloaded the recovery-clockwork3.0.0.5-crespo.img to the "tools" folder and renamed it "recovery.img"
i have tried to explain everything i have done so far but i am sure there are some steps i have missed. i read some on odin and downloaded it but i am even more lost trying to figure that out. i really need some help here and i would appreciate anything i can get
when you're in bootloader, you're supposed to use "fastboot"
you cant flash a recovery using adb.
go into bootloader mode
fastboot devices
... if your device doesn't show up, then your drivers are not properly set up.. uninstall them and look for the sticky and reinstall your drivers using those set of instructions; assure your SDK is updated to support 2.3.X
when you get your device to appear in fastboot devices.
download clockwork recovery 3.0.2.5 (3.0.2.4 is buggy) or 3.0.0.5; 3.0.2.5 is found in dev forums; rename it to recovery.img
put it in /sdk/tools/
fastboot flash recovery recovery.img
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
tohg2 said:
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
Click to expand...
Click to collapse
if your device is unable to GET into bootloader mode... that wont get you anywhere.
when you plug your phone into the computer with the USB.. does that USB sound pop up? if it doesnt.. then its bricked.
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
when i plug the usb in i dont hear a sound. the phone will only boot into "fastboot mode".
when i do fast boot devices i see "38328e03afbf00ec fastboot"
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
bootloader mode is for fastboot. you wont be using ADB to recover your device.
you unzip the file. it should be like: clockwork-recovery-version..blah blah blah.img
rename it to "recovery.img" assure that your "fastboot" appears as "fastboot.exe" and not just "fastboot." if it is "fastboot" you need to go into folder options and show extensions otherwise you'll be trying to flash "recovery.img.img" and SDK wont recognize it
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
Make sure you are typing the full file path, for example on my setup its "fastboot flash recovery c:\android\tools\recovery.img"
Sent from my Nexus S using XDA App
file extensions are being shown and it is named recovery.img. still saying cannot load "recovery.img" i have tried several recovery downloads from different sources. as for file size of the img its 3,988kb sound right? i tried fastboot oem lock and unlock and everything worked fine. is there another recovery img i can try. maybe a stock recovery or somehting?
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
tohg2 said:
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
Click to expand...
Click to collapse
cd C:\program files (x86)\android-sdk\tools\
fastboot flash recovery recovery.img
is what you want to do.
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
tohg2 said:
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
Click to expand...
Click to collapse
Odin is last resort. If fastboot devices shows your phone you will be able to flash recovery. Reinstall phone drivers and get fastboot to work. Then get back to trying to flash recovery. I really think it is some small mistake. Did you exctract the zip of recovery and copy the .img file?
The error you were getting means the appropriate file was not found in the file path you specified, so its not a phone error.
Sent from my Nexus S using XDA App
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
tohg2 said:
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
Click to expand...
Click to collapse
Cool! Glad you got it, good job!
Sent from my Nexus S using XDA App
Please help, I'm having the exact the same problem
I know, I shouldn't have play around with my phone since I don't know much about rooting the device.
My phone booted into Andriod logo with an unlocked, I have successful downloaded
clockwork recovery 3.0.2.5 and rename it to recover.img
I ran following command
fastboot flash recovery recovery.img and it was successful..
I tired to reboot my phone after that as normal but I'm still getting the same screen which only showing the Android Logo with an unlocked lock.
I'm not sure what I am suppose to do after need to get my phone to work again, any help would be appreciated.
Thank you,

Wiped OS, ADB not working, verge of tears

I am new to this (clearly heh) and wanted to put CM12 on my OPO, as it just arrived today and CM11 is a bit dated.
So after 101 issues I got TWRP installed, great!
However I messed it up by wiping my OS off the phone, leaving me with just access to TWRP and nothing else.
I was reading about ADB, but I cannot get the ADB sideload to start on my phone (it just hangs...).
ADB also does not detect my phone when I do an ADB push.
Any help is appreciated :'(
Acrylicus said:
I am new to this (clearly heh) and wanted to put CM12 on my OPO, as it just arrived today and CM11 is a bit dated.
So after 101 issues I got TWRP installed, great!
However I messed it up by wiping my OS off the phone, leaving me with just access to TWRP and nothing else.
I was reading about ADB, but I cannot get the ADB sideload to start on my phone (it just hangs...).
ADB also does not detect my phone when I do an ADB push.
Any help is appreciated :'(
Click to expand...
Click to collapse
If you are able to get into TWRP then this link http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471 will surely help you
- Install your device drivers first (If they are installed properly, then only skip this)
- Once adb and fastboot files are loaded on your computer, open command prompt and type command "fastboot devices". If you see your device serial number on the prompt, you are good to proceed ahead with flashing procedure.
- I recommend you to flash fastboot images of CMOS12 using that link.

Flashed stock recovery and thought I soft bricked my shield tablet.

First I'll give credit where it is due. From two threads on this site is where I got help with this issue:
I followed THIS guys steps for manually erasing and got the recovery images and lots of other useful information from HERE. Thank you guys very much!
OK, so, hopefully I can help someone with my little story as well. I was having issues with apps and programs crashing on me with lollipop and the new marshmallow update. The tablet just wasn't working properly and moving slow. I even had the SD card holding all my apps and larger files so I didn't overload the internal storage. So, I decided I wanted to flash back to factory/stock recovery and go from there. I did this using THIS method. I flashed via the "flash-all.bat" file (the command in fastboot is the same as the file name). I should note that there was one instance that failed during the install (I did try it again and got the same failure). Said something about “did you mean you wanted to flash this partition” or something, then showed it failed. After flashing I hit continue on the bootloader screen of the tablet and it said it was "cold booting." After about 5 minutes or so it started to boot but never made it past the NVidia screen. I tried wiping the phone with factory reset, wiping the cache, etc. and then re-flashing the recovery (again with the .bat file). I tried flashing TWRP but it didn't install apparently, because it still went to factory recovery. I even re-locked and then unlocked my bootloader to see if that would set everything straight. Nothing seemed to work. I knew I would eventually find a solution though so I kept looking. Stumbled on some other people that had the same issues but no solution (hope those people got it figured out). So here's what I did after some more research:
First, if you're in this situation and you did factory reset to try and resolve the problem, you may feel like you can no longer communicate with the device via fastboot/adb, but as long as you have the usb drive and your SDK tools installed (I used CodeWorks for Android all-in-one program) that shouldn't be a problem. You'll just have to be in the bootloader on the tablet.
-If for some reason you deleted or uninstalled your drivers and tools you'll have to download them again and then, the computer should still be able to communicate with the tablet. In the device manager under portable devices it will still show up as Module something or other. So the computer still sees the device but doesn't fully recognize it yet. Don't worry, this should still work! Just make sure you that fastboot is seeing the device by inputting "fastboot devices" in the command window and a 14 digit serial number should pop up. If it just says "list of devices" or there's nothing then you wont be communicating with the tablet.
Your device should be connected to your computer and started in bootloader mode. On your computer you should have the command prompt for adb/fastboot open. I just go to the folder where the .exe files are located and hold shift and right click in the white space of the folder, then select "open command window here."
From here follow the erase steps: stolen from manigault! :highfive:
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
Then flash your recovery MANUALLY:
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
You can download whatever recovery version you wish. I downloaded 2.2.2 because that's what my device came with out of the box on Christmas 2014. It will more then likely be a .zip file. To make this whole process a little easier simply extract the files in the .zip file where the adb.exe and fastboot.exe files are located (folder should be named platform-tools) and you can completely eliminate typing the whole directory before the file name. ***After your done flashing everything you can go back and delete those files if you want. Just double check that you're deleting the right files by looking at the original zip file. Not sure if it makes a difference but I deleted them anyway.
For example the commands in fastboot will look like this exactly :
(after extracting recovery files into platform-tools folder)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Note: Do NOT use the flash-all.bat command as this doesn't seem to work for this situation. Do it manually like shown above. And let each individual process complete before attempting to input another command.
After this step I didn't select continue on the bootloader. You can either select reboot or simply input "fastboot reboot" into the command window. It may take about 5 minutes to start installing everything but just be patient, it should start. Sometimes with these things you have to do things twice before it works. If for some reason it doesn't work the first time then start from the beginning and try it again. It took two times for me, but that's because I installed system.img twice and was getting double screen. Newb error... and I was a bit inebriated last night when I did this.
Hope this helps someone!
Thanks again to manigault and MidgetMob!
NVIDIA download files HERE!
i think i done the same thing
but the problem i now have is i cnt get tablet into fastboot on pc. i can load fastboot on tablet with power and volume down , but the tablet only shows as MTP device in device manager. i have downloaded drivers from nvidia and no matter what i try i cant install them i have been through all instructions but scince it went to mtp device i cant get device showing in adb. The only way i can get device showing in adb on pc ist to select apply update from adb ! but none of these commands listed in your post will work because its in sideload. is there anyway i cn reset , flash custom rom ect bu using commands while device is in adb sideload.
all i get is now send the package you want to apply to the device with "adb sideload <filename>".....
if you could shed any light on this it would be much appreciated , thanks , lester
did you update official android 6.0 before? then, not working stock recovery, stock boot...
If you can enter bootloader mode, download unofficial twrp 3.0.0.0 (here http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117) and flash it.
i have a working boot.img file on marshmallow if you want.. please reply.
Sorry for the late response! I have no clue how you got into sideload??? Are you talking about through the recovery on your device? You're not able to get adb/ fastboot to recognize the device, right? It doesn't matter how you get the tablet into the bootloader. Whenever you have the phone in the bootloader then you'll use the fastboot command to "talk to" the device; i.e. "fastboot devices" without the quotes. That command should show your device if it shows as an MTP device whenever you open your "device manager" in windows. That's the same exact situation I was in. Download the codeworks from nvidia like I linked above. Hopefully then you should be able to recognize your device through the bootloader. If not DM me and I'll try to help you.
I'm having the exact problem as Lester. Tablet boots into bootloader but won't connect to computer. So I go into recovery mode and nothing works except apply update from adb. Which brings up the side load message that Lester quoted. And bootloader is showing "device=locked". I am attempting to fix this tablet for a friend that messed it up trying to flash a custom rom. Problem is he had no idea what he was doing and I'm not exactly sure what he did. I do however have a lot of experience with rooted android devices and flashing so any help would be GREATLY APPRECIATED!
---------- Post added at 05:59 PM ---------- Previous post was at 05:55 PM ----------
Also, I've already tried flashing stock rom back onto the tablet by applying update from sd card function in the recovery but when I try to do that the tablet for some reason can't mount the sd card.
rom fiend said:
Tablet boots into bootloader but won't connect to computer.
Click to expand...
Click to collapse
If you've got the device in bootloader then you need to use fastboot, not adb. Try the command 'fastboot devices' and see if the device id is listed. If so then grab a factory image, unzip it and use fastboot to flash the .img files using the commands 'fastboot flash system system.img'. Just make sure to match the partition names to the files.
Hello i have similar issue except when i try flash something i get this error ''remote: file write failed''
and i have to reboot into fastboot to get it flashing fully
but even though i managed to flash everything by rebooting when i boot system nothing shows up, i can just see the back light coming on and turning off after a while
Please help

Can I still install any recovery(CWM or TWRP) after I have forgotten my password?

My question is: Is there any way that i can install any custom recovery now, when I am locked out of my phone, so I can try Method 7 from this post . I have enabled USB debugging, but for some reason, my device is unauthorized from executing adb commands.
I have Xiaomi Redmi Note 3, and have forgotten its password. I have tried Method 2, 5 and 6 from this post, but to no avail.
I tried method 2 and 5 which requires ADB to be installed, but I was not able to access my phone. I have USB debugging enabled and my phone is not rooted. When I tried to run the following code:
Code:
adb devices
adb shell
it showed that my phone is unauthorized and error: device unauthorized This adb server's $ADB_VENDOR_KEYS is not set
Here's the screenshot:
When trying method 6, I had to change the path of ADB driver because the file I downloaded from the post, had its own ADB driver which clashed with my already installed ADB driver, but even after that, it again showed the above error. Here' the screenshot:
Finally I want to try method 7 from the above post, which requires custom recovery to be installed on the phone, is there any way now?
Though it seems now that the I have only one option left and that is to factory reset my phone, but if , there is any other way by which I can bypass my lock screen, please please please inform me.
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
joe2k01 said:
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Didn't know that such package existed... I'd still do it my way if your phone was laggy/corrupted,... Else do the package flash. Keep me updated!
Sent from Lenovo a6000 1GB version.
Thanks! a lot, could you please guide me a little bit, how should I proceed?
MGlolenstine said:
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
dost25 said:
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
Click to expand...
Click to collapse
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Ok i will try
MGlolenstine said:
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Can unlocking my bootloader somehow brick my phone?
Everything can brick your phone. Updating my lenovo phone with official update hardbricked mine... But yeah, it can.

No OS... TWRP won't display files on otg/sd

I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
emmpii said:
I had a bit of a problem with CM and it kept saying trebuchet had stopped working. (This is after the phone had been running fine for a whole year with CM. Then the phone kept restarting and saying trebuchet had stopped working and it would constantly restart until it calmed down. I decided to install and alternative launcher but the problem didn't totally go.
Thereafter I decided to delete trebuchet from root and boom the phone never calmed down and kept restarting. Eventually I tried restoring factor settings and it says now that there's no OS.
I had TWRP installed before but now when I've tried to install the latest one, it doesn't show any files on the OTG. I've put twrp on the SD along with a rom as well but nothing shows at all.
Can someone help in simple terms?
Click to expand...
Click to collapse
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
sdembiske said:
Use adb commands to flash TWRP (Put your TWRP image in the same folder on your pc as your adb and enter each command separately):
adb reboot bootloader
fastboot flash recovery twrp.img (latest version is 3.1.1-0-peregrine, remame it to twrp.img - if that doesn't work rename twrp to recovery.img and try that).
fastboot reboot
If that works, restore you last known good working backup or try re-installing your stock rom.
Click to expand...
Click to collapse
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
ive managed to get the latest twrp on.. now I cant seem to adb sideload the rom nor does it show via otg.. ADB sideload disconnects and says invalid zip file
emmpii said:
I've installed fastboot onto my PC. Now i'm trying the adb commands but my phone isn't showing up
Tried a new cable.. so far it's started to recognise. I'll update this if theres news.
*adb command doesn't work... says no devices. Fastboot seems to work
Click to expand...
Click to collapse
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
sdembiske said:
Install or re-install your Motorola Device Manager on your pc from this link: https://mobilesupport.lenovo.com/us/en/solution/MS88481
Check in your pc Device Manager to see if your device is connected and recognized properly when you plug in the USB cable.
In the folder where your adb and fastboot files are, open a command prompt and enter adb devices to see if the phone is recognized now in adb. If it is, proceed as suggested earlier.
Click to expand...
Click to collapse
shows up in device manager as android usb device, Still not showing on adb
I managed to get the device to finally track on with adb. It tracks fine now. However I can't seem to flash a rom on regardless of whether its OTG or sideload...
emmpii said:
shows up in device manager as android usb device, Still not showing on adb
Click to expand...
Click to collapse
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
sdembiske said:
Try this command: fastboot boot recovery.img or fastboot boot twrp.img
Go to this link (https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816) and download the correct untouched rom for your phone model and transfer it to your sd card or internal memory.
Then try this command: fastboot boot recovery.img or fastboot boot twrp.img
and follow the directions exactly in the op in that thread to flash the rom.
Click to expand...
Click to collapse
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
emmpii said:
Absolutely no idea how but I managed to get one of the CM roms sideloaded and even though when i chose to reboot it said no OS. I've got it going, however I've forgotten to put gapps on so I'll try that now. Later on I'll try sideload stock rom or something and see how that goes. Thanks for the help so far! :good:
Click to expand...
Click to collapse
The problem with CM roms is they're not really being updated anymore - just one of the problems I have with a lot of custom roms besides the bugs, etc., etc.
If you're hell bent on a custom rom, I would check out this one: [ROM][OFFICIAL][Peregrine][7.X] LineageOS 14.1 at https://forum.xda-developers.com/moto-g/4g-development/rom-cyanogenmod-14-0-t3469103
Lineage is the new go-to from CM. I personally would go back to stock first, however, to ensure everything is restored properly before installing it.
It's being updated regularly currently.
I just had a old CM rom downloaded from before hence I went to that lol. I'm trying lineage for now but I've also downloads the stock ROM. Whatever will keep the phone going

Categories

Resources