Database Info

[HOW TO] Install Debian with GUI on any G1 (Any ROM!) ☻☻☻

Okay installing Debian on G1 was a pain in the ass when people make auto installers and never update them -_- I had so much problem trying to use the bootdeb script so heres a manual way to do it and should take like 10 minutes and when done, like 3minutes to start it up.
Feel free to PM me if you get stuck!
What you need:
A Debian Image (debian.img)
Get it here.
ext2.ko
Get it here. If dead, from this page.
unionfs.ko
Get it here. If dead, from this page.
busybox
Get it here. If dead, from this page.
Android Apps you'll need:
Terminal Emulator (Get the free one, even if you have a terminal app!)
VNC Viewer (Free or Paid, anything should work)
Initial Setup
Stuff you need to put in SD card and where.
Put all the files (debian.img, ext2.ko, unionfs.ko & busybox) in one folder named kit and put kit in the root of your SD Card.
Before we start please note this may look looong but Part 1 takes like 10 minutes and Part 2 like 5 mins. So try it out, its worth it!
​Part 1
We will install the base system in this part.
Please Note
You can run the commands below on your computer via ADB Shell but you may have trouble doing Part 2 on your computer. If you understand what you do in Part 1 you may proceed in ADB Shell.​
Click to expand...
Click to collapse
Step One
Open Terminal paste these in order:
Code:
export kit=/sdcard/kit
Press Enter​
Code:
export bin=/data/local/bin
Press Enter​
Code:
export mnt=/data/local/mnt
Press Enter​
Code:
export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
Press Enter​
Code:
export TERM=linux
Press Enter​
Code:
export HOME=/root
Press Enter​
Code:
insmod $kit/ext2.ko
If this gives you a error, ignore it!
Press Enter​
Code:
mkdir $bin #-p
Press Enter​
Code:
cat $kit/busybox >$bin/busybox
Press Enter​
Code:
chmod 755 $bin/busybox
Press Enter​
Code:
alias _=busybox
Press Enter​
Code:
_ mknod /dev/loop0 b 7 0
Press Enter​
Code:
_ mkdir -p $mnt
Press Enter​
Code:
echo 'nameserver 4.2.2.2' >$mnt/etc/resolv.conf
Press Enter​
Code:
_ chroot $mnt /bin/bash
Part 1 Done​
It shoud now say #localhost: || If not then something went wrong...
Part 2
Installing the GUI.
In your Debian Shell (#localhost) type this:
Code:
cd /etc/apt
Press Enter​
Code:
nano sources.list
Press Enter​Now add these two lines below the 1st source:
deb-src ftp://ftp.uk.debian.org/debian/ lenny main contrib non-free
deb ftp://ftp.uk.debian.org/debian/ lenny main contrib non-free
Click to expand...
Click to collapse
Hit Trackball+O to save and then Trackball+X to exit.
Now type:
Code:
apt-get install tightvncserver
After its done type:
Code:
apt-get install icewm
After its done type:
Code:
export USER=root
After its done type:
Code:
vncserver -geometry 480x320
You will be asked to setup the VNC Password after this. Set it and remember it!
Now type:
Code:
cd /root
then
Code:
cd .vnc
then
Code:
nano xstartup
Now edit out the file to look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hit Trackball+O and Trackball+X to exit
Now type:
Code:
cd /root
then
Code:
nano .bashrc
And add these lines to it:
Code:
export USER=root
cd /
rm -r -f tmp
mkdir tmp
cd /
vncserver -geometry 480x320
It should look like this:
Now go to Terminal Setting and type this in the Initial Command:
Code:
su
export kit=/sdcard/kit
export bin=/data/local/bin
export mnt=/data/local/mnt
export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
export TERM=linux
export HOME=/root
alias _=busybox
_ mknod /dev/loop0 b 7 0
_ mount -o loop $kit/debian.img $mnt
_ chroot $mnt /bin/bash
mount -t devpts devpts /dev/pts
mount -t proc proc /proc
mount -t sysfs sysfs /sys
Heres a screenshot:
We use this to save time and boot Debian swiftly!
Now reboot the phone!
After its rebooted, just open Terminal and let it do its thing. If it did it right you should see the Debian Shell launched...
Part 3
Playing around in the GUI!
Go to androidVNC (or any VNC client you have)
Enter the floowing details:
Address: localhost
Port: 5901
Password: the one you set while setting up tightvncserver...
Press connect!
Troubleshoot
If you get a blank window and a X on VNC Connection, goto terminal emulator>settings>reset term. And then reopen terminal. Now goto your VNC Viewer and change the port to 5902 and hit connect!
You should now be in the GUI!! Video of the whole thing coming up soon!​
Stuff you may wanna note!
You may not be able to mount your SD Card while Debian is running so you have to restart your phone to mount your SD Card!
Every time you wanna boot debian just open terminal Emulator and install it as a Debian Boot App or something!
There are a few flaws and I am a design guy and not a coder, if you find something wrong or wanna revise anything PM me or reply. I know its not perfect!
Nothing was done by me I just copyed and pasted stuff from sources. Special Thanks to Jay Freeman (saurik) for coming up with Part 1 and dangermouse over at AndroidFanatic for coming up with Part 2!​

Nice! I'm so excited to see that.

if you are trying this reply! I wanna know how it goes!

its the same thing i did months ago! it works fine but too slow :/ on g1

this thread is very organized, great job

aBsolutex3 said:
this thread is very organized, great job
Click to expand...
Click to collapse
Thanks, wanted it to be user friendly as its not that easy to understand

try it.Do‘’t know to ask you

mkdir $bin #-p
Gives me an error.

cctv35 said:
try it.Do‘’t know to ask you
Click to expand...
Click to collapse
Ummm what?
jatokor said:
mkdir $bin #-p
Gives me an error.
Click to expand...
Click to collapse
Are you sure you entered this:
Code:
export bin=/data/local/bin
Should work

Thank you for this thread
aBsolutex3 said:
this thread is very organized, great job
Click to expand...
Click to collapse
+1
got debian on my g1 for the first time using this walk-through.

Wait, so how do I run this within my mod? will everything on my phone be intact?

ForTehWolf said:
Wait, so how do I run this within my mod? will everything on my phone be intact?
Click to expand...
Click to collapse
Saurik on his website said:
This does not replace Android. This also gives you access to the full plethora of programs available in Debian and let's you continue using your phone as it was intended to be: as an Android device with all the capabilities thereof.
Please note that this is not a "port": Debian already supports ARM EABI, which is the underlying architecture of Android.
Click to expand...
Click to collapse
Its completely safe

error
echo 'nameserver 4.2.2.2' >$mnt/etc/resolv.conf
gives me this error: cannot create datalocalmntetcresolv.conf: directory non existent
sorry for my English i'm spanish boy

s0e0r0a said:
echo 'nameserver 4.2.2.2' >$mnt/etc/resolv.conf
gives me this error: cannot create datalocalmntetcresolv.conf: directory non existent
sorry for my English i'm spanish boy
Click to expand...
Click to collapse
check in /data/local/bin ... is bin a file or a folder? if a file delete it and make a folder manually...

SilentRazor said:
check in /data/local/bin ... is bin a file or a folder? if a file delete it and make a folder manually...
Click to expand...
Click to collapse
theres a busybox file in there, and thats it

echo 'nameserver 4.2.2.2' >$mnt/etc/resolv.conf
no such file or directory

chmod 755 $bin/busybox
gives me:
chmod: not found
and I can't go forward.

sickleman said:
chmod 755 $bin/busybox
gives me:
chmod: not found
and I can't go forward.
Click to expand...
Click to collapse
umm are u rooted?

_ chroot $mnt /bin/bash
gives cannot execute /bin/bash: No such file or directory

Well I dont have my G1 as its gone 4 repairing so... well wait up 4 a few days...

[DUMP] Sidekick 4G Partition + Kernel Source (Bootloader, Recovery, etc)

Credit to sofauxboho for performing dumps.
Partition Dump
http://gititbit.ch/sk4g2 - partition dump
Code:
bml1 256 KB contains boot.bin (262144 bytes), Primary Boot Loader (low-level hardware initialization)
bml2 256 KB contains PIT file first 512 bytes
bml3 10240 KB /dev/block/stl3 /efs
bml4 1280 KB contains Sbl.bin (1310720 bytes) Secondary Boot Loader (loads the Linux kernel and passes the necessary arguments)
bml5 1280 KB contains Secondary Boot Loader (for recovery, ect)
bml6 5120 KB param.lfs /mnt/.lfs j4fs
bml7 7680 KB contains zImage and initramfs
bml8 7680 KB empty - on Epic 4G and Fascinate, contains recovery.bin
bml9 293376 KB factoryfs.rfs ( /system RFS Partition) /dev/block/stl9
bml10 137216 KB dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
bml11 35840 KB cache.rfs ( /cache RFS Partition) /dev/block/stl11
bml12 12800 KB modem.bin
EDIT: It has come to my attention that the Super One Click works, no need for a script.
More Mirrors
http://gititbit.ch/sk41 - Sidekick 4G system dump
http://gititbit.ch/sk4g1 - Sidekick 4G Info Dump
dev.txt
devblock.txt
efs.txt
mount.txt
partitions.txt
proc.txt
Kernel + Platform Source
http://gititbit.ch/sk4g5 - SGH-T839_OpenSource.zip
Now for custom roms...
SK4G development chat can be found at irc.freenode.net #sk4g

hey, sorry i'm not super code-savvy.... do i simply place the .rar file on my sd card, or open it with say, 7zip, and copy the autoroot folder over? i'm getting 'unable to chmod, operation not permitted' the second way, and 'not found, no such directory, etc' when i place the .rar file on my sd card. both of these are appearing after the first line with chmod 755 etc.

Use winrar to extract the .rar then place the extracted folder onto the sdcard.

dasmoover said:
Use winrar to extract the .rar then place the extracted folder onto the sdcard.
Click to expand...
Click to collapse
ok, think i did that, but am still getting 'operation not permitted'..... perhaps i'll hold off and see if someone else has success with it?

Hmm...
Should line 14 specify the su file rather than the containing directory?
It currently reads:
Code:
cp su /system/xbin/ && chmod 4755 /system/xbin/
But perhaps it should read:
Code:
cp su /system/xbin/ && chmod 4755 /system/xbin/su

Updated the script in the main download.

yogi2010 said:
hey, sorry i'm not super code-savvy.... do i simply place the .rar file on my sd card, or open it with say, 7zip, and copy the autoroot folder over? i'm getting 'unable to chmod, operation not permitted' the second way, and 'not found, no such directory, etc' when i place the .rar file on my sd card. both of these are appearing after the first line with chmod 755 etc.
Click to expand...
Click to collapse
Im getting this when I try the lines too.

When I copied the autoroot folder to my SK4G, the contents of the folder were already set to 775, so there should be no need to chmod (though I also get the permission error when trying to chmod them).
The bigger issue is that my device doesn't have the cp command. I'd assume it would be in /system/bin along with things like ls and mv, but it's not.

Huh. That's odd. You guys are using the newer download, right?
Do you have any idea which chmod command is erroring out? I'm wondering if it's the chmod on the rage...bin in line 9 or the chmod on su in line 14.
Unfortunately I can't test without wiping my SK4G back to unrooted, which I would rather not do as it's my primary handset.
If you don't know which line is causing the trouble, could you try copying the kit but then entering each line manually?

sofauxboho said:
Huh. That's odd. You guys are using the newer download, right?
Do you have any idea which chmod command is erroring out? I'm wondering if it's the chmod on the rage...bin in line 9 or the chmod on su in line 14.
Unfortunately I can't test without wiping my SK4G back to unrooted, which I would rather not do as it's my primary handset.
If you don't know which line is causing the trouble, could you try copying the kit but then entering each line manually?
Click to expand...
Click to collapse
No I was usin the old link didn't try new one yet. Still says same thing on new version
Sent From SK4G

sofauxboho said:
Huh. That's odd. You guys are using the newer download, right?
Do you have any idea which chmod command is erroring out? I'm wondering if it's the chmod on the rage...bin in line 9 or the chmod on su in line 14.
Unfortunately I can't test without wiping my SK4G back to unrooted, which I would rather not do as it's my primary handset.
If you don't know which line is causing the trouble, could you try copying the kit but then entering each line manually?
Click to expand...
Click to collapse
I tried the newer download. All of the chmods error because my user doesn't own those files or already have write permissions for any of them. I don't have read, write, or execute permissions for /data/local/tmp either, so I can't list or copy to that location. But, separate from that, there is no cp command, so I can't copy anything anywhere.

jarrodlombardo said:
When I copied the autoroot folder to my SK4G, the contents of the folder were already set to 775, so there should be no need to chmod (though I also get the permission error when trying to chmod them).
The bigger issue is that my device doesn't have the cp command. I'd assume it would be in /system/bin along with things like ls and mv, but it's not.
Click to expand...
Click to collapse
Ah, right! That's why I used cat instead of cp when I rooted mine.
Try this:
Code:
#!/bin/sh
#autoroot script for sidekick v0.1
#chmod 755 autoroot.sh
echo "Copying binaries to /data/local/tmp/"
cat su > /data/local/tmp/su
cat Superuser.apk > /data/local/tmp/Superuser.apk
cat rageagainstthecage-arm5.bin > /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local/tmp/
echo "I'm about to chmod rageagainstthecage-arm5.bin"
chmod 755 rageagainstthecage-arm5.bin
echo "Executing exploit, please wait"
./rageagainstthecage-arm5.bin
sleep 20
echo "Attempting to spawn root shell"
sh
whoami
echo "Attempting to mount /system read-write"
mount -o remount,rw /dev/block/stl9 /system
echo "Attempting to copy and chmod su"
cat /data/local/tmp/su > /system/xbin/su && chmod 4755 /system/xbin/su
echo "Attempting to copy Superuser.apk"
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
sleep 5
mount -o remount,ro /dev/block/stl9 /system
#add root entry to passwd and group
echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
echo "root::0:" > /etc/group
echo "autoroot completed succesfully."
I've also added a bunch of echoed comments to help us track where things go wrong if it doesn't work.

sofauxboho said:
Ah, right! That's why I used cat instead of cp when I rooted mine.
Try this:
Code:
#!/bin/sh
#autoroot script for sidekick v0.1
#chmod 755 autoroot.sh
echo "Copying binaries to /data/local/tmp/"
cat su > /data/local/tmp/su
cat Superuser.apk > /data/local/tmp/Superuser.apk
cat rageagainstthecage-arm5.bin > /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local/tmp/
echo "I'm about to chmod rageagainstthecage-arm5.bin"
chmod 755 rageagainstthecage-arm5.bin
echo "Executing exploit, please wait"
./rageagainstthecage-arm5.bin
sleep 20
echo "Attempting to spawn root shell"
sh
whoami
echo "Attempting to mount /system read-write"
mount -o remount,rw /dev/block/stl9 /system
echo "Attempting to copy and chmod su"
cat /data/local/tmp/su > /system/xbin/su && chmod 4755 /system/xbin/su
echo "Attempting to copy Superuser.apk"
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
sleep 5
mount -o remount,ro /dev/block/stl9 /system
#add root entry to passwd and group
echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
echo "root::0:" > /etc/group
echo "autoroot completed succesfully."
I've also added a bunch of echoed comments to help us track where things go wrong if it doesn't work.
Click to expand...
Click to collapse
Type this into terminal right?

Actually, I whipped up a modified version of dasmoover's tool with my changes:
http://notfine.com/android/sk4g/autoroot-V01b-sfb.zip
Unzip that and copy the "autoroot" folder to your SD card.
Next, eject your SK, turn off USB Storage mode, and unplug it from your computer.
Then follow dasmoover's instructions (I've cleaned them up slightlly):
1. Place autoroot folder on sdcard
2. Install the Terminal Emulator app from the Marketplace
3. Open the Terminal Emulator app and type the following commands exactly, one at a time, hitting enter at the end of the line:
Code:
chmod 755 /sdcard/autoroot/autoroot.sh
./sdcard/autoroot/autoroot.sh
If the sdcard is mounted as noexec, follow these steps:
1. Place autoroot folder on sdcard
2. Install the Terminal Emulator app from the Marketplace
3. Open the Terminal Emulator app and type the following commands exactly, one at a time, hitting enter at the end of the line:
Code:
cat > /sdcard/autoroot/autoroot.sh /data/local/tmp/autoroot.sh
chmod 755 /data/local/tmp/autoroot.sh
cd /sdcard/autoroot/
./data/local/tmp/autoroot.sh
Click to expand...
Click to collapse
All credit to dasmoover, btw! Thanks, and I hope you don't mind me modifying and repackaging your tool. Just trying to help get it working.

