Related
original thread here:
http://forum.xda-developers.com/showthread.php?t=1248486
just thought i would post it for those that want to create flashable zips. sorry if this isn't the right section.
DOWNLOAD:
Rar archive
Windows installer
credits:
benzyniarz1
Jordan,
Tried this on my Win7 box and I keep getting error status 6?
What am I doing wrong?
When do you get the error? Running the program or when trying to create the zip?
The program runs on my Win 7 64bit setup. But I haven't tried to create a zip yet.
Have you tried right clicking on the file and changing the Compatibility to something like Win XP?
Truckerglenn said:
When do you get the error? Running the program or when trying to create the zip?
The program runs on my Win 7 64bit setup. But I haven't tried to create a zip yet.
Have you tried right clicking on the file and changing the Compatibility to something like Win XP?
Click to expand...
Click to collapse
It runs and creates the zip just fine. When I try to flash it with cwm it comes up with error 6 and fails.
SNadler said:
It runs and creates the zip just fine. When I try to flash it with cwm it comes up with error 6 and fails.
Click to expand...
Click to collapse
Sorry I haven't been able to reply. There should be two cwm options or whatever. The type like edify or amend or something hold on ill look at uot
Sent from my SAMSUNG-SGH-I997 using xda premium
Ok there's amend and edify
Sent from my SAMSUNG-SGH-I997 using xda premium
Nvm I know what it is
Sent from my SAMSUNG-SGH-I997 using xda premium
Ok. its the updater-script. U have to create a script.
Sent from my SAMSUNG-SGH-I997 using xda premium
JordanElliott said:
Ok. its the updater-script. U have to create a script.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
I am using edify....
Here is the one I made that does not work so you can maybe se where I went wrong and the program I was trying to make a .zip
I have it running in /system/app by restoring it from TB and also by means of ADB push but wanted to learn how to use this tool.....
Thanks!
SNadler said:
I am using edify....
Here is the one I made that does not work so you can maybe se where I went wrong and the program I was trying to make a .zip
I have it running in /system/app by restoring it from TB and also by means of ADB push but wanted to learn how to use this tool.....
Thanks!
Click to expand...
Click to collapse
here is what you do. go to meta-inf folder in your update.zip. and drag updater-script from the folder and right click. edit it with notepad++ and hit ctrl+a and copy this
ui_print("HERE U CAN PUT WHATEVER YOU WANT");
ui_print("Mounting system...");
run_program("/sbin/busybox", "mount", "/system");
show_progress(1, 15);
ui_print("Installing");
package_extract_dir("system", "/system");
ui_print("Unmounting system...");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Installation complete!");
here is notepad++
JordanElliott said:
here is what you do. go to meta-inf folder in your update.zip. and drag updater-script from the folder and right click. edit it with notepad++ and hit ctrl+a and copy this
ui_print("HERE U CAN PUT WHATEVER YOU WANT");
ui_print("Mounting system...");
run_program("/sbin/busybox", "mount", "/system");
show_progress(1, 15);
ui_print("Installing");
package_extract_dir("system", "/system");
ui_print("Unmounting system...");
run_program("/sbin/busybox", "umount", "/system");
ui_print("Installation complete!");
Click to expand...
Click to collapse
Thanks I will try it in the AM.
This will need to be used every time I run the program then to use it for programs that go into the /system/app folder correct?
SNadler said:
Thanks I will try it in the AM.
This will need to be used every time I run the program then to use it for programs that go into the /system/app folder correct?
Click to expand...
Click to collapse
Well if u want copy what I pasted directly into zip updater creater or whatever
Sent from my SAMSUNG-SGH-I997 using xda premium
JordanElliott said:
Well if u want copy what I pasted directly into zip updater creater or whatever
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Tried it and it still came up with error 6?
SNadler said:
Tried it and it still came up with error 6?
Click to expand...
Click to collapse
Idk then bro. I haven't tried the prohrar
Sent from my SAMSUNG-SGH-I997 using xda premium
JordanElliott said:
Idk then bro. I haven't tried the prohrar
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Thanks anyway, I just took another and swapped the program i wanted to use with the one in it and that was just as easy.......
So I am having problems having WiFiCalling.apk and other apps to install in the data/app in my flashable ROM.
I used this:
package_extract_dir("data/app", "/data/app");
Click to expand...
Click to collapse
And that didn't work. Can you anyone help me?
I have googled the web and this site and have found some information but it seems incomplete and was for other phones.
Mainly in order to install a Thai font I rooted my phone using adb and zergRush on linux. Tried SuperOneClick but got stuck at "Waiting for phone" despite ADB recognizing my phone after adding the id to the usb hotplug configuration. So I rooted, installed busybox and su through adb, installed terminal through the market, then proceeded to clean up all the crap from this phone (except drivesmart having read about someone bootlooping their phone that way though I kinda have my doubts that's why their phone looped).
I deleted the Browser.apk, then discovered that Fennec, Opera, Dolphin, and Skyfire for some reason will not hand over the live video stream from m.thaipbs.or.th to the media player, but the stock browser handled it perfectly (I just hope their site didn't get screwed up at the same time I deleted the stock browser, in which case I actually have no problem whasoever, but I digress)
I hunted for a stock Browser.apk, trying a couple of different ones which either failed to parse, told me that it didn't install, or gave me a white screen followed by fc after installing, or when copying directly to /system/app didn't show in my apps menu.
Finally I found a thread on xda-developers containing an archive of the stock /system/app from the t589... YES!!! But no joy, couldn't install and moving the apk and odex directly to /system/app which worked great for Google Play Store doesn't put the browser in my app menu.
I have found some threads for various devices referencing using recovery to flash a zip with the system app to your phone, but some of them say you have to use cwm, but this phone has no custom recoveries AFAIK. And I don't quite understand the flash process enough to feel safe doing it. Does the recovery flash wipe apps/data, or does it just stick whatever apks/odexes in the update.zip into your /system/app and do whatever magic needs to be done to make it work, leaving your phone basically intact?
Any kind of tutorials or just good solid info about what will happen if I flash the update.zip using the stock recovery would be appreciated. Thanks guys, you seem like an awesome community and I look forward to being a forum member!
只能帮顶了！：d：d：d
Is that Chinese for BUMP?
No replies? :"(
Well I found this post which seems helpful.. can someone please let me know if this method works and will leave my data intact?
Nikhil_007 said:
Hi Doomlord,
thats a wonderful work..i mean thats a perfect explanation of creating update.zips...
another alternative, which i use frequently to update apps in system forlder only is..
go to titanium back up options and create update.zip
now select this update.zip from mounted SD card and then open it with 7zip or any zip editor.
then replace system/app forlder ->app to any app u want to install in system..
save and close the file. and u r good to go...
just an alternative which i personally found easy...but nothing to take away from your awsum thread here..keep the good work..thanks..
Click to expand...
Click to collapse
I tried making an update.zip using titanium backup, then replacing titanium ackup with my own files, zipping it back up, then signing with zipsigner in test/auto mode. It gives me error 0... does anyone know what I'm doing wrong?
Here's my updater-script:
ui_print("");
ui_print("Installing Browser ...");
show_progress(1.0,0);
run_program("/sbin/busybox", "mount", "/dev/stl12", "/system");
set_progress(0.33);
package_extract_file("system/app/Browser.apk", "/system/app/Browser.apk");
package_extract_file("system/app/Browser.odex", "/system/app/Browser.odex");
set_progress(0.66);
set_perm(0, 0, 0644, "/system/app/Browser.apk");
set_perm(0, 0, 0644, "/system/app/Browser.odex");
unmount("/system");
set_progress(1.00);
ui_print("Done !");
Am I posting in the wrong forum> There is no device-specific forum for this phone.. if anyone knows a better place for me to seek help it would be very much appreciated. Thanks!
So, I was trying to get Google Wallet to work on my VZW rooted Galaxy S3. I edited three lines in my build.prop. Specifically, my edits were
Code:
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
They had been suggested on another site as a way to allow the installation of Google Wallet. In hindsight, probably shouldn't have gone with that advice. I did not perform a nandroid backup via CWM before starting, but did back up build.prop on my computer.
I rebooted my phone, and the phone got past the first Samsung logo, and then the Samsung Galaxy S3 screen, and went to a black screen after that. None of the buttons do anything, and the LED does nothing. Removing the battery is the only way to get back to a powered-off state from which I can re-enter the boot cycle. I can enter both recovery mode and download mode, and if I plug my phone into my computer at the black-screen point after normal boot, I can access the phone via adb.
So here's the real problem. I need to replace my build.prop with the backed-up version. In order to modify build.prop in the first place, I found that adb remount failed (I think I got permission denied or something), so after pulling build.prop, editing it, and saving it locally on the computer (using Ubuntu 10.04 LTS), I pushed the file to /mnt/sdcard/ so as not to encounter permission problems. I found that entering adb shell and going to su did not allow me to switch out the edited file, as I got a cross-device error. So in the phone I entered ES File Explorer (in which I enabled root explorer, and which I had previously used to remount the file system as read-write), and switched out the build.prop with my edited version.
Obviously, I cannot use my ES File Explorer trick to replace build.prop now that the phone is not working. So I try using adb shell. I again encounter the remount issue:
Code:
[email protected]:/Onyx/adiv/android-sdk-linux_x86/platform-tools$ ./adb remount
remount failed: Operation not permitted
I saw elsewhere that the same can be accomplished via adb shell with su. So I try, and get this far:
Code:
[email protected]:/ $ su
Segmentation fault
Definitely not good. Having now realized the error of my ways in not creating a nandroid before messing things up, I think, hey, I can make a nandroid now, pull the backup to my computer, and replace the build.prop in the backup, figure out how to update the MD5 sum, and recover from the modified backup. So I backup in CWM (recall that I can still enter recovery mode), pull the recovery, and take a look.
First I notice that the folder under clockworkmod/backup/ is quite oddly named 1970-01-30.22.07.14. I don't expect this to be a huge issue. I need to edit the system component, which I see seems to be distributed between system.ext4.tar.a (1.0 gb), system.ext4.tar (0 bytes), and system.ext4.tar.b (136.1 mb). I'm unable to unpack any of these three, as they don't seem to be packed like normal tarballs. And this is where I hit a dead-end for this method.
A third option which I admit I haven't fully explored is throwing the original build.prop in an update.zip and flashing that via recovery, and I haven't explored that option fully because I really have no idea what the inside of an update.zip looks like, or how I would go about building my own, and the few guides I looked at for building my own update.zip focused on either installing custom roms or installing apps, not replacing individual system files.
Any advice on where to go from here? I'd really rather not have to do a factory restore and re-apply root and re-install my apps and reconfigure everything and all that jazz, but if that's the only option I have, it's not like it's the end of the world--I can at least pull my data off the device using adb.
To summarize:
What I need to accomplish:
Replace my modified build.prop with the original build.prop that I backed up
Obstacles:
su in adb shell no longer appears to be working due to a "segmentation fault".
adb remount does not work, as the "Operation [is] not permitted."
I can't seem to unpack the system component of the nandroid backup, which has the wrong date.
How I thought I might fix it:
Use adb to push the new build.prop file and get it in its correct spot.
Edit a backup created by clockwork mod to have the correct build.prop and flash the backup via recovery.
Throw the correct build.prop in an update.zip file and install via recovery.
Any suggestions, ideas, or tips?
If I have to use option 3, does anybody have any tips as to building the update.zip? (Don't worry, if that's what I have to do, I'll do my due diligence and read up on update.zips and look through a few example update.zips)
Thanks,
Adiv
Stock build.prop in a convenient zip file. Enjoy.
Vorfidus said:
Stock build.prop in a convenient zip file. Enjoy.
Click to expand...
Click to collapse
Thanks! Will post back when I have results.
EDIT:
It seems the update-script in the zip file you provided was written in Amend, which is no longer supported--since 3.0, Android uses Edify. CWM throws an error accordingly. However, what you have provided is pretty much all I need to put together a new update.zip (I hope) with the correct scripting language.
adiv.paradise said:
Thanks! Will post back when I have results.
EDIT:
It seems the update-script in the zip file you provided was written in Amend, which is no longer supported--since 3.0, Android uses Edify. CWM throws an error accordingly. However, what you have provided is pretty much all I need to put together a new update.zip (I hope) with the correct scripting language.
Click to expand...
Click to collapse
I replaced update-script with updater-script. I then spent roughly two hours or so trying to find an update-binary that worked on the GS3 US variants. I have included the new update.zip file, with the update-binary inside. After switching to updater-script (written in Edify), and using the correct updater-binary, I finally got the updater-script to run. And I got as far as injecting the new build.prop. I get the following error:
Code:
assert failed: package_extract_file("build.prop","/system/build.prop")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Here is my updater-script:
Code:
ui_print(" Mounting system...");
assert(mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system"));
set_progress(0.100000);
ui_print(" Deleting old build.prop...");
delete("/system/build.prop");
set_progress(0.400000);
ui_print(" Injecting build.prop....");
set_progress(0.410000);
assert(package_extract_file("build.prop","/system/build.prop"));
set_progress(0.800000);
ui_print(" build.prop successfully injected!");
ui_print(" unmounting /system...");
assert(unmount("/system"));
set_progress(1.000000);
ui_print(" Done! Yay!");
I'll try the package_extract_dir command as well, but my experience thus far has been that it probably won't make a difference.
Anybody have any quick tips on getting the build.prop to actually inject? My hunch is that this is coming back to the difficulties I had with mounting /system as -rw.
OH GOOD LORD I HAVE DONE IT!
Switching to package_extract_dir did the trick.
For posterity, I'm uploading the final update.zip, and I'm posting here my updater-script:
Code:
ui_print(" Mounting system...");
assert(mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system"));
set_progress(0.100000);
ui_print(" Deleting old build.prop...");
delete("/system/build.prop");
set_progress(0.400000);
ui_print(" Injecting build.prop....");
set_progress(0.410000);
assert(package_extract_dir("system","/system"));
set_progress(0.800000);
ui_print(" build.prop successfully injected!");
ui_print(" unmounting /system...");
assert(unmount("/system"));
set_progress(1.000000);
ui_print(" Done! Yay!");
Hopefully, I never again do something like this without first performing a nandroid backup :/
So I guess my half done update zip did it. I knew I missed something haha.
Sent from my SCH-I535 using xda app-developers app
adiv.paradise said:
OH GOOD LORD I HAVE DONE IT!
Switching to package_extract_dir did the trick.
For posterity, I'm uploading the final update.zip, and I'm posting here my updater-script:
Code:
ui_print(" Mounting system...");
assert(mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system"));
set_progress(0.100000);
ui_print(" Deleting old build.prop...");
delete("/system/build.prop");
set_progress(0.400000);
ui_print(" Injecting build.prop....");
set_progress(0.410000);
assert(package_extract_dir("system","/system"));
set_progress(0.800000);
ui_print(" build.prop successfully injected!");
ui_print(" unmounting /system...");
assert(unmount("/system"));
set_progress(1.000000);
ui_print(" Done! Yay!");
Hopefully, I never again do something like this without first performing a nandroid backup :/
Click to expand...
Click to collapse
So if I lost my build.prop (Idk how, don't ask) flashing this in cwm will restore it?
Probably. The only thing you might run into is there's a line in the updater script that deletes the current build.prop before injecting the new one. If there is no current build.prop, it might throw an error. If it does, just delete that line from the script, repackage the zip, and flash from cwm.
Help my tablet - ramos w30 can not boot after edited build.prob
Hi all,
Please help me, after i edited file build.prob, my tablet (ramos w30) can not boot, it stop at logo.
Now i get origin file build.prob from another tablet and i want recopy to tablet to sovle this case.
I dont know way to make file update.zip with file build.prob thus please help me.
This is my origin build.prob , hope to get your update.zip from you
Thank you billion time.
jo_blow421 said:
So if I lost my build.prop (Idk how, don't ask) flashing this in cwm will restore it?
Click to expand...
Click to collapse
Tank you
thaibao1269 said:
Hi all,
Please help me, after i edited file build.prob, my tablet (ramos w30) can not boot, it stop at logo.
Now i get origin file build.prob from another tablet and i want recopy to tablet to sovle this case.
I dont know way to make file update.zip with file build.prob thus please help me.
This is my origin build.prob , hope to get your update.zip from you
Thank you billion time.
Click to expand...
Click to collapse
Sorry I never responded to this... That's what happens when you comment on an old thread.
I can't put together an update.zip for you, or rather, I won't. I'm not an update.zip factory to which you can place an order for an update.zip that will magically solve all your problems. Particularly for a device I don't have. However, I have in this thread laid out all the groundwork you'll need to do it yourself. You'll need to acquire a working build.prop for your device (using any other will brick your device), an update-binary specific to your device (you can't use the one in my update.zip, that's for the Verizon GS3), and then you'll need to change the update script that was discussed in detail here. For one, the memory addresses will be different, so for example mmcblk0p14 will be different for your device, and the directory structure might be different as well. You'll need to do some research and dig around in my update.zip to see how it was done.
Error on sideloading
adiv.paradise said:
OH GOOD LORD I HAVE DONE IT!
Switching to package_extract_dir did the trick.
For posterity, I'm uploading the final update.zip, and I'm posting here my updater-script:
Code:
ui_print(" Mounting system...");
assert(mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system"));
set_progress(0.100000);
ui_print(" Deleting old build.prop...");
delete("/system/build.prop");
set_progress(0.400000);
ui_print(" Injecting build.prop....");
set_progress(0.410000);
assert(package_extract_dir("system","/system"));
set_progress(0.800000);
ui_print(" build.prop successfully injected!");
ui_print(" unmounting /system...");
assert(unmount("/system"));
set_progress(1.000000);
ui_print(" Done! Yay!");
Hopefully, I never again do something like this without first performing a nandroid backup :/
Click to expand...
Click to collapse
I am trying to sideload my LG g2 (LS980) with this update.zip. Obviously I have modified the build.prop file inside it. But when sideloading i get the following error. E: footer is wrong
E: Signature verification failed
Do you know why this happen?
Anoop S S said:
I am trying to sideload my LG g2 (LS980) with this update.zip. Obviously I have modified the build.prop file inside it. But when sideloading i get the following error. E: footer is wrong
E: Signature verification failed
Do you know why this happen?
Click to expand...
Click to collapse
Same Error here, i only have Chance to recover my build.prop from update via sideload or directly from sdcard. Thanks for any hints.
Dude need help also. i have Lenovo A328, when i edited my build.prop i forgot to change the permisssions and then i rebooted it. unfortunately it ends up in black screen. and i cant seem to fix the problem using update.zip. it always says INSTALLATION ABORTED.
Guys, you need to realize that a solution for the Verizon GS3 (sch-i535) is not going to work for any other model--the firmware is different, the memory layouts are different, and the binaries involved are different. You can't just stick in a build.prop for your own phone. You need to find an update-binary or updater-binary or whatever that works with your specific model, do research on the memory layout used in your phone, edit the injection script accordingly (that means actually learning a bit of Edify, you can't just do a search-replace to make it work, you actually need to understand what the script is doing if you want any chance of building a proper script), and use the correct build.prop. It's going to take some legwork. Also, keep in mind that I found my solution about two and a half years ago--Android has gone through I think 3 or 4 significant revisions since then--I think my phone was still on ICS (4.0) at the time, we've since had 4.1, 4.2, 4.3, 4.4, and now 5.0 if you're on that. Things may have changed, and my solution may no longer work, even for the VZW GS3.
Alcatel 4011x bootloop after editing build.prop. Need script file
Help me (im newbie) can you guys make a update.zip for me.
My phone is alcatel one touch glory 2S pro (4011x). Please make me a update.zip to inject my backup build.prop. my phone bootloop because I did not change the permission I guess :what:
sorry for my grammar because english is not my native langguage
Ps: i cant use adb because i dont have a pc
Please help me I really need a script that can inject this build.prop
I Do Not own a 3D MaX but here is an ICS ROm this is a test to see if it works im working blind here but here it goes
Rom
Kernel
It's a normal Flashable Zip
I removed some skt stuff and other apps to reduce size
Happy Testing
Edit 1:
3dMax_ICS_Kernel_B2.zip - 5.85 MB
New Kernel
inside 9-5-13_updater-script.zip you will find updater-script file put it 3D_MaX_ICS.zip Open it with WinRar 7z nvaigate to META-INF\com\google\android and replace it
also 9-5-13_build.rar you will find build .prop replace the one inside 3D_MaX_ICS.zip in the system folder
hi
3D is working ?
teperkov said:
hi
3D is working ?
Click to expand...
Click to collapse
Its stock should be working flash it and then tell me
Sent from my LG-P920 using xda app-developers app
defcomg said:
Its stock should be working flash it and then tell me
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
hello @defcomg
i was sleeping when you messaged me.
can you pm me what changes you made?
and sorry i cant try as i am having only 2g internet with 15kbps speed
Sent from my LG-P725 using xda app-developers app
How did you extract su870 20f bin ?
OptimusRs said:
How did you extract su870 20f bin ?
Click to expand...
Click to collapse
if you guys dont know there is a new extractor known as LG BIN EXTRACTOR that directly unpack bin to .img
Google it
Sent from my LG-P725 using xda app-developers app
Eklovya said:
if you guys dont know there is a new extractor known as LG BIN EXTRACTOR that directly unpack bin to .img
Google it
Sent from my LG-P725 using xda app-developers app
Click to expand...
Click to collapse
i tryed the old bin extractor but not work with 20f kdz i well search
Thanks
OptimusRs said:
i tryed the old bin extractor but not work with 20f kdz i well search
Thanks
Click to expand...
Click to collapse
here you go.
www.lg-phones.org/how-to-convert-lg-firmware-from-bin-tot-to-kdz.html
Sent from my LG-P725 using xda app-developers app
defcomg said:
Its stock should be working flash it and then tell me
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
i cant download it : ( maybe could upload this on any different server ?
teperkov said:
i cant download it : ( maybe could upload this on any different server ?
Click to expand...
Click to collapse
so @defcomg here are the problems
1. the zip can be flashed but there is a problem in updater script as far as i know because the updater script is not able to mount partitions for system data and boot.
Solution :- I edited the updater script and edited lines pretaining to mount system and boot and it flashed successfully.
2. It boots but it has same and i would say more issues as after booting it shows BLUE ERROR HANDLER and com.lege.ime and java.lang have crashed and many other popups.
3. there is still no network . imei is null and wake lock issue is still there.
the phone freezes and reboots automatically.
Sent from my LG-P725 using xda app-developers app
3d ,gps,wifi ,working???
Eklovya said:
so @defcomg here are the problems
1. the zip can be flashed but there is a problem in updater script as far as i know because the updater script is not able to mount partitions for system data and boot.
Solution :- I edited the updater script and edited lines pretaining to mount system and boot and it flashed successfully.
2. It boots but it has same and i would say more issues as after booting it shows BLUE ERROR HANDLER and com.lege.ime and java.lang have crashed and many other popups.
3. there is still no network . imei is null and wake lock issue is still there.
the phone freezes and reboots automatically.
Sent from my LG-P725 using xda app-developers app
Click to expand...
Click to collapse
replace the lgeime with another keyboard it always force closes when the rom is deodexed i think the no network error is caused by nv1 and nv2 partition being different could please tell what partitions are on the p720 i also sylinked lgrm mpt partition as i did not know weather or not they exist as for wakelock may have todo with gb uboot so wkpark bootloader might be needed . so what i need is a full logcat and partitions list i wonder why the updater script did not work as it would mount system and data on any omap tested it on my o3d weird
Sent from my LG-P920 using xda app-developers app
Updated Post #1
Made some changes with feedback from Eklovya
Surprisingly with all the ics port request his the only one to try it
Without feedback logcats i cant do nothing more about it................
new kernel , what is change? 3d , wifi, gsm working?
defcomg said:
I Do Not own a 3D MaX but here is an ICS ROm this is a test to see if it works im working blind here but here it goes
Rom
Kernel
It's a normal Flashable Zip
I removed some skt stuff and other apps to reduce size
Happy Testing
Edit 1:
3dMax_ICS_Kernel_B2.zip - 5.85 MB
New Kernel
inside 9-5-13_updater-script.zip you will find updater-script file put it 3D_MaX_ICS.zip Open it with WinRar 7z nvaigate to META-INF\com\google\android and replace it
also 9-5-13_build.rar you will find build .prop replace the one inside 3D_MaX_ICS.zip in the system folder
Click to expand...
Click to collapse
hehe dafcomg
thanx for the rom
i have an error when i try to flash it error status 6
zak53 said:
hehe dafcomg
thanx for the rom
i have an error when i try to flash it error status 6
Click to expand...
Click to collapse
is this after or before replacing updater script
defcomg said:
is this after or before replacing updater script
Click to expand...
Click to collapse
after replacing the updater script
zak53 said:
after replacing the updater script
Click to expand...
Click to collapse
try this one ....
replace the text in updater-script of 3dMax_ICS_Kernel_B2.zip with this
Code:
ui_print("* Installing Kernel");
package_extract_file("boot.img", "/dev/block/mmcblk0p3");
run_program("/sbin/busybox","mount","/system");
show_progress(0.500000, 0);
package_extract_dir("system", "/system");
set_perm(0, 0, 0644, "/system/lib/lge-ril.so");
show_progress(0.200000, 0);
unmount("/system");
ui_print("");
and replace it
defcomg said:
try this one ....
replace the text in updater-script of 3dMax_ICS_Kernel_B2.zip with this
Code:
ui_print("* Installing Kernel");
package_extract_file("boot.img", "/dev/block/mmcblk0p3");
run_program("/sbin/busybox","mount","/system");
show_progress(0.500000, 0);
package_extract_dir("system", "/system");
set_perm(0, 0, 0644, "/system/lib/lge-ril.so");
show_progress(0.200000, 0);
unmount("/system");
ui_print("");
and replace it
Click to expand...
Click to collapse
I installed the rom and kernel B1 without changing the updater script
the phone stays on the LG logo
help dafcomg
i will try it, but download link is death