Hi,
I got 4 days ago my new ARIA & this is really amazing machine.
I root the device & also tried installing the latest rom published in the forum - cm-6.0.2.1 but i liked more the originl ROM which came with the device.
The only problem i'm facing with the original ROM is that it doesnt support the Hebrew language so i'm getting squares instead of letters.....
I tried to use DejaVuSans.ttf solution.... the one with the instructions to do in the terminal the following commands:
1. mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
2. chmod 4755 /system/fonts/DroidSansFallback.ttf
3. dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
4. reboot
The 2 first command lines worked ok but when i'm putting the dd line (#3) , i'm getting an error saying there is no room on the device & then it gives me 2 lines - something about 0+1 checked in & 0+0 checked out.
After rebooting the device, its not sulving the Hebrew problem, any thoughts?
i want to keep the same rom & not updating it, just adding language fonts....
Eran.
So the current update, after fighting with the device i was able to complete the replacment of the DroidSansFallback.ttf file but it didnt solve the problem, i still getting squares......
Please anyone can help me with that, i really need it.
I am running win7 32bit, Google SDK installed, xoom root zip extracted to SDK, file moved from platform tools to tools)
http://forum.xda-developers.com/showthread.php?t=1010568
i've followed this thread all the way, but always get stuck at the fastboot flash boot boot.img . (file taken from xoom root zip) once it has completed i do the reboot from ADB, and i am stuck at the dual core technology screen. If i flash the US MX604 boot.img it lets me boot but wifi is fubar'd. If I use the canadian files it stays stuck on dual core screen.
Has anyone encountered this at all? its starting to be quite annoying and through all the threads i have gone through nothing points me to the same issue or a good fix for it. I can see people using tiamat 1.4 boot.img but can't seem to get my hands on that file.
I did not post this in the dev because i'm a lurker and have not been posting much.
Merci!
*****
HTC Desire Rooted
Motorola Xoom, getting me angry
so I was able to flash tiamat 1.4.0 boot.img, still cant write files to any folder in /system, and now my wifi is fubar'd
done!
ran these 2 commands in adb shell
# mount -o rw,remount /system
# CHMOD 777 /SYSTEM
and was able to write to /system after, with the boot.img from tiamat 1.4.0 and wifi is working.
I would not change the permissions to 777 on /system
You will need to do "adb remount" and then push the superuser files to /system.
whats should i change it too, befor changing it to 777 it would not let me push to any folders under /system because write was off, and if I only did # mount -o rw,remount /system , it still would not turn on..
After i succesfull deodex my stock rom i've decided to share my experience with ya'll people ...
Here we go :
1. You must be rooted !!!
2. Download -> xUltimate
3. Unzip xUltimate v2.2, and launch "Main.exe"
4. Now xUltimate should recognize the phone and make a connection. You now should see a list of options.
5. Run option 1. After option 1 is done, run option 2.
6. Now these well take a while. Run option 3
7. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
8. Now run option 4, and wait.
9. Exit xUltimate, and put the phone in USB mass storage then copy "done_frame", and "done_app" to the root of the sdcard then put the phone in PC mode.
10. Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
After phone is boot, reboot again in CWM and Wipe Dalvin Cache, reboot and ENJOY !!!
Notice : The boot will take a little bit longer than normal (2-4 seconds +)
P.S. For step 7 ... there is no guava.odex, don't worry about, continue to next step !
Credits :
Rainabba, Mike919, toxman, teenfaces, Xeudoxus !
Fisrt post ! Good work dude!!
You must have adb (by installing android sdk, platform-tools, install usb driver too) and jdk to do this if anyone is wondering.
kevinlekiller said:
You must have adb (by installing android sdk, platform-tools, install usb driver too) and jdk to do this if anyone is wondering.
Click to expand...
Click to collapse
I assumed that those who want to deodex their rom already knew that, anyway, thanx for reply
Nice tutorial!
Sent from my GT-S5830 using xda premium
Thanks y'all, I will also post other tutorials if i discover something interesting !
I know this question is stupid, but what's the difference between odexed and deodexed rom?
Yesterday I was trying to figure out how to deodex and today you make a tutorial, lol
Thanks.
excellent!! could create one of how to add cf-root and menu extended to create custom roms, is the last thing I need to learn to develop roms
tazlooney89 said:
excellent!! could create one of how to add cf-root and menu extended to create custom roms, is the last thing I need to learn to develop roms
Click to expand...
Click to collapse
Cf root xd to easy
Its in th .zip self
Just extract look in folder and place them where they belong
Sent from my GT-S5830 using xda premium
thanks dude!
now i can get pdroid running on stock rom *_*
Great tutorial thanks!
It would be great if you show how to enable CRT animation in any stock rom ang make grouping widgets in menu.
P4qui7o said:
After i succesfull deodex my stock rom i've decided to share my experience with ya'll people ...
Here we go :
1. You must be rooted !!!
2. Download -> xUltimate
3. Unzip xUltimate v2.2, and launch "Main.exe"
4. Now xUltimate should recognize the phone and make a connection. You now should see a list of options.
5. Run option 1. After option 1 is done, run option 2.
6. Now these well take a while. Run option 3
7. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
8. Now run option 4, and wait.
9. Exit xUltimate, and put the phone in USB mass storage then copy "done_frame", and "done_app" to the root of the sdcard then put the phone in PC mode.
10. Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
After phone is boot, reboot again in CWM and Wipe Dalvin Cache, reboot and ENJOY !!!
Notice : The boot will take a little bit longer than normal (2-4 seconds +)
P.S. For step 7 ... there is no guava.odex, don't worry about, continue to next step !
Credits :
Rainabba, Mike919, toxman, teenfaces, Xeudoxus !
Click to expand...
Click to collapse
Superb Tutorial Dude...
I am currently testing @Jusadas latest "Carbon Sunday Beta1" rom... It is fully odexed & so far is bug free (Totally)...... I would like to try & DeOdex the rom so that PDroid & Patch can be implemented...
I Know that PDroid framework has now been ported for Odexed roms, but when I flash the Odexed version I get stuck at Android txt during boot...
Will report back if your technique works...
Stay Breezy n Be Lucky...
Pe"ACE"...
Thanx man what a great work , i actually look for deodexing method coz i want to translate an odexed rom but i has to be deodexed first
I'll give it a shot !
Excellent guide!!!
Will try it tmw
Thanks =)
Sent from my GT-P6800 using xda premium
Well the title says manually deodex. But this uses the tool. To manually do it you need to decompile each app individually and then edit it.
Btw, nice giude..
TeamCooper Developer
TheMyth Developer
www.teamcooper.net
ERROR!
Tried this on my stock ddkq8 gingerbread 2.3.6 rom. But whenever I run this line: busybox cp /sdcard/done_app/* /system/app/
it says cp: No space left on device.
and my phone bricks.
It seems that the command does not overwrite the files in /system/app and thus the error.
BTW what do you mean by pc mode?
PLS reply!
galaxyace152 said:
Tried this on my stock ddkq8 gingerbread 2.3.6 rom. But whenever I run this line: busybox cp /sdcard/done_app/* /system/app/
it says cp: No space left on device.
and my phone bricks.
It seems that the command does not overwrite the files in /system/app and thus the error.
BTW what do you mean by pc mode?
PLS reply!
Click to expand...
Click to collapse
Before "10. Open a command prompt, and do the following:"
Just delete some apps to make 40 mb free in system !
That's how i did and work's
Use Root Explorer or something
shaaan said:
Well the title says manually deodex. But this uses the tool. To manually do it you need to decompile each app individually and then edit it.
Btw, nice giude..
TeamCooper Developer
TheMyth Developer
www.teamcooper.net
Click to expand...
Click to collapse
Developer Talking
---------- Post added at 08:57 PM ---------- Previous post was at 08:56 PM ----------
Stuck on boot loop! :| And yes, I wiped everything. Nice tutorial BTW, appreciate it.
EDIT: Never mind. Sorted it.
C:\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# stop
stop
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_app/* /system/app/
cp: can't stat '/sdcard/done_app/*': No such file or directory
# busybox cp /sdcard/done_frame/* /system/framework/
busybox cp /sdcard/done_frame/* /system/framework/
cp: can't stat '/sdcard/done_frame/*': No such file or directory
# rm /system/app/*.odex
rm /system/app/*.odex
# rm /system/framework/*.odex
rm /system/framework/*.odex
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# reboot
reboot
C:\android-sdk-windows\platform-tools>
how come mine is like this...? anyone can help me...? plz
after that my phone cant start...it stuck on the galaxy ace screen...???
Hi everyone.
I've been sitting for almost 6 hours trying to get my wifi fixed after upgrading to 4.3 and rooting it etc.
Last time I tried I was unable to stick to carrier network but wifi was working.
This time it was the other way around.
After ALOT of trying and failing, I finally fixed it.
mount -o rw,remount /
and
mount -o rw,remount /system
after this it was just to set permissions, I did chmod -R 777 on /dev and /system/etc/wifi
My guess, without any more checking, is that alot of permissions are set wrong within the image I downloaded from samsung-updates, and the one from sammobile, that is from samsung themselves.
The weird thing is that my father has a 100% stock phone wich got the update, it all worked like a charm.
Min did not, and it was not rooted......until now with knox 0x1 and everything else
Also, I did alot of searching, but the only thing I found was a fix for my modem, wich did nothing for me.
And since I did not find anything else, I figured this might help others in the same situation
Update: the "fix" has to be re-done after reboot.
Anyone has a better fix ?
It doesn't help with full wipe and reinstall.
Hi,
I have the same problem here
How do I?:
mount -o rw,remount /
and
mount -o rw,remount /system
Thx
garfieldnl said:
Hi,
I have the same problem here
How do I?:
mount -o rw,remount /
and
mount -o rw,remount /system
Thx
Click to expand...
Click to collapse
after mount -o rw,remount /system
do a
chmod -R 777 /system/etc/wifi (I think this one makes the difference)
and
chmod -R 777 /dev
All requires root
I had a similar problem - no matter what I tried, I couldn't turn the wifi on, quick toggle would immediately switch back off and same in Settings. Every time I tried to switch it on I also got a Knox warning. Brilliant, well done Samsung.
I did some reading and it seems you can turn it on if you use a custom Kernel, but by then I'd given up and installed PacMan ROM, which will do until a proper 4.4 comes out.
darfbozo said:
I had a similar problem - no matter what I tried, I couldn't turn the wifi on, quick toggle would immediately switch back off and same in Settings. Every time I tried to switch it on I also got a Knox warning. Brilliant, well done Samsung.
I did some reading and it seems you can turn it on if you use a custom Kernel, but by then I'd given up and installed PacMan ROM, which will do until a proper 4.4 comes out.
Click to expand...
Click to collapse
I have tried two kernels, none of them fixed the problem, so for now the workaround have to work, I'm refusing to flash my phone.....again
Tody I actually had to go back to 4.2.2, I happy I for once did a nandroid backup yesterday befor I flashed 4.3, the phone stopped responding a few minutes after reboot, and gave me a flashing red light i the upper left corner, when screen was on.
After screen went off, the red light changed to a blue light.......
And I just saw that samsung pulled the 4.3 update as well....
I think my nex phone will be a nexus....if they at some point come with microsd slot.....if not.....perhaps going back to my old Nokia 6150, it was rock stable and had a week of power on one charge.
Hi,
i can't get a folder to mount on Android N while. On MM i just did it with init.d
Code:
mnt_boot
Code:
#!/system/bin/sh
sleep 10
mount -o bind /mnt/media_rw/6EF2-A903/.WhatsApp /data/media/0/WhatsApp
That worked well, but on N i can't get it to work. Anyone has a idea what's going on there or if it's a bug?
MorpheusKiller said:
Hi,
i can't get a folder to mount on Android N while. On MM i just did it with init.d
Code:
mnt_boot
Code:
#!/system/bin/sh
sleep 10
mount -o bind /mnt/media_rw/6EF2-A903/.WhatsApp /data/media/0/WhatsApp
That worked well, but on N i can't get it to work. Anyone has a idea what's going on there or if it's a bug?
Click to expand...
Click to collapse
Hi,
same problem on cm14.1. Cause of this seems to be different name spaces.
Start terminal su and you will see the mount.
I've no idea how to switch the name space while executing the init script.