Database Info

app2sd Step for step for any device (even 1.6 dount)

You need a rooted device
1.Step
Patitioning your sd-Card
forum .xda-developers.com/wiki/index.php?title=SD_card_partitioning
here is a great Howto for this
2. Step
plug on your device via usb to the computer
if you don't have it enable usb debugging
now extract the zip from the Attachment into the root of your sdcard
3. Step
open and adb shell with
Code:
adb shell
now instert the folloing command
Code:
sh /sdcard/app2sd.sh
4. Step
to install app2sd youst press enter
after some time your phone should be reboot
info : on the x10 they will the led lights show you if there is an error
with the sdcard
but my script creates a failsafe it's on /data/appbak
it will be used if you had an sdcard malfunktion
please say me all errors you have
wolfilein

I may need to edit something because I get this error on my M003 (Via8505) :
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
mount: mounting /dev/block//vold/179:2 on /system/sd failed: Invalid argument
busybox is /busybox/bin/busybox
tet
rm: can't remove '/etc/mount_sd.sh': No such file or directory
Partitioned SDcad with three partitions 1. 7gig Fat32 2. 96MB Swap 3. (1GB-96MB) as ext2
System will not complete boot now. Sits at initial boot screen then goes dark. Never get to animated logos.
Time to reflash ROM
Wanted swapfile. If it's the issue I'll remove it and try again

wolfilein said:
You need a rooted device
1.Step
Patitioning your sd-Card
forum .xda-developers.com/wiki/index.php?title=SD_card_partitioning
here is a great Howto for this
2. Step
plug on your device via usb to the computer
if you don't have it enable usb debugging
now extract the zip from the Attachment into the root of your sdcard
3. Step
open and adb shell with
Code:
adb shell
now instert the folloing command
Code:
sh /sdcard/app2sd.sh
4. Step
to install app2sd youst press enter
after some time your phone should be reboot
info : on the x10 they will the led lights show you if there is an error
with the sdcard
but my script creates a failsafe it's on /data/appbak
it will be used if you had an sdcard malfunktion
please say me all errors you have
wolfilein
Click to expand...
Click to collapse
so there is a chance that I can brick my phone (kyocera zio 1.6) and since phone doesnt have a recovery i would be screwed? correct?

i would like to know as well...
jcaf77 said:
so there is a chance that I can brick my phone (kyocera zio 1.6) and since phone doesnt have a recovery i would be screwed? correct?
Click to expand...
Click to collapse
i've been looking into this as well and was wondering the same thing as jcaf.. i have 0 space on this phone and would love to be able to install stuff onto sd card, thanks in advance

please help me..I got on Xperia X8..
busybox: not found
mkdir failed for /system/xbin, file exists
[2]
rm failed for /etc/mount_sd.sh, No such file or directory
sed: cannot create temp file /init.rccfoXyj: Read only file system
:::finished going reboot now:::
and he keeps restarting after SE logo..

Does it work on i5800 with ROOT?

need help rooting flipside

i have a motorola flipside with 2.2.2 installed. somehow it lost its root and will not reroot z4root keeps shuting down and giving some odd error saying The application z4root (process com.z4mod.z4root) has stopped unexpectedly. Please try again and leaves only the option to force close the app. i left gingerbreak running all night and when i woke up it was still running not getting anywhere theyed superoneclick it will not finish im getting very fustrated with this phone i even went as far as asuming somthing on the phone went bad and flashed it to a stock att rom and still cannot get the root to finish and apply. is there some way i can mannualy root this phone? also yes usb debuging is on allow unknown aps to install is enabled

