Related
I need to return my S3 as I've received my new one via insurance from ATT. The internal LCD is cracked and does not work - pitch black. So, I'm guessing it is best to flash it back to stock from KyanROM. Now I have a few questions:
Do I need to flash to stock for insurance purposes? I believe I found a youtube video that shows how to do a hard reset of data to wipe it clean (that way I know how many times to scroll). Should I do that before I flash to stock, or after?
I looked at this thread - http://forum.xda-developers.com/showthread.php?p=33570269#post33570269 - and there are a few ATT stock roms. Which do I need, does it matter?
Since I am unable to see my display, would like to flash without tripping counter. Which is the preferred way to flash back to stock and keep counter at 0?
Let's start simple then.
Should I flash back to stock if returning phone for insurance (not warranty)?
Tough crowd! Whew! Haha..ok, well, I guess I'm going to give flashing to stock a go. Could someone help point me in the right direction as far as which ROM I need. I'll beg a lil too - PLEASE!
Follow this tutorial, you shouldn't need to worry about scrolling:
http://forum.xda-developers.com/showthread.php?t=1984717
OK, that looks like it'll restore factory settings. That'll work after I flash stock ROM. Can someone point out the proper ROM I should use?
You don't have to, read the entire thread. Kies downloads and installs the latest stock rom for your device, it detects from model and serial number.
You just have to plug it, follow the instructions and wait until it boots up stock unmodified.
vladeco said:
You don't have to, read the entire thread. Kies downloads and installs the latest stock rom for your device, it detects from model and serial number.
You just have to plug it, follow the instructions and wait until it boots up stock unmodified.
Click to expand...
Click to collapse
I'll be honest, I only read the first post. I'll read through the rest. In the meantime, in case it doesn't mention this, do you know about flash counter? Mine currently is not tripped - does this keep the counter as unmodified? Also, last I remember Kies did not recognize my phone after I put custom ROM on there (kyanROM), so will that matter if trying to do it via Kies?
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.
Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
ive tried odin and try reflashing back to stock but odin failed
ImJusDatGuy said:
Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
Click to expand...
Click to collapse
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
ImJusDatGuy said:
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
Click to expand...
Click to collapse
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
dawgdoc said:
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
Click to expand...
Click to collapse
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
ImJusDatGuy said:
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
Click to expand...
Click to collapse
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
dawgdoc said:
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
Click to expand...
Click to collapse
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
ImJusDatGuy said:
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
Click to expand...
Click to collapse
thanks man for telling me what was wrong your an amazing human being and i love you (no homo) and thanks again a million thanks bro.
Did that modem fix some of the problems?
If your on 4.1.1 shouldn't you flash the DKL3 version or can't you just flash thru Odin the DLK3 stock ROM thru Odin Amd start all over again
I've been on 4.3 with that bootloader Amd have flashed back to 4.1 back to the baseband version DLK3 firmware. I would think being on 4.1 you should be able to reflash using Odin to fix the issue or flash the modem for 4.1 .
I'm really frustrated. I've been trying to update this Galaxy S3 for days now with no success. Currently I am running on Slimkat 7.0. It's sometimes slow and buggy and needs some updating.
For reference, this is the phone at its current state:
- Bootloader: i747ucalh9 (literally taken from the fail message when trying to update to any other bootloader)
- Modem/firmware (?): I747UCLH9
Here's what has happened, greatly summarized (note I'm using CM6.0.4.7 for all of these operations, and when I say "update", I mean "flash"):
- I tried updating to Slimkat 9 but received no signal. I gave up on it entirely for a while
- I tried installing various LP ROMs, including CM12.1.
- I had 12.1 running for a bit, but I had no connectivity. LTE, 3G,H+ nothing.
- I tried installing a newer modem (this thread. Finally at MJB, I could actually get connectivity in some of the newer ROMs (including Slimkat 9)... but it was very erratic. It would just randomly oscillate between LTE and 3G and H+. This also broke CM12.1 entirely.
- Again, the above problem was always present. Most of the LP ROMs would just bootloop me, though. The only one that worked was Cyanide L... which I didn't really like.
- I thought maybe the issue was the bootloader. My bootloader is still i747ucalh9. So I tried updating it to various bootloaders from here, but none of the updates will work. Literally, they give me error 6 or 7 and pretty much essentially tell me that I can't do it.
- So after repeating the cycle of "let me try to update this" several times and having the update fail on me, I'm still stuck at Slimkat 7 as the only thing that worked on LTE (note the past tense). Worse yet, I tried simply downgrading my modem to match my current bootloader version, but that made things worse than better. I am now stuck at 3G... which just recently went back to LTE. Talk about erratic.
- I also tried going full stock by flashing this: http://forum.xda-developers.com/showthread.php?t=2363882 But it expects 5 arguments for format, and got 3... or something. Failed hard.
So, I'm pretty much at the end of my rope here. I really might just go and grab a new phone at this point. I just really don't want to because this thing still works fine.... I guess I got unlucky and am at a version of the bootloader that is difficult to update from. I can't seem to go anywhere with this thing. Anyone have any ideas? Do I need to use a different recovery?
Thanks...
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
jason2678 said:
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help! I actually did/tried a majority of this an hour or two before you posted that, except the latest firmware update link you supplied. I knew it existed and I had seen that thread before, but I couldn't dig up the link again before I had to go to work. Thing is I kind of wanted to avoid Odin for some reason but I finally gave up and used it. And yeah I already knew my bootloader version. The phone told me when it failed to update the bootloader lol.
Here's what happened thus far:
- I used Odin to flash the sammobile 4.1.1. The flashing worked just fine, but booting into it did not. It hung on the Samsung logo. So, OTA updates were out the window.
- I have no idea why, so I just used Odin to flash TWRP onto it afterwards (from here)
- I tried one of the ROMS. Data still didn't work.
- I used the thread you linked to update to MJB bootloader and whatnot. The update went fine.
- Tried another few ROMs. Data worked, but LTE was still erratic.
- Updated to NE4 and then grabbed the deoxed stock ROM.
- The deoxed stock rom failed to boot (stuck at ATT globe logo). For some reason my phone can't use stock ROMs.
- So again used Odin to put TWRP onto the phone
- Installed various LP ROMS. Again the data was erratic and plus the battery life was horrid.
- Tried getting the ktoonsez kernel. My service was murdered.
- Gave up on LP. Tried Slim 9.0. Erratic data.
- Tried Liquidsmooth 4.4.4 instead.
Currently that's kind of where I'm at. The LTE data works fine (takes a bit to get up and running after reboot though) and thus far everything is okay (though that can quickly change considering I haven't done much of anything), so I don't even know if I want to mess with it anymore. It looks like this specific ROM includes a custom kernel. So I'm guessing it's an incompatibility between the kernel and the firmware version on the other ROMs. It seems like most of the LP roms have horrible battery life (back of my phone feels like a furnace on them), so I'm not even sure if I want to do that last firmware update to use them.
It'd be kind of nice to use the OTA but apparently my ability to go stock in any form or fashion is just totally borked.
Thanks for the post though, that's pretty gold. I'm sure someone in a situation like me where they have a super old firmware will find this thread of some use as it has actual instructions and links to what you need to do to get up and running. Before you posted that, I had to go digging around pretty much everywhere figuring out what and where was going wrong.
Glad you've got it mostly working.
You might have been able to get that stock ROM to boot if you had booted into the stock recovery and run a full wipe. Touchwiz ROMs can be tough to get running after being on AOSP. As a general progression try to format internal storage with TWRP (the wipe where you have to type "yes" to confirm), if that doesn't work try a wipe with Philz, and if that doesn't work nothing, not even Odin, is effective as a wipe in the stock recovery.
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
Click to expand...
Click to collapse
Yep. You've got it. If you're on the latest and greatest firmware I think the towelroot exploit has been patched, unless geohot has retaken the lead in that arms race.
Easiest way to root on this phone since the bootloaders are unlocked is to just use Odin to flash a custom recovery then use the custom recovery to flash SuperSU. There's just a little trick to it. Store SuperSU.zip somewhere on your phone before flashing the custom recovery. Uncheck everything but f.reset time when you use Odin; don't let it auto reboot. Upon success pull battery. Replace battery and boot straight into recovery with vol up + home + power. If you mess up and boot into unrooted stock ROM with a custom recovery it will get overwritten with a stock recovery and you'll have to Odin custom recovery back onto it and try again.
I would do this to root your stock ROM just to execute this command in a terminal app or adb shell before any more serious flashing:
Code:
su
reboot nvbackup
That fixes a derp and gives you a working efs backup on a few backup partitions built into your phone instead of a blank one. Highly recommended before doing any ROM flashing. This will just look like a pretty normal reboot. You might see a quick flash of tiny blue text if you're watching for it.
Then you're ready to make a nandroid backup (just in case), wipe, and flash away. Take a look at LiquidSmooth if you're looking for a good lollipop ROM.
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Thanks for the suggestion on the ROM but I think I'll stick to official cm12.1 it's not my phone and that should be a nice readily updatable bland flavor of lollipop.
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Click to expand...
Click to collapse
At the Android 4.3 update it was noticed that flashing a custom recovery would be overwritten by the stock recovery on the initial reboot unless following the method Jason described. Another solution was to delete two lib or .so files. On devices still on stock recovery, stock recovery does not overwrite itself.
There is a blank EFS partition on the device intended for a backup. The nvbackup command populates that partition with an image which will rebuild your EFS if it is lost during a modem update or ROM flash. The loss of EFS does happen. I believe wanam, of the xposed module fame, created an EFS backup tool for Samsung devices. I don't believe he updates it any longer because he rolled the functionality into a partition backup tool, the later is in the PlayStore listed under a different creator name, yet it's still him.
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
coolwhipp420 said:
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
Click to expand...
Click to collapse
Since you are on LK3 you may want to considr applying the free sim/carrier unlock method before upgrading; that is if you are on stock LK3 and you have not previously carrier unlocked your device.
There was an OTA release for the MG2 stock ROM, I believe that was 4.1.2. You may want to go to that before MJB. Did you make the nvbackup suggested by Jason?
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
There is a command to manually trigger the restore routine. I think it's
Code:
reboot nvrestore
but don't hold me to that. I'd never execute that command except if in dire need. The problem with this phone is there is an automatic routine that can be triggered in the event of a bad flash that will overwrite your nvram with the backup, even if the backup is blank. I don't think the backup stores anything modem specific, but I've never been able to confirm that. So I've always done it again after updating modems (only had to once).
Having the phone sim unlocked can be nice if you plan on traveling internationally. Otherwise, potential future carrier hopping or added resale value are the only reasons to do it.
coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
If you will never be switching carriers, nor ever sell/give/trade the phone to someone who will switch, then it is an unecessary step to do the carrier unlock.
I see Jason beat me to answering both of your questions.
Hello,
I'm a noob but usually try to fix this kind of issues on my own, looking at the boards, following tutorials, learning, but this time I think I'm not able to find a solution on my own so I'm asking for advice here.
Some time ago I installed cyanogenmod 10.1 on my Note 2 LTE and was happy with it for some month, than last week I tried to upgrade to cm12.1 It worked but there where some issues and bugs, mainly I wasn't able to swap internal/external sd cards.
So I decided to go back to latest available stock rom 4.4.2 from sammobile.
Here is where the problem starts. The stock 4.4.2 resulter in a bootloop, tried cache/dalvik/factory reset, flash again, whipe again.. nothing.
The phone is not able to get past the white label "Samsung Note 2 gt-n7105" screen. It goes black than the white label again and again.
It doesn't even get to the Samsung animated logo.
Ok bottloop, no problem, try to flash again something else.
I tried different Custom roms, different kernels, different flashing methods. I can flash anything with no problem but every time a get a bootloop.
During the various attempts knox fired, but I don't care. I don't know if this could be the cause.
Actually the only firmware that works is the original oldest STOCK 4.1.2, every other stock firmware past that or any custom rom is bootlooping the same way. To fix I only can reinstall stock 4.1.2 with odin.
I really need any advice or hint.
At the moment my goal is to get at least to stock 4.3 but I cant.........
Thanks!
When you first bought your phone, did it come with Knox?
ErnestChia said:
When you first bought your phone, did it come with Knox?
Click to expand...
Click to collapse
nope it doesn't existed before, but now I can see it when I boot in download mode "knox warranty void:1"
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/showthread.php?t=2088809/[URL]
From what you've described, I think the Stock ROM 4.4.2 from Sammobile contained a bootloader update. So when you flashed this ROM, it updated your bootloader from the non-Knox version to the Knox version.
I am very unfamiliar with the technical details of Knox, but I think the new Knox bootloader is causing your bootloop problem.
However, I don't know why 4.1.2 works when everything else doesn't work!
Can you check the Stock ROM 4.4.2, and see whether it really contains a bootloader update?
mysuperdonghae said:
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/sho...can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
misthero said:
I think so, there is a boot.im, anyway I also discovered that I can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
Since a boot.img is present, it means that it would flash your boot partition. So now we know for sure that when you attempted to flash the Stock ROM 4.4.2, your bootloader was changed to the Knox version.
So the lesson here is: before you flash anything via ODIN, always check to see if there is a bootloader update. Usually you don't want to be changing the bootloader on your phone.
***
So now there are 2 possible ways to reach your goal:
1) Keep your new bootloader and see whether you can get Stock 4.3 or Stock 4.4.2 running on your phone
2) Try to restore your old bootloader
As I said earlier, I'm not familiar with the technical details of Knox, so I'm not sure how to get Stock 4.3 or Stock 4.4.2 running on your phone when your Knox indicator is already 0x1. You need someone else to help you.
And you can only restore your old bootloader if you happen to have made a copy of your boot partition before you flashed the Stock ROM 4.4.2. Even if you did have a copy of your original boot partition, I'm not confident with helping you to restore your old bootloader. You need someone else to help you in this case too.
Conclusion: I don't think I can help you to solve your problem I'm sorry. Hopefully someone else who is more of a pro than me will come along to help you out.
Good luck!