Database Info

[Q] TWRP problem

I want to root my tablet so I flashed TWRP 2.6.0.0 using fastboot everything works fine.
But now I want to install the zip to root the tablet, problem is TWRP cannot mount any storage, internal sdcard external sdcard nothing at all is alway says E:Can't mount 'xxx' on anything I tap.
I tried CWM, and 2.5.0.0 and nothing seems to work.
I can boot fine in the stock OS, everything works fine but that
My bootloader is 10.6.1.27.1-20130711
Can anyone help me?

Ok now it is bad, I tried to factory reset using the bootloader (power + volume down)
It booted in the buged TWRP and now it keeps booting in TWRP and I cannot even reach the bootloader

Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE

aarsyl said:
Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
I cannot get this to work on Windows 8, I have Asus Transformer ADB interface lister in device manager but I cannot see my device with the adb devices command.
Also, in TWRP when I try adb sideload it says failed.

win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster

Buster99 said:
win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster
Click to expand...
Click to collapse
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help

Matiosse said:
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help
Click to expand...
Click to collapse
fastboot should work. hold Vol-down and reset the device and keep vol-down pressed. it should go to fastboot. when you're in fastboot connect it to your laptop and see if the OS recognized your device - if not you have a driver issue. resolve that by installing the asus driver or the newest google generic drivers.
when you can see your device on dosprompt/powershel with fastboot devices then continue with getting recovery to work.
btw- stuck in twrp means? booting twrp (teamwin screen) but not responding?
good luck
-Buster

The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways

Matiosse said:
The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways
Click to expand...
Click to collapse
but you are still able to boot into android?

I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.

Matiosse said:
I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.
Click to expand...
Click to collapse
can you boot into twrp? and i mean just boot into it? so that you see install, backup, restore etc. buttons?
if yes - twrp has an adb mode
connect your tab in twrp to your pc (check that you can see it - adb devices) if yes type: adb reboot bootloader
and you should boot into that. test it with fastboot devices.
most important thing is that you get into fastboot or a working recovery to flash or prepare to flash a (custom) rom back onto your device.
Buster

I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)

Matiosse said:
I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)
Click to expand...
Click to collapse
learn to crawl before you run :angel:

Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android

Matiosse said:
Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android
Click to expand...
Click to collapse
dude - you can't boot into android anymore, you can't boot into fastboot to your own accord - yet you try to sideload stuff in twrp for what ever reason.
i gave you more hints and tips in my previous posts and link to get it to work yet it eems you did none.
so don't get me wrong - but what excactly is your goal here?

My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.

Matiosse said:
My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.
Click to expand...
Click to collapse
yes i read your posts - but im still unclear what you are trying to accomplish with sideload?
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?) "adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
-B

ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?

Matiosse said:
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
Click to expand...
Click to collapse
when its connected - is device manager at least showing it as faulty or not at all? (yellow triangle exclamation mark thingy, i just installed asus on my VM) -> see attached file

UPDATE: I succeeded to go in fastboot mode
I couldn't get my tab to be recognized by windows so I installer my Nexus 4 using the toolkit, when it was succesfully installed I could manually install my tab since the "android devices" option appeared in the list when you want to manually install a driver in the devices manager. So I could choose Asus ADB interface.
Now I can boot into Android, but it will go into TWRP as soon as I restart my tablet.
Now I will try the link you sent me to get TWRP recognize my storage so I can flash a new rom, I will let you know if something go wrong.
Thanks for helping

Phone stuck in boot cycle

First time post and it's been a hell of a day. I need to figure out how to either sideload the factory ROM, load a 3rd party ROM, or actually factory reset my phone to stock.
I unlocked my bootloader and installed TWRP and SuperSU earlier in the day. I then wanted to try to load Cyanogen11, but there were issues with the load, it constantly failed. I made a backup before I did this, but when I attempted to load the backup, nothing happened, it would just continually boot to recovery.
I attempted a few other things, clearing caches, doing wipes, powering the phone off for 5~ minutes, etc. etc.
Nothing is working, I can't load any ROM now and phone is either stuck at a bootcycle or the HTC Splash screen (Aside from being able to load bootloader/CWP)

