Database Develop

[MOD] Fully deodexed/zipaligned App and Framework

You will have to manually install it via adb push or adb shell.
Below is the link for a package that contains /system/app and /system/framework fully deodexed and zipaligned (not signed). It's the Stock version, I didn't remove any apk or framework.
Use at your own risk!
Backup your /system before upgrade!
I did notice speed increase and better memory utilization.
http://www.usk.bz/android/system-deodexed.bz2
EDIT: Here is a quick howto do it. Do some research, speacially on the "Recovering from a software brick" thread posted by Designgears. You may need it, in ase you don't execute this right.
Warning: Do those steps carefully! If you get any error as a return for a command you did, stop immediately and post here with the error to make sure it's safe to continue or what you should do before continue.
1. Download the file system-deodexed.bz2 (it's a tar.bz2)
2. uncompress it with tar zxf system-deodexed.bz2. You will get a folder called "system" with two other folders inside(app and framework).
3. First push it to the device to a safe location (your internal sdcard):
Code:
adb push system /mnt/sdcard/deodexed/system
4. Now open an adb shell and backup the folders you will mess with to the sd card, in case you need to recovery them
Code:
adb shell
$ su
# mkdir /mnt/sdcard/original_system
# mkdir /mnt/sdcard/original_system/app
# mkdir /mnt/sdcard/original_system/framework
# cp /system/app/* /mnt/sdcard/original_system/app
# cp /system/framework/* /mnt/sdcard/original_system/framework
5. Now the tricky part, you will get force closes on the device screen, because you will do this with the system running, don't worry for now. It should clear up once you are done. (Thx for the tip!) Lets update the system with the deodexed files. While still on the adb sheel as root, from the previous step, continue with these commands:
Code:
# stop
# mount -o rw,remount /dev/block/mmcblk0p12 /system
# cp /mnt/sdcard/deodexed/system/framework/* /system/framework
# cp /mnt/sdcard/deodexed/system/app/* /system/app
# rm /system/framework/*.odex
# rm /system/app/*.odex
6. Once you are done, exit the adb shell and do a reboot:
Code:
adb reboot
It should take a little longer to reboot, its normal for the first time. Then you should have normal boot speeds.
I recommend do this on a clear system, or that you do a factory reset once you reboot. The reason for that is that sometimes you get some data corruption during the force closes (corruption on the configuration files, not user data). But a factory reset fixes that.
If all go well, you have a deodexed system and are ready to use some Mods!
Have fun!
[ Known issues ]
- None! Please report if you notice anything!

http://forum.xda-developers.com/showthread.php?t=961382
Hey, here is a fully working on I did over the weekend.

Thanks! I didn't see it before. Will still compare with mine to see which package I messed up.

uskr said:
Thanks! I didn't see it before. Will still compare with mine to see which package I messed up.
Click to expand...
Click to collapse
usually packages with sound files get messed up for whatever reason when deodexing

designgears said:
usually packages with sound files get messed up for whatever reason when deodexing
Click to expand...
Click to collapse
Are you still planning on posting your mod version with steps? I am asking because I want to take look before making I own edits if necessary. I figured you may have it the way I want and it would less work for me either way.

designgears said:
usually packages with sound files get messed up for whatever reason when deodexing
Click to expand...
Click to collapse
Do you use an automated script to deodex them? or manually do one by one? The BOOTCLASSPATH dependencies sometimes give me some headache.
Also, do you mind to share which zip compression level do you use to repackage them?
Thank again!

designgears said:
usually packages with sound files get messed up for whatever reason when deodexing
Click to expand...
Click to collapse
Actually, I just tried yours and it has the same problem. Can you try to add the "Social Status" motorola widget to your MotoBlur and tap it to Setup your account and see if it starts something?
Mine doesnt start the Setup intent and I can see a Java exception on adb logcat.

uskr said:
Actually, I just tried yours and it has the same problem. Can you try to add the "Social Status" motorola widget to your MotoBlur and tap it to Setup your account and see if it starts something?
Mine doesnt start the Setup intent and I can see a Java exception on adb logcat.
Click to expand...
Click to collapse
Nevermind. Neither were bugged. I installed the deodexed without a data wipe and something got corrupted on the /data (some configuration file or something). I did a factory data reset and everything is working!
Not to play with changing some apks!

Hi guys,
I don't have an Atrix for now, so maybe it's just a dumb question. Sorry if it is.
With the Defy, if you push files and your phone won't reboot because you messed with something, you're screwed, as we don't have a true custom recovery. (you need a booting system to be able to get to the bootstap custom recovery, which you can't get into if your system is messed and the phone doesn't boot).
So when we are in that case with a Defy, our only option is to reflash a Motorola signed sbf file using RSD lite, root again, install again bootstrap recovery,... and try again ;-).
I guess it has to be the same with the Atrix (as the bootloader is locked as in the Defy)
So my question is:
- Are there already Atrix sbf files out there to recover a soft-bricked Atrix?
- If not, how do you recover it if you messed with the system files and the Atrix won't boot into a working system (of at least a state where you can get root shell though adb).

