Related
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
I have an A100 that I flashed a very old version of Flex Reaper to right when ICS came out. So the complete setup looks like this.
CWM (very old version)
Android 4.0.3
Kernal 2.6.39.4+
Build Number
FLEX-100-REAPER-R3.1
Also has Crossix memory swap mod.
I set it up many months ago, and it has run great ever since.
Until, my son decided to pull out the SD card while it was running. @#%@[email protected]#^$#
Now, it won't let me update, or install anything. It says there is not enough storage room left even though it shows 18G of free space. I am guessing things got corrupted when the boy pulled the card out.
So, I have two questions.
1. Whats the safest way to dump this sucker and reload it from scratch?
a. Are there any gotcha's I need to look out for? (like removing crossix's mod before booting back into CWM)
2. I see there has been a lot of new recoveries, rom's, and kernal's put out for the A100 since I stop messing with mine. I'd gladly take some advice on setup's. I am much more interested in stability than extra features, or speed. If my son hadn't pulled that card, and corrupted my setup I would have never messed with it again because it just flat worked well as it was. I do however have an interest in Jelly Bean if there is a solid rom built at this time. I saw the CM10 threads, but there is so much back and forth, I can't get a good feeling it's solid yet.
Thanks ahead of time,
You can boot in cwm correct?
G2x-temasek CM7 build135.3 w/faux 054 kernel
justjackyl said:
You can boot in cwm correct?
G2x-temasek CM7 build135.3 w/faux 054 kernel
Click to expand...
Click to collapse
Yes,
Have you tried removing the crossix mount swap and reapply?
From what I am gathering, you are able to boot up normally, and have full functionality, and can run apps, but just cannot do anything new beyond that?
Such as installing, updates as you said. But can you open up apps that run before the "incident"?
Yes I can run everything already on the device. The only issues at this time are existing apps can't be updated, and new ones can't be installed.
I haven't tried to re-apply the mod swap. I figured the safest route long term would be a complete wipe, and start from a newly flashed rom. Might not be necessary, but I just figure safer long term. I am not afraid to re-flash it. It's still rooted, and unlocked. I just know it's better to be safe and ask questions first. I wouldn't be the first guy to brick an A100, it's not the friendliest device to work with.
The second question is based on the fact that if I am going to re-flash it, I may as well move to a more current rom if it is as stable as the rom I am coming from.
Sorry if I am a PITA, but thanks for helping out
BcWilk said:
Yes I can run everything already on the device. The only issues at this time are existing apps can't be updated, and new ones can't be installed.
I haven't tried to re-apply the mod swap. I figured the safest route long term would be a complete wipe, and start from a newly flashed rom. Might not be necessary, but I just figure safer long term. I am not afraid to re-flash it. It's still rooted, and unlocked. I just know it's better to be safe and ask questions first. I wouldn't be the first guy to brick an A100, it's not the friendliest device to work with.
The second question is based on the fact that if I am going to re-flash it, I may as well move to a more current rom if it is as stable as the rom I am coming from.
Sorry if I am a PITA, but thanks for helping out
Click to expand...
Click to collapse
Nah dude, your fine. Kinda why I hang around here.
In this case, I would not mess with trying to flash a new recovery.
As for CM9 or 10, I'm a strong advocate for 10. Others will argue. I had a lot of app compatibility issues with CM9.
That being said, your best bet for stability is CM10 09/02/12 build. It is the currently longest running build with few complaints. Pio has been kind enough to resume development for the A100 and has released an updated source build to 11/08/12, its what I am running and runs great.
Stock kernel is not bad, godmachines v2.0 kernel offers a few more tweaking options and is very good as well.
Download your flavors of ROM and kernel and put on your external SD. I'm sure you know what to do from there.
BTW, for cm/ICS. Flex-relix is most popular.
Iconia A100 CM10 PRIVATE BUILD, TabletUI, Updated to 11/03/12 Source; godmachine v2.0 kernel
I agree. Take your pick of the popular ROMs on the first dev page. Full wipe and reflash the one you pick, as per the ROMs instructions. I would backup any needed data off the microsd card and reformat it also, NTFS.
Thanks goes to both of you.
I was trying to get a grasp on if I need to upgrade to a new rom or not. It's a tough question to ask on what is basically a developers forum as this is a family tablet. Stability is much more of a concern than raw performance. I along with most others here always wants the latest on our devices, but when the tablet in question basically belong to the wife and kids, obviously stability take priority. I travel too much to deal with "issues". No digg to developlers. Bug's are just part of the process I understand. I test software for a living. I just want to leave that part of my life at work. We all appreciate what you do here.
Glad to hear that there is not much point in upgrading what already works from a recovery standpoint, but CM10 is sounding like a solid rom. I have it on my gnex, and it is just simpler to keep everything the same. I look forward to the update
Thanks everyone.
Ok, so I did a little reading to get caught back up on how to work with this device. I just wanna make sure I have the correct order, and files I need to get this done right the first time.
1. Delete the "install_recovery.sh" file that is there because of crossix swap mod.
2. Boot into CWM recovery, and wipe basically everything. (there is nothing on the tablet I need)
3. Flash the lastest CM10 found here http://droidinsider.com/download.php?folder=a100/ ? I think?
4. Flash kernal ( I can't find a link to download "godmachines v2.0 kernel" ) any help?
5. Flash gapps latest link I can find is here http://forum.xda-developers.com/showthread.php?p=29236322 is that right?
6. This thread seems to cover the rest well. http://forum.xda-developers.com/showthread.php?t=1931085
That seem about right?
BcWilk said:
Ok, so I did a little reading to get caught back up on how to work with this device. I just wanna make sure I have the correct order, and files I need to get this done right the first time.
1. Delete the "install_recovery.sh" file that is there because of crossix swap mod.
2. Boot into CWM recovery, and wipe basically everything. (there is nothing on the tablet I need)
3. Flash the lastest CM10 found here http://droidinsider.com/download.php?folder=a100/ ? I think?
4. Flash kernal ( I can't find a link to download "godmachines v2.0 kernel" ) any help?
5. Flash gapps latest link I can find is here http://forum.xda-developers.com/showthread.php?p=29236322 is that right?
6. This thread seems to cover the rest well. http://forum.xda-developers.com/showthread.php?t=1931085
That seem about right?
Click to expand...
Click to collapse
Here you go bud. It's always good to have a stockpile. Soooo...
CM10 4.1.2 Sources 11-8-12
CM10 4.1.1 Sources 9-2-12
Modded Stock ICS ROM (Acer Modded ROM)
FLEX-A100-REAPER-RELIX_Rev2
So choose your flavor of ROM, and than you can use the stock kernel, or the highest recommended by linuxsoxiety aka godmachine: godmachine v2.0 kernel
Gapps (Source Dependant)
4.1.1 Source Gapps
4.1.2 Source Gapps
Stinky ICS Gapps
You won't need to mess with crossix mount swap removal, will be removed upon wipe.
Boot into CWM. Now I use TWRP recovery (although I use CWM on my G2x), so the terms might differ slightly, but I think you'll understand:
Perform:
Factory/Data Reset (wipe)
Format/Wipe Cache
Format/Wipe Dalvik Cache
Format/Wipe System (in CWM, goto mounts and select format /system)
Just to be safe, I would:
Format/Wipe Internal Storage/SD
Than flash from external SD
ROM
Kernel (if not using stock)
Gapps (proper for source?)
Than make sure you follow the ten min, reboot, ten min rule. I'm sure you know what I mean from your studying.
Should be good.
Although, I recommend using GL to SD app in place or crossix mount swap. Takes a lil more effort to use, but, if there is an accidental SD pull, it won't affect the system.
Hope this helps.
Up and running.
Can't get that swap mod to run for some reason, I'll have to look into that when I am not drinking.
The launcher on CM10 is a little buggy, but other than that it seems to run well. Thanks for all the help
many thanks
BcWilk said:
Up and running.
Can't get that swap mod to run for some reason, I'll have to look into that when I am not drinking.
The launcher on CM10 is a little buggy, but other than that it seems to run well. Thanks for all the help
many thanks
Click to expand...
Click to collapse
Use apex launcher (its talked about in my tips thread)
And gl to sd in place of swap mount
I think the mount points are different than ice and swap wont work on jb
G2x-temasek CM7 build135.4 w/faux 054 kernel
justjackyl said:
Use apex launcher (its talked about in my tips thread)
And gl to sd in place of swap mount
I think the mount points are different than ice and swap wont work on jb
G2x-temasek CM7 build135.4 w/faux 054 kernel
Click to expand...
Click to collapse
They are but symlinked for backward compatibility. I also put up a jb version awhile back.
That said it does pose potential issues if its yanked hot as you saw.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
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...
Note: This should go without saying since this is a very early beta build, but I'm not responsible for any direct, or indirect damage done to any phone or accessories from flashing/ using this rom.
Also please read the entire op before installing/posting.
Welcome to:
THE ARKO PROJECT
About the Rom:
I started this whole project when I had a G5, and development was still slow. I met someone who was kind enough to get me started, and give me the basic info I needed to start my journey in development. I had always wondered if I could, but never really knew where to start.
Seeing the lack of development for such a great device. I decided to take matters into my own hands (however inexperienced they may be). So far I've created basic tweaked stock roms for the G5 & G Stylo. I never released them however because I didn't make it too far. Because the devices ended up being damged (which is unusual for me).
Anyway that brings us to here & now. This rom is also very basic (for now). I plan however to add as many features as possible & plausible. While keeping it fast, smooth, and reliable. Rest assured I test every build for at least a couple of days before posting them here. Anyway onto the good stuff.
Source: Pulled from stock MM 6.0 30d
Boot img: Pulled from stock MM 6.0 30d (changed to insecured).
Android ver: MM 6.0 30D
Features:
Rooted (Sytem install)
Wifi, data, bluetooth etc. all working
Dpi set to 560
Debloated (More apps removed in future updates)
Busybox
All app multiwindow support enabled by default
Quick power on
Auto rotate in homescreen (tested with Nova Launcher)
Faster video streaming
Increased wifi scan interval
No ring delay
Enabled Adoptable storage
Jpeg quality 100% plus other media enhancements
Disabled error reporting
And some more I can't think of....
Planned features (feel free to suggest some):
4 way reboot
Volume button orientation mod
Possibly aroma installer
That's all I can think of off the top of my head but there is more.
I also plan to make a few color ui themes as well.
For example
Red & Black
Blue & Black
Green & black
Etc. Etc.
Feel free to request different colors as well (doesn't mean it will neccesarily happen, but you can ask
Install instructions:
*Make sure the version of TWRP you are using supports updater-scripts! This is very important! If it doesn't the rom will not flash! I'm using the latest version of multirom TWRP, and can confirm the rom flashes just fine.
1. Make a TWRP backup (optional, but heavily suggested)
2. Download and place zip on sd card
3. Do a full wipe
4. Install zip
5.Enjoy
Note: updates are disabled two minutes after booting the rom. No user action is required. The old method I had tried didn't actually work. Got the ota again a week later. However it is 100% fixed now.
New DL link: https://drive.google.com/file/d/0B1bdSH2f5u2UMzdBUlkzcTFBMU0/view?usp=drivesdk
I don't know if this would work since I have not really put much research in to it, but could you make the folder where the update is downloaded to read-only?
BoredKender said:
I don't know if this would work since I have not really put much research in to it, but could you make the folder where the update is downloaded to read-only?
Click to expand...
Click to collapse
Probably not a good idea. Folder also has a few log files too. If all else fails then I'll give it a shot. I also had a thought that perhaps it isn't named anything like lgdmsclient.
After some sleep I've got a couple days off work so I'm gonna try to get multi rom working. (Haven't used it since kk early android L. That way I can just go down the list remove lg services apk's one by one and hope that either multirom or twrp could save me from a brick if anything goes wrong. Right now I have been using the delete update.zip/reboot. To keep the zip off my phone. Only problem is it takes a while for the system to realize an update is available after that. So It would be easier to remove an apk, build, flash, repeat until I find the culprit. MR will really help though as it'll save a lot of time between flashes. I really do appreciate the help/input though.
Also I've randomly found myself booted into twrp and the update try to install itself. Just luckily had zip verification on so it didn't flash.
Removed build.
Deleted
The Rom now has it's own thread in Tmo Android development located here:https://forum.xda-developers.com/tm...t/rom-arko-project-g3-edition-6-0-mm-t3555919
Moderater if you will please, close this thread. Thanks.
Thread Closed.
What is the most recent and stable ROM for the Gio GT-S5660M ?
Importantly it would be to have a ROM that is new enough to work with modern apps, which often require at least android 4 or 5. Also, I would prefer to avoid GApps and go with F-Droid and Aurora Store, and the latter seems to require android 5+.
I have a couple of these lying around and thought they might make good WiFi IP phones with a SIP client. With a modern ROM and a new replacement battery (remember those?!) they could have new life.
Is this workable? This phone is so cute and compact that I really don't want to get rid of it if it can be used for something.
It has an armv6 cpu wich is no longer supported on android the last supported version was kitkat 4.4.4, this is the latest rom available for the device: https://forum.xda-developers.com/t/rom-cyanogenmod-11-final-05-08-2015.3066771/
It can still be used to listen to fm radio etc, although it no longer has browser support, so it won't work on all sites. I have one too and think it is a very nice tiny phone but I am affraid you are going to have to buy a newer phone for daily usage.
@J.V.B. Thank you for your reply!
Does that rom work well? There is some conflicting feedback in the thread. Which is the correct rom (msm vs msm7x27)?
How can the rom be flashed from the stock non-rooted state? There aren't instructions in that thread, though there is a post saying to use this CWM recovery (requires root?): https://forum.xda-developers.com/t/...-11-wip-alpha-1.2582642/page-27#post-54754255
Good point, the browsers all seem to require android 5+.
Currently on stock (android 2.3.4) I am using CSipSimple and that's working reasonably well. A newer rom might give a bit more flexibility in settings (eg. I can't figure out how to enable wifi on boot and autostart CSipSimple on 2.3.4), and maybe just maybe a few apps through F-Droid.
Both versions work they are just different kernels, I forgot what the advantages over each other were, I think the 7x27 version was more buggy but I am not sure, I recommend checking out both.
That cwm is indeed the only correct version, newer or older ones can't install this rom. I think to install the cwm you just have to boot to recovery (home button + power button and keep the home button pressed in.) and apply update from sd card and select that cwm(wrong: see edit). After this you boot to recovery again and now you factory reset and flash the rom. You also need to flash the camera patch after you flash the rom, otherwise you won't be able to record using the camera. I am not responsible for anything that happens, custom roms are always a risk. Hope it works for you
edit: You need to be rooted and on android version 2.3.3 or higher to install cwm: https://forum.xda-developers.com/t/...mwares-mods-tips-tricks.1397120/post-20397988
I also recommend using link2sd:
https://www.apkmirror.com/apk/bulent-akpinar/link2sd/ .
For instructions, follow this guide but scroll all the way down to the for cwm only users method: https://awanstuff.wordpress.com/201...ink2sd-in-any-android-phone-with-screenshots/
Link2sd will fully transfer apps to sd card instead of only the package. I changed the settings to make sure auto link is on and install location is set to sd. You can also transfer already installed apps to the sd and a lot more.
After this maybe post about how well the gio is running for documentation.
Some extra tips: the built in root is handy and if you enable developer options in the rom you will also get a performance menu in settings where you can make it run faster.
Thanks, I plan to try installing CWM and the CM11 rom soon. From searching it looks like "MSM7x27" refers to the Snapdragon S1 processor version:
List of Qualcomm Snapdragon systems on chips - Wikipedia
en.wikipedia.org
The Gio has a MSM7227 https://www.gsmarena.com/samsung_galaxy_gio_s5660-3741.php so maybe the MXM7x27 version is the correct one? I don't know if the plain "MSM" version rom is referring to a specific or generic designation.
Thanks for the tip about link2sd. It's nice to have that option since the very limited storage on this phone is maybe the biggest weakness. I'll see if I need it, since I don't plan to install many apps at all, rather I want to maximize battery life.
I got 1500 mAh batteries from Polarcell and in airplane mode with wifi and just CSipSimple running on the stock rom it lasts over 7 days in "standby". Let's see a modern phone do that!
I think this is the msm7x27: https://github.com/androidarmv6/android_kernel_samsung_msm
and this is the msm: https://github.com/HerroYou/android_kernel_samsung_msm/commits/cm-11.0
The msm just adds overclocking but might be more unstable and it also breaks the backlights. I don't know which is the best one. I recommend if the msm7x27 doesn't work well enough to try the msm and see if that gives you better results.
Also just so you know I have not found any gapps that work yet.
Also when you before you reset your device and flash the rom. Right after the cwm install I recommend fully backing up your device to an sd card so you can just go back any time you want.
I tested csipsimple and it works. If you want better battery life, the power menu that gets enabled after you unlock dev mode might allow you to downclock the cpu to get even more battery.
HerroYou has a mxm7x27 repo too: https://github.com/HerroYou/android_kernel_samsung_msm7x27
It would have been so helpful for them to leave a couple of notes about the difference. It seems like these terms might be common enough in the dev circles that they didn't think it needed explanation.
About gapps, I wasn't interested anyway, so I'll take its lack as a "feature". Not sure if microg is feasible. In any case, side-loading and F-Droid are ok for me on this device.
And yes, a backup after installing CWM but before the rom installation is essential. No intention to skip that.
oh I see the msm2x27 kernel is based on linux kernel 2.6.37 and the msm kernel is based on linux kernel 3.0
I have been reading up on things and see that most threads say you must be rooted and above version 2.3.3 to flash the cwm recovery: https://forum.xda-developers.com/t/...mwares-mods-tips-tricks.1397120/post-20397988
I am sorry I forgot about it. It really has been a long time since I installed it
Nice catch. In that case it is tempting to try msm with the more recent kernel 3.0.
Is there no way to flash CWM without root?
If not, is this post on rooting still valid? https://forum.xda-developers.com/t/...wares-mods-tips-tricks.1397120/#post-20397899
It is to root the stock rom so it should still work since the stock rom hasn't been updated in forever. I would also recommend reading the rest of the beginning of that thread to make sure you didn't miss anything because while mostly outdated, the things like rooting the stock rom and installing cwm is still the same.
I would also just to be sure use the cwm version in the thread: https://forum.xda-developers.com/t/...mwares-mods-tips-tricks.1397120/post-20397988 and then update it to the new version.
I started downloading the resources needed for this project, but the link (actually the whole hosting site) is dead for the root gb updated.zip hmm...
There are a few other files for rooting uploaded by random forum members:
Big thread For New Users (Rooting , Flashing,Firmwares,Mods,Tips, Tricks)
This thread is collection of all available data/tutorials about samsung galaxy gio,so it may save time for you guys. -------------------------------------------- For Simpilfication each post will contain single tutorial, Main post will only used...
forum.xda-developers.com
Big thread For New Users (Rooting , Flashing,Firmwares,Mods,Tips, Tricks)
This thread is collection of all available data/tutorials about samsung galaxy gio,so it may save time for you guys. -------------------------------------------- For Simpilfication each post will contain single tutorial, Main post will only used...
forum.xda-developers.com
A bit scary, but not sure there's another choice. It would be ideal if the recovery and rom could be flashed without root.
I found a rooting tutorial with a download on this post: https://forum.xda-developers.com/t/...kernels-recoveries-scripts-tutorials.1623393/
It is under the tutorials section.
Again I am not sure if you have to root to be able to install cwm but I wouldn't take any risks.
Also before you install anything is there anything you want me to confirm whether it's working or not on this rom?
I got youtube to work through newpipe and mx player although you have to download the videos because at low resolutions newpipe loses audio when sending to external video player.
Thanks, that's a nice resource thread. In the second page of the rooting thread someone has a modified version of the file for Bell S5660M variant, which is what I have, so I suppose I'll use that. I would prefer to go with CWM and CM11 without rooting, since I don't need or want root, but as you say it could be risky...
Oh, it would be great if you could verify on CM11 if 1) wifi can start automatically on (re)boot (eg. if it was on when powering off or rebooting, 2) if programs like CSipSimple can be autostarted on boot. That's all I really need right now to make it useful as an wifi IP phone.
I don't know how I would go about autostarting apps on boot. Is there a setting or a test for that? The wifi stays enabled after reboot.