So I have previously rooted my phone. I flashed it back to stock using the stock firmware. Updated my phone to the official ICS release. Now after i upgraded the phone would not recognize my sim and it would only display the notification bar. There is nothing where my background and apps used to be. I tried samsung support and they suck balls. I also tried the leaked rom and the same thing happens.
Did you try to call ATT?
Getting this exact same issue, and I updated from stock. Never rooted or modified the device at all.
The same thing happened to me, I updated from stock. ATT had me wipe the whole phone and now I have to send it back for RMA.
Yeah, we're in the att warranty center. They're trying to flash it, and are going to replace it if it doesn't take.
Sent from my HTC One X using xda premium
All they did was flash the device back to 2.3.5 and give me a "try again and see if it works."
Well, tried it again. It didn't work.
Need to find a way to get back to 2.3.5 at home so I can use this phone until I've got a chance to RMA it.
--Edit--
Got it back to 2.3.5 using by flashing CWM6, Inception, then using Odin to get back to 2.3.5, factory resetting at every step. Tried using Kies, the ICS leak, the CWM Flashable version of the leak, nothing works. I get no information other than it force closes the Installer after about a minute at the black screen (which has a status bar, and allows me to pick WiFi networks and set up a Samsung account).
I'm at a loss. Going to have to wait for AT&T to either RMA it or update their warranty center flash to ICS. Either way, leaving it at 2.3.5 for now. If any dev feels adventurous and wants to try to tackle this, just PM me and I'll get you any info you want/need.
It happened to me when I updated to ICS two days ago. Exact same thing, black screen, notification bar only, no service. Once in a while I would get a message about "application installer" not responding.
Long story short, I just waited and it sorted itself out. Maybe something was installing the whole time, I don't know. It took an extra day for my service to come on.
About how long would you say?
Sent from my Nexus 7 using xda premium
trunicated said:
About how long would you say?
Click to expand...
Click to collapse
Maybe 2-3 hours? I would give it overnight at least before sending it in.
Gave it about 24 hours and it completed. It's having issues seeing the SIM card. It's weird, it connected to the network without a SIM card (emergency calls only), but didn't pick up the SIM when i put it in, so i restarted it. Now is doesn't connect it see the card.
I'll play with it more tonight, just dropping by to say thanks for the help so far!
Sent from my HTC One X using xda premium
trunicated said:
Gave it about 24 hours and it completed. It's having issues seeing the SIM card. It's weird, it connected to the network without a SIM card (emergency calls only), but didn't pick up the SIM when i put it in, so i restarted it. Now is doesn't connect it see the card.
I'll play with it more tonight, just dropping by to say thanks for the help so far!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
That's exactly that happened to me. Even now it seemingly randomly stops recognizing my SIM.
I had the same problem. I had to reinstall devs rooted ics then ran ATT stock ics and rerooted. No longer on leaked ics and currently on ATT stock ics with root
Sent from my SGH-I927 using xda premium
justqt said:
I had the same problem. I had to reinstall devs rooted ics then ran ATT stock ics and rerooted. No longer on leaked ics and currently on ATT stock ics with root
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
I am having the same issue I tried flashing to the leaked version still no luck now I cant flash to the ATT version using Kies...
Does anyone care to hook me up with a file and instructions for flashing back to Gingerbread? I am a total Noob and I apologize in advance.
Look at my other post and maybe it will help u out.
http://forum.xda-developers.com/showthread.php?t=1878643
Sent from my SGH-I927 using xda premium
---------- Post added at 01:01 AM ---------- Previous post was at 12:48 AM ----------
Did you guys do wipe on cache and reset? Maybe try that and reinstall.
Here is the Stock ATT Gingerbread ROM:
http://phile.mobi/fw/I927UCKI3_I927ATTKI3_ATT.zip
justqt said:
I had the same problem. I had to reinstall devs rooted ics then ran ATT stock ics and rerooted. No longer on leaked ics and currently on ATT stock ics with root
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
So you had the stock, flashed rooted ICS, the flashed stock ICS, then flashed CWM, and now you don't have problems with your Sim?
Sent from my Nexus 7 using xda premium
Yes.. exactly. Think it is maybe a permission prob? Try cwm fix permissions. Just guessing on permission.
Sent from my SGH-I927 using xda premium
justqt said:
Yes.. exactly. Think it is maybe a permission prob? Try cwm fix permissions. Just guessing on permission.
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
Did you flash them with CWM? And when you flashed them, did you have to wait the giant amount of time for them to come back up like I said I did earlier in the thread?
I flashed stock att the regular "download" way however I wanted to get keyboard light to work so I installed cwm6 then installed superuser and keyboard fix through cwm6. For some reason the first time I went from ics rooted to att ics I got stuck on samsung loading screen. I think it all comes down to permissions. I hope I'm making since here.
And to the time thing, no I didn't have to wait.
Try what others have said... wipe everything, install which ever version u want. But if u get stuck on samsung thing reinstall devs ics root to fix samsung loop
Sent from my SGH-I927 using xda premium
Related
I just rooted and flashed beast mod on my gs2. An hour after using it, T-mobile popped up in my notification tray with a new update. I'm assuming this is 2.3.6 and eventually the dev's will develop or update their roms.
I just want to make sure that I shouldn't update my phone this way, or I will be bricked?
i dont think it will brick you, but it will unroot you.
[Q] got prompted for OTA Update but i'm rooted / custom ROM?
I have a rooted sII and i just received a software update for my phone. do you know if i install the update will that affect anything?
I lost my root installing the update. looking to re root now.. It alos reinstalled all the Tmo bloat ware again.
[Q] got prompted for OTA Update but i'm rooted / custom ROM?
Well T-Mobile just sent me a update ofcourse I'm rooted I dont want to officially update.the annoying part is the notifaction for it wont go away and its really annoying ? Any suggestion how to get rid of it?
Sent from my SGH-T989 using XDA App
Same Problem Here...
Hi-
I rooted my phone a month ago. I have had no problems except that when I try to download T-Mobile's software update, I get stuck in Clockwork recovery. I don't know what to do next.
Please help!
Thx!
(I rooted my phone based on Melvin's [HOWTO] ROOT T-Mobile SGSII via ODIN -- Updated Recovery on 10/20/2011 and the recovery by Bubbly in the Developer's Forum.)
ritthyhang said:
Well T-Mobile just sent me a update ofcourse I'm rooted I dont want to officially update.the annoying part is the notifaction for it wont go away and its really annoying ? Any suggestion how to get rid of it?
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
I was on same boat till yesterday . There is stock ROM 2.3.6 on android development section. Download it and install from cwm.
Make sure you dont postpond the update otherwise it will be pain in back.
Sent from top of Mt. Everest using my SGH-T989 using XDA App
bikrame said:
I was on same boat till yesterday . There is stock ROM 2.3.6 on android development section. Download it and install from cwm.
Make sure you dont postpond the update otherwise it will be pain in back.
Sent from top of Mt. Everest using my SGH-T989 using XDA App
Click to expand...
Click to collapse
I rebooted my phone and left the notifaction alone dont want or need to update to 2.3.6 I hope jugs update soon so I can get rid of this problem
Sent from my SGH-T989 using XDA App
Upgrade
I'm on Bombraider by TricH and I have the notification for the update. What will happen if I run it?
Juggernaut v3.7 and Tmobile software update????
I am using Juggernaut v3.7 ROM, and my phone recently constantly show Message about upgrade the software from Tmobile. What should I do next? Flash stock rom 2.3.6 to get rid of Tmobile upgrade? and then can I flash Juggernaut v3.7 back to my phone?
Is there any way to disable (inside the code or build.prop file) the upgarde notification?
chicamama said:
Hi-
I rooted my phone a month ago. I have had no problems except that when I try to download T-Mobile's software update, I get stuck in Clockwork recovery. I don't know what to do next.
Please help!
Thx!
(I rooted my phone based on Melvin's [HOWTO] ROOT T-Mobile SGSII via ODIN -- Updated Recovery on 10/20/2011 and the recovery by Bubbly in the Developer's Forum.)
Click to expand...
Click to collapse
i have the same question
T-Mobile update service
Can I do the T-Mobile update while rooted on a custom rom?
Sent from my SGH-T989 using xda premium
This is going to be a hot item for most of us with rooted phones. Simply no way of knowing what will happen should we let the update go through. And just to be safe, most of us would prefer to cancel the update.
I followed someone else's advice and used Titanium Backup Pro to:
- wipe data for "Device Manager"
- "freeze" the same application
The nag is gone. I reckon this method should work for everyone with rooted phones.
Otherwise, we'd need to wait to respective ROM teams to release their own patches etc.
TB team should see a nice uptick in app purchases in next few days. The app is well worth it, so if you been on a fence, get it now, $6 well spent.
[Q]OTA Update but i'm rooted?
I just got the ota update. It says it's going to automatically update my phone in 24 hrs. Is this going to mess my phone up? I am currently rooted with. Bombradier rom. Do I need to do anything? Thanks
Sent from my SGH-T989
i am rooted with stock rom and receive the update, np at all. In your case, you have a different rom and not stock. odin probably is the best bet.
bought sgs2 last weekend and rooted using superoneclick and at the end of the day, receive ota update and update my sgs2 and i forgot that i am rooted. i left my phone to finish updating and when i came back, its up and have 2.3.6 uVKL1, did not receive any problem. battery great, wifi calling is there. im just surprised it let me update even though my phone is rooted. btw stock rom, stock kernel just rooted.
I think I'll just wait until somebody comes out with an official sticky solution because I didn't flash any ROM to mine, I just rooted it.... I don't know what to do either... Until someone posts a solution there will be several posts pertaining to this subject
Sent from my SGH-T989 using XDA App
updates to OTA 2.3.6 and you lose root
+1
gabriel713281 said:
I think I'll just wait until somebody comes out with an official sticky solution because I didn't flash any ROM to mine, I just rooted it.... I don't know what to do either... Until someone posts a solution there will be several posts pertaining to this subject
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
rashid11 said:
This is going to be a hot item for most of us with rooted phones. Simply no way of knowing what will happen should we let the update go through. And just to be safe, most of us would prefer to cancel the update.
I followed someone else's advice and used Titanium Backup Pro to:
- wipe data for "Device Manager"
- "freeze" the same application
The nag is gone. I reckon this method should work for everyone with rooted phones.
Otherwise, we'd need to wait to respective ROM teams to release their own patches etc.
TB team should see a nice uptick in app purchases in next few days. The app is well worth it, so if you been on a fence, get it now, $6 well spent.
Click to expand...
Click to collapse
Thanks for posting this. I tried this method and it works great.
Hello to all - does anyone know what the Chameleon has FC error means. I did try to flash the LK8 and I know that may cause it. However I did just unroot and I am still getting the error? Any ideas?
the12nv said:
Hello to all - does anyone know what the Chameleon has FC error means. I did try to flash the LK8 and I know that may cause it. However I did just unroot and I am still getting the error? Any ideas?
Click to expand...
Click to collapse
For now just stay on lk8. I've tried everything with no luck.
Sent from my SPH-L900 using xda premium
rwright64 said:
For now just stay on lk8. I've tried everything with no luck.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
+1 10 chars
See the update lk8 update Zip thread. Another member who I can't remember at the moment figured it out. The fix is to odin ljc using a tar or the stock restore exe. Then redo the lk8 update.zip and the chameleon error goes away.
Sent from my SPH-L900 using Tapatalk 2
pwhitersxs said:
See the update lk8 update Zip thread. Another member who I can't remember at the moment figured it out. The fix is to odin ljc using a tar or the stock restore exe. Then redo the lk8 update.zip and the chameleon error goes away.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
worked like a flippin charm - thanks for pointing this out - this is super helpful and I am now updated to LK8 - SSSAAAWWWWEEEETTTT!!
anyone try to format DATA and install an LJC room? I think LK8 have some error in the build.prop script.
K.0.0.L. said:
anyone try to format DATA and install an LJC room? I think LK8 have some error in the build.prop script.
Click to expand...
Click to collapse
I have it don't fix it. It's some left over code if you flashed an LK8 rom and went back to an LJC. I have run throught every format option in TWRP and used Odin to flash a factory stock image. No one seems to know where it's coming from!
modmandan said:
I have it don't fix it. It's some left over code if you flashed an LK8 rom and went back to an LJC. I have run throught every format option in TWRP and used Odin to flash a factory stock image. No one seems to know where it's coming from!
Click to expand...
Click to collapse
Darn.....our hope is up to Chainfire
pwhitersxs said:
See the update lk8 update Zip thread. Another member who I can't remember at the moment figured it out. The fix is to odin ljc using a tar or the stock restore exe. Then redo the lk8 update.zip and the chameleon error goes away.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
When I do this I cant connect to wifi ive dtried this like 3 times and every time I update to lk8 I loose wifi.
Sent from my SPH-L900 using Tapatalk 2
Just my 2 cents, my experience with this error.
I'm getting the Chameleon FC, and the persistent HandsFree Activation on every reboot. All started when I lost wifi on the LK8 update zip (I was rooted, thanks to Voodoo OTA rootkeep), and tried to get back to LJC...
I'll quote myself from another post (written in a slight daze late last night:
kingdazy said:
well, this is annoying. I seem to be stuck with the "hands free activation" and chameleon fc.
i'm assuming a nice total stock one click should fix it?
Click to expand...
Click to collapse
garwynn said:
Sure should! Please try the stock restore or rooted restore.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
kingdazy said:
interestingly, it didn't fix it... "preparing network", "hands free" and chameleon FC on every reboot. this is after the rooted full restore OC. what am I missing? weird.
(history: I was rooted stock w/ twrp from the mskip toolkit method of rooting, got rid of twrp using the mrRobinson stock w/ root, and flashed the sxtp update to lk8, got a wifi failbug and tried to get back to stock rooted using mrRobinson and started getting this issue. lol. ok. so... one-clicked your rooted full restore, still there. is that even possible?)
well, my phone seems to work, as long as I don't reboot.
but I find it worrisome.
have to sleep for work now, but if you had any advice for things to try when I wake up, let me know? thanks dood.
Click to expand...
Click to collapse
And this morning, I tried the following:
Installed TWRP with GooManage, restored a BU from my orig rooting using the toolkit, no luck, same two errors.
So then I OneClicked the Full Restore (SPH-L900_LJC_Stock_Restore.exe), and wtf, still there.
As I mentioned in my quote, it (the Note2) works, not broken, but I find the persistent error worrisome.
I am open to criticism, suggestions, whatever. What am I missing?
I feel exactly how you do. The phone works but the errors are bothering me.
Sent from my SPH-L900 using Tapatalk 2
I suppose that it's worth noting that I get no errors whatsoever on flashing, OneClicks, or Odins. Although, on stock recovery (I think?) I seem to remember seeing the Android on its back w/ a red triangle?
Confounded. :banghead:
Ive never had to do a logcat, but willing to do whatever it takes on the direction from a Dev or one of our esteemed Contributors, if it will help solve my (and obviously several others) issue.
Sent from my SPH-L900 using xda premium
I've try every method but no luck. What in the god's name went wrong.
Sprint is apparently replacing these for this error. If you go into the store and have them look at it. I've been told that Sprint is replacing these devices as there is no fix until the OTA is released. That's just what I heard.
I would definitely be back to stock before paying then a visit.
Sent from my SGH-T889 using xda premium
ptfdmedic said:
Sprint is apparently replacing these for this error. If you go into the store and have them look at it. I've been told that Sprint is replacing these devices as there is no fix until the OTA is released. That's just what I heard.
I would definitely be back to stock before paying then a visit.
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Thanks! not exactly the answer I was hoping for, but an option. I am at least able to get back to stock w/ 0 flash counter, so I feel safe that they can't tell me it's *wink* my fault *wink*.
ptfdmedic said:
Sprint is apparently replacing these for this error. If you go into the store and have them look at it. I've been told that Sprint is replacing these devices as there is no fix until the OTA is released. That's just what I heard.
I would definitely be back to stock before paying then a visit.
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Finally a light at the end of tunnel.
Has anyone tried odin back all the way to ALJ1. I know T3project had a link to one the repartitioned everything basically making it completely fresh. This is how he fixed his no connection to network problem.
cincyelite22 said:
Has anyone tried odin back all the way to ALJ1. I know T3project had a link to one the repartitioned everything basically making it completely fresh. This is how he fixed his no connection to network problem.
Click to expand...
Click to collapse
Do you have the download link for the ALJ1? I'm gonna try that to see if it work.
I went back to lj1 and let it update to ljc. Errors stuck around. Only way I've avoid the errors is by leaving phone with lk8 which lucky for me works perfectly.
I did try the store replacement thing but they wanted to give me a refurbished phone as replacement. I am going to wait for an update and cross fingers it works without error.
Sent from my SPH-L900 using Tapatalk 2
I had to get a replacement but I received a brand new phone right out the box because the tech said they didnt have any refurbished ones at this point.
Sent from my SPH-L900 using Tapatalk 2
I just tried to update my ICS Galaxy S2 to JB 4.1 through Samsung Kies, and the update process took a dump on me and I spent the better part of the last two hours getting the phone up and running again. The phone is rooted, and the recovery installed is Clockworkmod touch. My battery was right at about 51% when I started, so it may have had something to do with it im not sure. Anybody successfully updated? If so can you please share your story? Thanks.
No problems for me, but I returned everything to stock first. Stock recovery included. Might've been your issue
Sent from my SGH-T989 using xda app-developers app
I had no problem updating a few days ago. Was running stock rooted ICS with CWM non-touch recovery. It took close to 2 1/2 hours including updating Kies, but it worked fine. My battery was probably closer to 85% (and I have a big aftermarket battery).
I did a few days back also. No problems when I ran it for the day.
Officially, I think the battery should be at 80% for Kies to let you update, but that is not important now.
My first attempt bricked the phone, I tried taking it to a third PC for the emergency recovery and it did not work on that PC at all.
I got a replacement phone instead of trying again, but on the 3rd and final PC it worked fine.
The first 2 PCs had windows XP while the final was W7, I don't think windows was the issue, but on the first 2 I did sometimes have issues detecting the phone, so I unplugged and plugged it back in a few times for it to connect. I think that was the key to the problem.
On the final machine it connected fine first time and every time. I still don't know why this happened. I have 2 more phones to update and am wondering if I should try the first 2 machines again or play it safe and use the one that worked?
Good luck.
hi,
for those of you who have stock rooted ics, after updating to JB, did it stay rooted?
mine is rooted stock ics.
thanks!
Sent from my SGH-T989
I updated my wife's phone, but it was completely stock and unrooted
testrider said:
hi,
for those of you who have stock rooted ics, after updating to JB, did it stay rooted?
mine is rooted stock ics.
thanks!
Sent from my SGH-T989
Click to expand...
Click to collapse
You will lose root, but it's very easy to re-root. I rooted four T989s in about ten minutes.
Using kies, went to update my wife's phone the other day with it having like 20% battery and it gave me an error message before starting saying my battery was to low. When it came to my rooted phone I used Odin and lost root. It was pretty easy for me to root it back and start installing custom ROMs.
Sent from my SGH-T989 using xda premium
Just did it today and it worked fine. Had to reinstall a newer version of Java for Kies to upgrade itself properly, but once I did that it was smooth sailing.
Hi all,
now please don't laugh: what exactly is the advantage of getting JB over ICS?
thanks.
Mike
Sent from my SGH-T989
I managed to soft brick my phone on the first attempt to use kies. Fortunately, the phone was sick on Odin download mode. I used Odin too flash a new ics image and the second time, the kies to 4.1.2 worked just fine. My original OS version was ics from the tm ota update on a new phone.
Sent from my SGH-T989 using xda premium
I had mine rooted with TWRP, but with stock radio and it upgraded without problems.
testrider said:
Hi all,
now please don't laugh: what exactly is the advantage of getting JB over ICS?
thanks.
Mike
Sent from my SGH-T989
Click to expand...
Click to collapse
There are a bunch of improvements, they took out a lot of bloatware and fixed a bunch of glitches so JB is a lot faster and smoother than ICS. Also they brought back some features that were taken out of ICS like a Contacts button in the phone (I never understood why they took it out in the 1st place)...
Sent from my SGH-T989 using xda premium
Will the stock jb from TMobile work on my Telus 989?
Sent from my SGH-T989D using xda app-developers app
I was on a rooted Stock ICS and I used Kies for the update. It was successful, but of course I lost root. Since then the phone has been faster, smoother and has better battery life. I still have not manged to re-root using either CWM nor TWRP, even after re-flashing the stock JB via ODIN, (I am still working on this).
disneytech951 said:
I just tried to update my ICS Galaxy S2 to JB 4.1 through Samsung Kies, and the update process took a dump on me and I spent the better part of the last two hours getting the phone up and running again. The phone is rooted, and the recovery installed is Clockworkmod touch. My battery was right at about 51% when I started, so it may have had something to do with it im not sure. Anybody successfully updated? If so can you please share your story? Thanks.
Click to expand...
Click to collapse
steve adams said:
Will the stock jb from TMobile work on my Telus 989?
Sent from my SGH-T989D using xda app-developers app
Click to expand...
Click to collapse
I am pretty sure through Odin, But why not install the Telus version with the new radio?
Octane70 said:
I am pretty sure through Odin, But why not install the Telus version with the new radio?
Click to expand...
Click to collapse
I didn't think telus had job for the gs2x yet.
Sent from my A210 using xda app-developers app
steve adams said:
I didn't think telus had job for the gs2x yet.
Sent from my A210 using xda app-developers app
Click to expand...
Click to collapse
think again.
Just to be safe you should always odin back to the last stock rom before doing an update through kies. You dont have to but I get nothing but pasper weights if I dont. I never had a problem with kies with a completly stock phone though. And I think thje batt is 80% but I always charge it to 100% just in case.
Just tried supercharger v6 latest black dog version on my stock rooted ROM, and after reboot it won't go past the galaxy T-Mobile splash screen. Anyone had this issue?
Sent from my SGH-T989
demoncamber said:
Just tried supercharger v6 latest black dog version on my stock rooted ROM, and after reboot it won't go past the galaxy T-Mobile splash screen. Anyone had this issue?
Sent from my SGH-T989
Click to expand...
Click to collapse
Its a issue with a lot of Roms right now, try rebooting a few times, or boot to recovery and then reboot, if that doesn't work clean install again, boot/setup phone, make data only backup, erase data only and restore the data only backup, fixed it for me on a few Roms
Sent from my SGH-T989 using xda premium
Do you know if its an issue of the latest v6 black dog? Would an older version of v6 maybe work better?
Sent from my SGH-T989
demoncamber said:
Do you know if its an issue of the latest v6 black dog? Would an older version of v6 maybe work better?
Sent from my SGH-T989
Click to expand...
Click to collapse
Its been a lot of 4.1.2 Roms if that helps, some 4.2.2, I've never flashed black dog so idk, is it a twiz or asop ROM?
Sent from my SGH-T989 using xda premium
Yeah that does help man thanks. Its the stock tmo twiz ROM, rooted. Yeah I have rebooted, pulled bat, nothing I've tried worked... Oh well, I'll just keep testing things.
Sent from my SGH-T989
demoncamber said:
Yeah that does help man thanks. Its the stock tmo twiz ROM, rooted. Yeah I have rebooted, pulled bat, nothing I've tried worked... Oh well, I'll just keep testing things.
Sent from my SGH-T989
Click to expand...
Click to collapse
Which stock ROM there's a couple, I know one that was posted up here that had a few issues, wouldn't let me update anything, kept force closing, and got stuck at splash screen, had to flash diff kernel to boot it, if u want a stock ROM I have a pretty stable deodexed and rooted one I dumped and made flashable, its because the official firmware from Sammy is flawed, so hopefully next update...
Sent from my SGH-T989 using xda premium
I'm literally using the official firmware from samsung that came on this phone from tmo, it was updated when tmo sent me a new one a week ago. Then I just rooted it.
Sent from my SGH-T989
demoncamber said:
I'm literally using the official firmware from samsung that came on this phone from tmo, it was updated when tmo sent me a new one a week ago. Then I just rooted it.
Sent from my SGH-T989
Click to expand...
Click to collapse
Yeah its just the firnware fron sammy, its flawed at its base somewhere n they havent released any fix or anything, try rebooting to revovery and rebooting system from there, then make a data only backup an when and if u get stuck wipe data and restore the backup, fixed it for me, other than that u could try asop, seems to happen less in those roms
Sent from my SGH-T989 using xda premium
So I decided to retry v6 and ultimatic again after a while, and I've narrowed it down to getting stuck at the splash screen whenever doing a super clean and restart or engine flush. Any ideas? It'll boot back up if I backup then restore a nandroid, but there has to be some way around this.
hey guys, I don't really know much about rooting and all that stuff. i rooted it once out of curiousity but quickly went back to the stock firmware and reset the counter. months later (now) I recently started getting all these sim card errors I figured i installed the firmware wrong or something so i tried to redownload the stock firmware and upgrade from there
I launched odin 1.85 installed OUDHS-Recovery-jfltetmo-1.0.3.3 into the phone, ( it passed) and then i installed ROOT_M919UVUAMDL after it rebooted i started getting this
"kernel is not se android enforcing
set warranty bit: kernel"
I can still access cwm touch req0very v1.0.3.3 but I dont know where to go from here, i just want my phone back
Are you still getting sim card errors?
Sent from my SGH-T999 using Tapatalk
lol well it wont go past the galaxy s screen. it stuck there and it gives me the error, also i believe its because the stock rom i got was android 4.2 but it was running 4.3. i dont even care what os runs as long as i get my phone running. i tried going through all the posts in the other threads but I dont understand some of the procedures to get them running. cyanogen mod looks nice and simple
I got it to boot up with a nexus rom, its really different from touch wiz it still gave me the kernel error when i booted it but it ran fine afterwards, i was also checking out the rom and it said that I only have 1.2 gb of ram when ireally have 2 gb. slowly but surely i'm starting to dig this changing of the roms, haha. can anyone hook it up with a link the latest firmware of stock touchwiz? i kinda want to get it running good by the weekend. thanks in advance
There's nothing wrong with the message at boot up, you tripped the Knox counter so that's why you get that message.. You can just flash a stock ROM if you want to go back to touchwiz
Sent from my SGH-M919 using Tapatalk
well, it looks like i'm still getting the sim error message, could it be because its running 4.3 still? how do i get it back to stock and reset the counter so that i can exchange it at tmobile?
It's because you tripped the Knox bootloader. I usually just flash the stock ROM that came with the phone when exchanging.
Sent from my SGH-M919 using XDA Premium 4 mobile app
dfa1979 said:
well, it looks like i'm still getting the sim error message, could it be because its running 4.3 still? how do i get it back to stock and reset the counter so that i can exchange it at tmobile?
Click to expand...
Click to collapse
You cannot reset it.. All you can do is flash the stock 4.3 firmware with Odin if you're thinking about doing an exchange
Sent from my SGH-M919 using Tapatalk
serio22 said:
You cannot reset it.. All you can do is flash the stock 4.3 firmware with Odin if you're thinking about doing an exchange
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
wont they notice though?
Not in my experience. They just have stuff like Knox and the flash counter, so they have the upper hand in a dispute.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
Not in my experience. They just have stuff like Knox and the flash counter, so they have the upper hand in a dispute.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
wish me luck bros lol
dfa1979 said:
wont they notice though?
Click to expand...
Click to collapse
Only if they check, which I don't think they will
Sent from my SGH-M919 using Tapatalk
well, i got the replaced but guess what, it still has the sim card issue, i'm' a 3rd sim card so it seems like these phones are factory defective. looks like I will have to call samsung and try to get it replaced again.