Related
WARNING KNOW WHAT YOU ARE DOING BEFORE ATTEMPTING THIS, IF YOU DON'T UNDERSTAND WHAT IS BEING TALKED ABOUT HERE YOUR BEST TO LEAVE IT ALONE
This is a Vibrant kernel/recovery image that includes EXT2/3/4 support as well as init.d support for user scripts. Everything works as expected Wifi/GPS/BT etc
This eliminates the race condition as the scripts in init.d run before the default Android services.
You can add any user scripts you want by adding them to the /system/etc/init.d folder e.g "05userscript" They are parsed by order 00 then 01 then 02 etc
BEFORE FLASHING THE KERNEL You must flash the init.d update to add the needed folder and files to boot with this kernel. That is because the completion script sets a prop value telling the default Android services to run. If that prop isn't set you will be sitting at the Vibrant screen forever.
The new init.d updates remove any other versions of busybox and install the correct version and symlinks to take care or the issues people have been having with multiple BB installs. There is a version that has no data to SD script for those that want to run other lag fix's. And then there is one with the data to SD script.
Default CPU frequencies and Overclocked versions available.
OCv4
Clock Drift fixed
Fix scaling bug, performance level was set past end of table on sleep
Scaling enhancement, selectable clock source for GPU
GPU clocked at 222MHz for all speeds except 100MHz, where it matches CPU clock
more up/down threshold changes
Wake Lag improvements
Switched back to "CFQ" for perf reasons over deadline and no-op
BB symlinks removed from ramdisk (to avoid conflict with mods that make their own links to BB)
OCv3
NO MORE WAKE LAG!!!!
Reverted back to OC on boot
up/down threshold adjustments again
rebuilt with crosstool-ng 1.8.0 gcc 4.3.4
OCv2
Extra steps are back. [100/200/400/600/800/1000/1200] YOU MUST use setCPU to up it to 1.2Ghz it is set at 1Ghz default for stability reasons,this CPU is very sensitive to voltage/freq changes. Should be more stable overall then prev build. (Thanks Unhelpful)
up/down threshold adjustments
SCv9
No More WAKE LAG!!
Uncommented FM Radio module in init.rc
SCv8
Conservative/Deadline
SCv7
Ondemand/Deadline are default now in
SCv6
ADB issue resolved.
Busybox issues resolved. Can now update through stericson's BB utility from the market.
OC version available with extra 600mhz and 1200mhz step added (you still have 800, 1000 etc) Linpacks in the 10.0's (Thanks to ivanmmj for the help)
SCv5
Volume rocker fixed
cleaned up RAMDISK
reverted to stock recovery (rev1 had clockwork as the recovery but was having a few issues)
added symlinks for busybox applets
Fully compatible with Clockwork (backups/restore from ROM manager) (no more annoying reboot before Clockwork starts)
INSTRUCTIONS
Note:The new init.d updates install BusyBox for you and create the symlinks. They also remove any other prior version before doing so
1.Choose one of the init.d updates that suites you.
A.
Data and Dalvik init.d-busybox with data to SD update.zip
MD5:0317ae432d2db15e51fd0da2c4d53857
B.
Data and Dalvik init.d-busybox without any lagfix scripts update.zip
MD5:9e720b587188676e7fff2f144433bd23
2.Reboot into recovery and flash this. Once booted check your system/etc dir for the init.d folder and scripts inside before moving forward. If they are there we move on.
3.Download the kernel/recovery image
OCv4 1.2 No Wake Lag/No Time drift
Update.zip (flash through clockwork recovery)
www.justanotherdev.slackdev.com/Kernel-Vibrant-OCv4.zip
MD5:33487d4bec50d123d0bb10843d141723
ODIN Image
www.justanotherdev.slackdev.com/kernel-vibrant-OCv4.tar
MD5:5aae7e5ab08227e1fd4c931c24f678ac
OCv3 1.2 No Wake Lag
kernel-vibrant-OCv3-NG.tar
MD5:1e2ddb9bd9fe4adb0ccc73fa818c63be
OCv2 1.2Ghz with extra steps back in. More aggressive up/down thresholds
kernel-vibrant-oc-ng.tar
BETA OC 1.2Ghz (no added steps for now)
kernel-vibext4-oc1.tar.md5
MD5:d1e26f769406c5d368492855c7b5059e
SCv9 No Wake Lag
kernel-vibrant-SCv9-NG.tar
MD5:0614a8205087a84fe34bbe2c653183a9
SCv8
kernel-vibext4-8.tar.md5
MD5:e9c2a45d89d994c485b8af8e1b1a923c
SCv7
kernel-vibext4-7.tar.md5
MD5:cedbad0273a2dd2a1b2d0a4ed3e89fce
4.Reboot into download mode and use ODIN to flash the kernel. Use the CSC field with no PIT file. This will flash the kernel/recovery
NOTE:You can find ODIN in my other thread here
If you have an EXT2/3/4 partition I used tabbals script (to tired and will be re-writing this shortly) for the mean time to bind your data to the EXT partition or otherwise known as the "EXT hack" for those that want those wondering. If you do not want this script you can remove the 07a2sd script from the init.d folder before flashing the kernel.
Now you can add any user scripts you like to the init.d folder and we dont need to use the "playlogos" hack anymore. This is a work in progress and more tweaks/features will be integrated and updated as they are tested and made available in this thread. I had to give you guys something to mess around with. And a proper way to run user scripts.
Thanks to Unhelpful, supercurio, cyanogen, scepterr, wes garner, Eugene_373 and everyone that helps out in the XDA community!
Sources:
Kernel: T959 source from opensource.samsung.com
Voodoo-fix http://github.com/project-voodoo
OC patch posted below
Enjoy!
Need to revert to the stock kernel??
www.justanotherdev.slackdev.com/kernel-vibrant-stock.tar.md5.tar
MD5:9f89f8c5a6c785ff967806a4ca70906f
Beautiful! now if only we can find a way to flash the kernel from recovery without needing odin.....
anomalous3 said:
Beautiful! now if only we can find a way to flash the kernel from recovery without needing odin.....
Click to expand...
Click to collapse
Agreed. Feel free to use this kernel/recovery in your ROMS just give credit and I'll be more than happy
Also more to come folks just sit tight. This is my hobby and I have to take care of some real life issue ATM...cough ...the woman...cough.
amazing job! thanks for helping calm down the xda addicts. how well does the userinit and apps2sd play with kernel, can we use those files or will they have to modified to work with your kernel?
frank707 said:
amazing job! thanks for helping calm down the xda addicts. how well does the userinit and apps2sd play with kernel, can we use those files or will they have to modified to work with your kernel?
Click to expand...
Click to collapse
Any scripts will work fine just as before. The main difference is that we dont need the "playlogo" hack that was used previously which runs a script called userinit from /system/bin/ now all user scripts will go in /system/etc/init.d/
Now we have this folder (init.d) to store all are user scripts in and gives us the option to choose which runs first according to how they are labeled. Just have a peek inside the init.d folder to see what I'm talking about. Init.d is pretty common on Linux boxes just not Android
Also to be clear this should clear up race conditions as any user scripts in init.d will run before the default Android services.
FYI tabbals scripts is renamed "/system/etc/init.d/07a2sd" (which I should have names d2sd but whatever lol) in this build. Same script so yes the scripts will work just fine
frank707 said:
amazing job! thanks for helping calm down the xda addicts. how well does the userinit and apps2sd play with kernel, can we use those files or will they have to modified to work with your kernel?
Click to expand...
Click to collapse
one of the main purposes of the kernel is to give us a linux-standard place for people to add startup scripts, and to make data2sd possible without trouble, including ext4 which combines most of the speed of ext2 with the stability of ext3.
anomalous3 said:
one of the main purposes of the kernel is to give us a linux-standard place for people to add startup scripts, and to make data2sd possible without trouble, including ext4 which combines most of the speed of ext2 with the stability of ext3.
Click to expand...
Click to collapse
Exactly.
Have fun I'm off to bed for now. I've been running this for 2 days without issues. Please let me know if you find any bugs. WiFi BT and everything else should be working just like the stock kernel I also haven't had one kernel panic yet.
justanothercrowd said:
FYI tabbals scripts is renamed "/system/etc/init.d/07a2sd" in this build. Same script so yes the scripts will work just fine
Click to expand...
Click to collapse
can't wait till take takes off. So is tabbal's script already setup to run automatically as long as i have my ext partition setup?
Im definately +1 for getting rid of odin, Jac do you use github at all ?
frank707 said:
can't wait till take takes off. So is tabbal's script already setup to run automatically as long as i have my ext partition setup?
Click to expand...
Click to collapse
This is correct yes.
bbuchacher said:
Im definately +1 for getting rid of odin, Jac do you use github at all ?
Click to expand...
Click to collapse
I use git/mercurial but not github. I will be creating an account their to share code as people have been requesting it
bbuchacher said:
Im definately +1 for getting rid of odin, Jac do you use github at all ?
Click to expand...
Click to collapse
good to see some Super D/E/F power using this phone. Would I be correct in thinking the main problem with packing the kernel into a boot.img would be the offsets, or do you think we're dealing with something a bit more serious?
Would I have to wipe if I flashed this kernal? Or can this be flashed on top of what I have now and not lose anything?
Goog1e Phone said:
Would I have to wipe if I flashed this kernal? Or can this be flashed on top of what I have now and not lose anything?
Click to expand...
Click to collapse
No Wipe is needed. Make sure you flash the update first though it is a REQUIRMENT for it to boot with this kernel.
justanothercrowd said:
No Wipe is needed. Make sure you flash the update first though it is a REQUIRMENT for it to boot with this kernel.
Click to expand...
Click to collapse
attempted to flash the first zip but init.d folder wasn't created. Wouldn't flash through stock recovery, attempted to flash through cw, will try again and update
The follow error occurs on flash
Code:
E:Can't chown/mod system/etc/init.d/02a2sd
(No such file or directory)
E:Failture at line 7:
set_perm 0 1000 0755 SYSTEM:etc/init.d/02a2sd
Installation aborted.
problem is in script, just edited it, about to try to flash
no dice, no install
davbran said:
no dice, no install
Click to expand...
Click to collapse
EDIT: realized my FTP client wasnt uploading in binary mode which caused some issues.
Re-download the files they have been hashed and double checked.
Enjoy!
Hi,
I cannot get root access on my terminal. The following is my configuration:
Froyo 2.2
PC: GT-I9000HKYTIM
PDA: GT-I9000AIJP6
PHONE: GT-I9000XXJPP
CSC: GT-I9000TIMJP4
Recovery : 3e
I installed speedmod k13e, but i cannot enable tweaks, bln and root.
Whenever i enter recovery mod i try to install root (simple) from the speedmod/ulk menu, at the end of the process it says "Done!" but when i reboot titanium backup complains that i do not have root privilegies.
Furthermore when i try to enable tweaks, every tweak i choose prompts "disabled". The same thing happend when i try to turn on BLN.
Any idea?
Thank you for you help.
Mattia.
Check if you actually have the Super User app on your phone.
If you don't have it download busybox from TitaniumBackup.
The Froyo Speedmod is ultrastable so this is quite odd to me.
If neither of this works I think you might have to reflash the kernel.
Hi,
thank you for your reply.
I did not have the superuser app installed and i did not find a way to download busybox from TitaniumBackup.
So i installed both superuser and busybox from the market.
I run superuser, then TitaniumBackup, but it does not start and it does not ask for root privileges.
In the same way i run superuser, then the BusyBox installer, but it does not start and it does not ask for root privileges.
I reflashed SpeedMod, but nothing has changed.
I forgot to say taht my sgs is branded and i did not unbrand it. Other things i should try?
Mattia.
I also tried with SpeedMod k12u and CFRoot 1.2 for JP6.
No progress made: no root privilegies.
I did one small step forward: i managed to correctly install busybox with CFRoot. I've never been able to do it with SpeedMod.
Could it be because the system ROM is full?
Mattia.
aittam said:
I also tried with SpeedMod k12u and CFRoot 1.2 for JP6.
No progress made: no root privilegies.
I did one small step forward: i managed to correctly install busybox with CFRoot. I've never been able to do it with SpeedMod.
Could it be because the system ROM is full?
Mattia.
Click to expand...
Click to collapse
yea I guess your /system probably is full. to change that delete for example google maps (you can just download and install it from the market) from /system/app with root explorer or go into recovery and convert the filesystem the conversion will give you some more free space even if you change back to rfs afterwards
I did it using ADB Shell.
From the shell both su and busybox worked like a charm.
So eventually i managed to do my backups!
Mattia.
Okay here it goes:
I'm planning on building my own kernel from the lge-sniper-kernel. Basically, what I want to add is just InteractiveX as the default governor for better battery life. I read a lot on the topic and I'm well able to build and inject the kernel. My plans are based on this guide by knzo (dated 4th November 2011): h++p://forum.xda-developers.com/showthread.php?t=1332776
The question now is: Is the lge-sniper-kernel source still compatible with the latest releases of CM7? I'm worried it is not anymore, because the Huexxx-v4 kernel and NOVA kernel are based on the sniper sources and became not compatible with CM7 anymore at some point.
Oh yes and: If I mess up the kernel build and flash it, can I still access S/W download mode or is the phone bricked beyond recovery?
boype said:
Okay here it goes:
I'm planning on building my own kernel from the lge-sniper-kernel. Basically, what I want to add is just InteractiveX as the default governor for better battery life. I read a lot on the topic and I'm well able to build and inject the kernel. My plans are based on this guide by knzo (dated 4th November 2011): h++p://forum.xda-developers.com/showthread.php?t=1332776
The question now is: Is the lge-sniper-kernel source still compatible with the latest releases of CM7? I'm worried it is not anymore, because the Huexxx-v4 kernel and NOVA kernel are based on the sniper sources and became not compatible with CM7 anymore at some point.
Oh yes and: If I mess up the kernel build and flash it, can I still access S/W download mode or is the phone bricked beyond recovery?
Click to expand...
Click to collapse
The CM7 has the lge-sniper-kernel. The NOVA kernel and Huexxx-v4 kernel wasn't updated. Huexxx updated his kernel to 4.1, he just update with the latest commits, and then it worked.
The part of you messing up, I think if you do a nandroid you can easily restore everything. Since when you update to the latest nightly for an example, the kernel is substitute for the default one, I think you wont have any problem. Just flash over a nightly or the RC version and you will be ok, I think.
I'm not a dev and I don't did this test, it just my assumption.
Sniper is the cm7 kernel so its supposed to work on cm, but huexxx kernel 4.1 is also compiled from source and has interactivex governor, and your phone will still access download if you do something wrong.
FDN
Yeah, you can use Huexxx kernel. This kernel has InteractiveX and other things...
dcop7 said:
Yeah, you can use Huexxx kernel. This kernel has InteractiveX and other things...
Click to expand...
Click to collapse
I can't use Huexxx-4.1 with a non-default governor: Whenever I choose InteractiveX (or any other non-default kernel) and set it to load on boot, the phone is incredibly laggy and slow after reboot. This is why I want to build the kernel myself with interactiveX as default, hoping it won't be laggy.
boype said:
I can't use Huexxx-4.1 with a non-default governor: Whenever I choose InteractiveX (or any other non-default kernel) and set it to load on boot, the phone is incredibly laggy and slow after reboot. This is why I want to build the kernel myself with interactiveX as default, hoping it won't be laggy.
Click to expand...
Click to collapse
It is laggy only in the first minutes. And I think with an init.d script you can make interactiveX default governor, but I don't know if it will be laggy also
---------- Post added at 10:08 AM ---------- Previous post was at 10:05 AM ----------
I think if you use this command you will be able to change the governor:
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
In your case, it will be something like this:
echo interactiveX > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Create a blank file with this name: "77governor" or something and put this lines
#!/system/bin/sh
echo interactivex > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Copy that file to system/etc/init.d and then reboot. Check if in this way it will be laggy
But do a nandroid first! I didn't test this!!
@dcop7
Not work with init.d script
You must use ROM Toolbox app (or similar), there is an option to make script at boot in scripter menu
slurpdroid said:
@dcop7
Not work with init.d script
You must use ROM Toolbox app (or similar), there is an option to make script at boot in scripter menu
Click to expand...
Click to collapse
Thanks, I didn't know that.
I only used init.d scripts to change other values...
I need to report back here, hoping anyone of you (previously very helpful) guys has a solution to another problem that came up: After injecting my kernel, the phone just gets stuck at the initial LG boot logo (the buttons do not even start flashing). I am able to run S/W update mode to recover though.
I followed knzo's indicated guide to build my own kernel (h++p://forum.xda-developers.com/showthread.php?t=1332776):
1) I installed all needed linux packages
2) cloned the lge-sniper-kernel from github
3) made the '.config' via the command 'make ARCH=arm cyanogenmod_hub_defconfig'
4) built the /arch/arm/boot/zImage successfully with the command 'make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -j2'. No *.ko files were generated.
5) copied the zImage to aprold's kernel injector zip file from h++p://forum.xda-developers.com/showthread.php?t=1350679
6) flashed the zip via CWM (after doing wipe cache and wipe dalvik).
On a sidenote: I did not even alter anything within the kernel-source, since I first wanted to check out whether I am able to build and flash a kernel in the first place.
Did I do anything wrong or did I forget something? Thanks for your help in advance.
Sorry for doublepost. I solved my problem by using another toolchain.
Just today i downloaded the latest cyanogenmod 9 and even 10 ....their is very large vibration whenever i press a key...and i want dat vibration.....so how can i decrease the vibration intensity / sensitivity
Download latest Devil Kernel (ICS Kernel for Cm9 or JB Kernel for Cm10)
There are two or more possible ways:
1)
Download latest Devil Manager or Devil app
- start one of them and grant SU rights
- look for vibratorintensy and change it
done
2) Reboot into Recovery
- go to DEVIL
- got to Misc Menu
- change VibratorIntensy
done
vibration remove
jogibush said:
Download latest Devil Kernel (ICS Kernel for Cm9 or JB Kernel for Cm10)
There are two or more possible ways:
1)
Download latest Devil Manager or Devil app
- start one of them and grant SU rights
- look for vibratorintensy and change it
done
2) Reboot into Recovery
- go to DEVIL
- got to Misc Menu
- change VibratorIntensy
done
Click to expand...
Click to collapse
is there any way to completely remove vibration...devil app decrease the intensity and still there is somewhat vibration...which may cause eating battery,,,plzzz
Sure just go to
- settings
- sound
- scroll down and disable vibrate on touch
Sent from my GT-I9000 using Tapatalk 2
Anyone know where the settings are in the root folders for this? used to be in /sys/class/timed_output/vibrator/duty, but seems to have moved since CM10/JB
[ROM][Stock][ICS]LG P990 v28g Stock ICS flashable zip by harsh & tonyp [DISCONTINUED]
LG P990 Stock ICS flashable zip [DISCONTINUED]
This ROM is discontinued.
If you're looking for a stable ROM I recommend this ROM as an alternative: ParanoidAndroid CM10
It's more up-to-date and smoother than Stock ROMs - but at the same time still rock stable and qualifies as a daily driver.
If you want to continue using a Stock ROM on the GB bootloader I'd recommend to use the updated and actively maintained v30a/b Stock ROM by rugglez.
Some of the work of this ROM went into it - especially the heavily reworked ramdisk.
Using this ROM with the kowalski oldbl kernel does work as well (and fixes the callbug).
I've never intended to support a Stock ROM in the long term - I prefer CM based ROMs by far.
The initial intention of the first version of this ROM was to provide an easy way for people to test the SU660 leaks - back when we didn't even have P990 ICS leaks.
Nowadays that's easy, thanks to tools like the AIO toolbox by spyrosk, but back then it was more complicated for the users - especially with a SU660 ROM as base.
Then harsh & I decided to work on it together and update the initial SU660 base to a P990 v28 one.
A big thanks to harsh with whom I've been working closely together.
What is this?
This is a flashable zip version of the official LG v28g ROM by LG.
It's a Stock LG Android 4.0.4 ROM which uses the default ("old") bootloader and stock ("old") partition layout.
I prefer to stick with the GB layout and old bootloader as pretty much all ROMs, including CM10, are build for that.
If you have used the NVFlash ICS ROM you need to go back to the GB partition layout.
There are two versions. The standard version will fit into the stock GB partition layout.
To make it fit in there we had to remove some apps, including LGEmail, LG Calendar, LGMemo (QuickMemo is still there, don't worry) etc.
If you want to have the full ROM you can use the extended version, but need to increase the /system partition size to 512mb+ beforehand (see here for instructions).
Note that by only changing the partition size the partition layout won't change - so you still can flash other ROMs like CM10.
What's working?
This ROM is considered stable. harsh and I are using it as a daily driver currently!
Full hardware accelleration including:
Working Videocamera
Google Chrome
Videodecoding
etc.
In-call audio
Playstore
LG UI 3.0 & LG 4x lockscreen (THE MOST demanded feature in every dev thread )
Bluetooth
2G/3G
FM Radio
Everything else you can expect from a stable ROM (data, wifi, sms etc.)
What's not working?
slow charging on usb computer connection. Wall charger does work.
Workaround: Power off phone, attach usb cable, boot.
Screenshots (Power + Vol down) are empty. Just use Quickmemo (Vol up + down).
LG Application Manager not fully working and thus not included
The call issue of CM10 ROMs is present for some people.
If you reboot the phone once a day (e.g. at the morning) it usually won't occur during the whole day.
Credits:
Besides harsh thanks (especially for the old versions) to the following people:
(alphabetical order)
Someone missing? PM me asap!
aremcee
bihariel
ergoen
Kostja_V
wkpark
Due to the continuous misunderstanding: This ROM requires you to run the GB (aka the "old") bootloader and partition layout.
If you flashed a ICS ROM (kdz etc.) with NVFlash you need to go back to the old layout and bootloader, for example with this tool:
[TOOL] Full Brick Repair (Clean & Easy)http://forum.xda-developers.com/showthread.php?t=1975274
If you're coming from CM7, CM10, PA, GB (Android 2.3) Stock ROMs etc. this warning does not affect you.
Note:
I fixed the error which required you to use CWM 5.0.2.x for this ROM so you can now use any recovery you want now.
I'd recommend the official CWM 6.0.1.5 Touch or the newest TWRP.
How to install the new CWM:
You can use the ROM Manager to install CWM. But you need ROM Manager premium (or an in-app purchase for ~2$) to be able to flash CWM Touch with it.
You can use this flashable zip to install CWM 6.0.1.5 Touch easily: http://forum.xda-developers.com/showpost.php?p=34263577&postcount=1083
You can use my freshly zipped NVFlash CWM6 touch Recovery flasher (based on Rusty!'s method):
http://goo.im/devs/tonyp/P990-stuff/various/CWM6.0.1.5 touch NVFlash-tonyp.zip
Remove battery, hold both Vol - & Vol +, connect the phone to your notebook and use the "install_cwm6.bat" file (or the matching linux sh install script). APX driver is included.
This will flash CWM without touching any other partition.
Installation (follow carefully!):
Read post 1 and post 2 completely before you're doing anything with your phone!
If it doesn't exist, yet: Create the folder "external_sd" on your internal sdcard.
Reboot once.
Reboot into your recovery.
If you are coming from another ROM than my Stock ICS:
wipe data/factory reset(!)
Install zip from sdcard (flash the ROM)
Reboot (can take a couple minutes)
After fully booting up and going through the setup wizard: Restart your phone once again
Don't touch the RIL! And don't mind the "Unknown baseband" if everything works. This just means you got one of the older basebands which aren't displayed properly anymore. Nothing to worry about.
If automatic time if off you can either flash the v28g baseband (see my stickyied thread) or disable automatic time and use ClockSync.
Download:
standard version (fits into GB's /system partition):
http://goo.im/devs/tonyp/P990-stuff/ICS
extended version ("full" version requires /system of 512+ mb):
http://d-h.st/CVb
Changelog:
Code:
[u]version 3.01[/u]
[LIST]
[*]build.prop lines added to identify it as P990 device in the ROM Manager
[/LIST]
[u]version 3.0[/u]
[LIST]
[*]updated to v28g
[*]CWM Encryption error fixed (you can use any recovery now)
[*]kernel updated. fixes the bluescreen issue and some bugs & memory leaks
[/LIST]
[u]version 2.0[/u]
[LIST]
[*]complete new version based on the v28e leak
[*]no more korean SU660 files, pretty much all bugs are fixed
[*]thanks to harsh who build this version!
[/LIST]
[u]version 0.98[/u]
[LIST]
[*]bsod on screen off fixed (thx arcee!)
[*]huge update to the updater-script
[*]now pre-rooted
[*]Playstore updated
[*]Stock Messaging app replaces LG's one
[*]added Stock LG Browser
[*]added LGAlarm
[*]removed Google TTS
[/LIST]
[u]version 0.81[/u]
[LIST]
[*]typo fix in the updater-script
[/LIST]
[U]version 0.8[/U]
[LIST]
[*]initial release
[*]A mix between the final SU660 v30c ROM and the P990 ICS leak
[*]custom kernel to let it boot with the old bootloader
[/LIST]
Old installation instructions for versions prior to 3.0 (which was way more complex):
Installation (follow carefully!):
Read post 1 and post 2 completely before you're doing anything with your phone!
Create the folder "external_sd" on your internal sdcard.
You need to use ClockWorkMod 5.0.2.x
TWRP & CWM 6.x will result in encryption errors (something to investigate later)
use e.g. RomManager, scroll to the bottom, choose "older recoveries" and install 5.0.2.0
Backup your current ROM
wipe data/factory reset
mounts and storage - format /system
Install zip from sdcard (flash the ROM)
remove the usb cable from the mobile phone!
(if you boot with the phone connected to your PC the PC will either freeze or show you a bluescreen!)
Reboot (can take a couple minutes)
After the setup wizard go to Settings - Connectivity and change the USB connection type to MTP
(now you can attach the phone back to your PC).
Restart your phone
Don't touch the RIL! And don't mind the "Unknown baseband" if everything works. This just means you got an older baseband which aren't displayed properly.
If automatic time if off you can either flash the v28e baseband or disable automatic time and use ClockSync.
Thanks man.
i'll try this and feedback later
thx i'm test:good:
Thanks man. I'll try whether the USSD code is usable or not. This is important for a prepaid user like me.
Sent from my LG-P990 using xda app-developers app
yeah baby
tonyp said:
It's possible that in-call audio is not working! It's too late to call someone to test it.
Click to expand...
Click to collapse
downloading now, will flash and call myself (landline) and report back
I get almost 40kb/s so I think it's gonna be a while
Thank u. Will try
Sent from my LG-P990 using xda app-developers app
flashing...
Damnit, I had it at the USB cable the whole time. I just realized the ROM will bsod when going into deep sleep.
This is a kernel issue due to the GB bootloader.
So this is mainly a "let's check out how ICS works" ROM at the moment
Doesn't deserve an own thread. I can't yet close my own thread, will have to ask a mod about it.
no go then
will check tomorrow for any news
dont worry, you did a amazing job by make it flashable
go get some sleep you deserve it and thanks you again for your hard work :good: :fingers-crossed:
unkown function "uassert"
I wanted to try this anyways(despite the BSOD issue). Installation aborted with (Status 6). Logs show
Code:
line 1 col 89: unknown function "uassert"
1 parse errors
I wiped data and was on CM9 PA rom before. Tried toggling script asserts in recovery but same results.
Let me know if I am missing something? [busybox maybe?]
Edit: Maybe this is a recovery issue, I am on 5.0.2.7, but never had this issue before with any other roms.
Fix: Just use the 0.81 build or modify the update-script as described in the post below.
Aj264 said:
I wanted to try this anyways(despite the BSOD issue). Installation aborted with (Status 6). Logs show
Code:
line 1 col 89: unknown function "uassert"
1 parse errors
I wiped data and was on CM9 PA rom before. Tried toggling script asserts in recovery but same results.
Let me know if I am missing something? [busybox maybe?]
Click to expand...
Click to collapse
This is a simple mistake I made resulting of me being tired.
I did some last minute modifications of the update-script file (to ensure no P999 or SU660 users try and install it) and unfortunately wrote uassert instead of assert.
You can either fix it yourself: Goto META-INF/com/google/android/updater-script and remove the first character (the "u").
Or download v0.81.
goo.im is a great hosting service and offers me remote ssh access via a linux terminal - so I just unzipped the ROM, fixed the line and rezipped it as v0.81. No need to re-upload
Please reply if it works.
v0.81 of this rom is release i didn't even finish to download the first build and another build is uploaded thanks tonyp download speed is 40kbps so it take a while to test it
Tonyp is one of my favourite guy, there is a reason behind and thats he is simply amazing!
Thank u man. Now ppl can flash it w/o worries and fear
Sent from my LG-P990 using Tapatalk 2
grimmyrippy said:
v0.81 of this rom is release i didn't even finish to download the first build and another build is uploaded thanks tonyp download speed is 40kbps so it take a while to test it
Click to expand...
Click to collapse
Oh, goo.im slow again. A couple hours ago I had full speed.
If someone wants to provide a mirror feel free to do so, I'm out now really.
The v0.81 zip is untested, I hope it works the way I did the change remotely. If it doesn't use 0.80 and apply the manual fix I posted in my last post.
Open the updater-script with a texteditor like Notepad++.
Use build 0.81
tonyp said:
This is a simple mistake I made resulting of me being tired.
I did some last minute modifications of the update-script file (to ensure no P999 or SU660 users try and install it) and unfortunately wrote uassert instead of assert.
You can either fix it yourself: Goto META-INF/com/google/android/updater-script and remove the first character (the "u").
Or download v0.81.
goo.im is a great hosting service and offers me remote ssh access via a linux terminal - so I just unzipped the ROM, fixed the line and rezipped it as v0.81. No need to re-upload
Please reply if it works.
Click to expand...
Click to collapse
thanx, i'll modify the update script and try. I also thought it should be assert but refrained on commenting lest you had defined your own macro.
Thank you for your hard work. :good:
Edit: Can confirm that modifying updater-script manually works. Using stock ICS now. Cheers.
Somebody who has installed it, could try running playing song through music player before screen lock?
Does music/song keep playing continuesly after screen locks and after 2-3 mins does the phone wakeup by pressing unlock key or still BSOD?
Definately unplug usb cable before doing this
Sent from my LG-P990 using Tapatalk 2