[Q] O3D stuck at boot - bad android.policy.jar - Android Q&A, Help & Troubleshooting

My O3D is constantly rebooting right after the boot img because I copied a wrong android.policy.jar in /system/framework/ . The original android.policy.jar is still there, renamed to android.policy.jar1. What is the easiest and simplest way to delete the faulty jar file and rename the original one?
P.S. ADB doesn't work in clockworkmod. Mount usb doesn't do anything.

Related

Kitchen for Samsung M110S

HI I have unzip my update.zip which i get from RFS used ultraISO with kitchen V0.98 。 I use kitchen deodex all of the apks and jars file, then I signed to the APKS with 21choose。And news the new zip file。 after this, I get the apps and framework file to recovery RFS file which I get from the new ZIP file , i delete all the odexs file in the RFS。 I flash my cellphone with the new RFS I have made , the cell phone can't power on 。 why ?
thx!!!
mapleshadow said:
HI I have unzip my update.zip which i get from RFS used ultraISO with kitchen V0.98 。 I use kitchen deodex all of the apks and jars file, then I signed to the APKS with 21choose。And news the new zip file。 after this, I get the apps and framework file to recovery RFS file which I get from the new ZIP file , i delete all the odexs file in the RFS。 I flash my cellphone with the new RFS I have made , the cell phone can't power on 。 why ?
thx!!!
Click to expand...
Click to collapse
I'm not really sure what you are doing. If you deodex the ROM, the odex files shouldn't have to be deleted manually. Maybe I don't understand. No, I don't understand.
logcat is your friend... Connect a usb cable and do a 'adb logcat' from the command prompt while the phone is booting. You'll have to have the Android SDK downloaded and be in the tools folder or have it in your path to use adb.
I don't delete the *.odex manually, the files were deleted by the kicthen automatic.
After that, I made a update.zip, then upload the file, the device stuck in the startup loop.
Seriously, I do NOT modify any *.odex, just repack them.
I don't know why? Can you help me?
mapleshadow said:
I don't delete the *.odex manually, the files were deleted by the kicthen automatic.
After that, I made a update.zip, then upload the file, the device stuck in the startup loop.
Seriously, I do NOT modify any *.odex, just repack them.
I don't know why? Can you help me?
Click to expand...
Click to collapse
I can't help without more information. Can you get the output from 'adb logcat' while the phone is stuck in the startup loop and post it here?
The kitchen is really meant for Android on HTC phones, so your mileage may vary. Other device manufacturers tend to do some things differently.
This question has been asked in the Android Kitchen thread. Please do not start redundant threads.

[Q] Stuck on infinite boot loop

I was trying to change the notification bar by replacing framework-res.apk in system\framework folder. As soon as I copied the new one, my phone keeps rebooting. I keep the original copy of framwork-res.apk under \sdcard folder and I think just copying the original file back to system\framework folder will solve this. However, because of automatic rebooting, I can't connect the phone from pc to use adb from the PC or root exploer on the phone.
When I boot my phone with recover mode (volume key + power button), it only gives me 4 options.
Reboot system now
reinstall package
delete all user data
delete cash data
When I select reinstall package, it looked for update.zip that I don't have in my phone now. I'm really stuck.
Anyone knows how to copy the file into system folder in this case or reset to the factory rom?
I really appreciate for your help.
ADB should work in recovery mode.
If adb don't work try odin flash back to original
Sent from my SGH-T959 using XDA App

[Q] A riddle - Device Won't boot after changing Framework.jar file - why?

