Related
I've been flashing kernels through Clockwork, but I decided to download Kernel Manager Lite and I'm considering trying it. Has anyone had any experiences with it, good or bad? I'd appreciate any feedback before giving it a go. Thanks
it's works flawless for me, i use the free one.
The only problem I've run into was flashing a kernel while on BAMF 1.6, it worked but broke wifi. I flashed the same kernel using clockwork and wifi was back with no problem. I read someone else had the same problem.
Sent from my ADR6400L using XDA Premium App
That might have been me and more of a 1.6.1 ROM issue which has Kernel Manger Lite included. My story:
http://forum.xda-developers.com/showpost.php?p=13444295&postcount=351
icesteve said:
The only problem I've run into was flashing a kernel while on BAMF 1.6, it worked but broke wifi. I flashed the same kernel using clockwork and wifi was back with no problem. I read someone else had the same problem.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I was using kernel manager pro when I attempted, not the one included in the rom. I figured it had to be kernel manager because CWM flashed it perfectly.
Sent from my ADR6400L using XDA Premium App
Thanks for the responses. I'll probably give it a try. I guess I can always reflash through Clockwork if anything goes wrong. Or worse case, I can flash a backup if anything gets seriously out of whack.
bunklung said:
That might have been me and more of a 1.6.1 ROM issue which has Kernel Manger Lite included. My story:
http://forum.xda-developers.com/showpost.php?p=13444295&postcount=351
Click to expand...
Click to collapse
I had the same problem .. I never considered that it may have been kernel manager .. thanks for that
Sent from my ADR6400L using XDA App
For me the issue is this ...
No backup made prior to flashing ... I'm sticking w/ RM for kernel flashing
Based on my experience with BAMF rom and leanKernel, it appears that any customization scripts and/or files that the kernel developer intended for you DO NOT get flashed with Kernel Manager (I have Pro version). The people with broken wifi using KM but working wifi with RM proves the point. My experience was that 4G hotspot didn't work when flashing leanKernel from KM, but works fine with an RM flash. This is actually a common problem across several devices I've used. Many kernel devs modify the wifi driver and/or other things in a manner that they end up only working with their specific ROM. The do this by including the modified files in their zip package along with a script telling the phone what to put where. The issue becomes if you switch to a kernel that's relying on a stock wifi driver, and doesn't put it back on its own, then you've got a busted wifi. The only way around that is to manually push/restore a copy of a wifi driver known to work with the kernel you're using. I kind of regret paying for the pro version after finding this out; hopefully the KM folks can figure it out. The kernel itself is just the boot.img file; the add-ons files that go into the /system partition or where-ever. If you're interested in knowing what a particular kernel is pushing on your phone, just open the zip file and drill down through the folders to find what files are in /system tree. This is also a way to find files you need to go back to stock drivers, just find a stock rom that's flashable in RM and drill down to the files in /system/lib and push them back to the phone via adb or root explorer.
i bought the pro version and i wish i hadn't. i downloaded/flash one of protekks kernels through there and it sent my phone into a bootloop and by the time i'd flashed a nandroid backup the 15 minutes had gone by -_______-
why?
I haven't actually tried this yet, I guess the question for me is why? Does it do something that CW cannot do? I don't know much about the product so I am just trying to understand the benefit of installing it.
turbosrrgood said:
I haven't actually tried this yet, I guess the question for me is why? Does it do something that CW cannot do? I don't know much about the product so I am just trying to understand the benefit of installing it.
Click to expand...
Click to collapse
It will notify you of kernel updates, and you can filter kernels based on what you want
Sent from my ADR6400L using XDA Premium App
[CLOSED][ROM]Bone Stock & Stock Deodex ROM's Triumph-Now Resets Splash.img!![CLOSED]
Thread closed because I no longer own this device. The download links no longer work. Sorry for any inconvenience.
i just installed and wifi works but when trying to go online rebuts the phone, also the screen goes black and stays like that for like 2 minutes. And yes i did all the restores available.
Which ROM did you flash? Deodexed or Complete Stock?
deoxed one.
Hmm that's odd cause the woofing works fine on mine! Ill look into it!
Sent from my OC'ed Triumph!
b_randon14 said:
Hmm that's odd cause the woofing works fine on mine! Ill look into it!
Sent from my OC'ed Triumph!
Click to expand...
Click to collapse
Same here it works... weird, this is the fix for me that got the wifi functioning again. But then again, I flashed b_randon14's stock theme zip, not this one.
If you want deodex I would recommend that one, more confirm it working at least right now.
Stupid question perhaps, but will apktool properly decompile and recompile framework-res.apk? I ran into a doozy of a problem trying to do that with somebody else's ROM.
Yeah it decompiles just fine! I have done it a thousand times!
Edited op with the zips that will reset the splash.img back to factory as well!!!
Thanks and I'm going to have to try this one out now.
Is the Android logo text hidden deeper in the system than I originally thought? I've actually seen it on my new phone a couple of times now, after reverting different things. You know, the flashing "android" text...
When there is no boot animation, it reverts to the flashing android logo. Its in the framework Res under assets/images. The boot logo(red Motorola logo) is on the same partition as the recovery image as a splash.img. to flash it I have the recovery mount that vfat partition as sd-ext and copy over the the splash.img its the same way I flash recoveries from cwm.
The bootanimations( red Motorola animated logo then cm splash animation) is locates in /hidden/data/power-on animation.
Sent from my MOTWX435KT using Tapatalk
So I installed the deodexed version and I was able to use mobile wifi tether with barnicale without having to change the MTU for the Motorola Triumph!
Once you change the MTU once on a computer, you never have to change it again... you sure it's not just a residual effect?
primetechv2 said:
Once you change the MTU once on a computer, you never have to change it again... you sure it's not just a residual effect?
Click to expand...
Click to collapse
I'm quite well aware of that. I did it on my laptop, but not my desktop. but my desktop was able to connect online with the tether. i guess i should try it on another machine to make sure.
Is there any advantage with the deodexed version over the odexed version if your goal is to restore the phone to stock after having another ROM installed?
Selling my Motorola Triumph to a friend - I've been running CM7 since the alpha days, so I need to go back to stock. I still have a nandroid of the stock ROM, but that also has a lot of installed apps, not to mention personal information/passwords. Will the complete stock ROM allow her to activate the phone?
InfamousBlade said:
Selling my Motorola Triumph to a friend - I've been running CM7 since the alpha days, so I need to go back to stock. I still have a nandroid of the stock ROM, but that also has a lot of installed apps, not to mention personal information/passwords. Will the complete stock ROM allow her to activate the phone?
Click to expand...
Click to collapse
It should.
I know this thread is about a year old, but thanks for the stock files.
I had CM7 running on my daughters Triumph. I finally decided to just put both of my kids on my VZW family plan since the Gnex dropped to $50 each and Virgin Mobile's service is a complete waste of money.
I'm selling her Triumph now and the phone has to be stock in order for the new owner to activate it, so this came in handy.
Thank you very much!
Works perfectly. My girlfriend didn't want a buggy ROM ruining her Candy Crush games so I had to bring her back to stock. Took less than ten minutes! Tanks!
well right now I'm currently flashing the cm7 rom. I can't send/receive any mms right now. I've tried searching and I've tried a lot of things, but nothing seems to be working. I also miss my stock froyo as well. So I was wondering if I can revert back to the original stock froyo, but still be root.
I used rom manager and I backuped the orginal rom before I flashed the cm7 and the addons, but I don't know where it use or even how to go about it . Can I use that to revert back to the orginial rom and will I still be rooted?
I'm currently on the mytouch4g and if you know where I can download the rom for froyo please post a link.
thank you very much.
mytouch4gnoob said:
well right now I'm currently flashing the cm7 rom. I can't send/receive any mms right now. I've tried searching and I've tried a lot of things, but nothing seems to be working. I also miss my stock froyo as well. So I was wondering if I can revert back to the original stock froyo, but still be root.
I used rom manager and I backuped the orginal rom before I flashed the cm7 and the addons, but I don't know where it use or even how to go about it . Can I use that to revert back to the orginial rom and will I still be rooted?
I'm currently on the mytouch4g and if you know where I can download the rom for froyo please post a link.
thank you very much.
Click to expand...
Click to collapse
Hi, the answer to your question is actually in your post...if you backed up your froyo rom with the rom manager, then you just have to restore the backup.
To do that, go to the Rom manager, manage and restore, and then find your backed up rom. It should take a while and you will be back to the state you were before flashing CM7. Just in case make a nandroid backup of your current rom in case things don't go as expected. It should be working neatly. Hope it helps. Let me know if you could restore it. See ya....
mytouch4gnoob said:
well right now I'm currently flashing the cm7 rom. I can't send/receive any mms right now. I've tried searching and I've tried a lot of things, but nothing seems to be working. I also miss my stock froyo as well. So I was wondering if I can revert back to the original stock froyo, but still be root.
I used rom manager and I backuped the orginal rom before I flashed the cm7 and the addons, but I don't know where it use or even how to go about it . Can I use that to revert back to the orginial rom and will I still be rooted?
I'm currently on the mytouch4g and if you know where I can download the rom for froyo please post a link.
thank you very much.
Click to expand...
Click to collapse
Hey i also have a Mytouch 4G and i have looked around before but couldn't seem to find a Stock froyo rom that is rooted. I would recommend you use a different ROM other then CM7. There are plenty of roms in the mytouch 4g section. we also have a great dev TheDerekJay does an amazing job with keeping all his roms updated. im using his MIUI rom on my mytouch and im in love with it.
actually I just looked at my rom manager backup file. and it says the date for today... I used mybackup root to just back up my data because I was planning on changing my rom. So I'm seriously am confused now... I back uped the rom (froyo) just yesterday so shouldn't it say that 1/1/2012 instead of 1/2/2012? Should I just flash this backup anyway and hope for the best?
mytouch4gnoob said:
actually I just looked at my rom manager backup file. and it says the date for today... I used mybackup root to just back up my data because I was planning on changing my rom. So I'm seriously am confused now... I back uped the rom (froyo) just yesterday so shouldn't it say that 1/1/2012 instead of 1/2/2012? Should I just flash this backup anyway and hope for the best?
Click to expand...
Click to collapse
I should have the date and time when you did the backup...but if It was after midnight or your time zone is not correct that might affect the name. If it is the only backup you did then it must be it. Let me know after you flashed it how things resulted.
thanks glevitan. You were right the time zone is probably not set correctly. I restored the file and I'm back to the original stock froyo and I'm still rooted I'm very happy now. thank you so much.
mytouch4gnoob said:
thanks glevitan. You were right the time zone is probably not set correctly. I restored the file and I'm back to the original stock froyo and I'm still rooted I'm very happy now. thank you so much.
Click to expand...
Click to collapse
You're welcome...enjoy your new/old rom. See ya!
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Same problem
CZory91 said:
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Click to expand...
Click to collapse
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
bmanderle said:
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
Click to expand...
Click to collapse
It's an AOSP problem based on the firmware of your camera when getting the phone from what I've seen.
http://forum.xda-developers.com/showthread.php?p=37072484#post37072484
Here's the thread I was talking about, however I'm confused about how to go about zipping and unzipping these files. Or even how to get to them to place the files in to begin with considering internal SD card is the only thing that comes up for USB storage. Unless you're supposed to move them in and out from within android.
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
CZory91 said:
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
Click to expand...
Click to collapse
I had the camera problem on MIUI...
Before flashing, I made a backup of my system with CW
I extracted the SlimISP_ZH.bin from my backup and
copied it to my /data directory and it worked fine.
Link: d-h.st/dwx
(I can't post links yet)
maybe... someone post the fix in this forum and make it sticky... lol
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
CZory91 said:
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
Click to expand...
Click to collapse
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
Click to expand...
Click to collapse
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
Click to expand...
Click to collapse
Yes, that is the post. I also tried MB1 out of curiosity, no dice on either of them. I had a perfectly working CM10. I dun goofed :\.
That was my next step (rerooting, installing that firmware AIO, and then installing CM10). However my question is this, what happens when more firmware comes out? I have to re root and start over again?
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
dandydon414 said:
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
Click to expand...
Click to collapse
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
bbqsfire said:
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Hmm, over the past couple days I've tried out a few different ROMs on my girlfriend's S3 here, and on each one I would get this "Could not connect to the camera" error, every single time upon opening the camera app. One of the Paranoid Android ROMs, Liquid Smooth, and Synergy (even the Touchwiz camera was broken on that!).
I can restore to the original backup I made of the stock ROM, and the camera works fine again. But as soon as I try a different ROM, no camera.
I'd love to get an AOSP ROM running on this phone, but having a working camera is a requirement, and I can't figure out what I'm doing wrong. Searching the individual threads for the ROMs yields little help, and I'm getting exactly the same error on different ROMS, so I feel like I'm doing something wrong on a higher level. Any chance that switching from TWRP to CWM would make a difference? I don't see why it would, but I suppose it's something I could try.
bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
CZory91 said:
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
Click to expand...
Click to collapse
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Watanuki-Kun said:
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Click to expand...
Click to collapse
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
CZory91 said:
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
Click to expand...
Click to collapse
Probably best, that would be my first thing to try if I had that problem, restarting from scratch. If all else fails, restarting from scratch will wipe out everything. If that failed, I would probably suspect hardware issue.
Watanuki-Kun said:
Have you tried odin back to MB1...
Click to expand...
Click to collapse
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
dandydon414 said:
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Click to expand...
Click to collapse
Well I would recommend liquid 2.5 with the kernel that comes with it and I never change any of the overclocking settings. I don't have to pull the battery at all on this one.
Sent from my SCH-I535 using xda premium
TunedReference said:
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
Click to expand...
Click to collapse
Yep, that's what I tried. Nothing.
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!