anyone please this dam phone is practicaly useless without a root to me id rather be using my stupid windows 7 phone at this rate because at least it had my ringtones and allowed me to use a different backround image than stock att ones.
---------- Post added at 02:09 PM ---------- Previous post was at 01:47 PM ----------
ok i have come accross this but i am a little lost at the steps
wiki.rootzwiki.com/index.php/Motorola_Flipside
it says to download 3 files psneuter busybox and super user unzip the downloads into the same folder. then it says to open a terminal and change to the folder i dont understand this what am i suposed to to? it then says i need android sdk installed and working witch i do i installed it for android screencast. then it says adb devices but does not say how im suposed to enter this command. after that im fairly sure its from the cmd entering the commands shown on that link. can anyone tell me how to get throgh the first few steps please?
copyed from link
Manual Root
[edit] Download
psneuter: Download
Superuser: Download
busybox: Download
Unzip the downloaded files into the same folder
Open a terminal and change to the folder.
You need the android SDK and ADB working. To make sure type:
adb devices
if your device lists, then you are ready to go!
[edit] Gain Root
Run the following commands:
adb push psneuter /data/local/temp/psneuter
adb shell
chmod 755 /data/local/temp/psneuter
./data/local/temp/psneuter
ADB should hang, wait a little while and then type:
adb shell
NOTE: You should have the "#" sign instead of the "$". If you do, you have temporary root, and can continue on.
Type:
exit
adb push busybox /data/local/temp/busybox
adb shell
chmod 755 /data/local/temp/busybox
./data/local/temp/busybox mount -o rw,remount /system
The last command should return nothing

update i learned how to do the procedure and finished sucesfully however the phone is still not rooted. i did reboot the phone after it seems faster now but not rooted.i downloaded the root checker app and scaned the phone it emailed me a log and here is that log
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 is installed!
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your MB508 device by Root Checker version 3.7 from joeykrim in the Android Market

is it even posible to root this phone?

i guess im not allowed to be helped or somthing.

i have a procedure here that i had to build up from 2 seperate write ups. i had to use this one http://androidforums.com/droid-all-...oid-without-rsd-lite-up-including-frg83d.html along with this one together http://wiki.rootzwiki.com/index.php/Motorola_Flipside to get it to root properly.
here is what i did. u will need the downloads from both links for this to work i beleive. follow the steps from the second link to gain root once u get to where the number simbole is shown in the command line u need to switch to the instructions in link 1 and start at step 13 and follow to the end. this works to root your flipside when nothing els will work at least for me it did none of the apps that are suposed to root for you worked for me.
thank you me for having to figure this out on my own have fun

Problem rooting
I rooted my Flipside at its stock state and it worked fine. And then I upgraded my software to 2.2.2 Froyo and lost the root so now I am trying to reinstall z4root and re-root the phone but z4root now doesn't work. It gets successfully installed but when I hit PERMANENT ROOT it just stays in that window with the turning wheel and gets stuck there. It doesn't completely root. I've tried the hard reset by pulling the battery, and hitting the back key and forced closing it and then trying it again. Nothing works! HELP!

I once had a flipside. I rooted it the stock rom and then updated to gingerbread and then rooted again. I used superoneclick though. I'm not sure which version, but there is (or was) a flipside forum here on xda with documentation on the entire process.
Edit: here's the forum link: http://forum.xda-developers.com/forumdisplay.php?f=772

jovanphilip said:
I once had a flipside. I rooted it the stock rom and then updated to gingerbread and then rooted again. I used superoneclick though. I'm not sure which version, but there is (or was) a flipside forum here on xda with documentation on the entire process.
Edit: here's the forum link: http://forum.xda-developers.com/forumdisplay.php?f=772
Click to expand...
Click to collapse
Really? I thought the only upgrade I can do to it is from stock to Froyo. How'd you do that? I'm sorry. I am totally untechie. :/

Problem rooting Live WIth Walkman (WT19i)

