Related
Ok
The first time it showed up (when activating), it offered the OTA update and I declined. Then I took it home, rooted the phone, and everything went well...
BUT I can't find the OTA update anymore... and the SD card bug is killing me!!!!
Is there any other way of installing it?????
From the main screen
Menu - Settings - System Updates
Check all 4 to see if any updates are available but im pretty sure "HTC software update" was the OTA
Actually go over to android central and download rvu 1.1 its based on the newest ruu with that update included and its still rooted
Btw this should be in general section not development
I know, but it keeps telling me that there is no update available!!!
And I am running
Baseband: 1.39.00.04.26
Build: 1.32.651.1 CL171253 test-keys
Software: 1.32.651.1
And it keeps telling me YOUR PHONE IS UP TO DATE
Is there any way to force it????
Settings > System Updates > HTC software update
dchamero said:
I know, but it keeps telling me that there is no update available!!!
And I am running
Baseband: 1.39.00.04.26
Build: 1.32.651.1 CL171253 test-keys
Software: 1.32.651.1
And it keeps telling me YOUR PHONE IS UP TO DATE
Is there any way to force it????
Click to expand...
Click to collapse
I don't recommend updating if you like root
bcnice20 said:
Actually go over to android central and download rvu 1.1 its based on the newest ruu with that update included and its still rooted
Btw this should be in general section not development
Click to expand...
Click to collapse
But, that ruu is missing may of the included apps (all the sprint and HTC ones, and I need them). Also, it wipes all the information....,
So, no other way?
Besides I read that that particular ruu kills the 4g radio...
So, I am the only one or most of you are running without the OTA update?
I like to root, in fact the wifi tethering is working great, but the SD issue is really annoying....
dchamero said:
Ok
The first time it showed up (when activating), it offered the OTA update and I declined. Then I took it home, rooted the phone, and everything went well...
BUT I can't find the OTA update anymore... and the SD card bug is killing me!!!!
Is there any other way of installing it?????
Click to expand...
Click to collapse
i too couldn't get the update to re-show up after not accepting it the first time. i went to system updates and tried both htc and firmware, and the OTA update still wouldn't show. Then i enabled wifi, soft reset, and boom, it showed up. Give it a try, worked for me....
vinscuzzy said:
i too couldn't get the update to re-show up after not accepting it the first time. i went to system updates and tried both htc and firmware, and the OTA update still wouldn't show. Then i enabled wifi, soft reset, and boom, it showed up. Give it a try, worked for me....
Click to expand...
Click to collapse
Well, I had it on wifi all the time, and no luck.... now... when you say "soft reset", how exactly? I just turn it off, and then turn it on again... Is there a soft reset option that I am missing somewhere?
If the root changed your recovery you likely won't get OTA's anymore.
bluehaze said:
If the root changed your recovery you likely won't get OTA's anymore.
Click to expand...
Click to collapse
Ok, that's what I was suspecting...
So.. what are my options now? Is there a way of getting the updates manually? or is there a way of changing the recovery back or modifying some settings to re-allow updates?
I had the same problem after installing one of the custom firmware images. Never could get the OTA to show up. I ended up installing the stock .6 firmware using the RUU.
Look for the "[ROM]RUU_Supersonic_1.32.651.6" thread in EVO 4 Android Development. (sorry, new user account on the forums, it won't let me post links yet).
dchamero said:
Well, I had it on wifi all the time, and no luck.... now... when you say "soft reset", how exactly? I just turn it off, and then turn it on again... Is there a soft reset option that I am missing somewhere?
Click to expand...
Click to collapse
No, you're not missing anything, I meant the same as you, power off, power on.....
I wanna switch so I can get updates from Google, and not Samsung
So what are the cons of switching?
I heard it makes your boot loader locked, what does a locked boot loader mean?
I don't plan on rooting by the way
Sent from my Galaxy Nexus using XDA App
Been there, I am with Bell, had yakjuux and flashed to yakju. No regret, nothing really changed so far.
Your boot loader will stay unlocked, you it wipes your devices completely as a scurity measure. So make sure you do a backup 1st.
Malarie said:
Been there, I am with Bell, had yakjuux and flashed to yakju. No regret, nothing really changed so far.
Your boot loader will stay unlocked, you it wipes your devices completely as a scurity measure. So make sure you do a backup 1st.
Click to expand...
Click to collapse
did you get android 4.0.2?
oh man... im such a noob to these things
can someone in toronto (mississauga / brampton) do this for me?
ill pay you
There is no point to doing this. All ICS builds are ICS. Not everyone on yakju gets their updates faster than people on yakjuux. You will not magically get the 4.0.2 update just by doing this.
joshnichols189 said:
There is no point to doing this. All ICS builds are ICS. Not everyone on yakju gets their updates faster than people on yakjuux. You will not magically get the 4.0.2 update just by doing this.
Click to expand...
Click to collapse
this is exactly what i was thinking right now...
i don't mind if samsung updates my phone instead of google, but the question is
how much longer does samsung take?
i don't wanna wait till the galaxy s2 gets ice cream sandwich
"Androind Updating" after changing to yakju
Using the USB drivers and Firmware from the Samsung Germany website I went from yakjuzs (Hong Kong) to yakju.
After doing this, I powered off my phone, and powered it back on.
After the Google Logo and Animation, I get a message box that says "Android Updating...". after short period of time (under 2s) at the bottom of the screen it says "No Service", then the message box says "starting Applications" under the "Android Updating..." message. The phone then finishes initialization as normal and goes to the home screen.
This made me think that my phone might be trying to upgrade from 4.0.1 to 4.0.2. So I went to the system settings > about phone > system updates and checked for updates. It said my phone was up to date, and the version in the about section is 4.0.1.
Has anyone had this happen to them before? Have any ideas?
This happens every time I shutoff my phone and turn it back on.
subxero123 said:
this is exactly what i was thinking right now...
i don't mind if samsung updates my phone instead of google, but the question is
how much longer does samsung take?
i don't wanna wait till the galaxy s2 gets ice cream sandwich
Click to expand...
Click to collapse
You will not wait that long. It is still AOSP ICS, no matter who builds it. The wait will never be much longer than yakju devices. Hell my friend is on yakju and got the volume fix a week ago so so much for that.
1Speed said:
Using the USB drivers and Firmware from the Samsung Germany website I went from yakjuzs (Hong Kong) to yakju.
After doing this, I powered off my phone, and powered it back on.
After the Google Logo and Animation, I get a message box that says "Android Updating...". after short period of time (under 2s) at the bottom of the screen it says "No Service", then the message box says "starting Applications" under the "Android Updating..." message. The phone then finishes initialization as normal and goes to the home screen.
This made me think that my phone might be trying to upgrade from 4.0.1 to 4.0.2. So I went to the system settings > about phone > system updates and checked for updates. It said my phone was up to date, and the version in the about section is 4.0.1.
Has anyone had this happen to them before? Have any ideas?
This happens every time I shutoff my phone and turn it back on.
Click to expand...
Click to collapse
Android upgrading is not the same as changing to a new version its a feature in ICS that optimizes installed apps and whatnot, completely different things
1Speed said:
Using the USB drivers and Firmware from the Samsung Germany website I went from yakjuzs (Hong Kong) to yakju.
After doing this, I powered off my phone, and powered it back on.
After the Google Logo and Animation, I get a message box that says "Android Updating...". after short period of time (under 2s) at the bottom of the screen it says "No Service", then the message box says "starting Applications" under the "Android Updating..." message. The phone then finishes initialization as normal and goes to the home screen.
This made me think that my phone might be trying to upgrade from 4.0.1 to 4.0.2. So I went to the system settings > about phone > system updates and checked for updates. It said my phone was up to date, and the version in the about section is 4.0.1.
Has anyone had this happen to them before? Have any ideas?
This happens every time I shutoff my phone and turn it back on.
Click to expand...
Click to collapse
This exact thing is happening on my galaxy nexus. I hope someone can help because I am also stuck on 4.0.1
subxero123 said:
I wanna switch so I can get updates from Google, and not Samsung
So what are the cons of switching?
I heard it makes your boot loader locked, what does a locked boot loader mean?
I don't plan on rooting by the way
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
you can follow a guide I've made to switch
http://forum.xda-developers.com/showthread.php?t=1464881
TenPercenter said:
This exact thing is happening on my galaxy nexus. I hope someone can help because I am also stuck on 4.0.1
Click to expand...
Click to collapse
Easy solution: flash a 4.0.3 ROM in ClockworkMod Recovery.
synaesthetic said:
Easy solution: flash a 4.0.3 ROM in ClockworkMod Recovery.
Click to expand...
Click to collapse
thanks I can do that. Do I need to do 4.0.2 first?
TenPercenter said:
thanks I can do that. Do I need to do 4.0.2 first?
Click to expand...
Click to collapse
No - ROM's here are full ROM's. You can flash a top of everything and it will be fine. All you need is unlocked bootloader and clockwork mod recovery installed (check stickies in General/Development subforums)
Only issues i have had after switching is now my battery meter always shows "On Battery" even after charging .. It charges fine, and i can get 100% Charge, infact i find i have better battery life on 4.0.4 Yakju then on 4.0.1 Yakjuux ... Unfortunatly the batter thing is annoying me even though its the only issue i am having.
I have also noticed my benchmarks on the device have fell a little bit. I may find a Yakjuux build and revert back to it. But for now ill test this build for a week and see how it goes.
I'm not sure if anybody will be able to help me. Here is what is going on.
Since I received my phone (Unlocked GSM) the signal was never great. It got progressively worse in the time I've had it to the point where I can't get a signal any longer. Some details that may be helpful:
T-Mobile US
Running version 4.0.1 (ITL41F)
I started with the XXKK1 radio.
I have since unlocked the bootloader, rooted, and tried XXKK6, UGKK7, and UGKL1. None have made a difference.
I think the phone is defective, but I'm hopeful that somebody can find a solution for me. In the event that it is defective do I have any shot of getting a replacement now that I have unlocked the bootloader?
Any help would be greatly appreciated, because as it stands I am the proud owner of a very expensive paper weight.
To get a replaced phone simply... restore your radio back to XXKK1 and fastboot oem lock the phone again. I'd only do this if you can't figure it out. But let's do a few steps to check if everything's okay.
Have you tried resetting the APN? Try putting your SIM card in another T-Mobile phone? Is there service with your same SIM card in that phone? Do you have another SIM card (family member on the same plan or whatever?) try putting their SIM card into your GN and see what happens.
zephiK said:
To get a replaced phone simply... restore your radio back to XXKK1 and fastboot oem lock the phone again.
Have you tried resetting the APN? Try putting your SIM card in another T-Mobile phone? Is there service with your same SIM card in that phone?
Click to expand...
Click to collapse
Good to know. I was under the impression I was screwed with an unlocked bootloader.
I've reset the APN and even tried new ones. I'm currently using my backup phone with the same SIM. No problems, great service.
I knew I left out a couple details... I'm a bit tired at the moment lol.
EDIT: I haven't tried another T-Mo SIM but I have tried an AT&T SIM with no luck :/
roccom33 said:
Good to know. I was under the impression I was screwed with an unlocked bootloader.
I've reset the APN and even tried new ones. I'm currently using my backup phone with the same SIM. No problems, great service.
I knew I left out a couple details... I'm a bit tired at the moment lol.
Click to expand...
Click to collapse
Okay so it's not a SIM card problem. Have you tried doing a factory reset? or even flashing 4.0.2 (using stock Google images)?
http://code.google.com/android/nexus/images.html
zephiK said:
Okay so it's not a SIM card problem. Have you tried doing a factory reset? or even flashing 4.0.2 (using stock Google images)?
Click to expand...
Click to collapse
Negative on the factory restore. The phone was wiped when I unlocked the bootloader so I didn't bother. I haven't tried 4.0.2 yet either. I'll give those two a shot.
roccom33 said:
Negative on the factory restore. The phone was wiped when I unlocked the bootloader so I didn't bother. I haven't tried 4.0.2 yet either. I'll give those two a shot.
Click to expand...
Click to collapse
Try 4.0.2, you can search XDA to find instructions on how to flash it. It's pretty simple. Bootloader mode,
fastboot flash <whatever> <whatever>.img
If all else fails, you won't have to reflash XXKK1, you should just be able to just lock the bootloader and send it back in.
zephiK said:
Try 4.0.2, you can search XDA to find instructions on how to flash it. It's pretty simple. Bootloader mode,
fastboot flash <whatever> <whatever>.img
If all else fails, you won't have to reflash XXKK1, you should just be able to just lock the bootloader and send it back in.
Click to expand...
Click to collapse
I'll definitely give it a shot. Thanks for the advice.
roccom33 said:
I'll definitely give it a shot. Thanks for the advice.
Click to expand...
Click to collapse
You're welcome. Hopefully it's not a hardware defect. Where did you buy your phone from?
EDIT: You are able to get WiFi, Bluetooth from your phone correct?
zephiK said:
You're welcome. Hopefully it's not a hardware defect. Where did you buy your phone from?
EDIT: You are able to get WiFi, Bluetooth from your phone correct?
Click to expand...
Click to collapse
Purchased from Expansys USA. WiFi works fine, have not tried bluetooth.
roccom33 said:
Purchased from Expansys USA. WiFi works fine, have not tried bluetooth.
Click to expand...
Click to collapse
Okay well before you do that fastboot flash business. Try putting WiFi on and going into settings -> about phone -> and manually search for update. OTA for 4.0.2 is back for GN, so you might be able to get it that way... after you update. See what happens, if it doesn't work well, then go into the recovery and factory wipe it and start all over. See if the results change.
And oh okay. Expansys is pretty good, I'm sure they'll replace it in a timely fashion.
Just did a factory restore and received 4.0.2 right away. Attempted to install and got the red exclamation point.
Is this due to having a different radio installed? I'm going to go back to XXKK1 and try again.
roccom33 said:
Just did a factory restore and received 4.0.2 right away. Attempted to install and got the red exclamation point.
Is this due to having a different radio installed? I'm going to go back to XXKK1 and try again.
Click to expand...
Click to collapse
Red exclamation point? can you be more specific? Any errors? text?
zephiK said:
Red exclamation point? can you be more specific?
Click to expand...
Click to collapse
Shows the Android with the opened belly and a red sign with exclamation point... as if to say, "this ain't working."
I pulled the battery and it booted fine but 4.0.2 failed.
roccom33 said:
Shows the Android with the opened belly and a red sign with exclamation point... as if to say, "this ain't working."
I pulled the battery and it booted fine but 4.0.2 failed.
Click to expand...
Click to collapse
Hmmm. You must of done something and it didn't like how your "Android" was set up. Probably because you did a change to it that wasn't stock-like.
Try putting it back to radio XXKK1 and try it again. If it doesn't work, download the stock images of Google and flash it via fastboot.
zephiK said:
Hmmm. You must of done something and it didn't like how your "Android" was set up. Probably because you did a change to it that wasn't stock-like.
Try putting it back to radio XXKK1 and try it again. If it doesn't work, download the stock images of Google and flash it via fastboot.
Click to expand...
Click to collapse
Looks like I'll have to try the stock images. Went back to XXKK1 and still the same problem.
roccom33 said:
Looks like I'll have to try the stock images. Went back to XXKK1 and still the same problem.
Click to expand...
Click to collapse
Bummer. Okay, flash those images... the radio.img one will probably bring it back up to XXKK6 anyway.
Ok I'm going to look into this tomorrow. Just want to relax now. Thanks a bunch for the help.
roccom33 said:
Ok I'm going to look into this tomorrow. Just want to relax now. Thanks a bunch for the help.
Click to expand...
Click to collapse
Glad I could somewhat help. You're more than welcome to PM me if more assistance is required.
I got the update message (41.2) MB.
It is being downloaded and verifies.
I then select to restart & install.
The phone starts booting, but stays on the Google logo for a very long time (more than half an hour).
To try the update again I have to take the battery out, restart the phone (which shows 4.0.2), clear Google Services Framework and check for update.
The updates download etc. etc.
My phone is not rooted and it had no problem in the past updating OTA to 4.0.2
Thanks
So you are trying to update "YAKJUXW" 4.0.2 to 4.0.4?
hmm.. have you flashed any custom kernel or another radio baseband and are you using custom Clockworkmod..?
try to make backup of the 4.0.2 if possible (move to somewhere PC, hardware,..) and then make factory reset and try then update it to 4.0.4
manumanfred said:
So you are trying to update "YAKJUXW" 4.0.2 to 4.0.4?
Click to expand...
Click to collapse
Yes
manumanfred said:
hmm.. have you flashed any custom kernel or another radio baseband and are you using custom Clockworkmod..?
Click to expand...
Click to collapse
No. Nothing like this.
I will try the factory reset if I can't fix it without it.
Thanks
OferR said:
Yes
No. Nothing like this.
I will try the factory reset if I can't fix it without it.
Thanks
Click to expand...
Click to collapse
Okay!
Any resolution?
manumanfred said:
Okay!
Click to expand...
Click to collapse
I've been experiencing same. Bought GalNex from (apparently) Poland before Play store. It is yakjuxw. Past two weeks it's tried to update itself 3 times and just sits at (white) Google on black screen for a very long time.
I actually have to remove battery to recover. Then all is well, but no firmware update and if i follow reddit.com's -> ysk_how_to_get_the_404_ota_quicker to "force" the update, same result.
Did your factory reset solve the problem?
oh4real
No resolution
Sorry, I did nothing so far. I'm still on 4.0.2.
When I get the time, I'm likely to move on to a rooted yakju.
If you do manage to resolve it, please tell us.
Thanks
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
CrfEpic4g said:
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What do you mean by that? Which stock tar?
I think the latest tar we have is still Lj7 but idk. just flash the lj7 tar in odin and update to the latest ill try and find it for you
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 08:50 AM ---------- Previous post was at 08:47 AM ----------
http://www.hotfile.com/dl/161492098/9fa8372/L710VPALEN_L710SPRALEN_SPR.zip.html
Theres a link to lj7 just download that flash it in odin and youll be back to stock. Then all you have to do is update to mb1.
Sent from my SPH-L710 using xda app-developers app
Saturn2888 said:
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Click to expand...
Click to collapse
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
topherk said:
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
Click to expand...
Click to collapse
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
If you dirty flash the rom over whatever you had before, it should not affect any settings
CNexus said:
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
If you dirty flash the rom over whatever you had before, it should not affect any settings
Click to expand...
Click to collapse
MB1 as of now. What do you mean by dirty flash the rom?
edfunkycold said:
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Saturn2888 said:
MB1 as of now. What do you mean by dirty flash the rom?
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Click to expand...
Click to collapse
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
CNexus said:
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
Click to expand...
Click to collapse
Yeah, last time I did that, the system wouldn't boot.