X8 Custom ROM - XPERIA X8 Android Development

Because propoff2 got himself banned, I've decided to re-create his threads for you, hopefully with easier to follow instructions than before.
X8 Android 2.1-rus
X8 Android 1.6
Modified Image (x8.img)
Data.img
Busybox, Rootshell, Chargemon
(If for whatever reason any of the above links don't work, scroll down and see propc's post.)
Before moving on, decide whether you want to boot the rom from the sdcard or from the internal memory, then use the correct instructions to do so.
If you've tried this method and REALLY don't like the customized rom, then see this thread for how to install a clean, pre-rooted rom!
==BOOTING CUSTOM ROM FROM SD==
Before you begin, put chargemon, busybox, rootshell, x8.img and data.img onto the sdcard.
1. Flash 1.6 firmware to the phone.
2. Root the phone.
3. Copy the files rootshell, chargemon and busybox to /system/bin
(You can do this by putting the files on the sdcard, and using a file manager such as root explorer to copy the files into /system/bin. Command line instructions will be here soonish. This guide is still a WIP).
4. Chmod the files.
Code:
chmod 4755 /system/bin/rootshell
chmod 755 /system/bin/busybox
chmod 777 /system/bin/chargemon
5. Copy both x8.img (/system) and data.img (/data) to the sdcard.
6. Flash 2.1 kernel using this flashing utility. (The GUI version is perfectly fine to use.)
Remember to remove system.sin and userdata.sin from the flash files!
7. Reboot and hope it works.
==BOOT CUSTOM ROM FROM INTERNAL MEMORY==
Before you being, copy x8.img and busybox on to the sdcard.
1. Follow steps 1-2 from the instructions above.
2. Copy busybox to /data/local/tmp
Code:
cd /data/local/tmp
cat /sdcard/busybox > /data/local/tmp/busybox
3. Chmod busybox.
Code:
chmod 755 busybox
4. Using busybox, remount /system as rewriteable.
Code:
./busybox mount -o remount,rw /system
./busybox sh
5. Mount x8.img.
Code:
./busybox mkdir /data/local/tmp/1
./busybox losetup /dev/block/loop1 /sdcard/x8.img
./busybox mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1 /data/local/tmp/1
6. Remove the contents of /system. ADVICE: Remove the folders one by one, leave /system/bin and /system/app last! That way your phone is less likely to crash whilst doing this step. DO NOT TRY AND USE YOUR PHONE WHILE DOING THIS, YOUR PHONE IS CERTAIN TO CRASH! Make sure the phone is locked.
Code:
./busybox rm -rf /system/media
./busybox rm -rf /system/usr
./busybox rm -rf /system/etc
./busybox rm -rf /system/lib
./busybox rm -rf /system/xbin
./busybox rm -rf /system/framework
./busybox rm -rf /system/fonts
./busybox rm -rf /system/drm
./busybox rm -rf /system/build.prop
./busybox rm -rf /system/app
./busybox rm -rf /system/bin
7. Now copy the files into the phone's internal memory. Again, we have to copy these over one by one, as the phone WILL run out of memory during this process! Most important files go first.
Code:
./busybox cp -prfR /data/local/tmp/1/bin /system/
./busybox cp -prfR /data/local/tmp/1/xbin /system/
./busybox cp -prfR /data/local/tmp/1/etc /system/
./busybox cp -prfR /data/local/tmp/1/usr /system/
./busybox cp -prf /data/local/tmp/1/build.prop /system/
./busybox cp -prfR /data/local/tmp/1/lib /system/
./busybox cp -prfR /data/local/tmp/1/framework /system/
./busybox cp -prfR /data/local/tmp/1/fonts /system/
./busybox cp -prfR /data/local/tmp/1/drm /system/
./busybox cp -prfR /data/local/tmp/1/media /system/
./busybox cp -prfR /data/local/tmp/1/app /system/
Hopefully you won't run out of space until you try and copy /app over. No worries! Your phone will still start, and you can easily restore those files after.
8. Flash the 2.1 kernel, and userdata.
Unlike in the previous instructions, you only want to remove system.sin from the flash files! Put userdata.sin back if you've removed it!
9. Turn on your phone and just hope you didn't mess up!
==APPS ON SD==
See this thread: App2SD Mod (Moves dalvik cache to SD) Instructions
ARGH!! MY PHONE IS STUCK IN A ETERNAL REBOOT? WHAT DO I DO?!
Well, if you know for sure what you did, and don't fancy reflashing all over again, then just plug in your phone and use adb to shell into the phone. Quickly fix the problem before the phone reboots!
Just putting this out there: These instructions were roughly written up. If you're having issues, don't be afraid to ask! If you spot any mistakes, please let me know! I'll expand on these instructions later.
All credits go to pulpoff2, for figuring out this solution, and propc for re-uploading the files, discovering steps 6 and 7 in the internal memory instructions, and for helping me fix these instructions multiple times.

