stuck in twrp - Nexus 5 Q&A, Help & Troubleshooting

I deleted my rom file while doing a wipe. adb sees the device, so I ran from cmd and cd'd into the platform tools directory. Then ran:
Code:
C:\Users\Administrator\Desktop\android-sdk-windows\platform-tools> adb push ROM.zip
But when I run that, I get the man pages or error:closed
At least it's good that adb sees my device after running adb devices. Is there something wrong with the way I'm trying to push the rom over?

You need to tell it what to push it. \sdcard\download. Or something along those lines
Sorry, you need to use / not \
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You need to tell it what to push it. \sdcard\download. Or something along those lines
Sorry, you need to use / not \
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm trying eveything I can think of, but still nothing. So close.
When I run adb status-window I get:
<-[2J<-[2HAndroid Debug Bridge
State: sideload

did you try adb push ROM.zip /sdcard/ROM.zip but changing the name ROM.zip to whatever the exact name of your file is?

goofball2k said:
did you try adb push ROM.zip /sdcard/ROM.zip but changing the name ROM.zip to whatever the exact name of your file is?
Click to expand...
Click to collapse
I just tried that, and got:
error:closed
Ran the original command with sideload:
C:\Users\Administrator\Desktop\android-sdk-windows\platform-tools> adb sideload ROM.zip
and got:
* failed to write data 'protocol fault <no status>' * 1%

If all else fails, just flash stock, reroot and start fresh.
Return to Stock

OK, I got it done. I rebooted the phone back into recovery mode, and ran the original command which finally worked. I got a new rom installed successfully! Thanks for the help guys, all is well, and lesson learned.

wolfen69 said:
I'm trying eveything I can think of, but still nothing. So close.
When I run adb status-window I get:
Sorry didnt noticed that you tried
Click to expand...
Click to collapse

Related

[Q] help getting update.zip to my sdcard

Did something to my captivate, when it starts and gets to the desktop, it stops force closing the launch and android accore something. I have no way of getting to anything, settings or otherwise.
I'm able to get it into recovery mode, but if i run reinstall packages it says it can't open /sdcard/update.zip.
I can connect to adb and see the device, but i can't seem to push the update.zip to it. I also have a $ i thought it should be a #.
Any ideas on how to proceed, no way to get into anything on the phone, and adb is acting odd. It shows:
List of devices attached
I89789fda6da recovery
If an aftermarket launcher is your problem, use adb uninstall to get rid of it or any other apk that is causing problems.
its the actual launcher thats erroring out - I can't even figure out how to get adb to let me browse the files on the phone. I have the update file that will resolve the issue, but no way to get it to the internal sdcard
JacenSolo2001 said:
its the actual launcher thats erroring out - I can't even figure out how to get adb to let me browse the files on the phone. I have the update file that will resolve the issue, but no way to get it to the internal sdcard
Click to expand...
Click to collapse
in order to push files I think you need root. if you've rooted your phone, use the su command to get the # prompt, which is super user status.
ok, here's where I'm at:
Android system recovery screen, with the 4 options, reboot, reinstall packages (which can't find the zip file), and the 2 deletes. This is the only place i can use adb at from here:
I do an adb devices and get
List of devices attached
I89789fda6da recovery
So at this point, is there a way anyone knows of to get the zip file to the internal sdcard?
oh and btw: the phone is rooted
Do you have busybox on the phone? If you do, do this:
Code:
adb shell
cd /sdcard/
busybox wget <url to update.zip>
i don't think busybox is on there any longer, it just says busybox: not found
dewt said:
Do you have busybox on the phone? If you do, do this:
Code:
adb shell
cd /sdcard/
busybox wget <url to update.zip>
Click to expand...
Click to collapse
I don't get it: what wget will get? Are you saying I need a web-server on my windows laptop?
Please be more specific: update.zip sits on my D:\tmp. How wget will see it?
Example please
JacenSolo2001 said:
Did something to my captivate, when it starts and gets to the desktop, it stops force closing the launch and android accore something. I have no way of getting to anything, settings or otherwise.
I'm able to get it into recovery mode, but if i run reinstall packages it says it can't open /sdcard/update.zip.
I can connect to adb and see the device, but i can't seem to push the update.zip to it. I also have a $ i thought it should be a #.
Any ideas on how to proceed, no way to get into anything on the phone, and adb is acting odd. It shows:
List of devices attached
I89789fda6da recovery
Click to expand...
Click to collapse
If you can get into recovery mode, have you tried a master clear? If you can't copy files via ADB and you can't use any apps on your phone, then that is your only choice. Or an Odin one click restore to stock.
alphadog00 said:
If you can get into recovery mode, have you tried a master clear? If you can't copy files via ADB and you can't use any apps on your phone, then that is your only choice. Or an Odin one click restore to stock.
Click to expand...
Click to collapse
Exactly what I was thinking. It doesn't make sense to be trying so hard to fix that when a simple one click Odin will remedy the problem.
Sent from my Captivate

( Clockworkmod Installation:Please, need Help )

Hey guy's, I've beentrying to install clockworkmod on my Epic for some time now to no avail. See, I just rooted my phone using the noobnl's "one click method v2.2.6". The only recovery I have on my phone as of right now is tthe stock recovery. I've read just about every post about the installation on clockworkmod recovery and tried accordingly. Still no custom ecovery. Im really noob to all this "wiz stuff", and would greatly appreciate any help you guy's could give me. Perhaps some DETAILED step by step instructions ( CUZ IM REAL BRAIN DEAD AT TIMES )?? I have DI11 installed on my phone as of now, and im running the stock kernel v2.6.29. again, Im rooted with "noobnl's one click" and I do have root. Also, I need to know if you download to my pc, then push it to my phone using command prompt? Do I flash it with Odin? And what do I do after I run the clockworkmod exploit? Will I have custom recovery after that, is there anymore steps involved? Thank you all for making this site the best web site I"ve been on so far. You guy's are the best. Please hel[p with my dumb question, and sorry to waste your time. Thankx IA..
http://forum.xda-developers.com/showthread.php?t=782300
Download the .zip from that. Extract it to your desktop and rename the folder "cwm". Open up command prompt. Type this:
Code:
cd C:\Users\YOUR USER NAME\Desktop\cwm
adb shell
su
remount rw
exit
exit
After that, run the run.bat from the folder.
Download the .zip from that. Extract it to your desktop and rename the folder "cwm". Open up command prompt. Type this:
Code:
cd C:\Users\YOUR USER NAME\Desktop\cwm
adb shell
su
remount rw
exit
exit
After that, run the run.bat from the folder.
Click to expand...
Click to collapse
Excuse the stupid question please, do I have the sdcard mounted, or unmounted? I heard it can be done either way...
The only thing you use Odin for is to flash a complete .tar file. Ie, returning to stock, or updating to a new release DG27, DI07, or DI18
sniperkill said:
Excuse the stupid question please, do I have the sdcard mounted, or unmounted? I heard it can be done either way...
Click to expand...
Click to collapse
Make sure it is NOT mounted as a mass storage device. Make sure you can access it from the phone. So, don't mount it.
LSanna1488 said:
The only thing you use Odin for is to flash a complete .tar file. Ie, returning to stock, or updating to a new release DG27, DI07, or DI18
Click to expand...
Click to collapse
Technically, custom ROMs can be made for Odin, too... But since it's not a very good method, everyone prefers the recovery method. noobnl released his first rooted kernel for Odin. Odin does a lot more than just complete .tars.
LSanna1488 said:
The only thing you use Odin for is to flash a complete .tar file. Ie, returning to stock, or updating to a new release DG27, DI07, or DI18
Click to expand...
Click to collapse
I ran the commands as you stated, then ran the exploit. It keeps saying,
"remove stock recovery patcher"
"device not found"
system (something) install recovery.sh permission denied
"system/recovery-from-boot.p permission denied
failed to copy 'zImage' to /sdcard/zImage: permission denied
reboot: operation not permitted
im failed for /sdcard/zImage, permission denied
So what do you think is going on? Any thoughts?
I had same exact issue. Went back to completely stock then rooted then did clockwork. Do not mount sd card. Follow instructions exactly.
Sent from my SPH-D700 using XDA App
I'm having the same issue. When trying to 'su' to do the remount I'm getting a permission denied... but apps that require root seem to be working.
sniperkill said:
I ran the commands as you stated, then ran the exploit. It keeps saying,
"remove stock recovery patcher"
"device not found"
system (something) install recovery.sh permission denied
"system/recovery-from-boot.p permission denied
failed to copy 'zImage' to /sdcard/zImage: permission denied
reboot: operation not permitted
im failed for /sdcard/zImage, permission denied
So what do you think is going on? Any thoughts?
Click to expand...
Click to collapse
Is your phone in debug mode? (Settings -> Applications -> Development -> USB Debugging) Did it actually let your run those commands I told you?
Yes, my phone is in fact in debugg mode. My desktop command prompt does let me run the commands.
Adb devices
Adb shell
Su #
Remount rw
Exit
Exit
After I type the command "su" it gives me the #. Then on my phone a superuser request comes thru and askes to chose "yes" or "no". So I hit "yes". But when I run the exploit in the beginning it says "mount", and it says that the operation is not permitted... then it starts saying "I'm failed for" and "operation not permitted" and so on.. I think I'm missing a step somewhere but I don't kno...
Sent from my SPH-D700 using XDA App
Running su through adb shouldn't ask for permission the phone... that is weird.
Sent from my SPH-D700 using XDA App
I spent the weekend trying to get my Epic rooted and cwm installed. I was finally successful with both. CWM I had to install by typing in each command that was in the bat through the cmd window with adb.
Flak said:
I spent the weekend trying to get my Epic rooted and cwm installed. I was finally successful with both. CWM I had to install by typing in each command that was in the bat through the cmd window with adb.
Click to expand...
Click to collapse
So exactly what are the steps you took to install clockworkmod manually through windows command prompt? Do I just look in the bat exploit?

[Q] Samsung 4g Exhibit framework-res.apk HELP PLEASE ILL GIVE THANKS 2 ALL

i have a Samsung Exhibit 4g phone, rooted and backed up by titanium backup. I tried using the kitchen theme stuff, and i copied the original framework-res.apk file to a folder in the sd card . Then i copied the framework-res.apk file from the UOT zip to the location where the original file was and rebooted the phone. Now my phone is stuck at the Samsung logo screen and it keeps looping. anyway to fix this? :/
P.S: the location i copied the original file doesnt show up in the recovery menu when i go to install package. Also, when i tried the downloading mode, it just says downloading and doesnt do anything. Tried factory restore too. The original file is somewhere on the sd card i just dont know how to access it and put it back into its original location.... no i dont have a copy of it on my computer.
Follow this guide
If you are in a loop, you have to manage this fast or else it will just reboot again, i suggest a copy and paste function for the third command. also I don't know for sure whether /dev/block/st19 is your /system partition, but i'll try.
Code:
adb shell
Code:
su
Code:
mount -o rw,remount /dev/block/st19 /system
Code:
exit
Code:
adb push /pathtoyour"ORIGINAL"frameworkres /system/framework
PS, Do this within 15-20 seconds. (You will have multiple attempts as you can do it after every loop)
once you are done, just hard reboot your phone(using power button)
Also you do this in a terminal/cmd window with your phone plugged in.
wait
airfluip1 said:
If you are in a loop, you have to manage this fast or else it will just reboot again, i suggest a copy and paste function for the third command. also I don't know for sure whether /dev/block/st19 is your /system partition, but i'll try.
Code:
adb shell
Code:
su
Code:
mount -o rw,remount /dev/block/st19 /system
Code:
exit
Code:
adb push /pathtoyour"ORIGINAL"frameworkres /system/framework
PS, Do this within 15-20 seconds. (You will have multiple attempts as you can do it after every loop)
once you are done, just hard reboot your phone(using power button)
Also you do this in a terminal/cmd window with your phone plugged in.
Click to expand...
Click to collapse
wait, sorry im new to this stuff, but i plug in my phone to the computer and then type all of that into cmd while the phone is turning on right? Ill give it a try, but also, i tried using odin before but my computer just doesnt detect the phone all the drivers are install and everything too... so idk if this willl work but ill try and let you know
edit: i tried it, and umm sorry again for being a noob, i plugged in the phone and the battery screen cameup, i opened cmd.exe, turned the phone on and typed "adb shell" in cmd, but uh it said its not a command...
I am sorry, I assumed you had installed the Android SDK.
Google it.
Sent from my SGH-T959V using xda premium
Then install the Samsung composite drivers. Google them.
Then retry the process.
I can guaranty that it will work.
Sent from my SGH-T959V using xda premium
downloaded
airfluip1 said:
Then install the Samsung composite drivers. Google them.
Then retry the process.
I can guaranty that it will work.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
http://www.samsung.com/us/support/owners/product/SGH-T759ZKBTMB
i downloaded them 2 weeks ago already.... that is if that is what your talking about... i tried it again and it also gave me the message Samsung Android Modem has already been installed or something
OK, but did you install the sdk?
Dowload and install the JDK(just choose the one for your OS) LINK
Then install the SDK from android LINK

RUU File for RADIO-26.17.14.11_M

Hi,
I have the HTC Inspire 4g with:
Software #: 3.20.502.52 710RD
Android Version 2.3.5
HTC Sense 3.0
Baseband version: 12.69a.60.29u_26.17.14.11_M
I have unlocked the bootloader using htcdev and have successfully rooted the the device but i'm still S-ON. I have tried installing some custom ROMs however after flashing the device did not boot. I understand that I have to flash the boot.img file located in the .zip file of the custome ROM. That I know how to do... My concern is that I want to try out some ROMs but as a precaution I would like to have the stock RUU file for the type device I have should I need to restore it.
I did create a backup of my ROM and have used it previously to restore the phone after installing the custom roms that haven't boot. I just want to know if I flash the boot.img file will a restore bring it back to where it was before the flash or do i need the RUU file to restore stock?
If the later please advice where I can find that particular file as I've searched but can't seem to find the one to use.
Thanks a million.
360fifa
360fifa said:
Hi,
I have the HTC Inspire 4g with:
Software #: 3.20.502.52 710RD
Android Version 2.3.5
HTC Sense 3.0
Baseband version: 12.69a.60.29u_26.17.14.11_M
I have unlocked the bootloader using htcdev and have successfully rooted the the device but i'm still S-ON. I have tried installing some custom ROMs however after flashing the device did not boot. I understand that I have to flash the boot.img file located in the .zip file of the custome ROM. That I know how to do... My concern is that I want to try out some ROMs but as a precaution I would like to have the stock RUU file for the type device I have should I need to restore it.
I did create a backup of my ROM and have used it previously to restore the phone after installing the custom roms that haven't boot. I just want to know if I flash the boot.img file will a restore bring it back to where it was before the flash or do i need the RUU file to restore stock?
If the later please advice where I can find that particular file as I've searched but can't seem to find the one to use.
Thanks a million.
360fifa
Click to expand...
Click to collapse
RUU 3.20.502.52
Thank you kindly for taking the time to respond and also help.
Hi Gizmoe,
is there a rooted and s-off RUU file I could use as well?
Thanks again..
360fifa said:
Hi Gizmoe,
is there a rooted and s-off RUU file I could use as well?
Thanks again..
Click to expand...
Click to collapse
RUU 's can not be modified. You will not lose s off however by running an ruu. After you run ruu just pd98img a recovery and flash away.
Gizmoe said:
RUU 's can not be modified. You will not lose s off however by running an ruu. After you run ruu just pd98img a recovery and flash away.
Click to expand...
Click to collapse
So are you saying that I would need to unlock the bootloader again then following the same steps I have now? I had the impression based off could threads I've read that there's a way to root the device while gaining S-OFF that will allow me to avoid having to manually flash the boot.IMG everytime i install a custom rom. If there's a thread I can read or a guide to follow please provide a link so that I can proceed. Oh, does all the pd98img file the same?
Thanks again.
360fifa
360fifa said:
So are you saying that I would need to unlock the bootloader again then following the same steps I have now? I had the impression based off could threads I've read that there's a way to root the device while gaining S-OFF that will allow me to avoid having to manually flash the boot.IMG everytime i install a custom rom. If there's a thread I can read or a guide to follow please provide a link so that I can proceed. Oh, does all the pd98img file the same?
Thanks again.
360fifa
Click to expand...
Click to collapse
Yeah that's right. Your not s off. Well here is the only method left for the inspire. It may be a bit intimidating but really isn't that hard. Here is link.
http://tau.shadowchild.nl/attn1/?cat=6
Gizmoe said:
Yeah that's right. Your not s off. Well here is the only method left for the inspire. It may be a bit intimidating but really isn't that hard. Here is link.
Click to expand...
Click to collapse
Your're right very intimidating, however I'm willing to try my only concern is what is dd highlighted below "High Level Steps (some detail deliberately NOT included)
htc dev unlock, install cwm recovery and root ONLY
dd the stock boot image to /data/local/tmp and pull it to your pc HD (/dev/block/mmcblk0p22 is boot)
adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img"?
Also i navigated to the folder on my device however it doesn't show any boot.img file. Just a init.rc file. Could you explain just this part of it please?
Thanks again,
360fifa
360fifa said:
Your're right very intimidating, however I'm willing to try my only concern is what is dd highlighted below "High Level Steps (some detail deliberately NOT included)
htc dev unlock, install cwm recovery and root ONLY
dd the stock boot image to /data/local/tmp and pull it to your pc HD (/dev/block/mmcblk0p22 is boot)
adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img"?
Also i navigated to the folder on my device however it doesn't show any boot.img file. Just a init.rc file. Could you explain just this part of it please?
Thanks again,
360fifa
Click to expand...
Click to collapse
DD is copy and convert. It will copy boot files and convert it into boot.img. Use adb shell to do it as shell works within phone directories. Then pull it from pc using adb pull. He is giving you the exact adb commands to do both.
Code:
adb shell
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img
Gizmoe said:
DD is copy and convert. It will copy boot files and convert it into boot.img. Use adb shell to do it as shell works within phone directories. Then pull it from pc using adb pull. He is giving you the exact adb commands to do both.
Code:
adb shell
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img
Click to expand...
Click to collapse
Lol... I figured those were the commands to use, was just wondering what dd stand for.. ( copy and convert ). So let me see if i understand whats happening in the code.
So firstly I need to have the the HTC drivers installed and have the Android SDK on the root of c drive. Basically the same folder used when I unlocked to bootloader. In that folder I have the adb files, should I also add the files listed in the zip file he provided? If so let me explain the code, if no please shed some light.
So adb shell starts the emulator with the device
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot will copy and convert the mmcblk0p22 file if it is found in the /dev/block folder on the device and place it to the /data/local/tmp/ folder and call it boot.img
adb pull /data/local/tmp/boot.img I'm thinking that the computer is going to pull the boot.IMG file from the /data/local/tmp folder however where is it putting it? In the same folder that I started the command prompt from? That is the Android folder on my c drive?
360fifa said:
Lol... I figured those were the commands to use, was just wondering what dd stand for.. ( copy and convert ). So let me see if i understand whats happening in the code.
So firstly I need to have the the HTC drivers installed and have the Android SDK on the root of c drive. Basically the same folder used when I unlocked to bootloader. In that folder I have the adb files, should I also add the files listed in the zip file he provided? If so let me explain the code, if no please shed some light.
So adb shell starts the emulator with the device
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot will copy and convert the mmcblk0p22 file if it is found in the /dev/block folder on the device and place it to the /data/local/tmp/ folder and call it boot.img
adb pull /data/local/tmp/boot.img I'm thinking that the computer is going to pull the boot.IMG file from the /data/local/tmp folder however where is it putting it? In the same folder that I started the command prompt from? That is the Android folder on my c drive?
Click to expand...
Click to collapse
You will want to work out of the platform-tools directory.
Yes adb pull will always pull to your working directory unless another path is specified. Adb shell will need root. So if you type adb shell and don't see a # sign type su to get it. When done in adb shell you will need exit so you can pull to computer. If you had to take two steps to get a # prompt then you will type exit twice.
Gizmoe said:
You will want to work out of the platform-tools directory.
Yes adb pull will always pull to your working directory unless another path is specified. Adb shell will need root. So if you type adb shell and don't see a # sign type su to get it. When done in adb shell you will need exit so you can pull to computer. If you had to take two steps to get a # prompt then you will type exit twice.
Click to expand...
Click to collapse
Kool, thats the directory i'm referring to... I'm sure i'm already rooted. But your saying that when i send the command "adb shell" if I don't see the # sign then i should type su. Are you then saying that if I had to type su twice then I need to hit exit twice to pull to pc?
Oh before I forget should i run ruu before attempting this or remain as is? Also, do I need cmw recovery installed or can i remain on twrp 2.6.0.0?
Thanks again bro..
360fifa
360fifa said:
Kool, thats the directory i'm referring to... I'm sure i'm already rooted. But your saying that when i send the command "adb shell" if I don't see the # sign then i should type su. Are you then saying that if I had to type su twice then I need to hit exit twice to pull to pc?
Oh before I forget should i run ruu or remain as is?
Thanks again bro..
360fifa
Click to expand...
Click to collapse
Yes you would need to type su to see #. Adb shell root access works independently of phone root. It needs root access over adb which without an UN-secure boot img will need the su command. Exit for each level. Once for su and once for shell itself. You want to exit until you are back at Windows directory. Adb shell is at the phones root directory. The dd command is moving files within the phone, while Adb pull would be used to copy from phone to pc. I would not run that ruu if you are going to try and s off. I would run 2.47.502.7. Which I posted a link in the att stock Rom thread.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
http://forum.xda-developers.com/showthread.php?p=50027824
Gizmoe said:
Yes you would need to type su to see #. Adb shell root access works independently of phone root. It needs root access over adb which without an UN-secure boot img will need the su command. Exit for each level. Once for su and once for shell itself. You want to exit until you are back at Windows directory. Adb shell is at the phones root directory. The dd command is moving files within the phone, while Adb pull would be used to copy from phone to pc. I would not run that ruu if you are going to try and s off. I would run 2.47.502.7. Which I posted a link in the att stock Rom thread.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
http://forum.xda-developers.com/showthread.php?p=50027824
Click to expand...
Click to collapse
Do i need to run a ruu or can I proceed as is? If so u recommend running the 2.47.502.7 ruu before going thru the adb commands, y?
Thanks again..
360fifa said:
Do i need to run a ruu or can I proceed as is? If so u recommend running the 2.47.502.7 ruu before going thru the adb commands, y?
Thanks again..
Click to expand...
Click to collapse
Yes go ahead and proceed as is. You should not have any issues. If not successful then try ruu. You may not be able to run the older ruu if your bootloader is newer. Which in that case just run the newer one. I beleive I used this process on a phone with the newer software but the older works for sure.
Gizmoe said:
Yes go ahead and proceed as is. You should not have any issues. If not successful then try ruu. You may not be able to run the older ruu if your bootloader is newer. Which in that case just run the newer one. I beleive I used this process on a phone with the newer software but the older works for sure.
Click to expand...
Click to collapse
Gizmoe you have been very patient and very helpful i thank you a million times. If i encounter any other issues I'll definitely let you know.
Thanks again..
360fifa
360fifa said:
Gizmoe you have been very patient and very helpful i thank you a million times. If i encounter any other issues I'll definitely let you know.
Thanks again..
360fifa
Click to expand...
Click to collapse
I encountered an issue while trying to pull the boot.img file from /data/local/tmp/. The command used was adb pull /data/local/tmp/boot.img I then got a msg saying the adb is not a command, if I remove the adb and send the command with just pull it says pull is not a command.
If I exit su "#" it brings me to $ and if I send the command again it says that I don't have permission. Can you advise what I might be doing wrong? Oh, I got the mmcblk0p22 file to copy and convert into the boot.img file. I was able to see it using ES File explorer on my phone.
Do I need to go in fastboot usb, does unknown sources need to be checked?
Thanks again.
360fifa said:
I encountered an issue while trying to pull the boot.img file from /data/local/tmp/. The command used was adb pull /data/local/tmp/boot.img I then got a msg saying the adb is not a command, if I remove the adb and send the command with just pull it says pull is not a command.
If I exit su "#" it brings me to $ and if I send the command again it says that I don't have permission. Can you advise what I might be doing wrong? Oh, I got the mmcblk0p22 file to copy and convert into the boot.img file. I was able to see it using ES File explorer on my phone.
Do I need to go in fastboot usb, does unknown sources need to be checked?
Thanks again.
Click to expand...
Click to collapse
You need to exit one more time so you can see c prompt with your platform tools folder. Your still in shell therefore still in phone and not actually pulling to your pc. Only the pc uses Adb commands so you have to be at your platform tools folder. If you restart your phone temp empties too so if you can't see boot img anymore that's why.
Gizmoe said:
You need to exit one more time so you can see c prompt with your platform tools folder. Your still in shell therefore still in phone and not actually pulling to your pc. Only the pc uses Adb commands so you have to be at your platform tools folder. If you restart your phone temp empties too so if you can't see boot img anymore that's why.
Click to expand...
Click to collapse
Okay.. I am going to try that now, I swore I did that as well but lets see.
360fifa said:
Okay.. I am going to try that now, I swore I did that as well but lets see.
Click to expand...
Click to collapse
Here's what it said "failed to copy '/data/local/tmp/boot.img' to ' ./boot.img': Permission denied

Is there a way to delete/uninstall an APK and its data from fastboot?

so i went into FKU franco kernel updater and changed my CPU max speed from 1500 back to the default but did not change my voltage settings back to default. now the device is softbrocked and just boots to the google nexus splash screen
I have tried flashing:
system.img
boot.img
bootloader.img
stock 4.4.4 kernel
yet regardless of flashing the above the device still is softbricked and wont get past the nexus google logo.
the only thing i have not flashed over is my user data and thats because i dont want to lose my pictures and video of my little boy that i didn't get to back up yet due to my dropbox just hitting its limit.
Im hoping I can remove the franco updater app and its user data and boot but maybe thats not possible?
Thanks for any and all help!
nextelbuddy said:
so i went into FKU franco kernel updater and changed my CPU max speed from 1500 back to the default but did not change my voltage settings back to default. now the device is softbrocked and just boots to the google nexus splash screen
I have tried flashing:
system.img
boot.img
bootloader.img
stock 4.4.4 kernel
yet regardless of flashing the above the device still is softbricked and wont get past the nexus google logo.
the only thing i have not flashed over is my user data and thats because i dont want to lose my pictures and video of my little boy that i didn't get to back up yet due to my dropbox just hitting its limit.
Im hoping I can remove the franco updater app and its user data and boot but maybe thats not possible?
Thanks for any and all help!
Click to expand...
Click to collapse
Do you have a custom recovery? If so, use adb while in recovery to pull your files. If not, then flash one then pull them.
Not sure why you mentioned "boot.img" then "stock 4.4.4 kernel", boot.img = the kernel lol
Don't know why your device won't boot even after flashing stock boot.img, but if you use TWRP you can use the file manager to delete the .apk/other files.
Lethargy said:
Do you have a custom recovery? If so, use adb while in recovery to pull your files. If not, then flash one then pull them.
Not sure why you mentioned "boot.img" then "stock 4.4.4 kernel", boot.img = the kernel lol
Don't know why your device won't boot even after flashing stock boot.img, but if you use TWRP you can use the file manager to delete the .apk/other files.
Click to expand...
Click to collapse
thanks, i deleted the franco files and still cant boot.
i want top pull files but it looks like I need ADB and currently i can only get into fastboot mode.
(i'm using wugfresh toolkit, i know some say manual is the way to go but right now this is what I have to go on and have had no issues thus far with it)
i was using the button pull files in the tool kit but its not detecting the device since im in fastboot mode.
i swear I did a factory reset before and my photos were still present but many articles online say in 4.4 that a factory reset will wipe your photos.
nextelbuddy said:
thanks, i deleted the franco files and still cant boot.
i want top pull files but it looks like I need ADB and currently i can only get into fastboot mode.
(i'm using wugfresh toolkit, i know some say manual is the way to go but right now this is what I have to go on and have had no issues thus far with it)
i was using the button pull files in the tool kit but its not detecting the device since im in fastboot mode.
i swear I did a factory reset before and my photos were still present but many articles online say in 4.4 that a factory reset will wipe your photos.
Click to expand...
Click to collapse
Don't use toolkits. You say you've had no issues but you have and that issue is that you don't know how to use adb and fastboot
Click the link in my signature to get to the sticky roll -up thread. From there you will find my "adb and fastboot. What is it?" thread. Please read it. You'll have ALL the information you need to get your photos etc off your sdcard
Stock recovery - factory reset wipes sdcard
Custom recovery - factory reset preserves sdcard
Sent from my Nexus 5 using Tapatalk
rootSU said:
Don't use toolkits. You say you've had no issues but you have and that issue is that you don't know how to use adb and fastboot
Click the link in my signature to get to the sticky roll -up thread. From there you will find my "adb and fastboot. What is it?" thread. Please read it. You'll have ALL the information you need to get your photos etc off your sdcard
Stock recovery - factory reset wipes sdcard
Custom recovery - factory reset preserves sdcard
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks,
since i can not boot, i am forced to use TWRP recovery and then go ingo CMD shell and ADB there however when I do ADB Devices i get the serial number showing its connected but then it says RECOVERY at the end.. much lke when you are in fastboot it says FASTBOOT at the end of the device.
i tried doing a pull using this:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
but when I do ADB Shell, the command prompt says this
~ # ←[6n
if t that prompt i type mount data then I get this:
mount data
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
~ # ←[6n
im not sure how else to get to a working ADB to perform a proper pull if i cant boot into the device fully
nextelbuddy said:
Thanks,
since i can not boot, i am forced to use TWRP recovery and then go ingo CMD shell and ADB there however when I do ADB Devices i get the serial number showing its connected but then it says RECOVERY at the end.. much lke when you are in fastboot it says FASTBOOT at the end of the device.
i tried doing a pull using this:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
but when I do ADB Shell, the command prompt says this
~ # ←[6n
if t that prompt i type mount data then I get this:
mount data
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
~ # ←[6n
im not sure how else to get to a working ADB to perform a proper pull if i cant boot into the device fully
Click to expand...
Click to collapse
It could say "device busy" if data is already mounted. Does twrp have a "mounts and storage" menu like CWM? Where you can mount data? If so, check if it is mounted there (would typicall say "unmount data" if it was mounted, otherwise it would say "mount data" if it is unbmounted)
nextelbuddy said:
Thanks,
since i can not boot, i am forced to use TWRP recovery and then go ingo CMD shell and ADB there however when I do ADB Devices i get the serial number showing its connected but then it says RECOVERY at the end.. much lke when you are in fastboot it says FASTBOOT at the end of the device.
i tried doing a pull using this:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
but when I do ADB Shell, the command prompt says this
~ # ←[6n
if t that prompt i type mount data then I get this:
mount data
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
~ # ←[6n
im not sure how else to get to a working ADB to perform a proper pull if i cant boot into the device fully
Click to expand...
Click to collapse
ok so i went into TWRP and UNMOUNTED DATA
and then I went back in to cmd prompt and tried mount again and it worked i guess since theres no error. I typed EXIT and was brought back to normal windows command prompt. I then typed
adb pull data/media/0 C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM
and when I hit enter it just shows a list of ADB commands as if it didnt recognize anything yet when I do ADB DEVICES it shows the device and ID
nextelbuddy said:
ok so i went into TWRP and UNMOUNTED DATA
and then I went back in to cmd prompt and tried mount again and it worked i guess since theres no error. I typed EXIT and was brought back to normal windows command prompt. I then typed
adb pull data/media/0 C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM
and when I hit enter it just shows a list of ADB commands as if it didnt recognize anything yet when I do ADB DEVICES it shows the device and ID
Click to expand...
Click to collapse
If you're going to put spaces in your folder names, you'll have to enclose the entire path in "...
Example
adb pull data/media/0 "C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM"
Best to avoid spaces though.
I'll put this in the guide, thanks.
rootSU said:
If you're going to put spaces in your folder names, you'll have to enclose the entire path in "...
Example
adb pull data/media/0 "C:\Users\srobertson\Desktop\Nexus 5 7-15-2014 DCIM"
Best to avoid spaces though.
I'll put this in the guide, thanks.
Click to expand...
Click to collapse
Thanks so much for your help
I ended up taking the leap and performing a Factory reset from TWRP and when I logged back into the phone I saw all my media was still present Whew.
just for posterity I went ahead and tried your code in ADB to make sure the quotes worked and it did so thank you very much and i will keep those notes handy for next time.

Categories

Resources