Related
Please help! Accidentally did a wipe /system in TWRP and now get the message "exec '/system/bin/sh' failed: No such file or directory". How can this be a fix?
Having no experience with the fire, my guess would be to use the USB mount in twrp put on cm7 flash it.
Sent from my Full Android on Bravo using XDA App
adbirdie said:
Having no experience with the fire, my guess would be to use the USB mount in twrp put on cm7 flash it.
Sent from my Full Android on Bravo using XDA App
Click to expand...
Click to collapse
Now I have nothing else works except ADB. I tried to copy the system dir by
adb push "D:\sdf\system" /sytem
but in result received message:
push: D:\sdf\system/app/Windowshop.apk -> /sytem/app/Windowshop.apk
failed to copy 'D:\sdf\system/app/Windowshop.apk' to '/sytem/app/Windowshop.apk'
: No such file or directory
What am I doing wrong?
You need to flash a zip in recovery try cm7
Sent from my Galaxy Nexus using XDA App
JackpotClavin said:
You need to flash a zip in recovery try cm7
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
With TWRP I flashed stock firmware, then decided to wipe everything. So now I have no recovery. Just sign on the screen "Kindle fire"
When I try to do adb shell I get the message "exec '/ system / bin / sh' failed: No such file or directory"
Sorry for my poor English.
If you flashed stock firmware with TWRP, then can you just not do that again?
I didnt think wiping system wiped recovery.... In fact, im sure it doesnt as I wiped system yesterday when I flashed CM7.
About the adb push thing not working. Not tried, but does ADB recognise windows formatted paths? Seems like it doesnt. Move what you are trying to copy into the adb directory and try again.
Oh lord stock overwrites the recovery. Looks like your device is broken permanently, the same thing happened to me and my first kindle. Unless you can get yourself a factory cable you are going to need to get a new one
Sent from my Galaxy Nexus using XDA App
JackpotClavin said:
Oh lord stock overwrites the recovery. Looks like your device is broken permanently, the same thing happened to me and my first kindle. Unless you can get yourself a factory cable you are going to need to get a new one
Click to expand...
Click to collapse
Sad
factory cable? Where I can get it? Can be solder?
Im confused, sorry. If you flash Stock using TWRP, and this means you lose recovery, how can you then do a system wipe using TWRP?
alchemyst said:
Im confused, sorry. If you flash Stock using TWRP, and this means you lose recovery, how can you then do a system wipe using TWRP?
Click to expand...
Click to collapse
you can wipe system...but you can't flash stock firmware, as it will install stock recovery, then you lose function over your TWRP recovery, hence the whole process halt!
ck_looi said:
you can wipe system...but you can't flash stock firmware, as it will install stock recovery, then you lose function over your TWRP recovery, hence the whole process halt!
Click to expand...
Click to collapse
Maybe you can flash twrp with the fastboot command. If you still get recognized by adb devices you are not totally lost.
Sent from my SGH-I777 using Tapatalk
warren2781 said:
Maybe you can flash twrp with the fastboot command. If you still get recognized by adb devices you are not totally lost.
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
That was my thought too. Could you use idme to set the boot mode to fastboot then use that to flash twrp and firefirefire? Even if idme isn't available, you can adb push it from a computer.
ttabbal said:
That was my thought too. Could you use idme to set the boot mode to fastboot then use that to flash twrp and firefirefire? Even if idme isn't available, you can adb push it from a computer.
Click to expand...
Click to collapse
when i try "adb shell" i get message "exec '/system/bin/sh' failed: No such file or directory"'.
ttabbal said:
Even if idme isn't available, you can adb push it from a computer.
Click to expand...
Click to collapse
What exactly should I push?
when your fire boots to the "kindle fire" screen connect it to comp and try running the "fastboot devices" command and see if it will recognize it, if it does then you are ok we can fix it if. make sure you are in <your path to sdk>/platform-tools to try the fastboot commands.
I had this problem with my first kindle. Afaik there's no way to get into fastboot without a factory cable in the current state that it's in. He's missing the sh binary that actually lets you go into the shell. He can't push to the system because he doesn't have the su binary so he cannot remount. There's no way to push files to a PATH location as they are all read only unless you're root. He needs a factory cable or he's screwed.
As for the cable itself, if you Google tbh Motorola factory cable you'll find it. You can also make one from an existing cable, just google around for a guide
Sent from my Galaxy Nexus using XDA App
JackpotClavin said:
I had this problem with my first kindle. Afaik there's no way to get into fastboot without a factory cable in the current state that it's in. He's missing the sh binary that actually lets you go into the shell. He can't push to the system because he doesn't have the su binary so he cannot remount. There's no way to push files to a PATH location as they are all read only unless you're root. He needs a factory cable or he's screwed.
As for the cable itself, if you Google tbh Motorola factory cable you'll find it. You can also make one from an existing cable, just google around for a guide
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
many thanks =). This cable looks easy, I'll try
My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
sonshadsil94 said:
My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
Click to expand...
Click to collapse
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Petrovski80 said:
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Click to expand...
Click to collapse
I know where the files are, but how am I supposed to remove or rename them without root access?
sonshadsil94 said:
I know where the files are, but how am I supposed to remove or rename them without root access?
Click to expand...
Click to collapse
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
bk201doesntexist said:
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
Click to expand...
Click to collapse
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
whats the exact fastboot command you're using to flash twrp?
problem was you made a backup of stock, which has files that restore, on boot, the stock recovery.
sent from my i9250
efrant said:
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
Click to expand...
Click to collapse
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
sonshadsil94 said:
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
Click to expand...
Click to collapse
Try using a different USB cable, and try using a different port on the back of your PC.
efrant said:
Try using a different USB cable, and try using a different port on the back of your PC.
Click to expand...
Click to collapse
I tried both of those just now, with the same error message as before.
sonshadsil94 said:
I tried both of those just now, with the same error message as before.
Click to expand...
Click to collapse
The only thing I can think of is flash the LC03 bootloader. Try flashing that first, and make sure you have the latest version of fastboot. Then try again.
would running terminal in windows with admin privileges help?
sent from my i9250
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
deeren said:
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
thanks deeren, i asked him what was the exact command he was using, that error had to be syntax error.
sent from my i9250
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
sonshadsil94 said:
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
Click to expand...
Click to collapse
please edit the title of the thread to include the tag "[SOLVED]".
bk201doesntexist said:
please edit the title of the thread to include the tag "[SOLVED]".
Click to expand...
Click to collapse
How do you edit the title?
I have same problem to...
sonshadsil94 said:
How do you edit the title?
Click to expand...
Click to collapse
Edit first post?
Sent from my i9250
hey guys i need some serious help here. so i accidentaly erased my sd card with my custom roms on it. im sitting at the "google" screen right now and my computer (windows 8 64) recognizes the phone in adb, if i go into CWM i cannot install drivers windows 8 will not let me no matter how i try. but this is my huge dilemma im trying to push the rom to my sdcard with adb and i keep getting either permission denied, or failed to copy..... is a directory. what command am i missing? i have done this plenty of times before and it worked. currently i have tried the directories on the device: /data/media/sdcard, /sdcard/, /sideload, /mnt/sdcard/ and all come back with a similar error. please help i cant figure out what is wrong.
Chyrio said:
hey guys i need some serious help here. so i accidentaly erased my sd card with my custom roms on it. im sitting at the "google" screen right now and my computer (windows 8 64) recognizes the phone in adb, if i go into CWM i cannot install drivers windows 8 will not let me no matter how i try. but this is my huge dilemma im trying to push the rom to my sdcard with adb and i keep getting either permission denied, or failed to copy..... is a directory. what command am i missing? i have done this plenty of times before and it worked. currently i have tried the directories on the device: /data/media/sdcard, /sdcard/, /sideload, /mnt/sdcard/ and all come back with a similar error. please help i cant figure out what is wrong.
Click to expand...
Click to collapse
Try /storage/sdcard0
But if that doesnt work, reboot to bootloader and flash stock userdata.img through fastboot; reboot to recovery right after that, push rom.
Sent from my i9250
I ran into the same problem, I erased my internal memory and i'm now stuck with the google screen
i have TWRP recovery but there is nothing on the sd card to flash from, how do i push files to the sd card from the computer?
I tried use the nexus root toolkit but i get "fastboot device not found" even though the bootloader says that it is in fastboot mode.
please help
nope that didnt work either but i found a work around. i had never played with CWM's sideload feature. FOR FUTURE GOOGLE GOERS
NOTE: you need CWM 6.0.1.5 and above i think
reboot into recovery
select install from sideload
make sure drivers are installed (i used the universal android drivers here: http://forum.xda-developers.com/showthread.php?t=1514942)
open up adb in cmd (hopefully you have adb in your com)
and type "adb sideload <filename.zip>" without quotes or the little arrows
and you should see it start copying
I would like CWM and TWRP for using this in their recovery!!!!!
Chyrio said:
nope that didnt work either but i found a work around. i had never played with CWM's sideload feature. FOR FUTURE GOOGLE GOERS
NOTE: you need CWM 6.0.1.5 and above i think
reboot into recovery
select install from sideload
make sure drivers are installed (i used the universal android drivers here: http://forum.xda-developers.com/showthread.php?t=1514942)
open up adb in cmd (hopefully you have adb in your com)
and type "adb sideload <filename.zip>" without quotes or the little arrows
and you should see it start copying
I would like CWM and TWRP for using this in their recovery!!!!!
Click to expand...
Click to collapse
I tried to use your sideload command but it didn't work. It said "ERROR: CLOSED"
i'm really anxious and worried if i can get the phone to work at all:crying:. any help will be greatly appreciated!
Download Wugfresh Galaxy Nexus Tool. You can't possibly have a bricked phone after using that tool
italbomber said:
Download Wugfresh Galaxy Nexus Tool. You can't possibly have a bricked phone after using that tool
Click to expand...
Click to collapse
Thank you. I tried doing that but it wasn't any help. however, i figured how to sideload using the TWRP setting. It took a little trial and error but finally got it to work.
i don't see how can you guys not get it to work through normal adb, other than you're using Windows, but glad you got it to work.
Glad to hear you are up and running again. Sorry i just always had great luck with his toolkit. Adb was always failsafe too.
Sent from my Galaxy Nexus using Tapatalk 2
Just a note you were probably getting an error because you didn't Mount the sdcard in recovery before trying to push to it.
Sent from my Galaxy Nexus using xda premium
I did a full wipe of the phone and SD card and was unable to see my phone in adb while in CWM recovery.
I run the push command any way and it did push to the file to the phone.
I push the file to /data/media/ no need to mount SDcard as it doesn't have a real one, in the past (while using ics) I have had to mount data to push files to /sdcard/
Model: GT-I9250T
Original Android version 4.04.
Root method: Gained root without having to unlock or overwrite the vanilla boot-loader and used OTA RootKeeper to backup su.
Long story short: My phone recently updated to 4.2.1 OTA. I restored root using OTA RootKeeper without issue. However when I went to restore The LBE Privacy app service, it caused my Nexus to enter a loop the moment it finishes booting and the lock screen appears.
Behavior:
After booting to the lock screen, the screen flashes and goes black then gets back to desktop and starts all over again in a loop. Once it does that about 3 or 4 times, it'll eventually get to a totally black screen except for the Android robot guy lying down with his belly open and an exclamation mark coming out. It'll then sit like that for about a minute and then the phone will reboot from scratch and the whole process repeats.
Apparently i'm not the only one either: url = badappreviews.com/apps/23315
From the linked site it looks like someone fixed it by using clockworkmod. However I don't see how that's possible as there is no way to enable usb debugging or copy any files to the sdcard as you can't boot the phone properly in the first place. I also noticed that I can no longer get into fastboot using the volume up and power button. However I can get into Odin mode.
Any ideas???
Install CWM or TWRP, wipe it clean, mount sdcard from there or adb sideload a ROM.
Sent from my Galaxy Nexus using Tapatalk 2
iLeopard said:
Install CWM or TWRP, wipe it clean, mount sdcard from there or adb sideload a ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
But how do I do that if I can't get usb debugging or get it connected to a computer or fastboot as mentioned?
Edit: nvm, looks like i am able to get into fastboot after all.Now here's hoping I can install it without having usb debugging enabled.
.DCCXVIII said:
But how do I do that if I can't get usb debugging or get it connected to a computer or fastboot as mentioned?
Edit: nvm, looks like i am able to get into fastboot after all.Now here's hoping I can install it without having usb debugging enabled.
Click to expand...
Click to collapse
Just flash the android stock image through adb and go from there. You don't need debugging access when you're in fast boot
Have I helped? Don't forget to make love to that "Thanks" button!
Download stock images and flash em via fastboot, but you will lose everything. Its the freshest start you can get.
Sent from my Nexus Prime
Seriously, do you need to 'enable debugging' to be able to use adb in recovery?? It's a completely different and independent partition.
And fastboot doesn't need any enabling at all.
So, boot to recovery
mounts and storage
mount sd card
open up a DOS box (or terminal if you're on a mac or linux)
<path to adb>/adb shell
...
profit
The ... is where you go and uninstall the app/service, like the example you found mentioned above.
Usually this would be removing a .apk from either /system/app or /data/app
Thanks for all the help, however i am unable to get the adb drivers installed. I tried both Samsung's and Google's and they both fail (Windows doesn't even recongise a driver even after pointing it to: \sdk\extras\google\usb_driver. Anyone got any other sources for a working driver? Win7 64bit.
Edit: Managed to connect it using the pdanet drivers. Then proceeded to try to load CWM using: "fastboot flash recovery *file name*.img", but just got an error: "FAILED (remote: invalid argument)". I noticed that on my fastboot menu, it says lock state: Locked. Is this why it's failing? The boot loader is still locked? Because I tried "fastboot oem unlock" and that didn't work: "FAILED (unknown status code)".
Edit: Looks like my phone just needed a reboot. Because once I did, I was able to use the fastboot oem unlock command with success! However, before I proceed with unlocking the bootloader, can someone please confirm for me that I need to do so in order to install CWM? Many thanks.
Yes, but unless you have a play store gnex, this will probably wipe your phone anyway.
Sent from my brain using telepathy
m.is.for.michael said:
Yes, but unless you have a play store gnex, this will probably wipe your phone anyway.
Sent from my brain using telepathy
Click to expand...
Click to collapse
OK, i've managed to successfully unlock the bootloader, flash CWM and used the "fix permissions" function. I lost all my data/apps etc but I now have a working phone! Many thanks to all that helped!
Hello-
I flashed Beanstalk Build 4.4.247 using Nexus Root Tool Kit & for got to include gapps in zips to be flashed. Problem is I cannot access custom recovery (TWR) not matter what I try- including holding down all combos of volume & power buttons. I can access the Android System Recovery and use "apply update from adb" option. Sideload goes well in sending update package and opening update package. At verifying update package, I keep getting "Installation aborted".
What gives hear? Any thoughts? Cannot do anything w/phone because no install wizard.
Thanks greatly.
[EDIT] Another avenue is is there a way to get Nexus Root Tool to recognize it w/out debugging enabled or enable debugging w/out having access to settings?
You dont have to enable usb debugging to use adb in recovery. Maybe its a bad download. Download the rom again and retry. Did you flash it manually or using a toolkit (manually is way better and not so hard)? If all fails maybe try CWM recovery instead of TWRP.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You dont have to enable usb debugging to use adb in recovery. Maybe its a bad download. Download the rom again and retry. Did you flash it manually or using a toolkit (manually is way better and not so hard)? If all fails maybe try CWM recovery instead of TWRP.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I flashed using Root Tool. Currently, the phone turns on, boots up, shows time date LTE battery icon etc in the status bar. However, I can go no further because I keep getting messages related to no gapps, for example "setup wizard stopped". I cannot access Nexus Root Tool because no debugging yet. Also, can't get into custom recovery in this state.
Can I install CMW in this state? I don't know why gapps won't install w/sideload.
OffcerClancy said:
I flashed using Root Tool. Currently, the phone turns on, boots up, shows time date LTE battery icon etc in the status bar. However, I can go no further because I keep getting messages related to no gapps, for example "setup wizard stopped". I cannot access Nexus Root Tool because no debugging yet. Also, can't get into custom recovery in this state.
Can I install CMW in this state? I don't know why gapps won't install w/sideload.
Click to expand...
Click to collapse
You can enter bootloader right? Just use fastboot flash recovery then.
xzilem said:
You can enter bootloader right? Just use fastboot flash recovery then.
Click to expand...
Click to collapse
I'm sorry, "use fastboot flash recovery" to do what? Install custom recovery or gapps?
Thanks greatly.
OffcerClancy said:
I'm sorry, "use fastboot flash recovery" to do what? Install custom recovery or gapps?
Thanks greatly.
Click to expand...
Click to collapse
To flash new recovery.img cwm/twrp. Then you can just dirty flash your rom and then gapps through recovery.
I would suggest twrp with easier menu. You can use adb sideload or just use usb otg to flash it.
xzilem said:
To flash new recovery.img cwm/twrp. Then you can just dirty flash your rom and then gapps through recovery.
I would suggest twrp with easier menu. You can use adb sideload or just use usb otg to flash it.
Click to expand...
Click to collapse
Got it. Thanks.
xzilem said:
To flash new recovery.img cwm/twrp. Then you can just dirty flash your rom and then gapps through recovery.
I would suggest twrp with easier menu. You can use adb sideload or just use usb otg to flash it.
Click to expand...
Click to collapse
I'm still getting the "installation aborted" message even when I try to sideload a recovery image. I want to try and push a file to the phone and use the usb flash option. When I try "adb push rom.zip /data/media/0/" or /data/media/, I get error: closed.
I believe the "error: closed" is probably related to the install aborted message.
Does any one know if the above is the proper push location to send a file to the sdcard?
OffcerClancy said:
I'm still getting the "installation aborted" message even when I try to sideload a recovery image. I want to try and push a file to the phone and use the usb flash option. When I try "adb push rom.zip /data/media/0/" or /data/media/, I get error: closed.
I believe the "error: closed" is probably related to the install aborted message.
Does any one know if the above is the proper push location to send a file to the sdcard?
Click to expand...
Click to collapse
try this;
adb push /sdcard/your_files.zip
if sideload;
adb sideload 'drag you zip file here'
OffcerClancy said:
I'm still getting the "installation aborted" message even when I try to sideload a recovery image. I want to try and push a file to the phone and use the usb flash option. When I try "adb push rom.zip /data/media/0/" or /data/media/, I get error: closed.
I believe the "error: closed" is probably related to the install aborted message.
Does any one know if the above is the proper push location to send a file to the sdcard?
Click to expand...
Click to collapse
Why do you want to transfer recovery.img to sdcard? Just use fastboot command from pc to flash your recovery img.
If you're using Windows and got unlocked bootloader Get this ADB & Fastboot Installer
Get the latest ClockworkMod Recovery or TWRP
Then use the fastboot command:
fastboot device - show your device serial number
then
fastboot flash recovery recoveryname.img
After that you can just adb sideload using the custom recovery