Database Users

Please help! Stuck on

Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.

Zehlek said:
Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Click to expand...
Click to collapse
i'm not on twrp at the moment but you may be able to try this
you may also try the nexus toolkit

Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?

Zehlek said:
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Click to expand...
Click to collapse
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.

efan3719 said:
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
Click to expand...
Click to collapse
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?

Zehlek said:
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Click to expand...
Click to collapse
On the main screen of the nexus tool kit there is a radio button option you can click for it.
Sent from my Nexus 4 using xda premium

not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.

exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
This guy sounds like he knows what he's doing.
Sent from my Nexus 4 using xda premium

exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
It says fastboot is not recognized as an internal command

In twrp, it keeps saying starting adb sideload feature

i posted this in another thread. try this...
1. First make sure that you have fastboot driver installed.
2. Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
3. Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
4. Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly. if not, check to make sure Google Nexus 4 drivers are installed correctly.
5. now open Nexus 4 toolkit and Flash Google Factory stock Rom. Once you are back to stock continue on from there...
Good Luck!

Zehlek said:
It says fastboot is not recognized as an internal command
Click to expand...
Click to collapse
my bad, it's fastboot-toolkit. But since you have a recovery with sideload already, just download a rom that's working, put it in your nexus 4 toolkit folder, rename it to flash.zip, and type in CMD
"adb-toolkit sideload flash.zip"

Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2

Zehlek said:
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium

efan3719 said:
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you. I was beginning to panic when I saw there nothing working that would transfer a rom to my sdcard. Again thank you for all your help
Sent from my Nexus 4 using Tapatalk 2

Messed up mako(Resolved)

I just used toolkit to root new nexus clicked option 8 one click. Everything went fine it rebooted into Google and now its stuck. USB debugging is no longer active, how can I push a file to phone to get boot. Please help. Is there a free node channel for N4 discussion. Thanks.
Sent from my SGH-T959V using xda app-developers app

anoymonos said:
I just used toolkit to root new nexus clicked option 8 one click. Everything went fine it rebooted into Google and now its stuck. USB debugging is no longer active, how can I push a file to phone to get boot. Please help. Is there a free node channel for N4 discussion. Thanks.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Hold the power for about 10 seconds to turn it off, wait 10 seconds and press volume down and power button to get into the bootloader. If you have a windows pc try this link http://download.chainfire.eu/297/CF-Root/CF-Auto-Root/CF-Auto-Root-mako-occam-nexus4.zip to get root. Unzip the downloaded file and click root-windows. That should work.

----- CF-Auto-Root-mako-occam-nexus4 -----
Please make sure your device is in bootloader/fastboot mode before continuing.
***WARNING*** ALL YOUR DATA *MAY* BE WIPED ! ***WARNING***
We are going to run the "OEM UNLOCK" command on your device. If your device
was not previously unlocked, this will wipe all your data !
After the unlock, CF-Auto-Root will boot. You should see a big red Android
on your device's screen.
Press Ctrl+C followed by Y to cancel !
Press any key to continue . . .
The system cannot find the path specified.
The system cannot find the path specified.
It may take a minute or so for the red Android to appear. If it doesn't show up
at all, there may be a problem.
Press any key to continue . . .
gee2012 said:
Hold the power for about 10 seconds to turn it off, wait 10 seconds and press volume down and power button to get into the bootloader. If you have a windows pc try this link http://download.chainfire.eu/297/CF-Root/CF-Auto-Root/CF-Auto-Root-mako-occam-nexus4.zip to get root. Unzip the downloaded file and click root-windows. That should work.
Click to expand...
Click to collapse
any other suggestions

anoymonos said:
----- CF-Auto-Root-mako-occam-nexus4 -----
Please make sure your device is in bootloader/fastboot mode before continuing.
***WARNING*** ALL YOUR DATA *MAY* BE WIPED ! ***WARNING***
We are going to run the "OEM UNLOCK" command on your device. If your device
was not previously unlocked, this will wipe all your data !
After the unlock, CF-Auto-Root will boot. You should see a big red Android
on your device's screen.
Press Ctrl+C followed by Y to cancel !
Press any key to continue . . .
The system cannot find the path specified.
The system cannot find the path specified.
It may take a minute or so for the red Android to appear. If it doesn't show up
at all, there may be a problem.
Press any key to continue . . .
any other suggestions
Click to expand...
Click to collapse
That is what you are supposed to see, don`t worry about it and just press any button. If the bootloader is allreay unlocked you will not loose data. And don`t use Toolkits anymore

