News
1/31/11: v0.1 is released; initial beta.
-A JS3-based ROM with a focus on simplicity, stability, speed, and battery life.
Hello XDA.
I wanted to create a ROM on the latest firmware with an emphasis on simplicity, stability, and speed, and battery life. I wanted to be able to customize the ROM without the use of extra software, gimmicks, or any unnecessary tool. I wanted it to be as close to the stock ROM as possible (in terms of appearance, not performance), with only the bloatware removed, and a few key applications added. I also wanted it to be blazing fast without sacrificing battery life.
So, I started working on seeARMS' XWJS3. This ROM gives users the choice of installing their preferred kernel, modem, bootanimation, etc, and using either a wipe / non wipe version (and soon: themes, applications, everything) simply by deleting and renaming a few files.
Using a handful of shell scripts, this ROM checks for, say, the SpeedMod kernel (named "speedmod") in your SD card. If it's found, it installs the speedmod kernel. If you prefer Super Optimized Kernel, that's alright: leave the file named "sok" and delete the other kernels. This ROM will automatically install whichever kernel you choose, without the need to use additional tools or software.
Note before proceeding: This is the initial BETA release, so there are bound to be bugs. I've been running this build for a few days and everything's been fine, but that isn't to say it's completely bug-free. Have a backup on hand in case anything goes wrong.
Also, read the first few posts before asking a question, as I'll try to address everything I can. When you are posting a question/problem, please include the logfile located at "seearms/log/seearms.log" (if it exists). If it doesn't exist, please say so.
Alright, so now that that's done, heres the index:
1. Download and Installation Instructions
2. Changelog, To-Do
3. FAQ and Common Problems
4. Screenshots, Media, User Comments
Current Kernels: SpeedMod K12T-T1, Super Optimized 4.7.2, Advanced Voodoo v666.1+2.
Current modems: JL2, JPY
Current addons: Nexus Bootanimation, Wipe
Features
Based on XWJS3 (v2.2.1) [Latest firmware; fast, battery efficient]
Choice of SpeedMod, Super Optimized, Advanced Voodoo kernel [All have Voodoo sound, sharpness + color, BLN, faster, better battery!]
Created an error-checking script which prevents battery drain and force closes [Ensures the installation goes smoothly]
WiFi Firmware Version Fix [Better battery life]
Circle Battery Mod installed by Default
3 Launchers - Gingerbread, Stock, Launcher Pro
3 Keyboards - Gingerbread, Stock, Multi-Language Swype
Fully deodexed [Easily Themable]
Fully zipaligned [Better RAM Usage]
Fully updated Google Apps (YouTube, Flash, Market, Gmail, Maps)
Latest Su and Busybox [Preinstalled, no extra effort required]
All protected apps in market visible - modified build.prop
Big APN list, which allows instant internet + MMS access
Stock AOSP Lockscreen
Backlight Notifications
Removed startup + shutdown sounds
Phone Ascending Ringtone Fixed
Modified Applications
+ Gingerbread Keyboard
+ Launcher Pro
+ MIUI Music Player
+ SGS Info, Toolbox, Tools
+ Swype 2.15 Multi-Language
- Press Reader
- Write and Go
- MiniDiary
- AllShare
- Buddies Now
- Android Books
- ThinkDroid
- Aldiko eBook
- Layar
- FileIndex, Telegraaf, Samsung Shortcut from stock JS3
Downloads
Latest and Greatest
v0.1: seeARMS' XWJS3 v0.1 (1/31/11)
http://www.multiupload.com/842IKYJ8FU
Addons
Coming soon
Installation Instructions
Before installing, make sure to disable any lagfixes, create any backups that you need, etc.
Long version:
1. Extract the downloaded file to the root of your SD card.
2. Navigate to the "seearms/kernel" folder, and here you should see 3 files: sok for Super Optimized, voodoo for Advanced Voodoo, and speedmod for the SpeedMod kernel. Delete two of them, leaving only the one that you want to install.
3. Navigate to the "seearms/modem" folder, and here you should see 2 files: jl2 and jpy. For Canadians, or other users who want the use of the 850MHz band, leave the "jl2" file untouched, and delete the jpy file. For everyone else, delete jl2 and leave jpy.
4. Navigate to the "seearms/extra" folder. Here you should see nexus_bootanimation, and a "wipe" file. Leave the bootanimation untouched if you want the Nexus S bootanimation, and leave the wipe file if you want the ROM to format /data.
So, before installing, you should have one file in kernel, one file in modem, and anything in extra, depending on your preferences.
5. Boot into CWM or Recovery 2e, select "Install from zip", navigate to the ROM you copied, and install.
I'd recommend the following files left untouched:
seearms/kernel/speedmod
seearms/modem/jpy
seearms/extra/wipe
This will install the SpeedMod kernel, JPY modem, and will wipe your data to allow for a brand new install.
Short version:
1. Extract the downloaded file to your SD card.
2. Delete any kernel and modem you don't want, leaving only 1 in each folder.
3. Delete seearms/extra/wipe if you don't want it to wipe. Delete anything else in this folder you don't want.
4. Boot to CWM, flash the zip.
After it boots, I'd recommend doing a few things to ensure your phone is as fast as possible:
1. Enable the EXT4 lagfix in recovery
2. Enable all tweaks in recovery
3. Overclock if you wish using SetCPU
Changelog
1/31/11: v0.1, initial beta release
To-Do
-Extended power menu
-More modems, kernels
-Choice of applications and themes to install
FAQ
Contents (Use control + F to find the question)
Q1 - I'm on stock Froyo and I have 3e recovery!
Q2 - I have a Bell Galaxy S, and I'm afraid of my phone bricking! What can I do to prevent it?
Q3 - I'm encountering force-close issues, and general app issues right after installation.
Q4 - My GPS isn't working! It takes forever to lock and displays my position inaccurately!
Q5 - My battery is running out very, very quickly!
Q6 - What's all this talk about the 850MHz band and modems?
Q1 - I'm on stock Froyo and I have 3e recovery!
Click to expand...
Click to collapse
If you're on stock Froyo (ie: not running Eclair with recovery 2e or ClockworkMod) then you might have to do a bit more work before installing any custom ROM. Just follow these steps:
1. Download Odin from here.
2. Download the latest Super Optimized kernel (or any other kernel that has CWM) in the attachments. Make sure to download the Odin kernel, not the CWM one!
3. After downloading, extract the .TAR file from the file you just downloaded.
4. Open Odin, and turn off your phone. Connect your phone to your PC via USB, and enter download mode by holding volume down + home + power.
5. Odin should detect your phone. Load up the .TAR file in the "PDA" box in Odin. Make sure the other boxes are left blank. Untick "Repartition". Start flashing.
6. Your phone should automatically reboot with the new kernel! To double check, shut it off and boot into recovery. If you see CWM recovery, you're successful!
After doing this, follow the normal steps to install this rom.
Q2 - I have a Bell Galaxy S, and I'm afraid of my phone bricking! What can I do to prevent it?
Click to expand...
Click to collapse
It isn't entirely known right now why the phones are bricking; some say it's a hardware issue involving the motherboard, whereas others say it's strictly a software issue. Both Samsung and Bell have stated that the new firmware, JL2, fixes this problem and will prevent the internal SD card from dying. However, there have still been reports of phones running the JL2 firmware and dying (albeit much, much less reports).
A bit more technical: Included in the stock JL2 firmware from Bell is a new secondary boot loader (Sbl.bin). This deals with the phone at boot-time; it handles three button recovery, etc. Typically, the Sbl isn't included in a new ROM, as nothing needs fixing and the boot loader doesn't need touching. Except for this time! The Sbl.bin is apparently the file which fixes the internal SD card problem.
So, if you're wondering what to do in order to prevent your phone from dying, your best bet would be to flash the JL2 firmware using Kies (or Odin if you know what you're doing - tick bootloader update), then you're basically free to flash any other firmware you wish (except for firmwares which contain the Sbl.bin, because that would overwrite the current Sbl. But, every custom ROM and essentially every stock ROM lacks this file, so you're fine to flash anything).
Again, I'm going to restate that not everything is known involving this problem and the above is based on my own research. A handful of people have done this and have still had their phones die.
Q3 - I'm encountering force-close issues, and general app issues right after installation.
Click to expand...
Click to collapse
If you installed the ROM without wiping, try leaving the "wipe" file untouched so the ROM performs a completely clean install. If you're still encountering issues after doing this, boot into recovery, perform a factory reset, and clear the cache + Dalvik cache.
Q4 - My GPS isn't working! It takes forever to lock and displays my position inaccurately!
Click to expand...
Click to collapse
Try clearing the GPS data on your phone. Do the following: (Original poster unknown. Reposted by dpvu.)
1) Enter *#3214789650# into the dialpad.
2) Under "Application Settings" set the Start Mode to Coldstart.
3) At the main menu "Delete GPS Data".
4) At the main menu "Get Position Test".
If you're still not finding many satellites try setting Operation Mode to "MS Based" in the "Application Settings". I did all of this then set the GPS back to hot start.
Lastly, if you desperately want to fix your GPS, try flashing the JK4 modem. There have been different reports, but it has been regarded by some as the best modem for GPS. To flash it, download the modem, and use Odin to select the "modem.bin" file in the PHONE box. Go to Settings -> About on your phone after flashing and look at Baseband to ensure it flashed correctly.
Download the JK4 modem from the Downloads section. http://www.multiupload.com/3HOKWMBHO2
Q5 - My battery is running out very, very quickly!
Click to expand...
Click to collapse
There are many, many things which may cause the battery to run out quickly. I'll go over a few of the problems here:
1. After a fresh install of a ROM, the battery may be uncalibrated. Try charging your phone, and use it normally until it discharges. Repeat this 2-3 more times; your battery meter should be accurate again.
2. Clearing your batterystats.bin has been said to help fix the problem, and improve battery life by a lot. Charge your phone to 100%, then boot to recovery and clear batterystats.bin (by selecting wipe battery stats). Reboot, and use your phone normally until it shuts off by itself. After it does, charge it up fully, and you're good to go.
However, it's worth stating a few things: the above method has been put down by some users, who state that the batterystats.bin only contains a history of the battery usage and nothing more. Also, the Galaxy S contains a Li-Ion battery, which technically shouldn't be fully discharged (in order to extend the life of the battery). Do the above at your own risk.
For a few more fixes, please visit this thread.
Q6 - What's all this talk about the 850MHz band and modems?
Click to expand...
Click to collapse
The 850MHz band is a 3G band which apparently has better range and reliability (as opposed to the higher frequency 1900MHz band). It's basically only used in Canada (and I guess Australia?) but cell carriors like AT&T in the US are trying to make it the standard. Because of this, the i9000 International (not the Bell Galaxy S, i9000M) doesn't have the functionality to connect to the 850MHz band.
To get back this band, you have two options: flash any international ROM (JPY, JPX, JPO, etc), then flash a Canadian modem (JK4, JL2) afterwards. The second option is a lot easier: just install a ROM that contains a Canadian modem already (ie: this ROM, or stock JL2).
Screenshots
User Comments
Existence. said:
running great with speedmod and jl2 modem - thanks a lot.
battery life is amazing too - its at 85% and ive been using it all day!
Click to expand...
Click to collapse
Hi, well done. Nice to see you releasing another rom.
Sent from my GT-I9000 using XDA App
I will have a look at it.
thanks! seems very interesting!
PS: 3G 850Mhz band is also used all over central and south america, from mexico to argentina
[[ Cold ]] said:
thanks! seems very interesting!
PS: 3G 850Mhz band is also used all over central and south america, from mexico to argentina
Click to expand...
Click to collapse
Got it, thanks.
running great with speedmod and jl2 modem - thanks a lot.
battery life is amazing too - its at 85% and ive been using it all day!
Existence. said:
running great with speedmod and jl2 modem - thanks a lot.
battery life is amazing too - its at 85% and ive been using it all day!
Click to expand...
Click to collapse
Thank you.
Nice job seeARMS! It is running well so far (speedmod + JL2 modem).
I want to use SOK and overclock it but I can't seem to disable the VSF that is included with the kernal.
Your rom also works with the Generation X theme, which includes the extended power menu too! The AOSP lockscreen included could still be unlocked with the menu key but the Gen X theme solved that. Have you seen the 4 lockscreen? It looks very nice but I can't seem to find it.
Keep up the good work!
Hey found a bug every time i install anything from samsung apps it vibrates and then takes me to the bootanimation screen going to flash it again and see
ok tried it again i can't install any apps even from market
seeARMS said:
Screenshots
User Comments
None yet
Click to expand...
Click to collapse
Great choice of music
JJustin said:
Nice job seeARMS! It is running well so far (speedmod + JL2 modem).
I want to use SOK and overclock it but I can't seem to disable the VSF that is included with the kernal.
Your rom also works with the Generation X theme, which includes the extended power menu too! The AOSP lockscreen included could still be unlocked with the menu key but the Gen X theme solved that. Have you seen the 4 lockscreen? It looks very nice but I can't seem to find it.
Keep up the good work!
Click to expand...
Click to collapse
Not sure how to disable it since I don't use SOK, but try setting the file "/sys/devices/platform/s3cfb/VSF_enable" to 2. This should disable VSF.
dlzp said:
Hey found a bug every time i install anything from samsung apps it vibrates and then takes me to the bootanimation screen going to flash it again and see
ok tried it again i can't install any apps even from market
Click to expand...
Click to collapse
That's odd, I've installed many apps just fine. Try clearing the market cache by going to Settings > Applications > Manage Applications > Market, then select "Clear Data" and "Clear Cache".
If that doesn't fix it, a factory reset would almost certainly.
Hi seeARMS,
As you know, I am currently running your custom JL2 ROM as I am with Bell, etc and I am loving it except for the speedmod kernel as that VSF function just drives me crazy so I flashed one of Hardcore's kernels instead.
I have read your info on this JS3 ROM and I am curious and may like to flash it to see what it is all about but I have a question.
Obviously my base is the Bell JL2 and in saying that I should have the .SBL file that I need in order to keep my SGS from bricking (or so the theory goes) so my question is... If I want to flash this JS3 ROM, do in need to first install the JS3 firmware and then flash your ROM "OR" can I just download the .zip file, make my modifications (as described in your instructions for kernel, bootload animation, wipe, etc) and flash directly over my current seeARMS ROM / JL2 and keep my important JL2 items?
Sorry if this question is confusing but as my signature says... Im still a bit of a NOOB and still learning.
Also... Still waiting for my Blue theme for your JL2 ROM! LOL!!!
yiannisthegreek said:
Hi seeARMS,
As you know, I am currently running your custom JL2 ROM as I am with Bell, etc and I am loving it except for the speedmod kernel as that VSF function just drives me crazy so I flashed one of Hardcore's kernels instead.
I have read your info on this JS3 ROM and I am curious and may like to flash it to see what it is all about but I have a question.
Obviously my base is the Bell JL2 and in saying that I should have the .SBL file that I need in order to keep my SGS from bricking (or so the theory goes) so my question is... If I want to flash this JS3 ROM, do in need to first install the JS3 firmware and then flash your ROM "OR" can I just download the .zip file, make my modifications (as described in your instructions for kernel, bootload animation, wipe, etc) and flash directly over my current seeARMS ROM / JL2 and keep my important JL2 items?
Sorry if this question is confusing but as my signature says... Im still a bit of a NOOB and still learning.
Also... Still waiting for my Blue theme for your JL2 ROM! LOL!!!
Click to expand...
Click to collapse
To flash this ROM, all you need to do is download the zip, follow the instructions, and flash it from CWM recovery. This will leave your secondary boot loader untouched, hopefully preventing your phone from getting bricked. The only way your Sbl.bin would ever get overwritten would be if you flashed a ROM in Odin that contains the Sbl.bin, with "Bootloader Update" checked. (Or, updating it from Kies to a ROM that has the Sbl).
So, you're generally quite safe regarding the secondary boot loader.
Lol, sorry about the theme :/ Good news is, if you flash this ROM, you should be able to flash the blue theme right after installing it without me needing to port it over. (If it's compatible with JS3, which I'm pretty sure it is.)
seeARMS said:
To flash this ROM, all you need to do is download the zip, follow the instructions, and flash it from CWM recovery. This will leave your secondary boot loader untouched, hopefully preventing your phone from getting bricked. The only way your Sbl.bin would ever get overwritten would be if you flashed a ROM in Odin that contains the Sbl.bin, with "Bootloader Update" checked. (Or, updating it from Kies to a ROM that has the Sbl).
So, you're generally quite safe regarding the secondary boot loader.
Lol, sorry about the theme :/ Good news is, if you flash this ROM, you should be able to flash the blue theme right after installing it without me needing to port it over. (If it's compatible with JS3, which I'm pretty sure it is.)
Click to expand...
Click to collapse
Ok, so... Would you say in your EXPERT opinion that me flashing this onto a Canadian i9000M is safe?
Also... When and where do I make my modification to the install .zip file? Do I download the package to my desktop, make the modifications and then move it to my internal SD card "OR" do I download the package directly to my internal SD card, navigate to the package (with Astro for example), make my modifiactions from there and THEN flash?
Please advise...
PS... Id still like to see the blue theme available for the JL2 ROM just incase I get too chicken to try this JS3 one... LOL.
Hey yiannis.
Here's what I did:
Download to computer. Unzip it to the sd card when,plugged into computer. And just under my computer, I deleted the files I didn't need. Also, remember to disable lagfix beforehand
Sent from my GT-I9000 using XDA App
yiannisthegreek said:
Ok, so... Would you say in your EXPERT opinion that me flashing this onto a Canadian i9000M is safe?
Also... When and where do I make my modification to the install .zip file? Do I download the package to my desktop, make the modifications and then move it to my internal SD card "OR" do I download the package directly to my internal SD card, navigate to the package (with Astro for example), make my modifiactions from there and THEN flash?
Please advise...
PS... Id still like to see the blue theme available for the JL2 ROM just incase I get too chicken to try this JS3 one... LOL.
Click to expand...
Click to collapse
I'd say it's quite safe. While building this ROM I flashed my device well over 30 times, and it's still running great. My previous SGS I flashed less than 10 times and it died, so I'd wager it's perfectly safe.
And it really doesn't matter where you do the modifications. It's probably easier to just copy the files over to your internal SD card, delete anything you don't want using your PC, then simply flash the ROM.
Related
Ok, I finished rooting/packaging JME for yous guys.
If you want to install ClockWorkMod, use CF-Root as its tested to work with Roto-JME and it does not change your filesystem format!
Get it here:
http://forum.xda-developers.com/showpost.php?p=10053743&postcount=1
Flash CF-Root after Roto-JME has completed its installation rebooting and you test that Roto-JME is working ok.
These firmwares are for any GSM Tab, whether you have protected bootloaders or not. They don't contain and won't install protected bootloaders either.
All the files are here:
http://files.deodexed.com/ModADroid-Galaxy-Tablet/Rotohammer/JME/
Please backup your apps and settings with Titanium Backup from the market.
Write down ALL your current APN settings in Settings/Wireless/Mobile/Access Point Names/, the one with the green dot next to it. There is 14 settings in all.
New Jan 9, 2011 Roto-JME-v4
Fixes:
Full landscape Swype
OpenVPN works with CF-Root
Diodict FC fix
added car home
added all language locales
full version wipes sdcard
slipped Program Monitor widget back in
Code:
619fc4b3cb21ebd9cce0ca2dc827d8e1 Roto-JME-Full-v4.zip
a945da9d28945132de1f509d1a1ee51b Roto-JME-Upgrade-v4.zip
From the feedback I've got so far, if you run a stock or JJx version firmware, you must flash the Full firmware with the pit file. If you have any JMx firmware currently, then you can flash the Upgrade firmware without the pit file.
New Jan 8, 2011 Roto-JME-v3
Version 3 is a different direction. Stock gallery is back, along with all the other apps that everyone missed.
Files removed:
Maps
install_flash_player
Gmail
StreetView
Zinio
Kobo
PressReader
Files Added:
AppWidgetPicker
Ebook
cifs.ko
slow-work.ko
tun.ko
module loader script
perf tweaks
The new downloads:
Roto-JME-Upgrade-v3.zip: Upgrades your existing firmware to JME. Try this first.
Roto-JME-Full-v3.zip: This package wipes your data and apps.
Addon-JME-Modem.zip: modem P1000XXJMA (big deal, from early December)
I recommend you wipe your Dalvik cache if you get any fc's after startup. Heres how:
Code:
adb shell su -c "rm /data/dalvik-cache/* && reboot"
New Jan 1, 2011
The following 2 firmwares are a start on the way to a custom rom. I removed several stock apps to make room for the Gallery3D app that doesn't consume 100% cpu (but instead fc's on remounting sdcard), and added the Ebook reader from the hidden.tar.
Files removed:
DailyBriefing
SamsungWidget_WeatherClock
Maps
install_flash_player
Gmail
ClockDateWeatherWidget
ClockAndWeatherWidget
Gallery3D
The new downloads:
Roto-JME-Upgrade-v2.zip
Roto-JME-FmtIntSD-v2.zip
If you already flashed Roto-JME (upgrade or full), just re-flash with the Roto-JME-Upgrade-v2.tar to get the new apps and not loose any settings.
(other than the home screen, but you can restore that from Titanium Backup right?)
The best option is to backup all your data/apps, flash Roto-JME-FmtIntSD.tar with the PDA button and partition with P1_add_hidden.pit. Flash the Addon-JME-Modem with the Phone button as well, or some other modem of your choice, as its going to be erased due to partitioning. Thats a nice clean setup, guaranteed to work the best
Use the upgrade if you already have a lot of apps installed and you feel lucky. Don't use the pit file with the upgrade firmware. Worst case is you flash the whole enchilada later. Backup your data anyways before hand.
Flash using Odin, using PDA button for any file you flash. If you need/want to flash the addons too, use the PHONE and CSC buttons, they all do the same thing.
Note: Anyone who flashed a previous Roto-JME-Upgrade.tar and now wants the *#1234# to show the correct values, just re-download/re-flash this file and you'll be fixed.
Simple how-to guide here:
http://forum.xda-developers.com/showthread.php?t=895827
To get the customary question out of the way, by "everyone," you mean all carriers and locations can use this package?
You, sir, are a steely eyed missile man.
I don't have the thanks button (I run the classic theme) but consider yourself thanked.
ZoinksS2k said:
To get the customary question out of the way, by "everyone," you mean all carriers and locations can use this package?
Click to expand...
Click to collapse
I was referring to the bootloaders, but, these firmwares are for any GSM Tab.
Is this fast like jmc? I read some people complaining about lag with flash in this rom? Differences youvee seen vs jmc please. Thanks. Anyway to build these to flash through clockworkmod? To streamline the way to do it? I am on the edge of returning my tab i feel the lag is causrd by the increased resolution and the processor is loaded trying to keep up. Maybe im wrong. I am currently stock with root and oclf installed. I was going to try roto-jmc tonight before making up my mind. I still have hope for this tab after seeing nero v3 on wifes vibrant its blazing fast.
ianandamy said:
Is this fast like jmc? I read some people complaining about lag with flash in this rom? Differences youvee seen vs jmc please. Thanks. Anyway to build these to flash through clockworkmod? To streamline the way to do it? I am on the edge of returning my tab i feel the lag is causrd by the increased resolution and the processor is loaded trying to keep up. Maybe im wrong. I am currently stock with root and oclf installed. I was going to try roto-jmc tonight before making up my mind. I still have hope for this tab after seeing nero v3 on wifes vibrant its blazing fast.
Click to expand...
Click to collapse
ClockworkMod only works with a stock firmware at the moment. Flashing with Odin is pretty easy though. Just like all the past Android phone, things start off sluggish but as more developers jump onboard, device performance increases. JME feels the best to me so far.
Someone like you could give us a better review of JME since you strongly know what you dislike about stock.
Roto you are the man!
Sent from my GT-P1000 using XDA App
Thanks roto...did upgrade from JMC to JME plus the cashe...so now got all samsung apps..not just the 2 like many reported....seems fine at present...so hopefully stay that way...
Thanks again roto..
Sent from my GT-P1000 using Tapatalk
I've been using JME for about one hour now and I wanted to post my first impressions. It is definitely snappier than JMC, but other than that I have not found any other advantages. Still no Samsung boot logo (not a big deal), but I am glad that I upgraded.
Hey Roto, just want to say thanks for all the awesome work you do for our Galaxy Tabs. You've made my experience that much more enjoyable. I would like to know if it is safe to flash your JME update package over the JM6 firmware I have now or do I need to flash something else first before I do JME.
Ill flash it tonight and let you know rotohammer
Only questions i have is.
Can i get back to stock? T-Mobile usa
Also will this make call after flashing your jme i only use it for wifi currently so 2g isnt a biggie yet
kris said:
Hey Roto, just want to say thanks for all the awesome work you do for our Galaxy Tabs. You've made my experience that much more enjoyable. I would like to know if it is safe to flash your JME update package over the JM6 firmware I have now or do I need to flash something else first before I do JME.
Click to expand...
Click to collapse
Just flash the upgrade, you'll be fine, its safe. Don't forget to do a Titanium backup first.
ianandamy said:
Ill flash it tonight and let you know rotohammer
Only questions i have is.
Can i get back to stock? T-Mobile usa
Also will this make call after flashing your jme i only use it for wifi currently so 2g isnt a biggie yet
Click to expand...
Click to collapse
Yes, I posted the files to get back to stock T-mobile. Yes, you'll be able to make calls, but not with the T-Mobile internet only SIM card though.
rotohammer said:
Just flash the upgrade, you'll be fine, its safe. Don't forget to do a Titanium backup first.
Click to expand...
Click to collapse
Thanks again Roto, you're the man!!! Happy New Year!!!
That's pretty weird, I am stuck on Samsung logo at start, even though Odin tells me the flash was successful...
I am coming from JMC and just ran the upgrade...
Edit: reflashed it just in case, same story. I get the Samsung animated screen and then get to the Samsung logo where it stays stuck.. (Gives a vibration and blinks every 30sec that's all)
Alcibiade said:
That's pretty weird, I am stuck on Samsung logo at start, even though Odin tells me the flash was successful...
I ma coming from JMC...
Click to expand...
Click to collapse
Try flashing:
Use the PIT included in the original post.
This will enable Reformat, that is fine.
PDA: Roto-JME-FmtIntSD
CSC: Addon-JME-Hidden
Phone: (whatever modem you need)
Flash. You shouldn't have any issues then.
If you are upgrading, its common to get these issues and you're pretty much stuck without doing a restore and losing ur data anyways. Thats why Roto recommends you do a titanium back up BEFORE flashing.
seven2099 said:
Try flashing:
Use the PIT included in the original post.
This will enable Reformat, that is fine.
PDA: Roto-JME-FmtIntSD
CSC: Addon-JME-Hidden
Phone: (whatever modem you need)
Flash. You shouldn't have any issues then.
If you are upgrading, its common to get these issues and you're pretty much stuck without doing a restore and losing ur data anyways. Thats why Roto recommends you do a titanium back up BEFORE flashing.
Click to expand...
Click to collapse
Mmh ok so my only way to go through is to erase everything
I did back up a few stuff (Not everything) but that's a pain... Unlucky I guess...
That said I didn't check in detail but I guess Titanium backs up everything on the SD Card so I should not let it be reformated, no ?
Hi there,
I just got my Galaxy Tab 2 days ago. I am with bell, and it is not on any contract...
I currently have a galaxy s (although it is in at bell for repair (internal sd issue)).
Do i first need to flash to JM6 before flashing to JME (as provided in the thread: Flashing Guide http://forum.xda-developers.com/showthread.php?t=886714)?
If i do, what files am i supposed to flash with? Or should i wait until the guide has been updated with the correct files?
Thanks to anyone who is able to help!
I've been using my tab with your new firmware for 2 hours and it's a blissful experience! Everything works perfectly and smoothly. 2010 finishes happily
Thank you.
Alcibiade said:
Mmh ok so my only way to go through is to erase everything
I did back up a few stuff (Not everything) but that's a pain... Unlucky I guess...
That said I didn't check in detail but I guess Titanium backs up everything on the SD Card so I should not let it be reformated, no ?
Click to expand...
Click to collapse
Just flash the Roto-JME-Upgrade.tar alone and see what happens.
First off, this is not for the faint of heart. Backup your junk, don't flash modems or bootloaders if you don't what you're doing, in fact, don't flash anything, if you are not aware of what is what... Read this ENTIRE GUIDE FIRST, THEN DO IT... that way you have a clear understanding of what is suppose to be on your sd card, etc....
Second, none of this is my own work. I take no credit for the development of any of the following, this is more of a guide than
a rom on how to get a Sprint SPH-P100 working with a custom recovery, kernel and rom.
I should note, I have tmobile US, and my interest in this tablet is a secondary device, hence it being a sprint device. It is not meat to be a phone for me... I dont plan to make calls or text, only tether it to my phone, use GPS as well as the other functions. It is, essentially, a laptop replacement with extra goodies...
That being said, if you test this, it is at your own will and I will provide no further instructions on how to undo something you have done... this forum has a search feature, use it. Any contributions to developing it further and providing fixes for the problems listed below are welcomed.
Before I begin, big, BIG thanks to alterbridge for providing me with excellent tips.
Also to Khasmek for his kernel and everyone who helped in the production of heimdall.
Again I say, this guide is meant to give you overclocking features for your tablet. As-well-as the ability to reboot to a custom recovery from the gui (in this case cwm 3.0.0.0).
What works?
Wifi
Camera
Video Recorder
Gallery
all other apps
What does not work?
GPS
What may or may not work?
Calls
MMS
SMS
Voicemail
What's included:
Refer to:
http://forum.xda-developers.com/showthread.php?t=932082
I'm assuming here that you are rooted. If you are not, use superoneclick. Google it...
I'm assuming your are stock also, if you are not, I advise you to get that way using this: http://forum.xda-developers.com/showthread.php?p=9753941#post9753941
Please read it carefully as you can complete bork your tablet if you are not certain. Thanks to gordesky1 for the guide.
When/if you are back to stock you can begin this process. I insist that you do this, because it is the method I started from after flashing various roms/kernels etc...
Now preload your microSD card with the following (i'm assuming you have formatted and can load it with a pc-usb attachement)
[ROM] Overcome 1.6.3
Link: http://www.multiupload.com/8XVZ2JPE4V
Source: http://forum.xda-developers.com/showthread.php?t=932082
[Kernel] KhasMek Voodoo Plus v5
Link:http://gunsforgeeks.com/Tab/kernel/KhasMek.Voodoo.Plus.CDMA.Tab.v5.OC.zip
Source: http://forum.xda-developers.com/showthread.php?t=941781
You will also need a new vold.fstab file, a link is within the instructions.
Lets begin (flashed with Windows 7, sorry mac/linux users, you are on your own):
Step 1: Flash the VZW kernel, as it contains cwm custom recovery and allows you to flash kernels and roms.
Source: http://www.thegalaxytabforum.com/index.php?/topic/1775-clockworkmod-for-sprint-galaxy-tabs/
Download zImage file here: http://www.megaupload.com/?d=SV6IKL1D
Process: (thanks jkurl15)
"To get the zip file containing the zimage download it from here. http://www.megaupload.com/?d=SV6IKL1D
To flash the zimage you will need to use Heimdall which can be downloaded here. http://www.glassechi...ducts/heimdall/ <--------click on the binaries
link for 1.1.1
instruction are below.
Heimdall install instructions
1. Download Heimdall here http://www.glassechi...ducts/heimdall/
2. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. http://www.microsoft...&displaylang=en <------only if you are using Microsoft widows
2. Unzip Heimdall and you should have several files in the folder called Heimdall.exe, Heimdall-Frontend.exe, QtCore4.dll, QtGui4.dll, Readme.txt and drivers folder containing zadig.exe
3. Put you tab into Download mode(while the tab is OFF hold Volume Down + Power Button). Hook the tab up to you PC and Run Zadig.exe to install the
drivers.
4. From the menu chose Options -> List All Devices.
5. From the USB Device list chose "Samsung USB Composite DEvice".
6. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
7. Done. This only needs to be done once.
ClockWorkMod Install Instructions
1. First root you tab (use one click root or z4root) then downloaded rom manager.
2. Unzip the flash_image_VZW_zimage.zip. It will have have two files flash_image and zimage. you only need to use the zimage file. Open Heimdall-Frontend.exe and browse to where you unzipped the zimage to and select it. Make sure the box infront of zimage is checked. Hit start and it should flash the zimage and reboot the tab. when it reboots it will get stuck at the samsung screen long hold the power button to shut it off. boot into recovery (cwm) power button plus volume up button it will start backing up to do the fs conversion but it will fail at /data and /cache. it will leave you in recovery.
3. While still in recovery select factory reset/data wipe when finished also do a cache wipe.
4. select reboot system, if you let it try to boot it will loop/hang on the SAMSUNG logo, this is not an issue just hold power key until it powers off.
5. while off hold volume up + power until you see the SAMSUNG logo then release both keys! NOTE: if step 4 does not fully power off and reboots just keep holding the power button until the screen blanks again then let go and quickly hold down only volume up + power until you see the SAMSUNG logo.
6. once it boots back into recovery (cwm) it will start the same backup/conversion process again, this time it will finish and leave you in recovery.
7. select reboot system and wait for it to load the tab back to froyo. (it will be back to factory defaults with the activation screen again)
8. Your tab will still be rooted so install terminal emulator and run "mount" to verify that your partitions are ext4.
9. Power off then boot back into recovery with volume up + power, it will boot back into recovery (cwm)
10. Do a backup and reboot your tab. " - zkurl
Step 2: Your screen should show you cwm 3.0.0.0 and be ready...
1) Wipe Data/Factory reset (for good measure)
2) Wipe Cache
3) Wipe Dalvick
Step 3:
Install the [Kernel]. It will flash and let you know when it is successful.
Step 4:
Install the [ROM]. It will flash and let you know when it is successful.
Step 5:
Install the [Kernel] AGAIN. (i know, it seems retarted, however I've had bootloops otherwise and it didn't matter if i didn't flash it before the rom or not, it would screw up) Anyways, it doesn't hurt.
Step 6:
Wipe again, just for good measure
Step 7:
Reboot device (first boot will take a few but doesn't hang at anything. Which means, if you see the samsung logo for longer than 60 seconds (actually takes right at 30 seconds)... you screwed up. The boot animation of the blue android with astro stars thingies going around it means you are on the path to booting)
Step 8:
The external and internal memory are jacked up. A fix has been provided and you will need to push it to your phone, and reboot.
Download vold.fstab here: http://www.multiupload.com/EKYF3CW39R (thanks to alterbridge)
bring up adb (if you dont know how, stop reading this, re-stock your phone and quit)
adb remount
adb push vold.fstab /system/etc
adb reboot
Your tab will reboot and when it comes back up, no more memory errors.
You've done it! You've flashed a oc'd kernel and a custom rom. From here, you can tinker with fixing the auto-rotate and gps and any other bugs you may encounter. I admit, i'm new to certain things, fixing it isn't my forte
I encourage you to post fixes/bugs here in the thread so that other sprint users can benefit from it all as there is a serious lack of development for them.
Future Updates: I'm assuming we can continue to flash whatever overcome updates come our way, we just have to then reflash the khasmek kernel and re-push the vold.fstab file. If we fix GPS, Screen orientation and it's through pushing means, that will have to continually be redone also. The alternative, someone cooks roms just for us... I myself could probably do it, however have never attempted to. If i get time, I will look into it, however, there are no promises...Maybe gingerbread/honeycomb variants will trickle out soon and we wont have to worry about it.
If you enjoy the rom/kernel, I encourage you to donate to the devs mentioned above, I myself will not require any donations, as this is merely a guide using other peoples materials. A big, big thanks again to the people who contributed to these roms, kernels and tools. Thank you!
Update 1: (4.30.2011 @ 6:49PM CST)
Fix for rotation using a method from the voodoo thread. Can either push it, or copy to usb with pc, then use root explorer or similar to move it into place (requires reboot)
"Try pushing the sensors.default.so file from bauxites thread. I have attached it.
unzip this and place it in /system/lib/hw (backup your old file just in case!)"
Update 2:
When you first boot, your keyboard is selected as "chinese". Simply change it to samsung or whatever else you may want to install...
Thanks to Bauxite!
File: http://forum.xda-developers.com/attachment.php?attachmentid=562977&d=1302188558
Source: http://forum.xda-developers.com/showthread.php?p=12722251&highlight=sensors.default.so#post12722251
Have you tried pushing the sensors.default.so from the v5 thread to /system/lib/hw
Thats what I just did to fix my sensors on the voodoo build
Sent from my SPH-P100 using XDA App
Obama's>god said:
Have you tried pushing the sensors.default.so from the v5 thread to /system/lib/hw
Thats what I just did to fix my sensors on the voodoo build
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
will give that a shot, thank you
Edit: that worked like a charm thank you so much, love XDA!
No problem its one of the last pages. Someone also posted a file gralloc.something.so dont use that. It gave me a weird boot crash where id get the 3 vibrates from a force close over and over again.
Sent from my SPH-P100 using XDA App
just curious, are you using this same setup as myself?
curious if sprint can still make/receive calls send/receive messages... etc...
if you're even utilizing those features... just wondering, thank you again
You mean stock sprint? On stock you can send or recieve messages but no calls
Sent from my SPH-P100 using XDA App
ah no, i meant sprint with the overcome rom and the voodoo kernel. I know there is a lot different so i'm sure it wont work, was just curious
From what I understand its only gsm that can do calling. It's either going to take aosp or some serious serious hacking to get calls on cdma. Im hoping for cyanogen, but I still cant get a stable version of that for my brother's samsung epic.
Sent from my SPH-P100 using XDA App
This worked like an absolute charm!
can anyone of you confirm if you
1. installed on Sprint Tablet
2. have the GPS working?
Thanks soo much!
BTW, great on the write up!
galexandr said:
can anyone of you confirm if you
1. installed on Sprint Tablet
2. have the GPS working?
Thanks soo much!
BTW, great on the write up!
Click to expand...
Click to collapse
1) Yes
2) No.
galexandr said:
Thanks soo much!
BTW, great on the write up!
Click to expand...
Click to collapse
You are very welcome
My Wifi all of a sudden quit working. I turn the Tab on, press the wifi toggle in the notification bar, and then it says "Error" and turns off.
That's interesting. This and Force Closes is why I ended up wanting Overcome over the KhasMek rom....
However, My sprint tab has not encountered this as an error, and I've flashed other modems and everything...
You might try and "fix permissions" from the recovery ... otherwise reflash again just for s's and g's.... I myself haven't seen this as a problem and have used it this way well over a week.
mr2324jgf said:
That's interesting. This and Force Closes is why I ended up wanting Overcome over the KhasMek rom....
However, My sprint tab has not encountered this as an error, and I've flashed other modems and everything...
You might try and "fix permissions" from the recovery ... otherwise reflash again just for s's and g's.... I myself haven't seen this as a problem and have used it this way well over a week.
Click to expand...
Click to collapse
I wiped data from CWM 3.0 and wifi started working again. I wonder what the issue was.
I'm also curious - would this technique work for the GSM CM7 port? Or is CM7 too far away from stock?
I've tried flashing cm7 a few ways and am always unable to get it to work. I'm assuming it's because I need the pit file with it which in heimdall requires the bootloaders also. I haven't messed with oldin or heimdall command prompt...
Last night I attempted again to flash the voodoo kernel over top of the clockwork mod with the stock rom... I then used titanium to clean some junk up, so i'm basically back to stock sprint with a custom OC kernel... it's pretty nice. I'm still not satisifed fully because I know there has to be other options.
mr2324jgf said:
I've tried flashing cm7 a few ways and am always unable to get it to work. I'm assuming it's because I need the pit file with it which in heimdall requires the bootloaders also. I haven't messed with oldin or heimdall command prompt...
Last night I attempted again to flash the voodoo kernel over top of the clockwork mod with the stock rom... I then used titanium to clean some junk up, so i'm basically back to stock sprint with a custom OC kernel... it's pretty nice. I'm still not satisifed fully because I know there has to be other options.
Click to expand...
Click to collapse
Just curious, why did you revert back to stock from this rom?
Sent from my SPH-P100 using XDA App
followed the guide and still stuck at the samsung screen after flashing kernel, rom kernel.
This is going to sound like critisism but I mean it as an honest sincere question. Why would anyone want to follow this guide if it breaks GPS? It's already possible to get the OC with Kazmek or Bauxite's kernels on the stock firmware with EXT4, and GPS also works fine with that other AOSP build, so what's the point of this?
cmoreno911 said:
Just curious, why did you revert back to stock from this rom?
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
I've since returned to overcome, I really wouldn't mind having my gps back... but i'm testing different options on it. It's fun to tinker with it, whatever the case, lol
idumych said:
This is going to sound like critisism but I mean it as an honest sincere question. Why would anyone want to follow this guide if it breaks GPS? It's already possible to get the OC with Kazmek or Bauxite's kernels on the stock firmware with EXT4, and GPS also works fine with that other AOSP build, so what's the point of this?
Click to expand...
Click to collapse
the stock firmware has bloatware for any given carrier. the overcome rom is stripped of some of the nonesense without having to go into titanium and delete crap trial and error...
also, in the overcome rom, i can boot into recovery, reboot etc from the power button, whereas with the stock rom i can only power off....
not to mention, i dont have sprint and the sprint branding bothers me... custom boot etc makes me feel like i'm in control of my tablet.
the other benefit of myself and others doing this, is to try and FIX the gps, thus making this the best CDMA/Sprint option for the tablet.
etc etc etc....
thanks.
So, as people know, the newest builds of CM7 or CM9 by JackpotClavin require it to be placed on top of a fully updated Gingerbread Droid Pro. However, those of us with a US Band unlocked radio can't do that without losing our unlocked radio since there is no unlocker for the gingerbread radio. Based on what Axl did for the Droid 2 Global, I've created a gingerbread kernel based on the Droid Pro to allow us to install gingerbread roms while maintaining our unlocked radios. I've also created a clockworkmod backup that can be used as is, or as a base for installing another gingerbread rom such as CM7. Thanks to JohnS and dettofatto, the kernels and clockworkmod backups were updated to 4.7.3. Below are the Resources and the Process.
Resources:
1) RDS Lite (http://forum.xda-developers.com/showpost.php?p=19390783&postcount=1)
2) SBF 2.26 (http://db.tt/5gKwCQwF)
3) TBH Radio Unlocker (http://goo.gl/6NuuG - http://www.mediafire.com/?9pfbk846tjb5a36)
4) Root (http://www.psouza4.com/Droid3/)
5) Droid 2 bootstrap (http://www.mediafire.com/?g8l7vy0futbc4g5)
6) Kernel (US http://www.mediafire.com/?swv4bl7wa47mpxg or EU http://www.mediafire.com/?w6963rmkvdqmro1)
7) ClockworkMod Backup (Verizon US http://www.mediafire.com/?yhr4b768qbnyote or European http://www.mediafire.com/?wn3pyy5fw3i1nr2)
8) Optional Roms - CM7 for Droid Pro (http://goo.gl/M6e4s) or Apex for Droid Pro (http://goo.gl/sTwSp)
Process:
1) Boot to Recovery & Wipe Data (R+M+Power)
2) Boot to Bootloader (Up+Down+Power) & SBF to 2.26 (Using RSD Lite & SBF file) - Usually I have to copy SBF File to root of Hard Drive & name it 2026.sbf or it may fail (ymmv)
3) Skip Activation (http://goo.gl/n2Zhw)
4) Settings->Applications, Set Unknown Sources and USB Debugging (in development)
5) Root
6) Install Bootstrap apk, open, press 'bootstrap recover'. then 'reboot recovery' to boot to recovery mode.
7) While in recovery mode, and without rebooting at all:
...a) Wipe Data
...b) Install Radio Unlock
...c) Install Kernel
...d) Restore Clockworkmod backup (you should have extracted the clockworkmod zip so the folder is located on your sdcard at [ie clockworkmod\backup\...] folder (with the system.img and other images under that folder))
8) Optional - Install cm7, apex or other rom you download
9) Reboot
Notes:
1) You can build your own Clockworkmod recovery file by following the JackpotClavin link below and then just backing up your build. It won't have signal while you're doing it (because of the locked radio), but after you restore it later using the above steps, it'll be fine.
2) Your SIM needs to be unlocked from verizon (i used sim-unlock.net) to work.
3) Info on an Argentinian 2.3.6 rom here
Credits:
JackpotClavin - CM7 for Droid Pro (http://goo.gl/M6e4s)
Axl - Created the Droid2 Kernel which allowed me to use the same method for the Droid Pro (http://goo.gl/ErLAR)
dettofatto - Clockworkmod backup and kernel for European 4.7.3
JohnS - Clockworkmod backup and kernel for Verizon US 4.7.3
Good Luck!
hey im from argentina, here we have Motorola Pro which is the same as droid pro but it doesnt use cdma, it uses gsm and hsdpa. Can i install this on my phone or will it turn to a nice brick?
now i have ANDROID 2.2.2 and it says that the phone is the xt610 same as the droid pro.
thanks
edit: i just followed your source (jackpotcalvin) and it says it should work with gsm but there are still issues
bveditz, thanks for your work.
i have a droid pro (unlocked, verizon branded).
right now i'm using android v2.2 because the TBH radio hack only works with this version. i didn't dare doing any updates because of that. lol. i have one questions.
my phone is already sim unlocked.
so with this new CM7 build, can i just flash and use it without doing the TBH radio hack all over again?
chagla said:
bveditz, thanks for your work.
i have a droid pro (unlocked, verizon branded).
right now i'm using android v2.2 because the TBH radio hack only works with this version. i didn't dare doing any updates because of that. lol. i have one questions.
my phone is already sim unlocked.
so with this new CM7 build, can i just flash and use it without doing the TBH radio hack all over again?
Click to expand...
Click to collapse
Yes, you don't need to unlock the radio, you can start from step 5 (or 6 if its already rooted) and just skip the part about running the radio unlock. Running the radio unlock again doesn't hurt anything either.
Just a word of note, I don't know how the froyo build is by default (i didn't use it), but the current CM7 build still has the issue with switching between mobile data and wifi data, and mobile data can also cut out at times. All that info is in the CM7 discussion, but it's worth noting that the Droid Pro CM7 Build isn't a final build and might not function with the same stability as the Froyo build did. This has nothing to do with this process, it's just the current state of the CM7 rom at the moment. Flashing APEX might produce better results with the radio, but you lose features of CM7, although it has a number of its own features.
installed it. i just started with step 7C. so far so good.
radio is working. sim is still unlocked.
so far i've found one thing, maybe i didn't see the setting yet. the keyboard back lights aren't working?
chagla said:
installed it. i just started with step 7C. so far so good.
radio is working. sim is still unlocked.
so far i've found one thing, maybe i didn't see the setting yet. the keyboard back lights aren't working?
Click to expand...
Click to collapse
No, with that issue and the wifi/radio issues (loosing connection and not being able to switch between the two) , I switched over to the APEX ROM, it's more stable. You don't get the features of CM7, but it has less bugs. Might want to try that. You don't need to do anything different, just put the apex file on your SD, reboot to clockwork mod and wipe data and reflash.
is it possible to use this in some way to have band unlock and normal ginerbread without cm7
Yes. You need to basically upgrade Gingerbread to the full release, root it and do a nandroid backup. Then, you follow the steps in the first post but instead of restoring the nandroid backup of CM7, you install the nandroid backup of regular gingerbread that you made yourself.
bveditz, thanks, that is along the lines of what i was thinking might work after reading the directions... Im already running tbh rooted gingerbread... Do i need to sbf and upgrade to a clean gingerbread, or can i nandroid backup what i already have and then retain all my settings and apps so i dont have to start over. Has anyone noticed any disadvantage to useing the older radio besides the obvious advantage of being able to use the band unlock?
Excellent tutorial!!
EXCELLENT TUTORIAL GUYS. Also, you should make sure to mention after installing bootstrap, press 'bootstrap recover'. then 'reboot recovery' option. I did that, installed the kernal and restored backup fine.
Only issue so far was a -20% battery decrease randomly. I had 100% with a brand new battery fully charged for the first time and when I finished installing cm7 I was already on 80%, then dropped to 70% on a reboot or two, its weird. Anyone else had this happen? I heard the apex 2.0 rom did it to someone else as well on another forum
Also, do you guys know how to get back the blur social network apps such as friendfeed, or whichever app it was that adds your friends social network updates to their contact numbers on your contacts? Most people don't like it, but I think its a pretty awesome built in feature
jxs714 said:
EXCELLENT TUTORIAL GUYS. Also, you should make sure to mention after installing bootstrap, press 'bootstrap recover'. then 'reboot recovery' option. I did that, installed the kernal and restored backup fine.
Only issue so far was a -20% battery decrease randomly. I had 100% with a brand new battery fully charged for the first time and when I finished installing cm7 I was already on 80%, then dropped to 70% on a reboot or two, its weird. Anyone else had this happen? I heard the apex 2.0 rom did it to someone else as well on another forum
Also, do you guys know how to get back the blur social network apps such as friendfeed, or whichever app it was that adds your friends social network updates to their contact numbers on your contacts? Most people don't like it, but I think its a pretty awesome built in feature
Click to expand...
Click to collapse
Thanks, made the note to the tutorial. I haven't noticed the issue with the battery, but I do know that this is one of those roms that seems to jump in increments of 10 for the battery which is kinda weird. That said, i only used it about a week on CM7 before switching over to the Apex rom (and haven't noticed that issue on the apex rom).
Don't know about blur, I didn't use the original OS at all. That said, you can do what the guy above did and wipe the phone, upgrade all the way to gingerbread, do a nandroid backup then follow the original instructions but use that backup to restore to, which should have the full motoblur functionality. Thats just a guess though, haven't tried it myself.
------------------
Could you re-up just the Kernel file? I've followed your instructions to the T and every time it seems that I have a problem at that step.
I've gotten to Flashing the Kernel VIA CWM, and when I try to restore the backup of CM7 via \clockworkmod\restore\ folder - it will say MD5 mismatch.
Also, if I skip the restore portion of CM7 and just try to reboot the phone after flashing the Kernel, I will be stuck at the red M.
I've tried rebooting the phone right after applying the band unlock (all after SBF + Wipe data), and the phone will boot up just fine if I skip flashing the Kernel (again I leave it in zip form and install it via CWM).
I’ve already unlock my SIM via code provided by VZW (I am a VZW customer in good standing)
While stuck at the red M, I’ve done a battery pull and tried to enter Recovery mode by pressing M+R+Power, and the recovery screen that is booted up doesn’t look like it’s compatible with the phone. I can almost describe it as a bunch of white horizontal lines of what the menu should be, and all the menus and the green android are skewed diagonally to the right/and also looks like it’s double or triple vision.
I know a very similar process works for the D2G, because I have successfully performed and tested it on the D2G on one of my other lines.
Any help is greatly appreciated. I can stick with Froyo, but I’d like to have GB.
Try redownloading the CM7 backup, it might be a corrupted download. If that doesn't work, try the APEX file. But, yes, you cannot reboot without restoring a gingerbread backup or you'll have to start over again (there's ways to get back to the cwm but i'm not sure how, I did it accidently a few times).
Thanks I am a complete noob
So it turns out the problem is when I unzipped the Backup that it created sub folders "\nandroid\restore\xxxx\xxx\backup\restore\"
Just to save everyone headaches, make sure the when you unzip the file into your backup folder that the name of the next folder down is the series of numbers that represent the name & number i.e.
Should NOT be
\clockworkmod\backup\clockworkmod\clockworkmod\backup\2011-11-27.09.52.03\
but instead SHOULD BE
\clockworkmod\backup\2011-11-27.09.52.03\
My 7zip by default created all those sub directories, which caused the CWM restore not to find the back up files.
On another note, I am having issues with GSM Wifi and 3G.
With a fresh flash & WiFI on - if I connect WIFI first I cannot later add the APN and access Cellular Data
Inversely, If I add the APN first (again after a fresh SBF flash, kernel update, and Backup restore), and connect to cellular data, none of the WIFI connects I make can access WIFI Data
I am going to try WIFI fixer in one of the older threads to see if this resolves the problem.
DROID PRO
Please upload the file in other downloads bc megaupload is temp down
agni said:
Please upload the file in other downloads bc megaupload is temp down
Click to expand...
Click to collapse
If you're talking about the two multiupload files I put up, use one of the other links below megaupload. I just tried the bottom one (wupload) and it worked. If you're talking about RSD Lite and SBF files, I'll see if I can find another link to them, but you can easily find them by searching the forums or google.
**Edit** Edited first post with non-megaupload links.
jraskal said:
On another note, I am having issues with GSM Wifi and 3G.
With a fresh flash & WiFI on - if I connect WIFI first I cannot later add the APN and access Cellular Data
Inversely, If I add the APN first (again after a fresh SBF flash, kernel update, and Backup restore), and connect to cellular data, none of the WIFI connects I make can access WIFI Data
I am going to try WIFI fixer in one of the older threads to see if this resolves the problem.
Click to expand...
Click to collapse
Let me know how that worked out. I stopped using CM7 and switched to Apex because of the Wifi/Cellular switching issues of the november cm7 rom.
bveditz said:
Let me know how that worked out. I stopped using CM7 and switched to Apex because of the Wifi/Cellular switching issues of the november cm7 rom.
Click to expand...
Click to collapse
Can you provide a link to the Apex rom you're using?
aaevann said:
Can you provide a link to the Apex rom you're using?
Click to expand...
Click to collapse
Theres an apex thread on xda that links to the rom http://forum.xda-developers.com/showthread.php?t=1292506
Basic concepts, how-to'sThis thread is a work in progress. If you would like to contribute information or have ideas for what should be added please PM me.
Disclaimer "just because i am trying to be helpful does not make me responsible for anything that you do to your phone. playing with any of this stuff could destroy your phone"
I am not a dev, but I have been flashing on Samsung phones since the international S2 came out. I also spend a ton of time reading the forums and researching what I don't know. I would like to give back to the community in some way and I hope that this post can help the noobs not brick their devices, as well as keep them from being overly annoying to the members and developers here by posting in the wrong places and asking dumb questions.
Some basic rules if you are a noob and don't want to turn your phone into a brick.
1. be patient. don't be the first or even the tenth person to flash anything. wait until you see others using whatever Rom or kernel with success.
2. If you have any doubts about what you are doing, read more. don't flash.
3. make sure you are in the forum for your device, not some similar or related device.
Some basic rules for these forums
1. If you have a question, the first thing to do is look it up yourself. that means searching the forums first, then searching Google.
2. If after searching you can't find an answer, then post in the q&a forum
3. don't report bugs unless you are using an intact version of whatever Rom, if you have changed kernels, installed a ton of apps etc it probably isn't a bug, it's a bad combo or its you.
4. don't report bugs unless you are 150% sure that no one has reported it yet.
5. if you report a bug, make sure you can duplicate it first, then get a logcat of the problem so you can help (see below for logcat info)
Why flash?
by flashing your device you can make your phone act differently, look different, and enable new or disabled options. you could ,for example:
enable native tethering
enable call recording
change the look of your phone
add custom toggle buttons
overclock or undervolt
increase battery life
etc..
Kernel vs Rom vs Recovery vs Modem
Kernel is the layer between the phone hardware and the rom. it controls things like Wi-Fi power, touch sensitivity, possible range of screen brightness, phone logging, and processor max and min speed. kernel must be designed not only for your device but also for the type of rom you are using (Sammy rom or Aosp) some kernels support all roms, others are specific.
Rom is the operating system of your phone. there are three main categories of roms.
roms that are based off of the Samsung stock rom (Sammy rom)
roms that are based off of Android open source project aka AOSP (AOSP, AOKP)
roms based off of the miui project (these used to be a branch of AOSP but recently they have also used Sammy base for miui)
recovery is a partition that you can access at boot by holding down a combination of keys. (volume up and home button in the case of our sgs3) every phone has recovery stock but it doesn't do much. you can replace stock with clockwork mod recovery which is extremely useful for flashing all kinds of things and making backups before you do. There are other alternative recoveries besides clockwork but that seems to be the most common. TWRP is also gaining popularity these days, especially on the sgs3. You can easily switch between recoveries and or upgrade your current recovery. All that needs to happen is for a new image to be flashed onto the recovery partition. See the rooting guide for more info on how to flash a custom recovery.
modem is a file that controls the cell radio of the phone. helps determine what frequencies to use and settings for a particular network. It is important when flashing a radio that you flash a radio that is for the AT&T sgs3 as flashing the radio from another carrier has been known to cause problems with the IMEI
Methods for flashing files - Odin vs mobile Odin vs. clockworkmod(cwm) vs adb
Odin is the internal Samsung tool for flashing. I believe it only exists on Windows platform. This tool is mostly used to initially flash an insecure kernel or rooted kernel, OR to return to completely stock rom. This tool can effect your flash counter (see below). Files for flashing in odin generally should end in .tar or .tar.md5 although sometimes they come zipped and the tar is inside the zip. Read more about Odin before using it as it can easily break your phone. !!!as a general rule make sure you never check the "partition" checkbox EVER!!!
Mobile Odin is a phone based version of Odin made by the very talented developer Chainfire. It can be installed on a rooted phone and used to flash the same .tar based files as the desktop version. Mobile odin has a few advantages. 1 you can use it from your phone. 2 it does NOT effect the flash counter on your phone, 3 it can auto root a stock rom (nice if you want to try out a brand new update that has not been rooted yet)
clockworkmod(cwm) is recovery based tool that can make backups of your entire phone, flash new roms, kernels etc.., and do many other useful tasks. Once you have this on your phone my guess is that most of your flashing will be done through this tool. The files for flashing through clockworkmod are .zip files. Clockworkmod will NOT effect your flash counter.
ADB is the android develpment bridge. It allows for command line interface with your phone through it's debugging options. ADB can do most anything as I understand it. In my several years of flashing I have only had to use it once, and i could have waited for someone to come up with another solution. In general as a noob i recommend you stay away from ADB.
open source vs Samsung based roms vs miui
Open Source Roms such as AOSP/AOKP are built using Google's open source android code as a base. The developers then add functionality specific to the device. The advantages of these builds are that they often have tons of options built in to the rom that change the behavior and look of the phone. They usually allow you to change the toggles in your notification pull down, change the battery display, make all kinds of adjustments to sounds, vibration etc... Some people also prefer the "vanilla" android look and feel. These roms often provide "bleeding edge" concepts, design, and modifications. The Disadvantages of these roms is that some of the hardware coding is done closed source by the phone manufacturers, which means that things like bluetooth, camera, video recording, and MHL video out often don't work or take much longer to get working by the developers. Basically anything that relies on the Samsung framework will not work in an open source build. This means Svoice, Snote, and the Samsung camera app will not work.
Samsung based roms are taken from the Samsung original phone software and modified by the developer. Usually, these roms are modified in order to be faster and to make changes to some of the features. Expect to see changes to the stock rom like: debloated (ATT and samsung software removed), de-odexed (explained later), enable tethering, unlimited sms recipients, added notification toggles, etc. Most of these changes are made to: make the phone faster, improve battery life, make the phone easier to theme. The advantage of these roms is that they still use the Samsung framework so all the proprietary stuff like camera, bluetooth, MHL still work, the disadvantage is that they will never be as customisable as open source roms.
MIUI is a rom that focuses on theming. Official MIUI (Chinese) gets updated weekly on Friday and then there are lots of miui developers who adapt it to other languanges and make some tweaks to it. MIUI can be built from AOSP source or Samsung source and depending will have different features. The first MIUI rom for our phone just appeared in these forums and it is based off of AOSP. MIUI has a unique look and is also highly customizable through theming. There are tons of themes available for download through the rom itself and you can mix and match any part of any theme you want. This includes icons, lockscreen style, etc.. Some people criticize while others praise MIUI for being very "iphone like". This is because the icons look more iphone like and there is no app drawer in the MIUI launcher. However, you can still use any launcher you like within MIUI.
odexed vs de-odexed
odexed is how the phone comes stock from Samsung. Odexed means that system files and apps are split into two pieces and kept in different places on the phone. This is done to speed things up a bit. However, it makes it harder to theme the phone because the apps are split up. Most custom roms choose to de-odex (basically regroup the files back into one) so that custom themers can make themes more easily for the phone.
download mode and recovery mode how to access
(Copied from mskip and his toolkit thread here: http://forum.xda-developers.com/showthread.php?t=1746665)
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
STEP BY STEP how to flash your phone for the first time
A. get root
first off, you need to gain access to the root of your phone. there are several ways to do this (thanks to all the talented devs).
I recommend using mrRobinson's method as it will not trip the flash counter on your phone.
1. you will need to have odin from here http://forum.xda-developers.com/showthread.php?t=1722686 remember to hit the thanks button, download and install odin.
2. Kies (on Windows, not on your phone), Samsung's sync program, can interfere with Odin. Either make sure Kies is closed and close it out of background processes using the task manager in windows...or better yet, uninstall it completely.3. make sure you have the proper samsung drivers installed. you can get the USB drivers directly from Samsung here: http://www.samsung.com/us/support/owners/product/SGH-I747MBBATT
4. you need to download the right image from mrRobinson's thread. to find out which one hit the menu key from your home screen, select system settings, select about phone at the bottom, and look for the build. it should be either UCALEM or UCALG1. Once you know, go to mrRobinson's thread here http://forum.xda-developers.com/showthread.php?t=1739426 download the matching image, and dont forget to thank him.
STEPS 5-7 COPIED FROM mrRobinson's THREAD
5. Extract the .tar file from the .7z file you just downloaded from the thread in step 46. Put your phone into download mode (see how above)
7. Start Odin, connect your phone to your PC, you should see the box under ID:COM change color to show your device is connected. click on PDA and select the .tar file you just extracted. Hit the start button and wait for the file to flash to your phone. When done your phone will reboot automatically. One word of warning about Odin: DO NOT TOUCH THE CHECKBOXES!!! WHATEVER YOU DO>>DONT TOUCH THE RE-PARTITION CHECKBOX!!!!B. installing clockworkmod
the next step is to get a working clockworkmod recovery on your phone instead of the default recovery. Again, there are many ways to do this and there are several different versions of CWM recovery available. I recommend using the one from Rom Manager as it seems to be compatible with most roms. Note that currently most versions of CWM can only see your internal SD card and not your external if you have one.
1. Go to the Google play store and download Rom Manager (https://play.google.com/store/apps/...anager&feature=nav_result#?t=W251bGwsMSwyLDNd)2. Open Rom Manager app, flash clockworkmod recovery (first option), choose the appropriate phone..in this case galaxy s3 att, grant it superuser privileges, it should say install successful. NOTE: some users have reported not seeing the S3 ATT in the list of devices in Rom Manager...this is a bug and hopefully will be fixed. It may be that you need the purchased version instead of the free version for it to work? Not sure why this is but if it gives you trouble there are other ways to flash a recovery image. The next easiest way once rooted is to use the tool in this thread: http://forum.xda-developers.com/showthread.php?t=1746665 from there you can flash both cwm or twrp whichever you prefer. Alternatively you could also use goo manager to flash TWRP link to goo here: https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en
C. Test out your new recovery and make a backup of your phone
1. turn your phone off, then turn it back on while holding the Volume UP and home key. (more detailed instructions above) You should see Clockworkmod Recovery at the top.2. Use your volume keys to navigate to the backup option and select backup, then wait for it to complete. You now have a backup of your phone you can restore to at any time.
D. downloading and flashing a new rom
now its time to decide what rom to flash. when choosing a rom read the first post of the thread (the OP) carefully and take time to read through most if not all of the thread. At the very least go read the last 10 pages of the thread so you are familiar with any current issues people may be having. Once you have picked a rom:
1. Download the rom you want to try2. Make sure that the rom ends up on your internal SD card and that you know where it is3. Get into CWM recovery4. As a general rule it's a good idea to wipe data/ factory reset from CWM recovery (this will wipe all your data on the phone except any photos/videos you may have taken)5. It is also good practice to wipe cache from CWM recovery6. Lastly, from the advanced menu in CWM choose to wipe Dalvik cache7. now go back out to the main recovery screen and choose "install .zip from SD Card" option and navigate to your rom, select it and confirmnote that a new rom may take longer to boot the first time.
Flashing "dirty" vs flashing "clean"
Clean
Doing a clean install of a rom means erasing or formatting all the data from the previous rom before you flash the new one. This is the prefered way to flash a rom to ensure that it will run smoothly. It is necessary if you are switching from one rom type to another (CM to Samsung base). In order to do a clean flash you need to boot into recovery and select the following options: wipe user data (this wipes all apps and personal data, but not your photos/videos), wipe cache, advanced>wipe dalvik cache, storage/mounts>format system. This will ensure that no trace of the former rom is left on the phone. Beware that at this point your phone will not boot until you install a new rom. I suggest using titanium backup to backup apps and smsbackup+ for texts to make getting your new rom configured easy.
Dirty
Doing a dirty install means just flashing a new rom right over the top of the old one without wiping any data. The advantage to this is that you don't lose any apps or account info. The disadvantage is that you open up the possibility for problems. Generally you only want to flash this way if you are upgrading a rom (CM10 nightly to the next nightly, or from one samsung based rom to another). If you decide to flash over the top and have any issues, you should not report bugs, but try flashing clean first.
backing up IMEI
There have been some issues with people losing their imei number when flashing roms. *It appears to be limited to the old imei software version 2 but the evidence is not yet conclusive. *If you lose your imei, you will not be able to connect properly to the data network. *Luckily some devs have figured out how to re-inject an imei number into our phone and get it working again. *It is certainly a good idea to back up your imei info before flashing just to be on the safe side. *There seems to be two main threads dealing with backing up and restoring your imei. *you can check them out here:
http://forum.xda-developers.com/showthread.php?t=1801997
http://forum.xda-developers.com/showthread.php?t=1804117
huge thanks go out to these devs for figuring this out!! as always make sure you thank them.
I have yet to try either of these methods out myself so if one seems much easier or clearer please let me know.
tethering (for stock Samsung based rom)
you can use a mod to enable wifi tethering from your phone to up to ten other devices and share your data connection. If you are running a custom rom you probably already have this enabled and don't need it. It is already included in any AOSP roms also.
Make sure that you use the version of the mod that is for your software version number (UCLEM or UCLG1 see beginning of rooting guide to figure out which one you are on).
The original mod for UCLEM is here: http://forum.xda-developers.com/showthread.php?t=1732262
The mod for UCLG1 is here: http://forum.xda-developers.com/showthread.php?t=1768826
The Flash Counter
The flash counter is an internal counter that ticks every time you install a non-samsung firmware through Odin. This allows Samsung or AT&T to see if the phone has been flashed with custom roms. custom recoveries such as Clockworkmod and TWRP as well as the mobile version of Odin DO NOT change the counter. Only flashing non-Samsung files through the desktop version of Odin does. You can see your flash counter when you enter download mode on your phone. Luckily, Chainfire has developed an app that allows this counter to be reset, so there is really little concern anymore about having the counter trip. If you do need to send your phone in for repairs, you will want to reset the counter and then flash an unmodified stock rom through odin to get your phone back to factory state.
Link to Chainfire's app through this post here: http://forum.xda-developers.com/showthread.php?t=1800878
Logcat
Logcat is a way to access the android system log for everything that is going on behind the scenes. This tool is used to help developers pinpoint problems in a rom. If you want to actually be helpful to a dev when reporting a bug, you should really learn to use this tool. I am no expert on logcat but you can find some good information in this post: http://forum.xda-developers.com/showthread.php?t=1726238
APN settings
This is the apn that comes on stock at&t phone. It allows you to connect to LTE as well as hspa+
Name: ATT PTA
APN: pta
MMSC: http://mmsc.mobile.att.net
MMS Proxy: proxy.mobile.att.net
MMS port: 80
MCC: 310
MNC: 410
Auth: none
APN type: default,mms,supl,hipri
NOTES BELOW ARE COMING SECTIONS. Feel free to pm me questions you would like to see answered or suggestions for other info:
theming
unlocking sim
returning to stock
What info is stored in each area: system, data, cache etc...
Looks good.
Stuck
FNM
I now know more about Android OS! Thanks for the info.
Good thread! In your step by step guide I suggest you add installing adb and adb basics. IMO, this is essential for anyone flashing, has bailed me out of trouble on more than one occasion.
Sent from my SGH-I747M using XDA Premium HD app
MORE ! MORE ! Very nice work thanks, this is shedding some lights on the terms we see floating around
excellent information, much appreciated, so what is de-odexed and odexed? thanks again!!
I got my s3 when it first shipped, and soft bricked it a month later. Even if you do everything right, it can still mess up. So waiting for a USB jig to come in the mail since my homebrew jig didnt work or I hard bricked my phone... Be warned...
Very helpful thread, thanks a lot!
Thanks for this guide!! Very helpful. Coming from a very different phone, everything about the S3 is foreign to me! Could you maybe talk about backing up nv stuff and imei?? I know there's another thread that explains it, but, this being the noob helper, I think it'd be good for anyone new to this phone.
Thanks
Thank you for making this! I'm sure this will help a lot of people out. I've flashed quite a few times and having a guide like this is definitely helpful.
I sure hope I had this guide when I flashed for the first time a few days ago, but at the time you only had part 1 done and the guide had not been completed yet. Glad to see it finished and it'll definitely help out others.
mods
Thanks for all the invaluable info on flashing ROMs. I've been a BB user for years so Android is still new to me. I'm looking into rooting and trying out some custom roms, but I had a question. When it comes to Mods can you just add those individually?
I want to use Team Sonic's FreeGS3 Rom mainly due to it's Sony Bravia engine Mod and the Awesome Beats Mod (or at least when they get it working on apps other than Google Music). However, they don't have a fully supported Rom for AT&T just yet.
Trying to have the best of both worlds....I may just need to try out something else and wait for the full ATT version.
This is a great thread you've created OP. However, I'm a tad confused. You mention in the guide that Kies interferes with Odin and you say to close and close it out of the backround, but you also mention "better yet, uninstall it completely." One of the reasons I'm rooting my new phone is to be able to delete this bloatware. Are you implying this is possible without first rooting the phone?
Thanks a lot in advance, this is very helpful.
jroyjohnson said:
Thanks for all the invaluable info on flashing ROMs. I've been a BB user for years so Android is still new to me. I'm looking into rooting and trying out some custom roms, but I had a question. When it comes to Mods can you just add those individually?
I want to use Team Sonic's FreeGS3 Rom mainly due to it's Sony Bravia engine Mod and the Awesome Beats Mod (or at least when they get it working on apps other than Google Music). However, they don't have a fully supported Rom for AT&T just yet.
Trying to have the best of both worlds....I may just need to try out something else and wait for the full ATT version.
Click to expand...
Click to collapse
I would wait to flash any ROM that isn't specifically for your device. However you may be able to flash the mods you want like the bravia mod on top of an att ROM. You need to find the original post for the mods you want, and do some research to see what they require and if anyone has used them successfully. Be extra careful of mods written for the international version of the phone.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
omi__ said:
This is a great thread you've created OP. However, I'm a tad confused. You mention in the guide that Kies interferes with Odin and you say to close and close it out of the backround, but you also mention "better yet, uninstall it completely." One of the reasons I'm rooting my new phone is to be able to delete this bloatware. Are you implying this is possible without first rooting the phone?
Thanks a lot in advance, this is very helpful.
Click to expand...
Click to collapse
I can see why you are confused. I am referring to kies on your windows PC. (If you installed it at some point) Not the version that runs on the phone.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
OP, are you sure you can install CWM through ROM Manager after rooting? I remember trying to do this on my SGS2 last year and my phone soft bricked. Tried it twice, and still soft bricked.
Why not just use Robinson's method?
ComradeNF said:
OP, are you sure you can install CWM through ROM Manager after rooting? I remember trying to do this on my SGS2 last year and my phone soft bricked. Tried it twice, and still soft bricked.
Why not just use Robinson's method?
Click to expand...
Click to collapse
I tested it out myself and it works fine. I figured this was the easiest way to get it done and not have to get adb up and running. Also, the official cwm is supported by all the new roms like cm10 and some other recoveries have had issues flashing those roms.
Thanks for putting this together! Very Helpful!
One question, you say flash CWM , first in list choose Galaxy S3 ATT, when i open Rom Manager and choose Flash i don't have the S3 for a choice ?I have Galaxy Note, Skyrocket and T-Mobile Galaxy S2, no S3....
Cholerabob said:
One question, you say flash CWM , first in list choose Galaxy S3 ATT, when i open Rom Manager and choose Flash i don't have the S3 for a choice ?I have Galaxy Note, Skyrocket and T-Mobile Galaxy S2, no S3....
Click to expand...
Click to collapse
Try scrolling down the list
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Shiny ROM: Android 4.4.4, KTU84P for VZW Galaxy Nexus (Toro)
Skip right to the downloads (if you dare )
Hello there XDA GNex community! I'll admit this is a pretty spontaneous post; I've been building ROMs from the Android Open Source (Project) for awhile now, but I've never "published" any of them. I myself own a Verizon Galaxy Nexus, so I've always built from AOSP to make sure I'm as up to date as possible. Well, that's a little background so let's get going with the overview of the ROM itself:
Overview
This ROM is Android KitKat 4.4.4, build KTU84P. The ROM is built directly from source, that is, the Android source code published by Google available for download to all of us developers. The reason I say the ROM is "OTA-like" is because I make VERY few modifications to it, aside from the things that it takes to get the ROM working. I'll go into detail about those things below, but basically I just want the ROM to make your phone feel stable and shiny and new as if it has just received a new OTA update. That being said, it's clear that the landscape of Nexus devices is changing as new ones are released. Therefore, the other primary goal of this ROM is to keep our Galaxy Nexus as close to the modern Nexus design as possible. This means that I will also add in features that will still be stock, but will also make our phones as close to a current Nexus as possible.
As for how I handle the forum side of things, I'm always open to comments, questions, suggestions, requests, etc. I know that most of those things will often be in the form of criticism, but it's okay, I think I can handle it That being said, I do also have a life and am a college student, so I may not get to come on here ALL the time. I will check back as frequently as possible, and I'm hoping that you guys will help each other out as much as possible! Keep it friendly! So now for the details...
Features
Stock Android 4.4.4, build KTU84P
Source (AOSP) built kernel (boot.img)
Easily rootable (see information below)
G-Apps (GMail, Play Store, etc.) included in build along with Nexus apps
Stock browser replaced with Google Chrome
Shiny restart options - access them by holding down the power button and then long pressing on "Power Off"
All the crazy Google proprietary app stuff has been taken care off
Updated frequently
Everything works!
So what do I mean when I say "Everything works!"?
I'm sure by now you all know that when someone says that, it usually ends up not being true. This ROM is not an exception to that rule, but I can say that I've tested most of the things that would be expected to work in stock Android, such as...
WiFi Tethering (no subscription check)
Bluetooth streaming
Google account sign-in and auto-restore of apps and settings
Google Wallet
Location Services (pretty fast GPS lock in my area also)
Photosphere
Android beam
Photo editing with the new filters
Email
Exchange support
Like I said, the normal stuff (data, voice, hardware acceleration, etc.)
More things that aren't important enough to mention here - check out the changelog for a more comprehensive list
Possible Bugs
It's impossible for me to test for and notice EVERY single possible bug in the operating system, so as of right now I can't say that there are any, although I'm sure you will find some. If you do, report them here!
Other IMPORTANT Information
Root
But wait, nothing in this post said anything about root!!!11!!1!1!!! That's right, my ROM does NOT have root built in! (I don't use any root apps, and it's important to the whole "OTA-like" theme). That being said, the ROM is easily rootable; I made sure of this because I know that many, many of you will use root for many useful purposes. If you want to root the ROM, it's as easy as installing Chainfire's new superuser control app/su with this ZIP file. More detailed information can be found in the "Installation Instructions" section. **NOTE** If you are rooted and upgrading to a new build, you should not have to reflash the rooting flashable ZIP because the ROM will keep root for you.
Updates
Now that the ROM has gotten to this stage, the update policy needs a bit of editing Based on the stats I have access to from the website host and data that I collect myself, it seems like Shiny ROM is currently (as of May 27, 2014) stable for at least 80% of the users who have downloaded it. Based on this, and because the ROM is stock, Nexus-like, it doesn't really make sense to update the ROM as frequently as before. The ROM will still be updated as soon as possible after new versions of Android are released. In between Android versions, I will work on making things 100% stable, although that goal isn't always attainable with older devices and aging hardware support. If we decide to explore other paths for the ROM, you will see many more updates If/when the time comes for me to stop updating Shiny ROM, I will let everyone know in a clear way.
Radios
This ROM will (most likely) work with any toro radios; however, I of course recommend using the most recent, Verizon-approved radios which are the FK01 and FK02 radios. My ZIP installation package for these radios can be downloaded here.
Bootloader
Once again, I'm assuming that this ROM will work with all tuna/toro bootloaders; BUT for optimal experience and performance, use the newest Google-approved bootloader, PRIMEMD04. My ZIP installation package for that bootloader can be downloaded here.
ClockworkMod Recovery
I personally recommend using ClockworkMod Recovery as it has always worked well for me with no quirks. Android 4.2 messed up a few aspects of recoveries because of its multi-user system. ClockworkMod Recovery has been updated to correct some of these issues, and I recommend updating to the most recent version, 6.0.4.3. You can flash either the touch recovery or non-touch recovery image through fastboot OR you can download my flashable recovery update ZIP (touch/non-touch) and flash it in recovery. Check out the installation instructions for more details on this.
Some Other Not-so-important Information
Naming Conventions
All of my ROM ZIP files are automatically generated by my build computer. The file name for all builds up to and including the 11/10/13 build always begins with baldwinguy77_toro_aosp so you know that it's my build for toro. All builds after 11/10/13 begin with the prefix ShinyROM_toro_aosp. That prefix is always followed by the date in mmddyy format (e.g. 112212), a hyphen ("-"), and the time in 24-hour, hhmmss format (e.g. 153945). Finally, all builds end with the "signed" suffix - it just helps me know which packages have finished building and which have not. Hopefully this helps everyone to know which update is newest; I stay away from version numbers because I let Google do all of the version control.
Source
In keeping with the spirit of open-source, all relevant Shiny ROM code can be viewed on Github. I'm not extremely experienced with Github, so bear with me as I learn! Thank you!
File Hosting
I've switched over from using Dev-host to a privately hosted site, graciously and generously given to me by user Goofball. Dev-host is still an amazing service, but it's much more convenient for me to use a privately hosted site, plus I get my own suburl and FTP access! HUGE thanks to Goofball! The private hosting will definitely help me deliver a better experience to you guys as far as downloading goes. You can view all of my uploaded, public files here: http://shinyrom.goofball.org/
Also, if anyone ever wants to mirror for me, please feel free so long as you keep the file name and the file itself intact. As for everyone who downloads from a posted mirror: BE CAREFUL! Always use a virus scanner and be careful with what you are putting on your device!
Installation Instructions (VERY IMPORTANT - Note: You can flash all of these ZIPs in CWM or TWRP*)
*Android 4.4 KitKat builds must be installed using the latest version of your preferred recovery!
ROM
1. Download the latest version of the ROM from the download post. (Also download any other files you will need to install, such as Chainfire's SuperSU Root ZIP, the radios installation ZIP, the bootloader installation ZIP, etc.)
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. If you want to be 100% sure there are no problems, wipe data. If you are coming from another ROM or Android version, wipe data. If you do not wipe data and something goes wrong, repeat this process but wipe data - this step is not necessary if you are simply upgrading.
10. If you are updating your radios, flash FK01_FK02_Radios-signed.zip
11. If you are updating your bootloader, flash PRIMEMD04-signed.zip
12. Flash the ROM (ShinyROM_toro_aosp...signed.zip)
13. If you are rooting, flash Chainfire's SuperSU ZIP file - this step is not necessary if you were rooted on the previous build and are simply upgrading.
14. Reboot your phone, and enjoy!
**Note: If you are simply upgrading to a new version of the ROM and want to keep root, follow the exact instructions above, and do not format /system. It really is not necessary to format /system at any time (unless specifically noted), as the ROM installer has this function built in.
Mods
1. Download the latest version of the mod(s) you wish to install from the download post.
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. Install the mod(s) you downloaded in step 1.
10. Fix permissions (not really necessary)
11. Reboot and enjoy!
**Note: You can remove all mods you've installed by dirty flashing the latest version of the ROM.
ClockworkMod Recovery (Fastboot method - must have an unlocked bootloader and fastboot in your path)
1. Download either the CWM touch recovery image or non-touch recovery image to your computer and rename it to "recovery.img".
2. Power off your phone.
3. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
4. Plug your phone into your computer using the standard USB cable.
5. Open the command prompt/terminal and navigate to the folder where your "recovery.img" is saved.
6. Type "fastboot devices" to make sure your phone is recognized; a serial number should show up on the screen.
7. Type "fastboot flash recovery recovery.img" and wait for the process to complete (should be quick).
8. You're done! Use the volume keys to select "Recovery" and boot into your new recovery!
ClockworkMod Recovery (Flashable ZIP method - easier)
If you are updating your recovery before flashing a ROM, these steps should ALL be completed PRIOR to flashing the ROM.
1. Download either the touch recovery flashable ZIP or the non-touch recovery flashable ZIP.
2. Place the ZIP file downloaded in step 1 on your internal storage/sdcard.
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Choose "Install update from sdcard"
7. Select "Choose file from sdcard"
8. Find the flashable recovery ZIP file you downloaded and install it
9. Back up to the root menu of recovery
10. Select "advanced"
11. Select "reboot recovery"
12. The phone should boot up into your new recovery!
Credits
As with most ROMs, I only did a small part to get everything together. Also, a note that should be made here is that when I am using someone else's file, I ALWAYS host files on the Shiny ROM server to ensure that I don't put any unnecessary stress on their servers. Any file, however, still belongs to and is accredited to its original creator as listed below:
Willyjay - For providing us with lots of amazing and innovative mods for the ROM!
Inmanster - Another great modder who we are fortunate to have here in the thread. He works in collaboration with Willyjay and his mods for many things, but also does some of his own unique mods!
Chainfire - For their SuperSU app and su binary, as well as the convenient ZIP update package, which was previously used and recommended. Check out their website, http://www.chainfire.eu/
Groupers - My new buddy who helped me out with a GPS issue that popped up in 4.2.
Google - Without their amazing staff and willingness to share the source code of their operating system, I wouldn't have been able to build this ROM! Of course, all of the Google apps are theirs, along with the Play Store and system apps. They really are the true owners of all of this.
Samsung - We all may have some mixed feelings about them, but in the end they gave us the amazing, hackable phone that is the Galaxy Nexus.
XDA - By providing such a great Android community, ROMs like this one are able to easily connect with users and get their work out there
Dev-Host - The file-sharing service with virtually no limits on sharing - kudos to them and their hard work. d-h.st
Koush and the ClockworkMod/ROM Manager Team - They make the best recovery that's been around for longest, and their constant updates allow us to keep making ROMs! Also, Koush's recently released open source Superuser control app is the best available and the one linked to in the thread. Thanks Koush! clockworkmod.com
Kevdliu - Huge thanks to this dev and their amazing quick settings mod!
The CyanogenMod Team - For a working implementation of DSPManager on Android which can be ported to any AOSP-based ROM! Without them and Bigwavedave25, the DSP manager mod would not be available! Be sure to thank them and to check out the CyanogenMod website! Also, for their feature-filled version of the stock Messaging app which is available as a mod for my ROM!
bouchigo - a user who has helped to make the CM10 Messaging app available as a mod for my ROM in conjunction with Willyjay for bringing it to my attention.
Schoat333 - A user who helped out Willyjay with the bubble styled MMS mods. The credit for the screenshots to go along with the mods goes to him!
Yarly - The most experienced admin I've ever had the pleasure of talking with, who taught me some new debugging tricks and answered some of my questions.
Razorloves - Another admin who helped me out with a few problems and answered a lot of my questions!
Tiny4579 - A kernel dev who also took the time to talk with me and answer a few of my questions.
Thanks to everyone for their hard work and sharing that work with others!
DISCLAIMER
Come on guys, it's a Galaxy Nexus, to what extent could it really get messed up? Nonetheless, in case someone flashes this then puts their phone in the microwave or something and tries to blame it on me, I am not directly responsible for anything that occurs, either negative or positive, from flashing this ROM to your phone. Despite that, I am posting in the spirit of the Android community, a community that I have embraced and belonged to for several years, and I would never try to hurt any of your innocent, beautiful phones. Also, none of the original source for Android belongs to me, nor do any of Google's apps. All preinstalled applications are property of Google, Inc. and I make no claim of ownership to them.
Okay that's about it! THE ROM DOWNLOAD LINK AND A SUMMARY OF ALL FILE DOWNLOADS CAN BE FOUND BELOW!
ROM Download & Changelog
ShinyROM_toro_aosp_080914-125720-signed.zip
MD5: 5844c6e48fb30bbafc976199c5c1effd
Fixes/Changes Included So Far
(older changes)
6/21/14 CHANGES
Updated to Android 4.4.4, KTU84P
8/9/14 CHANGES
Added system-side support for native screen casting
Added Italian translations for the Shiny restart menu (courtesy of XDA user lparcshinoda)
Switched to prebuilt version of CellBroadcastReceiver in an attempt to fix issues with it on toro
Mods
Before installing any of the packages below, please be sure to check out the mod installation instructions in the OP!
Key
To make mod installation more convenient, all mod links will now be color-coded based on the files they change. The key shows what each color corresponds with:
Red - SystemUI.apk
Blue - framework-res.apk
Purple - SystemUI.apk & framework-res.apk
Green - Other
If you install mods that are in the same color group, it is likely that they will overwrite each other. It is OK to overwrite a previously installed mod, but please note that the originally installed mod will no longer be there. If you want to completely revert to stock, flash the "Back to Stock ZIP" mod under the baldwinguy77 mod section. This mod replaces your SystemUI.apk and framework-res.apk files with ones from the stock ROM.
Developer-specific Mods
All of these mods have been provided by some really awesome mod developers who take the time to continue to make updated mods for my newest ROM builds. That being said, they have lives and can't always get the mods out right away, so make sure the date next to their name matches the build you're running! They usually are around the thread and are open to doing custom mods if you ask Be sure to thank them and check out the credits section for more info!
Baldwinguy77 (Updated for 8/9/14 build)
Back to Stock ZIP - Returns you to the stock version of the ROM by removing SystemUI and framework-res mods.
Stock kernel flashable ZIP - Overwrites any custom kernel you have installed with the stock kernel normally packaged with the ROM.
Inmanster (Updated for 3/9/14 build)
36 DPI Nav. Bar - Replaces the stock navigation bar with a smaller (height-wise), 36 DPI version.
Black Dash-style Softkeys - Replaces the stock navigation bar buttons with black, dash-style ones.
Blue Stock Softkeys - Replaces the stock navigation bar buttons with blue-colored ones.
Carrier Text Replacement - Replaces the carrier text on the lockscreen and pulldown notification shade with "Galaxy Nexus".
Extended Battery Framework Mods - Improve accuracy of battery level reporting for those using extended batteries.
2100 mAh (with Carrier Text Replacement mod)
3050 mAh
3800 mAh
5900 mAh (with No CRT-off Animation mod)
Grey Battery Percentage - Enables display of the current battery percentage in the status bar with grey-colored font.
InmanMod - A combination of the 2100 mAh battery, no CRT-off animation, carrier text, 36 DPI nav. bar, and white zenyth softkeys mods.
No CRT-off Animation - Removes the stock, default CRT-like screen off animation.
White Zenyth-style Softkeys - Replaces the stock navigation bar buttons with white, zenyth-style ones.
Universal Mods & Downloads
These mods have been compiled by myself, sometimes in conjunction with the modders above, to always work with any version of the ROM (but not necessarily any device). Therefore, you don't have to worry so much about these being up-to-date because they should always work. If that is ever not the case, simply PM me and we'll get it fixed This section also includes some other Verizon Galaxy Nexus related downloads such as the latest radios and bootloader. You can use these according to the installation instructions in the OP.
Universal Mods
AOSP Web Browser (for Android 4.4) - Installs the AOSP web browser with Chrome bookmark syncing for Android 4.4.
DSP Manager(for Android 4.4) -Installs the DSP Manager app along with the audio libs and configs important to running the service, allowing you to customize the audio equalizer of your device. At the moment, certain apps on Android 4.4 do not work with the modular DSP service.
ClockworkMod Images
Touch 6.0.4.3
Non-touch 6.0.4.3
ClockworkMod Recovery Flashable ZIPs
Touch 6.0.4.3
Non-touch 6.0.4.3
Chainfire's SuperSU Root Control App and ROOT Flashable ZIP (Works with 4.3 & 4.4)
Download (Latest version, v2.02)
Toro Radios[/size]
FK01 & FK02 Radios Flashable ZIP (Latest)
FF02 & FG02 Radios Flashable ZIP
Tuna Bootloaders[/size]
PRIMEMD04 Bootloader Flashable ZIP (Latest)
PRIMELC03 Bootloader Flashable ZIP
Thanks for your roms, they have been the daily driver on my wifes GN since you started posted them way back when.
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
kielby said:
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
Click to expand...
Click to collapse
Are you sure it's only when plugged into a wall charger? If that's true, it sounds like a hardware issue, but I think you probably just happened to notice it at that time. You may want to try out the 1/4 build as that one seems to work well for people with mobile data-related problems in the newer builds.
kielby said:
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
Click to expand...
Click to collapse
How did you flash the radios? Also are you using any mods/3rd party kernels? First step in fixing radio issues for me is to restore back to stock - this makes sure good radio files get installed then after allowing to settle for 24 hours I flash back to a custom Rom then checking without installing any mods for a day.
If unsure that radios flashed cleanly or having strange signal issues that make no real sense it is a good idea to try stock install.
hotrodwinston said:
How did you flash the radios? Also are you using any mods/3rd party kernels? First step in fixing radio issues for me is to restore back to stock - this makes sure good radio files get installed then after allowing to settle for 24 hours I flash back to a custom Rom then checking without installing any mods for a day.
If unsure that radios flashed cleanly or having strange signal issues that make no real sense it is a good idea to try stock install.
Click to expand...
Click to collapse
I flashed the zip files from this thread using CWM before flashing the ROM the first time. I'll try going back to stock for a couple of days to see if it fixes the issue.
To the previous poster, I'm pretty sure it's related to charger somehow. My wife started complaining that should couldn't reach me on my cell during the work day (hmm is this a *feature* or a bug?!). I was sitting at my desk during those times with my phone plugged in. I tried calling the Nexus from my desk phone and it wouldn't ring until I unplugged it. It only started after I flashed the new radios and ROM.
Thanks guys.
kielby said:
I flashed the zip files from this thread using CWM before flashing the ROM the first time. I'll try going back to stock for a couple of days to see if it fixes the issue.
To the previous poster, I'm pretty sure it's related to charger somehow. My wife started complaining that should couldn't reach me on my cell during the work day (hmm is this a *feature* or a bug?!). I was sitting at my desk during those times with my phone plugged in. I tried calling the Nexus from my desk phone and it wouldn't ring until I unplugged it. It only started after I flashed the new radios and ROM.
Thanks guys.
Click to expand...
Click to collapse
By the way I reflashed the 4.1.1 (JRO03O) radios from radio thread without changing anything else and the problem seems to have gone away.
What kernel should I use with this ROM to get the best performance/battery life combo. Link please!
Sent from my 2013 Kindle Fire HD
Is an upgrade to KVT in the works?
UPDATE -- I'm running the latest version with the latest franco and Xposed Framework and - wow. Rock stable, fast and melted chocolate smooth (boom - trademarked.) I don't know why I haven't done this sooner. This is all I need for awhile. Truly happy with my GNex at this moment haha.
RoxRedEye said:
Is an upgrade to KVT in the works?
UPDATE -- I'm running the latest version with the latest franco and Xposed Framework and - wow. Rock stable, fast and melted chocolate smooth (boom - trademarked.) I don't know why I haven't done this sooner. This is all I need for awhile. Truly happy with my GNex at this moment haha.
Click to expand...
Click to collapse
Hey there! I'm sorry, somehow I missed your post earlier! Anyways, glad to hear you're liking the ROM so much There is an updated build available as of today so check the download post. More info is coming in a few seconds
3/9/14 Build Information
Hey there everyone! It seems like it's been awhile since the last time I got make one of these new build posts, and I have to say it feels good to be able to do it again! I first have to apologize for my absence both in terms of development and communication in the thread. I'm getting close to the end of my sophomore year in college, and let's just say it has been keeping me extremely busy. I don't mind it, but I just wish it still left more time for me to do Android-related things! Luckily, I had a whole week off to catch up on a lot of things, including Shiny ROM development. So with that, we have a new build ready to go that includes a very minor update to the AOSP base of the ROM as well as some not so minor updates to the telephony stack. What this means is that mobile data and voice performance/reliability may have some big improvements in this build. We didn't get a chance to do a wide-scale test with these changes, and they're only in the master branch of AOSP, but after reviewing the code I'm hopeful that they'll bring improvements for us. That being said, be sure to leave your feedback here on the thread so we know how it's working! If you experience any problems, try to grab a logcat and let us know about them so we can try to get everything straightened out! So after reviewing the other information and installation instructions below, head over to the download post to grab the new build!
I also want to take this opportunity to point out that Shiny ROM has a new website! For now, the URL/domain is still http://shinyrom.goofball.org/ to stay consistent. The website has a lot of information about Shiny ROM as well as some future plans. It also lists details for the newest build of Shiny ROM along with download links, etc. I'm hoping that this website serves as a good platform for Shiny ROM to grow as we can now deliver a lot of information without having to worry about it getting buried in the forum and whatnot. So check that site frequently for Shiny ROM news and updates as well as information about new builds! There is also a contact form there for everyone to leave their suggestions, report bugs, etc. I hope you all like it!
(You can still access all of the Shiny ROM files here.)
Thanks to everyone for your continued support of myself and Shiny ROM!
Installation Instructions
Download desired ZIP files (ROM, SuperSU*, mods, etc.) and place on internal storage.
Reboot to the latest version of your preferred custom recovery (CWM or TWRP).
Wipe cache.
Wipe dalvik cache.
**OPTIONAL** Wipe data/factory reset (will erase user data like apps and saved games, etc., but may fix strange bugs).
Flash ROM.
**OPTIONAL** Flash other desired ZIPs (SuperSU, mods, etc.).
Reboot.
Enjoy!
*As of 3/9/14, the latest version of SuperSU is v1.93.
baldwinguy77 said:
Hey there! I'm sorry, somehow I missed your post earlier! Anyways, glad to hear you're liking the ROM so much There is an updated build available as of today so check the download post. More info is coming in a few seconds
Click to expand...
Click to collapse
No worries. Thanks for the reply and thank you for your hard work bringing us a stable stock KitKat. Glad I have extra batteries with me - gonna download and flash asap.
Hey @baldwinguy77, can't access rootz right now, but was systemui.apk updated for today's build? I have a home cooked mod from last version that I'd like to use. Thx
ART isn't sticking when I change from dalvik. I flashed on top of the last build. Did not do a full wipe yet.
Sent from my Galaxy Nexus using Tapatalk
asilentcivilian said:
ART isn't sticking when I change from dalvik. I flashed on top of the last build. Did not do a full wipe yet.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
full wipe did the trick. thanks for keeping this ROM alive!
Sent from my Galaxy Nexus using Tapatalk
klobkelosh said:
Hey @baldwinguy77, can't access rootz right now, but was systemui.apk updated for today's build? I have a home cooked mod from last version that I'd like to use. Thx
Click to expand...
Click to collapse
Hmmmm I would just give it a try, I think it will probably work fine especially if it only modifies SystemUI
asilentcivilian said:
full wipe did the trick. thanks for keeping this ROM alive!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Glad to hear it! Thanks for your support!
baldwinguy77 said:
Hmmmm I would just give it a try, I think it will probably work fine especially if it only modifies SystemUI
Click to expand...
Click to collapse
Yes it worked fine, thanks for the response. Unfortunately, this build is not very nice to my battery
klobkelosh said:
Yes it worked fine, thanks for the response. Unfortunately, this build is not very nice to my battery
Click to expand...
Click to collapse
Glad to hear it! I would give it some time before making any conclusions; charge it up tonight, grab it in the morning and see how it is with normal use
If you want, you can put the APN refresh delay back to its value from the previous build. To do this, you need to be rooted so that you can edit the build.prop. You simply have to remove this line:
Code:
persist.radio.apn_delay=5000
I don't think it should be making a big difference, but that's the only change that could (in theory) have some effect on battery life. Of course, removing that line may come at the price of having longer/trickier data handoffs. Unfortunately, Verizon's network certainly isn't making it easy for us to give everyone good battery life and good data handoffs
baldwinguy77 said:
Glad to hear it! I would give it some time before making any conclusions; charge it up tonight, grab it in the morning and see how it is with normal use
If you want, you can put the APN refresh delay back to its value from the previous build. To do this, you need to be rooted so that you can edit the build.prop. You simply have to remove this line:
Code:
persist.radio.apn_delay=5000
I don't think it should be making a big difference, but that's the only change that could (in theory) have some effect on battery life. Of course, removing that line may come at the price of having longer/trickier data handoffs. Unfortunately, Verizon's network certainly isn't making it easy for us to give everyone good battery life and good data handoffs
Click to expand...
Click to collapse
I'll take that under consideration, but man it was really killing me. Following new rom flash, for everything set up, charged up to 100 percent. Good. Drive to dinner, 30 mins, in and out of 4g and 3g, battery at 80 percent. After 2 hour dinner on 3g, 60 percent. Back home 40 percent, lots of hand offs. She's nearly dead now and I haven't even used her tonight. I love this ROM, but she's not right...