Hello to you all.
Noob ):
Ok, so I speak Hebrew, and Hebrew and Arabic I think are the only two languages that are being written from right to left.
This created a mess in Gmail and text messaging.
I emailed a friend, and he emailed me a revised Framework.jar file that fixed it on his vibrant. Cool.
So, I was doing everything according to procedure (see bellow), but got a stuck display on the boot screen "Galaxy S - Cynogen". Before my MIUI Rom booted.
This made me very sad, and I had no idea what to do. I went to recovery again and went to re-flashing my MIUI ROM
It worked and the phone booted again after it re-installed the zip MIUI - and everything is back to normal.
This means that something is not right with the Framework file or something?
Really not sure, I am really not good when it comes to this. Just followed directions.
Please help ):
Here is what I was told to do:
c:
cd tmp
dir
(Make sure you see the framework.jar file after you typed the "dir" command)
this will reboot your phone into recovery:
adb reboot recovery
after you are in recovery run this:
adb pull /system/framework/framework.jar framework_org.jar
This will backup your original file..
adb push framework.jar /system/framework/
This will copy the new file over..
After this reboot your phone either using the recovery menu options or by typing the following command:
adb reboot
Here is the revised Framework.jar file that I replaced with the "Stock" file

[Q] Help, removed bootstrap, ruined phone

I was following a guide to remove boot strap recovery, said to delete hijack in the system/bin folder and logwrapper, then rename logwrapper.bin to just logwrapper. Now I had hijack and logwrapper, but not logwrapper.bin, so to be safe i deleted hijack and renamed logwrapper to logwrapper.bak. Now my phone won't boot....
Anyway I can fix this without flashing a stock sbf on here?
rdbunch said:
I was following a guide to remove boot strap recovery, said to delete hijack in the system/bin folder and logwrapper, then rename logwrapper.bin to just logwrapper. Now I had hijack and logwrapper, but not logwrapper.bin, so to be safe i deleted hijack and renamed logwrapper to logwrapper.bak. Now my phone won't boot....
Anyway I can fix this without flashing a stock sbf on here?
Click to expand...
Click to collapse
You can try to use Early USB Enumeration and get into ADB. Most likely you will have to reflash.

[Q] Getting bootloop after push framework-res.apk

Hi, I know there are a few topic about this, but I checked it and don't have an answer.
I want to get work this: http://forum.xda-developers.com/showthread.php?t=1427510
So I dowloaded smoothspinners.7z and copy famework-res.apk from my phon to place-apk-here-for-modding in sdk folder (I installed APK Multi-Tool version 2.0)
I opened APK Multi-Tool and chose 9 (decompile) next go to project folder and replace file from smoothspinners.7z to framework-res.apk/res/drawable.
After that I chose 11 (compile) in APK Multi-Tool
"is this a system apk?" I chose "y"(yes)
"Aside from the signatures, would you like to copy over any additional files that you didn't modify from the original apk in order to ensure least # of errors" I chose "n" (no)
Next rename "unsignedframework-res.apk" from place-apk-here-for-modding to framework-res.apk and copy to android-sdk/platform-tools/
Next I adb:
adb remount
adb push /system/framework/framework-res.apk
adb remount
Next change permission to 644
And after reboot I have bootloop
Can someone help me, please? (of coures I have backup in recovery so my phon work, but I want to know what I made wrong in this steps)
atomic339 said:
Hi, I know there are a few topic about this, but I checked it and don't have an answer.
I want to get work this: http://forum.xda-developers.com/showthread.php?t=1427510
So I dowloaded smoothspinners.7z and copy famework-res.apk from my phon to place-apk-here-for-modding in sdk folder (I installed APK Multi-Tool version 2.0)
I opened APK Multi-Tool and chose 9 (decompile) next go to project folder and replace file from smoothspinners.7z to framework-res.apk/res/drawable.
After that I chose 11 (compile) in APK Multi-Tool
"is this a system apk?" I chose "y"(yes)
"Aside from the signatures, would you like to copy over any additional files that you didn't modify from the original apk in order to ensure least # of errors" I chose "n" (no)
Next rename "unsignedframework-res.apk" from place-apk-here-for-modding to framework-res.apk and copy to android-sdk/platform-tools/
Next I adb:
adb remount
adb push /system/framework/framework-res.apk
adb remount
Next change permission to 644
And after reboot I have bootloop
Can someone help me, please? (of coures I have backup in recovery so my phon work, but I want to know what I made wrong in this steps)
Click to expand...
Click to collapse
You should better ask D.O.C. directly in his thread or via PM, if you are not able/allowed to post questions in his thread.
He will know the best answer for your question ... surely.

Categories

Resources