gee2012 said:
That is what you are supposed to see, don`t worry about it and just press any button. If the bootloader is allreay unlocked you will not loose data. And don`t use Toolkits anymore
Click to expand...
Click to collapse
ya but no red andriod appeared it just stayed in fastboot mode

anoymonos said:
ya but no red andriod appeared it just stayed in fastboot mode
Click to expand...
Click to collapse
Close CF Auto root, disconnect and reconnect usb and open CF Auto root again and try again.
If that doesn`t work flash TWRP recovery from here http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img in fastboot and flash this superSU zip http://download.chainfire.eu/331/SuperSU/UPDATE-SuperSU-v1.32.zip in recovery

I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app

anoymonos said:
I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Do a data factory reset in recovery, wipe cache and reboot. And try rooting again after you enabled usb debugging.

anoymonos said:
I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Might help to know what error and which img file (specifically), I would just pull down TWRP 2.5.0.0 (specifically for mako):
fastboot flash recovery name-of-recovery.img
Boot into recovery (wipe/format and flash up new rom, etc), or if you instead get an error note the specific error.
PS: If you have no rom/etc due to erasure, you can 'adb push' the zip files to /sdcard while in recovery.

C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
kbeezie said:
Might help to know what error and which img file (specifically), I would just pull down TWRP 2.5.0.0 (specifically for mako):
fastboot flash recovery name-of-recovery.img
Boot into recovery (wipe/format and flash up new rom, etc), or if you instead get an error note the specific error.
Click to expand...
Click to collapse

anoymonos said:
C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
Click to expand...
Click to collapse
First off, bootloader isn't a "recovery", second you're missing a parameter
fastboot [action] [partition] [file]
You were basically telling it to flash nothing onto a partition named bootloader-make-makoz10o.img which course doesn't exist.

anoymonos said:
C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
Click to expand...
Click to collapse
Dude why you are flasing a bootloader!

kbeezie said:
First off, bootloader isn't a "recovery", second you're missing a parameter
fastboot [action] [partition] [file]
You were basically telling it to flash nothing onto a partition named bootloader-make-makoz10o.img which course doesn't exist.
Click to expand...
Click to collapse
i have folled this link and am syuck at flashing bootloader.http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html
basically all i can access is fastboot

This is why you don't use a bootloader. Just do it the old fashion way.
You don't need to flash a bootloader. Just fastboot flash stock Google images and start over
https://developers.google.com/android/nexus/images#occam
Also please change the title, your phone isn't bricked. You just messed up due to taking a shortcut route aka toolkit.

zephiK said:
This is why you don't use a bootloader. Just do it the old fashion way.
You don't need to flash a bootloader. Just fastboot flash stock Google images and start over
https://developers.google.com/android/nexus/images#occam
Also please change the title, your phone isn't bricked. You just messed up due to taking a shortcut route aka toolkit.
Click to expand...
Click to collapse
thats the problem it wont let me flash anything through fastboot

anoymonos said:
thats the problem it wont let me flash anything through fastboot
Click to expand...
Click to collapse
Do a data factory reset/ wipe cache in recovery and reboot.

anoymonos said:
thats the problem it wont let me flash anything through fastboot
Click to expand...
Click to collapse
You have the proper drivers installed? http://forum.xda-developers.com/showthread.php?t=1996051

gee2012 said:
Do a data factory reset/ wipe cache in recovery and reboot.
Click to expand...
Click to collapse
i dont have a recovery everything got wiped

zephiK said:
You have the proper drivers installed? http://forum.xda-developers.com/showthread.php?t=1996051
Click to expand...
Click to collapse
yes proper drivers installed. Just unrooted and relocked old nexus 4 for return and then tried to root and unlock new one and it **** on me

It probably will if you use the proper syntax since you have to tell it which partition.
If you go and grab the TWRP 2.5.0.0 recovery image from their website for mako, you can use the following
fastboot flash recovery nameofrecovery.img
Making sure there are 4 parts as the word recovery is part of the command.
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
Thus why you download one and flash. It's nearly impossible to hard brick a Nexus. Just helps not to receive panic. Take a couple breaths and figure out the proper commands.
Sent from my Nexus 7 using XDA Premium HD app

Nexus 4 stuck in bootloader no recovery

hello i tried to download and flash paranoid ROM on my nexus 4 after some time i dnt like it so try to revert back to nexus 4 stock rom but something went very wrong and now my phone stock in boot loader
wen i try to switch on my phone it directly goes to boot loader i cnt do anything if scroll down and go to recovery my phone went black and its also not starting that.
wen try to connect my phone to computer to recover it ...most of the tool kits showing msg that u dnt have usb debugging on
Please help how to recover my phone

I had that issue once with when flash back from PA. I have to flash IMG files using a toolkit
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 08:06 AM ---------- Previous post was at 08:04 AM ----------
This is the took kit that I used and I had no debug on
http://forum.xda-developers.com/showthread.php?t=1995688
Sent from my Nexus 4 using Tapatalk 4

Zehlek said:
I had that issue once with when flash back from PA. I have to flash IMG files using a toolkit
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Can u please tell me whice toolkit i should use and what is the procedure to do that many thanx

You'll have to do it the old fashioned way, i.e. use fastboot. If you're not familiar, don't rush it, research each step and ensure you have the drivers set up, adb and fastboot installed, etc...
Did you flash the stock recovery back on? IIRC once selecting Recovery from the bootloader you're presented with a black screen, and then must hold the power button for a second or two and then the stock recovery will show up. Limited options available however, wipe data, cache, etc...
http://forum.xda-developers.com/showthread.php?t=2010312

core81 said:
Can u please tell me whice toolkit i should use and what is the procedure to do that many thanx
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1995688
Sent from my Nexus 4 using Tapatalk 4
First select 1 to install drivers. Then download Google factory image and put Boot, System, Recovery in folder(to flash IMG files) in your toolkit folder. Then use option 11 to flash each one. Make sure you are in bootloader mode

axtzenswas
Zehlek said:
http://forum.xda-developers.com/showthread.php?t=1995688
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
okay i ll try and get back to you..but should my computer can identify the device in boot loader mood?
any way i ll try the stock recovery method also and get back to you guys
many thanx for your time

core81 said:
okay i ll try and get back to you..but should my computer can identify the device in boot loader mood?
any way i ll try the stock recovery method also and get back to you guys
many thanx for your time
Click to expand...
Click to collapse
fastboot commands work from BL, adb doesn't. So long as the drivers are installed you will be able to see your phone.

https://developers.google.com/android/nexus/images#occam
That is the link to the factory images for the nexus 4.
http://forum.xda-developers.com/showthread.php?p=42407269
That is the fastboot you will need. (FOR WINDOWS)
turn off the phone and plug it in to fully charge it.
install fastboot
extract the files from the factory image into the fastboot folder.
turn on the device and leave it in the bootloader. (if need be turn off the device and hold vol up and down plus the power until you see bootloader)
run "fastboot devices", this will list any devices that fastboot sees. if your device is not in the list something more is wrong.
This images shows "adb devices" but it is the same output for "fastboot devices" https://sites.google.com/site/rodsmods13/_/rsrc/1370839220039/home/example screenshot.png
now run the "flash-all.bat"

dl200010 said:
...now run the "flash-all.bat"
Click to expand...
Click to collapse
Although a reminder that running the bat file without removing the userdata.img file from the zip, and editing the -w out of the bat file will wipe the sdcard in case the OP's is still intact.

CMNein said:
Although a reminder that running the bat file without removing the userdata.img file from the zip, and editing the -w out of the bat file will wipe the sdcard in case the OP's is still intact.
Click to expand...
Click to collapse
Yeah I completely forgot that! I don't have the image downloaded to look at to list the commands to install without using the bat file.

dl200010 said:
Yeah I completely forgot that! I don't have the image downloaded to look at to list the commands to install without using the bat file.
Click to expand...
Click to collapse
bat file is definitely the way to go however*, I've grown to hate typing terminal commands :laugh:
*Except for that one time I forgot to edit stuff

CMNein said:
bat file is definitely the way to go however*, I've grown to hate typing terminal commands :laugh:
*Except for that one time I forgot to edit stuff
Click to expand...
Click to collapse
I admin three Linux headless servers, so it is like second nature to me. Maybe best route for him is for one of us to modify the bat and post it.
Sent from my Nexus 4 using XDA Premium 4 mobile app

CMNein said:
Although a reminder that running the bat file without removing the userdata.img file from the zip, and editing the -w out of the bat file will wipe the sdcard in case the OP's is still intact.
Click to expand...
Click to collapse
my frnd can u please explain little bit more about the process

THANKS TO CMNein dl200010
MY PHONE IS BACK TO NORMAL
thanks alot

core81 said:
my frnd can u please explain little bit more about the process
Click to expand...
Click to collapse
One you have the factory image in hand and have the following files extracted to your platform-tools folder, you'll want to keep on opening the archives until you're left with the following, but don't extract anything from the zip file:
-bootloader-mako-makoz20i.img
-radio-mako-m9615a-cefwmazm-2.0.1700.84.img
-image-occam-jwr66y.zip
-flash-all.bat
You'll want to open the image .ZIP and delete userdata.img.
Then open the flash-all.bat and delete the -w as seen on line 23 in the screen capture.

core81 said:
THANKS TO CMNein dl200010
MY PHONE IS BACK TO NORMAL
thanks alot
Click to expand...
Click to collapse
Awesome, I see you got yourself sorted out while I was replying :highfive:

[Q] Help Needed Soft bricked LG G2

Ok so My lg g2 can go into download mode and i can get it into twrp recovery but i accidentally completley wiped the phone out and my SD card so now im stuck with an empty lg g2 that can factory reset into TWRP recovery but nothing in the storage and no i do not have a backup anymore
i tried to do the Kdz firmware update but its a LGVS980-24A and i followed the steps but i dont get the language window where i have to chose korea and the language instead the LGB2c pops up and say its already up to date so nothing happens....So what do i do now any suggestions im totally up for someone taking over the computer and doing it for me bcuz imma noob at this stuff

LaEezus said:
Ok so My lg g2 can go into download mode and i can get it into twrp recovery but i accidentally completley wiped the phone out and my SD card so now im stuck with an empty lg g2 that can factory reset into TWRP recovery but nothing in the storage and no i do not have a backup anymore
i tried to do the Kdz firmware update but its a LGVS980-24A and i followed the steps but i dont get the language window where i have to chose korea and the language instead the LGB2c pops up and say its already up to date so nothing happens....So what do i do now any suggestions im totally up for someone taking over the computer and doing it for me bcuz imma noob at this stuff
Click to expand...
Click to collapse
Look up "15 second ADB" and install that. No need for the sdk. Download a Rom to your computer. Put it in a file while it's still in a zip file. Make sure you have adb and LG drivers installed. Right click inside the folder that contains your Rom.zip. and hit "open command terminal here" then type "adb devices" if you installed the drivers and 15 second adb it will display your phone Id inside the terminal. Then you have to adb push Rom.zip to your phone. I've had to do this TWICE.
Sent from my LG-D800 using XDA Free mobile app
---------- Post added at 11:09 AM ---------- Previous post was at 11:03 AM ----------
Pm me if you need further assistance
Sent from my LG-D800 using XDA Free mobile app

Clearing it up
Nigglenuts said:
Look up "15 second ADB" and install that. No need for the sdk. Download a Rom to your computer. Put it in a file while it's still in a zip file. Make sure you have adb and LG drivers installed. Right click inside the folder that contains your Rom.zip. and hit "open command terminal here" then type "adb devices" if you installed the drivers and 15 second adb it will display your phone Id inside the terminal. Then you have to adb push Rom.zip to your phone. I've had to do this TWICE.
Sent from my LG-D800 using XDA Free mobile app
---------- Post added at 11:09 AM ---------- Previous post was at 11:03 AM ----------
Pm me if you need further assistance
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
When you say put it in a file do you mean a new folder?

If you have any problems with adb just get an otg (on the go cable) and attach a pen drive with whatever you want to flash. Mount it in twrp and flash as usual.
Sent from my LG-D802 using Tapatalk

LaEezus said:
When you say put it in a file do you mean a new folder?
Click to expand...
Click to collapse
Precisely
Sent from my LG-D800 using XDA Free mobile app

Bricked L5.0.2 No ADB or USB

N4 16Gb : Loliop 5.02, SimpleAOSPv11, AK Kernel, CWM Philz Touch 6.46.3
I foolishly ran "Clean to install new ROM" from Philz recovery (under "Factory Reset").
I don't have a ROM on the device to flash, and can't see the device over USB or ADB.
Can anyone help recover this please? Thanks

fr0d0#2 said:
N4 16Gb : Loliop 5.02, SimpleAOSPv11, AK Kernel, CWM Philz Touch 6.46.3
I foolishly ran "Clean to install new ROM" from Philz recovery (under "Factory Reset").
I don't have a ROM on the device to flash, and can't see the device over USB or ADB.
Can anyone help recover this please? Thanks
Click to expand...
Click to collapse
First off, you're not bricked. When you boot into recovery and your device connected to your pc what do you get when you run the command adb devices from a Windows command window?
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
First off, you're not bricked. When you boot into recovery and your device connected to your pc what do you get when you run the command adb devices from a Windows command window?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks jd
I don't get anything no matter which mode I boot into

fr0d0#2 said:
Thanks jd
I don't get anything no matter which mode I boot into
Click to expand...
Click to collapse
Are you on a Windows pc? Do you have adb and fastboot setup on the pc? Had the pc recognize the device in the past?
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Are you on a Windows pc? Do you have adb and fastboot setup on the pc? Had the pc recognize the device in the past?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Windows 8 with adb installed that has previously seen the N4, yes.
I've had an HTC M8 connected recently. Just now, before wiping, I was connected via USB.

fr0d0#2 said:
Windows 8 with adb installed that has previously seen the N4, yes.
I've had an HTC M8 connected recently. Just now, before wiping, I was connected via USB.
Click to expand...
Click to collapse
Ok, so it doesn't seem like a driver or software issue. With your device booted into recovery and connected to the pc what do you see the device in device manager? It should show up as an android adb composite interface, or something like that.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Ok, so it doesn't seem like a driver or software issue. With your device booted into recovery and connected to the pc what do you see the device in device manager? It should show up as an android adb composite interface, or something like that.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I have an exclamation mark next to N4

Driver re-installed - now recognised as Android Composite ADB Device

fr0d0#2 said:
Driver re-installed - now recognised as Android Composite ADB Device
Click to expand...
Click to collapse
Good, download a rom.zip to your pc if you don't already have one. Then you're going to want to boot into recovery and push the zip to your device using adb. Once there you'll be able to flash it in philz
adb push rom.zip /sdcard/Download. I might have the / backwards. I always forget which way they go. For rom.zip use the full name of the rom. You'll want to have the rom.zip in the same folder as adb.exe and open your command window in that folder too.
Sent from my Nexus 9 using XDA Free mobile app

Thanks jd
You had the slashes the right way around - back in a bit

I'm still not getting the device listed at the command prompt, and get an error saying the same when I try the push command.
WUGs toolkit says it's there and in fastboot mode, and says it's pushed the file successfully but there's nothing there.

fr0d0#2 said:
I'm still not getting the device listed at the command prompt, and get an error saying the same when I try the push command.
WUGs toolkit says it's there and in fastboot mode, and says it's pushed the file successfully but there's nothing there.
Click to expand...
Click to collapse
I'm not that familiar with philz. Does it have an option to enable mtp when you're booted into it? If it did you can copy and paste the rom from your pc to the device. Twrp has that option under mount. I may have you boot into twrp with fastboot to use that option. How familiar are you with fastboot?
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I'm not that familiar with philz. Does it have an option to enable mtp when you're booted into it? If it did you can copy and paste the rom from your pc to the device. Twrp has that option under mount. I may have you boot into twrp with fastboot to use that option. How familiar are you with fastboot?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Not that I can find JD. There are several mount options but USB doesn't work... because it's looking for an external source I presume.
Not very familiar.

fr0d0#2 said:
Not that I can find JD. There are several mount options but USB doesn't work... because it's looking for an external source I presume.
Not very familiar.
Click to expand...
Click to collapse
Well,a good time to learn. Download the latest twrp image from here http://techerrata.com/browse/twrp2/mako. Rename it recovery for simplicity. I'm going to have you re-install fastboot from, Google 15 second adb install xda. That'll simplify the path issues using fastboot and adb, it sets an environment variable so you don't have to worry about the path to adb or fastboot.
Then open a command window in the same folder as the twrp image is in. With your device booted into the bootloader and connected to your pc run the command
fastboot boot recovery.img.
That'll boot you into the twrp recovery. Go to mount and in the lower right hand corner you should see and option to mount mtp. Then you should see your device in Windows just like you normally would. That should make it easy to copy and paste the rom.zip to your device. Once it's copied just install it using twrp. You shouldn't have to reboot or anything.
Sent from my Nexus 9 using XDA Free mobile app

Thank you so much JD
twrp installed and mtp enabled - plain sailing from there on.
I owe you a pint :good: :highfive:

fr0d0#2 said:
Thank you so much JD
twrp installed and mtp enabled - plain sailing from there on.
I owe you a pint :good: :highfive:
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 9 using XDA Free mobile app

For future reference a USB otg cord and pen drive would of been very easy and cheap glad you got it fixed!!
Sent from my LG-VS985 using XDA Free mobile app