All credits go to pulpoff2 for this! This is not by me, I am merely the messenger. Only thing I did was to ask pulpoff for the files and a tutorial With his permission I will share it with you.
This will provide you with a fresh and unmodified 2.1-system, exactly like you would do the official update - only exception is that it is rooted. So all the apps and games of the official firmware are available and nothing else. You can remove the crap (like the games or timescape for example) by yourself after doing the steps below.
UPDATE:
There is a newer ROM by propc you can use instead of this one. Look here:
http://forum.xda-developers.com/showthread.php?t=888427
-- NEW --
propc kindly provides us with a shellscript to automate the steps below. See here for the script and a short manual:
http://forum.xda-developers.com/showpost.php?p=10067921&postcount=120
If the script doesn't work for you or you prefer to do things the manual way, you may use the steps below.
Download these files:
x8-2.1rooted.img.yaffs.rar
and
ISO-8859-1__unyaffs-arm.rar
Also download the 2.1-firmware from here or here. Unpack it on your computer and delete the "system.sin".
Unpack "x8rooted.img", "busybox" and "unyaffs" to SDcard.
You need 1.6 with root on your phone. By the way, all the data on your phone will be lost after doing the following steps, so making a backup is advised.
Use "adb shell" to connect to your phone and become su:
Code:
su
Copy "busybox" and "unyaffs" to /data/local/tmp. (Pulpoff says you should copy to /sbin, but this requires remounting with busybox. I copied to /sbin, but I think /data/local/tmp should work just fine)
Code:
cd /data/local/tmp
cat /sdcard/busybox > busybox
cat /sdcard/unyaffs > unyaffs
chmod the files to make them executable:
Code:
chmod 755 busybox
chmod 755 unyaffs
EDIT: If you want to copy the files to /sbin (like pulpoff2 advises), you can do this OPTIONAL step:
EDIT2: It was confirmed that this is indeed not necessary!
Remount the root directory to make /sbin writable. Then copy the files over and change the working directory to /sbin:
Code:
[strike]
./busybox mount -o remount,rw /
./busybox cp -prf busybox /sbin/
./busybox cp -prf unyaffs /sbin/
cd /sbin[/strike]
Remount /system as writable:
Code:
mount -o remount,rw /dev/block/mtdblock0 /system
Switch to busybox shell:
Code:
./busybox sh
Remove /system (yes, really!). It's normal to get errors because of the "lost+found"-folders. Ignore the errors.
Code:
./busybox rm -r /system
Unpack pre-rooted image to system. It should output "end of image" if it finishes correctly.
Code:
./unyaffs /sdcard/x8rooted.img /system
Your phone won't boot anymore now and it will crash as soon as you try to use it - that's normal! Go to next step.
Just remove the battery and the usb-cable from the phone, then re-attach the battery. Flash 2.1-kernel (without system.sin !!) using the flasher-tool by Bin4ry. If the flasher gives you an error because of a missing "loader.sin" you can take this file from the 1.6-firmware. Refer to Bin4ry's thread to learn how to use his flasher and how to enter flash-mode on your phone.
The phone should now boot, although the first boot can take a little while. If you get into a boot-loop or you just see the white sony ericsson logo (not the green one after the animation) for several minutes, it probably didn't work and you have to start over again by flashing 1.6.
This was written as I remember how I did it by myself. It worked for me at first try! If it works for you, please click the thanks-button. It will make me feel better
After you have your nice rooted 2.1 you probably want to enable JIT for a nice performance boost.
But does it have root? Bad reading.
{
"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"
}
a-k-t-w said:
But does it have root?
Click to expand...
Click to collapse
Absolutely. But no busybox. So if you plan to enable JIT, you have to copy busybox to /system/bin by yourself.
a-k-t-w said:
But does it have root? Bad reading.
Click to expand...
Click to collapse
of course it is rooted.
now we know what to do with unyaffs.
2 things:
1. I've bought the phone with 1.6 android, but I was unable to root it with any method, then I've upgraded to 2.1 update 1. Is there any way to root it?
2. I have Hungarian language. Does it contain Hungarian language?
csengoi said:
2 things:
1. I've bought the phone with 1.6 android, but I was unable to root it with any method, then I've upgraded to 2.1 update 1. Is there any way to root it?
2. I have Hungarian language. Does it contain Hungarian language?
Click to expand...
Click to collapse
1: There is no way to directly root a phone with 2.1. You need to go back to 1.6, root it and then follow the above steps.
2: I guess so. As far as I know the firmware is the same for all countries.
Works like a charm! I removed the /system folder contents one by one though, using the method from the previous thread. Anyway, the first time I tried, unyaffs exited before extracting all the files (maybe the phone ran out of memory?). I didn't notice it and went on to flash the phone, ending up stuck at the Sony Ericsson logo. So, make sure that unyaffs reports that it has reached the "end of image" before moving on to the next step!
Thanks!!
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
how to proceed?
isaac12 said:
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
how to proceed?
Click to expand...
Click to collapse
in adb shell:
enter su and you have to look your mobile screen because it will ask you to allow su. (if you rooted well your phone)
i had this problem when i didn't press the allow button in superuser confirmation.
---dobule post--- sorry
trapacska said:
in adb shell:
enter su and you have to look your mobile screen because it will ask you to allow su. (if you rooted well your phone)
i had this problem when i didn't press the allow button in superuser confirmation.
Click to expand...
Click to collapse
rooted phone yes
su confirmed
cd /data/local/tmp
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
does it mount data.img on sdcard???
or i'll need to use chargemon from previous way?
WARR10r said:
does it mount data.img on sdcard???
or i'll need to use chargemon from previous way?
Click to expand...
Click to collapse
This has nothing to do with App2SD. Also the ROM gets loaded from internal flash, not from sdcard. The result is the same as with the official update, but with root.
If you want to have /data on sdcard, use the modified chargemon or neptun2's method.
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
gully666uk said:
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
Click to expand...
Click to collapse
try adding ./ before
gully666uk said:
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
Click to expand...
Click to collapse
You should still be in "/data/local/tmp" as the working directory (check with "pwd"-command). If you followed the steps correctly, you should have a working busybox-file in there. So just type "busybox sh". If it looks like it does nothing, it's all right
isaac12 said:
rooted phone yes
su confirmed
cd /data/local/tmp
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
Click to expand...
Click to collapse
try to use another su. i rooted my x8 with superoneclick 1.5.0
I got stuck at SE logo for at least 10mins, it doesnt re-boot cycle although..
Sectoras said:
I got stuck at SE logo for at least 10mins, it doesnt re-boot cycle although..
Click to expand...
Click to collapse
That's way too long, something isn't right there. To start over again you have to flash back to 1.6.
Ok I had not realised the superuser permissions was not popping up on my phone that's sorted now. I get to number 8 again and it said permission denied
Related
Hello everyone,
Its been great to have root on your X10 using the method posted here:
http://forum.xda-developers.com/showthread.php?t=711907
Well, this method works all right but I did some investigating of my own to audit the state of the system after its been rooted. Thanks to the discussions you may find here: http://forum.xda-developers.com/showthread.php?t=712178, the original developers soon chose to update the Rooting tutorial with some additional steps (See post #2 and #4 of the rooting thread). This is all good, because now you have the real power to act as a the *real* superuser i.e uid 0.
Most of the discussions that follow are only intended for users who are well versed with general *NIX security and concepts about user ids, permissions and other things. So please disregard this post if you have no ideas of these concepts.
Ok, so first things first. I basically followed the root tutorial as it is all the way upto step3 (or step3a as in my case). Remember, you essentially have a rooted phone right after step2, step3/3a just adds the updated baseband firmware, which has no effect whatsoever on the subsequent things that you do to your phone.
Well essentially, what I did do was install the "su" binary and the "Superuser.apk" following in the lines of step4v2 (post #2 in root thread). These are essential to give you control over your system as without them you are simply relying on a hacked "sh" binary which runs with elevated privileges. Here are the file permission masks for the "sh" binary which gets installed after the FOTA in step2:
Code:
# ls -l sh
ls -l sh
-rwsrwsrwx root root 86944 2010-06-28 18:08 sh
#
Wait!!! This is *not* quite ok. What this means is that any process can use this binary to gain super user privileges. This binary is setuid and setgid root!!!
Well you might say that... so is the case for "su":
Code:
# ls -l su
ls -l su
-rwsrwsrwx root root 22120 2010-06-28 08:08 su
#
But, this is different because its use is controlled by the Superuser Whitelist application that was installed with Superuser.apk.
This difference is crucial because if any non-privileged application and process forks and execs "su", the Superuser Whitelist app would immediately post a notification screen on the phone and provide options to allow or disallow.
With the "sh" binary installed on your phone as it is, you are basically inviting *any* application to be able to do anything it wants to your phone... and all this without your knowledge!!!
To test this theory, all you need to do is simply install one of the terminal emulators floating around the market or use the one provided in the rooting thread under the step4/app folder and launch it. It straight away, launches you into a root shell. Here is a screen shot of what you can do this way:
{
"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"
}
(Remember, no warnings, no notifications and all this can be done by any app under the hood)
Here is what you can do to make your phone more secure.
Step1: Download an alternative shell or simply change the permissions on the "sh" binary:
Code:
# cd /system/bin
# chmod 755 sh
Step2: In case you downloaded an alternative shell like "bash" and copied it under your /system/bin folder, simply get rid of the original "sh" binary and create a symlink to the one you download, for ex: bash:
Code:
# cd /system/bin
# rm sh
# ln -s bash sh
(Note: the above steps assume that you have /system mounted as rw, if you don't know what that means, then you should not be reading this, sorry)
Remember, when installing any alternative shell make sure that its permission mode is set to 755 or lower. I recommend to *never* set the setuid and setgid bits on the shell!!!
Here is what I did personally:
Installed bash from here: http://forum.xda-developers.com/showthread.php?t=537827
Installed it under /system/bin *without* the setuid and setgid bits
Removed the "sh" binary
Created a symlink named "sh" to the binary "bash"
This way, whenever I launch "adb shell" or use any terminal emulator on my phone, I always get a un-privileged shell. To get root, simply fire "su".
PS: This information is not intended for casual users who have limited or no knowledge of UNIX or UNIX like sytems like Linux, Adrdoid SDK commands like adb or don't know their way around if faced with a command line!!!
PS: Another post with some steps to properly secure the system: http://forum.xda-developers.com/showthread.php?t=712945
lmao..
http://forum.xda-developers.com/showthread.php?t=712945
zephyrix said:
lmao..
http://forum.xda-developers.com/showthread.php?t=712945
Click to expand...
Click to collapse
lol, you must've done this while I was writing mine!!
Anyways, its good to have this info out and I do point out some concepts detailing *why* this is a problem.
Definitely.
Make sure people have installed a proper way to elevate to root before attempting to change sh to not setuid, or they may screw themselves over lol
Thanks for your guide! Much appreciated would be an understatement.
is there any other way of testing that as using tht method in ur given picture now says read only error does this mean i successfully secured my root?
bcool15 said:
is there any other way of testing that as using tht method in ur given picture now says read only error does this mean i successfully secured my root?
Click to expand...
Click to collapse
Oh... I think I forgot to show this, but essentially you need to get the system partition into read/write mode as well. So it will be one more command before the write is attempted:
# mount -o remount,rw -t yaffs2 /dev/mtdblock2 /system
...
...
# echo "I can...
j4mm3r said:
Oh... I think I forgot to show this, but essentially you need to get the system partition into read/write mode as well. So it will be one more command before the write is attempted:
# mount -o remount,rw -t yaffs2 /dev/mtdblock2 /system
...
...
# echo "I can...
Click to expand...
Click to collapse
thats the command which stoppped wrkin so i just redid whole rooting procedure with new v3 update does it still need securing?
bcool15 said:
thats the command which stoppped wrkin so i just redid whole rooting procedure with new v3 update does it still need securing?
Click to expand...
Click to collapse
Dont worry about the example shown in the screen shot. That is just to illustrate what a setuid "sh" binary can do to your system.
j4mm3r said:
Dont worry about the example shown in the screen shot. That is just to illustrate what a setuid "sh" binary can do to your system.
Click to expand...
Click to collapse
this securing procedure isnt working on my new root any suggestions?
please
Regards,
bcool15 said:
this securing procedure isnt working on my new root any suggestions?
please
Regards,
Click to expand...
Click to collapse
Exactly what procedure are you referring to? The post is just meant to be a set of guidelines of a vulnerability that existed on the phone after it was rooted using "the root procedure" at the time this was posted.
If you have a "sh" binary on your phone which is setuid and setgid, then you have this vulnerability. I haven't updated the post with results from any new root procedures that have been posted since, but I suspect even the newer methods posted so far in the "root thread" don't get rid of the compromised "sh" binary.
Please ignore if you don't know what setuid and setgid means.
Maybe it's a known way, but I didn't find it yet . It works great for me. Your device has to be rooted.
Zocker Tko mentioned in his thread a black theme on a german forum. There's a little tutorial on that site on howto replace the framework-res.apk using Root Explorer:
* make a backup of the original file
* Copy framework-res.apk to the SD card
* Mount /system in RootExplorer as "rw"
* Copy framework-res.apk to /system
* Set permissions for framework-res.apk to 644. See 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"
}
* Move framework-res.apk to /system/framework and replace the existing file (reported to be safer than copy).
* Reboot your phone.
Ofcourse all credits goes to Bueffel the original poster.
i didn't know this...
thanks for sharing!
Can this work with 2.1?
vippie said:
Maybe it's a known way, but I didn't find it yet . It works great for me. Your device has to be rooted.
Zocker Tko mentioned in his thread a black theme on a german forum. There's a little tutorial on that site on howto replace the framework-res.apk using Root Explorer:
* make a backup of the original file
* Copy framework-res.apk to the SD card
* Mount /system in RootExplorer as "rw"
* Copy framework-res.apk to /system
* Set permissions for framework-res.apk to 644. See screenshot:
* Copy framework-res.apk to /system/framework and replace the existing file.
* System reboots. If it doesn't reboot it yourself.
Ofcourse all credits goes to Bueffel the original poster.
Click to expand...
Click to collapse
thanks for the hint, but the framework on german site will it work on all mini pros with different lang??? and that file to download there
yea it works great = language netural
morning_wood said:
yea it works great = language netural
Click to expand...
Click to collapse
Just to double check, is that in reply to me. hehe
Mitchio said:
Can this work with 2.1?
Click to expand...
Click to collapse
Yes, I've done this on 2.1. The framework-res has to be a 2.1 version too ofcourse!
morning_wood said:
yea it works great = language netural
Click to expand...
Click to collapse
Yes no more blue :-D
Sent from my U20i using Tapatalk
the instructions are great, I actually use the "move" command after setting permission ( copy to /system, set permissions, then "move" to /system/framework = no auto-reboot )
My phone reboots as stated, but then it hangs at the Sony Ericsson logo
whooper90 said:
My phone reboots as stated, but then it hangs at the Sony Ericsson logo
Click to expand...
Click to collapse
I had this with other methods. Use PC suite or SEUS to restore.
vippie said:
I had this with other methods. Use PC suite or SEUS to restore.
Click to expand...
Click to collapse
I did a bunch of times now
But I want to get rid of the blue shi**y layout xD
EDIT: It works with the move instruction at the last step, instead of the copy instruction
Edit:
Doesn't matter now, just gonna start afresh...
whooper90 said:
I did a bunch of times now
But I want to get rid of the blue shi**y layout xD
EDIT: It works with the move instruction at the last step, instead of the copy instruction
Click to expand...
Click to collapse
For me.... (x10 mini with 2.1 Generic UK) with file "framework Black Build 2.0.A.0.504(111110).rar"
1) Copy framework res apk to sdcard:
adb push framework-res.apk /sdcard/framework-res.apk
2) Set permission (see first post) with rootexplorer on /sdcard/framework-res.apk
3) Copy with rootexplore YOUR OLD /system/framework-res.apk to /system/
3a)IMPORTANT!!! Rename framework copied in /system to framework-res.apka
3b)Copy new framework with RootExplorer from sdcard to /system
4) adb shell
5) su
6) mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
7) dd if=/system/framework-res.apk of=/system/framework/framework-res.apk
If you see:
records in
xxxx records out
xxxx bytes transferred in xxxx secs (xxxx bytes/sec)
It's OK..
Your phone is rebooting, if you have any trouble after 2 minuts, don't reboot, with your hands, but:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
dd if=/system/framework-res.apka of=/system/framework/framework-res.apk
and you have the old framework again
My good log....
C:\android\tools>adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
# dd if=/system/framework-res.apk of=/system/framework/framework-res.apk
dd if=/system/framework-res.apk of=/system/framework/framework-res.apk
17015+1 records in
17015+1 records out
8711993 bytes transferred in 4.007 secs (2174193 bytes/sec)
My bad log.... My phone with only Sonyericsson log, I DIDN'T REBOOT!!!!
C:\android\tools>adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
# dd if=/system/framework-res.apka of=/system/framework/framework-res.apk
dd if=/system/framework-res.apka of=/system/framework/framework-res.apk
17357+1 records in
17357+1 records out
8886815 bytes transferred in 3.914 secs (2270519 bytes/sec)
Sorry for my English...
whooper90 said:
EDIT: It works with the move instruction at the last step, instead of the copy instruction
Click to expand...
Click to collapse
Nice! Did try it too. Had to reboot manually afterwards, but it worked fine! I'll edit the first post.
thanks to vippie and to dettofatto
its really a good way, i have tested it with root explorer on my x10i and it worked!
but i don´t know what is safer, to work with rooteplorer or with adb shell, when something goes wrong, because i had the problem on my x10i a few days ago. I changed my framework with adb and there was no transfer, it reboot independently and it stand only on the Sonyericsson log, so i had to reflash it. I dont know why, because after reflashing, the same custom framework changed with adb worked. The problem was i think, there was no transfer and the phone reboots independently. So i had no chance to reach the phone over adb shell because permission permitted.
and i know no risk no fun, hehe, sry for bad english
BTW: the "German" framework-res is the BOMB!
It looks really nice that framework from german site, but wich file do i need to install?
x10 mini pro-black-framework-res190810.rar (1,83 MB, 257x aufgerufen)
x10 mini-black-framework-res190810.rar (1,83 MB, 200x aufgerufen)
SystemApps-Black230810.rar (6,07 MB, 201x aufgerufen)
framework-res-Black Build 1.2.A.1.174(280910).rar (2,83 MB, 73x aufgerufen)
SystemApps-Black Build 1.2.A.1.174(280910).rar (7,10 MB, 81x aufgerufen)
SytemApps Black Build 2.0.A.0.504(101110).rar (4,68 MB, 114x aufgerufen)
framework Black Build 2.0.A.0.504(111110).rar (2,54 MB, 97x aufgerufen)
?
And do i need to install all the system apps also to get the phone black?
How do you EDIT the framework-res.apk? how do you zip the file?
Do you have to zip the folder (it creates a folder inside the zip)? Or do you have to select all the contents of the folder and then zip those?
i'd like to thank the OP for the method, worked without trouble on my mini pro (generic french 2.1)
Hello,
i wish to create an update.zip to copy fonts from the zip into the system/fonts/ folder because i delete them and kept one font but it seems android doesn't boot with one font only need other fonts to be there (or atleast matching the names) to be able to boot.
adb push doesn't work giving me permission denied because /system is not mounted R/W (which i do using Super Manager for example)
i read other update.zip files and it seems i need to create CERT.SF and MANIFEST.MF files in META-INF , but it seems there are some SHA1-Digest: below each file (is this a md5checksum?) so i can't just replace file names and apply it
any ideas how can i do it without Wipe data/factory reset ? (and if factory reset is my last option would fonts be returned or factory reset doesn't get fonts back? i feel not)
Thanks
The app below will sign the zip and allow you to flash it. You just need to put the zip inside the folder and call it 'update.zip'
l0st.prophet said:
The app below will sign the zip and allow you to flash it. You just need to put the zip inside the folder and call it 'update.zip'
Click to expand...
Click to collapse
Thank you , any chance there i a Linux version out there? i'm using adb on ubuntu
and for CERT.SF and MANIFEST.MF i just create them manually based on any update.zip file i download earlier?
I'm on windows now and i've signed the file, when i try to apply it from recovery i get
E:signature verification filed
Installation aborted
what i'm missing?
attached my signed update.zip
it seems i had a folder update inside the zip
i have re-created one and signed it and still same error
attached the file
btw as i'm rooted and i used to su from adb shell and terminal emulator earier, any idea why su not working now?
$ su
[1] + Stopped (signal) su
$
[1] Segmentation fault su
$
is it because i'm on the HeRO logo boot screen ? it didnt get in yet?
btw for linux/ubuntu users who want to sign on linux you can use this:
Code:
java -jar signapk.jar testkey.x509.pem testkey.pk8 update.zip update_signed.zip
inside the Auto Sign folder
after signing on linux i get the following:
E: failed to read footer from / sdcard/update.zip (I/O error)
E:signature verification failed.
Installation aborted
First of all, please use the edit button, posting 6 times in a row is very hard to read, and is considered bumping your own thread which is a quick way to lose friends.
Secondly, the autoSign program creates a file called update_signed.zip which is the file you need to flash, the cert and manifest files are created by the process, you don't need to touch them. I have attached a signed version of your zip
I resigned it for you, see attachment. I use "androsign" I found here somewhere on XDA, maybe go look for it. It is a very easy tool edit: Too late
When you are in "adb shell" you should have SU rights already.
Otherwise there is an option in adb to switch to SU rights, just type in "adb help" of a howto.
First of all , sorry for the multiple posts
second i've tried both update-signed.zip and update_signed.zip and both of them gave me the same error
{
"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"
}
*P.S: sorry if i'm not allowed to put an image ill delete it
EDIT:
riemervdzee said:
When you are in "adb shell" you should have SU rights already.
Otherwise there is an option in adb to switch to SU rights, just type in "adb help" of a howto.
Click to expand...
Click to collapse
i tried to the help i didn't find how to set su in the right roots?
Have you flashed an alternative recovery at all? This one looks like the default one.
And look at the first error, it asks for a path in /cache/... Just get amon_ra recovery This way you can select which zip you want to flash (as long as they are in the root of the sd-card).
And from "adb help":
"adb root - restarts the adbd daemon with root permissions".
However seen you still have the original recovery, that probably won't work in recovery.
You said you rooted the device already right? maybe you can move the files with adb then when the ROM is trying to start, and after everything works get a real recovery where you can do something.
riemervdzee said:
Have you flashed an alternative recovery at all? This one looks like the default one.
And look at the first error, it asks for a path in /cache/... Just get amon_ra recovery This way you can select which zip you want to flash (as long as they are in the root of the sd-card).
And from "adb help":
"adb root - restarts the adbd daemon with root permissions".
However seen you still have the original recovery, that probably won't work in recovery.
You said you rooted the device already right? maybe you can move the files with adb then when the ROM is trying to start, and after everything works get a real recovery where you can do something.
Click to expand...
Click to collapse
yeah i tried the adb root already but getting "adbd cannot run as root in production builds"
yes i'm rooted and everything is fine
btw why deleting fonts prevents the phone from booting although there is one font there "not the default one"
what i want is to push the font files into the phone but getting the error i mentioned earlier that its not mounted as as R/W:
[email protected]:~/linux_adb_fastboot/hero_fonts$ for i in `cat list`; do adb push $i /system/fonts/$i ; done
failed to copy 'DroidSerif-Bold.ttf' to '/system/fonts/DroidSerif-Bold.ttf': Read-only file system
failed to copy 'DroidSerif-Regular.ttf' to '/system/fonts/DroidSerif-Regular.ttf': Read-only file system
failed to copy 'DroidSerif-Italic.ttf' to '/system/fonts/DroidSerif-Italic.ttf': Read-only file system
failed to copy 'DroidSansMono.ttf' to '/system/fonts/DroidSansMono.ttf': Read-only file system
failed to copy 'DroidSansFallback.ttf' to '/system/fonts/DroidSansFallback.ttf': Read-only file system
failed to copy 'DroidSerif-BoldItalic.ttf' to '/system/fonts/DroidSerif-BoldItalic.ttf': Read-only file system
failed to copy 'DroidSans-Bold.ttf' to '/system/fonts/DroidSans-Bold.ttf': Read-only file system
failed to copy 'Clockopia.ttf' to '/system/fonts/Clockopia.ttf': Read-only file system
failed to copy 'DroidSans.ttf' to '/system/fonts/DroidSans.ttf': Read-only file system
and yes adb remount doesn't work
[email protected]:~/linux_adb_fastboot/hero_fonts$ adb remount
remount failed: Operation not permitted
You have "rooted" your phone but you can't get adb root? That is contradictory
But since I'm in a good mood. Try to boot up the phone on your ROM, so not in recovery or bootloader. Then try to remount.
If remount is still failing, you don't have root.
Maybe you should also read your stuff a bit in before attempting anything. You are kinda screwing up your phone here.
Yes i'm sure i'm rooted i had universal root which i can root and unroot, and before deleting the fonts i used to do su and get root
also to confirm im rooted i used to use Market Access to access US and other markets to buy (since my country only has free apps not paid yet)
i didn't get the part of botting up the phone using my ROM ?
also a side question when booting the phone normally (i think this is what you meant about booting into the ROM?) and it stays on the HeRO logo as you can see i can access the adb shell etc.. so the phone is actually responding but not booting because of the fonts not there? or something else could be broken ?
Bashar . said:
Yes i'm sure i'm rooted i had universal root which i can root and unroot, and before deleting the fonts i used to do su and get root
also to confirm im rooted i used to use Market Access to access US and other markets to buy (since my country only has free apps not paid yet)
i didn't get the part of botting up the phone using my ROM ?
also a side question when booting the phone normally (i think this is what you meant about booting into the ROM?) and it stays on the HeRO logo as you can see i can access the adb shell etc.. so the phone is actually responding but not booting because of the fonts not there? or something else could be broken ?
Click to expand...
Click to collapse
Read "adb logcat" or in adb shell, use the linux command "dmesg" to see what is wrong.
And yes, with booting your ROM I mean the normal boot process. But probably android won't start as it can't find the fonts (they are essential).
And really... Read your stuff. You deleted fonts but didn't put any new there yet? You are asking for problems, while you ask us to solve it.
Then you come up with the plan to flash the new fonts, but you don't have a customized recovery.
riemervdzee said:
Read "adb logcat" or in adb shell, use the linux command "dmesg" to see what is wrong.
And yes, with booting your ROM I mean the normal boot process. But probably android won't start as it can't find the fonts (they are essential).
And really... Read your stuff. You deleted fonts but didn't put any new there yet? You are asking for problems, while you ask us to solve it.
Then you come up with the plan to flash the new fonts, but you don't have a customized recovery.
Click to expand...
Click to collapse
I did put one font there, but my mistake is not renaming it as the default font names that was there, i thought it would scan the fonts folder and use ANY font listed there
but seems not...
catlog shows im missing the fonts: http://dpaste.org/ADyJ/
dmesg output: http://dpaste.org/8IGw/
i never thought the recover it had won't let met flash the fonts
EDIT: i tried the mv command as linux user but my main problem is that its a read only system
[email protected]:~$ adb shell
$ cd system
$ cd fonts
$ ls
DroidSansArabic.ttf
$ mv
USAGE: mv <source...> <destination>
$ mv DroidSansArabic.ttf DroidSans.ttf
failed on 'DroidSansArabic.ttf' - Read-only file system
$
You can't do "adb remount" when starting normally? You have rooted the ROM, not the recovery (which refuses root access, as it is still the default one).
If everything fails, you can always do a RUU. (google "hero RUU"), this will reset everything as HTC wants it. Then you start from scratch again.
riemervdzee said:
You can't do "adb remount" when starting normally? You have rooted the ROM, not the recovery (which refuses root access, as it is still the default one).
If everything fails, you can always do a RUU. (google "hero RUU"), this will reset everything as HTC wants it. Then you start from scratch again.
Click to expand...
Click to collapse
yeah it seems thats my only option
I was hoping to learn by fixing, i'll flash it tomorrow then
now back to the question, why the update.zip that we were trying to sign is not flashable or signable ? what might be the reason? is it because i didn't root the recovery ?
i tried an stock Hero rom and still gives me invalid signature, i can't apply any rom at all now or what?
It's really about time somebody made a simple, easy and straight forward guide for installing mik_os's clever touchscreen kernal patch thing. I'm not android genius and really struggled to install this having no knowledge of how androids really work inside. Trying to figure out how to install the much needed touchscreen fix was a disaster but I finally got it right.
Due to a lack of simple and easy to follow guides I have made this one to help out other beginners, who like me didn't receive the help they need despite hours of google searches.
WARNING: If you do something wrong, or if something breaks while you are following this guide, I'm not responsible for any of your actions. Do this at your own risk.
The files provided are not my work and I take NO credit for them. They were created by clever people to help our lives
Credits:
kernal/touch screen bug fix: mik_os http://forum.xda-developers.com/showthread.php?t=929941
z4root : RyanZA http://forum.xda-developers.com/showthread.php?t=833953
Custom recovery: getitnowmarketing http://androidforums.com/getitnowma...ry-optimus-one-p500-thunderg.html#post1896517
Firstly this guide shows you how to root and then flash your phone with mik's fix. I'm not very good with androids but this worked and is pretty fault proof if you follow the steps. BEFORE BEGINNING MAKE SURE YOU HAVE FULL BATTERY!
1) Make sure you have Froyo 2.2. To check what version you have go to settings> about phone> android version. If you have 2.2.1 or something I really can't help you, do a bit of searching on how to downgrade. Explaining it will only complicate things if you are knew to androids like me.
2) Click this : http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
3) Save it to your computer, plug your phone into the USB port and copy the newly downloaded file onto it(by enabling mass storage device thing on your phone) and just pasting it in there not in any folder.
4) On your phone open the android market, search for Astro file manager. Choose to install it(wait for download and install to complete).
5)Open Astro File manager and locate the file you downloaded (z4Root by RyanZa) using astro (it'll be in the sd folder on its own). Select z4Root and install it and run it after installing.
6) Choose to permanently root your phone(this voids your warranty btw). Let it do its stuff, your phone will restart and you will be a super user! win.
7)Next download this:
http://www.mediafire.com/file/uf752h914q0u228/recovery-RA-GNM-thunderg-1.1.0.img.zip
and
http://www.mediafire.com/?45u0obd6pjj5twp
(Do not extract this file only the others)
and this
http://androidforums.com/attachment...ery-optimus-one-p500-thunderg-flash_image.zip and extract both of them into folders.
(thanks to getitnowmarketing for guidance at this point)
Next do one of the following two methods:
METHOD A(EASIER):
8)Download & install:
Google Chrome to phone(PC Google Chrome extension)
Google Chrome to phone(Phone app)
Terminal Emulator (Phone app)
9)Synchronize your Google account in Chrome to Phone(browser extension and phone app) and make a test by sending something to your phone(link,text).Make sure it's working.
10)After that open Terminal Emulator and type "su"(without quotes) and click yes when it's asking you for Superuser permission."#" will appear.
{
"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"
}
11)From the commands list below copy every line (except red one) one by one and send it to phone.On phone paste all commands one by one,as you send them from Chrome, in Terminal Emulator.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
[COLOR="Red"][U](if it shouts at you here saying not found or something,ignore it)[/U][/COLOR]
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
reboot recovery
12)Wait a bit and your mobile/phone will turn off, hold in the down volume key and the home key. Keep them held in for a bit when the LG logo comes up.
Skip to step 16!
OR:
METHOD B
8) Now download this: http://dl.google.com/android/android-sdk_r09-windows.zip (windows) or http://dl.google.com/android/android-sdk_r09-linux_x86.tgz (linux) ,extract and install it.
9) Copy(with mass storage mode on) the FILES (and the one zip file that was downloaded from mediafire--> the other two things copied accross should not be zip files but instead individual files that have been extracted. ) to your SD card (not in any folder or anything, just in the main folder that opens when you open your SD card on your computer).
10) Turn off mass storage mode on your mobile (pull down the notification bar and click where it says USB Connected and make sure it is off).
11) Next go Settings>Applications>Development>Tick USB debugging (make sure it is on).
12) Next, on your computer press windows key + r, type cmd. Then type
cd <follwed by the address of the platform-tools folder in the sdk folder>
For example mine was (remember all lowercase):
c:\downloads\android-sdk_r08-windows\android-sdk-windows\platform-tools
so i typed :
cd c:\downloads\android-sdk_r08-windows\android-sdk-windows\platform-tools
13) A whole lot of writing should come up and stuff in the box you typing in (cmd prompt). Next type adb shell and then the word su. Your phone should ask if it should allow permission for super user, select allow or grant access or whatever it says on your phone.
14) Making progress. Next copy the following lines and go back into cmd prompt and right click in it and select paste. Do one line at a time into cmd prompt.
15)
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
[B][U](if it shouts at you here saying not found or something,ignore it)[/U][/B]
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
reboot recovery
Wait a bit and your mobile/phone will turn off, hold in the down volume key and the home key. Keep them held in for a bit when the LG logo comes up.
16) You may back up if you want at this point by going to backup/restore (scroll using volume key and select it using the key on the very left of your phone at the bottom in the front). Choose nandroid backup and let it do its business).
17) Next get back to the mainscreen and select flash zip from sdcard. Select signed_kernal.zip and choose to let it flash. Let it do its business, go to the mainscreen, click reboot system now and you done. Your phone should restart happily with a much less cpu intensive touch screen!
hope this guide helps someone who had the same troubles as me.
Feel free to inform me of anything I may of left out
good work but all the commands can be entered using terminal emulator on phone itself..
thanks
I would much rather just use my pc to type the commands cause I can copy paste them nicely and I trust my pc more
ccdreadcc said:
good work but all the commands can be entered using terminal emulator on phone itself..
Click to expand...
Click to collapse
Best solution is Terminal Emulator + Chrome to phone.Very easy!
rosuvladut said:
Best solution is Terminal Emulator + Chrome to phone.Very easy!
Click to expand...
Click to collapse
If someone types that out I'll add it in (from getting the addon to accessing the terminal).
eichos said:
If someone types that out I'll add it in (from getting the addon to accessing the terminal).
Click to expand...
Click to collapse
Well,from step 8 using Terminal Emulator and Chrome to phone.
8)Download & install:
Google Chrome to phone(PC Google Chrome extension)
Google Chrome to phone(Phone app)
Terminal Emulator (Phone app)
9)Synchronize your Google account in Chrome to Phone(browser extension and phone app) and make a test by sending something to your phone(link,text).Make sure it's working.
10)After that open Terminal Emulator and type "su"(without quotes) and click yes when it's asking you for Superuser permission."#" will appear.
11)From the commands list below copy every line (except red one) one by one and send it to phone.On phone paste all commands one by one,as you send them from Chrome, in Terminal Emulator.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
[COLOR="Red"][U](if it shouts at you here saying not found or something,ignore it)[/U][/COLOR]
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
reboot recovery
12)Wait a bit and your mobile/phone will turn off, hold in the down volume key and the home key. Keep them held in for a bit when the LG logo comes up.
Skip to step 16!
You can update first post if you like it!
Nice...
What about WifiKeyboard? With this tool you can write on phone with keyboard on your PC. Also can be used for SMSs, emails, and so on.
even better and more easy to use copy/paste for emulator.
It works
Thank u for the tutorial. It really worked fine, using the wireless keyboard. 10x for the help and effort u put in this.
thanks for this tutorial.. it helped me a lot..
Actually I found easier with the sdk and windows dos terminal, but whatever ^^, this is a great guide, should have seen before
So are you sure this doesn't work in 2.2.1?
hey i was just wondering... since lg will be releasing gingerbread for the optimus one(p500), is there a way to be able to do this in the future with this setup? or have we given up all future updates from lg or otherwise for this custom kernel??
also i just got an error message when i copied in the first part of the terminal part. I comes up "cannot create /system/bin/flash_image: read-only file system"
Need help!!!
Edit: i found somewhere you had to type in the "mount" line before it all... and it seemed to have worked, hope i didn't break something :s
Edit 2: now i've run into another problem as your instructions seem to skip steps and information towards the end. this line in particaular:
17) Next get back to the mainscreen and select flash zip from sdcard. Select signed_kernal.zip and choose to let it flash. Let it do its business, go to the mainscreen, click reboot system now and you done. Your phone should restart happily with a much less cpu intensive touch screen!
Select flash zip? There is no flash zip anywhere mentioned besides here. could you please clarify or could anyone tell me what he means as im stuck on this part
cyanide911 said:
So are you sure this doesn't work in 2.2.1?
Click to expand...
Click to collapse
You can't root AFAIK on 2.2.1.
@hatethat:
is SU on?
hey sry i edited that post a number of times as not to spam posts... but yeah i got past all that stuff and am now stuck on step 17... i dont know where flash zip came from?
Edit: i went into the recovery mode adn it says "flash zip" there so i tried that and it worked fine ty anyway
HateThat said:
hey sry i edited that post a number of times as not to spam posts... but yeah i got past all that stuff and am now stuck on step 17... i dont know where flash zip came from?
Edit: i went into the recovery mode adn it says "flash zip" there so i tried that and it worked fine ty anyway
Click to expand...
Click to collapse
U need to download signed-kernel.zip and flash that
eichos said:
You can't root AFAIK on 2.2.1.
@hatethat:
is SU on?
Click to expand...
Click to collapse
Ah damn
Sent from my LG-P500 using XDA App
thank you good guide
I can`t find the Google Chrome to Phone (phone app) in the market, can anyone help me with it?
And of course in the pc market, my network provider won`t let me install it.
L.E.: finally i`ve found the app. Flashed the kernel, works like a charm. Thank you.
Hey guys,
I know A LOT of the new users want to use mods and theme things now that they are newly rooted on ND7 4.4.2. So I was trying to think of a way to make it easier to do so, one being deodex. For us who are unlocked, we develop and theme mostly on deodex system's. So lets get to the guide.. This will make all your apps in system/app and system/priv-app Deodex, therefore you can theme them and head over to my Mods Thread and take advantage of them!
Prerequisites:
PC
Android SDK and/or ADB
USB cable
Patience
First make sure you have USB Debugging enabled on your device (Go into About Device in Settings, Find Build Number, Hit it 8 times until you unlock developer settings. Go into Developer Settings..Scroll down.. Enable USB debugging) Let make sure ADB is setup correctly and working.. Open a cmd prompt where you installed ADB (If SDK it should be C:\SDK\platform-tools\) type:
Code:
adb devices
Your return should look something 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"
}
If it does NOT look like this you need to either enable USB debugging, Grant the PC access to the phone or look up some guides on getting ADB started.
So once we know ADB works, lets download the zip I provided with the apps. These are pulled straight from ND7 Stock tar and Deodex by me, there should be no issues. I want you to extract them to your PC. Now lets make some folders on your internal sdcard(Use a root explorer/file explorer):
Folder names:
deodex_app
deodex_priv-app
Once you made the folders go ahead and copy the apps in their correct directory. App goes in deodex_app and Priv-app goes into deodex_priv-app.
When this is finished its time to start the ADB commands..
So we should already have our device connected and adb working with the return device serial number. Lets execute some cmds. After each line hit ENTER:
Code:
adb shell
su ([COLOR="Red"]MAKE SURE YOU GRANT SU PERMISSON!![/COLOR])
stop
mount -o rw,remount /system/ /system/
cp /sdcard/deodex_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/deodex_priv-app/* /system/priv-app/
rm /system/priv-app/*.odex
mount -o ro,remount /system/ /system/
exit
exit
adb reboot
**BE SURE TO PAY ATTENTION TO YOUR COMMANDS...SPELLING AND SPACES ETC..
Once rebooted your device should update all apps..You should be Deodex and ready to do whatever your heart desires!!
Happy Theming! Any ?'s just post and ask! Want to learn how to Theme??? Head to this THREAD!!
PS: You want frameworks as well? Do this:
Download this zip, extract it, make a folder on your sdcard: deodex_frame. Copy unzipped contents to that new folder. Start ADB:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/deodex_frame/* /system/framework/
rm /system/app/*.odex
mount -o ro,remount /system/ /system/
exit
exit
adb reboot
Should update and be good to go! Enjoy!
@KennyG123 would mind making this sticky?? THANKS!
awesome, I've been using wanam xposed and love the outcome however there are still a few system ui errors. gonna try this and see what I get.
thanks
Sent from my SCH-I605 using Tapatalk
lacoursiere18 said:
Hey guys,
I know A LOT of the new users want to use mods and theme things now that they are newly rooted on ND7 4.4.2. So I was trying to think of a way to make it easier to do so, one being deodex. For us who are unlocked, we develop and theme mostly on deodex system's. So lets get to the guide.. This will make all your apps in system/app and system/priv-app Deodex, therefore you can theme them and head over to my Mods Thread and take advantage of them!
Prerequisites:
PC
Android SDK and/or ADB
USB cable
Patience
First make sure you have USB Debugging enabled on your device (Go into About Device in Settings, Find Build Number, Hit it 8 times until you unlock developer settings. Go into Developer Settings..Scroll down.. Enable USB debugging) Let make sure ADB is setup correctly and working.. Open a cmd prompt where you installed ADB (If SDK it should be C:\SDK\platform-tools\) type:
Code:
adb devices
Your return should look something like this:
View attachment 2945524
If it does NOT look like this you need to either enable USB debugging, Grant the PC access to the phone or look up some guides on getting ADB started.
So once we know ADB works, lets download the zip I provided with the apps. These are pulled straight from ND7 Stock tar and Deodex by me, there should be no issues. I want you to extract them to your PC. Now lets make some folders on your internal sdcard(Use a root explorer/file explorer):
Folder names:
deodex_app
deodex_priv-app
Once you made the folders go ahead and copy the apps in their correct directory. App goes in deodex_app and Priv-app goes into deodex_priv-app.
When this is finished its time to start the ADB commands..
So we should already have our device connected and adb working with the return device serial number. Lets execute some cmds. After each line hit ENTER:
Code:
adb shell
su ([COLOR="Red"]MAKE SURE YOU GRANT SU PERMISSON!![/COLOR])
stop
mount -o rw,remount /system/ /system/
cp /sdcard/deodex_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/deodex_priv-app/* /system/priv-app/
rm /system/priv-app/*.odex
mount -o ro,remount /system/ /system/
exit
exit
adb reboot
**BE SURE TO PAY ATTENTION TO YOUR COMMANDS...SPELLING AND SPACES ETC..
Once rebooted your device should update all apps..You should be Deodex and ready to do whatever your heart desires!!
Happy Theming! Any ?'s just post and ask! Want to learn how to Theme??? Head to this THREAD!!
PS: You want frameworks as well? Do this:
Download this zip, extract it, make a folder on your sdcard: deodex_frame. Copy unzipped contents to that new folder. Start ADB:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/deodex_frame/* /system/framework/
rm /system/app/*.odex
mount -o ro,remount /system/ /system/
exit
exit
adb reboot
Should update and be good to go! Enjoy!
@KennyG123 would mind making this sticky?? THANKS!
Click to expand...
Click to collapse
So do you copy the the contents of deodex_app/app to deodex_app on the phone or do you copy the app folder itself to the phone
sergeptx said:
So do you copy the the contents of deodex_app/app to deodex_app on the phone or do you copy the app folder itself to the phone
Click to expand...
Click to collapse
Unzip it and there should be a /app and /priv-app folder.. Make a folders called deodex_app and deodex_priv-app on your sdcard.. open those folders and copy the contents(the actual apps) inside of those folders
lacoursiere18 said:
Unzip it and there should be a /app and /priv-app folder.. Make a folders called deodex_app and deodex_priv-app on your sdcard.. open those folders and copy the contents(the actual apps) inside of those folders
Click to expand...
Click to collapse
Thanks.... gonna try it
Could you just copy and paste using a root explorer as well
Sent from my SCH-I605 using XDA Free mobile app
dillonorden said:
Could you just copy and paste using a root explorer as well
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Nope..
Don't know what I did wrong but I'm stuck at the verizon boot logo...
Only thing I did different was created folders on internal storage on pc instead of using root browser on phone.
Nice write up lacoursiere18, worked like a charm. :good: thanks for the deodexed files
got the apps and priv-apps deodexed fine but, when I get to the part for framework the copy goes fine but when I do rm /system/app/*.odex it fails and says no .odex found. Should it be rm /system/framework/*.odex ??? Seems to have worked, don't see any odex files. Thanks for the write up!