adlx.xda said:
So my question is:
- Are there already Atrix sbf files out there to recover a soft-bricked Atrix?
- If not, how do you recover it if you messed with the system files and the Atrix won't boot into a working system (of at least a state where you can get root shell though adb).
Click to expand...
Click to collapse
If you only messed only with /system/app or /system/framework folders/files, designgear posted how to recovery those files using the stock, that you can also download a tar with all the /system files from this forum.

Updated the post with a short howto.
If you get a software brick, search the forum for a post from designgears about how to recovery from a software brick.

As per the link below - I type "stop" once in the adb shell and it allowed me to transfer everything over without corrupting everything.
http://forum.androidcentral.com/mot...cks/30539-how-manually-deodex-your-phone.html

slhawkins said:
As per the link below - I type "stop" once in the adb shell and it allowed me to transfer everything over without corrupting everything.
http://forum.androidcentral.com/mot...cks/30539-how-manually-deodex-your-phone.html
Click to expand...
Click to collapse
Thx. Added to the howto!

uskr said:
Thx. Added to the howto!
Click to expand...
Click to collapse
Add the following to your instructions otherwise you will get an error message
You need the below line before the others
# mkdir /mnt/sdcard/original_system
The below are in your original instructions but the above is needed prior to the below
# mkdir /mnt/sdcard/original_system/app
# mkdir /mnt/sdcard/original_system/framework

lpsi2000 said:
Add the following to your instructions otherwise you will get an error message
You need the below line before the others
# mkdir /mnt/sdcard/original_system
The below are in your original instructions but the above is needed prior to the below
# mkdir /mnt/sdcard/original_system/app
# mkdir /mnt/sdcard/original_system/framework
Click to expand...
Click to collapse
Thanks! Updated.

I want to try this but i dont have linux to uncompress the file. possible to recompress it in something like zip or rar format?