BTW, here are some good goodies on how this root exploit works for the technical and curious:
I'd read this one first: http://intrepidusgroup.com/insight/2010/09/android-root-source-code-looking-at-the-c-skills/
And this one second:
http://dtors.org/2010/08/25/reversing-latest-exploid-release/

How did you get rid of the $ sign and get a # ? When I type the first line with the ca it sayd directory can't be found.
Sent From SK4G

I copied the new cat version onto my device and did the following:
$ chmod 755 /sdcard/autoroot/autoroot.sh
Unable to chmod /sdcard/autoroot/autoroot.sh: Operation not permitted
$ cat /sdcard/autoroot/autoroot.sh > /data/local/tmp/autoroot.sh
Cannot create /data/local/tmp/autoroot.sh: permission denied
So, I'm still stuck since /data/local/tmp isn't writable. (Also, you'll note I fixed the small error in the cat line I used.)

Ace42 said:
How did you get rid of the $ sign and get a # ? When I type the first line with the ca it sayd directory can't be found.
Sent From SK4G
Click to expand...
Click to collapse
So, the # means root. The $ means not root. The whole point of this is to get the #, which indicates a root prompt.
If it says the directory can't be found then either the command was typed incorrectly or the files are in the wrong place. The files have to be in the exact right places with the exact right names.
Download my modified version:
http://notfine.com/android/sk4g/autoroot-V01b-sfb.zip
Unzip it, and it should give you a folder called "autoroot". Inside that should be four files:
autoroot.sh
rageagainstthecage-arm5.bin
su
Superuser.apk
Make sure there is only a folder named "autoroot" with those four files inside. If there is another directory inside it won't work. If the names are at all different it won't work.
Copy this "autoroot" folder to the top level of your SD card. There should be other folders there like Music, DCIM, Playlists, and Android. Maybe some others. Make sure it's at the very top level, along with these other directories.
Here, take a look at my directory structure:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Yes, I'm on a Mac, but your SK and Android don't care. File locations work the same on Windows or Linux or whatever. Also, I may have some folders you don't have. That's ok.)
Next, eject your SK, turn off USB Storage mode, and unplug it from your computer. **I forgot this part earlier! It's important.**
Then open up Terminal Emulator an your SK4G. Type:
Code:
cd /sdcard/autoroot
Then type:
Code:
ls
This should list the same four files above. If it does, you're ready to start the instructions I posted previously.
If it doesn't, type:
Then type:
Code:
ls /sdcard/
Let me know what it says.