jdolbeer said:
First time post and it's been a hell of a day. I need to figure out how to either sideload the factory ROM, load a 3rd party ROM, or actually factory reset my phone to stock.
I unlocked my bootloader and installed TWRP and SuperSU earlier in the day. I then wanted to try to load Cyanogen11, but there were issues with the load, it constantly failed. I made a backup before I did this, but when I attempted to load the backup, nothing happened, it would just continually boot to recovery.
I attempted a few other things, clearing caches, doing wipes, powering the phone off for 5~ minutes, etc. etc.
Nothing is working, I can't load any ROM now and phone is either stuck at a bootcycle or the HTC Splash screen (Aside from being able to load bootloader/CWP)
Click to expand...
Click to collapse
Are you still having issues? If so, PM me and I'll help you out.....

Got everything sorted with the great help of Nelvin. I had previously gone to the twrp support IRC and after answering a few questions, they just stopped talking... Glad there are people out there still willing to help! He spent a good hour or so with me making sure everything was working.

Hey you two!
Did you solve your problem via PM, then maybe send me the log of it please.
I dont know exactly if we have the same problem, but i'll try to explain mine:
I wanted to put a ROM on my mini, because it is branded.
I unlocked the bootloader on the htc one mini and then put the twrp recovery on it. It seems to work.
Next i wanted to put super su on it, but I'm already stuck in a bootcircle, so i cant put any files onto the phone. I tried to move files with Qick ADB Pusher, but always when I try to send the file from PC(win7) to one mini it says "Opeartion Failed! Exit Code 1". I tried this when i was in Bootloader. When I am in Recovery ADB doesnt even recognize the phone via USB.
If there is more explanation needed, please feel free to ask.
Thank you for your help in advance!
Greetins,
just2lose.

just2lose said:
Hey you two!
Did you solve your problem via PM, then maybe send me the log of it please.
I dont know exactly if we have the same problem, but i'll try to explain mine:
I wanted to put a ROM on my mini, because it is branded.
I unlocked the bootloader on the htc one mini and then put the twrp recovery on it. It seems to work.
Next i wanted to put super su on it, but I'm already stuck in a bootcircle, so i cant put any files onto the phone. I tried to move files with Qick ADB Pusher, but always when I try to send the file from PC(win7) to one mini it says "Opeartion Failed! Exit Code 1". I tried this when i was in Bootloader. When I am in Recovery ADB doesnt even recognize the phone via USB.
If there is more explanation needed, please feel free to ask.
Thank you for your help in advance!
Greetins,
just2lose.
Click to expand...
Click to collapse
Hi, can you let me know: Which ROM you want to flash, if you have attempted to s-off, and that you can boot to recovery?
Also, i'd advise against using utilities like the "pusher", please download this http://d-h.st/qmi and create a directory called c:\adb\ - move your ROM and SuperSU zip files here and extract the adb_windows.zip file to the directory.....

I did not attempt s-off, just normal htc dev bootloader.
First i wanted to flash Magio R4, but then i was thinking about Stock Rom Sense 5.5, which tr1gg3r84 uploaded.
i created folder and moved rom there. i also extracted the adb_windows zip there. what to do next? (i just wanna ask, because im a little scared of totaly breaking the phone now)
Thanks for now!

just2lose said:
I did not attempt s-off, just normal htc dev bootloader.
First i wanted to flash Magio R4, but then i was thinking about Stock Rom Sense 5.5, which tr1gg3r84 uploaded.
i created folder and moved rom there. i also extracted the adb_windows zip there. what to do next? (i just wanna ask, because im a little scared of totaly breaking the phone now)
Thanks for now!
Click to expand...
Click to collapse
Boot to recovery, then
adb push therom.zip /sdcard/
adb push UPDATE-SuperSU.zip /sdcard/
Remember to extract the boot.img from the ROM zip file, and after flashing the ROM and SuperSU, boot to bootloader and FASTBOOT menu then:
fastboot flash boot boot.img