I'm trying to root my SE WT19i, but it's being impossible. I´ll tell you all what I've tried so anyone can see any solution:
I followed this thread for downgrading from andoid 4.0 to 2.3. First, flashed the phone with the 4.0.2.A.0.62 version.
Then, for installing adb drivers, tried installing PC Companion, but it wasn't able to install any driver. So, I searched and installed the drivers this way (installing the “Google USB Driver” package).
Then, following the first thread, downloaded the DooMLoRD's Easy Rooting Toolkit [v4.0] , and followed the instructions (USB debugging, unknown sources, even the 10 minutes screen timeout). Don't worked.
So, I flashed again the phone, with the 4.0.2.A.0.42, and tried one more time (and changed the options again according to the script's instructions). Don't worked.
Same for 4.0.2.A.0.58, that is the version that runs my phone now.
Then, I tried this method, by using the Super One Click. That program prompted me to install drivers, so I installed all I was prompted, but don't worked any exploit method of it (yeah, I know the other method "maybe won't work in Android 2.3 and higher", but I had to try).
As there were new drivers installed, I thought the DoomLord's script now, finally, will be able to work, so I tried again. Well, the console output is this (and it is generated in a few seconds...)
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
cannot open 'files\zergRush': No such file or directory
--- correcting permissions
--- executing zergRush
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2262 KB/s (1075144 bytes in 0.464s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
53 KB/s (439 bytes in 0.008s)
--- Free space on /system : 172928 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
Well... the "files\zergRush" actually exists. I haven't modified anything in the files more than unzipping them. I don't know why don't recognise it, but because of that, I downloaded directly the zergRush script and replace it, but didn't worked either even when the DoomLord's script found it. I've also tried to unzipping it directly in C:\, but the results are the same.
I'm using Windows 7, but have tried to run in compatibility mode with xp sp3, and with admin permissions without results.
I don't know what more to do, I think I've tried all. Can anyone help?
PS: I was going to post this in the thread of DoomLord's script (that is the correct place for this, I think), but I'm not allowed yet, sorry.

Accordingly to the rules, bumping thread so it can be seen by anyone who could know about it.
I'm currently trying to contact someone in the IRC, but it'is a bit dead... :-/

install stock rom again and try again

That's already done. Several times. Now, I think the problem is more of the computer for not founding the zergRush script than of the phone. I need a way for getting the script working, but don't know how to...
--------------------------------------------------------------------------------------
Edit: I give up. I can't have my phone useless for more time (because is stupid reconfigure it each time you flash it...). I'm interested no more in rooting the phone. Thanks to all who have read this thread.

[Q] HTC Inspire 4G Not installing CWM or SU

HTC Inspire 4G - AT&T
Android - Stock GB 2.3.5 + HTC Sense 3.0
Build - 3.20.502.52
PC OS - Windows XP Pro SP3
Method - Easy Ace Root Tool
Noob - Yes
Problem - Bootloader unlock successfully achieved, but installation of BusyBox, Clockworkmod, and SuperUser interrupted during process.
Text from Post-Unlock on shown below. Trouble Areas Colored Red
Summary of Problem according to Tool - "Parameter Format not correct," "Read-Only file system," and "No such file or directory"
USB Debugging and Unknown Sources enabled when errors occur
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
< waiting for device >
sending 'recovery' (3554 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 0.953s]
finished. total time: 1.594s
rebooting...
finished. total time: 0.297s
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Make sure that USB debugging is enabled and charge only is set as default
Achieving Temp Root
cannot stat '/tools/tmp/fre3vo': No such file or directory
Unable to chmod /data/local/tmp/fre3vo: No such file or directory
/data/local/tmp/fre3vo: not found
Pushing Busybox, SU and Superuser
1 KB/s (536 bytes in 0.312s)
1829 KB/s (380532 bytes in 0.203s)
1906 KB/s (1372660 bytes in 0.703s)
Trying to gain Perm Root
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'tools\su\su' to '/system/bin/su': Read-only file system
failed to copy 'tools\su\Superuser.apk' to '/system/app/Superuser.apk': Read-onl
y file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
FIND: Parameter format not correct
rm failed for EasyAceRoot.cmd, No such file or directory
Perm Root achieved...

I too am looking for the answer. I'll edit this post if I find something

If CWM would install, that wouldn't be a problem
Scozzar said:
I too am having this issue at the moment. The bootloader is unlocked, but I will not get perm root, even though it says it was achieved...
EDIT: Turning off Fastboot yields different results. But still no SuperSU.
EDIT2: I GOT IT! Basically, I downloaded the latest SuperSU .zip off XDA, put it on the phone, then flashed it in CWM. SuperSU now appears as an app!
Click to expand...
Click to collapse
I'll try turning off fastboot, but I can't get CWM to install at the moment either. SuperSU and Busybox also can't install.
Again, I'll try turning fastboot off and see how it behaves.

Prestige0813 said:
I'll try turning off fastboot, but I can't get CWM to install at the moment either. SuperSU and Busybox also can't install.
Again, I'll try turning fastboot off and see how it behaves.
Click to expand...
Click to collapse
What have you done? Also, you can't turn off fastboot; it's a mode selected from the bootloader. Do you mean ADB? Turning that off won't do anything either, other than making your phone's system inaccessible from the computer.

Scozzar said:
Fastboot, as in the check box in the stock ROM. You can't get into bootloader with it on. Also, if I was able to flash a new ROM, does that mean busybox is installed?
Click to expand...
Click to collapse
Depends on the ROM.

Scozzar said:
V2 Oxygen JB is what I'm using.
Click to expand...
Click to collapse
Er, I don't know for every ROM. If it's a custom ROM, probably. If you're rooted (and again, if you're using a custom ROM, you probably are), you can always install it from the play store.

Update:
First off, I've already downloaded the SuperSU App from Google Play, and it's failed to obtain root abilities, so a perm root is not being acheived.
Also, I've downloaded the latest SuperSU via PC, and it's ready to go once I manage to successfully install CWM (however, if the Ace Root Kit succeeds, then using CWM to install root isn't a needed method)
I've tried continuing the process with the Fastboot setting disabled, and I didn't see any difference in the end result. It seems that recovery is successfully written, but it doesn't succeed in installing SuperSU, CWM, or busybox.
On another note, I've downloaded the busybox installer app from Google Play, and it states the phone is rooted; but runs into errors when I attempt to install (regardless of the version I select). I've run two root checking apps, and both say that the phone is not rooted.
In short, All I've been able to achieve is getting the Boot Loader unlocked.

Can you flash recovery manually from fastboot?

New Update
I just found that CWM is in fact installed. I did not realize until just now that from the HTC bootloader I had to select recovery to access it.
I placed the SuperSU.zip on the phone and installed it via CWM, as scozzar had suggested, and the phone is now rooted (verified by two root checking apps)!
From there I installed busybox via Google Play with no hiccups.
I apologize for not trying this sooner I hope that others find success. The Inspire's a great phone, and now I've made mine even better!

Yess
bananagranola said:
Can you flash recovery manually from fastboot?
Click to expand...
Click to collapse
Yes! here is the tutorial
1- Download Android.zip and unzip it
2- make a folder called "Android" in C:/ like that: C:/Android.
3- put inside of the folder Android the files: adb.exe, fasttboot.exe, AdbWinApi.dll and the recovery.img
4- go to cmd and write:
cd \Android
fastboot flash recovery recovery.img
READY! now you have a CWM Recovery
Sorry for my bad english

[Q] Question about removing system/bin/recovery?

OK, in the middle of writing up this topic, my situation has suddenly changed. (And changed again.)
The story begins: an old AT&T Samsung Infuse 4G, still on Froyo. Put it through a factory-reset and began to fiddle with how to install Clockwork Mod recovery. So there's the guide to upload a modified 3e recovery.
I run adblinux to push the modified recovery over the stock 3e at "system/bin/recovery" -- but "system/bin" was only in read-only mode and adblinux can't run "mount" and doesn't have permission to enter shell and run "su" (or enter shell as root) and File Manager HD (with Super User privledges) can't modify read-only folder "system/bin".
I managed to find a go around by pushing the modified-recovery into the sdcard's root and going through a terminal emulator on the phone to overwrite the file... but I rebooted the phone without running "chmod" on the newly overwritten file and the Infuse bricked so bad that even the battery in off-state refused to refresh.
I understand and accept what I did should be labelled as 'idiotic', but I did manage to wait at the Samsung logo until adblinux recognized the device and eventually restored the original recovery back to "system/bin" (I also found out adblinux didn't have permission to run chmod in the "system/bin" directory).
So... A few questions before I continue:
Why did (pushing the old recovery) work? ADB initially did not recognized the phone, but then the Infuse came up as "I997ae56e13f recovery" -- why was the name now 'recovery?'
And why does running "./adblinux reboot recovery" brings back the bootloop? (In fact, I cannot enter recovery mode, so something is still wrong -- the recovery file is not 755 and I can't chmod a read-only file-system either from adb or via super-user terminal. The temp-root method times out.)
OK, now I'm going home. I'll probably still try to re-install SuperUser. Maybe that will allow adblinux to run "su" in shell, but I'm not going to try anything too extreme.

Justin20 said:
OK, in the middle of writing up this topic, my situation has suddenly changed. (And changed again.)
The story begins: an old AT&T Samsung Infuse 4G, still on Froyo. Put it through a factory-reset and began to fiddle with how to install Clockwork Mod recovery. So there's the guide to upload a modified 3e recovery.
I run adblinux to push the modified recovery over the stock 3e at "system/bin/recovery" -- but "system/bin" was only in read-only mode and adblinux can't run "mount" and doesn't have permission to enter shell and run "su" (or enter shell as root) and File Manager HD (with Super User privledges) can't modify read-only folder "system/bin".
I managed to find a go around by pushing the modified-recovery into the sdcard's root and going through a terminal emulator on the phone to overwrite the file... but I rebooted the phone without running "chmod" on the newly overwritten file and the Infuse bricked so bad that even the battery in off-state refused to refresh.
I understand and accept what I did should be labelled as 'idiotic', but I did manage to wait at the Samsung logo until adblinux recognized the device and eventually restored the original recovery back to "system/bin" (I also found out adblinux didn't have permission to run chmod in the "system/bin" directory).
So... A few questions before I continue:
Why did (pushing the old recovery) work? ADB initially did not recognized the phone, but then the Infuse came up as "I997ae56e13f recovery" -- why was the name now 'recovery?'
And why does running "./adblinux reboot recovery" brings back the bootloop? (In fact, I cannot enter recovery mode, so something is still wrong -- the recovery file is not 755 and I can't chmod a read-only file-system either from adb or via super-user terminal. The temp-root method times out.)
OK, now I'm going home. I'll probably still try to re-install SuperUser. Maybe that will allow adblinux to run "su" in shell, but I'm not going to try anything too extreme.
Click to expand...
Click to collapse
I am curious how adblinux differs from the linux compiled version of adb. Usually it's just called adb.
Anyway, if you are using a Linux OS, and you pulled the original recovery to your PC before overwriting it, it should maintain it's permissions. Likewise, a push would set the permissions like they were on the host PC as well. They say to chmod afterward, because if you are using a windows packaged/downloaded file, or pushing with a Windows PC, the permissions could be anything in the end (rarely what you really want).
As to why the device name changes, not sure. Device names change based on the ROM installed (not always serial number), so it's not out of the question that recovery could tack on something else.
With above, problem is, even with Linux, it doesn't always line up so permissions can be influenced in a push but you may not get what you were asking for. Try chmod 755 the recovery on the local side and adb push the recovery again, after making a backup of the recovery that is there and see if it continues to bootloop.
If all else fails, as long as you have download mode, you can always use ODIN (or Heimdall) to go back to stock (albeit newer Gingerbread). Option A gives you root only, option D, root + recovery (CWM).
Hope this helps.

Thanks for replying!
joel.maxuel said:
I am curious how adblinux differs from the linux compiled version of adb. Usually it's just called adb.
Click to expand...
Click to collapse
I.. have no idea actually. I don't know how to configure Wine to properly emulate an environment for the Windows ADB and I can't get the correct phone-drivers for my WinXP system. (Kleis won't recognize the rooted phone, though if I leave the phone plugged in while installing Kleis, it will interrupt with a "Samsung Mobile Device connected" message.)
joel.maxuel said:
They say to chmod afterward, because if you are using a windows packaged/downloaded file, or pushing with a Windows PC, the permissions could be anything in the end (rarely what you really want).
With above, problem is, even with Linux, it doesn't always line up so permissions can be influenced in a push but you may not get what you were asking for. Try chmod 755 the recovery on the local side and adb push the recovery again, after making a backup of the recovery that is there and see if it continues to bootloop.
Click to expand...
Click to collapse
Unfortunately I can't chmod and push at the same end.
-I tried changing the permissions of recovery file on my PC, but I wouldn't be able to push it onto the "system/bin" directory in the phone.
-I tried changing the permissions on the existing "/system/bin/recovery" file, but the phone says it's a read-only filesystem.
-I tried chmod from the phone in a different directory, but I can't move the file into the "system/bin" directory (cross-device link), delete the existing recovery file (read-only filesystem), and.. why don't I have the copy command?
joel.maxuel said:
If all else fails, as long as you have download mode, you can always use ODIN (or Heimdall) to go back to stock (albeit newer Gingerbread). Option A gives you root only, option D, root + recovery (CWM).
Click to expand...
Click to collapse
I thought flashing with Odin/Heimdall required access to recovery (to wipe all user data and cache folders either before or after the flash).
Without a recovery mode to boot into, won't I be sunk if things go wrong?
Also, I seem to have a different Heimdall frontend, one that doesn't have slots for PDA. It might be because I'm using an newer/older (1.3.1) edition from Ubuntu 12.04 (the official downloads page only has it for 12.10~13.04 editions of my OS), so I'm probably going to have to command-line it.
Code:
heimdall --verbose flash --factoryfs factoryfs.rfs --cache cache.rfs --modem modem.bin --kernel zImage
Look about right? (No partition image table from the tarball found in that forum link?)

Justin20 said:
I.. have no idea actually. I don't know how to configure Wine to properly emulate an environment for the Windows ADB and I can't get the correct phone-drivers for my WinXP system. (Kleis won't recognize the rooted phone, though if I leave the phone plugged in while installing Kleis, it will interrupt with a "Samsung Mobile Device connected" message.)
Click to expand...
Click to collapse
There is adb for Linux, I think adb is natively Linux anyway (the Windows version being the port). Don't have to worry about drivers if in Linux, due to the native support. If using Debian, Ubuntu (or any other Debian derivative), just need to run:
Code:
sudo apt-get install adb
But judging by immediately below, a different version of ADB probably won't change much.
Justin20 said:
Unfortunately I can't chmod and push at the same end.
-I tried changing the permissions of recovery file on my PC, but I wouldn't be able to push it onto the "system/bin" directory in the phone.
-I tried changing the permissions on the existing "/system/bin/recovery" file, but the phone says it's a read-only filesystem.
-I tried chmod from the phone in a different directory, but I can't move the file into the "system/bin" directory (cross-device link), delete the existing recovery file (read-only filesystem), and.. why don't I have the copy command?
Click to expand...
Click to collapse
'cp' should exist, be interesting if it did not. A different ADB could change the outcome (#1), but as pointed out before, you probably won't get the permissions you wanted in the end. Outcomes 2 and 3 would end up being the same, as the device is mounted read only.
You may get lucky with this:
Code:
adb shell mount -o remount,rw system
If root has any influence with this ADB session, it will remount your /system so you can chmod your recovery file on the device end.
Justin20 said:
I thought flashing with Odin/Heimdall required access to recovery (to wipe all user data and cache folders either before or after the flash).
Without a recovery mode to boot into, won't I be sunk if things go wrong?
Click to expand...
Click to collapse
My understanding is that it is completely separate, as the process will replace recovery to stock as well. But just in case, keep this one as a last resort.
I never used Heimdall, just ODIN through a WinXP Virtual Machine (only heard about Heimdall later), but when I used ODIN, I never had any problem with these generic drivers (adbsetup-1.3):
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/

Wow, I wish I took better notes last week. I had to go elsewhere and come back to this project and whatever progress I had made, I think I'm starting over from scratch.
I still can't mount/remount the system folder from anywhere (via ADB under Win/XP and Linux/Ubuntu 12.04); running "su chmod" from the phone still gives a permission denied, changing from Superuser to SuperSU didn't do anything (both programs did find the SU binary to be outdated), and adding a Busybox APK did not add a 'copy' function to my terminal emulator (on the phone) so running an ADB shell would be limited in that regard as well.
I'm going to have to take the phone to a McDonald's and attach a Google account to it. (I would have liked to have done all this offline somehow.)
joel.maxuel said:
when I used ODIN, I never had any problem with these generic drivers (adbsetup-1.3):
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Click to expand...
Click to collapse
How did you manage to get your virtual OS to go "online?" When I tried installing the Google device drivers that came with adbsetup, a big red "X" popped up (Install failed).
I saw that there was a Java-based ODIN, but it's Java 8.0. Should I be using a later/earlier version of Odin/Heimdall? The latest versions don't support my OS (surprising since they support the latest, 14.04, and 12.10 but not anything between or 12.04, the other big release). The existing XDA threads all use Odin/Heimdall 1.1 -- the 1.3 version I have does NOT look like that (and does not have the "PDA" options in the GUI).

Justin20 said:
How did you manage to get your virtual OS to go "online?" When I tried installing the Google device drivers that came with adbsetup, a big red "X" popped up (Install failed).
Click to expand...
Click to collapse
Did the adbsetup binary change? I remember a DOS install process, so there shouldn't have even been a setup wizard (graphical anyway).
Anyway, to get the virtual OS to recognize, need to right click on the devices icon on the bottom status bar (at least in VirtualBox), looks like a USB drive, and select Android, or whatever pops up.
Hope this helps. Also, did the shell remount mentioned earlier have any effect (using adblinux)?
Sent from my Asus MeMO Pad 8"

joel.maxuel said:
Did the adbsetup binary change? I remember a DOS install process, so there shouldn't have even been a setup wizard (graphical anyway).
Click to expand...
Click to collapse
The DOS prompt process begins a driver install. From there, the Setup Wizard popped up.
joel.maxuel said:
Anyway, to get the virtual OS to recognize, need to right click on the devices icon on the bottom status bar (at least in VirtualBox), looks like a USB drive, and select Android, or whatever pops up.
Click to expand...
Click to collapse
Another bad sign: nothing pops up.
As for using mount/remount, the option "remount" was not found. (It would scroll down the whole list of options and switches.)
I think it's time for me to give up the ghost on fixing this issue. I still don't know how I managed to foul it up in the first place because I tried repeating it (entering the command-prompt from the phone, entering superuser, and moving files into "/system/bin") to no avail. So there is a modified 3e recovery file in "/system/bin" without the correct permissions that's preventing the phone from entering recovery mode (and slowing up the boot-up process and "battery recharge" icon when powered off), but other than that the device works, so that's something.
I still would like to try flashing the entire thing with ODIN/Heimdall if I could get either to work. (I ran the latest Heimdall, 1.4.0 32-bit, under WinXP only to find it was not a valid binary. The various Open Disk-Imager in a Nutshell (ODIN) apps out there, but nothing looks like those used on these forums (and did not include a PDA option).

Justin20 said:
The DOS prompt process begins a driver install. From there, the Setup Wizard popped up.
I still would like to try flashing the entire thing with ODIN/Heimdall if I could get either to work. (I ran the latest Heimdall, 1.4.0 32-bit, under WinXP only to find it was not a valid binary. The various Open Disk-Imager in a Nutshell (ODIN) apps out there, but nothing looks like those used on these forums (and did not include a PDA option).
Click to expand...
Click to collapse
The correct version of ODIN will be packaged with whatever image you choose. Just find a windows machine lying around, install the adbsetup drivers, and flash away. Hope this helps.