Related
so i rooted my g2x with the one click methode and got su. then i did the one click clockwork mod recovery flash. when i press vol down and powere it takes me to clockworkmod recovery, but all of menu is red. is this normal? alsoafter downloading rom manager i flashed the recovery and made some back ups, but when i reenter rom mananager my backups are gone, when i load into recovery backups are there! seems like rom manger doesnt stay synced with phone. i am using eagleblood rom and when i try to power off phone it doesnt respond , so i have to take out battery! please help, any info is welcome! thanks.
not sure which way it goes.. but depending on which CWR you installed, it may be working off of your external card.. and rom manager is looking for backups on the internal.
just gotta connect usb and move the files or use some kinda file manager app.
emilianos said:
so i rooted my g2x with the one click methode and got su. then i did the one click clockwork mod recovery flash. when i press vol down and powere it takes me to clockworkmod recovery, but all of menu is red. is this normal? alsoafter downloading rom manager i flashed the recovery and made some back ups, but when i reenter rom mananager my backups are gone, when i load into recovery backups are there! seems like rom manger doesnt stay synced with phone. i am using eagleblood rom and when i try to power off phone it doesnt respond , so i have to take out battery! please help, any info is welcome! thanks.
Click to expand...
Click to collapse
ok im thinking you did the nvflash method which is good if you did since the menu is red(yes this is normal). your probably not going to see your backups unless you do it the volume down & power way. not sure why its not powering off. you may wanna trying down loading the eagleblood rom again booting into clockwork with the volume down method installing the rom that way and see if that works.
sounds like a hassle i probably wont even use rom manager any more. thanks for info
thanks for info ill just skip rom manager all together, which rom is the most stable in your opinion
emilianos said:
thanks for info ill just skip rom manager all together, which rom is the most stable in your opinion
Click to expand...
Click to collapse
I Would go with Dark or Light sinister rom 2.2.1, or the Ultimate rom 2.2.1. until the release gb sourse or until krylon drops bionix rc2 which is hopefully soon.
dligon said:
I Would go with Dark or Light sinister rom 2.2.1, or the Ultimate rom 2.2.1. until the release gb sourse or until krylon drops bionix rc2 which is hopefully soon.
Click to expand...
Click to collapse
At this point, as far as the most stable.. I agree.. anything w/ 2.2.1.. Most have been just sticking w/ stock because of many diff probs with 2.2.3/4. I think that's why the GB was 'leaked' a while ago. To help get some of these bugs brought to the surface.. and probably why we have seen the delay in launch. At least, I hope that's the case. I would not be shocked if they purposely leak these so they can watch the boards to see what probs are out there... Then spend a few weeks fixing it.
I'd have to agree that as far as using 'something' different, Bionix is good.. but it has its probs too. It has the typical reboots/locks up as most others have (excluding 2.2.1). Don't expect Bionix updates to be released like the others. They try to create a quality rom without doing "nightlies". Also, the dev is working on a 100 other projects. Not sure where the bionix priority is, but I'm sure it is not at the top of the list on a regular basis.
Seriously, from looking at how functional all of these releases are.. I think stock is your best option. After using Bionix for a few weeks now, I like it.. but the reboots/lockups are a pain.
Okay ... So I am about to update to the latest pushed version. Am rolling back to EE4 now and have the update.zip on my card. What about CWM? Does my current version I've been using with my Gummy Charged 2.1 work with it? I have the Imosyn (sp) kernel on my card that I will apply after the update to 2.3.6 for root, as I understand it.
Are there any Gummy's or anything that are going to work after the 'official' update?
You don't use CWM with the update. You use stock recovery.
Gummy is EP1W. If you install it over the OTA, you'll bring yourself right back down to EP1, and the update will be pointless. You can get lagfix by running imoseyon kernel. It's EP4. It's slightly older EP4, but I haven't had any issues.
shrike1978 said:
You don't use CWM with the update. You use stock recovery.
Gummy is EP1W. If you install it over the OTA, you'll bring yourself right back down to EP1, and the update will be pointless. You can get lagfix by running imoseyon kernel. It's EP4. It's slightly older EP4, but I haven't had any issues.
Click to expand...
Click to collapse
Thank you sir! Phone is updating now. I will apply the imoseyon kernel after it's done. Lagfix is the main thing anyhow, I can nuke the bloatness with my Titanium.
now I'm confused .... I no longer have CWM recovery. How am I to apply the imoseyon kernel via stock recovery? Can I just rename it as update.zip?
By taking it back to stock EE4 and installing the update, one of the things it did was restore the default recovery environment.
Go back into ODIN and install CWM, don't use Auto-Reboot. When it's done flashing, turn the phone off and hold the button combinations to start the phone into CWM. Flash iMoseyOn's kernel and you're done at that point.
trparky said:
By taking it back to stock EE4 and installing the update, one of the things it did was restore the default recovery environment.
Go back into ODIN and install CWM, don't use Auto-Reboot. When it's done flashing, turn the phone off and hold the button combinations to start the phone into CWM. Flash iMoseyOn's kernel and you're done at that point.
Click to expand...
Click to collapse
Ahhhh.... it's @ the Sammy screen and she's talking to me! Looks like all is good while it re-writes the allocation tables. Thanx again, appreciate the heck out of the help.
hmmm .... I guess all is not well ... I installed the kernel but I don't have root. I installed superuser from the market and then Titanium and when opening Titanium I have no root .... what next?
Chopstix9 said:
hmmm .... I guess all is not well ... I installed the kernel but I don't have root. I installed superuser from the market and then Titanium and when opening Titanium I have no root .... what next?
Click to expand...
Click to collapse
You SHOULD have root since the kernel is your root method. Have you tried restarting?
Sent from my SCH-I510 using xda premium
Yeah I sure have. The kernel I used is imoseyon_kernel_charge_gb_4.0.0 ... not rooted .... guess I need to drop five yards and punt (do it all over)
Edit: The one thing I did not do prior to rolling back to EE4 was to do the big 3 wipe of data/cache/etc ..... maybe that's the problem?
Chopstix9 said:
Yeah I sure have. The kernel I used is imoseyon_kernel_charge_gb_4.0.0 ... not rooted .... guess I need to drop five yards and punt (do it all over)
Edit: The one thing I did not do prior to rolling back to EE4 was to do the big 3 wipe of data/cache/etc ..... maybe that's the problem?
Click to expand...
Click to collapse
Try installing Superuser from the Market? imosyeon kernel should have installed binary and apk, but maybe it missed part of it. If all else fails, flash the superuser zip from CWM.
http://www.toms-world.org/android/download/http/Superuser-3.0.7-efgh-signed.zip
Yes, I had installed SU from the market and didn't have root. I had an SU zip saved on my desktop .... su-2.3.6.3-efgh-signed .... I put that on the sd and installed it and I am rooted !!
Thanx Again
I love Lagfix and Voodoo Sound, but I'm currently running the stock kernel. I read in other forum discussion that Samsung designs their kernels to work with their OS revisions. People have said they're getting the best performance with the stock kernel.
Until IMoseyOn releases a new kernel based on the EP4D source that was released, I'm going to stick with stock.
Just some food for thought.
KarateExplosion6 said:
I love Lagfix and Voodoo Sound, but I'm currently running the stock kernel. I read in other forum discussion that Samsung designs their kernels to work with their OS revisions. People have said they're getting the best performance with the stock kernel.
Until IMoseyOn releases a new kernel based on the EP4D source that was released, I'm going to stick with stock.
Just some food for thought.
Click to expand...
Click to collapse
My concern was updating to 2.3.6 and having root. (on the road all day and need wireless tethering so outlook is open on laptop) Using the tad older imoseyon kernel gave me that, plus lagfix, which I have liked since this phone hit the market. I'm good for now, I can always update when the latest and greatest comes out.
Chopstix9 said:
My concern was updating to 2.3.6 and having root. (on the road all day and need wireless tethering so outlook is open on laptop) Using the tad older imoseyon kernel gave me that, plus lagfix, which I have liked since this phone hit the market. I'm good for now, I can always update when the latest and greatest comes out.
Click to expand...
Click to collapse
I have root on the stock kernel bro. Did a clean EE4 install, skipped as much set up as possible, ran update.zip in stock recovery, ODIN flashed imnuts' latest CWM recovery with auto-reboot disabled, booted directly into CWM recovery, flashed the latest SU zip, then ran setup as normal. Boom! Root.
Completely clean install, latest OS and kernel, root, plus tether works and everything.
Right now I'm just waiting on imnuts' TW4 theme to launch (he's estimating Sunday). Hopefully I can install that theme over a debloated and deodexed version of the latest OTA. It won't be long before IMoseyOn releases a kernel built from source that enables Lagfix. That's really all I'm missing, since Voodoo Control lets me load most of Voodoo Sound on top of the stock kernel.
What I'm REALLY looking forward to is an release of Liberty for the Charge or something AOSP if we ever get the 4G RIL sorted out... This things will take considerable time though.
It just doesn't matter ... In all honesty I liked the feel of the Gummy GBE 2.1 better than this stock ginger ... but again, it just doesn't matter to me. Functionality is all I care about, it's only a damn phone !!!
I loaded up the debloated/deodexed/rooted all-in one package danalo posted in development, flashed perfectly and after a wipe in CWM on first boot seems to be running fine except for the poop
sent from my Acer Iconia A500 beast of a tablet via XDA app
KarateExplosion6 said:
I have root on the stock kernel bro. Did a clean EE4 install, skipped as much set up as possible, ran update.zip in stock recovery, ODIN flashed imnuts' latest CWM recovery with auto-reboot disabled, booted directly into CWM recovery, flashed the latest SU zip, then ran setup as normal. Boom! Root.
Completely clean install, latest OS and kernel, root, plus tether works and everything.
Right now I'm just waiting on imnuts' TW4 theme to launch (he's estimating Sunday). Hopefully I can install that theme over a debloated and deodexed version of the latest OTA. It won't be long before IMoseyOn releases a kernel built from source that enables Lagfix. That's really all I'm missing, since Voodoo Control lets me load most of Voodoo Sound on top of the stock kernel.
What I'm REALLY looking forward to is an release of Liberty for the Charge or something AOSP if we ever get the 4G RIL sorted out... This things will take considerable time though.
Click to expand...
Click to collapse
Care to make a thread of what you done? Files used? I want to re-root my Charge, but want to keep the latest ota update and radios. Main question is the "update.zip" file?
iMoseyOn has stated that he's not going to be developing kernels anymore due to him having to turn in all of his phones to his old employer. He's taken up a new job and because of that he has to return his phones, including the Droid Charge.
trparky said:
iMoseyOn has stated that he's not going to be developing kernels anymore due to him having to turn in all of his phones to his old employer. He's taken up a new job and because of that he has to return his phones, including the Droid Charge.
Click to expand...
Click to collapse
Yeah, I read last night. Awful news. I hope someone can just get us full Voodoo and EXT4 support. I don't absolutely need OC/UV, but it'd be nice...
In other bad news, imnuts is getting a Galaxy Nexus and only pledging support for the Charge for "a few more months."
Let's hope JT and the gang can get this RIL figured out, so we can at least have Team Douche to continue development with CM 7.2 and CM 9...
Sent from my SCH-I510 using xda premium
Damn. And I thought it couldn't get any worse with iMoseyOn leaving. And now we have imnuts leaving too? It just went from bad to worse in a matter of 48 hours!
Guess I better get used to just using the stock kernel.
Hey guys, ok so I am coming from two HTC Heros (CMDA Sprint)
Was running cyanogenmod on both (me and the wife) loved it.
Now that I have the E4GT, I went ahead last week and used ODIN to install LoStKernel.
Now it did give me root and I have used apps like rom toolbox and setcpu.
My main problem is it seems these samsung devices are a lot trickier to tinker with.
Basically I am looking to get Clockworkmod so I can flash roms and make nandroid backups.
From what I have read, I need a kernel that supports and/or has CWM in it.
I tried flashing CWM with rom manager, and it installed - but I have no option to backup/restore I can only flash a zip or clear cache.
There are SO MANY things posted in the development section and I do not know which kernels are the latest, best etc.
I need:
a) CWM/busybox
b) overclocking support
c) FULL stock functionality (no loss of wifi or something stupid like that)
From what I am understanding the kernel is included with a rom. But I can't flash a rom without CWM. So I am rooted but stuck with stock rom and it's kernel.
Confused, lol!
Can someone point me to a proper thread to get me CWM and a well supported ROM to install? Can I get CWM working fully on the stock kernel/rom?
If someone can point me to the right direction, maybe I can find a developer to donate to lol!
No love?
At this point I'm just trying to get cwm. Seems I may have already had it just didn't know it came with lostkernel and now I botched it using rom manager.
Sent from my SPH-D710 using XDA App
You can actually flash a new kernel with CWM in odin
Thats the easiest method
There are several, as for the best I dont know yet
Im still tinkering with my setup
I guess that's my main issue - I can't find one that has CWM, everything I am seeing is a ROM that needs CWM to install.
If I had CWM I'd be all set because then I can backup my setup and try new things without worry, but I don't want to use ODIN to try a kernel that CWM won't take, or isn't there, and then lose what I have ya know?
All set, seems I flashed a kernel that wasn't what it was supposed to be. I apparently flashed his earlier version (pre-LoStKernel) that did not have CWM5 it it.
Just used ODIN last night to drop in LoStKernel and kept root, but also have CWM5 now. After clearing my SD Card, made my first backup. 1.5GB, jesus! lol. Nearly my whole SD card... yes, it's from my old Hero, so, time to get a 32GB.
i see that the guys working on the jellybean port for the infuse are using cwm 6.0.0.5 or so -- how can i get this installed on my infuse without installing the new jellybean rom (yet) ?
just want to stick with aokp 40 until jellybean is done, but want to play with the cool new touch recovery too...
Some one would have to compile the recovery into the ics kernel....
Sent from my HTC PH39100 using Tapatalk 2
What's so new about it?...........
May want to read this before pulling the trigger.. http://forum.xda-developers.com/showpost.php?p=29037114&postcount=275
hazard66 said:
i see that the guys working on the jellybean port for the infuse are using cwm 6.0.0.5 or so -- how can i get this installed on my infuse without installing the new jellybean rom (yet) ?
just want to stick with aokp 40 until jellybean is done, but want to play with the cool new touch recovery too...
Click to expand...
Click to collapse
I can personally tell you that cwm 6 is not touch...I used it on my vivid and there was no touch...at least the vivid has no touch...ill flash the vivid cwm 6 again just to be sure...
Even better...can someone who has flashed jb say wether or not the cwm has touch?
EDIT: Cwm 6.0.0.5 does not have touch for the HTC vivid...not sure about the infuse though...for the vivid it works just like the old cwm...use volume to navigate, power to choose
Sent from my HTC PH39100 using Tapatalk 2
whether or not cwm has touch enabled or not does not have to do with its version.
The Jack of Clubs said:
whether or not cwm has touch enabled or not does not have to do with its version.
Click to expand...
Click to collapse
yes, i know that as ive seen others with touch...thats why i said not sure about the infuse, the vivid one is built from official cm source so i don't think CWM 6 naturally supports touch...as in touch is enabled by some sort of add on/code edit-i could be wrong as i didn't build it nor have i looked at the source or anything so this is all based off of my observations of the vivid cwm 6
-jack if you've used the cwm from scotts cm10 build can you let us know if it has touch...i would pm scott but hes busy and knowing whether or not a recovery has touch isn't really necessary.
either way...doesn't effect me, im not a fan of CWM any longer and likely will not use it again for flashing roms
enabling touch isnt that hard to do in cwm. if you used the aroma installer on something like aokp on the infuse, youve used touch in cwm on the infuse. i know however its not enabled in the cwm6 thats with the jb rom. its just not a priority to fix right now. but im sure after getting more things working, itll be added one day.
The Jack of Clubs said:
enabling touch isnt that hard to do in cwm. if you used the aroma installer on something like aokp on the infuse, youve used touch in cwm on the infuse. i know however its not enabled in the cwm6 thats with the jb rom. its just not a priority to fix right now. but im sure after getting more things working, itll be added one day.
Click to expand...
Click to collapse
thanks for the reply, yeah...im sure once everything is as stable as ics some one may look into adding touch, ive used aroma before so i know what your talking about there...im buying an infuse in a few hours so i will be able to actually test things out before i reply
as for aroma...i love it and i hate it...its cool that you get to customize your flash some what...but the size of the download can be so huge! especially if its an aroma built for the vivid...stock vivid is 600mb unzipped...zipped and compressed its 400mb add another few hundred megabytes in there for aroma add ons and your looking at one or two roms per gig lol
mg2195 said:
thanks for the reply, yeah...im sure once everything is as stable as ics some one may look into adding touch, ive used aroma before so i know what your talking about there...im buying an infuse in a few hours so i will be able to actually test things out before i reply
as for aroma...i love it and i hate it...its cool that you get to customize your flash some what...but the size of the download can be so huge! especially if its an aroma built for the vivid...stock vivid is 600mb unzipped...zipped and compressed its 400mb add another few hundred megabytes in there for aroma add ons and your looking at one or two roms per gig lol
Click to expand...
Click to collapse
love the touch CWM for the GNote...
http://forum.xda-developers.com/showthread.php?t=1584576
stock Gnote i downloaded was a one click oding 1gig the virgin stock...
Odexed & Stock Rooted, Zipaligned, Deodexed & CRT 600-700mg
most of the GNote custom ROM 600-650...there is work to use the aroma with the GNote again...for the add-ons....its gonna be a whooper...
So is the new CWM suppose to be touched based???
Sent from my SAMSUNG-SGH-I997 using xda premium
slicingtaco said:
So is the new CWM suppose to be touched based???
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Could be wrong...but just based off only official cm source I don't think its touch based...i think the touched based ones have some sort of modification to the cm source
Sent from my HTC PH39100 using Tapatalk 2
http://www.clockworkmod.com/rommanager <- both touch and nontouch recovery are both by clockworkmod. and again, version means nothing towards it. to get touch working in cwm, you just need to load touchscreen modules. theyre just not in any of the infuse versions yet.
Somehow i have cwm 6 while running ics paranoid android. I didn't do it on purpose
MattSoRaven said:
Somehow i have cwm 6 while running ics paranoid android. I didn't do it on purpose
Click to expand...
Click to collapse
With most non-samsung phones recovery is not built into the kernel(actually HTC are the only phones I know like this), its in its on little partion which means you can change kernels without changing recoveries
For the infuse the recovery seems to have always been tied into the kernel so when you flash a kernel you flash a recovery...
Now by you saying that you still have cwm6, that leads to believe that possibly Scott has somehow removed the recovery from the kernel...if that was the case though you'd think there would be problems with the recovery inside the ics kernel...so I'm thinking somehow your still running he jb kernel which somehow can still run ics??? Lol I'm kinda at a lost...that was just me typing my thoughts/thinking outloud/rambling on about recoveries
Makes me curious tho...
Sent from my HTC PH39100 using Tapatalk 2
I think you're right that the recovery was partitioned somewhere and didn't go away. I was on an ics kernel. I believe this based on the build.prop info saying it was a 6/20 kernel, everything worked fine including Wi-Fi, torch, etc.
I was on JB and used Zen's toolkit to "complete wipe" then used the toolkit to restore to PA.
Edit: I flashed the latest yuma kernel because i needed to change this thing asap. I also just noticed multiple kernels have 6/20 as a date. The yuma kernel is signed differently with an "aaron" in the name that the previous kernel didn't have and is has a 6/30. I would have grabbed a screen shot, but i have ppl coming over soon and need to charge it so i can answer calls.
Well matt...here's what Scott had to say, the recovery is not in the kernel...its in recovery (assuming that means in its a seperate partion) so I guess as soon as you get cwm 6 your stuck with it unless you Odin/heimdal back to stock...
Now you wanna hear something interesting/cool? If the recovery is in its own partion then this opens the door for more types of custom recoveries! I was already planing on building an ics kernel with twrp recovery baked in when I get an infuse to work with...the problem with that though is as soon as you flash a Rom you would lose my kernel/twrp...but if Scott has it in its own partion then as soon as there's a twrp for jb I would be able to compile it and not have to worry about it getting erased from flashes..
Here's a video of twrp in action...http://www.youtube.com/watch?v=D2VlpVKj1eI&feature=youtube_gdata_player twrp is my favorite recovery...its fully touch based recovery and you can also theme the recovery as the UI is built with xml codes...really cool-I have it on my vivid...its also based off cwm source...so its just as stable as cwm
EDIT...i like your profile pic/avatar...nothing like some $5 Hot N' Ready large pizzas lol
Sent from my HTC PH39100 using Tapatalk 2
it isnt in the kernel, it is a partition. you cant boot to something inside of a kernel file, that doesnt make sense. you do however need a kernel capable of running whichever version of recovery you want to use. since fastboot is not on this device and many other samsung devices, there is a sort of failsafe in which recovery is written onto the device during system boot. which is why when you flash from a touchwiz rom to aosp rom, you have to let it boot up and freeze, then go back into recovery and flash again. you can look up partition information in recovery.fstab.
The Jack of Clubs said:
it isnt in the kernel, it is a partition. you cant boot to something inside of a kernel file, that doesnt make sense. you do however need a kernel capable of running whichever version of recovery you want to use. since fastboot is not on this device and many other samsung devices, there is a sort of failsafe in which recovery is written onto the device during system boot. which is why when you flash from a touchwiz rom to aosp rom, you have to let it boot up and freeze, then go back into recovery and flash again. you can look up partition information in recovery.fstab.
Click to expand...
Click to collapse
Actually...recoveries are built into the kernel...why else would you get red cam by flashing entropies gb kernel zimage
And as you can see in the picture (twrp Samsung github) they even state that most Samsung's must have recovery built into kernel..
Now it may be different with aosp Roms...but for normal stock Roms and stuff, i know for a fact that kernels contain the recovery...
Sent from my HTC PH39100 using Tapatalk 2
hrm. maybe its some kind of uimage. dunno, doesnt really apply to the infuse though.
Hello, all.
I have a T-Mobile Blaze 4G with rooted stock ROM (Gingerbread), flashed radio version T989UVMC6, manually debloated and dewizzed. I'm running Halo launcher and Busybox Free version 9.6.
Since almost the first day I've had this phone, it would occasionally force close the phone process, usually when hanging up the phone with the Bluetooth radio on and paired with an earpiece. It happened bone stock, rooted, after I changed the modem, whenever. It seemed to happen less often after I changed the modem. The process always starts back up, but the Bluetooth device connection and system sound controls are wonky (unusable) until the phone is rebooted.
The only thing that seems to stop it is running Zepplinrox's V6 Supercharger script. That, however, occasionally freezes the entire system when trying to open certain apps, requiring a reboot. I've run earch after search on this subject, and nobody else seems to have this problem. The only thing I haven't tried is wiping the whole thing and flashing a custom ICS or JB ROM. I tried Dark Knight ver. 8 and hated it pretty much instantly.
I have two questions. Number one; Will flashing a custom ROM fix this situation? I figure that this must be a problem with the crappy stock Samsung ROM. Number two; Which ROM is fully functional and stable? I'd really like to keep this phone dependable. I don't care about the latest and greatest funky cool features that are hit-or-miss at best. I just need dependable, fast and functional.
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Romman0 said:
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Click to expand...
Click to collapse
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
ionizd said:
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
Click to expand...
Click to collapse
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Romman0 said:
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Click to expand...
Click to collapse
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
The stock roms don't require gapps, but like Wolf said the cm10 jb variants do.
If your willing to use cm10 it is very stable. Just use the latest CM10 nightly and not the old stable version.
Here http://forum.xda-developers.com/showthread.php?t=1922935
The jb gapps 20121011 http://goo.im/gapps/gapps-jb-20121011-signed.zip
xWolf13 said:
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
Click to expand...
Click to collapse
Of course. I get a bit confused ever since people started talking about 10.1.
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
ionizd said:
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
Click to expand...
Click to collapse
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
jparnell8839 said:
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
Click to expand...
Click to collapse
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
ionizd said:
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
Click to expand...
Click to collapse
Since you have it setup, except for battery life. I would make a backup, then try a mod one at a time and see if any help. Also check the battery stats to see if anything of is seen. ICS will use more juice than GB, generally.
I would suggest Nos/direct injection, supercharger, or cross breeder. I would use one and see, then restore and try another.
http://forum.xda-developers.com/forumdisplay.php?f=565
Some time later...
I've been using the stock rooted ICS ROM since my last post, debloated and dewizzed of course, with Holo Launcher and T989UVMC6 baseband version flashed. Just over a month has passed, and I have good news!
I FREAKING LOVE THIS PHONE!!!
All of the force close and freezing issues have vanished, the phone's battery lasts almost as long as it did on GB, it's WAY more user friendly, and the phone is as fast as it ever was.
The bad news is that my wife got a GS4 and I lust after it now. : /
Thanks to everyone for their help!