I have come to the conclusion that something is wrong with my phone. I have tried to install ICS....a lot. I am not exagerating when I say that I have tried every Odin install, and every ICS ROM that has more than a few positive results. Nothing will work. I am not new to flashing, I have had a Captivate, Inspire, Tab and have had no issues with those, even created a few themes and build.prop tweaks. I know what I am doing and I follow the OP instructions perfectly. The damn thing just wont take. I get the white Samsung screen, a black screen, a vibration, and a reboot. So at this point I think I am just going to stick with GB for right now and hope that either the offcial ICS update works (when available) or maybe 5.0 later this year.
Two weeks of try to make this work has run me ragged. Outside of the ICS issues though this is by far the best device I have had in terms of performance and reliablility.
Rant over.
Did u flash the uclc5 radio at any point in time?
If not what radio did u install, and did u install it before u flashed ics rom?
What recovery were u using?
Did u odin back stock in between each ics attempt? Did u use dark side wipe at all?
*#* Google dropbox, its useful.
https://www.dropbox.com/referrals/NTcwNDE0ODUyOQ *#*
icenight89 said:
Did u flash the uclc5 radio at any point in time?
If not what radio did u install, and did u install it before u flashed ics rom?
What recovery were u using?
Did u odin back stock in between each ics attempt? Did u use dark side wipe at all?
*#* Google dropbox, its useful.
https://www.dropbox.com/referrals/NTcwNDE0ODUyOQ *#*
Click to expand...
Click to collapse
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
lacer4576 said:
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
Click to expand...
Click to collapse
Personally, I haven't had anything but trouble with superdarkside. Its an excellent tool, but for me, hasn't meshed well with ICS. You should try following seans op for Sky ICS UCLC4, without using darkside at all to change from where your at now.
Also, the modem (aside from UCLC5 for some) has no effect on the installs, I sat on Sky ICS UCLC4 with the UCLC3 modem for a couple weeks without any issues at all.
I have tried all of the CWM mods posted here, and to be honest, my favorite is the CWM touch when installed from rommanager. Seans roms seem to take better with it more than the rest. The CWM touch that is posted on the sky UCLC4 OP is good, but it has a couple minor bugs.
Are you using SuperSU or superuser? Supersu has backfired on numerous occasions for me, I always stick to superuser (and I'm sure I'll be flamed for the comment. Every skyrocket reacts differently, remember)
mahausrath said:
Personally, I haven't had anything but trouble with superdarkside. Its an excellent tool, but for me, hasn't meshed well with ICS. You should try following seans op for Sky ICS UCLC4, without using darkside at all to change from where your at now.
Also, the modem (aside from UCLC5 for some) has no effect on the installs, I sat on Sky ICS UCLC4 with the UCLC3 modem for a couple weeks without any issues at all.
I have tried all of the CWM mods posted here, and to be honest, my favorite is the CWM touch when installed from rommanager. Seans roms seem to take better with it more than the rest. The CWM touch that is posted on the sky UCLC4 OP is good, but it has a couple minor bugs.
Are you using SuperSU or superuser? Supersu has backfired on numerous occasions for me, I always stick to superuser (and I'm sure I'll be flamed for the comment. Every skyrocket reacts differently, remember)
Click to expand...
Click to collapse
I will give it a shot. I would really like to get back to ICS, I got so used to it on my other phones.
I have been using superuser, haven't had a problem yet from that.
lacer4576 said:
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
Click to expand...
Click to collapse
I know this may be silly but have you tried to re-download the one click leak your using? Maybe you have a bad download or a corrupt file. And, or try to use a different usb port when you flash. It seems you've tried everything and maybe you have a defective device. I started having a lot of issues recently after going from ROM to ROM so I just flashed the one-click to get back to a clean state and then carefully chose which ROM I wanted to use and carefully install it. I've always used Darkside Superwipe but since I've quit using it, things have been much smoother. What I do now is what most Devs are saying now is to wipe/factory reset multiple times and format/system multiple times. If thats not working maybe go all the way back to stock GB with k0nanes stock tar and go from there. As far as the uclc5 radio, be careful!! I'm sure you've read that it can corrupt a partition and cause issues. I did flash it once and it did work for 48 hours but I noticed signal loss so I flashed back to uclc2. Maybe I got lucky it didn't mess me up, who knows? And if you have an issue not receiving an official update, IF you do go back to the stock GB tar, do a nandroid and flash that when it comes out. Just make sure you flash the stock recovery before you take it. I have a stock GB backup on my SD, so IF and WHEN it does come out, I'll just flash the backup, flash stock recovery and take the OTA. With your constant bootloops, it seems to me its a bad download or a defective device. It seems you've tried everything. Good luck...
^^^ this makes sense. Also I was asking about the note radio to advise u against it, or u may end up screwing up ur phone even worse, and have to make a visit to my corrupt efs fix thread lol.
hcyplr29 said:
I know this may be silly but have you tried to re-download the one click leak your using? Maybe you have a bad download or a corrupt file. And, or try to use a different usb port when you flash. It seems you've tried everything and maybe you have a defective device. I started having a lot of issues recently after going from ROM to ROM so I just flashed the one-click to get back to a clean state and then carefully chose which ROM I wanted to use and carefully install it. I've always used Darkside Superwipe but since I've quit using it, things have been much smoother. What I do now is what most Devs are saying now is to wipe/factory reset multiple times and format/system multiple times. If thats not working maybe go all the way back to stock GB with k0nanes stock tar and go from there. As far as the uclc5 radio, be careful!! I'm sure you've read that it can corrupt a partition and cause issues. I did flash it once and it did work for 48 hours but I noticed signal loss so I flashed back to uclc2. Maybe I got lucky it didn't mess me up, who knows? And if you have an issue not receiving an official update, IF you do go back to the stock GB tar, do a nandroid and flash that when it comes out. Just make sure you flash the stock recovery before you take it. I have a stock GB backup on my SD, so IF and WHEN it does come out, I'll just flash the backup, flash stock recovery and take the OTA. With your constant bootloops, it seems to me its a bad download or a defective device. It seems you've tried everything. Good luck...
Click to expand...
Click to collapse
I will try to get a different download, but I do not think that is it. The only reason I say that is because my phone had the exact same response for EVERY ROM I have download. They can't all be bad files. I have tried on two different PCs with three different USB cables. Good thought though, I have had bad downloads before. I am going to keep trying as the ROMs are updated and hope that I figure out what is going on, and hope that I can get the official update at some point. Then I will just root it and get rid of the bloat myself if I have to
I am going to stay away from the L5 radio, not worth the hassle.
On a side note, if installing a rom from the site, remember, most will work with the "base"
But need to reset/full boot before "updating".. dont just flash rom and flash update then reboot
I had a hard time with ICS as well with different problems, all I can say is it disproves the definition of insanity. Trying the same things over and over again will eventually make it work!
Hang in there, it's worth it. Whenever you do get the ODIN one click to work I highly recommend flashing Raider03's SMOOTHIE ROM. Awesome battery life and extremely "SMOOTH"! But be prepared for a few FCs and bugs with all of the ICS ROMS for now!
Related
....in between flashing new ROMs?
Even in the same ROM family?
Why?
Not having to do this with Incredible ROMs, and was just curious. Thanks for any input.
rfarrah said:
....in between flashing new ROMs?
Even in the same ROM family?
Why?
Not having to do this with Incredible ROMs, and was just curious. Thanks for any input.
Click to expand...
Click to collapse
Rom flashing is not perfect so sometimes things dont get overwritten. it has been known to fix some odd issues. Some will say you dont have to and others will say it is the safest way to know if there is an issue with the rom or if it is due to some bit of the old rom that didnt get over written
Flashing back to stock is like erasing a chalkboard before you write on it.
You can try to skip this step and flash one on top of the other, but you could very well run the risk of a bad install with symptoms like force closes, bad/non-existent data connection, etc. Yes, there are people out there who don't flash back to stock and wipe the phone who say they've never had any problems, but that's like shooting dice in my opinion.
It takes less time to use Odin to go to stock, and flash the desired custom ROM than it does if you skip Odin, have a botched install, and have to redo the entire process again.
Only if you have problems.
used to be able to flash any combo...even I-9000 roms(darky's...) with proper kernel and modem combos.
Had no problems ever!
Now, ANY combination kills my signal. Paragon; perception, pheonix, the list goes on and on.
The only ROM i can run is Cognition. If i flash to a different kernel/modem combo,(even while running cognition) I have problems.
Now atleast I am stuck with a good ROM, but I would love to fine-tune with a different kernel/radio and I have NO idea why my phone is acting this way. I am thinking maybe it's a SIM card thing(I pulled the SIM out one timebefore the phone was fully shut down...
other than that I cannot think of anything weird I have done.
In between flashes I have ODIN'd back to H2 and then Master Cleared.
Flash via CWM. Root with 1-click.
PLEASE give me some idea of what I have done?!?!!?
Or is it warranty time for the phone due to 'GPS' issues..
Thanks
boardsportsrule said:
used to be able to flash any combo...even I-9000 roms(darky's...) with proper kernel and modem combos.
Had no problems ever!
Now, ANY combination kills my signal. Paragon; perception, pheonix, the list goes on and on.
The only ROM i can run is Cognition. If i flash to a different kernel/modem combo,(even while running cognition) I have problems.
Now atleast I am stuck with a good ROM, but I would love to fine-tune with a different kernel/radio and I have NO idea why my phone is acting this way. I am thinking maybe it's a SIM card thing(I pulled the SIM out one timebefore the phone was fully shut down...
other than that I cannot think of anything weird I have done.
In between flashes I have ODIN'd back to H2 and then Master Cleared.
Flash via CWM. Root with 1-click.
PLEASE give me some idea of what I have done?!?!!?
Or is it warranty time for the phone due to 'GPS' issues..
Thanks
Click to expand...
Click to collapse
Find the modem cognition uses that gives you the least problems. Are you flashing to stock before each ROM?
Sent from my SAMSUNG-SGH-I897 using XDA App
Yep, back to stock & master cleared between(only once problems arised..back in the day I could just flash to what I wanted and never really had a problem. Went back to stock once when the new flash responded strangely.)
Looking at cognition, I get minimal information, I THINK it's stock radio/kernel..
http://forum.xda-developers.com/showthread.php?t=912657
Any one???
I would..check your usb plug/cable/port first..make sure it isn't bad and effecting your data transfer..Make sure your not plugged into a external port and plug into PC directly..
Re down load your roms and kernels again..keep them separate from what you have already used..
Flash back to stock..master clear delete all data on your internal and your data
Re-install everything over again..cause it sounds like something got corrupted along the way
Mac
Mac11700 said:
it sounds like something got corrupted along the way
Click to expand...
Click to collapse
Thats how I am leaning, but i dont think it's with the roms/kernels/radios i have downloaded...since I have tried so many damn copies that wouldn't make sense. also tried downloading directly to phone, eliminating the "3rd party" computer, and have used drop box in the past...
I have flashed to stock and master cleared, i could do it again, but i am tempted to go back to stock and try to exchange it for a new one due to either random shut-offs or GPS(both of which mine are effected by..) but i would like to avoid this hassle...
If something did get corrupted, any idea how I'd solve that? I am at a loss as to what could have gotten corrupted that a odin'd stock + master clear wouldn't solve...?
boardsportsrule said:
If something did get corrupted, any idea how I'd solve that? I am at a loss as to what could have gotten corrupted that a odin'd stock + master clear wouldn't solve...?
Click to expand...
Click to collapse
It's possible that your phone has a hardware issue making it more finicky. Try stock for a bit and see if the problems go away. Maybe try Andromeda 1.0 and see how the KP1 modem works (or just flash KP1 on some other ROM).
opcow said:
It's possible that your phone has a hardware issue making it more finicky. Try stock for a bit and see if the problems go away. Maybe try Andromeda 1.0 and see how the KP1 modem works (or just flash KP1 on some other ROM).
Click to expand...
Click to collapse
hopped back to Stock... Gonna run things here, see which problems arise, and go from there. Can you flash a different kernel onto the stock ROM? I'd assume you need a 2.1 kernel, and i don't think many are retrofitted to 2.1, but the KP1 modem is a good idea, ill let things pan out on stock and see what happens if/when i flash kp1 modem.
funny fact: fire fly made problems for me... it's based on rogers 2.2, same as cognition. that seemed odd to me.
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
nvertigo said:
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
Click to expand...
Click to collapse
Yes, you can use the one-click to put KJ6 on there then flash a different ROM via CWM.
Personally I've had the best experience with Valhalla ROMs. Last night I just flashed RAVERX3X latest Valhalla Black build. Its low profile so it's quick and responsive, and even better, not a single instability issue.
Sent from my SGH-T959V using XDA App
thanks for the advice guys!
I did the first flash step, which worked successfully and rebooted my phone. then i tried to flash the bootloaders that came with it, but uploading PIT 1/10 failed, and it froze trying to end session. i pulled the battery and the phone seemed bricked, but i connected the cable and oneclick said it was connected (no download mode screen, no lights at all). so i did the initial one-click flash and let it reboot again, then flashed valhalla black.
nothing SEEMS to be wrong, but i'm a little scared. can anyone weigh in on what happened?
You're ok. I can't explain what happened but people have reported similar issues, nothing on the screen but it can be seen in ODIN, and were able to recover (as you did) just fine.
Sent from my SGH-T959V using XDA App
This section of XDA is small, but good in terms of quality.
I just flashed Raver's Cyanogenmod/Valhalla hybrid and it is smooth and stable.
One-Click...
At the beginning of the week, I still had Froyo on my device.
I used Bryan's one-click (SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar)...
(I had a scare, too... which involved the so-called "Rainbow screen" -- but FB suggested I run the one-click, again and also to do the Bootloaders -- and everything turned out ok).
But, I needed to get CWM 5 (and, that particular one-click had CWM 3.0.2.8x)
So, I flashed an update of Bryan's kernel (sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip)
And, because I was feeling overjoyed at all the goodness that I'd seen so far, I flashed RaverX3X's rc3.zip (from Team Acid's Source Forge site)...
And, life is really, really, really... good.
yep
+1 Valhalla black edition! Installed today and love love love.
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
nvertigo said:
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
Click to expand...
Click to collapse
Not sure about the crashing but I experienced reboots because of the kernel Valhalla Black uses. There are fixes out there for that part of the problem but what you should really is perform a factory data reset, do the one to get a ROM with CWM on it, then use CWM to install Valhalla Black per the instructions on the page for it. I've a feeling you'll be much more stable after that.
As for the 10 minutes, that's basically to allow your phone to rebuild the Davlik cache (cache with optimizations for your apps). Definitely let it sit while it does that just to be safe.
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
nvertigo said:
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
Click to expand...
Click to collapse
If it was fully booting and you weren't getting the "rainbow" screen, then your boot loaders are fine. If in doubt, go check out bhundven's one-clicks, and run one of them - twice. The first time it doesn't let you check the boot loader box but the 2nd time it does.
Valhalla Final comes with bundven's beta 2c kernel. I believe people are running that without issue. Keep in mind Valhalla Final and Valhalla Black are two different ROMs with two different kernels.
I did a one-click back to stock (factory reset, cache wipes, etc.) & am running bhundven's latest beta kernel with no problems (thus far).
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
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!