I am looking for the stock 4.4.2 NE4 rom for D2ATT to flash through Odin.
A little background. Phone soft boots on me, and I am able to get into recovery. However, if I try to flash anything or restore a backup, the phone reboots. I am able to get into download mode, but can't find the correct stock file to flash. I have the recovery flashable file, but can't flash it. Every where I have searched for the Odin file has been a dead end.
This has happened to me before, and Odin did the trick. That was on 4.1.1 though which was before the bootloader changes.
Anyone have the Odin file by chance? Thanks.
[CORRECTION]: I am on the NJ1 bootloader/modem.
There is no stock firmware available for later builds.
What were you trying to do when you got to the soft brick?
Any errors when you try to flash a rom?
What roms have you tried flashing?
What is your current bootloader version?
Sent from my SGH-T999 using Tapatalk
I was afraid of that. Actually I wasn't doing anything (this time lol). I was running the official CM nightlies (I think I flashed last week some time, coming from Pac Rom).
When I try to flash in recovery, the screen goes black several second into flashing and then reboots into a boot loop. If I try to turn on it is a boot loop as well. I am in the latest NE4 modem/bootloader version.
Edit: I was able to do a wipe in recovery before reboot. It had an error with data during the wipe. I wasn't able to get a picture in time so I don't know what the exact error was.
Edit #2: When trying to flash I get the error "cannot mount system" before it boot loops on me.
Ok so you were running cm and are trying to get back stock correct?
If I recall correctly, you need to just flash the stock recovery and factory reset from there.
You can find the stock recovery in one of enewman17's bootloader/modem threads. Let me know if you can't find it.
Not sure that'll solve it for you, but I'd say it's worth a shot.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 01:33 AM ---------- Previous post was at 01:28 AM ----------
NE4 stock recovery.
https://www.androidfilehost.com/?fid=23681161096070493
Flash from custom recovery.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
NE4 stock recovery.
https://www.androidfilehost.com/?fid=23681161096070493
Flash from custom recovery.
Sent from my SGH-T999 using Tapatalk
Thanks! Ok question for you. How will this get the stock firmware installed? I still have the problem of no Odin flashable firmware.
Edit: It looks like I am unable to get into recovery at this point. Phone just reboots.
Is it possible the phone has a problem with the power button? Was it hyper-sensitive before the bootloops started?
audit13 said:
Is it possible the phone has a problem with the power button? Was it hyper-sensitive before the bootloops started?
Click to expand...
Click to collapse
That's possible. I had this issue before though, and it was fixed when I use Odin to reflash stock. Right now it's at the point where it will automatically try to boot up when I put the battery in.
Edit: The other thing I was thinking of, was possibly corrupted partitions, or perhaps the storage is corrupted/ needs formatted.
Edit#2: Just did some back reading, and realized I am on the NJ1 bootloader, which is the latest 4.4.2. I thoroughly regret upgrading, so if you are reading this and considering an update, DON'T DO IT!!!! I will update the OP and thread title accordingly.
The phone now will not stay booted in download mode either. Ends up rebooting after a couple of seconds.
I think this one is pretty much hosed, as even if I were able to unbrick it, there still is the matter of no compatible software that can be flashed. It is not my daily driver, so not the end of the world, but it still sucks. The biggest loss is several videos I took this weekend of a martial arts tournament my son was in.
Thanks so much guys for your help on this. It is much appreciated.
Sounds like you've got the faulty power button. If it tries to turn on when you insert the battery, it's a sure sign of this.
Replacements are pretty cheap if you care to try soldering it yourself. Otherwise most repair shops should be equipped to help you out.
The reason I suggested factory resetting from stock recovery is because many people have had similar issues when coming from cm. Not sure why, but it does a better job at reformatting the internal memory. After doing the reset, most people are able to boot into stock again.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 03:13 AM ---------- Previous post was at 03:04 AM ----------
Oh, and it is possible for corruption to occur when it is constantly rebooting. I don't think it's common though. I had one that was doing exactly the same thing for over a month and I never had any data loss or corruption.
It's only a temp fix, but try blowing into the power switch with a can of compressed air. You can also try giving it a swift, gentle (but hard) tap on the edge of a wood table. (Try on both sides of the phone and around the button itself). This is how I was able to keep using mine until I got around to fixing it. Beware though, hitting it too hard, or against something with no give can easily crack the glass! Obvious, I know, but figured I should mention it anyway!
Oh and if you get it to come back on, don't even breathe on the power button! It'll be super sensitive still. I couldn't even use my case until it was fixed.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Sounds like you've got the faulty power button. If it tries to turn on when you insert the battery, it's a sure sign of this.
Replacements are pretty cheap if you care to try soldering it yourself. Otherwise most repair shops should be equipped to help you out.
The reason I suggested factory resetting from stock recovery is because many people have had similar issues when coming from cm. Not sure why, but it does a better job at reformatting the internal memory. After doing the reset, most people are able to boot into stock again.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 03:13 AM ---------- Previous post was at 03:04 AM ----------
Oh, and it is possible for corruption to occur when it is constantly rebooting. I don't think it's common though. I had one that was doing exactly the same thing for over a month and I never had any data loss or corruption.
It's only a temp fix, but try blowing into the power switch with a can of compressed air. You can also try giving it a swift, gentle (but hard) tap on the edge of a wood table. (Try on both sides of the phone and around the button itself). This is how I was able to keep using mine until I got around to fixing it. Beware though, hitting it too hard, or against something with no give can easily crack the glass! Obvious, I know, but figured I should mention it anyway!
Oh and if you get it to come back on, don't even breathe on the power button! It'll be super sensitive still. I couldn't even use my case until it was fixed.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you. I will give that a shot.
Related
Hey guys,
I've never had any real problems with any android phone that I've had. However, I have been running Liquid Beta 2 on my nexus for over a week now and it seemed to be running great. I did see a few random reboots every now and then but thought that might be due to it being a beta.
Today it seemed to escalate to a new level. I turned on the torch in the pulldown bar and as soon as the light came on the phone restarted. However this time it was never able to start back up. It got about half way through the boot animation and started over and will continuously do this.
I can still boot into recovery so that is good news. I have tried restoring previous roms that I had backed up for just in case and they ran into the exact same problem. I have also tried wiping everything and then installing a fresh rom that I had on my phone and again, ran into the same problem.
At this point I am clueless and really have no idea what to do. If anyone can perhaps share some advice or give some suggestions, that would be great and I would greatly appreciate it. Thanks guys.
edit: Not sure if it matters but I do have the Verizon branded GN.
Make sure you are wiping data, cache and dalvik.
Make sure you didn't get a bad download on the rom you are trying to flash.
I am running stock kernels and have never installed any non stock kernels as stock seems to run just fine. I have wiped everything completely and I've tried two different roms and get the same problem. I don't think it has to do with it being bad downloads. Thank you for the advice though guys. Anyone else have any input? I may just have to go to the verizon store and see if I can exchange it out.
Dude. I had that too some weeks ago and had the problem that I encrypted the phone, which made me not getting into recovery mode. I downloaded a fresh restorer rom from samsung. After everything was fresh I never saw the failure again.
Sent from my Galaxy Nexus using XDA App
murflee33 said:
Hey guys,
I've never had any real problems with any android phone that I've had. However, I have been running Liquid Beta 2 on my nexus for over a week now and it seemed to be running great. I did see a few random reboots every now and then but thought that might be due to it being a beta.
Today it seemed to escalate to a new level. I turned on the torch in the pulldown bar and as soon as the light came on the phone restarted. However this time it was never able to start back up. It got about half way through the boot animation and started over and will continuously do this.
I can still boot into recovery so that is good news. I have tried restoring previous roms that I had backed up for just in case and they ran into the exact same problem. I have also tried wiping everything and then installing a fresh rom that I had on my phone and again, ran into the same problem.
At this point I am clueless and really have no idea what to do. If anyone can perhaps share some advice or give some suggestions, that would be great and I would greatly appreciate it. Thanks guys.
edit: Not sure if it matters but I do have the Verizon branded GN.
Click to expand...
Click to collapse
Flash it back to stock and if it still does this, contact Verizon.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/
Geezer Squid said:
Flash it back to stock and if it still does this, contact Verizon.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/
Click to expand...
Click to collapse
DO NOT CONTACT VERIZON. After unlocking bootloader, your warranty is voided. Verizon will not be able to help you.
@OP: You can always flash back to stock using stock images provided by google via fastboot with the link Geezer provided.
zephiK said:
DO NOT CONTACT VERIZON. After unlocking bootloader, your warranty is voided. Verizon will not be able to help you.
@OP: You can always flash back to stock using stock images provided by google via fastboot with the link Geezer provided.
Click to expand...
Click to collapse
Not kidding. That link to tells him how to return to stock and re-lock the bootloader.
Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Another Update:
I just re-flashed with odin, this time it says it successfully completed but once again it's stuck at the flashing Samsung logo with the indicator led on.... I am starting to really freak out lol. I have another file downloading that is supposedly just stock, no root or anything...
rakhov said:
Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Click to expand...
Click to collapse
Actually have the exact same situation going on right now, I will post if I can find a fix. Downloading an alternate stock build I found now and will let you know how it goes.
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
rakhov said:
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
Click to expand...
Click to collapse
Thats exactly what Odin is working on loading now, Download had just finished.
avarize said:
Thats exactly what Odin is working on loading now, Download had just finished.
Click to expand...
Click to collapse
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
rakhov said:
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
Click to expand...
Click to collapse
I've always noticed the LED being on during boot (or some of the boot) and it was also on when I had a bootloop during cm9 so I don't think it means anything.
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
rakhov said:
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
Click to expand...
Click to collapse
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
Click to expand...
Click to collapse
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 for reboot options to force it into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 to force into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
Click to expand...
Click to collapse
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
rakhov said:
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
Click to expand...
Click to collapse
Should have explained a bit better. Yes that toolkit
While it was stuck at samsung screen.
1 For AT&T (Obviously)
20 For reboot options
1 For recovery.
Then wipe data/cache
Then wiped cache (no idea why)
then rebooted.
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
That is exelent. I am downloading the toolkit right now and will report back shortly.
Once you got it to boot, did you still have root? I am wondering if you flashing the "stock rom" that I posted, if that had any impact. I have only pushed the root66 file, so I am expecting root when(if XD) I get this thing going again. I appreciate you being more thorough with your instructions, and will report back with my results as soon as I get some
Also, are we loners on this? I am not seeing any other posts about going back to stock/stock rooted from modded roms using odin? I am trying to figure out the best method to go back to stock. I made a nandroid and I am sure that would work, but all of this word about having to flash different kernels and bluetooth/wifi drivers to get stock working properly makes me wonder if just using odin is the easiest method, as it restores everything on the phone (to my knowledge).
crash822 said:
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
That is great, this may sound a little silly, but how do I boot to recovery? Thanks!
UPDATE:Nvm, google hehe. I just did the factory reset...Things are looking good so far, the haptic lights turned on at least...BOOM! We are good gentlemen. It looks like all it took was the recovery wipe. This is great news! I will try to figure out how to mark this as solved, and you crash822, you get a thanks
NP sir. We all have to start somewhere. Luckily for me I was already planning on doing a full wipe so I backed up everything I wanted to keep from my phone onto my computer before using odin.
I seem to be having the same issue. I've downloaded the toolkit as you guys have suggested. are you guys in download mode on the phone while you use this? it seems to want me to be in debugging mode and i can't get to that. I've tried a factory reset with no luck.
It all started here:
http://support.t-mobile.com/thread/44716
I griped on the T-Mobile forums about the struggle I've had in finding a smooth ROM for my T999. And I made an off-handed comment in another thread that got me pointed in the right direction hopefully. I'm looking for other T999 owners that have this problem.
The problem on DMD5 is all related to (apparently) intensive tasks. Playing games, mostly. Temple Run 2 and Fruit Ninja, neither of which are all that intensive, were nigh-on unplayable. Other games like Scramble with Friends would lag and stutter a bit, too. So after a lot of searching, I reverted to a pre-rooted T999UVDLJC with the matching baseband, so that way my phone doesn't try to update itself OTA. And performance is pretty good. But I'd like to think that I'm not alone, and I found I'm not alone in this thread:
http://forum.xda-developers.com/showthread.php?t=2326763&page=33
At the bottom of this page and the top of the next one, I found at least one kindred spirit that has a rev0 phone and has the same issue with DMD5.
NO other ROM has this issue. I've tried all of the official Samsung ROMs and I have tried official CM10.1 nightlies and the official 10.1 stable release and performance is very good on all of them. But it took a huge serious nosedive on T999UVDMD5.
So I'm curious about two things:
Does DMD5 run well on your phone? Particularly with games - that's where it was most notable, but even TWLauncher is laggy for me.
How old is your phone? According to the box for my phone it was built 6/30/2012.
If you are affected, could you help us all out on the T-Mobile support forum, and post a message in my thread at the top of the page? If we can get T-Mo and/or Samsung to look into it maybe we won't get left behind. I plan on using this phone for another year or more and I'd rather get the official updates in the future, too.
Update July 6, 2013: I found out thanks to help from people in this thread that I can run mismatched modem firmware/ROM and with the JLC modem on MD5 ROM, my phone runs fantastic. Or at least it has for about 2 hours - usually issues have shown themselves by now, and since they haven't cropped up I'm calling this resolved.
When you were on MD5, how did you update to it? OTA? Odin? Recovery flashable ROM?
And how much data have you been carrying over? (When did you last wipe data/factory reset, without restoring backups?)
Sent from my SGH-T999 using xda premium
---------- Post added at 01:03 AM ---------- Previous post was at 12:50 AM ----------
Btw, I'm on MD5, completely stock right now. Hw is Rev. 0
I get very little lag, if any, ever. Simple games or even intensive games run very fluidly for me.
For example, I just got Man of Steel when it went on sale and it works almost perfectly. Disney, Gameloft, EA games have all worked just fine.
The only MD5 issues I've seen around here seem to occur when someone is using a mixed build with the MD5 radio. And then its only been reports of heat issues and slight battery issues. Haven't seen much of anything regarding poor performance.
Sent from my SGH-T999 using xda premium
Please do not check "yes this is a question" if it is "info gathering" as all Q's are moved to Q&A. I will edit the title for you.
FNM
DocHoliday77 said:
When you were on MD5, how did you update to it? OTA? Odin? Recovery flashable ROM?
And how much data have you been carrying over? (When did you last wipe data/factory reset, without restoring backups?)
Sent from my SGH-T999 using xda premium
---------- Post added at 01:03 AM ---------- Previous post was at 12:50 AM ----------
Btw, I'm on MD5, completely stock right now. Hw is Rev. 0
I get very little lag, if any, ever. Simple games or even intensive games run very fluidly for me.
For example, I just got Man of Steel when it went on sale and it works almost perfectly. Disney, Gameloft, EA games have all worked just fine.
The only MD5 issues I've seen around here seem to occur when someone is using a mixed build with the MD5 radio. And then its only been reports of heat issues and slight battery issues. Haven't seen much of anything regarding poor performance.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I've tried all of the above. I even let Kies install it once. I've used TriangleAway and Odin to install 4.0.4 and let it do all the OTAs. Iv'e done factory resets and I've told setup not to restore my data to the phone and started from scratch. I used a flashable ZIP with the pre-rooted ROM, and when I did that I also got the DMD5 modem flashable ZIP to go along with it. I've tried not rooted. I've tried custom kernels, and I've tried stock. Odin completely stock and flashable zip totally customized. I've played with custom DMD5-based ROMs with the v6 script and I've tried not. I'm way out of ideas right now.
Sorry, @kennyglass123, I didn't realize I'd checked that box.
Starting to think all of them have "rev 0" for the CPU identifier, so that may not be the way to tell who has what.
Just to be clear, did you ever Factory Reset, then Odin flash MD5 (not mobile odin btw), and factory reset again to ensure internal sd was cleaned out too? If for MD5, you only flashed the Rom and Modem, you would have been on a mixed build. Also, many devs suggest waiting an hour before starting with any testing or reconfiguring. I'm not convinced this is always necessary, but they do usually kno more than me!
Don't get me wrong. I'm not trying to argue against your point, just to make sure not only that you've covered all angles, but that anyone who wants to back up your claim has also done the same.
As for the revision number, it may still be relevant as mine would have been among the first built too. We would need to find at least several others with the same, and different, to know for sure if it matters here.
Its always possible too that you got the unlucky pick of the hardware. (Just as possible though that I got a lucky pick)
Anyway, if you really are having that bad of problems with it, you may want to check if its still under warranty. I don't believe its the norm though.
Sent from my SGH-T999 using xda premium
Yeah I'm pretty sure, but I'm willing to do anything at this point. I'll do it again. I've stashed the Odin tar.md5 file on my backup hard drive, so I'll back up my working config and flash it again. Worst case scenario is that I re-root it, re-install recovery, and then restore my backup. Should take an hour max.
Use the root66 version of the firmware. Its pre rooted and is what I am running right now. Root alone won't have any negative effect, but will allow for much better troubleshooting.
Aside from that, keep it as clean from restored data as possible. Even a single corrupted contact entry can cause services to hang and eat up resources. I wouldn't even flash a recovery until you're ready to restore something.
(I use Mobile Odin Pro and it almost completely replaces the need for cwm or twrp. The only thing it can't do yet is make a nandroid backup.)
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Use the root66 version of the firmware. Its pre rooted and is what I am running right now. Root alone won't have any negative effect, but will allow for much better troubleshooting.
Aside from that, keep it as clean from restored data as possible. Even a single corrupted contact entry can cause services to hang and eat up resources. I wouldn't even flash a recovery until you're ready to restore something.
(I use Mobile Odin Pro and it almost completely replaces the need for cwm or twrp. The only thing it can't do yet is make a nandroid backup.)
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
So the root66 is an Odin image? I assume you're talking about this: http://forum.xda-developers.com/showthread.php?t=1771687
I've got it downloading now. Thanks for all your suggestions. I've not heard of Mobile Odin Pro, is it a custom recovery?
Whoops - found the Mobile Odin thread on XDA and got the lite version and the T999 flashing kernel. I'll give it a go.
Regarding The AOSP MD5 issues: the same thing is happening to me on stock. Have to use LJC or the battery sucks. What are your reboot habits like?
DocHoliday said:
If for MD5, you only flashed the Rom and Modem, you would have been on a mixed build. Also, many devs suggest waiting an hour before starting with any testing or reconfiguring. I'm not convinced this is always necessary, but they do usually kno more than me!
Click to expand...
Click to collapse
There is no possible way it could be necessary. Proof or it's placebo.
DeerSteak said:
So the root66 is an Odin image? I assume you're talking about this: http://forum.xda-developers.com/showthread.php?t=1771687
I've got it downloading now. Thanks for all your suggestions. I've not heard of Mobile Odin Pro, is it a custom recovery?
Click to expand...
Click to collapse
Yes, root66 is basically just 100% stock firmware, only rooted. Itll download as a .7z file. Just extract it and use the .tar.md5. You have the correct thread.
Mobile Odin is one of my all time favorite apps. Its from Chainfire if you are familiar with him. (SuperSU)
Its not a recovery exactly. What it does is reboots using what's called a flash kernel. This allows it to flash firmware like PC Odin, but also can flash roms that are made for recovery flashing. It doesn't replace the stock recovery like cwm/twrp either, so it also won't trip the flash counter. (I know that doesn't really matter with Triangle Away available (also by Chainfire)).
The only two drawbacks, (minor imo) are that it can't create nandroids, and it doesn't flash the FULL firmware (this is by design though).
I wouldn't bother with it right now, but definitely check it out after testing all this. Theres a free, lite, version here on xda. Ill send more info from my computer later.
Sent from my SGH-T999 using xda premium
---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------
DeerSteak said:
Whoops - found the Mobile Odin thread on XDA and got the lite version and the T999 flashing kernel. I'll give it a go.
Click to expand...
Click to collapse
Don't use Mobile Odin for testin right now. It doesn't flash the full firmware.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Yes, root66 is basically just 100% stock firmware, only rooted. Itll download as a .7z file. Just extract it and use the .tar.md5. You have the correct thread.
Mobile Odin is one of my all time favorite apps. Its from Chainfire if you are familiar with him. (SuperSU)
Its not a recovery exactly. What it does is reboots using what's called a flash kernel. This allows it to flash firmware like PC Odin, but also can flash roms that are made for recovery flashing. It doesn't replace the stock recovery like cwm/twrp either, so it also won't trip the flash counter. (I know that doesn't really matter with Triangle Away available (also by Chainfire)).
The only two drawbacks, (minor imo) are that it can't create nandroids, and it doesn't flash the FULL firmware (this is by design though).
I wouldn't bother with it right now, but definitely check it out after testing all this. Theres a free, lite, version here on xda. Ill send more info from my computer later.
Sent from my SGH-T999 using xda premium
---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------
Don't use Mobile Odin for testin right now. It doesn't flash the full firmware.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
OK awesome, I will check it out. I think what I'm going to do right now is just reset the flash counter, flash the Odin image, and then factory reset and set it up as a new phone. Does that sound reasonable? If I reboot into CWM after triangle away, it trips the flash counter again, at least that's what it seems to do, so I can't do anything other than reboot to download after Triangle Away.
Aerowinder said:
Regarding The AOSP MD5 issues: the same thing is happening to me on stock. Have to use LJC or the battery sucks. What are your reboot habits like?
There is no possible way it could be necessary. Proof or it's placebo.
Click to expand...
Click to collapse
I don't reboot unless the battery dies, or I was rebooting a lot when I was on MD5 trying to get stuff to work well. Generally I try not to mess with a good thing.
DeerSteak said:
OK awesome, I will check it out. I think what I'm going to do right now is just reset the flash counter, flash the Odin image, and then factory reset and set it up as a new phone. Does that sound reasonable? If I reboot into CWM after triangle away, it trips the flash counter again, at least that's what it seems to do, so I can't do anything other than reboot to download after Triangle Away.
Click to expand...
Click to collapse
That sounds fine. Remember, if you factory reset with stock recovery installed, it will wipe internal sdcard.
As long as you have cwm or twrp, the flash counter will always be at 1. I wouldn't worry about that for now though. It won't affect overall operation.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
That sounds fine. Remember, if you factory reset with stock recovery installed, it will wipe internal sdcard.
As long as you have cwm or twrp, the flash counter will always be at 1. I wouldn't worry about that for now though. It won't affect overall operation.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
OK, I won't mess with it too much then. I've backed up my internal storage already and I've backed up my SMS using SMS Backup and Restore. That thing has been very handy keeping copies of my texts while I screw with this.
Cool, sounds like you're good to go! Good luck! And let us know how things seem to be acting after flashing.
Don't forget to factory reset after flashing md5.
:thumbup:
Sent from my SGH-T999 using xda premium
OK I got as far as the factory reset and then it was time to paint. My daughter's bedroom wasn't going to paint itself. I finally came back to the phone and it was patiently waiting for me to log in. I logged in and installed just a couple apps while I ate lunch, and then it sat until we were done painting and cleaning up. Logged into Facebook and Twitter, set up Google Now and updated Samsung apps. Once all that was done, I fired up Temple Run 2 and it was OK at first, but within 3-4 minutes it was choppy and laggy again. The phone never got warm to the touch. It just ran poorly. I exited out and killed all apps with the built-in task manager, and went back to the game. Not really any better. It's just super choppy. I even turned down all the graphics options in the settings for the game and that made zero difference.
Eventually I gave up. Restored my 4.1.1 backup, fired up some stuff, performance was great. It's just the combination of my phone and that software. No idea what it is at this point. I do appreciate all the assistance you guys have lent me.
Right now I'm on T-mo and was waiting out the 60 days before I ported my wife's number in to my account. Now that that's over, I'll eventually port in her number. She's extremely happy with her iPhone 4s and insists she's not interested in an iPhone 5, so what I'll probably do is use the ability to get new hardware as an excuse to get a Galaxy S4. WHen I first came to T-mo I just got a SIM and bought the phone used - found out later on that I should have just bought a phone through T-mo because I can't get a new phone on a payment plan for a year unless it's as part of a new line. She'll be a new line, so I'll get a phone.
This hasn't put me off on Samsung or even on the GS3 - it's just my phone has a weird issue of some sort. And the people here have been super awesome. Thanks tons for all your advice. In the meantime I'll run JLC and leave well enough alone.
DeerSteak said:
OK I got as far as the factory reset and then it was time to paint. My daughter's bedroom wasn't going to paint itself. I finally came back to the phone and it was patiently waiting for me to log in. I logged in and installed just a couple apps while I ate lunch, and then it sat until we were done painting and cleaning up. Logged into Facebook and Twitter, set up Google Now and updated Samsung apps. Once all that was done, I fired up Temple Run 2 and it was OK at first, but within 3-4 minutes it was choppy and laggy again. The phone never got warm to the touch. It just ran poorly. I exited out and killed all apps with the built-in task manager, and went back to the game. Not really any better. It's just super choppy. I even turned down all the graphics options in the settings for the game and that made zero difference.
Eventually I gave up. Restored my 4.1.1 backup, fired up some stuff, performance was great. It's just the combination of my phone and that software. No idea what it is at this point. I do appreciate all the assistance you guys have lent me.
Right now I'm on T-mo and was waiting out the 60 days before I ported my wife's number in to my account. Now that that's over, I'll eventually port in her number. She's extremely happy with her iPhone 4s and insists she's not interested in an iPhone 5, so what I'll probably do is use the ability to get new hardware as an excuse to get a Galaxy S4. WHen I first came to T-mo I just got a SIM and bought the phone used - found out later on that I should have just bought a phone through T-mo because I can't get a new phone on a payment plan for a year unless it's as part of a new line. She'll be a new line, so I'll get a phone.
This hasn't put me off on Samsung or even on the GS3 - it's just my phone has a weird issue of some sort. And the people here have been super awesome. Thanks tons for all your advice. In the meantime I'll run JLC and leave well enough alone.
Click to expand...
Click to collapse
Before you give up, try debloating your install. I will PM you a link to the one I made. Backup first.
Aerowinder said:
Before you give up, try debloating your install. I will PM you a link to the one I made. Backup first.
Click to expand...
Click to collapse
OK i'll give it a go. Thanks.
Should I re-flash the MD5 modem?
I'd flash the LJC firmware, Third firmware link in my sig. LJC link is buried in the OP.
Aerowinder said:
I'd flash the LJC firmware, Third firmware link in my sig. LJC link is buried in the OP.
Click to expand...
Click to collapse
OK I see it there. So I should use the LJC modem/firmware with the DMD5 debloat ROM you're going to PM the link for to me? Will they work if they're mismatched? I assumed (not that I'd bothered asking before) that they'd all have to be the same.
I just unrooted my gs3 on softskip toolkit. Is it possible to remove twrp and go back to stock?. Do I have to root my phone first to restore my backup i made before i rooted my phone? I have to get my phone fix my camera is not working at sprint. Also is it possible to wipe data etc. I do not want them to know I rooted my phone.
missmonet said:
I just unrooted my gs3 on softskip toolkit. Is it possible to remove twrp and go back to stock?. Do I have to root my phone first to restore my backup i made before i rooted my phone? I have to get my phone fix my camera is not working at sprint. Also is it possible to wipe data etc. I do not want them to know I rooted my phone.
Click to expand...
Click to collapse
I'm just copying this from a previous post of mine on another thread.
The safest, easiest, and most foolproof way to restore to completely stock ROM and recovery would be through Samsung Kies. You can download Samsung's KIES software here: http://www.samsung.com/ca/support/usefulsoftware/KIES/JSP
Once in KIES, you would plug in your phone to the USB port and, if needed, download any drivers for your phone. Then, you would follow this path: Tools --> Firmware Upgrade and Initilisation. This will give you a warning that you will lose all your stored data on the phone, and will offer you to make a backup -- a very limited backup -- of information on your phone. If you don't have any worthwhile information, I'd skip the backup and go right to stock ROM/recovery restore.
Also, I am pretty sure you have to be on a Touchwiz ROM -- rooted/unrooted -- to restore. Recovery will not affect the ability to restore via Kies.
Caveat: Even though you do a complete stock restore via Kies, that will not reset the flash count in the bootloader. There is no way to reset it, and does indicate tampering even though you're on stock.
Hope this helps.
Higgs_Boson said:
Caveat: Even though you do a complete stock restore via Kies, that will not reset the flash count in the bootloader. There is no way to reset it, and does indicate tampering even though you're on stock.
Hope this helps.
Click to expand...
Click to collapse
Ive never ran it on stock but triangleaway reset my flash counter to zero. I just ran it cuz mine was high and I wanted to see if it worked, which it did. There's also a way to get your software to official in the about phone menu if triangleaway doesnt, again it did on mine even though I'm running a custom rom
jbnorton0524 said:
Ive never ran it on stock but triangleaway reset my flash counter to zero. I just ran it cuz mine was high and I wanted to see if it worked, which it did. There's also a way to get your software to official in the about phone menu if triangleaway does, again it did on mine even though I'm running a custom rom
Click to expand...
Click to collapse
There is no known way to reset the KNOX trip status. That's what I was referring to. Once you flash something in ODIN it trips the KNOX indicator. I guess it's not quite the sams as a flash count, now that I think about it.
You are correct in that there is a way to show the phone status as "official" but that's purely cosmetic.
Oh OK. Gotcha. I wasn't even thinking about Knox when I put that. Do they actually check that if you have to go in for warranty work, or is taking them a smashed phone the only way around that?
jbnorton0524 said:
Oh OK. Gotcha. I wasn't even thinking about Knox when I put that. Do they actually check that if you have to go in for warranty work, or is taking them a smashed phone the only way around that?
Click to expand...
Click to collapse
I haven't the slightest idea. But, I imagine that if you don't let on that it is/was rooted and had a custom ROM, then I don't see why they'd check.
Who knows, they may even have an interface where they plug the device in and it immediately checks the bootloader for tampering.
Again, just guessing.
Higgs_Boson said:
I haven't the slightest idea. But, I imagine that if you don't let on that it is/was rooted and had a custom ROM, then I don't see why they'd check.
Who knows, they may even have an interface where they plug the device in and it immediately checks the bootloader for tampering.
Again, just guessing.
Click to expand...
Click to collapse
I hope not though. I heard a lot techs at sprint are not train to operate advances tec like root,COM etc.
Higgs_Boson said:
I haven't the slightest idea. But, I imagine that if you don't let on that it is/was rooted and had a custom ROM, then I don't see why they'd check.
Who knows, they may even have an interface where they plug the device in and it immediately checks the bootloader for tampering.
Again, just guessing.
Click to expand...
Click to collapse
ok. i have a big problem. remember when i was updating kies on my pc. my mom pulled the out the cord while it was updating my phone.She didnt know. now my phone is unstable from updating with kies. its say unfortunately sea has stopped, andriod, process system do you want to close i/log provider, s suggest stop,process acore has stopped system uid inconsistent. wipe phone partition. everything is unstable!
missmonet said:
ok. i have a big problem. remember when i was updating kies on my pc. my mom pulled the out the cord while it was updating my phone.She didnt know. now my phone is unstable from updating with kies. its say unfortunately sea has stopped, andriod, process system do you want to close i/log provider, s suggest stop,process acore has stopped system uid inconsistent. wipe phone partition. everything is unstable!
Click to expand...
Click to collapse
Just try running the Kies process again. It should work. If not, you'll have to put the phone in download mode and flash the ROM via ODIN.
missmonet said:
ok. i have a big problem. remember when i was updating kies on my pc. my mom pulled the out the cord while it was updating my phone.She didnt know. now my phone is unstable from updating with kies. its say unfortunately sea has stopped, andriod, process system do you want to close i/log provider, s suggest stop,process acore has stopped system uid inconsistent. wipe phone partition. everything is unstable!
Click to expand...
Click to collapse
You also shouldn't post questions in two threads (this one and the thread you created) about the same problem.
---------- Post added at 09:32 AM ---------- Previous post was at 09:31 AM ----------
jbnorton0524 said:
Ive never ran it on stock but triangleaway reset my flash counter to zero. I just ran it cuz mine was high and I wanted to see if it worked, which it did. There's also a way to get your software to official in the about phone menu if triangleaway doesnt, again it did on mine even though I'm running a custom rom
Click to expand...
Click to collapse
I was thinking of adding that info too, but then I thought yeah, he's referring to the warranty bit, although the flash counter is a different thing, and still resettable via Triangle Away.
---------- Post added at 09:38 AM ---------- Previous post was at 09:32 AM ----------
jbnorton0524 said:
Oh OK. Gotcha. I wasn't even thinking about Knox when I put that. Do they actually check that if you have to go in for warranty work, or is taking them a smashed phone the only way around that?
Click to expand...
Click to collapse
Best Buy Geek Squad, I can personally attest to, doesn't care if your warranty bit was tripped. Depending on your issue or the tech you talk to, you might be best resetting your flash counter via Triangle Away and Odining the stock ROM. For my first problem I exchanged phones for a few weeks ago, which was that OTG didn't work any more but data to the PC and charging worked, several techs were flipping out because there was the custom KT747 splash screen/custom recovery. Perhaps just restoring the flash counter and putting on the stock recovery would've been enough, but I wanted to wipe my phone for them anyway and put it back 100% stock. I went home, Odined the stock ND8 tar, took it back and they ordered me a replacement phone.
The second time I exchanged phones just a week ago, because the power button on the refurb they gave me was faulty and causing it to turn on and off randomly like they do, I already had Odined the stock ND8 tar. When I told the tech up front that I had restored it completely to stock, he acted as if it didn't matter.
As far as Sprint, others have had the personal experience that they don't care about the warranty bit either. Word is that Samsung is the only one that checks or cares about the warranty bit. At least one person even reported that a refurb phone either Sprint or Geek Squad gave as a replacement already had the warranty bit tripped.
Higgs_Boson said:
Just try running the Kies process again. It should work. If not, you'll have to put the phone in download mode and flash the ROM via ODIN.
Click to expand...
Click to collapse
yea its not working, I been trying. how do you go to download mode and download odin. I only use soft skit tool kit. Can I root my phone again and on the tool kit downloads odin for rooting process and twrp. Will it brick my phone the whole system is unstable. I cant get into recovery nor entering my phone.
roirraW "edor" ehT said:
You also shouldn't post questions in two threads (this one and the thread you created) about the same problem.
---------- Post added at 09:32 AM ---------- Previous post was at 09:31 AM ----------
I was thinking of adding that info too, but then I thought yeah, he's referring to the warranty bit, although the flash counter is a different thing, and still resettable via Triangle Away.
---------- Post added at 09:38 AM ---------- Previous post was at 09:32 AM ----------
Best Buy Geek Squad, I can personally attest to, doesn't care if your warranty bit was tripped. Depending on your issue or the tech you talk to, you might be best resetting your flash counter via Triangle Away and Odining the stock ROM. For my first problem I exchanged phones for a few weeks ago, which was that OTG didn't work any more but data to the PC and charging worked, several techs were flipping out because there was the custom KT747 splash screen/custom recovery. Perhaps just restoring the flash counter and putting on the stock recovery would've been enough, but I wanted to wipe my phone for them anyway and put it back 100% stock. I went home, Odined the stock ND8 tar, took it back and they ordered me a replacement phone.
The second time I exchanged phones just a week ago, because the power button on the refurb they gave me was faulty and causing it to turn on and off randomly like they do, I already had Odined the stock ND8 tar. When I told the tech up front that I had restored it completely to stock, he acted as if it didn't matter.
As far as Sprint, others have had the personal experience that they don't care about the warranty bit either. Word is that Samsung is the only one that checks or cares about the warranty bit. At least one person even reported that a refurb phone either Sprint or Geek Squad gave as a replacement already had the warranty bit tripped.
Click to expand...
Click to collapse
I wasnt getting many response. How other ppl got many responses for their threads in this section. Trying to get help asap. I was bugging out. Im going to delete it though.
When you say "unstable" what exactly do you mean? If you hold volume down+home button+power to turn the phone on it will/should enter download mode unless you are bricked. Go into download mode on the phone and put odin on your computer, get the stock tar file on your computer and flash it to your phone with odin.
Sent from my SPH-L710 using XDA Free mobile app
roirraW "edor" ehT said:
You also shouldn't post questions in two threads (this one and the thread you created) about the same problem.
---------- Post added at 09:32 AM ---------- Previous post was at 09:31 AM ----------
I was thinking of adding that info too, but then I thought yeah, he's referring to the warranty bit, although the flash counter is a different thing, and still resettable via Triangle Away.
---------- Post added at 09:38 AM ---------- Previous post was at 09:32 AM ----------
Best Buy Geek Squad, I can personally attest to, doesn't care if your warranty bit was tripped. Depending on your issue or the tech you talk to, you might be best resetting your flash counter via Triangle Away and Odining the stock ROM. For my first problem I exchanged phones for a few weeks ago, which was that OTG didn't work any more but data to the PC and charging worked, several techs were flipping out because there was the custom KT747 splash screen/custom recovery. Perhaps just restoring the flash counter and putting on the stock recovery would've been enough, but I wanted to wipe my phone for them anyway and put it back 100% stock. I went home, Odined the stock ND8 tar, took it back and they ordered me a replacement phone.
The second time I exchanged phones just a week ago, because the power button on the refurb they gave me was faulty and causing it to turn on and off randomly like they do, I already had Odined the stock ND8 tar. When I told the tech up front that I had restored it completely to stock, he acted as if it didn't matter.
As far as Sprint, others have had the personal experience that they don't care about the warranty bit either. Word is that Samsung is the only one that checks or cares about the warranty bit. At least one person even reported that a refurb phone either Sprint or Geek Squad gave as a replacement already had the warranty bit tripped.
Click to expand...
Click to collapse
Thats good to know though.
Also, if you didnt know how to get to download mode, you are trying to get to recovery by turning the phone on with volume up+home+power?
Sent from my SPH-L710 using XDA Free mobile app
jbnorton0524 said:
When you say "unstable" what exactly do you mean? If you hold volume down+home button+power to turn the phone on it will/should enter download mode unless you are bricked. Go into download mode on the phone and put odin on your computer, get the stock tar file on your computer and flash it to your phone with odin.
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
I mean my phone says unfortunately the process.com,andriod.phone has stopped. unfortunley SEA has stopped, Sytem UID inconsistent you need to wipe your data partition or your device will be unstable. then under that it says feeling lucky. I can go into download mode. My phone is not rooted though. I unrooted to take it back to sprint. Can I still use odin? my usb debuging not working maybe abd mode? My phone is not recognized my the pc anymore.
Yes you can still use odin to flash a stock rom
Sent from my SPH-L710 using XDA Free mobile app
Started out with having problems with freedompop, it suddenly started using up all my data for texts and calls, even though I'm on unlimited calls and texts. Tried to root the phone and bricked it.
Then I managed to unbrick with Odin reloading TWRP recovery.
Have now tried 3 or 4 ROMs and they all boot loop. I also upgraded the bootloader because I read you have to have a bootloader that can handle later android like 4.4 or 5.1. Now someone told me they never bothered with that and had no problem, so maybe the new bootloader is causing my boot loop problem? I've tried 2 bootloaders that can handle 4.4 and still get boot loop.
At this stage I'd be happy just to go back to 4.3 stock if it would get my phone working again.
I did notice that it didn't seem to be able to find any checksums when it was flashing, and just bypassed them. could that be it?
padosaurus said:
Started out with having problems with freedompop, it suddenly started using up all my data for texts and calls, even though I'm on unlimited calls and texts. Tried to root the phone and bricked it.
Then I managed to unbrick with Odin reloading TWRP recovery.
Have now tried 3 or 4 ROMs and they all boot loop. I also upgraded the bootloader because I read you have to have a bootloader that can handle later android like 4.4 or 5.1. Now someone told me they never bothered with that and had no problem, so maybe the new bootloader is causing my boot loop problem? I've tried 2 bootloaders that can handle 4.4 and still get boot loop.
At this stage I'd be happy just to go back to 4.3 stock if it would get my phone working again.
Click to expand...
Click to collapse
Downgrading boootloader will give u a nice shiny paperweight! What device you on reg s3 triband, bootloder?
Sent from my SPH-L710T using XDA Free mobile app
padosaurus said:
I did notice that it didn't seem to be able to find any checksums when it was flashing, and just bypassed them. could that be it?
Click to expand...
Click to collapse
Unless you downloaded an md5 file separately, then it will skip the checksum, because you didn't provide one. No big deal, as long as you checked it yourself.
Stop changing bootloaders or you will brick. Nj2 is fine for all current roms. By boot loop you mean it stayed in boot animation? Because lollipop roms do that. Sometimes if it stays for a loooong time, I boot to recovery then straight back to system and it starts optimizing right away. But you may just have to be patient.
(I can't seem to log back on with my other account and it made me start a new account using google....)
I've tried these roms:
aicp_d2spr_lp-10.0-NIGHTLY-20151210.zip
ND8_STOCK_ODEX_ROOTED.zip
and these bootloaders:
L710-ND8-Bootloader.tar
KT747-TW-KK-4.4-SPR-05-13-2014.zip
Is this the info you asked for? I don't know what reg s3 triband is.
I've gone back and forth between the above bootloaders but I think they are the same level bootloaders and the phone hasn't bricked so hopefully that's not the problem. someone else said I needn't have changed the original bootloader to try higher roms like 4.4 or 5.1, but I don't know.
hilla_killa said:
Downgrading boootloader will give u a nice shiny paperweight! What device you on reg s3 triband, bootloder?
Sent from my SPH-L710T using XDA Free mobile app
Click to expand...
Click to collapse
---------- Post added at 04:42 AM ---------- Previous post was at 04:34 AM ----------
madbat99 said:
Unless you downloaded an md5 file separately, then it will skip the checksum, because you didn't provide one. No big deal, as long as you checked it yourself.
Stop changing bootloaders or you will brick. Nj2 is fine for all current roms. By boot loop you mean it stayed in boot animation? Because lollipop roms do that. Sometimes if it stays for a loooong time, I boot to recovery then straight back to system and it starts optimizing right away. But you may just have to be patient.
Click to expand...
Click to collapse
KT747-TW-KK-4.4-SPR-05-13-2014.zip is the bootloader that is currently loaded, should I just leave that one?
the rom that's loaded now is supposed to be stock 4.4. It does the fancy sprint splash screen, then the word SAMSUNG appears and just stays there forever, with a blue shadow fading in and out.
Maybe I should try a different ROM? The other one I tried is aicp_d2spr_lp-10.0-NIGHTLY-20151210.zip, that also boot loops with a spinning pattern with icy android robot.
---------- Post added at 05:39 AM ---------- Previous post was at 04:42 AM ----------
madbat99 said:
Unless you downloaded an md5 file separately, then it will skip the checksum, because you didn't provide one. No big deal, as long as you checked it yourself.
Stop changing bootloaders or you will brick. Nj2 is fine for all current roms. By boot loop you mean it stayed in boot animation? Because lollipop roms do that. Sometimes if it stays for a loooong time, I boot to recovery then straight back to system and it starts optimizing right away. But you may just have to be patient.
Click to expand...
Click to collapse
So I shoulda/coulda checked the checksum myself?
paddosaurus said:
(I can't seem to log back on with my other account and it made me start a new account using google....)
I've tried these roms:
aicp_d2spr_lp-10.0-NIGHTLY-20151210.zip
ND8_STOCK_ODEX_ROOTED.zip
and these bootloaders:
L710-ND8-Bootloader.tar
KT747-TW-KK-4.4-SPR-05-13-2014.zip
Is this the info you asked for? I don't know what reg s3 triband is.
I've gone back and forth between the above bootloaders but I think they are the same level bootloaders and the phone hasn't bricked so hopefully that's not the problem. someone else said I needn't have changed the original bootloader to try higher roms like 4.4 or 5.1, but I don't know.
---------- Post added at 04:42 AM ---------- Previous post was at 04:34 AM ----------
KT747-TW-KK-4.4-SPR-05-13-2014.zip is the bootloader that is currently loaded, should I just leave that one?
the rom that's loaded now is supposed to be stock 4.4. It does the fancy sprint splash screen, then the word SAMSUNG appears and just stays there forever, with a blue shadow fading in and out.
Maybe I should try a different ROM? The other one I tried is aicp_d2spr_lp-10.0-NIGHTLY-20151210.zip, that also boot loops with a spinning pattern with icy android robot.
---------- Post added at 05:39 AM ---------- Previous post was at 04:42 AM ----------
So I shoulda/coulda checked the checksum myself?
Click to expand...
Click to collapse
Well kt747 is not a bootloader, its a kernel. And it's a kernel for stock 4.4.2. Stop flashing random things or you will destroy your phone. The difference between regular and triband s3 is big. Regular is sph-l710, the triband is sph-L710t. That little t makes all the difference. You need to check your model number.
Use odin to flash nj2 stock .tar and start fresh.
Get it here
You will also need the freedompop messaging app for your phone to work.
Got it back again with the nj2 stock.tar! Many thanks
Can't get freedompop messager because google play thinks it's already installed.
Mine says SPH -L710 on label behind battery, so I guess it's not triband?
CAn I now root and install a custom rom eg with android 5.1 and is it worth the trouble?
madbat99 said:
Well kt747 is not a bootloader, its a kernel. And it's a kernel for stock 4.4.2. Stop flashing random things or you will destroy your phone. The difference between regular and triband s3 is big. Regular is sph-l710, the triband is sph-L710t. That little t makes all the difference. You need to check your model number.
Use odin to flash nj2 stock .tar and start fresh.
Get it here
You will also need the freedompop messaging app for your phone to work.
Click to expand...
Click to collapse
paddosaurus said:
Got it back again with the nj2 stock.tar! Many thanks
Can't get freedompop messager because google play thinks it's already installed.
Mine says SPH -L710 on label behind battery, so I guess it's not triband?
CAn I now root and install a custom rom eg with android 5.1 and is it worth the trouble?
Click to expand...
Click to collapse
Google freedompop apk itll take you where u need to be! Some people have trouble dling it from google play check it out! Valuable info for you!
Sent from my SPH-L710T using XDA Free mobile app
paddosaurus said:
Got it back again with the nj2 stock.tar! Many thanks
Can't get freedompop messager because google play thinks it's already installed.
Mine says SPH -L710 on label behind battery, so I guess it's not triband?
CAn I now root and install a custom rom eg with android 5.1 and is it worth the trouble?
Click to expand...
Click to collapse
It is not a triband. Congrats on fixing it. Yes you can now easily root, using odin to flash the most recent twrp tar file for d2spr (our s3's codename).
5.1.1 roms were (are) worth it for me, but everyone's taste is different. I'm actually running aicp 11 (marshmallow 6.0.1) right now!