Related
Hello everyone,
Can someone please inform and post a thread link of a battery mod that works on the i9001? By battery mod I mean small zip file that is installed from recovery and changes the stock battery meter
You can make it yourselt.
1. Use Root Explorer to get your framework-res.apk file
2. Go to http://uot.dakra.lt/ to customize it yourselt.
3. Go to http://forum.xda-developers.com/showthread.php?t=1253707 to download the Root-i9001-Signed.zip
4. Put the modified framework-res.apk in the above zip file and delete the unneeded files.
5. Update the updater-script file, resign the zip file.
6. Flash the zip file in recovery.
Do you like this one?
quest221 said:
You can make it yourselt.
1. Use Root Explorer to get your framework-res.apk file
2. Go to http://uot.dakra.lt/ to customize it yourselt.
3. Go to http://forum.xda-developers.com/showthread.php?t=1253707 to download the Root-i9001-Signed.zip
4. Put the modified framework-res.apk in the above zip file and delete the unneeded files.
5. Update the updater-script file, resign the zip file.
6. Flash the zip file in recovery.
Do you like this one?
Click to expand...
Click to collapse
If you use manveru0's kernal and recovery you can now flash the update files as they come from the kitchen
quest221 said:
You can make it yourselt.
1. Use Root Explorer to get your framework-res.apk file
2. Go to http://uot.dakra.lt/ to customize it yourselt.
3. Go to http://forum.xda-developers.com/showthread.php?t=1253707 to download the Root-i9001-Signed.zip
4. Put the modified framework-res.apk in the above zip file and delete the unneeded files.
5. Update the updater-script file, resign the zip file.
6. Flash the zip file in recovery.
Do you like this one?
Click to expand...
Click to collapse
Hmm... yes, nice, but I'm not in to designing things. I was looking for something that has been already created
what's the version of your Rom?
quest221 said:
what's the version of your Rom?
Click to expand...
Click to collapse
Firmware version : 2.3.4
baseband version I9001XXKP4
Kernel Version : [email protected] #7
Build Number : GINGERBREAD.XXKP4
I use Go launcher (from my opinion it's the best), if you think otherwise please post the better launcher, I am opened to experiment others.
Many thanks,
Ciprian
I don't have a I9001XXKP4 Rom in my hard drive. If you can send your your framework-res.apk, I can make one for you.
quest221 said:
I don't have a I9001XXKP4 Rom in my hard drive. If you can send your your framework-res.apk, I can make one for you.
Click to expand...
Click to collapse
I would like something like http://img225.imageshack.us/img225/9943/smoothbatt.png if it is possible.
I have attached framework-res.apk
opps a
hey guys!
just used this. twice great kitchen, really revamped some of the more boring icons on stock roms. thanks for the tip!!
1framework-res_I9001XXKP4_signed.zip is the file that I updated the updater-script so you can flash it in the in-build recovery.
1framework-res_I9001XXKP4_original_signed.zip is your original file. If there are any issues, you can flash it back in the in-build recovery.
How to:
Copy the zip file to the internal SD card, not the external one, go to recovery, flash it.
quest221 said:
1framework-res_I9001XXKP4_signed.zip is the file that I updated the updater-script so you can flash it in the in-build recovery.
1framework-res_I9001XXKP4_original_signed.zip is your original file. If there are any issues, you can flash it back in the in-build recovery.
How to:
Copy the zip file to the internal SD card, not the external one, go to recovery, flash it.
Click to expand...
Click to collapse
Thanks, exactly what I needed. I flashed it and all is ok
quest221 said:
1framework-res_I9001XXKP4_signed.zip is the file that I updated the updater-script so you can flash it in the in-build recovery.
1framework-res_I9001XXKP4_original_signed.zip is your original file. If there are any issues, you can flash it back in the in-build recovery.
How to:
Copy the zip file to the internal SD card, not the external one, go to recovery, flash it.
Click to expand...
Click to collapse
can i use it on 2.3.6 rom?
nope because you will end up in a bootloop by flashing this
its only for XXKP4
urm, Ive tried to do as you told in post number 2(by cooking it according to my own preference)
but my problem starts from step number 5
5. Update the updater-script file, resign the zip file.
Click to expand...
Click to collapse
I already received the cooked file
but I dont know how to change the update script and end up failing to update using the zip file.
can you please help me?
or link me to a place that really can help me to learn better on changing the update script.
try this one, I updated the updater-script, you can compare it with the one from kitchen.
PS: Forgot to update the update-binary file, now try the new one. It should work.
Thanks!!!! But I got an error that states
E:error in /tmp/sideload/package.zip
(status 2)
I wonder whats wrong.
looked in a thread
http://forum.xda-developers.com/showthread.php?t=1194245&page=3
and from what I understand it seems to be a problem with the update binary. But Im just an end user and this is too much for me.
anyway maybe Ill try to flash the cranium ROM and try to cook again a new one and use your update script.
cheers!!
Hi,
Is there any posibility to change framework-res.apk file without CWM? I don't want to instal CWM becouse of it has a problem with front side cam and I need this cam. It's can't be overwritten when the phone works. Maybe some adb and push command is possible.
Could you help me by describing the whole procedure? Sorry for my English.
@quest221
Can you maybe make one for Android 2.3.5 like the screenshot @ page 1?
I have baseband I9001XXKPF, Build XXKPG
I update the zip file with the new update-binary file.
Is there any posibility to change framework-res.apk file without CWM?
Click to expand...
Click to collapse
Yes, I just use the recovery from Samsung, not the third-party.
Check the post #2, that's the steps. Also replace the update-binary file with the one in my zip file.
Can you maybe make one for Android 2.3.5 like the screenshot @ page 1?
Click to expand...
Click to collapse
Upload your framework-res.apk file.
So while I was still learning about flashing, ROMs, Kernels, etc, I managed to get a CM9 build on my Captivate. However, I installed the build for smtd device instead of mtd device. Now when I go to install the latest nightly CM9 build (mtd version), it fails right away with an assert failure. I think it is because it is checking my device type and sees that I have the smtd version currently.
Is there an easy way around this? I've considered editing the install script in the zip file to bypass the assert. Would that work, or there a better way?
cgulka said:
So while I was still learning about flashing, ROMs, Kernels, etc, I managed to get a CM9 build on my Captivate. However, I installed the build for smtd device instead of mtd device. Now when I go to install the latest nightly CM9 build (mtd version), it fails right away with an assert failure. I think it is because it is checking my device type and sees that I have the smtd version currently.
Is there an easy way around this? I've considered editing the install script in the zip file to bypass the assert. Would that work, or there a better way?
Click to expand...
Click to collapse
Open the .zip file with winrar, then go to "\META-INF\com\google\android" and open the file "updater-script" with Notepad ++. Delete all the lines (The very beginning) that says: assert(getprop("ro.product.device") == "captivate" etc... save it, let winrar update the files. Then try flashing it again.
Thanks! That worked. That was what I suspected I needed to do. I can tell you this, it takes a LONG time to re-zip such a large file on a little under-powered netbook.
Nick0703 said:
Open the .zip file with winrar, then go to "\META-INF\com\google\android" and open the file "updater-script" with Notepad ++. Delete all the lines (The very beginning) that says: assert(getprop("ro.product.device") == "captivate" etc... save it, let winrar update the files. Then try flashing it again.
Click to expand...
Click to collapse
I've been having a similar problem, so I did this and was able to install the ROM, but it gets stuck in the boot animation. Any ideas?
UPDATE: Fixed it by formatting the boot and system partitions. I blame semaphore.
Hi All,
I'm relatively new to Android (had the Nexus 7 for about a year). My questions is this:
I have 4.2.2 currently loaded. When I orinally got the nexus 7, I used a toolkit to unlock the bootloader and root the device, so I could install SixAxis and a few other apps that required root.
What is the easiest way for me to now update to 4.3? Will the OTA update that is bound to show up on the device shortly work?
BTW This is the WiFi only Nexus 7, 16 GB and my main PC at home is a Mac.
Thanks.
Foxman2k said:
Hi All,
I'm relatively new to Android (had the Nexus 7 for about a year). My questions is this:
I have 4.2.2 currently loaded. When I orinally got the nexus 7, I used a toolkit to unlock the bootloader and root the device, so I could install SixAxis and a few other apps that required root.
What is the easiest way for me to now update to 4.3? Will the OTA update that is bound to show up on the device shortly work?
BTW This is the WiFi only Nexus 7, 16 GB and my main PC at home is a Mac.
Thanks.
Click to expand...
Click to collapse
Get it locked and unrooted to get OTA possiblt easiest way.
Otherwise flash the factory images:thumbup:
Sent using Nexus 7
basuraunak said:
Get it locked and unrooted to get OTA possiblt easiest way.
Otherwise flash the factory images:thumbup:
Sent using Nexus 7
Click to expand...
Click to collapse
Do you have a link of a guide that I could follow on how to flash the factory image?
Can I download the zip and then use the clockwork recovery i have installed to load the zip?
I don't think that having the bootloader locked or unlocked will really affect the OTA..
Am I right or am I right?
Foxman2k said:
Do you have a link of a guide that I could follow on how to flash the factory image?
Can I download the zip and then use the clockwork recovery i have installed to load the zip?
Click to expand...
Click to collapse
Just use wug's toolkit. Its over in the android development in the n7 section...
---------- Post added at 10:04 AM ---------- Previous post was at 10:00 AM ----------
drake90001 said:
I don't think that having the bootloader locked or unlocked will really affect the OTA..
Am I right or am I right?
Click to expand...
Click to collapse
I dont think having it unlocked will effect the ota (it hasnt in the past for me), but it sounded like he wanted to flash the factory image. I actually have a nandroid of it on my unlocked n7. Gonna flash the official and see if I can get the ota later...
I've taken OTAs no problem on an unlocked, rooted device with TWRP recovery. So you're fine.
Sent from my Nexus 7 using Tapatalk 4 Beta
Here you go for flashable zip :
http://forum.xda-developers.com/showthread.php?t=2376522
Sent from my Nexus 7 using xda premium
So I downloaded what I believe to be the right file, ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07 (1).zip.
I then reboot my nexus 7 into clockworkmod revovery and select install zip, choose zip from sdcard, browse to the aboev file but then get an error:
It ends in (Status 7) Installation aborted.
What am I missing?
Also, just tried via adb sideload and that didn't work either.
Foxman2k said:
So I downloaded what I believe to be the right file, ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07 (1).zip.
I then reboot my nexus 7 into clockworkmod revovery and select install zip, choose zip from sdcard, browse to the aboev file but then get an error:
It ends in (Status 7) Installation aborted.
What am I missing?
Click to expand...
Click to collapse
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Groid said:
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Click to expand...
Click to collapse
No to all of the above. I don't know what odex files or buildprop file would refer to, so I defintely haven't modified them.
It says:
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/debuggerd", "a whole bunch of letters and numbers", "a whole bunch of letters and numbers")
E:Error in /sdcard/0/update rom/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi - JWR66V - from - JDFQ39.ab67ca07 (1).zip
(Status 7)
Installation aborted.
Groid said:
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Click to expand...
Click to collapse
Foxman2k said:
No to all of the above. I don't know what odex files or buildprop file would refer to, so I defintely haven't modified them.
It says:
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/debuggerd", "a whole bunch of letters and numbers", "a whole bunch of letters and numbers")
E:Error in /sdcard/0/update rom/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi - JWR66V - from - JDFQ39.ab67ca07 (1).zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Does it make a difference that my current build number in "about tablet" shows as JDQ39 and not JDFQ39 as above?
The problem file is 'debuggerd' in the /system/bin folder as it says in the error message. I had the same issue previously on the last N7 update. I had to get the original file from someone since the file had been replaced by another app (possibly Stickmount) or it can be extracted from the previous update to 4.2.2. I don't know about the JDFQ39 compared to the download file showing JDQ39, but that is the same file I downloaded. The (1).zip means you had previously downloaded the file and this is an additional d/l. That shouldn't be a problem, but you can delete the (1) if you want.
I'll try flashing through CWM and let you know if mine worked. If so, I can send you the right 'debuggerd' file.
Groid said:
The problem file is 'debuggerd' in the /system/bin folder as it says in the error message. I had the same issue previously on the last N7 update. I had to get the original file from someone since the file had been replaced by another app (possibly Stickmount) or it can be extracted from the previous update to 4.2.2. I don't know about the JDFQ39 compared to the download file showing JDQ39, but that is the same file I downloaded. The (1).zip means you had previously downloaded the file and this is an additional d/l. That shouldn't be a problem, but you can delete the (1) if you want.
I'll try flashing through CWM and let you know if mine worked. If so, I can send you the right 'debuggerd' file.
Click to expand...
Click to collapse
Ok great. I do have stickmount installed...
Well, I got the debuggerd error also. I'll try the backup debuggered file I used in the last update. Otherwise, I'll have to find the debuggerd file from 4.2.2. Any help out there?
Groid said:
Well, I got the debuggerd error also. I'll try the backup debuggered file I used in the last update. Otherwise, I'll have to find the debuggerd file from 4.2.2. Any help out there?
Click to expand...
Click to collapse
Glad I'm not alone lol
Still no joy. I think someone will have to get the right debuggerd file and get it to one us on a pm or email. Also, I noticed on my update try that the file was listed as JDQ39. ... and not the JDFQ39. ... that you saw.
Groid said:
Still no joy. I think someone will have to get the right debuggerd file and get it to one us on a pm or email. Also, I noticed on my update try that the file was listed as JDQ39. ... and not the JDFQ39. ... that you saw.
Click to expand...
Click to collapse
once we get the file, how do I replace the file with the debuggerd that is currently on the nexus?
What I will do is to copy the debuggerd file to the N7 internal storage root folder from my pc. Then I will rename /system/bin/debuggerd to debuggerd.bak (or whatever extension you want to add). Then I will copy the correct debuggerd file from sdcard to /system/bin and try the update again. I started a new thread asking for someone with an unaltered 4.2.2 debuggerd file to send it to me. If I get it I'll pass it along to you.
Groid said:
What I will do is to copy the debuggerd file to the N7 internal storage root folder from my pc. Then I will rename /system/bin/debuggerd to debuggerd.bak (or whatever extension you want to add). Then I will copy the correct debuggerd file from sdcard to /system/bin and try the update again. I started a new thread asking for someone with an unaltered 4.2.2 debuggerd file to send it to me. If I get it I'll pass it along to you.
Click to expand...
Click to collapse
Are you using a tool like ES File Manager to do the moving and renaming of files etc?
Hello,
I currently have Tsunami X 5.6 android 4.2.2.
I want to update to Kitkat roms but I cant.
I get "status 7" error while trying to install.
I understood that it's because I have an old CWM recovery (6.0.3.2).
How do I update it?
Sorry for the n00b question..
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing called “asserts”.
How To Fix Statue error:
DO A NANDROID BACKUP if you haven't done so already just in case...
1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.
2. Once unzipped, browse to the META-INF/com/ google/android directory. You will find two files called “update-binary” and “updater-script”.
3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.
4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file.
5. Save file.
6. Rename “updater-script.txt” back to “updater-script”.
7. Rezip all the files you’ve unzipped.
8. Copy the new, edited zip file to your phone.
9. Try re-installing ROM, now it should install fine without Status 7 error.
-MaoR- said:
Hello,
I currently have Tsunami X 5.6 android 4.2.2.
I want to update to Kitkat roms but I cant.
I get "status 7" error while trying to install.
I understood that it's because I have an old CWM recovery (6.0.3.2).
How do I update it?
Sorry for the n00b question..
Click to expand...
Click to collapse
If the previous answer is too complicated for you, just flash CM10.2 that will do proper partition for the latest ROMs and give you updated CWM recovery with which you can flash any KK rom. Just reboot once intonthe OS, then back to recovery and flash a KK rom. Don't forget to manually wipe /system before installing KK.
You will need to flash zip twice, as first time it will disolay warning of repartition and abbort with status 7. By next attempt it will work flawless.
pryerlee said:
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing called “asserts”.
How To Fix Ststue error:
DO A NANDROID BACKUP if you haven't done so already just in case...
1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.
2. Once unzipped, browse to the META-INF/com/ google/android directory. You will find two files called “update-binary” and “updater-script”.
3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.
4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file.
5. Save file.
6. Rename “updater-script.txt” back to “updater-script”.
7. Rezip all the files you’ve unzipped.
8. Copy the new, edited zip file to your phone.
9. Try re-installing ROM, now it should install fine without Status 7 error.
Click to expand...
Click to collapse
tetakpatak said:
If the previous answer is too complicated for you, just flash CM10.2 that will do proper partition for the latest ROMs and give you updated CWM recovery with which you can flash any KK rom. Just reboot once intonthe OS, then back to recovery and flash a KK rom. Don't forget to manually wipe /system before installing KK.
You will need to flash zip twice, as first time it will disolay warning of repartition and abbort with status 7. By next attempt it will work flawless.
Click to expand...
Click to collapse
Thanks guys.
I actually did flash CM 10.2 just before even seeing the your comments.
It worked great and now I actually think on staying with this ROM lol..
It's very clean and nice.
Thanks again!
Need it for a Cricket 626s. It was never officially released by Cricket, so if anyone has a T-Mo or Metro ZIP, that would be wonderful.
The T-Mo/Metro RUU's didn't take.
I flashed the T-Mobile Debloated MM ROM from XDA on my Cricket 626s. I haven't encountered any big issues yet, but make sure you back up Lollipop in the event that you do.
IMPORTANT: Before you first boot up into MM, remove your SIM card. Do not insert it until the setup process is completely over. When you get to Self-Service, wait a while to bypass it.
jakesnot-hereman said:
I flashed the T-Mobile Debloated MM ROM from XDA on my Cricket 626s. I haven't encountered any big issues yet, but make sure you back up Lollipop in the event that you do.
IMPORTANT: Before you first boot up into MM, remove your SIM card. Do not insert it until the setup process is completely over. When you get to Self-Service, wait a while to bypass it.
Click to expand...
Click to collapse
Where can you download this?
technohunter123 said:
Where can you download this?
Click to expand...
Click to collapse
I misspoke; it's actually the Sprint ROM: https://forum.xda-developers.com/de...m-flashable-stock-htc-626s-debloated-t3293602
I forgot one step, though. There's a couple of lines in a single file that prevent this file from flashing.
To fix it:
Open the .zip file from Windows (Without extracting)
Navigate to /META-INF/com/google/android/
Open 'updater-script' with a good text editor
Delete the lines from 'assert' to the next semi-colon
Save, and let Windows recompile the .zip
This new file should flash without problem. If you have trouble doing this, say something, and I'll upload mine when I get home.
jakesnot-hereman said:
I misspoke; it's actually the Sprint ROM: https://forum.xda-developers.com/de...m-flashable-stock-htc-626s-debloated-t3293602
I forgot one step, though. There's a couple of lines in a single file that prevent this file from flashing.
To fix it:
Open the .zip file from Windows (Without extracting)
Navigate to /META-INF/com/google/android/
Open 'updater-script' with a good text editor
Delete the lines from 'assert' to the next semi-colon
Save, and let Windows recompile the .zip
This new file should flash without problem. If you have trouble doing this, say something, and I'll upload mine when I get home.
Click to expand...
Click to collapse
Thanks for helping out here. I just tried your suggestion, and when I flash from TWRP, I get the error:
"Updater process ended with ERROR: 6
Error installing zip file '/sdcard/TWRP/Sprint_Stock_MMDB_2.27.651.6.zip'"
embhorn said:
Thanks for helping out here. I just tried your suggestion, and when I flash from TWRP, I get the error:
"Updater process ended with ERROR: 6
Error installing zip file '/sdcard/TWRP/Sprint_Stock_MMDB_2.27.651.6.zip'"
Click to expand...
Click to collapse
Huh. Try this zip; I just flashed it successfully: https://drive.google.com/file/d/0B9O8izj2yw8iTWFnXzRWS20xaUk/view?usp=sharing
jakesnot-hereman said:
Huh. Try this zip; I just flashed it successfully: https://drive.google.com/file/d/0B9O8izj2yw8iTWFnXzRWS20xaUk/view?usp=sharing
Click to expand...
Click to collapse
That did it! Thanks for your help getting the right ROM.
:good:
After installing the ROM, I followed these instructions for activating / setting up (since I got the error "Cannot contact Google servers" trying activate G account):
https://forum.xda-developers.com/showpost.php?p=69853901&postcount=281
Help
Help please my little brother attempted to root his metro pcs htc desire 626s and some how he accidently wiped the os on it will the file on the thread be a rom i could install to his phone using twrp?
gruiz487 said:
Help please my little brother attempted to root his metro pcs htc desire 626s and some how he accidently wiped the os on it will the file on the thread be a rom i could install to his phone using twrp?
Click to expand...
Click to collapse
You can use the zip that jakesnot-hereman posted in TWRP