jarrodlombardo said:
I copied the new cat version onto my device and did the following:
$ chmod 755 /sdcard/autoroot/autoroot.sh
Unable to chmod /sdcard/autoroot/autoroot.sh: Operation not permitted
$ cat /sdcard/autoroot/autoroot.sh > /data/local/tmp/autoroot.sh
Cannot create /data/local/tmp/autoroot.sh: permission denied
So, I'm still stuck since /data/local/tmp isn't writable. (Also, you'll note I fixed the small error in the cat line I used.)
Click to expand...
Click to collapse
Yeah, I've confirmed this problem.
Folks, this thing won't work right now. We need a location that is both writable and allows execution. Any ideas?
(To confirm, you can still root by using adb to manually put these files at /data/local/tmp/ For some reason, adb has rights to this location. However, the standard Terminal Emulator does not. This is only a hang-up for on-device rooting, not rooting in general.)

sofauxboho said:
Yeah, I've confirmed this problem.
Folks, this thing won't work right now. We need a location that is both writable and allows execution. Any ideas?
Click to expand...
Click to collapse
I've poked around some and not found anywhere yet. :/

Cherry Mobile W900 Dragon Phone

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introducing (belatedly) this ...
It's a basically the SK Wynn S150 phone.
There are some work done on customizing in various Chinese and Brazilian forums most notably a CWM port but it seems to end there, and no updates.
Hopefully we can compile some more development for this mobile, especially now there was a huge price drop in our area for it which should mean a lot more of these are floating around waiting for a community development (in English please thank you!).
Most interest to me is rooting, which is at present accomplished using the mentioned CWM recovery option. This puts a quite outdated su binary and quite useless Superuser.apk into the phone giving it basic root functions but no prompts at all, and incorrect UID for root.
With some trial and error I was able to accomplish updating the su and Superuser.apk using existing tools and procedures already used in other mobiles. Details to follow in the next post.

How-to: Updating su and Superuser of Rooted Cherry W900 [draft 00]
Consider this a first draft - but it is still my effort though, so no copying! lol
Here we go!
BTW
STANDARD DISCLAIMERS APPLY with regard to modding, etc paraphrasing CM "Here Be Dragons ..." etc etc
Pre-requisites:
1. Rooted W900 using the builtin CWM function; >>> see this (translate if first) for detals : LINK
2. OS with adb properly installed and able to detect the W900;
3. Recent versions os the su binary, Superuser.apk and (optionally) busybox, I used chanifire's CWM zip update and zeppelins busybox version;
4. Familiarity with the adb commands and the terminal prompt in general;
Procedure:
A. Extract the su binary and Superuser app (and busybox) in a folder;
B. Start a Terminal/ Command Prompt (administrator mode in windows i think is required);
C. Attach the phone make sure it is useable with adb, enter the following in the terminal window:
D. Start an ADB shell;
Code:
<prompt>
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Cherry-Mobile-W900 device
E. Start an ADB shell;
Code:
adb shell
$
F. Start a root prompt;
Code:
$ su
#
F.1. Check user ID of root prompt pre-mod as reference;
Code:
# id
Note that there is 0/ root UID/ GID mentioned as expected;
G. Prepare for update, creating symlink, enter line per line in the adb shell root prompt;
Code:
# mv /data/local/tmp /data/local/tmp.bak
# ln -s /data /data/local/tmp
# reboot
H. Phone will reboot, repeat steps E-F again, then the following to add emulator mode:
Code:
# rm /data/local.prop > nul
# echo \"ro.kernel.qemu=1\" > /data/local.prop
# reboot
I. Phone will reboot into emulator mode now, repeat steps E-F again, then the following:
Code:
# id
********************************************************************
One of the IDs shown should be 0/ root
//IF ID IS 0/root THEN CONTINUE, ELSE START OVER:
Go back to CWM , then unRoot, then Root again, then restart from A
********************************************************************
J. For now exit adb shell, type exit on both adb shell prompts to return to your OS terminal;
Code:
# exit
$ exit
<prompt>
K. adb push su, Superuser.apk and busybox to phone; enter in your OS terminal prompt;
Code:
adb push su /data/local/tmp.bak/
adb push Superuser.apk /data/local/tmp.bak/
adb push busybox /data/local/tmp.bak/
L. Return to adb shell, re-do steps E-F;
M. Mount system parition as RW;
Code:
# mount -o remount rw /system
N.Copy respective files to proper locations and set correct owner/ permissions;
Code:
# cd /data/local/tmp.bak/
# rm /system/bin/su
# dd if=su of=/system/bin/su
# chown 0.0 /system/bin/su
# chmod 06755 /system/bin/su
# ls -l /system/bin/su <<< check first
# -rwsr-sr-x root root 22364 2008-02-29 02:33 su <<< this should be the result
Code:
# dd if=Superuser.apk of=/system/app/Superuser.apk
# chown 0.0 /system/app/Superuser.apk
# chmod 0644 /system/app/Superuser.apk
*********
N.1: following is optional but highly recommended - busybox installation
*********
Code:
# dd if=busybox of=/system/xbin/busybox
# chown 0.0 /system/xbin/busybox
# chmod 0755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/xbin
O. Cleanup, remove emulator mode, temp files;
Code:
# rm /data/local.prop
# rm /data/local/tmp
# mv /data/local/tmp.bak /data/local/tmp
# reboot
After that final reboot, you should now have a proper working Superuser app with prompts and everythings, and root apps like Titanium and link2sd work with no warnings.
On review, I really thought that step G. is an extraneous step, but all these were the steps I did to make it work. I did go thru a few trials before things finally stuck though so for completeness that step is still in there just in case. - I never could do step H without step G I think.

Filipino??? Ive installed sdk and its components, usb drivers. I have adb working, but when i tried to find the connected devices in cmd it shows that there is no device connected.
Ive type this code:
adb devices
List of devices attached:
and it shows nothing
Can you teach me how to configure the device or the adb?

Failed to get shell root
Mine says failed to get shell root, I also tried the superoneclick method and the sk-150 bat file thing, the latter just installs Superuser Superuser Elite and the Root Explorer but doesnt actually root it. Is there any other method out there to actually root this thing?

nah got it rooted using recovery method, now following your instructions, SUPER THANKS!!!

try this to root www.symbianize.com/showthread.php?t=811934

@ashralee
how did you root your phone?
mine wont work?
do you have to do something like
fastory reset or or have to turn on/off
something?
i just followed the steps on rootunlock
and root recovery but it both dont work
on my phone.
pls help me
thanks in advance.

http://www.facebook.com/groups/cher...group/284336801681086/?notif_t=group_activity
try this fb group maybe someone will help you how to root your phone

Help about cwm..i just backed up my stock rom b4 flashing to xperia custom rom.but when i tried to revert it back to my stock rom..cwm says md5 mismatch..what seems to be the problem?please anyone,,help me with this matter..thanks in advance..
Sent from my R800 using xda app-developers app

[GUIDE]To Unpack/Repack livesuit flashable images

While browsing XDA i didn't find anything for unpacking Livesuite images so i created this THREAD.
Things you need
Allwiner kitchen
Stock Firmware
Linux image tool
Ubuntu 64 bit
Click to expand...
Click to collapse
Lets start
Step 1
Extracting and building the stock image (Windows)
Extract a10_flash_kitchen_v1.zip and look inside the directory, you'll see packer_gb and packer_ics. packer_ics is for Android ICS, so that is the one you will be using.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open packer_ics and you will notice a bunch of directories and a couple of .bat scripts. We will spend a lot of time in these directories.
Extract the stock firmware you downloaded earlier, and copy the .img file into this directory. Rename the file to original.img.
Run the extract_image.bat script, and a command window will pop up while it is extracting.
The command window will output like the following, it will display Press any key to continue . . . when it is complete. Press a key to close the window.
Once the command window is closed, open the _extract directory and all of the extracted files will be there. The three following files are the ones we are interested in: RFSFAT16_BOOT_00000000000.fex (the boot partition), RFSFAT16_RECOVERY_0000000.fex (the recovery partition), RFSFAT16_SYSTEM_000000000.fex (the system partition, ext4 sparse).
NOTE and WARNING Some systems may also have a RFSFAT16_BOOTLOADER_00000.fex, which may also be required for your device to boot properly. There are some vague instructions @ this TechKnow forums post. I (the reader) will attempt to clarify and modify this page with the updated additional instructions for these devices to aid in making these instructions more universal for anyone using LiveSuit.
Click to expand...
Click to collapse
Step 2
Extracting, modifying and building partitions (Linux)
Copy your Extracted files to ubuntu
Rename the files as follows:
RFSFAT16_BOOT_00000000000.fex -> boot.img
RFSFAT16_RECOVERY_0000000.fex -> recovery.img
RFSFAT16_SYSTEM_000000000.fex -> system.fex
Click to expand...
Click to collapse
Copy the tools.tar.gz archive you downloaded earlier into the same directory.
To extract the tools, right click on the file and click Extract here.
This will extract the tools into a tools subdirectory.
Type terminal to show the terminal application. Hit enter and the terminal will appear.
Boot partition
Code:
$ cd "custom image"
$ tools/split_bootimg.pl boot.img
$ ls
Now extract the ramdisk file into a ramdisk subdirectory.
Code:
$ mkdir ramdisk
$ cd ramdisk
$ gunzip -c ../boot.img-ramdisk.gz | cpio -i
$ ls
You are now able to modify the files as needed.
Once you have finished modifying the file, we will rebuild the image. Run the following commands.
Code:
$ cd ..
$ tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
$ tools/mkbootimg --base 0x40000000 --kernel boot.img-kernel --ramdisk ramdisk-new.gz --cmdline 'console=ttyS0,115200 rw init=/init loglevel=8' -o new-boot.img
$ ls
Recovery partition
his follows the same process as the boot partition. Execute the following commands to extract the image:
Code:
$ tools/split_bootimg.pl recovery.img
$ rm -rf ramdisk
$ mkdir ramdisk
$ cd ramdisk
$ gunzip -c ../recovery.img-ramdisk.gz | cpio -i
$ ls
rebuild the image with the following commands:
Code:
$ cd ..
$ tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
$ tools/mkbootimg --base 0x40000000 --kernel recovery.img-kernel --ramdisk ramdisk-new.gz --cmdline 'console=ttyS0,115200 rw init=/init loglevel=8' -o new-recovery.img
$ ls
System partition
The process for the system partition is different, because it is not bootable and because it is ext4 sparse, so it cannot be mounted straight away. Execute the following commands to convert and mount the image:
Code:
$ tools/simg2img system.fex system.img
$ mkdir system
$ sudo mount -o loop system.img system
$ cd system
$ ls
Once you are done, execute the following commands to rebuild the system image:
Code:
$ cd ../tools
$ sudo ./mkuserimg.sh -s ../system ../new-system.fex ext4 ../tmp 300M
$ cd ..
$ sudo umount system
$ ls
Now switch back to the file browser and you will see many new files in your directory. The three files that you are interested in are new-boot.img, new-recovery.img, new-system.fex
Copy these to your Windows drive to the directory a10_flash_kitchen_v2/packer_ics/_input
Click to expand...
Click to collapse
Step 3
Building the new image (Windows)
Once the files are copied, jump back to Windows and rename the files as following:
new-boot.img -> root.fex
new-recovery.img -> recovery.fex
new-system.fex -> system.fex
Click to expand...
Click to collapse
http://i.imgur.com/klTA5.png/img]
Now we need to make some modifications to the image config file. Navigate to the files directory and you should see image.cfg.
[img]http://i.imgur.com/Wg6Ov.png/img]
Open this file using your text editor that supports Unix line endings. Using Notepad will break this file. Locate the two lines that reference OEM and VOEM as is highlighted below.
[img]http://i.imgur.com/YxczH.png
Comment these lines by adding a semicolon ( to the start of each line. Do not make any other modifications. Save the file once you have made the change.
http://i.imgur.com/urMMN.png/img]
Go back to the packer_ics root directory and find the create_image.bat script. It will open a console while it is creating the new image.
[img]http://i.imgur.com/X2O6l.png
Once the process is complete, you will see Press any key to continue . . . and you will have a new image called output.img.
AND JUST FLASH IT AND YOU ARE DONE
Click to expand...
Click to collapse

Credits
miniandwiki
To ME
To Everyone who helped me creating this one

do i have to use 64bit liux?? i only have a 32 bit computer?? thnx

Permission denied
Hey....
I installed Ubuntu on an external disk. But even logged at su (also tried sudo su) I dont have the permission to perform with the Linux-tool. When I click at the roo-folder, it is already set to rw permission for root.
What am I doing wrong?

Links are broken, can you kindly update them.

Links are broken Pls Upload to another host

Help:Error Executing updates binary in zip

I don’t know what to do - appreciate some help please. another Error is:”unknown command”
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You probably don't have ro.product.device set.
If you're sure that you actually do have a "viennalte".
Code:
setprop ro.product.device viennalte
If that doesn't work you can always delete the first line or so of META-INF/com/google/android/updater-script in the zip.

Renate said:
You probably don't have ro.product.device set.
If you're sure that you actually do have a "viennalte".
Code:
setprop ro.product.device viennalte
If that doesn't work you can always delete the first line or so of META-INF/com/google/android/updater-script in the zip
Click to expand...
Click to collapse
Thanx for replying. Where I put that code?
Adb command on cmd?

Yes, adb shell.

Renate said:
Yes, adb shell.
Click to expand...
Click to collapse
My pc doesn’t recognise my p905 when I’m in download mode (it dosnt exist on device manager from some reason) so couldn’t unlock bootloader ..and didn’t unlock oem either cause I couldn’t find it/::
I do rooted my device with Odin.
Do you Think delete the first line or so of META-INF - will be enough?

Just delete the line that starts with getprop("ro.product.device")...
If there is a line before/after that includes getprop("ro.build.date delete that too.

Renate said:
Just delete the line that starts with getprop("ro.product.device")...
If there is a line before/after that includes getprop("ro.build.date delete that too.
Click to expand...
Click to collapse
amazing!!! thx!!!
trying to install nikgapps - same Error. wich line to delete here?
#!/sbin/sh
# Shell Script EDIFY Replacement
#Variables
OUTFD=/proc/self/fd/$2;
ZIPFILE="$3";
addToLog() {
echo "$1" >> "/tmp/NikGapps.log"
}
contains() {
case $2 in
*"$1"*) echo true ;;
*) echo false ;;
esac
}
decrypt() {
mkdir -p "$(dirname "$2")"
addToLog "- decrypting $COMMONDIR/busybox"
addToLog " -> source $1"
addToLog " -> destination $2"
unzip -o "$COMMONDIR/busybox" "$1" -p >"$2"
chmod 755 "$2";
}
ui_print() {
until [ ! "$1" ]; do
echo "ui_print $1
ui_print" >> "$OUTFD";
addToLog "$1"
shift;
done;
}
find_zip_type() {
addToLog "- Finding zip type"
if [ "$(contains "-arm64-" "$ZIPNAME")" = "true" ]; then

I don't know what's going on there.
It's obviously trying to be invoked like an Edify script.
You'll have to explicitly state the error and quote the entire shell script.

thanx!!!

Renate said:
You'll have to explicitly state the error and quote the entire shell script.
Click to expand...
Click to collapse
Apparently??? what you quoted above as a script is in a file named "update-binary"???
They're doing something goofy by using a shell script instead of an Edify script???
Or else update in recovery can run without an update-binary???
Apparently there is some problem with fstab so it can't remount system (right after it unmounted it)?
Does this thing have a super partition?

Renate said:
Apparently??? what you quoted above as a script is in a file named "update-binary"???
They're doing something goofy by using a shell script instead of an Edify script???
Or else update in recovery can run without an update-binary???
Apparently there is some problem with fstab so it can't remount system (right after it unmounted it)?
Does this thing have a super partition?
Click to expand...
Click to collapse
Super partition? I don’t know /: how I can check?

Please post a link to this NitGapps.apk

Renate said:
Please post a link to this NitGapps.apk
Click to expand...
Click to collapse
https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/01-May-2021/NikGapps-stock-arm64-11-20210501-signed.zip/download

I thought that that would expedite matters, but I don't have any interest in downloading 600 Megs.
Just post the script, identify the file name and tell me if there is only one file in META-INF/com/google/android
I think we're exceeding the bounds of my expertise/interest.

2 files: update - binary, updater - script.
Updater-script text is:
#!/sbin/sh
# Shell Script EDIFY Replacement
#Variables
OUTFD=/proc/self/fd/$2;
ZIPFILE="$3";
addToLog() {
echo "$1" >> "/tmp/NikGapps.log"
}
contains() {
case $2 in
*"$1"*) echo true ;;
*) echo false ;;
esac
}
decrypt() {
mkdir -p "$(dirname "$2")"
addToLog "- decrypting $COMMONDIR/busybox"
addToLog " -> source $1"
addToLog " -> destination $2"
unzip -o "$COMMONDIR/busybox" "$1" -p >"$2"
chmod 755 "$2";
}

I don't believe that that's the entire extent of updater-script.
You're telling me that the size of that file is ~412 bytes?

@Daniel.aru I own a P900 and not a P905 but for me it seems that this LOS Rom needs a higher TWRP version.
3.0.2 is the latest official available.
That's what it says as well in #1 of the thread you downloaded it from.
The dev even offers it's own version so why don't you follow his suggestion?

bmwdroid said:
@Daniel.aru I own a P900 and not a P905 but for me it seems that this LOS Rom needs a higher TWRP version.
3.0.2 is the latest official available.
That's what it says as well in #1 of the thread you downloaded it from.
The dev even offers it's own version so why don't you follow his suggestion?
Click to expand...
Click to collapse
the 3.0.2 version is an IMG file and odin flash just a TAR. tried to convert the file drom img to tar but the odin process failed. what can i do ?

Daniel.aru said:
the 3.0.2 version is an IMG file and odin flash just a TAR. tried to convert the file drom img to tar but the odin process failed. what can i do ?
Click to expand...
Click to collapse
The TWRP installed should be able to flash the img.
Afaik all after 2.8.7 are able to.
Gotta select that option after selecting "install" in TWRP.

bmwdroid said:
The TWRP installed should be abtle to flash the img.
Afaik all after 2.8.7 are able to.
Gotta select that option after selecting "install" in TWRP.
Click to expand...
Click to collapse
it worked i have the right version . tried to flash the rom again and got eror number 1