NguyenHuu said:
I want to try this but i dont have linux to uncompress the file. possible to recompress it in something like zip or rar format?
Click to expand...
Click to collapse
Extract it to the file with no extension.
Open winrar.
Drag drop this file into that (u'll find the zipped up contents)
Drag drop these to ur desktop or anywhere u want them

NguyenHuu said:
I want to try this but i dont have linux to uncompress the file. possible to recompress it in something like zip or rar format?
Click to expand...
Click to collapse
push the file to sdcard of the device and using tar there after all it is also a linux system

diablo009 said:
Extract it to the file with no extension.
Open winrar.
Drag drop this file into that (u'll find the zipped up contents)
Drag drop these to ur desktop or anywhere u want them
Click to expand...
Click to collapse
great! thanks.

uskr said:
I recommend do this on a clear system, or that you do a factory reset once you reboot. The reason for that is that sometimes you get some data corruption during the force closes (corruption on the configuration files, not user data). But a factory reset fixes that.
Click to expand...
Click to collapse
Hi all,
I just did deodexed my atrix. Thanks much for the wonderful work~!!!
Mine has handful of apps installed prior to deodex. I was wondering what would be implication for not having clean system after deodex.

[HOW TO] Rooting the LT25i without unlocking the bootloader (4.0.4)

Rooting the Xperia V: How-To.
(XDA member datagubben requested that I post this here, as per http://forum.xda-developers.com/showpost.php?p=36753824&postcount=19)
Mirrors for the files provided are welcome.
This root method is courtesy of Xperia-Freaks.org, originally developed for the Xperia AX, translated and adapted by me for the LT25i.
Supported firmware: 9.0.1.D.0.10, probably also 9.0.D.0.484.
Reportedly does not work with 9.1.A.0.489.
You will need: TRIMMED-LT25i-SOL21_9.0.F.0.195.ftf (direct link: TRIMMED-LT25i-SOL21_9.0.F.0.195.ftf) or the original LT25i-SOL21_9.0.F.0.195.ftf (this FTF has its loader.sin replaced with LT25i's loader.sin; the trimmed version lacks unneeded files like baseband etc. and as such removes unneeded wipe/exclude options, leaving only the three files we actually need) and an LT25i FTF of your choice; the rootkit (this one is "translated" and edited for convenience; do NOT use regular GX/SX rootkits blindly as they require modification).
Make a backup using the stock Backup and Restore app in case something goes wrong so you can perform a factory reset.
Once rooted, you can safely restore from that backup.
1. Power the phone up in Flashmode (hold Volume down; connect USB). Using Flashtool, flash TRIMMED-LT25i-SOL21_9.0.F.0.195.ftf (or the untrimmed version if you like fiddling with excess checkboxes) using:
kernel.sin
loader.sin
system.sin
(Remember to uncheck the wipe options!)
2. Unplug USB. Turn the phone on. Enable USB debugging if it wasn't enabled previously. Connect the phone via USB again.
3. Unpack the Rootkit and start it (run install.bat). Confirm restore of the backup as requested, and press any key in the cmd window. Press any key again; the device will reboot (twice).
4. Run adb shell. To do it, you can open the rootkit folder in Windows Explorer, and shift-Right Click the "files" folder inside it. Choose "Open command window here". Type "adb shell" in that window.
If you're presented with a prompt that ends with "$", type "su".
The prompt should end with "#" now.
Type "echo ro.kernel.qemu=1 > /data/local.prop" and check if the file was created successfully by typing "ls -l /data/local.prop": below you will find an example of what the output looks like.
Code:
C:\Software\Rootkit\files\> adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo ro.kernel.qemu=1 > /data/local.prop
echo ro.kernel.qemu=1 > /data/local.prop
[email protected]:/ # ls -l /data/local.prop
ls -l /data/local.prop
-rw-r--r-- system system 17 2013-01-15 17:29 local.prop
[email protected]:/ #
5. Turn the phone off, and connect it in Flashmode again. Using Flashtool, flash your firmware of choice with:
loader.sin
system.sin
(Remember to uncheck the wipe options!)
6. Turn the phone on. Open a command prompt into the files subfolder of the rootkit folder, like in step 4, or return to that window if you haven't closed it.
Type "adb shell". If you get a $ prompt, try "su" to get to "#". Once in adb, type "/data/local/tmp/step2.sh", then "reboot". The phone will reboot.
When it boots back, run adb shell again, and type "/data/local/tmp/step3.sh". You'll witness another reboot or maybe two. You should be rooted now.
Code:
C:\Software\Rootkit\files\> adb shell
[email protected]:/ # /data/local/tmp/step2.sh
/data/local/tmp/step2.sh
0+1 records in
0+1 records out
57 bytes transferred in 0.001 secs (57000 bytes/sec)
[email protected]:/ # reboot
C:\Software\Rootkit\files\> adb shell
[email protected]:/ # data/local/tmp/step3.sh
data/local/tmp/step3.sh
43+1 records in
43+1 records out
22364 bytes transferred in 0.002 secs (11182000 bytes/sec)
1647+1 records in
1647+1 records out
843503 bytes transferred in 0.123 secs (6857747 bytes/sec)
2119+1 records in
2119+1 records out
1085140 bytes transferred in 0.089 secs (12192584 bytes/sec)
7. Turn the phone off, and connect it in Flashmode again. Using Flashtool, flash your firmware of choice with:
kernel.sin
loader.sin
(Remember to uncheck the wipe options!)
Do NOT skip this step: you need the LT25i kernel on your LT25i system!
8. Let's finish.
We will need adb shell once again. This time, you will need to type a few lines as follows:
Obtain root:
su
Remount /system:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
Remove /data/local.prop since it's a security hole; this is important and is normally done by the rootkit's step 3, but we needed to save the file to get to keep root access on our LT25i firmware:
rm /data/local.prop
And finally reboot:
reboot
Code:
G:\Android\LT25i\rootkitGXSX_v3\files>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
[email protected]:/ # rm /data/local.prop
rm /data/local.prop
[email protected]:/ # reboot
reboot
Done. You now have busybox, Superuser and su on your stock LT25i firmware.
Remember to clean up those pesky au apps.

Will link to the all in one. Many thanks

Good job translating!
Sent from your backyard...
Slender watches what you do...

I did some n00b experiments:
First I flash kernel.sin-, system.sin and loader.sin from above VL-firmware(Japan), then Bin4ary for root (OK) and back to V-kernel with system.sin again, but I lost root ofcourse :crying:
anyway, the first post is working but I get reboots when deleting something from system/apps/. Any fix?

datagubben said:
First I flash kernel.sin-, system.sin and loader.sin from above VL-firmware(Japan), then Bin4ary for root (OK) and back to V-kernel with system.sin again, but I lost root ofcourse
anyway, the first post is working but I get reboots when deleting something from system/apps/. Any fix?
Click to expand...
Click to collapse
Using the Bin4ry approach should be possible since as far as I know it's the exact same backup/restore timing exploit, you probably need to recreate /data/local.prop though before flashing the V's system.sin. Or do you mean reducing the number of flashing operations to 2? That won't work, we need to regain root on V's system to get it to enable adb root shell with the V's kernel.
If you delete something from /system/app and the phone starts rebooting, it means you just deleted a part of the Timescape framework, I'd presume?

This method will clean up my installed app?

Dude i'm step 6 but I keep getting this prompt.
C:\Users\user\Documents\Development\Xperia\Xperia V\rootkit-sony\files>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
edit: now do i panic?

Aaron_035, this means you did not obtain root during previous steps.
Did you verify that /data/local.prop was successfully created during step 4?

Gasai Yuno said:
Aaron_035, this means you did not obtain root during previous steps.
Did you verify that /data/local.prop was successfully created during step 4?
Click to expand...
Click to collapse
Found my mistake, I'm going to try again Fifth time!
Edit: Done! Love you dude.

All I want is just to root the phone. Why is this flash some japanese firmware to my phone!
Yes I am a n00b.

sunny7day said:
All I want is just to root the phone. Why is this flash some japanese firmware to my phone!
Yes I am a n00b.
Click to expand...
Click to collapse
Because "some japanese" firmware is with exploit before it was fixed by Sony

where can I download official hong kong firmware? I am stuck on step 5.

sunny7day said:
where can I download official hong kong firmware? I am stuck on step 5.
Click to expand...
Click to collapse
I haven't seen HK firmware beeing uploaded here on XDA yet, but you can make yourself with PPC + flashtool (its not difficult, look in the forum how to do).

I just got the hk firmware and finished all the steps in the first post, now i am rooted.
Yes it is rooted but it left alot of unwanted au japanese sofware in my phone.
It should be noted in the first line in the first post of this thread.
But thank you anyways.
So, I have to wipe and re-flash my stock HK firmware.
Are there any other way to root my Xperia V without flashing other firmware?

If you did everything according to the howto I posted, you would be running your stock HK firmware, rooted.
All those au apps left after flashing back the stock LT25i firmware can be easily uninstalled. They're in /data/app, not in /system/app.
And, quoting the last line from the howto I posted,
Remember to clean up those pesky au apps.
Click to expand...
Click to collapse
sunny7day said:
Are there any other way to root my Xperia V without flashing other firmware?
Click to expand...
Click to collapse
You're welcome to find one and share it with us. Believe me, I'd rather do something simple than bother with all this reflashing and app removal.
Also, if you really want it simple, unlock your bootloader already.

Gasai Yuno said:
If you did everything according to the howto I posted, you would be running your stock HK firmware, rooted.
All those au apps left after flashing back the stock LT25i firmware can be easily uninstalled. They're in /data/app, not in /system/app.
And, quoting the last line from the howto I posted,
You're welcome to find one and share it with us. Believe me, I'd rather do something simple than bother with all this reflashing and app removal.
Also, if you really want it simple, unlock your bootloader already.
Click to expand...
Click to collapse
First of all, thanks for doing the tutorial for us with locked bootloader. :good: :highfive:
a) But you need a ftf-file in order to flash back the original kernel and HK is not available as a download here on XDA yet (If you don't do it yourself).
b) Not everybody has a Ph.d in translation and "pesky" is rarely used by less educated, at least in my case.
c) I have an app_log.sin that bothers me, when trying to flash back the LT25i kernel and system, does it matter?
d) Will this work when we get Jelly Bean?
Ps. Watashi wa Tokyo no Yukigaya-Otsuka de sunde ima****a. Boku no okusan wa nihonjin de****a. Demo owari desu :crying:
Ps. ps. The language filter on XDA removed S and H and I and T. WTF!

datagubben said:
First of all, thanks for doing the tutorial for us with locked bootloader. :good: :highfive:
a) But you need a ftf-file in order to flash back the original kernel and HK is not available as a download here on XDA yet (If you don't do it yourself).
Click to expand...
Click to collapse
And if you do please PLEASE share it as we could do with it here
b) Not everybody has a Ph.d in translation and "pesky" is rarely used by less educated, at least in my case.
Click to expand...
Click to collapse
not a scooby doo fan then?
c) I have an app_log.sin that bothers me, when trying to flash back the LT25i kernel and system, does it matter?
d) Will this work when we get Jelly Bean?
Click to expand...
Click to collapse
There is no way to know untill it lands on our devices, Sony can(and do) monitor what we do on this forum and, allthough they are quite dev friendly, do find way to fix the loopholes we exploit to get root access. They want us only to get that via an official unlocking from their site. You cant blame them for that, they are a big company and have lots of ways of losing contracts if they cant secure their system.
But you can be your bottom dollar tha if they close that exploit, we will find another way
[/quote]
Ps. Watashi wa Tokyo no Yukigaya-Otsuka de sunde ima****a. Boku no okusan wa nihonjin de****a. Demo owari desu :crying:
Click to expand...
Click to collapse
I know this is a personal message but the rules state this is an english speaking forum. You can post in other languages but an english translation is always required. (I know you dont need this next bit but..) Please use google translate if you have trouble with getting an english translation
Ps. ps. The language filter on XDA removed S and H and I and T. WTF!
Click to expand...
Click to collapse
lol!

