I am considering buying an otterbox and I got to thinking how big a pita it may be to remove the sim and sd card each time I flash. So my question is what does it cause if you leave the SIM in and SD in and flash a new ROM? Whatever problems people say it cause, has anyone experienced the problem themselves?
Some things are just 1 in a million or old stuff that doesnt impact things now so I am trying to figure out the difference.
Thanks!
I do it as rule of thumb. Today I did not. Have not had an issue yet
Sent from my SGH-I897 using XDA App
I've never removed my sim, and never had a problem.....
I am a firm believer that if you are having problems with a ROM delete everything possible and remove the SIM and SD. though I have installed the last few ROMs with both in without any real problems.
i would be interested in finding out why its suggested...
Never removed anything before unless I soft bricked it.
Sent from my SAMSUNG-SGH-I897 using XDA App
I never remove the SIM while flashing. Don't generally remove the external SD card either. I didn't even remove them when recovering from a soft brick. If it's a concern of possibly losing data you can always back it up when you mount them to use on your computer.
To answer your ultimate question you really don't need to be removing the Captivate from your Otterbox.
avgjoegeek said:
Never removed anything before unless I soft bricked it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I've never removed it. Don't see why we would need to to be honest
I've never removed mine, never had trouble. I think it might be one of those "do it if it makes you feel better" sort of things.
I flashed once with the SIM to Cog6 about 5 weeks ago and lost my baseband version. Meaning, I couldn't make calls.
Reflashed to 1 click then back to Cog W/O SIM and I calls worked again
avs420 said:
I flashed once with the SIM to Cog6 about 5 weeks ago and lost my baseband version. Meaning, I couldn't make calls.
Reflashed to 1 click then back to Cog W/O SIM and I calls worked again
Click to expand...
Click to collapse
So reflashing can actually clear SIM settings? Yikes.
plasticdarlow said:
I've never removed my sim, and never had a problem.....
Click to expand...
Click to collapse
neither have i and i have flashed probably 30 times or more and never had a single issue.
I think I took the SIM out like once. And I've done hundreds of ROM flashes.
Only time you would need to take out your SIM is if your phone is soft-bricked so bad you end up having to do the whole take out everything to get it back into DOWNLOAD mode.
Otherwise - I've flashed probably about as much as Mikey (sad for not being a developer/chef) and never had an issue.
Related
Bad Kernel? Bad Radio? What?
I've used quite a few different ROMs. (Enom, Kang [CM], MIUI, and most recently, Rodriguezstyle's miui.)
But, the problem keeps happening, despite wiping between each ROM.
is it the radio? or the kernel? I think it might be, but I'm fairly certain I have the right kernel...and I upgraded my radio when I went to Froyo...
Gah.
I dunno about the kernel, but from what I've heard, if you have the wrong radio your n1 will be bricked. So I guess it's not the radio.
It's not a problem, I've been living with it. It's just rather annoying...
Maybe it's an app I have installed? Or things aren't...done right? Augh idk.
Change the Kernel and that will fix it, pershoot's worked the best for me.
Do you have to pull the battery when it reboots?
cmarti said:
Change the Kernel and that will fix it, pershoot's worked the best for me.
Click to expand...
Click to collapse
I've changed it to many kernels. Right now i'm using this one:
2.6.35.4-950mV-BFS-SVS-AIX-720p-Monks-082710
rickytenzer said:
Do you have to pull the battery when it reboots?
Click to expand...
Click to collapse
No. I will be chilling on the phone, and then I will randomly see the boot image.
if your nexus is still less than a year old, get a new replacement device
watch the logcat output (adb logcat), and also kernel messages http://bootloader.wikidot.com/linux:android:kmsg
khanh1289 said:
if your nexus is still less than a year old, get a new replacement device
Click to expand...
Click to collapse
I don't have insurance, I don't think...idk. I bought it outright from the google store...what would I have to do? Also, its unlocked, obviously...
hollywooder said:
I don't have insurance, I don't think...idk. I bought it outright from the google store...what would I have to do? Also, its unlocked, obviously...
Click to expand...
Click to collapse
Are you overclocked?
SiNJiN76 said:
Are you overclocked?
Click to expand...
Click to collapse
Not that I'm aware of. I don't even have setcpu installed anymore.
So unless the roms themselves overclock, then no. I upgraded my
kernel, but it has done a random shut off once since then. But it's
not that often. Not as often as it was at least.
Do you have more than one battery to try? My phone locked up or randomly rebooted several times a day when I was using Cyanogen 6rc1, but it only did it with one battery and ran fine with the other. The problem went away after I updated CM though.
My theory is that my "bad" battery is damaged slightly enough that it conflicted with something particular in that rom (also happened with 3-4 different kernels). I don't know anything about batteries, but if that's accurate, I don't see why a battery couldn't be damaged enough to conflict with all roms.
It doesn't sound like your problem exactly, but might be one of the simpler things to try, especially if you have a spare or could borrow one or something.
Try to extract the SD-card and Power ON the phone without it. If the phone works
well in that condition, problem solved.
Something like this happens to me one time, all I do was to format the entire SD-card
in my iMac with the Disk Utility, filling all the space with zeros (0) for be sure all the
data was erased correctly. Then I make the partitions again, flash a ROM and all
is fine now.
Good luck!
I had the same problem. Phone would reboot during many tasks. This would happen with any ROM even stock. I sent the phone to htc and they changed the motherboard under warranty. I noticed it first started to happen with robo defense and then other apps such as YouTube or browsing the net. I wasn't able to use the phone while it was charging or it would reboot.
wsrider said:
I had the same problem. Phone would reboot during many tasks. This would happen with any ROM even stock. I sent the phone to htc and they changed the motherboard under warranty. I noticed it first started to happen with robo defense and then other apps such as YouTube or browsing the net. I wasn't able to use the phone while it was charging or it would reboot.
Click to expand...
Click to collapse
My phone isn't that bad, and no luck with the sd card thing.
hollywooder said:
My phone isn't that bad, and no luck with the sd card thing.
Click to expand...
Click to collapse
I bought my nexus one in may. It got worse over time and i had it repaired in september
If you buy it off from google store, it comes with a 1 year manufacture warranty, call HTC and get a replacement device
khanh1289 said:
If you buy it off from google store, it comes with a 1 year manufacture warranty, call HTC and get a replacement device
Click to expand...
Click to collapse
I don't believe I ever filled out the warranty, can I still get it replaced?
Sorry for the double post, but I'm really curious...about the warranty thing.
sergioalvarezmac said:
Try to extract the SD-card and Power ON the phone without it. If the phone works
well in that condition, problem solved.
Something like this happens to me one time, all I do was to format the entire SD-card
in my iMac with the Disk Utility, filling all the space with zeros (0) for be sure all the
data was erased correctly. Then I make the partitions again, flash a ROM and all
is fine now.
Good luck!
Click to expand...
Click to collapse
This is my suggestion as well. A friend of mine had this problem. There was a corrupt video on his sd card that caused the entire issue.
Has this happen to anyone ? I think there will be a lot more cases of this as the Internal SD is written to.
sherazshahid1 said:
Has this happen to anyone ? I think there will be a lot more cases of this as the Internal SD is written to.
Click to expand...
Click to collapse
Why would the internal sd be written to ?
And no, i upgraded last evening and nothing has happened (knock on wood)
Yea this just happened to me...argh
miniflight said:
Yea this just happened to me...argh
Click to expand...
Click to collapse
No way.
Please tell me you're lying....I avoided all 2.2 roms because if my phone dies, I'll die.
or else, PLEASE tell me you had some lagfixes or other stuff installed!
I'm running completely stock on Rogers, and just upgraded via Kies, no registry hack, about 30 minutes ago. LOVING Froyo!!
deezy7 said:
No way.
Please tell me you're lying....I avoided all 2.2 roms because if my phone dies, I'll die.
or else, PLEASE tell me you had some lagfixes or other stuff installed!
I'm running completely stock on Rogers, and just upgraded via Kies, no registry hack, about 30 minutes ago. LOVING Froyo!!
Click to expand...
Click to collapse
Well man its only the Bell version have most problem. Rogers should be fine. i9000m is famous for internal sd explosions...
o wellz, good thing nexus s is right on the corner, tho i hate it but guess hv to change a new phone if bell won't take my phone for repair
and yea, i hv everything stock too
I'll probably get a Nexus S as well if they bring a 850 3G model
too bad it lacks the microSD
happened to my bell vibrant lol
here's my thread about it
http://forum.xda-developers.com/showthread.php?t=866838
miniflight said:
Well man its only the Bell version have most problem. Rogers should be fine. i9000m is famous for internal sd explosions...
o wellz, good thing nexus s is right on the corner, tho i hate it but guess hv to change a new phone if bell won't take my phone for repair
and yea, i hv everything stock too
Click to expand...
Click to collapse
omg nooo!
crunked said:
happened to my bell vibrant lol
here's my thread about it
http://forum.xda-developers.com/showthread.php?t=866838
Click to expand...
Click to collapse
just read it, and OMG NOOOOOOOOOOOOOOooooooooooooo!!!
I'm not using the Captivate, I'm using the Bell Vibrant, unlocked on Rogers. So I can't go to Bell to get it fixed (can I?!) if it happens! And, I'm not like, super rich, so I can't just drop $$$ on the Nexus S as much as I want to (besides, no microSD!! wtf?!?!)
I've been following all the threads about people's I9000M's dying after installing 2.2 roms, so I've avoided all of them as well as all lagfixes, etc. I just ASSUMED that a 2.2 update from Bell would be absolutely safe, since ROMS are hacked together by people who don't get paid to work with the code, while the people that get paid to work with the code (i.e. Bell employees) should be able to just put this together absolutely correctly.
This damn troublesome internal SD card!! ****!!! Should I just sell my phone now and get something else...or what...?...
And is it possible to roll back to 2.1 via Kies?
deezy7 said:
omg nooo!
just read it, and OMG NOOOOOOOOOOOOOOooooooooooooo!!!
I'm not using the Captivate, I'm using the Bell Vibrant, unlocked on Rogers. So I can't go to Bell to get it fixed (can I?!) if it happens! And, I'm not like, super rich, so I can't just drop $$$ on the Nexus S as much as I want to (besides, no microSD!! wtf?!?!)
I've been following all the threads about people's I9000M's dying after installing 2.2 roms, so I've avoided all of them as well as all lagfixes, etc. I just ASSUMED that a 2.2 update from Bell would be absolutely safe, since ROMS are hacked together by people who don't get paid to work with the code, while the people that get paid to work with the code (i.e. Bell employees) should be able to just put this together absolutely correctly.
This damn troublesome internal SD card!! ****!!! Should I just sell my phone now and get something else...or what...?...
And is it possible to roll back to 2.1 via Kies?
Click to expand...
Click to collapse
Well once the internal sd card exploded, you can't even open the phone so they probably can't find out if your phone is unlocked. You just need to like ask a friend or a family member that uses Bell to go with you and take the phone over to a Bell store and see if they will repair it. Dont tell them you unlocked it lol. Just let say that your friend or a family member that upgraded the phone and the internal sd exploded etc
I don't think it really matters how you flash it, or even if you don't flash it at all. I've seen people with bad sd cards on stock 2.1, flash with odin, flash with cwm, flash with kies. Mine went bad just last week. It was running docs rom flashed on jh2 with recovery. Fortunately, the Bell store I took it to took it in for repairs even though I'm on Rogers.
There's clearly a hardware problem. Maybe it's the MoviNand. If that were the case, maybe that's why the Nexus S is using an iNAND instead of the MoviNand.
BTW, this is the 2nd i9000M I had this problem with.
Yea good thing mine died last week, got ahead of everyone else updating through Kies , hopfully I wont have to wait to long to get my phone back. I feel naked without it
deezy7 said:
omg nooo!
just read it, and OMG NOOOOOOOOOOOOOOooooooooooooo!!!
I'm not using the Captivate, I'm using the Bell Vibrant, unlocked on Rogers. So I can't go to Bell to get it fixed (can I?!) if it happens! And, I'm not like, super rich, so I can't just drop $$$ on the Nexus S as much as I want to (besides, no microSD!! wtf?!?!)
I've been following all the threads about people's I9000M's dying after installing 2.2 roms, so I've avoided all of them as well as all lagfixes, etc. I just ASSUMED that a 2.2 update from Bell would be absolutely safe, since ROMS are hacked together by people who don't get paid to work with the code, while the people that get paid to work with the code (i.e. Bell employees) should be able to just put this together absolutely correctly.
This damn troublesome internal SD card!! ****!!! Should I just sell my phone now and get something else...or what...?...
And is it possible to roll back to 2.1 via Kies?
Click to expand...
Click to collapse
I had mine unocked on Fido and the internal sd problem occurred. I took it into the bell store. They charged me $35 for a repair quotation fee (incase it was water damaged).
It came back 2 weeks later...well a completely new phone came back 2 weeks later and they refunded my $35 since it was a warranty issue. My phone was rooted and had 2.2 but that didn't matter to them.
Man I feel bad for you guys !
Don't know what to say.
I've been very fortunate (knock on wood) to have not had any SD issues with my phone.
Had since release day and flashed at least a half dozen times with odin.
Just sent my phone in today for repair. I flashed a custom firmware I created with a lagfix enabled (stupid move, I know) which caused my phone to boot-loop. I had access to download mode, though, which allowed me to flash stock UGJH2 so I wasn't running a custom firmware when they looked at it.
danyul said:
I had mine unocked on Fido and the internal sd problem occurred. I took it into the bell store. They charged me $35 for a repair quotation fee (incase it was water damaged).
It came back 2 weeks later...well a completely new phone came back 2 weeks later and they refunded my $35 since it was a warranty issue. My phone was rooted and had 2.2 but that didn't matter to them.
Click to expand...
Click to collapse
you got a new one in return? are the new ones network unlockable? i thought they remedied that? im also on rogers using a network unlocked bell vibrant and im very scared of bricking because i may get a phone back that i cant unlock.
btw i upgraded to 2.2 without issue.
evil-doer said:
you got a new one in return? are the new ones network unlockable? i thought they remedied that? im also on rogers using a network unlocked bell vibrant and im very scared of bricking because i may get a phone back that i cant unlock.
btw i upgraded to 2.2 without issue.
Click to expand...
Click to collapse
Yeah, I was able to unlock it fine with the code generated by the SGS Unlocker that is in the market.
Yup... just upgraded with Kies an hour ago. Seemed OK and then just died. Now running an endless loop with logo and black screen. Can not get into recovery mode with 3 btn rec. Arrrgh. Going to Bell tomorrow.
I had a very similar problem where it ended saying "internal SD card damaged". HOWEVER I did not have to send it in to repair (yet!).
I recovered holding down "home+power+volume UP" (as opposed to DOWN). This gives you a bios menu that you can reformat internal SD, cache and factory reset. Do this and hopefully it will boot up again. To be safe, do another Factory Reset from within the OS and reformat the internal SD again.
After I did this, it is up and running good so far. Currently re-configuring from scratch again...
It died after JK4
OMG!
WOW! here's an irony...
phone was originally JG9, went to JH2 no problem, updated from JH2 to JH2+SPL fix no problem, when from JH2 SPL fix to JK3 no problem....
now after upgrading from JK3 to official JK4 toasted, during when i was restoring all the stuff back from Titanium Backup
it got stuck several times, rebooted the phone a few times, now it's totally black screen, and with the soft key lid, but doing nothing
I can go into both Recovery and or Download modes
I can flash back to any version of ROM i want, but always get the dreadful message /dev/block/mmcblk0p1
.... sigh... time to dig out the invoice and go to the store for repair
And as if on cue, there it goes. Unlocked phone, one of my widgets was screwed up, then black screen. Reboot, black screen. And of course today is the day I finally root it, but if it can't start they can't tell so ha
I am not willing to submit to dead SD yet though. This phone has been working since August 6th. I'll try wiping everything that can be wiped in recovery mode.
Edit: Nope, it's completely dead. I have the smartphone protection plan though, so I can "lose" this phone and get a brand new one for $150. Although preferably they give me a replacement then and there or a Desire Z. I do not want to leave the store tomorrow without a permanent replacement.
I honestly hate removing my case every time to flash a ROM. I don't have an SD card installed, but I was wondering if it was OK to flash a ROM with the SIM installed?
If not, what's the reason for removing it? Thanks a lot in advance!
Perfectly fine to do so
Sent from my HTC Vision
Pirateghost said:
Perfectly fine to do so
Sent from my HTC Vision
Click to expand...
Click to collapse
Just curious, how come in all of the flashing tut's I've watched, they tell you to take it out?
I'm not doubting what you say, I'm honestly just curious.
It won't affect the ROM flash to leave it in. Every flash I've done was with the SIM installed. Some people say that if you get a call during the flash it could mess it up, but until the OS is loaded a call will not go through.
I've done it a couple times and it didn't hurt anything. I usually by habit remove sim and sd because I've seen it so many times and have been a stickler for following the directions as much a possible.
Sent from my GT-I9000 using XDA App
from everything i have read its just a layover from older phones where flashing with the sim would screw the modem (eg my friend messed up his x10 and had to get a new sim becase he flashed a modem with the sim in) so its just an extra precaution in case something like that happened and its a good habit to get into especially if you are working on different phones
I never take out my sim when I flash and it has never done any harm to me.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Hey guys. Four days ago I bought a brand new LG Optimus Optimus 2X. Everything seemed to be good, but after a couple of hours the phone asked for pin code. I entered it and I didn't think much about it until I noticed that I didn't receive any calls or text messages. Tried to call out/send text messages but it didn't work.
I rebooted phone and things worked as usual again. This occurs about 6 times a day, and reboot is the only way to fix it. I went back to the store and told them about the problem. They gave me a new LGP990, but the same problem happen with the new phone I got. I didn't install any applications, and I even did a factory restore with the same result.
I thought it could be the batch the store got, but they had sold several other phones of the same batch and no problems was reported by the customers. Could it be my google account/a contact or something corrupting the OS?
connubialis said:
Hey guys. Four days ago I bought a brand new LG Optimus Optimus 2X. Everything seemed to be good, but after a couple of hours the phone asked for pin code. I entered it and I didn't think much about it until I noticed that I didn't receive any calls or text messages. Tried to call out/send text messages but it didn't work.
I rebooted phone and things worked as usual again. This occurs about 6 times a day, and reboot is the only way to fix it. I went back to the store and told them about the problem. They gave me a new LGP990, but the same problem happen with the new phone I got. I didn't install any applications, and I even did a factory restore with the same result.
I thought it could be the batch the store got, but they had sold several other phones of the same batch and no problems was reported by the customers. Could it be my google account/a contact or something corrupting the OS?
Click to expand...
Click to collapse
Don't think so. contact your service provider and suggest that you would like to replace the SIM card. It might help if new device didnt...
They should be able to send you a new SIM and activate your services on it for free.
SimDroid said:
Don't think so. contact your service provider and suggest that you would like to replace the SIM card. It might help if new device didnt...
They should be able to send you a new SIM and activate your services on it for free.
Click to expand...
Click to collapse
It's a reasonable explenation, but I find it a little strange, since the SIM card is about 2 weeks old, and it works completely fine in a different phone, but hey. I'll try out with another SIM card.
Your problema is another variant of random reboots. Welcome to the club ;-)
I've it too more or less.
Regards!
Me too
Sent from my LG-P990 using XDA App
Kept asking me to. I jumped over to another baseband, the 502. Helped a lot
Sent from my LG-P990 using Tapatalk
Same here ...
Sent from my LG-P990 using XDA App
Sckank said:
Kept asking me to. I jumped over to another baseband, the 502. Helped a lot
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
Does that mean your phone is cured, or just almost? Anyways. Do you have a good walkthrough/tutorial about how to upgrade baseband to 502?
I used the guide at madaco. Well it havent had it asking for pin-code with the madaco 18b2 and cm7 is also stable, or so they say
Sent from my LG-P990 using Tapatalk
connubialis said:
Do you have a good walkthrough/tutorial about how to upgrade baseband to 502?
Click to expand...
Click to collapse
Dead easy: http://android.modaco.com/content/l...lash-stock-baseband-release-1035-21-20110502/
Hm. I think I might wait for an update. I'm a little afraid that I'm gonna **** it up. Don't want my phone bricked, and I'm a newbie to android-flashing.
I flashed to cyanogenmod 7 and the pin prompt have still not appeared. I will get back to you in a couple of days when I've tested it more.
Edit: I was wrong. Problem still occurs on c7.
Edit2: I think it might have gotten a little better. It happens maybe 2-3 times per day now. So it might have helped.
Edit3: Flashed baseband to 1035.21_20110502. Exited to see how this works.
Edit4: Got a pin prompt 5 hours after flashing baseband. Waiting for an update from LG or clever answer then.
I made a new discovery. This seems to appear when I have bad reception. When I have no reception this happens ALL the time. Like several times per minute. So I really don't know what to do now.
After installing xposed on my S5, I kept losing service. Sometimes wouldn't even realize for a while (had my daughter call me on my work phone asking what's up with my phone)
Just wondering if anyone else had this problem or if it was caused by a specific module I used?? I had most of the Galaxy ones installed as well as the Framework (only mod that worked was to add custom text to my notification bar)
No signal issues here. I'm using wanam, app settings, gravity box (to swap recents/menu), greenify, isis root bypass and g touchwiz.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Same issue here on xperia Z1, android 4.4.4. Installed Xposed, activate framework and reboot -> signal loss. Restoring ROM, ejecting and then inserting SIM card did not help
It's not xposed... I went back to stock unrooted and the problem still existed. Called AT&T and they had me go to get a new SIM card... it's doing it still today GRRRRR I've gotta get rid of my custom boot image (flashing android) and Dr. Who sound byte on boot then I'm calling them back and getting a warranty replacement. I'm honestly severely dissatisfied with this phone. When it's time for an upgrade I will NOT be purchasing another Samsung device.
rachelm920 said:
It's not xposed... I went back to stock unrooted and the problem still existed. Called AT&T and they had me go to get a new SIM card... it's doing it still today GRRRRR I've gotta get rid of my custom boot image (flashing android) and Dr. Who sound byte on boot then I'm calling them back and getting a warranty replacement. I'm honestly severely dissatisfied with this phone. When it's time for an upgrade I will NOT be purchasing another Samsung device.
Click to expand...
Click to collapse
I would just flash back to stock & see if it comes back. If that doesn't work, the radio may have just coincidentally gone bad in the middle of modding. I see a lot of S5's & no problems with signal so I wouldn't give up on Samsung yet if this is your only issue.
BTW if you go into your settings, about device, status screen, does your imei still show up?
zoso28 said:
I would just flash back to stock & see if it comes back. If that doesn't work, the radio may have just coincidentally gone bad in the middle of modding. I see a lot of S5's & no problems with signal so I wouldn't give up on Samsung yet if this is your only issue.
BTW if you go into your settings, about device, status screen, does your imei still show up?
Click to expand...
Click to collapse
That's not the only issue...I'm upset about the bootloader being locked and the charging port flap no longer stays shut.
My IMEI is still there it only works on WiFi now AT&T is sending me a warranty replacement in 4 business days I'm about to use my BF's old S4 in the meantime
rachelm920 said:
That's not the only issue...I'm upset about the bootloader being locked and the charging port flap no longer stays shut.
My IMEI is still there it only works on WiFi now AT&T is sending me a warranty replacement in 4 business days I'm about to use my BF's old S4 in the meantime
Click to expand...
Click to collapse
I feel you on the bootloader issue.. everyone here does lol. I haven't seen the flap problem but you're definitely not having the best luck with the S5. Hopefully it's a fluke but make sure you're completely stock when you send the old one back b/c if they find any evidence that you voided the warranty (flashing, rooting, etc) they don't notify you, they just bill your account $400 and keep the phone.
rachelm920 said:
That's not the only issue...I'm upset about the bootloader being locked and the charging port flap no longer stays shut.
My IMEI is still there it only works on WiFi now AT&T is sending me a warranty replacement in 4 business days I'm about to use my BF's old S4 in the meantime
Click to expand...
Click to collapse
Mad about the bootloader? check this out.
https://www.change.org/petitions/att-give-us-the-freedom-to-modify-and-build-unlock-our-bootloaders
Need signatures please.
Sent from my SAMSUNG-SM-G870A using XDA Premium 4 mobile app
zoso28 said:
I feel you on the bootloader issue.. everyone here does lol. I haven't seen the flap problem but you're definitely not having the best luck with the S5. Hopefully it's a fluke but make sure you're completely stock when you send the old one back b/c if they find any evidence that you voided the warranty (flashing, rooting, etc) they don't notify you, they just bill your account $400 and keep the phone.
Click to expand...
Click to collapse
Oh yeah I odin'd it yesterday, it's back to stock completely. Didn't even install an app on it since it has no signal LOL. I'm using my BF's old S4 and running 4.4.4 AOSP ROM right now... I don't know if I'll want to go back to my S5 when it comes in... Oh how I missed AOSP
GDofWR420 said:
Mad about the bootloader? check this out.
https://www.change.org/petitions/att-give-us-the-freedom-to-modify-and-build-unlock-our-bootloaders
Need signatures please.
Sent from my SAMSUNG-SM-G870A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I signed... would share to my FB but none of my friends would know what I'm talking about LOL
rachelm920 said:
That's not the only issue...I'm upset about the bootloader being locked and the charging port flap no longer stays shut.
My IMEI is still there it only works on WiFi now AT&T is sending me a warranty replacement in 4 business days I'm about to use my BF's old S4 in the meantime
Click to expand...
Click to collapse
Did you try one of the USSD codes for a Hard reset on your old S5 (*2767*3855#)? Sometimes they fix a little bit more than a normal factory reset.
rachelm920 said:
I signed... would share to my FB but none of my friends would know what I'm talking about LOL
Click to expand...
Click to collapse
I thank you. Yea I'm finding it hard to get signitures as I don't have a Facebook or Twitter account, just don't want my info allover the net. So if you would help spread the word amongst the developing community that would help, this applies to anyone who cares about what we do here. Again I thank you for your support.
The Gods Approve This Post, From The Ghost Of Sparta's S5 active.