you mean to push with the quick ADB Pusher? but in this programm (on PC) it doesnt find the phone whilie it is is recovery boot.

just2lose said:
you mean to push with the quick ADB Pusher? but in this programm (on PC) it doesnt find the phone whilie it is is recovery boot.
Click to expand...
Click to collapse
No, use the adb binary from the download link I posted......
If your phone isn't found, check the windows device manager and verify that you have ADB Android device listed..... if not, download adb drivers for windows and install - then plug your phone back in.....
You are using TWRP 2.6.0.0 recovery image from here right? http://forum.xda-developers.com/showthread.php?t=2418938

the adb.exe just pops up the cmd console, showing a lot of commands for half a second and then its gone again.
the android device is listed on device manager.
no, i did not use this one(twrp). i used some explanation how to do it from another forum and another file.
should i use this one now? how exactly to do that? theres no explanation :/

Open a command prompt in Windows and cd to c:\adb
Then when your phone is in recovery, type the adb commands I posted earlier.....
Sent from my HTC One mini using XDA Premium 4 mobile app

terdingb all
cmd says that the command is wrong or misstyped
(im in c:/adb typing: adb push rom.zip /sdcard/)

Is your ROM zip file called rom.zip? Can you post a screenshot?
Sent from my HTC One mini using XDA Premium 4 mobile app

ok got it.
now the rom and the supersu.zip are on the phone.
i cleared cache and dalvik and flashed both files(Stock Sense 5.5 4.3 Rooted Odex/Deodex;UPDATE-SuperSU-v1.86; both zip files) and , after that i went into fastboot and tried (fastboot folder) "fastboot flash boot boot.img" but cmd only says "waiting for device"

just2lose said:
ok got it.
now the rom and the supersu.zip are on the phone.
i cleared cache and dalvik and flashed both files(Stock Sense 5.5 4.3 Rooted Odex/Deodex;UPDATE-SuperSU-v1.86; both zip files) and , after that i went into fastboot and tried (fastboot folder) "fastboot flash boot boot.img" but cmd only says "waiting for device"
Click to expand...
Click to collapse
Check device manager on your pc, most likely the adb driver device isn't listed - if not, reboot your pc and try again.... This has happened to me several times......

ok now it worked. writing boot and so on .. finished. total time: 2.717.
i shut it down and started the phone again.
now it almost made the starting sound. after 5 boot cycles it played the whole starting sound and also showed the second screen with the "o1ne" and "beatsaudio" on the bottom.
but thats it. boot cycling in a different way now .
seems like it just doesnt want to work.
i'm so sorry that I am bothering you for so long now..
another idea?
thanks again!
edit: im gonna go through everything again with magio rom r5...

ok got it now. thanks a lot dude!
i deleted the rom files now from the phone but still there is 9gb used on the phone. this is way to much, isnt it?
is there a safe method to clean the whole phone .. something like c:format ?
thanks ³

No problem dood.....
Download an app called diskusage from the store - start it and choose storage card.... Post a screenshot please!
Sent via a weather balloon towed by a flock of seagulls. That's how this messaging stuff works, right?

after the phone went out of battery, it was in a boot cycle again after loading and rebooting.
flashed super su.zip again, but it didnt help. stupid me didnt do a backup yet. so do i have to install the rom again and do all the configs from scretch?

What's your hboot status? Locked/unlocked, s-on/s-off etc
Also, did you do, or install anything before your phone powered off?
Sent from my HTC One mini using XDA Premium 4 mobile app

[Q] Nexus 5 Recovery broken and OS is missing

