@thecubed here are the the files and post that you requested for the F460. All 4 are in that zip
https://www.dropbox.com/s/cknccza84vsn6hw/F460S.zip?dl=0
and this is post #1000!
Pilz said:
@thecubed here are the the files and post that you requested for the F460. All 4 are in that zip
https://www.dropbox.com/s/cknccza84vsn6hw/F460S.zip?dl=0
and this is post #1000!
Click to expand...
Click to collapse
Did you know how can I push to my sd card the partitions.txt file using terminal emulator and not a PC?
jamm513 said:
Did you know how can I push to my sd card the partitions.txt file using terminal emulator and not a PC?
Click to expand...
Click to collapse
Terminal emulator should work of you use the proper commands.
Pilz said:
Terminal emulator should work of you use the proper commands.
Click to expand...
Click to collapse
Yes, I know, I push the 4 partitions need it, but I can't push the partitions.txt files to my sd card.
I'm using this command, but can't read the file.
cat /proc/partitions >> /data/media/0/partitions.txt
Maybe @thecubed can help me.
jamm513 said:
Yes, I know, I push the 4 partitions need it, but I can't push the partitions.txt files to my sd card.
I'm using this command, but can't read the file.
cat /proc/partitions >> /data/media/0/partitions.txt
Maybe @thecubed can help me.
Click to expand...
Click to collapse
Are you moving the partitions that I posted? Those the boot partitions why do you need to move them onto your phone?
Pilz said:
Are you moving the partitions that I posted? Those the boot partitions why do you need to move them onto your phone?
Click to expand...
Click to collapse
No, course not, I have a D855p, I'm just trying to push out the partitions.txt file from.my device.
jamm513 said:
No, course not, I have a D855p, I'm just trying to push out the partitions.txt file from.my device.
Click to expand...
Click to collapse
Ok I was just making sure. Have you tried to manually move them via a root explorer?
Related
ADB was working for awhile then quit.
Can someone please help me?
In command prompt it says "ADB is not an internal or external command, operable program or batch file"
Do you install the Sync software?
laufine said:
Do you install the Sync software?
Click to expand...
Click to collapse
Yes, I've tried it with and without.
I recently deleted the Sync, should I reinstall it?
I'll post the drivers. Here is the link.
http://www.megaupload.com/?d=PU08Q26S
You can try manual install the drivers.
Hero's Hero said:
ADB was working for awhile then quit.
Can someone please help me?
In command prompt it says "ADB is not an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
You have to either put it in your path, or cd to the directory where adb is contained.
Example:
cd \android-sdk-windows\tools
Then run your adb commands. That error message you're getting is because the OS doesn't know the adb executable exists.
smw6180 said:
You have to either put it in your path, or cd to the directory where adb is contained.
Example:
cd \android-sdk-windows\tools
Then run your adb commands. That error message you're getting is because the OS doesn't know the adb executable exists.
Click to expand...
Click to collapse
i was just about to type this up then saw this as the last post. Good work man
laufine said:
I'll post the drivers. Here is the link.
http://www.megaupload.com/?d=PU08Q26S
You can try manual install the drivers.
Click to expand...
Click to collapse
I have all the drivers
smw6180 said:
You have to either put it in your path, or cd to the directory where adb is contained.
Example:
cd \android-sdk-windows\tools
Then run your adb commands. That error message you're getting is because the OS doesn't know the adb executable exists.
Click to expand...
Click to collapse
I have them in the path, but no beauno
Hero's Hero said:
I have them in the path, but no beauno
Click to expand...
Click to collapse
Where is your SDK installed to?
DevinXtreme said:
Where is your SDK installed to?
Click to expand...
Click to collapse
It's in C:/
Hero's Hero said:
It's in C:/
Click to expand...
Click to collapse
And you've tried running this before any adb commands, right?
Code:
cd C:\android-sdk-windows*\tools
*Or whatever you named that folder
I've Had this issue. I Had to un-install the sync And sdk. Then install them right back on lol.Reloaded the vista drivers then Im back Tim. That is if its a Driver issue
-------------------------------------
Sent via the XDA Tapatalk App
Do you still need help with this? I can help you out
regaw_leinad said:
Do you still need help with this? I can help you out
Click to expand...
Click to collapse
Yes I do.
Would really appreciate it.
It seems you're on your way to receiving help. However, if you're still in limbo, locate your android folder or adb executable, right click, copy the location, and paste it into a follow-up reply. This is with respect to the diagnosis process.
Either way, I hope you're headed in the right direction to solve your slight dilemma.
Is there a way on the Vibrant to flash *.zip files like on the Nexus One? For example, I have a Mobile Defense as System App *.zip file that on the N1 I flash from the Recovery menu. Is this possible on the Vibrant? How else can I install System Apps?
it will be posible to flash .zip files in recovery once we get a custom recovery. there is a guy working on porting clockwork as we speak so it souldnt be too long before we can flash roms and kernals and other .zip stuff
hah2110 said:
Is there a way on the Vibrant to flash *.zip files like on the Nexus One? For example, I have a Mobile Defense as System App *.zip file that on the N1 I flash from the Recovery menu. Is this possible on the Vibrant? How else can I install System Apps?
Click to expand...
Click to collapse
You can only use the .zip flash function on the phone to manipulate some files. If you wanted to add a completely new rom you must use Odin. The clockwork recovery being done is still in it's very basic stage where nothing is working. So it's impossible to tell if they will get it to work especially since the bootloader is completely different from all other android phones.
Why not just inzip it on your computer and move the apk to your sd and install it that way?
Sent from my SGH-T959 using XDA App
spigatelli said:
Why not just inzip it on your computer and move the apk to your sd and install it that way?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Cause then it wouldn't be a system app. He could just use adb to push the file though.
Tried to push the file but I can't do adb remount. It says no such file or directory. What am I doing wrong?
Anyone??????
Your probably pushing the file to the wrong place.. Do you have the Samsung drivers and SDK installed?
DAKIDD236 said:
Your probably pushing the file to the wrong place.. Do you have the Samsung drivers and SDK installed?
Click to expand...
Click to collapse
Yes, because every other command works. Also, if you look, I am getting the error when not even trying to push. I am trying to do ADB REMOUNT.
hah2110 said:
Yes, because every other command works. Also, if you look, I am getting the error when not even trying to push. I am trying to do ADB REMOUNT.
Click to expand...
Click to collapse
Samsung devices use a different code to remount. Try this
mount -o rw,remount /dev/st9 /system
This is ripped from the behold 2 so you might have to play with the directories
yeah, if anyone can figure out what the mount directories are from /dev/ it would be great. i'm trying to push my ringtones so that they dont show up in media scanner. seems like a simple trick, but when remount wont work and we dont know the mount directory, its harder than it seems.
psychoace said:
Samsung devices use a different code to remount. Try this
mount -o rw,remount /dev/st9 /system
This is ripped from the behold 2 so you might have to play with the directories
Click to expand...
Click to collapse
Operation not permitted
hah2110 said:
Operation not permitted
Click to expand...
Click to collapse
Do you have root?
If so then it might just be because we don't know what mounting block to use.
we do know what mounting block to use.
http://forum.xda-developers.com/showthread.php?t=729976
So I just got to one of the final steps in rooting my xoom, but for some reason, when I enter the "push su /system/bin/" command, I get a "push: not found" response. I'm completely stuck at this step...anyone have any ideas on this one??
Was adb remount succesful before you tried?
joeski27 said:
So I just got to one of the final steps in rooting my xoom, but for some reason, when I enter the "push su /system/bin/" command, I get a "push: not found" response. I'm completely stuck at this step...anyone have any ideas on this one??
Click to expand...
Click to collapse
I ran in to this. Make sure your Xoom is not on the lock screen. Should be good to go.
PaulG1488 said:
Was adb remount succesful before you tried?
Click to expand...
Click to collapse
Yes, adb remount was in fact successful.
Edit - now I'm getting "cannot stat 'su': No such file or directory"
just to be clear, is it supposed to be:
adb push su /system/bin/
or
adb shell push su /system/bin/
???
syntax is "adb push ..."
bcgaynor82 said:
syntax is "adb push ..."
Click to expand...
Click to collapse
thats what I thought, and when I do this I get the "cannot stat 'su': No such file or directory" error message.
I have no idea what's going on here. Its almost as if I dont have the xoomroot files (including su) in the correct place, but they are there in the SDK tools folder as they are supposed to be. UGH!?!!?
joeski27 said:
thats what I thought, and when I do this I get the "cannot stat 'su': No such file or directory" error message. ?????
Click to expand...
Click to collapse
Make sure that one of the following is true:
the files you want to push are in the same folder as adb
adb is in your path and you are in the directory that the files are
Also make sure you are running this from your computer and not the Xoom, although it sounds like you are bumping into one of the two scenarios above.
nindoja said:
Make sure that one of the following is true:
the files you want to push are in the same folder as adb
adb is in your path and you are in the directory that the files are
Also make sure you are running this from your computer and not the Xoom, although it sounds like you are bumping into one of the two scenarios above.
Click to expand...
Click to collapse
yes they are in the same folder as adb, and I'm in the adb directory while in terminal. still getting the same error message. I'm so lost on this one.
Is there any chance that the unlock didn't take? Though I can't see how it didn't - I went through the entire procedure, answered all the prompts during fastboot, and it did erase/reset the tablet afterwards, so I'm guessing that isn't it.
joeski27 said:
yes they are in the same folder as adb, and I'm in the adb directory while in terminal. still getting the same error message. I'm so lost on this one.
Click to expand...
Click to collapse
Any chance you can screenshot your sdk tools folder
They're supposed to be in the 'platform-tools' folder, not tools. The files go in the same folder as adb so it knows where they are.
PaulG1488 said:
Any chance you can screenshot your sdk tools folder
Click to expand...
Click to collapse
Screenshot of my sdk tools folder:
EDIT: heres the link:
http://i869.photobucket.com/albums/ab259/olesweski/Screenshot2011-03-03at122552AM.png?t=1299130486
Elysian893 said:
They're supposed to be in the 'platform-tools' folder, not tools. The files go in the same folder as adb so it knows where they are.
Click to expand...
Click to collapse
I know, but I had already moved adb into the tools folder earlier on. So they are in the same folder.
send a screenshot of everything in your command prompt if u can please
PaulG1488 said:
send a screenshot of everything in your command prompt if u can please
Click to expand...
Click to collapse
here's the screenshot of my terminal:
http://i869.photobucket.com/albums/ab259/olesweski/Screenshot2011-03-03at124929AM.png?t=1299131460
Do you have the 3.0 sdk installed
Wait I see the problem after you remounted you have to direct it back into your tools foledr before doing the adb push command
PaulG1488 said:
Do you have the 3.0 sdk installed
Click to expand...
Click to collapse
all I know is that i have the latest sdk installed, but are you referring to something additional to that? such as "SDK Platform Android 3.0, API 11, revision 1" ?
joeski27 said:
all I know is that i have the latest sdk installed, but are you referring to something additional to that?
Click to expand...
Click to collapse
After u did adb remount it took you back to your main folder make sure you direct it back to your tools folder then run the adb push command and problem will be solved
PaulG1488 said:
After u did adb remount it took you back to your main folder make sure you direct it back to your tools folder then run the adb push command and problem will be solved
Click to expand...
Click to collapse
So I just did the remount again (successfully), and now instead of just entering "adb push ...", I would need to do what?
EDIT - just tried this, and got this result:
Joseph-Olesweskis-iMac:~ olesweski$ /Users/olesweski/Desktop/android-sdk-mac_x86/tools adb push su /system/bin/
-bash: /Users/olesweski/Desktop/android-sdk-mac_x86/tools: is a directory
[GUIDE] How to do a full backup to /sdcard-ext
How to backup your atrix with adb
Prerequisites:
update: adb,fastboot,moto-fastboot all in one zip
1. Get adb (from one of the following) (awesome thread about adb where to get it and how to use it)
a) Android adk
b) Gladroot or many of the other older rooting methods that are script based in the stickys
c) obtain moto-fastboot for your os version
32 or 64 bit ms windows xp, vista, or 7
64 bit linux
32 bit linux
Mac osX
fastbootandfriends? d) Drivers for your device - windows 32 and 64 bit (motorola.com site) other os's do not need driver files.
2. Obtain root on your device
a) look in the sticky threads (I prefer the CWM zip here)
Warnings:
Do not restore /data "/dev/block/mmcblk0p16" if your going from one rom to another. use titanium backup or another utility.
Do not restore /pds "/dev/block/mmcblk0p3" unless you have a issue with your touchscreen or unless instructed to do so by someone that understands /pds.
Do not ever share your pds.img with anyone
Backup:
adb shell
su
Then type the dd commands below to create a image file on your external sdcard for the following...
Boot
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard-ext/boot.img
Click to expand...
Click to collapse
System
dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard-ext/system.img
Click to expand...
Click to collapse
Data
removed use tibu
Click to expand...
Click to collapse
Osh/Webtop
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard-ext/osh.img
Click to expand...
Click to collapse
Recovery
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard-ext/recovery.img
Click to expand...
Click to collapse
PDS
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard-ext/pds.img
Click to expand...
Click to collapse
MOVE YOUR IMAGE BACKUPS OFF YOUR SDCARD!!!
Restore:
to restore use moto-fastboot (from the pudding thread)
boot
moto-fastboot flash boot boot.img
Click to expand...
Click to collapse
System
moto-fastboot flash system system.img
Click to expand...
Click to collapse
Data
removed use tibu
Click to expand...
Click to collapse
Osh/Webtop
moto-fastboot flash webtop osh.img
Click to expand...
Click to collapse
Recovery
moto-fastboot flash recovery recovery.img
Click to expand...
Click to collapse
WARNING - PDS is tricky - Do not touch pds unless you have to.
Also do not ever share your pds.img with anyone
PDS
adb push pds.img /data/local/tmp
adb shell
su
chmod 777 /data/local/tmp/pds.img
dd if=/data/local/tmp/pds.img of=/dev/block/mmcblk0p3
Click to expand...
Click to collapse
Why not just use cwm?
Sent from my Motorola Atrix using the XDA App
thebeardedchild said:
Why not just use cwm?
Sent from my Motorola Atrix using the XDA App
Click to expand...
Click to collapse
Because CWM nandroid restore has messed up a bunch of users touchscreens
Great info in one place, thanks!
Thanks
Sent from my MB860 using XDA App
I had to change the restore process for data to use adb as moto-fastboot will not flash a image that big.
my /data was 2 gig.
do not forget to delete data.img from /sdcard after you restore.
also keep in mind that your /data will be pretty big and will take quite a long time to restore.
also do not use DD if you have fat fingers and are prone to mistyping "of" and "if" since o and i are next to each other on most keyboards.
joe ferreira said:
Because CWM nandroid restore has messed up a bunch of users touchscreens
Click to expand...
Click to collapse
Wow that's stupid...Is there a fix on the way for that? This method here seems a little more intensive than just using CWM..
Oh well, thanks for giving us something to use while CWM sucks!
can we run these backup commands phone-side via terminal emulator?
the dd commands are best ran via adb
you can run them in terminal emulator but if terminal emulater fc's while your restoring then it could cause issues.
adb is the best way to do this.
really you should all be using titanium backup for /data anyways.
to avoid fat fingers you can also copy and paste.
Great thread Joe!
Permission denied
So I'm a bit of a n00b but I feel like I do pretty well at following directions. Obviously I'm missing something here because after typing "adb shell" and getting the '$' prompt I type the "su" command and am bumped to a new line without a '$' prompt. So far so good, but as soon as I type "dd" I immediately get "Permission denied". It won't even let me enter the entire line! Any help would be greatly appreciated.
AjaxTheCleaner said:
So I'm a bit of a n00b but I feel like I do pretty well at following directions. Obviously I'm missing something here because after typing "adb shell" and getting the '$' prompt I type the "su" command and am bumped to a new line without a '$' prompt. So far so good, but as soon as I type "dd" I immediately get "Permission denied". It won't even let me enter the entire line! Any help would be greatly appreciated.
Click to expand...
Click to collapse
you need root.
you type
adb shell
Click to expand...
Click to collapse
then type
su
Click to expand...
Click to collapse
then it will prompt you on the phone if you have root access to accept the root access request.
I had to remove the /data backup part until I can work the kinks out.
I will update and repost when it is finished
Thank you for the helpful response! I was able to install and run SuperUser on the device so I thought I had successfully rooted. Having been in helpdesk and IT for years there really is no excuse. I failed to follow my own first rule which is to reboot. After restarting my phone I was able to successfully logon to su and execute those commands, but it took finding out that I did in fact NOT have root access to prompt me to try such a thing. Thanks for providing helpful info and not flaming me (sincerely!)
what happens if you are on windows and not linux? can't restore the larger files through fastboot.
y2whisper said:
what happens if you are on windows and not linux? can't restore the larger files through fastboot.
Click to expand...
Click to collapse
your host system does not have anything to do with what I was discussing about image size.
the backup of /data was something that I had to takeout until i figure it out.
as always you should take multiple backups. I use titanium backup as well as the methods discussed in this thread.
i see. so how do I use moto-fastboot? to restore? (where to put the files etc)
y2whisper said:
i see. so how do I use moto-fastboot? to restore? (where to put the files etc)
Click to expand...
Click to collapse
correct me if I'm wrong, but I think you put the files in the fastboot folder.
if you don't put it in the fastboot folder -- you would have to type the full path of the file?
so im guessing --
fastboot flash recovery C:\MyDocuments\recovery.img
or something like that? im a noob too hehe
yeah that part i got down, but when I try to restore the system.img it doesn't let me due to the size.
EDIT
it says image is to big, use 0x10000000 bytes chunks
Failed <remote: 00000006>>
my sys files is 327680kb
Nevermind managed to find my way thanks to Magnetox!
hy
i try to flash kitkat on my phone (lg g2 32gb) and the process fail in the middle.
i go back to jb and my storage shown 10.2gb free even i didn't copy anything to my phone.
i try to flash *.kdz file of ver 32 gb and nothing happend.
what can i do to get back to 32gb like the begining?
Install this, see what's taking up space and where. https://play.google.com/store/apps/details?id=com.mobile_infographics_tools.mydrive
Sent from my LG-LS980 using Tapatalk
Thank you
But i think is something messed up in the partition.
Sent from my LG-D802 using XDA Premium 4 mobile app
yossim66 said:
Thank you
But i think is something messed up in the partition.
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I followed this guide http://www.android-hilfe.de/lg-d802-g2-forum/540911-lg-g2-32-gb-hat-sich-ein-16-gb-verwandelt-2.html
If you have problems please contact me
yossim66 said:
hy
i try to flash kitkat on my phone (lg g2 32gb) and the process fail in the middle.
i go back to jb and my storage shown 10.2gb free even i didn't copy anything to my phone.
i try to flash *.kdz file of ver 32 gb and nothing happend.
what can i do to get back to 32gb like the begining?
Click to expand...
Click to collapse
Did you use the searchbar? Because there's already a thread with this problem.
forum.xda-developers.com
midan said:
I followed this guide http://www.android-hilfe.de/lg-d802-g2-forum/540911-lg-g2-32-gb-hat-sich-ein-16-gb-verwandelt-2.html
If you have problems please contact me
Click to expand...
Click to collapse
Thank you,it's worked.
Sent from my LG-D802 using XDA Premium 4 mobile app
LG G2 international D802 became 16 GB from 32 GB
Hi Yossim66,
I faced similar problem while going back to stock. My phone D802 international became 16 gb from original 32 gb.
I tried following ur guide but unable to copy 4 files to system/bin partition, getting error permission denied. I already got my phone rooted using ioroot and tried copying using root explorer/total commander/es file explorer. Root is showing ok but unable to copy files. please help as I am badly stuck.
Regards,
Tushar Pimple
yossim66 said:
Thank you,it's worked.
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tusharpimple said:
I tried following ur guide but unable to copy 4 files to system/bin partition, getting error permission denied.
Click to expand...
Click to collapse
You are typing su before copying the files to elevate your shell privilege to root, yes?
hi
Hi D00lz
As I said, I am getting error while copying files from pc to device (system\bin) using total commander.
Where to run such command?
Thanks
d00lz said:
You are typing su before copying the files to elevate your shell privilege to root, yes?
Click to expand...
Click to collapse
Tusharpimple said:
Hi D00lz
As I said, I am getting error while copying files from pc to device (system\bin) using total commander.
Where to run such command?
Thanks
Click to expand...
Click to collapse
I use the adb shell for most access to my phone because your computer can't argue with command line (essentially).
1. Follow THIS guide to install ADB drivers on your computer.
2. Copy your 4 files into the C:\adb\ directory (created from Step 1).
3. Turn on USB Debugging on your Android device in Developer Options.
4. Plug your phone into your computer and wait for your device to be recognized.
5. Open Command Prompt as an Administrator and type
Code:
cd C:\adb
6. Type the following commands
Code:
adb push <file1> /system/bin
adb push <file2> /system/bin
adb push <file3> /system/bin
adb push <file4> /system/bin
If you would like to learn more about adb visit Basic adb/shell commands.
Hi everyone
I also have the same problem and i copied thise files and tried with adb shell but every time that i try it says "device offline" and does not procide. My g2 is connected and on and i can navigate to my phone through my pc and i have updated all the drivers. And usb debuging is on. So what cause the problem? What is wrong with adb shell? Any helps would be appreciated