I can only post the ftf.firmware from operators in Nordic/Sweden:
http://www.swedroid.se/forum/showthread.php?t=86895
What about "app_log.sin", does it matter? Cause it is flashed together with the Kernel.sin and system.sin
I don't watch Scooby Doo.
I speak japanese and I said "I lived in Tokyo but not now".
S,h,i,t

datagubben said:
I can only post the ftf.firmware from operators in Nordic/Sweden:
http://www.swedroid.se/forum/showthread.php?t=86895
Click to expand...
Click to collapse
I meant the other guy, in response to your post about making his own ftf, if he does, he should post it and share
What about "app_log.sin", does it matter? Cause it is flashed together with the Kernel.sin and system.sin
Click to expand...
Click to collapse
not sure
I don't watch Scooby Doo.
Click to expand...
Click to collapse
google it and watch, a clasic kids cartoon with a classic catchphrase of "I would have got clean away with it, if it wasnt for you PESKY kids!
I speak japanese and I said "I lived in Tokyo but not now".
Click to expand...
Click to collapse
thanks
S,h,i,t
Click to expand...
Click to collapse
I gathered that

datagubben said:
c) I have an app_log.sin that bothers me, when trying to flash back the LT25i kernel and system, does it matter?
d) Will this work when we get Jelly Bean?
Click to expand...
Click to collapse
c) Make a copy of your stock FTF file. Open the copy in Total Commander or 7-Zip. Delete everything except the manifest, loader.sin, kernel.sin and system.sin. No more app_log.sin appearing in Flashtool, yay!
d) Depends on two factors.
First, if the 4.1 update will replace the keys used to sign .sin files, removing compatibility with older firmware, this approach will be unavailable. This is what Motorola did with the DROID 2/X/2 GLOBAL.
Second, provided they don't replace the bootloader, and we can still flash back to 4.0: whether we will be able to retain root during firmware update (via OTA RootKeeper or whatever else exists).
As for the language filter, use Kunrei romaji (you know, the system where you use “si” instead of “shi” for し and “ti” instead of “chi” for ち) to work around it.