Hello Everyone. Normally I´m the quiet Reader and not the Active Poster but I need your help guys.
I have a problem since yesterday and I tried to fix it by myself with searching everywhere but couldn´t do it by myself.
What I had before:
Optipop 5.0.2 with Racer Kernel (both had Builds from January) + TWRP 2.8.1
What I wanted to do:
Flash Grogg's AOSP 5.1 and newest Code Blue Kernel
What happenend:
I factory resetted and successfully flashed Grogg's AOSP 5.1 and Code Blue Kernel but had Problems with FCing Clock and Dialer so I tried to reflash both after wiping completely (even internal storage), mounted it and put the needed new files on the internal storage.
I reflashed the Custom Rom + Custom Kernel and the newest Radio, wiped Cache/Dalvik and rebooted. It booted and the notification screen with 'optimizing apps' appeared. After that that screen went black and nothing else.
It was lit so I´knew that the device wasn´t shut down and tried to rebbot sincee nothing happened. I noticed that it was possible to reboot or shut down the device normally so there might have been a Problem with the Rom.
I retried the whole procedure and this time the notification screen didn´t show up after the boot logo and went directly to the black blank screen but i still had the possibility to rebbot/shut down the device normally. This time I didn´t wipe the whole storage and this time it got stuck at the boot logo and the Custom Recovery seems to be broken, too. The screen shows the dead Android with the red triangle.
My Problem is that I can´t connect my device to the computer, find it with 'adb devices' and reflash the Recovery with fastboot. The device is shown as 'android' in device manager in Windows 7 and nothing else. I already tried to un- and reinstall the Google drivers and that whole stuff but it doesn´t work for God's sake. adb doesn´t list my device and the 'list of devices attached' is blank although my device is connected.
I know my phone is soft bricked and that it is possible to fix that although I don´t know why it even broke the OS and Custom Recovery.
Can anyone help me out with a step-for-step-guide to fix the adb Problem and explain me why that blank screen even happenend?
Edit: If I´m in fastboot mode the device is shown as >Android Bootloader Interface< and isn´t listed with 'adb devices'. If it is powered off it is shown as >Android Composite ADB Interface< but is listed with 'adb devices' but I can´t flash the Custom Recovery.

Beyazid said:
My Problem is that I can´t connect my device to the adb to reflash the Recovery.
Click to expand...
Click to collapse
You don't use adb to flash a custom recovery. You use fastboot. That's your first problem.

I actually meant that it isn´t shown with the command 'adb devices' I will change that in the text
Edit: I also noticed that the fastboot mode is always on in the bootloader although the device isn´t connected to the pc. Shouldn´t it only be active if it´s connected?

Beyazid said:
I actually meant that it isn´t shown with the command 'adb devices' I will change that in the text
Edit: I also noticed that the fastboot mode is always on in the bootloader although the device isn´t connected to the pc. Shouldn´t it only be active if it´s connected?
Click to expand...
Click to collapse
I see a couple problems here.
First one is use the newest version of TWRP. You can get that from my signature.
Second is Code_Blue may not be compatible with the ROM you are testing.
You don't need ADB at all for this, you need fastboot.

As I said. I just use adb to make sure that my device is found by and connected to the pc. I know that fastboot is used to flash everything but my Nexus 5 isn´t even shown. So how can I get my phone connected to flash the custom recovery?
And it seems like it is compatible since it worked the after the first installation and boot

FFS, XDA. I had just written a huge ass post on how to use fastboot properly, with the proper commands and ****, and you logged me out, making me lose all that. F U.
Beyazid said:
and the Custom Recovery seems to be broken, too. The screen shows the dead Android with the red triangle.
Click to expand...
Click to collapse
This is the stock recovery.
You need to put your device in fastboot mode, REFLASH TWRP again with fastboot, then STRAIGHT FROM FASTBOOT select (with vol keys and Power) "Restart recovery". When you're in TWRP, wipe data/factory reset, reflash rom, gapps, REBOOT, PROFIT.
`fastboot devices` and `adb devices` are two commands to check if an active connection exists, between the host interface (on the PC, look at it as servers) and the device interface (look at it as clients). both commands will only return your device's SN IF drivers are correctly installed (speaking on a basic level, and about Windows). If you execute those commands, no SN comes up, then you need to fix drivers FIRST. Not even worth trying to do other commands.
`fastboot devices` only works here -> http://bazalabs.com/wp-content/uploads/2014/07/20140705_215603.jpg
`adb devices` works in TWRP/CWM (NOT in stock recovery) and in Android itself (needs USB Debugging active).

