Onyx is simply a TouchWiz Free version of Obsidian. The changelog is listed there, in addition to those changes the following have been made.
Will make flashable nonwiping updates available until all the bugs are worked out and cleared. Once they are the newer and stable revision will be posted with complete skinning in two seperate versions. Please make requests for feature changes and things you would like removed.
4.2
- Added inharent support for Backlight Notification compatible kernels (BLN)
- Optimized Build Prop with ROM Identification Added
- Streamlined Frameworks
- Numerous Corrected Images
- Return of TouchWiz MMS w/ Blurry mms Fix
- Integrated WirelessADB
- Additional I/O scheduler, VM management, kernel scheduler, and minfree edits via sombionixInit script
- Integrated Flashing with Universal Lag Fix system. (Source by sztupy @ XDA, Ported by Krylon360 @ TeamWhiskey)
Team Whiskey Universal LagFix Kernel Features
- All lagfixes and tweaks activated directly within clockwork advanced menu
- MULTIPLE lagfix options, new and old
- Integrated TW logo
- 3e recovery built into kernel
- No longer required to disable lagfixes before flashing
- Enable/disable back light notifications
- Option to switch to 2e recovery
- Option to install Superuser
- Enable/disable I/O scheduler tweaks
- Enable/disable VM management tweaks
- Enable/disable kernel scheduler tweaks
- Enable/disable misc. tweaks
- Reboot into download mode
How To Utilize Universal LagFix Kernel:
1. Flash ROM as you normally would via clockwork recovery
2. Let device boot and then reboot back into clockwork recovery
3. Once in recovery, you will now see 2 new options at the bottom
4. Within the new menus, you will find options to enable/disable certain features and an assortment of lagfixes
5. Enabling/disabling features and tweaks are fairly self explanatory, so have fun with those.
6. Lagfixes are also fairly simple, however, if you are not extremely familiar with them, I suggest sticking to what you know such as the OCLF or voodoo options
7. Once you select the lagfix you want, you will see that your current configuration is updated. You must then go back and select reboot.
8. It will kick you back into clockwork very quickly and give you options before converting your partitions to your selected lagfix. I suggest you pick the first one which creates a backup and restore of your system.
9. Your device will now convert your partition, reboot your phone, and you're done!
Known Issues:
PLEASE READ PLEASE READ PLEASE READ PLEASE READ
- Currently, there is a VERY small percentage of users who have reported that their internal sd partition has been wiped. This is happening to roughly 1/20 people who flash 4.2 with the universal lag fix. If this happens, you will have to odin back to JFD and then upgrade back to 4.2 or any version of your choice. The kernel works very well, however, this is the first time this source and recovery modding has been ported to the Vibrant. None of my dev team has had this happen to any of us so we unfortunately cannot reproduce the problem and pinpoint the problem. We are thinking its hardware related at the moment. Please flash this at your own risk. If it does work for you, you'll love it, trust me! If you're one of the unfortunate ones that gets your internal wiped, well, I apologize, but you've been warned. I suggest ONLY experienced users download the rom with the ULF included. All others should download 4.2 w/stock kernel. THIS IS A KERNEL RELATED ISSUE, NOT ROM RELATED!
Update:
For those VERY VERY few unfortunate people who get their internal sdcard partition wiped, we have confirmation that using odin, going back to JFD, then back to Obsidian/Onyx 4.2 works fine. Everyone that has done this has had no further issues regarding the wipe issue.
3.1
-Even MORE framework edits
-tamed dragons
-now prints money
3.0
-Additional Framework Edits
-Beginning of a complete graphical overhaul
-Reskinned DialerTab Functions
2.2
-Fixes Mounting
2.1
-Corrected several improper strings
-Repaired twframework and framework
-removed power menu
R2.1 fixes a few issues, random dropping into airplane mode, crash when using the power button, repeat mms notifications, and more.
2.0
-TouchWiz Disabled and removed
-Standard LauncherPro installation w/ Fusion Skinning
-Reskinned to include Onyx button bar and status bar
All the other changes that were listed in R1 in beta were combined with Obsidian to make one big pile of awesome.
Reverting back to previous iteration, it was running clean and bugfree. Does not have the same stability previous Rev did. Took those peices and reintegrated into R2+
Removed some edits, much more stable now. I KNOW How you hate flashing updates, I promise I will try to make this the last major flashing update for a very long time. Its stable and perfect as far as I can see other than the known mounting issue. Enjoy!
Additional Option Flashes:
If you REALLY like the samsung apps I removed flash this - http://teamwhiskey.com/bin/onyx/FlashPa ... gExtra.zip
If you REALLY liked the WiFi calling and need it back, even if it slows your phone down, constantly, even in the background - http://teamwhiskey.com/bin/onyx/FlashPa ... alling.zip
OCLF/Voodoo Displaced, not removed.
To enable your new box of awesome, you will first need to reboot back into recovery. You will notice this is slightly different from your standard recovery. I will keep this as brief as I can and to the point. You can do any combination you want of lagfix, from simple bind to overkill mode and replace the entire FS to JFS + EXT2 Binds. This is totally at your discretion.
Personally, I enabled EVERYTHING and activated the most OVERKILL mode I could, because I like things over the top lol.
Its fast, wicked fast, its like fast took meth and kicked not so fast in the face in a single springboard motion to be faster.
Reboot to Recovery
Go to the Advanced menu below CWM
Set tweaks and options as you want to, I turned on Backlight Notifications and all the tweaks personally
After that, go to the LAGFIX section and shop for your weapon of choice, pick whichever you want. (Understand that converting data is a dragon in disguise, like a shoplifter in a cage inside an ATM that he COULD BREAK FREE from. Use at your own discretion.)
Reboot
Allow it to convert, could take a long time. Get a snack. Watch Hulu.
Once it boots, its done, reboot after about 15 or 20 for good measure and extra flavor.
Restore your data, dont restore EVERYTHING from Titanium Backup if youre coming from an Eclair build, single select restore your apps and their data. Otherwise Titanium Backup tries to make you some Froyeclair in a blender.
Backlight notifications are awesome, use them.
IF YOU ARE A BATTERY MONGER AND HATE IF YOUR BATTERY DOESNT LAST FOURTYSEVENTYTEEN Hours. Flash the stock kernel, otherwise you will get an average of 10-14 hours with this kernel.
Download:
Onyx 4.2 w/stock kernel
ULF Removed for Stability Issues in flashing
If you are one of the ones that had serious issues with ULF properly flashing we are very sorry that you are having those issues. We have pulled the ULF kernel due to its inconsistant flashing and are moving forwards with a few different concepts. If you are still having issues with this kernel and going back to normal please visit Sombionix or Viralblack in the TeamWhiskey IRC channel.
NEW internal/external mounting fix - after flashing, reboot phone and computer
Download Rom Extras:
Rom Extras
Thank you, this Rom rocks!!!!
Question: The USB debug mode enables itself everything the phone reboots. Is it supposed to be this way?
Thanks again for a awesome rom
Wait 10-14 hours of battery with this kernel? i know the features are awesome but that seems pretty bad. is that 10-14 hours with normal use or just chilling? cause moderate to heavy use and 12 hours doesnt seem so bad.
Awesome rom. Love it as usual.
I was one of the unfortune that got their SD wiped, but I made a bakup.
I flashed froyo via Odin, then reflashed Onyx v4. Works like awesome sause.
Not sure what caused this, Onyx or the overkill JS lagfix, but when I mount my internal/external sd card, the external shows up as a cdrom drive. The internal one is fine.
Can you please make a version with stock kernel
Sent from my SGH-T959 using XDA App
theres a version for stock on the TW website. It was there when i downloaded this at 803 am EST
whats up with this new stuff? i selected the very bottom option in the tweaks for the JS overkill? is this JFS thing the new hotness? i dunno which to pick. i want this thing to be as epicly cracked out as i can make it. can you doo voodoo WITH this new thing or is it one or the other?
right now im sitting at 1406 quadrant and all i did was select that option
aeok18109 said:
theres a version for stock on the TW website. It was there when i downloaded this at 803 am EST
Click to expand...
Click to collapse
Correct, their website shows:
"SECOND FLASHABLE STOCK KERNEL, use if you dont want to risk dragons."
aeok18109 said:
theres a version for stock on the TW website. It was there when i downloaded this at 803 am EST
whats up with this new stuff? i selected the very bottom option in the tweaks for the JS overkill? is this JFS thing the new hotness? i dunno which to pick. i want this thing to be as epicly cracked out as i can make it. can you doo voodoo WITH this new thing or is it one or the other?
right now im sitting at 1406 quadrant and all i did was select that option
Click to expand...
Click to collapse
W/ voodoo it's either one or the other.
JFS = Journaled File System or JFS is a 64-bit journaling filesystem created by IBM.
RFS = Remote file sharing - essentially this is what Samsung originally went with and it's slow.
Viralblack said:
OCLF/Voodoo Displaced, not removed.
To enable your new box of awesome, you will first need to reboot back into recovery. You will notice this is slightly different from your standard recovery. I will keep this as brief as I can and to the point. You can do any combination you want of lagfix, from simple bind to overkill mode and replace the entire FS to JFS + EXT2 Binds. This is totally at your discretion.
Personally, I enabled EVERYTHING and activated the most OVERKILL mode I could, because I like things over the top lol.
Its fast, wicked fast, its like fast took meth and kicked not so fast in the face in a single springboard motion to be faster.
Click to expand...
Click to collapse
Quadrant scores aren't everything, if it feels fast, looks fast. It's fast.
oh yea i know. i personally could give a rats dong about Quadrant scores. This thing is pretty fast. i just posted it for reference. you know SOMEONE is gonna ask lol
Awesome, this is legit, had It since yesterday!
Sent from the speed demon
Okay, I was running the Macnut ROM (Eugene's ROM) and, having tried Onyx from the first beta, I decided to go back. I installed from CWM with no issues (no Internal SD wipe, etc.), let it sit for a bit then went into recovery to do the ULF. I didn't know what to choose but, I ain't afraid o' no ****in' dragons so, I chose the bottom most option for the works. After letting it sit for about 15 mins again and a Titanium restore of my apps, this thing screams. After a fresh reboot, I got 1852 on Quadrant and there is absolutely no lag on this thing. NONE. The only slight beef I have with this rom is that I miss the completely black Swype keyboard.
Stock Kernel
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
1. How do you use the WirelessADB??
2. What is Backlight Notifications?
miikey_ said:
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
Click to expand...
Click to collapse
it means flash the R4 zip in CWM, then flash the stock kernel in CWM WITHOUT REBOOTING IN BETWEEN.
fearless1964 said:
1. How do you use the WirelessADB??
2. What is Backlight Notifications?
Click to expand...
Click to collapse
it makes the 4 android keys at the bottom light up when you have notifications... awesome for those of us who came from phones like the Nexus One that had a notification LED and miss it like woah
miikey_ said:
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
Click to expand...
Click to collapse
flash one, then flash the kernel right after before rebooting into the rom for the first time. My issue is the stock kernel dl link is dead =\
miikey_ said:
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
Click to expand...
Click to collapse
flash the R4 zip then flash the stock kernel without booting the device in between
rsfaze said:
flash one, then flash the kernel right after before rebooting into the rom for the first time. My issue is the stock kernel dl link is dead =\
Click to expand...
Click to collapse
Here it is. One stock Kernel, enjoy.
how do u use WirelessADB???
fearless1964 said:
how do u use WirelessADB???
Click to expand...
Click to collapse
ADB functions without a wire (USB cable)
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!
Peach Sunrise is the first custom ROM for the Samsung Galaxy Exhibit. Based on stock UVLG3, it's deodexed, zipaligned, rooted, very lightly themed and uses a custom kernel. A CWM-based Recovery is required for installation. The industry spyware program Carrier IQ has been removed. This ROM is based on Samsung stock UVLG3 and is NOT vulnerable to USSD Dialer Attacks!
Everything that works with stock works with Peach Sunrise.
You can swap your internal and external sd storage using the included SwapSD app.
ADW Launcher is default. This launcher is highly themable, with many hundreds of themes (including ICS) downloadable from the Market.
EStrongs FM, Voltage Control, DSPManager and CIFSManager are included in the ROM.
V6 SuperCharger is included.
The stock WallpaperChooser has been modified exposing 30 new Wallpapers from Samsung, previously hidden in the source code!
Extra features include busybox, bash shell, terminal, init.d support, rc.local support, remount script. Additionally, adb now supports root access, allowing you to do things from your command line that were not previously possible.
Video review of the Galaxy Exhibit & Peach Sunrise by TheGeekRedneck
Download Peach Sunrise 3.01 Android 2.3.6 HERE
Download Mirror
Kernel sources
Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. The installation will format your data partition. I suggest Titanium Backup, available in the Market.
2. Download the peach.sunrise zip file & copy to either your internal or external sd card.
3. Install Galaxy Exhibit 4G Custom Recovery (cwm) . If you're already rooted, you may install from the command line, otherwise you may install from Samsung's Recovery. Samsung's recovery only sees the internal SD, so copy the cwm zip there. Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the color Samsung/T-Mobile Exhibit logo.
5. Select ROMwipe. This step is required! You will have problems if you do not install Peach to a clean system.
6. Highlight install zip from sdcard, then press Home.
7. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
8. Highlight the peach.sunrise zip file, then press Home.
After you confirm your choice, installation should take less than three minutes.
Big Thanks to Camcory for his assistance with the extended menu for this release!
Remember to do a Nandroid Backup when you're happy with your setup!
Bloat
Peach Sunrise has been de-bloated, meaning that most of the junk that
T-Mobile/Samsung includes to eat up your phone's storage has been removed.
If you need some of that stuff back, download the bloat file below, it's all in there.
bloat.peach.3.zip
Mirror
======================
As always, you install at your own risk. No guarantees or warranties are made or given. YYMV. Caveat Emptor, etc.
=============================
Attachments
=============================
Default home screen
Photograph: Taken in August, 2011 at New Smyrna Beach, FL with a Nikon D300.
Links & Information
Useful links and information HERE
Galaxy Exhibit 4G discussion HERE
Galaxy Exhibit 4G Wiki HERE
Working/not working list?
joshua.justice said:
Working/not working list?
Click to expand...
Click to collapse
Sure, I'll add something to the OP.
Since the the only difference b/w the Exhibit and Exhibit II is the camera processor, would flashing this rom works on my Exhibit?
Thanks.
Baddude8 said:
Since the the only difference b/w the Exhibit and Exhibit II is the camera processor, would flashing this rom works on my Exhibit?
Thanks.
Click to expand...
Click to collapse
Sorry, I have no idea. I'd guess probably not.
So this is just the Exhibit II's stock ROM debloated? If I already debloated all the stuff I don't need, does this ROM do anything?
dennis96411 said:
So this is just the Exhibit II's stock ROM debloated? If I already debloated all the stuff I don't need, does this ROM do anything?
Click to expand...
Click to collapse
What are you interested in having a ROM do? I've had the phone less than a week, so I'm pleased with this as a start
I like! . Haven't used it yet, but progress is good! Is there anyway you could make the kernel OCable?
THANKS! Great start. To answer your question, I would like to see overclock ability as one thing in a rom.
Thanks for this rom,happy people are working on this
About having custom kernels,will this take a while.....you did this rather quickly
The one thing I always wanted to use was voodoo sound and hope you can incorporate a kernel that supports it in the future
anyways keep up the good work and best of luck
I have to root to put this on my phone
sent from my exhibit 2 greatness
dswaggz said:
I have to root to put this on my phone
sent from my exhibit 2 greatness
Click to expand...
Click to collapse
No. It's already rooted.
So do then do I just flash it with Odin or do I have to do anything special b4 I put it on my phone
sent from my exhibit 2 greatness
dswaggz said:
So do then do I just flash it with Odin or do I have to do anything special b4 I put it on my phone
sent from my exhibit 2 greatness
Click to expand...
Click to collapse
Directions in the first post. It's Odin 4.43 all the way
jocala said:
Peach Sunrise is my first ROM for the Samsung Exhibit II. It's Touchwiz-based, rooted, very lightly themed (wallpaper only) and uses the stock kernel. It's been debloated, but not aggressively so. It also includes the bash shell for console junkies. This release uses Odin (included in the download). Future plans include deodexing and a custom kernel.
Download HERE
Consider this a beta, and use at your own risk. However, everything I've tested works. Calling, texting, camera, wifi,etc. If something is broken, it's probably something that I debloated that needs putting back.
Installation
Use Odin 4.43 or greater. 4.43 included in archive. Have Samsung USB drivers 1.4.8 or greater.
1. Put your Exhibit II into download mode. With power off, press and hold the download volume
button, then the power button. A warning screen about the evils of custom software will display.
Press volume-up and you should be in download mode. The screen has the Android robot in the center of the screen and "Downloading" underneath it.
2. Connect your Exhibit II via usb cable.
3. Click the OPS button, then select Ancora.ops
4. Click the "One Package" checkbox, then press the "One Package" button at the bottom of the Odin screen. Select the file peach.sunrise.tar. No other checkboxes need clicking, no other fields need filling. Press the start button.
The process takes 4-5 minutes to complete using Windows 7 in a virtual machine. Once your phone reboots, you should be done. YYMV.
Screenshot #1: Touchwiz launcher
Screenshot #2: GO Launcher & Beautiful
Home Time/Weather Widget (Not inc. with ROM)
Photograph: Taken in August, 2011 at New Smyrna Beach, FL with a Nikon D40.
Click to expand...
Click to collapse
So I should only have the one package box checked. I should uncheck the ones already checked?
tagzard said:
So I should only have the one package box checked. I should uncheck the ones already checked?
Click to expand...
Click to collapse
I've posted a screenshot above of what your Odin screen should look like prior to pressing start.
The COM port mapping field should be yellow, with a port number filled in.
All checkboxes are checked.
The Reset Time field is pre-filled in with the value 300.
The OPS field is filled in.
The One Package field is filled in.
HTH.
Did I do it right?
I think I did it wrong because once it finished rebooting everything seemed the same. How do I know I have the ROM installed?
tagzard said:
I think I did it wrong because once it finished rebooting everything seemed the same. How do I know I have the ROM installed?
Click to expand...
Click to collapse
Things like this are why we have public betas
You are probably fine. I need to brand the ROM, so it identifies via your settings. Since the Odin process does not format your /data partition when you reboot your home setup WILL look just like like it did, since your /data partition overrides the new default home screen.
If you're rooted at boot the new rom is in place. I'll work out branding in beta 2.
So then do I still have all my data from my I had installed b4 flash
sent from my exhibit 2 greatness
The purpose of this thread is to host a location and continue support for a really neat ext4 mod.
IMPORTANT: If you flash the no data limit mod you need to do it after every update or your data, which won't be lost will be hidden by the contents of the data data partition.
I'm going to keep this brief. The original thread was closed so I wanted to have a new location where everyone can find the files. But this is a new thread for Jermaine151's and my EXT4all mod.
Below is the original thread which already has a lot of useful information:
http://forum.xda-developers.com/showthread.php?t=1315372
Here is where you can find most of if not all the EXT4All files:
http://dinc.does-it.net/EXT4_Mods/
Sorry this thread isn't too organized but I threw one together so people could post on it with their comments.
This mod should work on all AOSP ROMs including ICS ROMs and MIUI. It's been confirmed on CM7 and MIUI but I've also tested on CM9. It should also work on all Sense ROMs and does work on every Sense ROM I've tested. Be sure to flash a newer version of the gingertiny kernel if you use a Sense ROM as the kernel version flashed to add ext4 compatibility is out of date.
V2 Mods with TWRP 2.3+ support and proper support for filesystem tweaks for ROMs that are already set to use ext4 found below:
V2 EXT4All Mods
FAQ
Q. How do I know if the ext4 mod(s) worked?
A. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.
Hey tiny, thanks for opening this btw. Wasn't sure if I should post here or on ur kernal thread but my girls dinc was having the data limit problem so I wiped cache and dalvic, flashed ext4 no data limit normal dalvic then flashed ur newest kernal (3/11 date). And I have been having the hardest time keeping her phone stable. I've tried every governor sav2, interactivex, ondemand, even sa, tried deadline, sio schedulers, even tried raising the voltages to a post u had on ur kernal thread, page 85 or something (wasn't sure if I should set the min and max of the voltages for the same thing, but that's wat I did). But she still says its very unstable. She's running stock+ 3.01 and she DOES have a cheap ebay battery in her phone, not quite sure how much that plays a role in the problem. She's at work right now so I can't pull any logs, but I know ull probably need a logcat? Or I dunno. If u could gimme directions on anything I should post to assist u. And I'm not overclocking at all for the record. On stock kernal she never had any stability issues, uptime of 200 hours+. But urs is definitely snappier and that damned data limit is the main reason y I even switched her over to begin with. Thanks tiny in advanced for everything u do!!!
Sent from my ADR6400L using xda premium
I'd prefer the kernel thread.
And I'll need a last_kmsg. Just copy /proc/last_kmsg with root explorer or another file explorer and attach it to a post on the kernel thread. Since you most likely eliminated undervolting by using the voltages on page 85 of the kernel thread, then it's possible the battery has an effect. I've heard that poorly made batteries can cause issues that stock batteries don't have so further deviation from stock may have an influence. Either way, I'll look at that log once you get it. Make sure not to battery pull until you can copy that log and try to do it within 24 hours of the last reboot to be safe.
the following thread contains very simple and plain english directions for using this MOD. it helped me, and it was my first time rooting. Thanks also to tiny4579 for posting this new thread.
http://forum.xda-developers.com/showthread.php?t=1488351
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
funkpod said:
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
Click to expand...
Click to collapse
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
I've been running various ICS roms and switched back to Warm rev 58. Upon installing the latest kernel and the Ext4 mod. I am unable to install apps. Any idea what may be causing this. I wasn't sure if it was the rom or not do I did an update with SVN and installed that with the same results. I have a nandroid with just the rom and all the apps I want, but would like to overclock and the stock kernel won't allow. And would also like to be able to install a new app should one arise.
Sent from my HTC Droid Incredible using xda premium
tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks, how do I generate the logcat?
Sent from my Incredible.
Aw yeah.
Ok. It's not the kernel. Installed the most recent and everything is fine. Installed the ext4 with dalvik moved before that and rebooted and apps were missing and it wouldn't let me install new apps and some of my previously installed apps were missing. When I tried to install them it said it was going to replace an existing app and then said app not installed.
Any ideas???
Sent from my HTC Droid Incredible using xda premium
tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
funkpod said:
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
Click to expand...
Click to collapse
Sorry I just dont have time tonight to explain. Maybe tomorrow.
Sent from my Galaxy Nexus using Tapatalk 2
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
funkpod said:
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
Click to expand...
Click to collapse
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
funkpod said:
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
Click to expand...
Click to collapse
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Sirknifealot said:
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Click to expand...
Click to collapse
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
funkpod said:
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
Click to expand...
Click to collapse
If you're wiping I don't see the point of fix permissions as it will fix it back to what it already probably is. I haven't fixed permissions in a while flashing ROMs and I've been ok. Force closes that I got that made me try fix permissions then weren't fixable with fix permissions anyway.
I would wipe, flash ROM, flash kernel if desired, then mod. Though if it's a sense ROM I would switch the order of kernel and mod flashing. So really you can do: ROM, ext4all mod, kernel after a wipe if you choose to wipe to fix your issue.
hey, flashed over to RC3! so far so good, slowly adding things back! will let everyone know how it goes!
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
omniatic said:
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
Click to expand...
Click to collapse
No, if you actually format the device like when the system runs the format command the filesystem will be ext4. However in your example of CM9 the ramdisk mounts data and cache as ext4. This will actually have a minor improvement over ext3. It'd still be an ext3 filesystem but loaded as ext4 so there's minimal performance gains.
In reality any time you flash a ROM or a boot.img type kernel (not any of mine) you will use the ramdisk of the ROM and reverse part of the effects. But since ROMs like CM9 and newer CM7 versions mount as ext4 you'll still see data and cache showing as ext4. Make sense? I never really did explain it properly before I think.
SAFESTRAP v3.73 (2nd-System Bootstrap / Recovery)
ATTENTION: I will be stopping official Safestrap support on 9/1/2014. For more information please see:
https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b
** INSERT STANDARD DISCLAIMER: I'm not responsible for any damage you do to your phone using my tools. Always have a fastboot available for disaster recovery. **
Download the APK Installer:
Mirror 1: Goo.im
Mirror 2: Crackflasher
FOLLOW THESE INSTRUCTIONS: How to Safestrap
[ DOUBLE-CHECK you have the "Maserati" version ]
NOTABLE TWRP-BASE CHANGES:
Key/button vibration in recovery and MANY more 2.7 updates
Screen saving in recovery. Can set the timeout under Advanced->Settings->Screen *Don't freak out of the screen is dark, try the power button.*
SElinux support in recovery
and much much more.. check the TWRP changelog here: http://www.teamw.in/project/twrp2
DEVICE SPECIFIC SAFESTRAP CHANGES:
[05/15] (3.73) Bugfix for dual SD card UMS mounting and pull in TWRP changes
[04/14] (3.72) Mostly other device updates
[01/15] (3.71) Code cleanup
[01/15] (3.71) Minor hijack updates
[12/18] (3.70) Mount cleanup during hijack / debugging output
[12/18] (3.70) Splashscreen: Instant stock boot key (needs to be set for Moto OMAP4's still)
[11/13] (3.65) recovery init.rc cleanup
[11/13] (3.65) fix updater build for cm 10.1 and 10.2
[09/20] (3.60) Better handling for virtual images > 2gb
[09/20] (3.60) Much improved block device handling
[09/20] (3.60) Bugfix in script translation
[09/20] (3.60) hijack / init.rc tweaks
[09/06] (3.53) Fixed mass_storage in recovery (via Mount menu)
[09/06] (3.53) Added Webtop to partition backup list (optional)
[09/06] (3.53) New virtual systems created will be 640mb (got reset 600mb)
[09/06] (3.53) Fixed file selector when changing from internal to external storage (previously location wouldn't update)
[09/05] (3.52) added "Reboot to Recovery" in APK
[09/04] (3.51) Disabled screen blank while creating a rom-slot
[09/04] (3.51) Fixed openrecovery script processing for stock slot to re-inject hijack after .zip install (cmupdater on stock now works)
[08/30] (3.50) If running a new CM10.1/CM10.2 ROM (08/30 or later) you *should* be able to install Safestrap and update the recovery w/o having to go back to stock. If Safestrap shows "recovery not installed" while you're on a ROM-slot, then that ROM hasn't been updated and it won't work. Swap back to stock ROM and update Safestrap from there.
[08/30] (3.50) Worked on stock ROM flashing and *should* work with CM10.1/CM10.2 builds on or after 08/30 *WILL NOT WORK WITH OLDER ROMs.*
[08/30] (3.50) Battery meter is back
[08/30] (3.50) Updated TWRP theme
[08/30] (3.50) Added partition sizes to ROM-slot screen when it's ACTIVE
[08/30] (3.50) Added "Check FS" function to ROM-slot screen when it's ACTIVE
[08/30] (3.50) Complete re-write against TWRP 2.6 base (up from version 2.2.2.1): TWRP changelog for reference
[12/29] (3.11) Allow use of custom updater-binary in .zip files for flashing on stock ROM (virtual slots still use prebuilt updater-binary in recovery).
[12/29] (3.11) BUGFIX: Fixed fake flash error at the end of a .zip install. (No real error, .zip installs fine)
[12/29] (3.10) Early support for booting custom ROMs on stock partitions.
[12/29] (3.10) Enable flashing to stock ROM *BE CAREFUL -- NEW FEATURE -- STILL TESTING*
After .zip installations, nandroid restore or system wipe on the stock ROM: the current Safestrap files are restored to the system partition (Doesn't include the APK in /data -- so if you're restoring an old backup, be sure to update the Safestrap APK)
During the Safestrap files restore a check is done to be sure there are minimal files on /system to re-enter Safestrap
[12/29] (3.10) New virtual system partitions will be 640mb (closer match to stock RAZR/D4)
[12/27] (3.07) Bugfix: missed some changes in Safestrap 3.06
[12/26] (3.06) Bugfix/Update for JB4.1 OTA for DroidRAZR (Non-JB devices can also use)
[10/17] (3.05) Fixed SD card / emmc sharing in recovery (UMS)
[10/17] (3.05) Fixed recovery installation/removal from ROM-slots
[10/14] Updated to v3.04 BETA.
[10/14] Recovery is now based off TWRP 2.2.2.1 (fully featured touch-based recovery)
[10/14] Can create up to 4 Virtual ROM-slots to flash ROMs to and when "Active" ALL TWRP functions affect that ROM-slot (For example: Flashing .zips, Backup and Restore)
[10/14] Nearly instant swapping from ROM to ROM
[10/14] User selectable data partition sizes during ROM slot creation: 1GB, 2GB or 3GB
[10/14] ROM slots are saved on the internal emmc space so that preinstall and webtop partitions are no longer used and shouldn't break OTAs.
[10/14] Charging in recovery
[10/14] Supports "Reboot Recovery" from Android OS
Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the menu button, it takes you to Safestrap Recovery.
SPECIAL THANKS TO:
The entire TWRP team who has built an AMAZING recovery system.
The testers which have helped in past and present versions of Safestrap, knowing that it could mean they brick their devices.
As always, let me know what you think!
SCREENSHOTS (showing slightly older TWRP base)
do i need to be rooted?
Sweet. Let the ics based roms begin.
Sent from my DROID4 using Tapatalk
pimpsalot69 said:
do i need to be rooted?
Click to expand...
Click to collapse
Yes. There is no way to get Safestrap installed w/o being rooted.
Tol flash the leak or to not flash the leak
Hashcode,
There seem to be too differing opinions on whether or not it is safe to flash the ICS leak or not. Being the android guru that you are, would you mind weighing in or whether or not this is safe to do? It seems, based on the fact the people are able to go from .200 to .206 that, theoretically, you should be able to use the same method to flash the OTA when it comes out and get back on the upgrade path. What are your thoughts? Thanks!
Just used safestrap 2.0 to do a full system backup. I think the confusing thing about pressing the keys to enter or skip the safestrap menu is the lack of haptic feedback when pressing the menu or search softkeys.
Thanks for your work hashcode. Without you the D4 would be lost.
Sent from my DROID4 using Tapatalk
kwyrt said:
Hashcode,
There seem to be too differing opinions on whether or not it is safe to flash the ICS leak or not. Being the android guru that you are, would you mind weighing in or whether or not this is safe to do? It seems, based on the fact the people are able to go from .200 to .206 that, theoretically, you should be able to use the same method to flash the OTA when it comes out and get back on the upgrade path. What are your thoughts? Thanks!
Click to expand...
Click to collapse
I don't recommend people jump on the ICS leaks just yet. But, if you do and are looking to make backups etc, then Safestrap is probably what you need. Just make sure to do the initial backup of your non-safe system (don't need webtop) so that you can put everything back the way you found it.
bdsullivan said:
Just used safestrap 2.0 to do a full system backup. I think the confusing thing about pressing the keys to enter or skip the safestrap menu is the lack of haptic feedback when pressing the menu or search softkeys.
Thanks for your work hashcode. Without you the D4 would be lost.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Ah the haptic feedback. Yes, I probably should add that back in. As it is, I'm not super thrilled w/ the touch response in the new Safestrap. I probably need to work on it as well. There are times when touches are "lost" and then double up (for 2 touches at once). But hey, it's better than nothing.
I could not agree with you more. I am ecstatic that i was able to make a backup. Now i can work on getting rid of some of this bloat without sacrificing the ability to update again.
Sent from my DROID4 using Tapatalk
I'm behind, say I'm running stock, with safestrap with aokp.
What's the best way to install the leak then install safetrap 2.0?
1. Go to non safe
2. Flash leak
3. Root the leak
4. Install safestrap
That about right?
Any gotchas we should know about?
Sent from my XT894 using Tapatalk 2
Here is the link for detailed instructions. If you have to the fastboot route than it is about an hour long process so my advice is start with a fully charged battery.
http://forum.xda-developers.com/showthread.php?p=26311439
Sent from my DROID4
bonesjones said:
I'm behind, say I'm running stock, with safestrap with aokp.
What's the best way to install the leak then install safetrap 2.0?
1. Go to non safe
2. Flash leak
3. Root the leak
4. Install safestrap
That about right?
Any gotchas we should know about?
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Follow the instructions posted but the basic rundown will be..
1. Fastboot .219 images
2. Re root phone with motofail.
3. UPDATE SUPERUSER BINARY!!!
4. Use Voodoo rootkeeper to backup root, temp unroot, and restore root.
5. Install .206 ICS leak with stock recovery
6. Use Voodoo Rootkeeper to restore root.
7. Install Safestrap 2.0
Done, and pretty sweet.
No more data issues!
No more not being able to do video!
No more not being able to use flash!
No more weird youtube glitch!
Now to wait to wait for an AOKP port and I'll be perfectly happy!
...Until the next android comes along...
Have you successfully removed any of this awful mototrash? It almost makes me want to go back to CM9's dailys. It's that awful.
strakajagr said:
Have you successfully removed any of this awful mototrash? It almost makes me want to go back to CM9's dailys. It's that awful.
Click to expand...
Click to collapse
I know your questions was not directed towards me but I used Titanium Backup to freeze all of the bloatware, then realized you can do this within the OS under the APPS list. There is a disable button in each app details screen. I froze almost EVERYTHING, except for the My Gallery/music apps. I pretty much did the same thing when I was running GB...was worried that something would cause a bootloop but was very careful I guess. Battery is MUCH better now!!!
Yeah I've done that for the most part. I just really can't stand the motoblur. It's so frustratingly cartoony and awful and I'm really conflicted about what is worse, the intermittent data or this crappy interface.
strakajagr said:
Yeah I've done that for the most part. I just really can't stand the motoblur. It's so frustratingly cartoony and awful and I'm really conflicted about what is worse, the intermittent data or this crappy interface.
Click to expand...
Click to collapse
Lol tell us how you REALLY feel. I have to agree with you though. Motoblur is dog ugly but then again so are most of the custom interfaces. I prefer vanilla android.
Sent from my DROID4 using XDA
flamefangahs said:
Lol tell us how you REALLY feel. I have to agree with you though. Motoblur is dog ugly but then again so are most of the custom interfaces. I prefer vanilla android.
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
+1 on that... I just really didn't want to purchase the galaxy nexus just to get a vanilla android experience.
Sent from my DROID4 using XDA
Any word on when it will be available to 208 users?
Not working for Newest ICS Leak 6.16.208
gdeeble said:
Any word on when it will be available to 208 users?
Click to expand...
Click to collapse
Good question, I can confirm this new Safestrap does not work for 208. When you push install recovery, it loads and obtains root rights, but it never changes from not installed/not active.
Actually I fixed mine. Make sure you install busybox when you root your phone. I just used the free busybox installer and it fixed it where Safe Strap installed on 208. Woo Hoo! My data from 206 also restored. Thank you god for Hashcode and this wonderful tool. :-D
[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