[Solved] Need help fixing CWM for locked bootloaders

OK, so here's the problem. We have a CWM for locked bootloaders but as of .489 JB firmware you can't get to it by pushing vol+ on boot. This is somehow kernel related because it works again if you flash a .223 kernel but then the phone doesn't boot after rebooting from CWM (which is sort of expected). I've found a workaround but it's ugly and tedious to do every time you want to go to recovery.
The script I made to automate this process doesn't really work and I don't have much know-how in this department so would really appreciate some help on improving the script or better yet, tackle the problem at the root.
Now I'll go into some more detailed description of the problem and the things I've already tried.
The way the CWM for locked bootloaders works is by replacing /system/bin/chargemon with a script that looks for the keypress and subsequently starts the recovery boot process. (I've attached the whole script, just remove .txt)
Code:
${CAT} /dev/input/event0 > ${WORKDIR}/keycheck &
For reasons yet unknown to me the keypress is not logged to the keycheck file, the file is empty, whereas on .223 you see symbols recorded to this file. Thinking no key has been pressed, the script continues normal boot.
My workaround was to comment out lines 108 & 178, the keycheck condition, forcing it to go to recovery. The downside to that is that the phone will keep rebooting to recovery unless you flash the CWM zip again before leaving recovery, or recovering the original chargemon with adb shell.
I made a script to copy chargemon to /system/bin and setting the permissions, then rebooting,
Code:
#!/system/bin/sh
# script to boot to recovery
# on Xperia T 9.1.A.0.489
# by TiMiN8R
mount -o remount,rw /system
mv /system/bin/chargemon /sytem/bin/chargemon.bak
cp chargemon /system/bin
chown 0.2000 /system/bin/chargemon
chmod 0755 /system/bin/chargemon
reboot
reboot
but I keep getting "failed on chargemon: no such file or directory". Of course the file is there, this is some stupid permissions issue, the shell script not having proper rights to manipulate the file or something, but my knowledge of this is too limited. I've googled and tried stuff like changing permissions and ownership of the script but to no avail. Also tried running the sript with Gscript and SManager but with same results.
So please, anyone with some shell scripting experience, shine your light on this. It'd be much appreciated by me and a lot of other people!

TiMiN8R said:
OK, so here's the problem. We have a CWM for locked bootloaders but as of .489 JB firmware you can't get to it by pushing vol+ on boot. This is somehow kernel related because it works again if you flash a .223 kernel but then the phone doesn't boot after rebooting from CWM (which is sort of expected). I've found a workaround but it's ugly and tedious to do every time you want to go to recovery.
The script I made to automate this process doesn't really work and I don't have much know-how in this department so would really appreciate some help on improving the script or better yet, tackle the problem at the root.
Now I'll go into some more detailed description of the problem and the things I've already tried.
The way the CWM for locked bootloaders works is by replacing /system/bin/chargemon with a script that looks for the keypress and subsequently starts the recovery boot process. (I've attached the whole script, just remove .txt)
Code:
${CAT} /dev/input/event0 > ${WORKDIR}/keycheck &
For reasons yet unknown to me the keypress is not logged to the keycheck file, the file is empty, whereas on .223 you see symbols recorded to this file. Thinking no key has been pressed, the script continues normal boot.
My workaround was to comment out lines 108 & 178, the keycheck condition, forcing it to go to recovery. The downside to that is that the phone will keep rebooting to recovery unless you flash the CWM zip again before leaving recovery, or recovering the original chargemon with adb shell.
I made a script to copy chargemon to /system/bin and setting the permissions, then rebooting,
Code:
#!/system/bin/sh
# script to boot to recovery
# on Xperia T 9.1.A.0.489
# by TiMiN8R
mount -o remount,rw /system
mv /system/bin/chargemon /sytem/bin/chargemon.bak
cp chargemon /system/bin
chown 0.2000 /system/bin/chargemon
chmod 0755 /system/bin/chargemon
reboot
reboot
but I keep getting "failed on chargemon: no such file or directory". Of course the file is there, this is some stupid permissions issue, the shell script not having proper rights to manipulate the file or something, but my knowledge of this is too limited. I've googled and tried stuff like changing permissions and ownership of the script but to no avail. Also tried running the sript with Gscript and SManager but with same results.
So please, anyone with some shell scripting experience, shine your light on this. It'd be much appreciated by me and a lot of other people!
Click to expand...
Click to collapse
change your script like this and try that
Code:
#!/system/bin/sh
# script to boot to recovery
# on Xperia T 9.1.A.0.489
# by TiMiN8R & Crazymister
su
mount -o remount,rw /system
cd /system/bin
mv chargemon chargemon.bak
cd /
cp chargemon /system/bin/
cd /system/bin
chown 0.2000 /system/bin/chargemon
chmod 0755 /system/bin/chargemon
reboot
it's a little dirty scripting, but it seems to work in adb at least. so should work from terminal emulater also is you save it as yourfilename.sh

Thanks but doesn't work,. Gives me same errors I had before. But I've devised a better method. I'll post it tonight when I get home.

Re: [Q] Need help fixing CWM for locked bootloaders
Maybe event7 now?

peetr_ said:
Maybe event7 now?
Click to expand...
Click to collapse
I'll give it a shot. Care to explain?

Re: [Q] Need help fixing CWM for locked bootloaders
Try it in terminal.
Input changed.

Re: [Q] Need help fixing CWM for locked bootloaders
Yes! Thank you so much. Glad it is so easy. Changed event0 to event7 in the chargemon script and successfully got into CWM.
Sent from my LT30p using xda app-developers app

TiMiN8R said:
Yes! Thank you so much. Glad it is so easy. Changed event0 to event7 in the chargemon script and successfully got into CWM.
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
so if i understand correctly, if you change evento > event 7 volume up/down works?

Re: [Q] Need help fixing CWM for locked bootloaders
Yup, changing to event7 means we can use vol up again to get to recovery.
Sent from my LT30p using xda app-developers app

Re: [Q] Need help fixing CWM for locked bootloaders
I am glad, it helped.

[Q] XXLSA Android 4.1.2 and Low Battery: Stuck at Boot. Data Recovery?

Recently my phone had a low battery status. It booted up but apparently lost power somewhere when restoring the Apex Launcher screens.
Since then it just shows the Samsung logo and gets rather hot. I left it in this state for over an hour with no progress.
Boot and recovery mode work fine. Unfortunately adb is not in root by default, as such pulling is useless as nothing is mounted.
issuing
Code:
adb root
will result in:
Code:
adbd cannot run as root in production builds
I can issue for instance:
Code:
adb shell
su
e2fsck -pv /dev/block/mmcblk0p10
mount -t ext4 /dev/block/mmcblk0p10 /data
Unfortunately I cannot tar gzip and copy to the externalSD nor pull the data folder.
Starting dalvikvm fails:
Code:
127|[email protected]:/ # dalvikvm
dalvikvm
Dalvik VM init failed (check log file)
What options do I have to backup my data? Please provide me with concrete ideas and steps.
Many people are having similar problems, and I sincerely thank you if you can help me figure out a way to backup my data at this stage.

After reading the first two sentences and the title:
Buy a new battery.
Install something else, you are still on an early leak and not an official release.

I found a quick solution. All kudos and thanks go out to Philz as well as
TAHER128
Instructions and files are here:
http://www.youtube.com/watch?v=1TinSwsehZ8
After the new recovery mode and kernel is installed, reboot into recovery mode and go to the mount menu in order to select "mount USB storage". Backup everything to your PC.
From hereon out you are safe.
Install busybox if you want. Reflash a stock or custom rom if you want and/or dig your way through logs and fixes within a now powerful bash shell.

blairmiller said:
This problem is difficult to solve by your phone itself. Maybe you need to install some software to help you.
Click to expand...
Click to collapse
This thread is 2 months old

root
The reasons for getting a bootloop on your Android device might be anything. If you wish to know the reason why your Android phone is stuck on the bootloop, you need not type your problem on the Google search box. Just calm yourself for a while and think what you did just before. It could be anything! Here are some major reasons why your Android device is caught in a bootloop.

Can't Get 4G to Work

I've had alot of problems getting this phone to work. I tried 4 different carriers until I figured out I needed to put the SIM in a phone that was already on Verizon in order for it to work in my phone. Now, even though cell service works, I can only get 3G. I did lose my IMEI reverting back to stock, but I fixed that. Is there any solution out there to this?

edit: ok, i had the exact same problem stemming from the same sequence of events, and now i got my lte back. there's no weird process to do it, i just re-flashed the stock rom (without erasing modems) and did what it said in this thread:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
so basically, steps are:
1. through adb, flash stock rom
2. through adb, flash twrp
3. through twrp, flash magisk
4. download busybox and a terminal emulator from the play store
5. install busybox to /system/xbin through the app
6. open the terminal emulator and type these commands:
$ su
# chown -R rfs:rfs /persist/rfs
# chown -R rfs:rfs_shared /persist/hlos_rfs
7. reboot
personally, if i flash another different rom i'll definitely be backing up EVERYTHING beforehand.

xtasquee said:
edit: ok, i had the exact same problem stemming from the same sequence of events, and now i got my lte back. there's no weird process to do it, i just re-flashed the stock rom (without erasing modems) and did what it said in this thread:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
so basically, steps are:
1. through adb, flash stock rom
2. through adb, flash twrp
3. through twrp, flash magisk
4. download busybox and a terminal emulator from the play store
5. install busybox to /system/xbin through the app
6. open the terminal emulator and type these commands:
$ su
# chown -R rfs:rfs /persist/rfs
# chown -R rfs:rfs_shared /persist/hlos_rfs
7. reboot
personally, if i flash another different rom i'll definitely be backing up EVERYTHING beforehand.
Click to expand...
Click to collapse
It worked. Thank you so much!

confirmed after fixing data and flashing msm extended, lte and volte working.
edit: for all it's worth, the guy just posted the fix in guides, so he deserves the thanks. and good timing since it is just figured out this month lol.