Thanks for the help. I was able to flash the Custom Recovery and the Custom Rom with and without Code Blue Kernel but in both ways the phone loads, sets up at the boot logo and goes straight into the blank black screen which appears without the notification screen of the apps that get optimized.
I can manually turn off, reboot.or take a screenshot which clearly indicates that the Rom itself is installed.
How can I fix that problem?
Thanks in advance
Edit: Tried with the Blue Code Kernel which gave that blank screen and wiped everything but internal storage and reflashed just the Custom Rom which gave me the same result
Could it be because the system.img or boot.img are missing??

Beyazid said:
Thanks for the help. I was able to flash the Custom Recovery and the Custom Rom with and without Code Blue Kernel but in both ways the phone loads, sets up at the boot logo and goes straight into the blank black screen which appears without the notification screen of the apps that get optimized.
I can manually turn off, reboot.or take a screenshot which clearly indicates that the Rom itself is installed.
How can I fix that problem?
Thanks in advance
Edit: Tried with the Blue Code Kernel which gave that blank screen and wiped everything but internal storage and reflashed just the Custom Rom which gave me the same result
Could it be because the system.img or boot.img are missing??
Click to expand...
Click to collapse
Try another ROM.
System.img .. boot.img.. comes with the ROM you flashed (well, not exactly, but both partitions do get written to), so no, they're not missing.

I gave it another try and fixed it.
I'll write it down so anybody who ever faces that problem can solve that, too.
Follow that guide (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701) step by step and after a few minutes of flashing and a few minutes of booting you should get a clean and fresh Android Version on your device. It removes all the old files and installs the newest files.
And thanks guys for helping me out with that adb/fastboot mistake. Kudos to you

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

bricked shield?

hi guys,
i my shield is stuck on the nvidia logo when booting normally, if it brings up the bootloader, it shows unlocked but hitting continue caused it to freeze on the screen, recovery freezes on nvidia logo and fastboot protocol just brings it back to this screen. i orginally installed twrp and it confirmed successful flash of new os .... on reboot it bricked to its now state, i cant get into twrp or get my pc to see it to install a new copy
anyone got any ideas
thanks

@Fairmax don't click continue, it freezes because there is nothing to continue to, as long as you can enter bootloader your device isn't fully bricked. So, to fix your problem you will have to download official ROM from nvidia's site (https://developer.nvidia.com/shield-open-source find your model and click recovery images).
When you download latest ROM unzip it and follow the textual guide, but, there will be one file missing (i can't remember which one, user data maybe or something like that), don't worry and just continue with the next step. After you flash just reboot to system by holding power button. Good luck !

i cant seem to get it to be recognised by windows all i get is this-- Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed.--
trying to install nvidia usb driver via have disk bring up an error that the file is not usable with x64 system

ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd

Fairmax said:
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Click to expand...
Click to collapse
Which command did you type in?

fpozar said:
Which command did you type in?
Click to expand...
Click to collapse
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:

Fairmax said:
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Click to expand...
Click to collapse
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...

fpozar said:
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
Click to expand...
Click to collapse
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works

Fairmax said:
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Click to expand...
Click to collapse
You can also try flashing twrp and then lineageos or something from twrp.

fpozar said:
You can also try flashing twrp and then lineageos or something from twrp.
Click to expand...
Click to collapse
good news after a few hours of trying (usb dropped connection a few times then battery died) it finally works again .....been over 2 years since iv had this shield running after nvidia did the recall , now goto put a different rom on there so it dosnt update and kill itself

Hello I had a similar issue with my k1 tablet and ended up flashing factory images via adb fastboot and all flashed fine. Now my tablet is stuck on the boot screen with the green and white nvidia logo. How long does it take to boot please?

I have same issue too. I can load TWRP and flash the other partitions but TWRP shows un-mountable partitions and even a full stock ROM flash will not allow it to boot. I have a similar issue with a recall tablet. what did you do to fix it?