Okay, so when trying to flash CM ROM, I stupidly ended up wiping EVERYTHING in the "wipe" option. Trying to recover it, I tried sideloading the file through ADB, but TWRP would disconnect off the PC and say failed (TWRP version 3.0.2-0). Pushing a ROM zip won't work, as the phone only connects to the PC as ADB Sideload mode ('error: closed' is what it would say), and nothing else would work except sideload. I no longer have a working OTG cable, as my last one broke on me a week ago. The PC will not connect to phone on the 'Mount USB' option from TWRP. Plz help! I'm running out of ideas. I did make a backup (using Online Nandroid Backup, no it wasn't a zip) on the SD card, but TWRP will not read the SD card on my device. Note that the only thing I have is TWRP; no bootloader, no Fastboot, no nothing. Just TWRP.
TRiP_E said:
Okay, so when trying to flash CM ROM, I stupidly ended up wiping EVERYTHING in the "wipe" option. Trying to recover it, I tried sideloading the file through ADB, but TWRP would disconnect off the PC and say failed (TWRP version 3.0.2-0). Pushing a ROM zip won't work, as the phone only connects to the PC as ADB Sideload mode ('error: closed' is what it would say), and nothing else would work except sideload. I no longer have a working OTG cable, as my last one broke on me a week ago. The PC will not connect to phone on the 'Mount USB' option from TWRP. Plz help! I'm running out of ideas. I did make a backup (using Online Nandroid Backup, no it wasn't a zip) on the SD card, but TWRP will not read the SD card on my device. Note that the only thing I have is TWRP; no bootloader, no Fastboot, no nothing. Just TWRP.
Click to expand...
Click to collapse
You can connect to ADB but the adb push command isn't working when you try to move the ROM.zip to the device?
Get a new OTG cable.
The nandroid backup you made should have been done in TWRP and stored on extsdcard instead of the online backup, online backup is crap because it only works in certain conditions, it's useless when the device can't connect to a network.
Sent from my SM-S903VL using Tapatalk
Yes. ADB commands other than sideload will say 'error:closed', and ADB Sideload will just end up making the phone disconnect. At this point, I may HAVE to end up getting a new OTG Cable.
Yes, I was trying to do the backup on TWRP, but as it couldn't read the SD Card, I used Online Nandroid Backup. Then I realized that everything I was doing was completely stupid while I wiped EVERYTHING....
TRiP_E said:
Yes. ADB commands other than sideload will say 'error:closed', and ADB Sideload will just end up making the phone disconnect. At this point, I may HAVE to end up getting a new OTG Cable.
Yes, I was trying to do the backup on TWRP, but as it couldn't read the SD Card, I used Online Nandroid Backup. Then I realized that everything I was doing was completely stupid while I wiped EVERYTHING....
Click to expand...
Click to collapse
Yeah, new cable seems to be your only option.
Sent from my SM-S903VL using Tapatalk
Alright then, I'm going to go see where I can buy one. Thanks for the confrirmation.
I cant even mount the ****ing usb flashdrive through OTG!!!!! On other devices, it works fine, but on this device it doesn't even show the frickin USB-OTG option.
TRiP_E said:
I cant even mount the ****ing usb flashdrive through OTG!!!!! On other devices, it works fine, but on this device it doesn't even show the frickin USB-OTG option.
Click to expand...
Click to collapse
Try rooting the device and then use the Stick Mount app, if your device has the hardware to support OTG, that should enable it, but if your device does not have the hardware to support OTG then it doesn't matter what you do softwarewise or what you modify, it has to have the hardware or it can't do it at all.
Things like this are why I'd never buy or own a ZTE device of any kind. Relatively soeakibg, they are all junk.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Only thing is, I dont HAVE any system to boot in order to check that. I guess I'm out of luck, no wonder why others said this phone was crap.
TRiP_E said:
Only thing is, I dont HAVE any system to boot in order to check that. I guess I'm out of luck, no wonder why others said this phone was crap.
Click to expand...
Click to collapse
If you can use adb shell or fastboot, you can try getting a copy of system.img from someone with your exact device and dd or fastboot flash the img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
After reading other pols forums, it seems that I didn't have to delete the internal storage........
TRiP_E said:
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
Click to expand...
Click to collapse
Sideloading a ROM won't work.
Try
adb reboot bootloader
If you can boot to bootloader or fastboot you can try finding the firmware for another device that has all of the exact same hardware components that your device has then try fastboot flashing it or extract the separate .imgs from the firmware and use the fastboot commands to flash the boot.img and system.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
can't get into fastboot, ADB command says error: closed, while doing the command in terminal in the TWRP menu keeps me on ZTE screen (only reboot recovery works, not as ADB command but in terminal).
TRiP_E said:
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
Click to expand...
Click to collapse
I have most, if not all the. Img files for this I managed to successfully root, TWRP, and deKingoCrap my n817
I also have a nandroid of this phone, though mine is the qlink one
help.
equitube said:
I have most, if not all the. Img files for this I managed to successfully root, TWRP, and deKingoCrap my n817
I also have a nandroid of this phone, though mine is the qlink one
Click to expand...
Click to collapse
dude i need the twrp backup of the qlink variant. i formatted the system and got bootloop at zte screen
filldapipe said:
dude i need the twrp backup of the qlink variant. i formatted the system and got bootloop at zte screen
Click to expand...
Click to collapse
Did you ever get the TWRP for this? I have it in my dropbox pm me.
The issue were running into is that the TWRP on this model can't see the ext sd. The backup is 1.5 or 2gb which is usually too large to fit on the internal SD
Slacker is working hard at modding the Fstab file to make TWRP see that storage. Any ideas please let him or I know([email protected] or here )
I'm also working on an EquiMods custom ROM for this. Bare bones battery saver, switchable to performance when needed.
Anyone know if and how these can be overclocked?
I have a deodex rom done for this phone and also should have the working twrp recovery by morning. The cm11.0 ive been working on is almost done. I hope Everytime i flash it to phone i get white screen. Also im going to install xposed on it in the morning. I think i found the fix for that to work
Any news on this? I can't find anything that works with this phone. I have adb sideload working, but that's pretty useless from what I understand.
edsfunsite said:
Any news on this? I can't find anything that works with this phone. I have adb sideload working, but that's pretty useless from what I understand.
Click to expand...
Click to collapse
They obviously got something to work since there are members in this thread that have TWRP installed on their devices, that means they can at least root the device but I doubt there are any ROMs for this device.
Sent from my LGL84VL using Tapatalk
I've rooted my N817 but never made an Nandroid backup. I still have TWRP up and working but I've tried to flash the 2 roms I know of....they both "install" but when I try to boot It stays in the ZTE screen...Help!
Related
Firstly, I am sorry for creating such a noob thread on the forum, but I could really use a hand.
I was flashing a 4.4 ROM (SlimKat), I had wiped /system, /boot, etc. everything but usb storage. I then went to flash the .zip and everything looked alright for about 30 seconds (formatting finished, mounting partitions, etc.) until the installation hit a bump and said there was an error in the ROM .zip, and then aborted.
I have a NANDroid backup on the USB storage, but for some reason CWM refuses to install it claiming there is an MD5 mismatch. USB storage won't mount to my PC (in CWM) for whatever reason, and fastboot won't work in either win7 or ubuntu. I've tried AdamOutler's unbrickable tool with no success, it can't recognise the device and says SBL Injection Failure.
Any ideas? Thanks very much for any help.
mrjimyjohn said:
Firstly, I am sorry for creating such a noob thread on the forum, but I could really use a hand.
I was flashing a 4.4 ROM (SlimKat), I had wiped /system, /boot, etc. everything but usb storage. I then went to flash the .zip and everything looked alright for about 30 seconds (formatting finished, mounting partitions, etc.) until the installation hit a bump and said there was an error in the ROM .zip, and then aborted..
Click to expand...
Click to collapse
What exactly was the error?
There wasn't a real error dialogue, if I remember right it just displayed "ERROR: there was an error in <ROM package.zip> installation aborted" The next line said something like "(code 7)".
Thanks man
Which CWM version were you using?
I was using 6.0.3.1. One of the first things I thought of was updating the recovery, but with no way to mount /sdcard I don't know how I could.
mrjimyjohn said:
I was using 6.0.3.1. One of the first things I thought of was updating the recovery, but with no way to mount /sdcard I don't know how I could.
Click to expand...
Click to collapse
You need at least CWM 6.0.4.3 to install any 4.4 rom. Flash the recovery.img via fastboot.
Download the latest CWM (.img, not .zip) and then also install this: http://forum.xda-developers.com/showthread.php?t=2317790, connect your device to pc, reboot to bootloader (vol up + power button) then enter this in command prompt provided by "minimal adb and fastboot": fastboot flash recovery <recovery img path and filename>.img
This should fix your problem if done correctly.
Thank you very much, I will try that.
I think the problem though, is that my pc cannot recognize the device in any form. Normally I would expect to at least see a "device not working properly" or similar message with the windows "beep", but I get nothing, in fastboot mode or with usb storage mounted in recovery. On a different ubuntu machine it's not recognized either, fastboot - devices and adb -devices both return nothing.
Try having your device drivers set-up through Nexus Root Toolkit. Just follow the "Full Driver Installation Guide" inside the app and delete all samsung drivers and then freshly install drivers needed for your device. This is worth the shot although the problem could be your usb cable, usb port, etc..
Thanks for your help. I actually tried Wug's tool with no luck, but I didn't ununstall the original drivers first so that may have been the problem. I'll also try using a different cords and PCs when I get back home.
Thanks again, and merry christmas!
So I bought a new usb cable and my pc could talk to the device as it was showing up in device manager. I installed the drivers again and got fastboot working, but I'm not really sure how to flash from here. I flashed the new CWM with
fastboot flash recovery <cwm*.zip>
It worked just fine, but how can I flash a rom now? regular .zip rom's can't be flashed through fastboot AFAIK, and looking through my NANDroid backups it looks like none of them have a system.img which seems really weird. Can I flash a system.ext4.tar.a as if it was a system.img?
I would have thought you could transfer files to /sdcard through fastboot but I guess not...
mrjimyjohn said:
So I bought a new usb cable and my pc could talk to the device as it was showing up in device manager. I installed the drivers again and got fastboot working, but I'm not really sure how to flash from here. I flashed the new CWM with
fastboot flash recovery <cwm*.zip>
It worked just fine, but how can I flash a rom now? regular .zip rom's can't be flashed through fastboot AFAIK, and looking through my NANDroid backups it looks like none of them have a system.img which seems really weird. Can I flash a system.ext4.tar.a as if it was a system.img?
I would have thought you could transfer files to /sdcard through fastboot but I guess not...
Click to expand...
Click to collapse
Oh I thought you already put your desired rom inside the sdcard. My workaround for this: flash TWRP via fastboot, mount sd card to pc, move rom.zip to sdcard, then re-flash latest CWM via fastboot. Flash rom through recovery.
I did have it on there originally but I foolishly did a full wipe through fastboot. I tried to mount SD card with cwm but my PC still wouldn't recognise it, does TWRP mount things differently or something? All is good now though, I didn't realise you could use adb while in recovery mode so I could push files that way with sideload. Thanks for your help man, its really, uh, helped.
Hey guys,
I seriously need help with my M4. I think I might have soft-bricked it :crying:
Here's what I have done:
I unlocked it and installed TWRP 2.7.1.1 to install a custom ROM. The thing is, I didn't know it was branded (as I found out too late, the CID is VODAP102), so the ROM wouldn't install. Now, I tried to change the CID to a SuperCID (11111111) but ran out of luck. So I thought I'd simply revert to Stock. So far, so good. Yesterday I got an update notification for a Sense 6.0 update but it wouldn't install. So I successfully flashed the stock recovery but the installation of the update halted (red exclamation mark). I then went back to flashing the boot.img too (from an UL rom, unfortunately) and relocked the bootloader. Still the same error. Then I read I should factory reset in the bootloader. So I did and the result was I got stuck on the bootscreen!! So I unlocked it again, re-installed the TWRP recovery to at least get back to the backup I made before, but the thing is: My storage got wiped and TWRP won't mount OTG-USB!!! I guess it's that some partitions/files are now messed up. Now I cannot do anything anymore. I don't have the stock ROM as a flashable zip, only the TWRP backup.
Here's what still works:
Fastboot & Recovery
What doesn't work:
ADB (because phone won't boot), ExtSDcard (naturally!) and flashing ROMs via fastboot because I need one that matches that damn Vodafone CID
I think if someone could upload their Vodafone Germany M4 ROM as a zip or exe, I could manage it. If someone has it, PLEASE give it to me!
If someone has any other idea how to get this phone to work, or at least get TWRP to mount the USB-stick, please HELP!!! I'm totally at a loss :crying:
You can ADP from TWRP so all is not lost
apjashley said:
You can ADP from TWRP so all is not lost
Click to expand...
Click to collapse
Well, if I start ADB sideload in TWRP, it says it is starting but then nothing happens. Or does it take more than 5 minutes? Because cmd says no devices found :/
It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.
apjashley said:
It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.
Click to expand...
Click to collapse
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...
kumpelfred said:
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...
Click to expand...
Click to collapse
What does your Windows device manager show when you're in TWRP but not sideload mode?
I've been wrong before but I believe from sideload mode "adb push firmware.zip /sdcard/" should work as normal.
Hi, thanks for your reply.
The device manager lists it as HTC One Mini but with a yellow question mark. When I plug it in, it recognizes it and installs all the drivers with the exception of the MTP driver, and it won't let me manually install it. In fastboot, it is listed as "MyHTC".
When I go into adb sideload mode in TWRP it gets stuck on telling me it starts the service but nothing happens. "adb devices" remains empty in the cmd console.
As I said, I DO have a backup, only I cannot restore it as TWRP is unable to mount the USB-OTG. I simply cannot check the box (all other partitions data, system etc. work)! I tried 3 different sticks and TWRP versions 2.6.3, 2.7.1.0 & 2.7.1.1. On a friend's M7 TWRP loads that stick in a few seconds. ADB is not working as I said, otherwise I could simply push the file to the internal SD and see if I can restore it from there :/ I think it may have something to do with TWRP not being able to fix permissions, too (it tells me to boot the system once after factory reset, which I cannot do of course!) but I'm not sure....
What I have also tried is setting back the phone (relocked, stock recovery, cache erased) via rebootRUU and a Vodafone DE firmware zip but it tells me "read zipped android info fail" and aborts. Probably because I'm on a higher hboot version than the one in the firmware zip and I cannot go S-OFF without ADB working -.-
I'm struggling with this for 3 days now... Is there nothing I can do to get it booted into anything???
Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:
kumpelfred said:
Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:
Click to expand...
Click to collapse
could u share that drivers pls. i have same problem ((
[email protected] said:
could u share that drivers pls. i have same problem ((
Click to expand...
Click to collapse
Hey, I was wrong about the HTC drivers, this was not the issue. The issue was that the latest TWRP recovery (2.7.1.1) did not work in adb mode for whatever reasons. The solution was not older drivers (as they update anyway) but to install an older TWRP version (2.6.3.0 worked for me).
This is only when you cannot boot into your system and have to adb push something to your sdcard. If the phone is not recognized when connected with a booted system running, the only fix is to remove drivers and programs that could interfere (Samsung Kies, HTC Sync, e.g.), reboot, reinstall the drivers, plug your phone into a different USB port and just hope 'adb devices' gets a result, otherwise try all over again.
Hello, my OPO device was bricked after I accidentally wiped the internal memory and it has no rom installed either. However, I have access to the fastboot mode and also TWRP. I've tried to use adb push to put in a rom but it says device not found when I try. Also while connected to my computer, the device doesn't show up, but in device manager it will show up as just "One".
When typing adb devices, nothing shows up, when typing fastboot devices my phone's ID will show with fastboot to the right.
Kogecha said:
Hello, my OPO device was bricked after I accidentally wiped the internal memory and it has no rom installed either. However, I have access to the fastboot mode and also TWRP. I've tried to use adb push to put in a rom but it says device not found when I try. Also while connected to my computer, the device doesn't show up, but in device manager it will show up as just "One".
When typing adb devices, nothing shows up, when typing fastboot devices my phone's ID will show with fastboot to the right.
Click to expand...
Click to collapse
You can do a couple things:
1. Flash COS12.1 from here via instructions in the linked thread
2. Download TWRP and flash it via fastboot commands, reboot to recovery and transfer a nightly and gapps and flash
You are not bricked at all, last time I managed to brick my phone the screen was black no matter what I did, you can easily get back from fastboot
Renosh said:
You can do a couple things:
1. Flash COS12.1 from here via instructions in the linked thread
2. Download TWRP and flash it via fastboot commands, reboot to recovery and transfer a nightly and gapps and flash
You are not bricked at all, last time I managed to brick my phone the screen was black no matter what I did, you can easily get back from fastboot
Click to expand...
Click to collapse
I can't transfer files into the phone as windows doesn't recognize the device anymore, and there is no device found when I try to use adb to push files into /sdcard/
I will try the first option and will let you know.
Edit: First option worked, phone is working fine now. Thanks for your help and I'll be more careful in the future.
Kogecha said:
I can't transfer files into the phone as windows doesn't recognize the device anymore, and there is no device found when I try to use adb to push files into /sdcard/
I will try the first option and will let you know.
Edit: First option worked, phone is working fine now. Thanks for your help and I'll be more careful in the future.
Click to expand...
Click to collapse
Twrp also has USB-OTG function .. Even if you don't have any ROM on phone .. You can download a rom to a usb pendrive and connect it to phone twrp will recognize the USB pendrice and then can install rom from that ..
sent from Bacon (OnePlus One)
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.
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