Thank you! I will try this as soon as the files are available.
Are there any downsides? Is everything working as before? What about the speed (when loading apps for example)?

Yes, there are a few downsides. While booting from the sdcard, you cannot mount the sdcard via the phone (you'll need to use a card reader, or push/pull files with adb). There may be some performance issues while booting from the sdcard aswell. The camera and the music player also don't work.
However, if you decided to put the rom into the phone's internal memory, all this is fixed! Absolutely no downsides. Unless you don't like the theme, then I guess that is a downside.

thanks for making a new thread, thread pulpoff2 was hacked by ****-arsehole people! maybe.

I don't think so. The site that he used to host the files has been redirected to an anti-muslim site, by the looks of it.

aktw
Thanks man! Really appreciate it! Now I just need your tut for internal memory. Thanks again!
ML

Edit: Can you add app2sd tutorial?
Much more concise internal flashing (for anyone who wants it)
Code:
adb shell
su
cd /data/local/tmp
cat /sdcard/ext/bin/busybox > /data/local/tmp/busybox
chmod 755 busybox
./busybox mount -o remount,rw /system
./busybox sh
/data/local/tmp/busybox mkdir /data/local/tmp/1
/data/local/tmp/busybox losetup /dev/block/loop1 /sdcard/x8.img
/data/local/tmp/busybox mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1 /data/local/tmp/1
/data/local/tmp/busybox rm -r /system
/data/local/tmp/busybox cp -prf /data/local/tmp/1/* /system

There, the internal memory instructions are up.

EDIT
ALL FILES NEEDED FOR ABOVE METHOD STATED BY a-k-t-w
Mediafire folder
http://www.mediafire.com/?2kk19r7u4x1w3\
duckload:
data.img
X8.img
X8 2.1 russian
Hotfile:
data.img
X8.img
X8 2.1 russian
ext.rar at the attachment
for external rom (if you use adb shell)
Code:
su [B]look at phone screen and press "allow"[/B]
cd /data/local/tmp
cat /sdcard/ext/bin/busybox > /data/local/tmp/busybox
chmod 755 busybox
./busybox mount -o remount,rw /system
./busybox cp -r /sdcard/ext/* /system/
chmod 755 /system/bin/busybox
chmod 777 /system/bin/chargemon
chmod 755 /system/bin/e2fsck
chmod 4755 /system/bin/rootshell
to mount x8.img
Code:
mkdir /data/local/tmp/1
cat /sdcard/ext/bin/busybox > /data/local/tmp/busybox
/data/local/tmp/busybox losetup /dev/block/loop1 /sdcard/x8.img
/data/local/tmp/busybox mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1
EDIT : a-k-t-w completed the instruction himself. LOL..i think i'll be here for support..
-there you go.
ext.rar and unyaffs uploaded
i'll help by uploading the firmware files on mediafire.

actually I need the firmware 2.1 unmodified, but I'm okay to waiting.
Thx before.

That can be done. You mean unmodified, but rooted, right?
propc said:
...
i'll help by uploading the files on mediafire.
Click to expand...
Click to collapse
Thank you very much!! You have the latest ROM right? I'll add these to the OP when you are done.
a-k-t-w said:
[highlight]Mod Edit: Sorry, but I had to remove the link to the former dev's site due to the nature of that link[/highlight]
Click to expand...
Click to collapse
Understood.
Edit: @propc, What is unyaffs used for?

will the custom ROM have Timescape???? Or it will be the non-customized Android version.....
sry if this is a stupid question....
and i am just a beginner, so want a ask, what to you mean by "Flash 2.1 kernel" how to do it.....what are the files?? what is 2.1 kernel file??
i am new here...sry!

a-k-t-w said:
That can be done. You mean unmodified, but rooted, right?
Thank you very much!! You have the latest ROM right? I'll add these to the OP when you are done.
Click to expand...
Click to collapse
I think it's the latest. btw, it's stable no worries

mohakrastogi said:
will the custom ROM have Timescape???? Or it will be the non-customized Android version.....
sry if this is a stupid question....
and i am just a beginner, so want a ask, what to you mean by "Flash 2.1 kernel" how to do it.....what are the files?? what is 2.1 kernel file??
i am new here...sry!
Click to expand...
Click to collapse
Sorrry, I'll edit the OP. What I mean is, flash the 2.1 firmware, but without the files system.sin and userdata.sin (if your doing the sdcard method). This is basically flashing the 2.1 kernel only. Hang in there, the files will be available for download soon.
The custrom rom does not have timescape. You may have to restore ALL apps as there are some missing that will prevent you downloading your providers settings. I'm not sure which it is, so my solution is restoring them all. :-S
propc said:
I think it's the latest. btw, it's stable no worries
Click to expand...
Click to collapse
Excellent! Thanks again for the help.

a-k-t-w said:
Sorrry, I'll edit the OP. What I mean is, flash the 2.1 firmware, but without the files system.sin and userdata.sin (if your doing the sdcard method). This is basically flashing the 2.1 kernel only. Hang in there, the files will be available for download soon.
The custrom rom does not have timescape. You may have to restore ALL apps as there are some missing that will prevent you downloading your providers settings. I'm not sure which it is, so my solution is restoring them all. :-S
Excellent! Thanks again for the help.
Click to expand...
Click to collapse
i'm uploading data.img, x8.img and russian 2.1(.sin files)
any other files that need to be upload?
using unyaffs, you can extract x8.img directly to /system
maybe needed for future
folder for needed files are up (uploading other files .....)
HERE

please help me when write a command i got a problem with copy file
screenshot:
{
"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"
}
this a file problem with copy:
/data/local/tmp/busybox rm -r /system/app/com.mizusoft.relaxandsleep.apk
/data/local/tmp/busybox cp -prf /data/local/tmp/1/bin/* /system/bin/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/drm/* /system/drm/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/fonts/* /system/fonts/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/framework/* /system/framework/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/lib/* /system/lib/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/usr/* /system/usr/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/xbin/* /system/xbin/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/build.prop /system/build.prop
/data/local/tmp/busybox cp -prf /data/local/tmp/1/media/* /system/media/
Click to expand...
Click to collapse
but remove a system -rm -r work for all files. help me pls

What is this custom ROM I keep reading about? What exactly is different there, except for the theme? I would like to see a screenshot of the theme, btw. Is JIT enabled?

Uhh. Probably not. The difference is just the theme, and root on 2.1. Because you can't get root any other way, if I'm not mistaken.

novincobra said:
please help me when write a command i got a problem with copy file
screenshot:
this a file problem with copy:
but remove a system -rm -r work for all files. help me pls
Click to expand...
Click to collapse
My guess is that you didn't mount the x8.img properly?
Or my cp command could be wrong. OH! Don't copy each app one by one, just the folders!
Don't put /* at the end! That means you are copying the contents of the folder! You want the entire folder on /system !

Ok, this means we have to use this customized ROM to gain root. Thanks for clarifying.

Related

Rooted with mediascape

Many ppl seem to want to reinstall mediascape..
well as far as i know you can't reinstall mediascape after rooting; however, it is possible to NOT DELETE mediascape in Step 4.
You follow the root guide in the stick up to step 3, then before you run step 4 (well i guess it's better to do it before you start rooting) open cleanup.sh in step 4 and remove mediascape and mediascapeplugin from the list... so it should look like this
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
rm -R /sdcard/apps
mkdir /sdcard/apps
cd /system/app
cp AndroidQuadrapop* /sdcard/apps
cp docomo_market* /sdcard/apps
cp EManual* /sdcard/apps
cp LatinIME* /sdcard/apps
cp LatinImeTutorial* /sdcard/apps
cp Launcher* /sdcard/apps
cp LearningClient* /sdcard/apps
cp MixiPlugin* /sdcard/apps
cp moxiermail* /sdcard/apps
cp officesuite* /sdcard/apps
cp pocket_rashinban* /sdcard/apps
cp SemcIME* /sdcard/apps
cp trackid* /sdcard/apps
rm AndroidQuadrapop*
rm docomo_market*
rm EManual*
rm LatinIME*
rm LatinImeTutorial*
rm Launcher*
rm LearningClient*
rm MixiPlugin*
rm moxiermail*
rm officesuite*
rm pocket_rashinban*
rm SemcIME*
rm trackid*
rm /data/app/*.zip
rm /data/app-private/jp.*
rm -r /etc/semc/startupshow
rm -r /etc/semc/preset/app
rm -r /etc/*.iso
then run step 4..
personally i don't know exactly what's changed on my phone other than the fact that i now have a zeam home launcher instead, titanium backup says my phone's been rooted, i didn't have to restore anything because everything (all data/apps i installed personally) were kept the same, mediascape still there, and i lost korean keyboard/option to switch to korean menu which came with the R2BA020 update...
oh and my step 3a wasn't working properly so i just skipped it.. but regardless i can type 'su' into better terminal, and titanium backup says my phone's rooted so i don't really care..
although if the devs could release another one with the korean keyboard/menu from the new R2BA020 update, it'd be great
oh and i went from x10a(rogers 014) -> x10i (R2BA020) -> root
Thanks Dude!!! This is just what I needed. No timescape?? What if I wanted timescape, is there a way to prevent it from removing that?
Fuzalert2k said:
Thanks Dude!!! This is just what I needed. No timescape?? What if I wanted timescape, is there a way to prevent it from removing that?
Click to expand...
Click to collapse
it doesn't remove timescape..
Retrying for the fourth time, I managed to root the phone, then I saw you could keep mediascape, and the original keyboard... tried opening and saving the sh file with notepad, wordpad, write... don't know if it modifies something but once we get to the uninstalling part I get 'No such files or directory'...
found the solution, do not edit shell file in windows with notepad,
http://sourceforge.net/projects/eme...-editor-2.72-r286/cedt-286-setup.exe/download
works pretty well on windows, so you can decide to keep whatever you want
mayamo said:
Many ppl seem to want to reinstall mediascape..
well as far as i know you can't reinstall mediascape after rooting; however, it is possible to NOT DELETE mediascape in Step 4.
You follow the root guide in the stick up to step 3, then before you run step 4 (well i guess it's better to do it before you start rooting) open cleanup.sh in step 4 and remove mediascape and mediascapeplugin from the list... so it should look like this
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
rm -R /sdcard/apps
mkdir /sdcard/apps
cd /system/app
cp AndroidQuadrapop* /sdcard/apps
cp docomo_market* /sdcard/apps
cp EManual* /sdcard/apps
cp LatinIME* /sdcard/apps
cp LatinImeTutorial* /sdcard/apps
cp Launcher* /sdcard/apps
cp LearningClient* /sdcard/apps
cp MixiPlugin* /sdcard/apps
cp moxiermail* /sdcard/apps
cp officesuite* /sdcard/apps
cp pocket_rashinban* /sdcard/apps
cp SemcIME* /sdcard/apps
cp trackid* /sdcard/apps
rm AndroidQuadrapop*
rm docomo_market*
rm EManual*
rm LatinIME*
rm LatinImeTutorial*
rm Launcher*
rm LearningClient*
rm MixiPlugin*
rm moxiermail*
rm officesuite*
rm pocket_rashinban*
rm SemcIME*
rm trackid*
rm /data/app/*.zip
rm /data/app-private/jp.*
rm -r /etc/semc/startupshow
rm -r /etc/semc/preset/app
rm -r /etc/*.iso
then run step 4..
oh and i went from x10a(rogers 014) -> x10i (R2BA020) -> root
Click to expand...
Click to collapse
So what i understand is that If I want to keep the Default home then I should be removing the Launcher from the list as well. Also is Backup and Restore Included which is there in new firmware.... as I do not want to go for limited backup tool.
hotfile.com/dl/51161486/a67bb41/step4.zip.html
Click to expand...
Click to collapse
moded
step4 with mediaspace

[Alpha Release] xWildFireMini 2.1 v0.2b

Hello,
This is the my port of the Wildfire 2.1 Eclair Rom for the Mini.
I chose Eclair because the drivers will probably be easier to find like this, you can expect a 2.2 Sense rom to come once the 2.2 AOSP is done.
[Download v0.2a Here]
[Download v0.2b Update]
Flash them is this order.
The Work's
Apps2SD
ADB
Booting
Display
xRecovery
Touch
SD-Card
OpenGL
Ext4 for Apps2SD
OMX (proper video playback)
Sound
The Won't 's
Charging [It says it's charging but it's not!]
GSM/3G
WiFi
USB mounting
Bluetooth
LED Flash & Light
Camera
YouTube Video showing installation.
YouTube Video in high quality by maxaan
Developer Notes:
Developer Notes:
Any Dev interested for testing all my future releases for the mini?
I ask developers for help to try out finding how to get the drivers for the non-working hardware parts to work. Simply said, you need to copy drivers from the SE 2.1 build to this build and report if it worked and which files were used.
Changelog:
v0.2a is up! Prepared the system for future drivers, little faster, ext4 support for apps2sd. Also for the mini fixed xrecovery thanks to peetr_
v0.2 Alpha is up! Fixed a lot: SD, Touchscreen, xRecovery, OpenGL
v0.1 Technical Preview / Pre-Alpha released for developers.
dang you are using same device..
i did try same thing but with clean wildfire [didn't get very far tho] [becouse work on kitchen] ... will download this too and see...
Problems on boot.
Or better no boot at all.
I made a full wipe, flashed the .zip and then these commands:
PHP:
adb shell
cd /system/bin
/system/bin/chmod 755 busybox
./busybox --install -s /system/xbin
./busybox --install -s /system/bin
After that reboot and stuck on Sony Ericsson white letters.
tried the mount command too but still no luck
PS: Something weird though. Xrecovery still working on me!
DaRk_dOg said:
Problems on boot.
Or better no boot at all.
I made a full wipe, flashed the .zip and then these commands:
PHP:
adb shell
cd /system/bin
/system/bin/chmod 755 busybox
./busybox --install -s /system/xbin
./busybox --install -s /system/bin
After that reboot and stuck on Sony Ericsson white letters.
tried the mount command too but still no luck
PS: Something weird though. Xrecovery still working on me!
Click to expand...
Click to collapse
Thanks for the info! This means I have to rebuild the ramdisk to have it work on the x10 mini. Oh one thing I forgot to state is that this NEEDS an ext2 partition on the sdcard (apps2sd not removed yet) and that the first boot will take ages stuck on the bootscreen since it's copying all apps over.
Could you adb pull system/bin/chargemon, open the file in notepad and send the content to me? Of the installed rom, that is.
In the update.zip package there is both an chargemon and chargemon~ file left over from text editing it with Ubuntu. Problem is that I can't acces the file through Nautilus (Ubuntu's version of Windows Explorer)
Hi, i also tried your work and i have the the same state as DarkDog with xRecovery working.
Tried the "logcat" :
sh-3.2# /system/bin/chmod 755 /system/bin/busybox
/system/bin/chmod 755 /system/bin/busybox
Unable to chmod /system/bin/busybox: Read-only file system
sh-3.2# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
sh-3.2# cd /system/bin
cd /system/bin
sh-3.2# /system/bin/chmod 755 busybox
/system/bin/chmod 755 busybox
sh-3.2# ./busybox --install -s /system/xbin
./busybox --install -s /system/xbin
sh-3.2# ./busybox --install -s /system/bin
./busybox --install -s /system/bin
sh-3.2# logcat
logcat
I/checkabortedflash( 1065): [110] Latest flash seems OK.
E/logwrapper( 1499): executing /system/xbin/busybox failed: Permission denied
I/logwrapper( 1493): /system/xbin/busybox terminated by exit(255)
Click to expand...
Click to collapse
Seems like something goes really wrong here....
Mby because the wrong ramdisk or something.
@peetr try to give the "mount" and "ls /system/xbin" commands, mby found something..
peetr_ said:
Hi, i also tried your work and i have the the same state as DarkDog with xRecovery working.
Tried the "logcat" :
Click to expand...
Click to collapse
Ah yes.. I'll update the commands, you need to
PHP:
adb shell
cd /system/xbin
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
/system/bin/chmod 755 busybox
cd /system/bin
/system/bin/chmod 755 busybox
./busybox --install -s /system/xbin
./busybox --install -s /system/bin
Can you see if that works?
Good job ! Up and running
Linpack - 2,3 MFLOPS
But looks nice.
peetr_ said:
Good job ! Up and running
Linpack - 2,3 MFLOPS
But looks nice.
Click to expand...
Click to collapse
Huh? You mean touchscreen works on the mini?!
Yes it works.
peetr_ said:
Yes it works.
Click to expand...
Click to collapse
That's odd, it doesn't on the Pro
u10a init.rc
Mikevhl
attached is the init.rc you requested, it is from u10a USA version. hope it helps. Thank you for for effort.
strykme said:
Mikevhl
attached is the init.rc you requested, it is from u10a USA version. hope it helps. Thank you for for effort.
Click to expand...
Click to collapse
Thanks, but I understand that it's booting now on the mini?
The commands that you have to run after installing are updated, would you mind giving it a try?
I think you can write in the first post, that its working on mini. And that we have to install busybox before leaving xrecovery.
But i must say again, it is too slow in this alpha version. Hope it can be faster in later versions.
peetr_ said:
I think you can write in the first post, that its working on mini. And that we have to install busybox before leaving xrecovery.
But i must say again, it is too slow in this alpha version. Hope it can be faster in later versions.
Click to expand...
Click to collapse
Try out the Alpha please, should be a tad faster since I've fixed openGL
Well i wait for some updates, then I'm gonna try it
Nice work tho, keep it up !
can you please remove the app2sd so i am able to test it because right now i have an ext3 on my sd card and i am missing my adapter!!! Or at least someone provide a method convert to ext2 mounted from the device e.g. from ubuntu?? Can i do it this way???
First thing, you have to change chargemon to event1 for mini

[Q] Deodex/adb help!

Ok I am on a rooted 345 us White dell streak.
I am trying to deodex. I have used the deo 1.2.1 deodexer in the xda forum thread for auto deodex 2.3.
I pulled all my apks and their odex files from the /system/app/ folder
and the jars and odex files from the /system/framework folder
I am trying to use adb to copy them from my sdcard to the correct folders, but when i reboot my phone hangs at the dell logo.
Hopefully someone can see what I am doing wrong.
I enter:
adb shell
su (then I allow permission on my phone)
mount -o rw,remount -t yaffs2 /dev/block/mtdblock6 /system
cp /sdcard/doneapk/* /system/app/
cp /sdcard/doneframework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system
reboot
what am i missing?
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
sync
reboot
also u can find them here as i done this to intgrade arabic to streak its in done_app & done_fram
my rom 345
http://hotfile.com/dl/110981641/4de9442/arabic_streak_345_15380_00.7z.html
bump..
can you guys post a quick guide with steps on how to do this? How hard is it to go back and edit files later like services.odex? if it doesn't exist anymore?
I have no idea what bump means......forum noob obviously.
But if you search auto deodex 2.3 in xda forums it is under droidx forums.
So I changed the mount command to yaffs2 /dev/bkock/mtdblock6 where theirs is different because from what I understand, that is the streaks mount command for mounting.
But I will try the other path and see if it works. I will keep you updated when I try it later.
freepal08 said:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
sync
reboot
also u can find them here as i done this to intgrade arabic to streak its in done_app & done_fram
my rom 345
http://hotfile.com/dl/110981641/4de9442/arabic_streak_345_15380_00.7z.html
Click to expand...
Click to collapse
so I tried your command path and no luck. still stuck on the dell logo.
Thank GOD for nandroid backup.
how exactly did you deodex your files? maybe thats what i am missing. Maybe the deodexed files i put in have an issue.
i used xUltimate-v2.2.2
and if u are 345 rom
u can use my files
also its take up to 10 min to load the phone
Krad said:
bump..
can you guys post a quick guide with steps on how to do this? How hard is it to go back and edit files later like services.odex? if it doesn't exist anymore?
Click to expand...
Click to collapse
Whenever you edit services.odex you first doedex it...then you modify it...then you carefully and painfully re-odex it...with a deodexed file system you get rid of the first and last steps...
so it would be services.dex, you copy it to your pc, edit it, and send it back...quicker and easier modding
freepal08 said:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
sync
reboot
also u can find them here as i done this to intgrade arabic to streak its in done_app & done_fram
my rom 345
http://hotfile.com/dl/110981641/4de9442/arabic_streak_345_15380_00.7z.html
Click to expand...
Click to collapse
ok I am trying your files. I see you put sync as your last command after you remount. that differs than the droidx forum How to manually deodex thread.
what does sync do?
I got farther with your files than i have before. So maybe I might have some luck after all, but still stuck on a frozen boot animation
I have no idea what I did differently but I am now deodexed using the file provided above.
My phone is now a rooted and deodexed 345 build. Nice!

[Q] how to cook room or delete folder ADB?

I have just cooked my rom( update.zip) and successful installation. But when I restart my mobile, I can't find my settings in bootanimation.zip, Build.prop...
I open Root Explorer and find folder ADB. This Folder has: adb.sh, bootanimation.zip, Build.prop… I can delete this folder but when I restart my mobile, I see it again.
I open file: adb.sh. It has content:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p6 /system
mount -o rw,remount -t ext4 /dev/block/mmcblk0p3 /data
mkdir /data/app
cat /adb/gotiengviet3.apk>/data/app/gotiengviet3.apk
chmod 0644 /data/app/gotiengviet3.apk
mkdir /system
cat /adb/build.prop>/system/build.prop
chmod 0644 /system/build.prop
mkdir /system/media
cat /adb/bootanimation.zip>/system/media/bootanimation.zip
chmod 0644 /system/media/bootanimation.zip
mkdir /system/etc/permissions
cat /adb/com.google.android.features.vendor.xml>/system/etc/permissions/com.google.android.features.vendor.xml
chmod 0644 /system/etc/permissions/com.google.android.features.vendor.xml
rm /adb/gotiengviet3.apk
rm /adb/build.prop
rm /adb/bootanimation.zip
rm /adb/com.google.android.features.vendor.xml
how to cook room or delete folder ADB?

SH Script help?

Hello guys, ok I do not know anything when it comes to shell script but last night i came up with an idea of creating a script to backup a rom boot animation and replace it with a new one. Ive probably completly f****d this up as i do not know anything:laugh:
Code:
#mount android root
/tmp/busybox mount /
#make folder called boot on sdcard
/tmp/busybox mkdir /sdcard/boot
#copy old bootanimation.zip to boot folder on sdcard and call it bootanimation.bak
/tmp/busybox cp /system/media/bootanimation.zip /sdcard/boot/bootanimation.bak
#delete bootanimation.zip from rom
/tmp/busybox rm -f /system/media/bootanimation.zip
#copy bootanimation.zip from sd card to rom
/tmp/busybox cp /sdcard/animations/bootanimation.zip /system/media/bootanimation.zip
#unmount andriod root
/tmp/busybox umount -l /
exit 0
could someone please tell me if there is any smidge of a chance that this will actually do something please? Thanks

Categories

Resources