hey guys I'm having some issue changing my phone back to stock, i did some digging around and found some stuff on different models though. I'm on a t-mobile galaxy s3 sgh-t999, i rooted my phone to get WiFi tethering. found out later that the new jellybean firmware blocks it so its pretty much useless now. i unrooted my phone using mobile odin, triangle away to rest count and cwm recovery to do so. wiped cache partition and did a factory reset. the unroot was successful but my phone says modified now instead of normal or original like its supposed to. the stock rom that i flashed takes me back to 4.0.4 ics when it goes to download updates it stops at 4.1.1 after that i get a message saying my phone is modified and updates are not available. all i want is my phone back to normal like i just bought it, I'm thinking about exchanging it and I'm pretty sure they wont take it if the status reads modified. i read this thread about a root66_TMO_T889UVALL4 rom with odin that keeps everything stock and keeps the count at zero thought the whole wipe and boot process. is that something i could use on my phone? any info on how i can fix this is extremely appreciated guys thanks.
Do not flash anything.
Open the battery compartment of your phone, take the battery out, and tell us what the model number says.
Aerowinder said:
Do not flash anything.
Open the battery compartment of your phone, take the battery out, and tell us what the model number says.
Click to expand...
Click to collapse
tmobile SGH-T999
Use the firmware from this page, so you don't brick your phone: http://forum.xda-developers.com/showthread.php?t=1949687
Aerowinder said:
Use the firmware from this page, so you don't brick your phone: http://forum.xda-developers.com/showthread.php?t=1949687
Click to expand...
Click to collapse
one more question, like i said i just unrooted my phone do i have to root it again in order to flash the rom you liked me to?
You don't need to be rooted to flash a ROM.
So, I was given a T-Mobile SGH-T999 that someone had found a while back, but was unable to get activated. It didn't have a SIM in it, and I think it may even have been used off T-Mobile at some point (based on evidence below). Checking the IMEI it seems that it's only blocked on T-Mobile (AT&T says they do not have a block against this IMEI, and it's not showing up in any lost/stolen databases), so I'm guessing non-payment or carrier unlock. I would like to SIM unlock it, but I'm not entirely sure what has been done to this phone. I've never owned or played with a Galaxy S3, so my only knowledge has been from digging around this forum for a couple hours. Here's what I can tell you from looking through this phone. I'm hoping to get some advice on my next course of action:
Model number SGH-T999
Android Version 4.1.2
Baseband version T999UVDMD5
Kernel version 3.0.31-1128078 [email protected] #2 SMP PREEMPT Mon Apr 15 11:59:10 KST
Build number JZO54K.T999UVDMD5
Device Status Modified
Odin Mode
Product name SGH-T999
Custom Binary Download: Yes (1 counts)
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: Enable
I first tried SIM unlock, only to eventually find out that I would need to downgrade from 4.1.2 to 4.1.1. The threads I've read on downgrading indicate that to get back down to official 4.1.1 I need to be stock to begin with. I don't think this phone is rooted because I am unable to "su" when using adb shell or browse directories like /data. However, Odin saying it has a custom binary, and the device status saying modified makes me believe this phone was rooted at some point. Again, I have no experience with the GS3, so I may be way off base (I don't even know if Odin is the stock recovery).
So, before I can downgrade to 4.1.1 do I need to use Triangle Away, reset the flash counter, etc? Or, can I just use Odin to flash 4.1.1. Finally, will I also need to flash a different modem even after that?
I'd appreciate any advice and help you can give me. Thanks.
Thanks for doing some research before posting. Its refreshing to see you picked up basics even if you have never used this model before.
You didn't mention if there's a custom recovery such as TWRP or CWM. If it was there and you were brave or comfortable enough, I'd have suggested a 4.1.1 modem to flash (UVDLJC).
So to your question on unlock, essentially, your best bet is to flash a Root66 of UVDLJC version. Read the first post of Root66 completely word for word before you download and flash. Less chances of hard brick that way. A Root66 is a Galaxy S* family term for rooted stock firmware. It just has root injected in it. Everything else is just stock. So it does not trip the flash counter.
Now your counter is already tripped. So you will have to use Triangle away as you already know. So after Root66 and Triangle Away, you will be all stock and good to go. Follow the process for unlock as you have already found out and then go with ATT.
Now if you wish, after the unlock, you can flash UVDMD5 version of Root66 and you will get JB 4.2.1. Do not flash UVUEMJC version of Root66. Locked bootloader and efuse hardbrick lie in that direction.
Perseus71 said:
Thanks for doing some research before posting. Its refreshing to see you picked up basics even if you have never used this model before.
Click to expand...
Click to collapse
No problem. I work in IT, so I know the frustration of someone asking for help without even trying to do any basic research first
You didn't mention if there's a custom recovery such as TWRP or CWM. If it was there and you were brave or comfortable enough, I'd have suggested a 4.1.1 modem to flash (UVDLJC).
Click to expand...
Click to collapse
Looks like I should have done my research a bit better. I misunderstood, thinking that Odin was some sort of recovery. Just looked up how to get into recovery, and it looks like stock to me (it just reads Android system recovery 3e). So, it is possible to just simply flash LJC modem on 4.1.2 so I can unlock, or am I misunderstanding?
So to your question on unlock, essentially, your best bet is to flash a Root66 of UVDLJC version. Read the first post of Root66 completely word for word before you download and flash. Less chances of hard brick that way. A Root66 is a Galaxy S* family term for rooted stock firmware. It just has root injected in it. Everything else is just stock. So it does not trip the flash counter.
Now your counter is already tripped. So you will have to use Triangle away as you already know. So after Root66 and Triangle Away, you will be all stock and good to go. Follow the process for unlock as you have already found out and then go with ATT.
Click to expand...
Click to collapse
Just to make sure I understand correctly, it IS Triangle away first, then Route66 second? If I'm interpreting correctly, I can do this even if not rooted? All the devices I've ever flashed ROMs to before (even when going back to stock ROM) needed a custom recovery and/or root. But, since this device doesn't appear to be rooted, I just wanted to make sure I don't need to root before flashing Route66.
Now if you wish, after the unlock, you can flash UVDMD5 version of Root66 and you will get JB 4.2.1. Do not flash UVUEMJC version of Root66. Locked bootloader and efuse hardbrick lie in that direction.
Click to expand...
Click to collapse
Thank you so much for the information. Once I get everything in order, and the SIM unlocked, I'll probably spend many hours researching how I want to progress (so you've already helped cut down that time). I honestly haven't come across modem flashing in previous devices, so I will definitely need to read more to fully understand the implications.
Out of curiosity, do you have any theories on how the flash counter was tripped? Everything appears to be stock, but the flash counter and device status seem to indicate otherwise. Just trying to figure out the history of this device. Again, thanks so much for the help.
Really everything Perseus said is on point, except you don't need to use triangle away because really that's just to reset the counter and its unnecessary for you.. You can either flash a custom recovery and flash the LJA or LJC modem to do the unlock, or Odin the LJA or LJC firmware and proceed with the unlock
Edit: and to answer how the counter was tripped, it looks like they may have rooted it at some point and then unrooted it and returned it to stock.. The counter does not change
Sent from my SGH-M919 using Tapatalk
YabosMcGee said:
Looks like I should have done my research a bit better. I misunderstood, thinking that Odin was some sort of recovery. Just looked up how to get into recovery, and it looks like stock to me (it just reads Android system recovery 3e). So, it is possible to just simply flash LJC modem on 4.1.2 so I can unlock, or am I misunderstanding?
Just to make sure I understand correctly, it IS Triangle away first, then Route66 second? If I'm interpreting correctly, I can do this even if not rooted? All the devices I've ever flashed ROMs to before (even when going back to stock ROM) needed a custom recovery and/or root. But, since this device doesn't appear to be rooted, I just wanted to make sure I don't need to root before flashing Route66.
Click to expand...
Click to collapse
Yes that's stock recovery. You can't flash modems with it. If you have custom recovery then the flash counter will keep on tripping at every boot. Best if use ODIN to flash LJA or LJC firmware, do the unlock and then flash MD5 firmware so you are back to JB 4.2.1. Triangle Away's purpose is to reset that flash counter you saw. I do believe it needs Root. I don't remember since I did it so long ago. I just thought you will want to it after all this flashing is done so its all squeaky clean.
YabosMcGee said:
Thank you so much for the information. Once I get everything in order, and the SIM unlocked, I'll probably spend many hours researching how I want to progress (so you've already helped cut down that time). I honestly haven't come across modem flashing in previous devices, so I will definitely need to read more to fully understand the implications.
Click to expand...
Click to collapse
Theoretically with android architecture, it could be done on any device. The trick lies in remounting that partition as read-write correctly. Have fun reading this.
YabosMcGee said:
Out of curiosity, do you have any theories on how the flash counter was tripped? Everything appears to be stock, but the flash counter and device status seem to indicate otherwise. Just trying to figure out the history of this device. Again, thanks so much for the help.
Click to expand...
Click to collapse
Looks like Serio beat me to it. He's spot on where the origins of the tripped counter is concerned.
Thanks Persus77 and serio22. Everything worked out great.
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
GreatGrizzwald said:
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
Click to expand...
Click to collapse
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
http://www.sammobile.com/
absinthesummer said:
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
Thank you very much for the advice. I am downloading the firmware now. baseband version is showing i317ucama4. Right now the phone is not activated with AT&T, is there a way I could test if I will be able to get cellular data before going to AT&T and activating it?
Click to expand...
Click to collapse
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
absinthesummer said:
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Click to expand...
Click to collapse
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
1425
rangercaptain said:
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
Click to expand...
Click to collapse
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
GreatGrizzwald said:
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
Click to expand...
Click to collapse
It sounds like the phone was updated previously to either 4.3 or 4.4.2, which have Knox and that pesky counter. Technically you can't directly downgrade, so be sure you're downloading firmware that is 4.3 or higher. I didn't realize sammobile only went to MA4 for US AT&T. (In a pinch you can use Canadian firmware, but we have other links for stock firmware). Also, don't worry too much about Kies. It can be helpful, but honestly I could never get my note 2 recognized by kies either.
When I get back from taking my kids to school, I'll gather some links that will help you revive this phone Links below:
@GreatGrizzwald:
More recent links to stock firmware: STOCK PACKAGES TO MK6 This is LJ2 (4.1.2), MK6 (4.3) and up. He's got all the stock firmwares, available for flashing either in recovery on via odin. I've highlighted the one I would use in the attached screenshot (MK6- ODIN)
He also has a thread for NE5 (The latest firmware, 4.4.2) HERE
So if MK6 doesn't work, try NE5. One of those two has to work. You're dad already updated to either 4.3 or 4.4.2, I don't know which so start with 4.3 (MK6) and if it doesn't work try 4.4.2 (NE5)
On those two threads, he has a TON of links that will be helpful to you in getting back to stock also.
And here's a reference page with some useful links: One Stop Shop
This one is dedicated to downgrading back to LJ2 (4.1.2) from 4.3+, it MIGHT come in handy for you: Downgrade Instructions
If you have trouble with the stock firmware, you can also try Chainfire's CF Auto Root. It's stock firmware but it's rooted. Try the other firmwares by Zen Arcade first though CF AUTO ROOT
We'll get it going for you The stock firmware will re-flash the modem and all the configuration files so you're data should work again. Then you can do whatever you want, root, recovery, flash other stuff, or leave it stock. You got this
---------- Post added at 07:51 AM ---------- Previous post was at 07:09 AM ----------
GreatGrizzwald said:
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
Click to expand...
Click to collapse
Also you have to figure out if it's software or hardware. I'm inclined to believe it's software so I think if you get it back to stock you'll be good. If it was hardware, it wouldn't even recognize a sim being inserted (recently repaired an htc one mini with this problem, it needed a new Sim tray, thankfully it was only $20).
But it sounds more like a bad flash corrupted some of those important files and configurations controlling data connections, it's all good, if it's software it can definitely be fixed. If it were hardware it could still be fixed it would just be a bit more time consuming.
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Thank you for all this, I will start working with it today. You have been a huge help.
GreatGrizzwald said:
Thank you for all this, I will start working with it today. You have been a huge help.
Click to expand...
Click to collapse
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
1100
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
GreatGrizzwald said:
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
Click to expand...
Click to collapse
That is great news! I'm so glad it's working for you. Enjoy your (new-to-you) note 2 and keep those files on hand in case you need them in the future!
absinthesummer said:
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
Click to expand...
Click to collapse
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
GreatGrizzwald said:
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
Click to expand...
Click to collapse
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
absinthesummer said:
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
Click to expand...
Click to collapse
Awesome, that makes a lot more sense now. Thanks again.
Hey I forgot you don't have custom recovery. Anyway, I sent you PMs,and you can do a search of this very forum- use the search term "update" or "ota" and you will find a LOT of threads on boot failures after OTA. Most people got their phones back.
If you can't get into DL mode (Vol-, Home, Power), try getting into the stock recovery (Vol+, Home, Power) because you should/could be able to factory reset the device from there. Also hold the button combo longer than usual. If one recovery option (DL mode) isn't working, than theoretically the other should still be accessible, through which you can adb sideload to the device or try factory reset. I know it's frustrating, but you're not the first nor the last to have an OTA go wrong ;/ We'll get ya back up & running.
You're not the only one in trouble after that update: http://forum.xda-developers.com/galaxy-note-2-att/help/todays-update-soft-bricked-phone-t2939649
Hey guys long time lurker here who needs some help,
First off, this is what I have on my phone:
Baseband: I747UCUEMJB
ROM: QuantumRom/QuantumKernel (Latest)
Philz Touch Recovery (slightly old)
Main Question: I want to completely wipe my phone (pretty much nuke it) and reset it all the way to where I still have a rooted phone and can put on a custom ROM. How do I go about doing this?
I want to do this because I may sell my phone later on down the road (approx. 2-3 months) and I want to clean out all the stuff I have, but I still want a phone that is rooted and able to sustain custom ROMs. I know this may seem like a noob question, but I want to make sure I do the process right and not lose my phone.
I'm not 100% sure but wiping data, cache, and Dalvik would pretty much wipe everything on your phone.
Alternatively, you could use Odin to flash a ROM.
The thing is, I wanna go back to pretty much stock with root. Like wipe the whole phone clean.
To go back to stock from MJB, you'll need to flash a stock ROM that has been compiled for flashing in Odin. Don't use any of the ROMs from sammobile.com.
This thread may help you out: http://forum.xda-developers.com/showthread.php?t=2722660
Wouldn't it brick my phone?
Wouldn't this brick my device though? I have the MJ2 Bootloader and I never updated OTA to 4.4 Samsung Stock. Reading through those posts gave me the feeling that the method stated would brick my device.
EDIT: Well I just hard-bricked.
UnknownTroll1 said:
Hey guys long time lurker here who needs some help,
First off, this is what I have on my phone:
Baseband: I747UCUEMJB
ROM: QuantumRom/QuantumKernel (Latest)
Philz Touch Recovery (slightly old)
Main Question: I want to completely wipe my phone (pretty much nuke it) and reset it all the way to where I still have a rooted phone and can put on a custom ROM. How do I go about doing this?
I want to do this because I may sell my phone later on down the road (approx. 2-3 months) and I want to clean out all the stuff I have, but I still want a phone that is rooted and able to sustain custom ROMs. I know this may seem like a noob question, but I want to make sure I do the process right and not lose my phone.
Click to expand...
Click to collapse
UnknownTroll1 said:
Wouldn't this brick my device though? I have the MJ2 Bootloader and I never updated OTA to 4.4 Samsung Stock. Reading through those posts gave me the feeling that the method stated would brick my device.
EDIT: Well I just hard-bricked.
Click to expand...
Click to collapse
Which bootloader did you have? The first post said MJB, the second said MJ2.
With the MJ2, I believe you could have flashed back to stock 4.1.1 and just run OTA updates until you hit 4.4.2.
MJ2 is the leaked bootloader: http://forum.xda-developers.com/showthread.php?t=2498233