Develop Bugs

Developing A Ramdisk (Unpacking & Repacking Boot.img)

I was hoping some of the kernel devs can help me with a quick question. I am familiar with unpacking and repacking boot.imgs for the Droid but not for the Evo, I usually use the method found here. Is there an alternate method or even some perl scripts that will make the job as easy as it is for the Droid? Note: I am not trying to compile a boot.img, I just want to be able to edit the ramdisk of existing ones. Thanks in advance!

BuglessPete said:
I was hoping some of the kernel devs can help me with a quick question. I am familiar with unpacking and repacking boot.imgs for the Droid but not for the Evo, I usually use the method found here. Is there an alternate method or even some perl scripts that will make the job as easy as it is for the Droid? Note: I am not trying to compile a boot.img, I just want to be able to edit the ramdisk of existing ones. Thanks in advance!
Click to expand...
Click to collapse
reading through the tutorial you linked to, i see perl scripts and directions. is there a certain part of that tutorial you've used on the EVO and have had trouble or its resulted in some kind of error? guess i didn't catch what isn't working for you?
edit: reviewing the tutorial again, i have been wondering which partitions are which on our phone? boot mtd2/3 ? recovery mtd2/3? i know system is mtd4 and data is mtd5 ...
once i know which partition for sure is boot, it might be worth while for me to grab the kernel and post up the stock ramdisk as a starting point for all those looking to do simple kernel mod'n ...

Not sure why this got moved out of development section, as it is related to developing a boot.img although it was a question.
I used the unpack perl script and it threw an error. I will also try the split script when I get off work.

