Related
So after receiving my replacement vibrant i've decided to simply root and use some of the apps i used to like. Assuming i don't end up breaking under pressure and flashing a ROM, will things such as morphs and changing system apps not allow an OTA to successfully flash and boot? I did apply a black bar mod with an accurate battery but other than that i've done nothing but app related activities that require root. So, say when the official 2.2 comes out, would i have to revert my framework to stock as well before accepting the update? Like I said, currently I remain on stock JI6 with the stock kernel.
I think you need to be completely stock, no mods, for an ota to take. If not you'll most likely brick
Sent from my SGH-T959 using XDA App
That's not true. You can have all kinds of mods. The only thing you need is touchwiz running during the ota time frame and you will get it.
Sent from my vibrant
For instance I was running jfd and jacs oc/uv kernel and a battery mod + a meta morph theme and no home replacement app and I got the update
Sent from my vibrant
blackerwater said:
For instance I was running jfd and jacs oc/uv kernel and a battery mod + a meta morph theme and no home replacement app and I got the update
Sent from my vibrant
Click to expand...
Click to collapse
yeah, but did it work? were your mods still there? i was told that having a different kernel will not allow the update to come through
My phone went to stock . Booted up with stock ji6 with ji6 kernel . I had to reroot even though my super user app was still there and reapply mods just like when you odin a stock rom . The only difference was my apps stayed in system/app and system/app-private and carried over with the update.
Sent from my vibrant
Hmm, I was just basing my comment on all the threads saying there were modded and ended up brickin...i havent even got the update yet so I dont know for sure
Sent from my SGH-T959 using XDA App
metalfan78 said:
Hmm, I was just basing my comment on all the threads saying there were modded and ended up brickin...i havent even got the update yet so I dont know for sure
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The ones that bricked were probably running voodo . That changes things... So if your running stock jfd and a voodo kernel your most likely to brick. But odin will save you.
O and you haven't recieved the ota yet?? That sucks. Why havent you used keys mini from samsung thats an official way to upgrade.
Sent from my vibrant
All I had at the time was root, clockwork rom, titanium backup and launcher pro and mine bricked (well soft bricked)...
Now, I'm running bionix 1.9.1 and loving it...hahahaha
Ive never used mini kies before, I wouldnt trust my old ass pc, I try not to use odin too much either
Sent from my SGH-T959 using XDA App
blackerwater said:
The ones that bricked were probably running voodo .
Click to expand...
Click to collapse
Mine soft brick , no voodo
You who reverted to 1.7x PRI because of 100% wake, any issues with newer radio & ROM?
I have an [originally] 3.29 ROM w/ 0003 HW. I flashed to a 3.70 ROM/#15 Kernel, then updated WiMax, radio, PRI, and NV. I noticed the 100% wake time problem (as reported by Spare Parts).
I flashed back to 1.7 PRI and problem went away.
Question is, has anyone seen issues with 1.7x PRI running with 1.90 NV, the newest radio, and 3.70 ROM/#15 kernel? Do they all get along?
I read in another post that someone with a stock, non-rooted Evo that had the OTA update and saw the same problem.
Also, has anyone with the issue been able to resolve it and be able to use 1.9 PRI without 100% wake?
Thanks.
I had the same issue with a 3.30 rom on a 1.90 and I had 100% wake i went back to 1.77 abd I'm all good now.
warm2. 2 rls5 plays nice with 1.9. with rls4 i too had to downgrade to the old pri. all good now though.
Sent from my PC36100 using XDA App
yeah rls5 plays nice because its a 3.70 rom. rls4 was a 3.30 rom so it needed the 1.77
Using final VaelPak 3.0 with SBC for 4.1.9.1 and newest radios, mine's working just fine. No 100% wake for me.
It strage that some people, including me, are seeing 100% wake with 3.70-based kernels and 1.90 PRI. When they (and me) revert to 1.77, the wake issues go away.
I'm still curious why this is and how it can be resolved...
I had to reactivate my evo. It currently has MikG 2.45 on it. I am getting data connection errors. Wifi is working fine. I also can not update my profile.
This a radio thing? Do I need to flash a stock rom or can I flash something 'smaller' than will allow me to not have to reload apps?
Will nandroid restore fix it?
Thanks.
You will need to update your profile to fix it. If you cant do it on this rom, make a backup, flash a stock rom, then update the profile and flash back
Thanks a bunch!
Sent from my PC36100 using Tapatalk
Id flash 2.5 I had issue with 2.45 and have been solid with 2.5 which was released today
So I'm thinking about rooting my Nexus S and keeping the stock rom, now my question is if I do root will I not receive the OTA update for ICS or will I still get it?
Sent from my Nexus S 4G using XDA App
A little reading wouldn't have hurt............
Anyways, if you do not modify anything in /system then you should be fine. I wouldn't ever be worried about receiving an ota anyways. Chances are someone will post the full rom here before your phone ever recieves the ota notification.
Sent from my Nexus S 4G using xda premium
Thanks for the fast reply, I new I was going to get hit with the not reading part, but rooting was something I thought of on an impulse and I did as much reading as I could before I got into work so I thought I would ask for a quick answer. Now that I have the answer I have a lot more reading to do before I even try to root.
Thank you again for the answer.
Sent from my Nexus S 4G using XDA App
Frost0113 said:
So I'm thinking about rooting my Nexus S and keeping the stock rom, now my question is if I do root will I not receive the OTA update for ICS or will I still get it?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
You WILL get the OTA update
Guys sorry if this a noob question. But I just recently rooted as well .
I'm running stock rom and francos kernel. Will stock rom and diff kernel mess up if you accept ota?
I'm also looking at trying diff kernels like trinity teuv.
I know I have to wipe cache and dalvik when flashing another kernel however some state to reflash the rom as well. I'm on stock so nothing to really reflash . What steps should I take to make sure kernels don't conflict.
Sent from my Nexus S using Tapatalk
I've had wifi driver issues when flashing kernel outside of rom flash also, sometimes it works fine, other times I get the wifi error. Do not update ota if your using a custom kernel and recovery, you must be 100% stock to do so. There are stock flashable roms however, google peter Alfonso, his stuff is in rom manager as well. Also bugless beast is a stock based rom with many improvements, very stable also. Perhaps check it out.
Follow the leader @corythug
corythug said:
I've had wifi driver issues when flashing kernel outside of rom flash also, sometimes it works fine, other times I get the wifi error. Do not update ota if your using a custom kernel and recovery, you must be 100% stock to do so. There are stock flashable roms however, google peter Alfonso, his stuff is in rom manager as well. Also bugless beast is a stock based rom with many improvements, very stable also. Perhaps check it out.
Follow the leader @corythug
Click to expand...
Click to collapse
Always disable wifi before flashing a rom. In fact putting your device into airplane mode is the safest bet.
Sent from my Nexus S 4G using xda premium
I'm not saying that's not good advice but I have done both and still had the error, but I'm sure it doesn't hurt.
Follow the leader @corythug
If you're rooted, most likely you will not get the OTA notification. That's not a big deal. When ICS hits, it's going to hit here just as quick if not quicker. You'll most likely get an error if you try to flash an official OTA on a rooted device, has to be stock.
Btw, Oxygen is my ROM of choice, so I await his ICS 4.0 ROM anyway. Heck with the OTA.
Sent from my Nexus S 4G
So I rooted today, before I rooted I was on 2.3.7 after I rooted I was on 2.3.4 and it told me there was an update, so I took the update the screen went black showed the picture of the Android with a ! Next to it, after about an hour I pulled the batter and when I booted back I was still on 2.3.4 and it no longer says I have an update.
Sent from my Nexus S 4G using XDA App
Manually update, look in rom manager under peter Alfonso for 2.37
Follow the leader @corythug
Okay folks, if somebody could bring my issue to the attention of anybody who knows what to do about it I would appreciate it.
My issue is twofold:
1)I'm still getting random reboots with RandomROM Thunderhawk 3.3 despite the posting on the thread that says (NO MORE REBOOTS) Is there anything that can be done about this?
2)I checked my baseband version and the modem is still EC05, is there a way to flash or ODIN an EI22 modem for this ROM without getting a black screen when the icons should come up? Could this also be what's causing the reboots?
Thanks for anybody's help that is willing to give it.
Are you using a custom theme? And you have to flash the stickied modem delta. If you are using a theme, I would blame that.
Sent from my ICS NookColor using Tapatalk
I was using thunderhawk too and I had some reboots but onlyyyyy on the lockmod version. When I flashed the regular one I had no problems at all
And for basband I would probably try this
Nandroid backup
Flash "ec05 to ei22" its somewhere in the development section I believe
Reboot
If that doesn't work then a fresh new start is what I would Recommend
Odin back to stock
Root
Install cwm
Flash "eco5 to ei22" modem
Flash thunderhawk 3.3 (without lockmod if you could live without it)
Sent from my SPH-D700 using XDA App
I got the EI22 modem here and flashed it in CWM and it worked well. Only problem I had with thunderhawk is the lockscreen mod, and I'm having data issues on wifi after the phone's been on a while.
I was ec05 but when I flashed the Thunderhawk and it changed to ei22. never had a problem. Got a wild hair up my butt to flash the shadow kernal 1.0.6. Never been happier. no reboots, wifi works perfect, and very responsive. running a live wall paper and still get awesome battery life. give it a try
I saw several posts from folks having some wifi-4g interaction problems...switching back and forth causing one or the other to fail...is that a common problem to all 3.3 users, or are most people not seeing it? I want to give this a try, but I use 4g (at work) and wifi (home) everyday, so I'd like to see how common that issue is. I'm currently on Mostly-stock with Nubernel's latest released kernel...
Sent from my SPH-D700 using XDA App
So...bummer. I guess I answered my own question...I installed Thunderhead 3.4.3 and sure enough... I have wifi and 4g problems. Seems like going back and forth between the two causes issues...had it fail going both ways today. On a positive...man, that ROM seems pretty nice and his new install process rocks...was seamless going from Mostly Stock...
Sent from my SPH-D700 using XDA App
You could always try a clean install with doing a factory data reset in CWM and wiping Dalvik, flash ROM, check to see if stuff works, then do an advanced data restore from your last nandroid. If you stll have problems then the best bet is to set everything up fresh after the clean install.
Cluefree said:
So...bummer. I guess I answered my own question...I installed Thunderhead 3.4.3 and sure enough... I have wifi and 4g problems. Seems like going back and forth between the two causes issues...had it fail going both ways today. On a positive...man, that ROM seems pretty nice and his new install process rocks...was seamless going from Mostly Stock...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
The deal with the wifi/4g issue is that 4g will show 0.0.0.0 for ip, baseband, and dns if used after wifi in most cases. This is on official releases of 3.3 and newer. If you turn off wifi, reboot, then turn on 4g it should work. This is oviously annoying. Random provided me with alpha builds of 3.4 and 4.0, and the issue was squashed for me. However, the issue still persists in 3.4.3 official release according to some reports. I have limited access to 4g and can only test on certain days.
Thunderhawk is in a transitional period right now, and 3.4.5 should be released today. Random is hopeful this might solve some issues, including the dialer issues some are reporting with the 3.4 official builds. After that his focus will be on 4.0, which is EL30 based. Consider anything from 3.4 on a beta, and only run it if you want to help find bugs. Obviously you don't mind reporting or I wouldn't be replying lol. Just follow the threads and wait untill it looks stable enough for your usage needs.
Sent from my SPH-D700 using xda premium
Thanks! I certainly wasn't busting on Random's work...and I know he has limited access to 4g for testing, so that makes it harder for him to verify these things. So
I absolutely saw what you describe going from wifi to 4g. Going from
4g to wifi, I had wifi that wouldn't turn on at all (error when trying to enable), and, like you and others have mentioned, a reboot resolved both cases. I will hang out and see if he pushes out a fix soon, and just eagerly await 4.0. If it gets too annoying, I'll restore to my
Mostly Stock... Hmmm... Is there an issue restoring an rfs backup if I am now on ext4? Heh...
Sent from my SPH-D700 using XDA App
Just installed the latest 3.4 revision...I think...Heh. The update was so fast its hard to tell!
Sent from my SPH-D700 using XDA App
And...confirming...the wifi/4g issue persists. 4g ip address is messed up on the first connect after being on wifi...reboot resolves.
Sent from my SPH-D700 using XDA App