Related
I had a few questions that I can't pull up much information on. There looks to be a ton of updates we now have the option of putting on our EVO, what are the differences.
Kernel
--- Alright, I know this one but for anyone who doesn't. This is the heart of the phone. It is what allows software to talk to hardware.
--- Why do some of the kernel changes break the camera/accelerometer? Are these drivers built into the kernel instead of modules? Can they not be rebuilt with different kernels?
NAND
--- What is the NAND and why are we unlocking it?
--- NAND is a type of flash, no? Are all they system files (i.e. the /system folder) on their own chip inside the evo? How can rooting and remounting the system r/w not control the /system folder?
--- While I'm at it, does rooting just me remounting everything but the /system folder as r/w. So a non rooted phone is read only except for the SD card and where ever apps from the market are installed?
Recovery
--- It seems like there are a couple recovery systems out there... clockwork and another. Did the EVO not come with its own recovery system. What have these modded versions added?
ROMS
--- What are these really doing if they are not messing with the /system folder. Are they just a bundle of different programs? Change the rom and you change the programs that are installed? What is the difference between a ROM and a DEV-ROM
RADIO
--- What is the deal with the new radio. Is it updated drivers for the baseband? This kind of gets into my kernel question about how the drivers are handled within the kernel. How can this work across multiple kernels, but we cant get the camera working?
I know this is a lot, but if anyone could fill in some of the holes for me I would appreciate it.
Thanks
bump...
Any thoughts? You don't have to answer them all.
I am NO expert, but can help a bit....
Kernel
--- Alright, I know this one but for anyone who doesn't. This is the heart of the phone. It is what allows software to talk to hardware.
--- Why do some of the kernel changes break the camera/accelerometer? Are these drivers built into the kernel instead of modules? Can they not be rebuilt with different kernels?
From my understanding, the kernles that break the camera, are kernels that are ports of kernels from other phones. So, the drivers for the camera are not the same as for the other phones camera.
Recovery
--- It seems like there are a couple recovery systems out there... clockwork and another. Did the EVO not come with its own recovery system. What have these modded versions added?
My understanding is that the phone's original recovery, is locked to only flash Sprint's Official ROM's. So the custom recovery will allow to flash custom ROM's
ROMS
--- What are these really doing if they are not messing with the /system folder. Are they just a bundle of different programs? Change the rom and you change the programs that are installed? What is the difference between a ROM and a DEV-ROM
Aside from changing apps, ROM's can do different things like optimizing the apps so that they run smoother, move data from one place to another to run more efficiently and allow for a number of customizations that would not be available with only the stock ROM rooted. A ROM is understanded as a usable, stable ROM. A DEV-ROM is one that is not stable, were it has things that still dont work and need to keep improving.
Hope it helps!
Perfect thanks.
The ROM/DEV-ROM thing was really bugging me, and the recovery explanation makes sense.
amw2320 said:
I had a few questions that I can't pull up much information on. There looks to be a ton of updates we now have the option of putting on our EVO, what are the differences.
Kernel
--- Alright, I know this one but for anyone who doesn't. This is the heart of the phone. It is what allows software to talk to hardware.
--- Why do some of the kernel changes break the camera/accelerometer? Are these drivers built into the kernel instead of modules? Can they not be rebuilt with different kernels?
Click to expand...
Click to collapse
So with *.NIX kernels such as linux, unix, and the android kernel there are modules that make up the kernel itself. Any *.NIX kernel is going to be modular and this makes it more efficient and robust. In the case of specific items not working between different kernels, it most likely means the kernel was compiled with specific modules that have specific scripts and drivers in it. This method speeds up the kernel because it takes out stuff not needed. But means it limits the devices the kernel can run on.
In the case of Android ROMs not being able to fully interface with hardware, it likely means the kernel is missing something as another commentator already suggested.
NAND
--- What is the NAND and why are we unlocking it?
--- NAND is a type of flash, no? Are all they system files (i.e. the /system folder) on their own chip inside the evo? How can rooting and remounting the system r/w not control the /system folder?
--- While I'm at it, does rooting just me remounting everything but the /system folder as r/w. So a non rooted phone is read only except for the SD card and where ever apps from the market are installed?
Click to expand...
Click to collapse
We are unlocking NAND and rooting phones to get access to file systems that are locked down by phone manufactures/cell providers. Doing so unleashes the full potential of the device.
If you rooted your phone and you do not have full access to the file system, you only did part 1 of the root process. There are 2 parts because one unlocks NAND and the other unlocks the file system completely with the phone booted. Step 1 just unlocks filesystem for NAND which means you have to be booted into NAND for full access to file system. I think I have that right.
Recovery
--- It seems like there are a couple recovery systems out there... clockwork and another. Did the EVO not come with its own recovery system. What have these modded versions added?
Click to expand...
Click to collapse
Clockwork and the others are just replacing NAND with their own system, if I am correct. I recommend doing this if you are rooted because you get better features and a constantly updated system, where as NAND is only updated when Sprint and HTC have an update with a NAND update in it (which isn't often). The way I recommend updating this is using ROM Manager once you are rooted. It is very safe and easy.
ROMS
--- What are these really doing if they are not messing with the /system folder. Are they just a bundle of different programs? Change the rom and you change the programs that are installed? What is the difference between a ROM and a DEV-ROM
Click to expand...
Click to collapse
When you see ROM, think GUI for the OS, collection of apps and scripts. The ROM what you are going to interact with and use. I highly recommend flashing a custom ROM once rooted because you will have less problems and they are way more efficient than stock. Developers take time and care to test and tweak their ROMs so that they not only perform good, but give us the features we want. Find one you like and install. Make sure you do a NAND backup though once you get everything installed the way you like. Also do a titanium backup (app from marketplace) too.
RADIO
--- What is the deal with the new radio. Is it updated drivers for the baseband? This kind of gets into my kernel question about how the drivers are handled within the kernel. How can this work across multiple kernels, but we cant get the camera working?
Click to expand...
Click to collapse
It is recommended not to mess with the radio unless a ROM you want requires it. I flashed it without any trouble at all and things seem fine on my phone. Some people recommend flashing it because they think it makes the cell radios in the phone perform more efficiently and such. This is all I can say on the radio as I'm no expert.
I see most of the questions have been answered above...I'll attempt as well and perhaps it will help clarify (or just give a different way of looking at it).
amw2320 said:
I had a few questions that I can't pull up much information on. There looks to be a ton of updates we now have the option of putting on our EVO, what are the differences.
Kernel
--- Alright, I know this one but for anyone who doesn't. This is the heart of the phone. It is what allows software to talk to hardware.
--- Why do some of the kernel changes break the camera/accelerometer? Are these drivers built into the kernel instead of modules? Can they not be rebuilt with different kernels?
Click to expand...
Click to collapse
Yes, the kernel is the heart of any OS (Windows has one, Linux has one, etc). The kernel is where everything eventually goes to do anything.
The reason the new kernels do not have camera functionality is because, while we have generic source code, we do not have the drivers/modules for that source code. HTC does some modifications within the source that are proprietary and so we have to attempt to try and reverse engineer it. About the time we do, they release the source code (I have suspicions of conspiracy, but that may just be me) and that's when the kernel's really roll out with some fun stuff.
New kernels will be the source of the most new features...overclocking, efficiency improvements, etc.
NAND
--- What is the NAND and why are we unlocking it?
--- NAND is a type of flash, no? Are all they system files (i.e. the /system folder) on their own chip inside the evo? How can rooting and remounting the system r/w not control the /system folder?
--- While I'm at it, does rooting just me remounting everything but the /system folder as r/w. So a non rooted phone is read only except for the SD card and where ever apps from the market are installed?
Click to expand...
Click to collapse
This is one of the areas I'm most weak in for understanding but I'll still take a stab.
NAND is a type of flash and, to my knowledge, it's own seperate chip. It is usually locked to prevent modifications that could break your phone or prevent it from updating properly...I *think* it's used during boot so the lock would translate straight through to your OS and prevent changes if put in a locked state (think similar to how some SD cards have a "lock" switch on the side to make it read only, except a software version of it).
Recovery
--- It seems like there are a couple recovery systems out there... clockwork and another. Did the EVO not come with its own recovery system. What have these modded versions added?
Click to expand...
Click to collapse
Clockwork and AmonRA's recoveries are replacements that add functionality over the stock recovery. The stock recovery is only meant to be used by the manufacturer to perform certain tasks (like updating, resetting, etc...but no user functions like backup/restores.). Both Clockwork and AmonRA's recoveries add the ability to take a complete image of your phone (so that you can always restore any software changes no matter how severe), reformat and partition your sd card (to add/remote a cache partition or a partition for Apps2SD), reset battery stats, and a host of other things I'm sure I haven't even touched on. Also, I believe they add the functionality to flash unsigned updates done by the community (not just restricting us to HTC's updates).
ROMS
--- What are these really doing if they are not messing with the /system folder. Are they just a bundle of different programs? Change the rom and you change the programs that are installed? What is the difference between a ROM and a DEV-ROM
Click to expand...
Click to collapse
Most of the ROMs you see now require NAND unlocks so that they can mess with the apps in /system. Some ROMs are just a certain package of apps or a set of themes. Others add functionality or make certain things easier to implement. Yet others are tweaked to attempt to change other aspects of the OS to improve performance of battery life through tweaks to when the system performs certain tasks.
Ultimately, each ROM is different and the changelogs *should* tell you what all they've done over the stock (or if they're based on another ROM, you can open that page to see the tweaks they are tweaking, etc). (Sometimes it can get pretty big on the tweaks on another rom's tweaks on another rom's tweaks...check the CDMA hero forums for some combination roms ).
ROMs vs Dev-ROMs - Dev-ROM's are usually a work in progress...they are testing new features and often will be on the bleeding edge (emphasis on bleeding). These will sometimes (even likely) break something while they try and improve or add new functionality in another aspect. You should only flash these if you want to help test and if you have an idea of what's going on so you can help troubleshoot.
Normal ROMs are usually more stable (usually) and will have milder modifications (though once a DEV-ROM has successfully gotten a new feature stable, most other ROMs will incorporate those changes...it's kindof a lifecycle).
RADIO
--- What is the deal with the new radio. Is it updated drivers for the baseband? This kind of gets into my kernel question about how the drivers are handled within the kernel. How can this work across multiple kernels, but we cant get the camera working?
Click to expand...
Click to collapse
Radio images are a bit more like firmware updates to the radio chip. These often help to improve reception or connectivity or fix instabilities or other problems. Not everyone experiences the issues that it attempts to fix and doing a flash on your own does have certain risks. The odds of a problem arising for you isn't high, but the effect is potentially severe if a problem does occur. The main thing to remember is to ensure you have enough battery for the changes to occur (firmware updates in general recommend this on all devices, be it laptop BIOS updates or phone radio updates...I recommend using the wall charger and not unplugging it until 5 minutes after the update has completed), and ensure that you don't try and do anything else on the phone while the update is occuring.
I know this is a lot, but if anyone could fill in some of the holes for me I would appreciate it.
Thanks
Click to expand...
Click to collapse
Hopefully the info given by me and my fellow ex-newbies will help with your desire to learn! There's a lot of cool stuff about our phones and I love that we can get a bit into the guts of the thing (unlike some phones*)
*I can't help but throw a little jab at Apple every so often.
This is great information and helps me to push myself even further towards ROM development.
I enjoy my Evo and this website is amazing
Great thread and information, I was looking for something similar. I'm totally new to Android and want to start the whole rooting process.
I don't mean to hijack the thread or anything, but some terms are thrown around and I don't have a 100% understanding of what they really mean....could someone please define them?
Recovery?
Flashing?
Thanks codemonk and webs, that was awesome.
Onepanda, i'll give your question a shot.
Flashing is really just putting files on you phone. Generally it refers to replacing the andriod system files. You can flash a kernel, a ROM, drivers, or just an update to one of those.
Recovery is a mode you can put your phone into from boot. This is where you flash the files from. You cant just replace system files while they are running, so you boot into recovery mode and flash them from there.
Recovery mode also has a few other features allowing you to reset settings (cache) and make backups.
Just had a peek at the Revolution ROM page, and noticed that you need to update the file system to ext4. A few questions surrounding this:
1) Which filing system is the DHD running at the moment?
2) Any advantages worth mentioning if you run ext4 on your device?
3) If I change to ext4, will stock ROMs still run? This one obviously goes for reloading my current backup if something goes wrong - guessing this is a no.
4) Is it possible to revert to the previous file system?
5) What are the chances of bricking my DHD if I do this?
DHD has been rooted, S-Off, etc. Ran CyanogenMod for a while, flashed a few other ROMs in the meantime, so the basics are done, risks understood. Haven't done a file system change before, though, so I'd like to know before diving in head-first.
FvanLog said:
Just had a peek at the Revolution ROM page, and noticed that you need to update the file system to ext4. A few questions surrounding this:
1) Which filing system is the DHD running at the moment?
2) Any advantages worth mentioning if you run ext4 on your device?
3) If I change to ext4, will stock ROMs still run? This one obviously goes for reloading my current backup if something goes wrong - guessing this is a no.
4) Is it possible to revert to the previous file system?
5) What are the chances of bricking my DHD if I do this?
DHD has been rooted, S-Off, etc. Ran CyanogenMod for a while, flashed a few other ROMs in the meantime, so the basics are done, risks understood. Haven't done a file system change before, though, so I'd like to know before diving in head-first.
Click to expand...
Click to collapse
1) The standard filesystem is ext3
2) There's quite a lot, google it if you want to know all the details. Practically you wont notice much difference, maybe a bit faster etc. It's just newer and more optimized.
3 & 4) ext4 is just a filesystem, it can always be changed by formatting.
5) Practically none
you say you ran CM for a while, if perchance this was CM7 then you already have experience of running an ext4 files system
Didn't realise CM7 was running ext4 already - my bad. So much for not diving in head-first, hey
Thanks, guys. Question answered.
Updated via recovery from an older franco kernel causing battery issues to the new milestone 4 in the developer section. Currently stuck on the Google boot screen. Let it continue to load for 10 minutes before I pulled the battery. Can't seem to open up fastboot. Not sure what to do at this point. Help?
I should add that I can access ODIN mode, although I'm not familiar with the utilization of it. I can access my sdcard via another phone so if there is something I can load onto the sdcard that will auto recover via ODIN mode, please let me know! I do have a nandroid backup, but again I cannot access recovery/fastboot for some reason. Just stuck at the Google boot screen.
To begin with, you're flashing the wrong kernel if you flashed Milestone 4 on 4.1.1. Know what you're supposed to be flashing before you flash it and odds are you won't create problems such as this for yourself. Franco has not released any Milestone JellyBean kernels, only nightlies.
Secondly, how would you propose accessing your sd card via another phone since the GN does not have a removable sd card? It's merely a partition within the internal memory.
At this point, you're probably just best off using the toolkit (even though I abhor things of its nature) to restore yourself to stock and start over from scratch.
I'd also strongly recommend purchasing Franco's updater app. In addition to supporting a fine dev and providing for some useful tweaks, it will only allow you to flash his kernels that are compatible with your phone.
najaboy said:
To begin with, you're flashing the wrong kernel if you flashed Milestone 4 on 4.1.1. Know what you're supposed to be flashing before you flash it and odds are you won't create problems such as this for yourself. Franco has not released any Milestone JellyBean kernels, only nightlies.
Secondly, how would you propose accessing your sd card via another phone since the GN does not have a removable sd card? It's merely a partition within the internal memory.
At this point, you're probably just best off using the toolkit (even though I abhor things of its nature) to restore yourself to stock and start over from scratch.
I'd also strongly recommend purchasing Franco's updater app. In addition to supporting a fine dev and providing for some useful tweaks, it will only allow you to flash his kernels that are compatible with your phone.
Click to expand...
Click to collapse
I have been playing with so many phones lately I completely overlooked the non-removable SD card in the GN. Total disbelief when I realized that. Also, regarding the ICS kernel M4, I did read through some 30+ pages before flashing it and could not find any reference to ICS *or* JB in discussion of M4. I took a leap of faith and it cost me. Nevertheless, I was able to get into the bootloader and then recovery, where I promptly loaded an old nandroid backup. Currently back on a stable 4.1.1 ROM running franco's r330.
/thread
[Q] Is there a "dual-boot" or "safe partition" recovery like Safestrap out there?
Hi all, first post here so I'm preparing myself for mallets to the head.
I do apologize if this question is redundant, but I did a few cursory searches trying to find out whether or not there exists any type of utility that allows you two "partitions" (in quotes because I'm not entirely sure that terminology is technically correct, but it's the closest analog my Windows-raised brain can muster) so that you can use one for your stock ROM and the other for flashing Custom ROMs and basically wreaking any kind of havoc you wish?
Safestrap is what I use for my Droid Bionic. It was mentioned here in another dev thread, I believe. It locks down one partition, which it calls "non-safe", not allowing you to flash anything to this area (although you can restore any backups you took of this non-safe partition), but you are free to do whatever you want on the other partition. (It uses CWM as its base I believe.) Its existence has saved my hide many a time when I was feeling mischievously experimental with my Bionic and I'm hoping I can use it to test out the handful of A100 custom ROMs out there (while keeping my daily driver safe) before I "settle" on a good one.
(Caveat is that I'd have to replace TWRP which I like quite a bit.)
MrCHUPON said:
Hi all, first post here so I'm preparing myself for mallets to the head.
I do apologize if this question is redundant, but I did a few cursory searches trying to find out whether or not there exists any type of utility that allows you two "partitions" (in quotes because I'm not entirely sure that terminology is technically correct, but it's the closest analog my Windows-raised brain can muster) so that you can use one for your stock ROM and the other for flashing Custom ROMs and basically wreaking any kind of havoc you wish?
Safestrap is what I use for my Droid Bionic. It was mentioned here in another dev thread, I believe. It locks down one partition, which it calls "non-safe", not allowing you to flash anything to this area (although you can restore any backups you took of this non-safe partition), but you are free to do whatever you want on the other partition. (It uses CWM as its base I believe.) Its existence has saved my hide many a time when I was feeling mischievously experimental with my Bionic and I'm hoping I can use it to test out the handful of A100 custom ROMs out there (while keeping my daily driver safe) before I "settle" on a good one.
(Caveat is that I'd have to replace TWRP which I like quite a bit.)
Click to expand...
Click to collapse
As far as I know nothing like that is available for the a100s, its pretty much all used in one way or another. Closest is the backup and restore of twrp and cwm recoveries. A500 has dual boot now, but we will likely never see that on our stuff. I won't say never, because you just never know and this is xda after all.
Tapatalked from my Galaxy S II.
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