Sorry to resurrect a dead topic, but I'm looking into this as well, and I haven't been able to modify a ramdisk successfully (I'm basically looking to set ro.secure=0 in default.prop). I typically use the same procedure as Pete outlined in the link, but using that for the EVO results in a hang at the bootscreen. (the white HTC EVO 4G screen seen on boot) Any help would be appreciated.

Resurrecting this topic once again.
ADB functionality is broken in Sense FroYo roms, maybe all froyo roms. I can communicate appropriately through fastboot and through ADB in Recovery, but not when running.
The /sbin/adbd process isn't running like it is on other ROMS, such as eclair and gingerbread.
Following this link:
http://code.google.com/p/android/issues/detail?id=9437
I found that some nexus one devs had the same issue, and had to replace the adbd process on the ramdisk with one from another build that worked in froyo.
Following this guide that everyone links to:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I was not able to use the included unpack/repack perl scripts without modifying them. It appears that the Evo has another file at the end and that script wasn't meant to handle that. Others commented out that line that kills it, I did so, but apparently that script doesn't grab the header appropriately, and the repack doesn't work appropriately for another. I get the white boot screen and it stays indefinitely.
I took the Boot.img and went through a hex editor to do it manually, and wasn't able to get the ramdisk to unzip correctly.
I'm at the end of my rope, and need someone else who's much smarter than I am to assist in what steps to take next.
I am developing a new app, and desperately need to have ADB working inside FroYo. I would run CM7, but it doesn't work right all the time, and has bad battery life for me. I use my phone for business too, so it all has to be stable.
Any ideas? I have lots of this stuff available as I've been working on it for the past couple days, so I can post links and the like to help bring anyone up to speed with what I've done. Thanks a crap-ton in advance. If you can help me get this working, I will send you a donation!
Also, this will fix ADB in all Froyo roms too, so you'd be doing the community a great favor as well.
-Nathan

kmartburrito said:
Resurrecting this topic once again.
ADB functionality is broken in Sense FroYo roms, maybe all froyo roms. I can communicate appropriately through fastboot and through ADB in Recovery, but not when running.
The /sbin/adbd process isn't running like it is on other ROMS, such as eclair and gingerbread.
Following this link:
http://code.google.com/p/android/issues/detail?id=9437
I found that some nexus one devs had the same issue, and had to replace the adbd process on the ramdisk with one from another build that worked in froyo.
Following this guide that everyone links to:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I was not able to use the included unpack/repack perl scripts without modifying them. It appears that the Evo has another file at the end and that script wasn't meant to handle that. Others commented out that line that kills it, I did so, but apparently that script doesn't grab the header appropriately, and the repack doesn't work appropriately for another. I get the white boot screen and it stays indefinitely.
I took the Boot.img and went through a hex editor to do it manually, and wasn't able to get the ramdisk to unzip correctly.
I'm at the end of my rope, and need someone else who's much smarter than I am to assist in what steps to take next.
I am developing a new app, and desperately need to have ADB working inside FroYo. I would run CM7, but it doesn't work right all the time, and has bad battery life for me. I use my phone for business too, so it all has to be stable.
Any ideas? I have lots of this stuff available as I've been working on it for the past couple days, so I can post links and the like to help bring anyone up to speed with what I've done. Thanks a crap-ton in advance. If you can help me get this working, I will send you a donation!
Also, this will fix ADB in all Froyo roms too, so you'd be doing the community a great favor as well.
-Nathan
Click to expand...
Click to collapse
Adb does work in sense froyo roms. It works on mine and I nandroid between my daily sense rom and my dev sense rom when I need to. I prefer to use adb through recovery but I have successfully adb pulled and pushed com.htc.resources from the framework while my device was running just last night. I have also not changed the adb file in the ramdisk (even though I could if I wanted to) so I doubt adb not working in sense roms is the issue unless the rom maker did in fact mess with the ramdisk and inadvertently messed something up.

lovethyEVO said:
Adb does work in sense froyo roms. It works on mine and I nandroid between my daily sense rom and my dev sense rom when I need to. I prefer to use adb through recovery but I have successfully adb pulled and pushed com.htc.resources from the framework while my device was running just last night. I have also not changed the adb file in the ramdisk (even though I could if I wanted to) so I doubt adb not working in sense roms is the issue unless the rom maker did in fact mess with the ramdisk and inadvertently messed something up.
Click to expand...
Click to collapse
It's not working for me on Fresh 3.5, Evio 1.8, or Mik's Z rom that was just released. I can go back to my PC36IMG.zip (eclair) or CM7, and it works just fine.
I've tried stock and custom kernels, to no avail. I'm absolutely NOT the only person with this issue. As you can see in the post above, Nexus one users are having the same problem, as are tablet owners with Tegra 2 chipsets, etc.
So, let me ask you, what ROM are you using? Is that the only ROM you've used since upgrading from Eclair?
I am at a loss for why this isn't working. As I said before, the /sbin/adbd process is NOT running, and I get a segmentation fault when attempting to launch it. It works fine on CM7 and Eclair, but NOT froyo. Not brand new, unaltered ROM installs, nothing. Whatever it is, the only thing in common is Sense and FroYo.
Thanks for responding, I think at this point I just need people to provide other things to look at that I haven't thought of. I'd still like to learn how to unpack and repack though, it could be a last resort.

kmartburrito said:
It's not working for me on Fresh 3.5, Evio 1.8, or Mik's Z rom that was just released. I can go back to my PC36IMG.zip (eclair) or CM7, and it works just fine.
I've tried stock and custom kernels, to no avail. I'm absolutely NOT the only person with this issue. As you can see in the post above, Nexus one users are having the same problem, as are tablet owners with Tegra 2 chipsets, etc.
So, let me ask you, what ROM are you using? Is that the only ROM you've used since upgrading from Eclair?
I am at a loss for why this isn't working. As I said before, the /sbin/adbd process is NOT running, and I get a segmentation fault when attempting to launch it. It works fine on CM7 and Eclair, but NOT froyo. Not brand new, unaltered ROM installs, nothing. Whatever it is, the only thing in common is Sense and FroYo.
Thanks for responding, I think at this point I just need people to provide other things to look at that I haven't thought of. I'd still like to learn how to unpack and repack though, it could be a last resort.
Click to expand...
Click to collapse
For my daily I use a rom based on miks eng base that I rooted and edited myself. For my dev rom I use joeykrims odexed rom that I deodexed. I also use a barebones 3.70 taken directly from the ruu, rooted and edited myself as well as deodexed it.
My two dev roms provide me with at least some sort of variables since joeykrim adds some extras to his rom.
In all three roms, the only thing I changed in the ramdisk is the kernel I compile and use (htc15 compiled to have sbc, havs, undervolt, etc.).
It could be (possible though unlikely since others do have success with adb on the roms you mention) that the ramdisk may have been edited in a way that prevents adb from starting in the init files.
Again just last night, both on my replacement evo and my wifes evo (she runs what I put on her evo which is usually a more polished version of mine) I used adb while the devices were running to pull some system apps and do some editing and then pushed them back. These are both sense based 3.70 roms using the same kernel.
Your situation is puzzling me at the moment since you said it works fine on cm7 and eclair but not on any sense based froyo roms. I would have drawn the same conclusion but since I personally can use adb on a sense based froyo rom I have to think the problem lies somewhere else and not solely on froyo. I'll try to duplicate this situation though I don't think I can without seeing what your device looks like.

[SPRINT][CDMA][FROYO][GUIDE] Overcome/KhasMek 1.4ghz OC FAST (4.30.2011)

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.

[Q] damn kids

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

[ROM][AOSP](8/9/14) Shiny ROM: OTA-Like, Stock Android [4.4.4] [KTU84P]

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...

[Q&A] [ROM][UNOFFICIAL] CyanogenMod 11 Nightlies / Releases [M11]

Q&A for [ROM][UNOFFICIAL] CyanogenMod 11 Nightlies / Releases [M11]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

my desire hd cant boot when i swich to ART mode
Mustaavalkosta said:
General:
These are UNOFFICIAL CM11.0 Kitkat Nightlies / Releases brought to you by AceEnablementProject and TeamCodefire as a continuum to CM10 and 10.1 nightlies. Builds are generated automatically each night. Process starts around 00:30 PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Latest 12 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
TeamCodefire (for build server and hosting, priceless)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
AceEnablementProject
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies / Releases [BasketBuild mirror]
Download gapps from here. Pico/Nano/Micro recommended, Mini/Full/Stock doesn't fit in our system partition after the ROM has been installed.
Put the files on SD card.
Reboot to recovery.
Do factory reset (ie. format /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-11-YYYYMMDD-UNOFFICIAL-ace.zip
Flash gapps zip
Remember to reflash boot.img via fastboot if you are HTCDev unlocked.
Reboot and enjoy.
Update instructions:
Download Nightlies / Releases [BasketBuild mirror]
Put the file on SD card.
Reboot to recovery.
Flash cm-11-YYYYMMDD-UNOFFICIAL-ace.zip
Remember to reflash boot.img via fastboot if you are HTCDev unlocked.
No need to flash gapps as CM backuptool script should take care of them. (Results may vary depending on which gapps package you are using.)
Reboot and enjoy.
InspireMod
http://downloads.codefi.re/mustaavalkosta/inspiremod
Kernel
Source: github
Compiler: stock AOSP gcc-4.7
Branch: cm-11.0
Kernel Version: 3.0.101
defconfig: spade_defconfig
Contact:
My Google+
My twitter
#codefireX @ freenode
Donations:
For hosting: codefi.re (use the donation button at the bottom of the page)
I don't really need your money right now but if you insist on donating to me I suggest you donate that money to EFF instead here: https://supporters.eff.org/donate
Q&A:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
A: Update your recovery to one that is compatible with new recovery functions. See the list below.
4EXT Recovery Touch v1.0.0.6 RC 3 or newer
CWM 6.0.4.8 Advanced Edition / PhilZ Touch 6.29.8 or newer
TWRP 2.7.1.0 ACE or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM11.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm11
cd cm11/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
mkdir -p .repo/local_manifests
wget https://github.com/AceEnablementProject/android/raw/cm-11.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/ace/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
[UNOFFICIAL] CyanogenMod 11 Nightlies / Releases [M11], ROM for the HTC Desire HD
Contributors
Mustaavalkosta, paulb_nl
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: M11
Beta Release Date: 2014-10-08
Created 2014-04-11
Last Updated 2014-10-09
Click to expand...
Click to collapse
some saids it`s because the partition of cache is too small

CM11 latest release freezes after first reboot
GD to all. I am trying to install CM11 latest release, first time starts ok, but after reboot it doesn't start, freezes with black screen before bootanimation. Tried to flash boot.img via ADB & also tried to install CM 10.1 SR3, nothing helped, same situation. Waiting for your replies. Thx in advance.

Hey!
Would it be possible to you to add gpu overclock to that kernel?
Thx

Question about bugfixes
Hi,
at the moment i have M10 installed but i want to ask if there is a fix in M11 included which fixes sudden restarts.
My DHD restarts over night or when i want to something (it doesnt depends on what i am doing).
And another Problem sometimes the screen wont turn on when pressing the power button only the menu keys lighten up.
And i think it is more like off topic but how i can unlock the phone that i do not need to flash boot.img it is at the moment only HTC-Unlocked.
And very much thanks for this ROM it is great!
Thanks in advance for your answers
ag1707

Cannot dirty flash Nightlies
Hi
Since sometime around M11 release, I can not dirty flash nightlies on nightlies. The phone stuck at booting with the message "Android is upgrading / Finishing boot".
I'm using TWRP 2.7.1.0 for recovery.
1. Install Rom
2. Wipe Cache/Dalvik (I've tried without wipe too)
3. Reboot System
Am I missing something here?
I'm using non-English locale. Could it be the reason?
Best Regards,

Solved
Nanashi_anon said:
Hi
Since sometime around M11 release, I can not dirty flash nightlies on nightlies. The phone stuck at booting with the message "Android is upgrading / Finishing boot".
I'm using TWRP 2.7.1.0 for recovery.
1. Install Rom
2. Wipe Cache/Dalvik (I've tried without wipe too)
3. Reboot System
Am I missing something here?
I'm using non-English locale. Could it be the reason?
Best Regards,
Click to expand...
Click to collapse
Just figured it out that PA_GAPPS requires flash every update for recent ROMs.

Hi and thx for your rom!
I flashed the cm-11-20141008-UNOFFICIAL-M11-ace from releases, using twrp 2.7.1.0 for the recovery on a HTC Desire HD.
I am experiencing some lag when opening the screen or starting apps / widgets. It can take be almost instant up to 3-5 sec for the app to launch and be accessible (camera, gallery, weather, settings, mail anything really).
Also once in a while parts of the text in the screen get deformed (example here), any action by me (moving my finger around) or by the OS (some notification) fixes it.
As far as I can tell I followed your instructions properly. Is there anything I could try?

XZelin said:
some saids it`s because the partition of cache is too small
Click to expand...
Click to collapse
Possibly. There are some posts about this from paulb_nl on the main thread but I didn't find them right now. They are there though.
sky141 said:
GD to all. I am trying to install CM11 latest release, first time starts ok, but after reboot it doesn't start, freezes with black screen before bootanimation. Tried to flash boot.img via ADB & also tried to install CM 10.1 SR3, nothing helped, same situation. Waiting for your replies. Thx in advance.
Click to expand...
Click to collapse
Are you using the latest recoveries mentioned in the first post's Q&A section in the development thread? If your issue is what I think it is, full wipe with the previously mentioned recoveries should fix it.
_Bon_Bon said:
Hey!
Would it be possible to you to add gpu overclock to that kernel?
Thx
Click to expand...
Click to collapse
Is there working GPU OC for ace? I thought it was hardware locked thus can't be overclocked via software.
ag1707 said:
Hi,
at the moment i have M10 installed but i want to ask if there is a fix in M11 included which fixes sudden restarts.
My DHD restarts over night or when i want to something (it doesnt depends on what i am doing).
And another Problem sometimes the screen wont turn on when pressing the power button only the menu keys lighten up.
Click to expand...
Click to collapse
I haven't heard any complaints about frequent reboots. I know that there are those but it's been said to happen like once a week or so. M11 may change something if your issues come from corrupted devlog partition but if it's something else, then M11 won't do anything for your reboot issue.
Nihim said:
Hi and thx for your rom!
I flashed the cm-11-20141008-UNOFFICIAL-M11-ace from releases, using twrp 2.7.1.0 for the recovery on a HTC Desire HD.
I am experiencing some lag when opening the screen or starting apps / widgets. It can take be almost instant up to 3-5 sec for the app to launch and be accessible (camera, gallery, weather, settings, mail anything really).
Also once in a while parts of the text in the screen get deformed (example here), any action by me (moving my finger around) or by the OS (some notification) fixes it.
As far as I can tell I followed your instructions properly. Is there anything I could try?
Click to expand...
Click to collapse
It's a bit slow but I suppose that's understandable considering we are talking about 4 year old device. People have reported it gets slower the more apps you install. I'm not sure why.
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?

Mustaavalkosta said:
It's a bit slow but I suppose that's understandable considering we are talking about 4 year old device. People have reported it gets slower the more apps you install. I'm not sure why.
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Click to expand...
Click to collapse
Yea that is very much true, this might sound bad but would is there some other version you would recommend (even if it's a previous android release) which would be snappier? (your ROM so far is absolutely fine outside of that lag which as you stated is probably because DHDs hardware can't handle it).
As for that graphics glitch can't think of something, any apps were installed from play store (not restored by titanium for example) it happens on different ones but a lot more often on k-9 email client (from which the screenshot is).
If there is something that you would like me to try, feel free to tell me, though any action on the screen restores it to its normal way.

Nihim said:
Yea that is very much true, this might sound bad but would is there some other version you would recommend (even if it's a previous android release) which would be snappier? (your ROM so far is absolutely fine outside of that lag which as you stated is probably because DHDs hardware can't handle it).
As for that graphics glitch can't think of something, any apps were installed from play store (not restored by titanium for example) it happens on different ones but a lot more often on k-9 email client (from which the screenshot is).
If there is something that you would like me to try, feel free to tell me, though any action on the screen restores it to its normal way.
Click to expand...
Click to collapse
I don't mind people looking for better solution for their needs. You may want to try my CM10.1 builds which were noticeably faster if I recall correctly. I haven't been using other ROMs that much during the time I've kept my own stuff going here so I can't really recommend anything else. A fellow user may be a bit less biased to recommend other options.
I'll see if I can catch that graphical glitch with K-9 myself. Thanks for reporting it!

Mustaavalkosta said:
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Click to expand...
Click to collapse
I get that black boxes glitch with the standard Email app all the time. They usually go away in less than a second. I also checked for those when I was testing the 4.4 adreno drivers and it was still not fixed.

paulb_nl said:
I get that black boxes glitch with the standard Email app all the time. They usually go away in less than a second. I also checked for those when I was testing the 4.4 adreno drivers and it was still not fixed.
Click to expand...
Click to collapse
Oh ok. If it has been mentioned in the development thread, I've just probably forgotten about it.

Mustaavalkosta said:
I don't mind people looking for better solution for their needs. You may want to try my CM10.1 builds which were noticeably faster if I recall correctly.
Click to expand...
Click to collapse
Thanks! What would be the proper way to backup the whole "phone" so I can switch back and forth between roms? Atm I 'm only backing up apps & data with titanium.

Nihim said:
Thanks! What would be the proper way to backup the whole "phone" so I can switch back and forth between roms? Atm I 'm only backing up apps & data with titanium.
Click to expand...
Click to collapse
Doing a backup in recovery should be sufficient to backup everything except sdcard.

Mustaavalkosta said:
Are you using the latest recoveries mentioned in the first post's Q&A section in the development thread? If your issue is what I think it is, full wipe with the previously mentioned recoveries should fix it.
Click to expand...
Click to collapse
Thx 4 yours above. I'm using latest 4ext recovery touch + full wipe, of course. Will try to do something with partition.

Update from M11 to Nightly
It is possible to flash the newest nightly over the M11 release?
Or I need a full wipe.

Christian1987 said:
It is possible to flash the newest nightly over the M11 release?
Or I need a full wipe.
Click to expand...
Click to collapse
Well, generally it's recommended to wipe if you switch from one to another but it may work in this case without wiping. Make a nandroid backup and try it.

My battery dies really fast. Do you guys have a recommendation in terms of which battery to get? Link it here. Thanks.

prufessor_oak said:
My battery dies really fast. Do you guys have a recommendation in terms of which battery to get? Link it here. Thanks.
Click to expand...
Click to collapse
You can get original Desire HD battery on ebay cheaply, no point looking at other batteries which cost almost the same. Just look for one in your region.
Install Wakelock Detector from the Play store and find out what is causing your battery drain. Depending on phone use it should be able to last all day, 2 days if just left on standby all the time. Screen on all the time will be around 3-4 hours.