Okay, either I am a complete idiot who can't figure out the search function, or there are no Odin flashable roms for the sprint galaxy s3. I know there's the stock 4.3 one by cnexus, but I don't want that because it still has Knox.
So here's what I did. I downloaded the all-in-one zip from ThunderStick and ran it in the latest version of TWRP. The ROM booted up fine, and I was able to work with 4.3 for a bit, but it was acting funny, so I redownloaded the zip and went back to TWRP to re-wipe and re-flash. The flash seemed to go fine, but then once I hit the reboot system button it got stuck at the 'Galaxy S3' splash screen. I can still access TWRP, and it still shows the zip in storage, but it fails whenever I try to flash. So now, I need an ODIN tar, something like stock 4.1.2, just whatever can keep me away from knox so I can try reflashing cnexus's Knox-less version. I think I'm in what is called a soft brick... and all I wanted was for the stupid Ota "update is available" to stop bugging me every five minutes.
EDIT: Here's what happens when I try to install.
"Checking to see if your device is compatible
Device confirmed - d2spr
Checking previous ROM installed
File_getprop: failed to stat "/system/build.prop
E: Error executing updater binary in zip '/sdcard.......
Error flashing zip '/sdcard.......
Updating partition details"
And then a big red "Failed" under that.
I need this phone back in operation one way or another by tomorrow morning. I will spend all night on Google if that's what it takes, and maybe even sell a kidney if I have to. We'll see how the night turns out.
if you go here, there is a one click odin for md4 (4.1.2) [ROM][ODIN][TAR]SPH-L710 MD4 (MD4 Modem/Kernel/ROM - Stock)
Following those instructions should get you going
I can weigh in here. been roughly where u are.
check md5 on the files your using
try applying zips from both internal and external storage.
I screwed up watching tv and listening to family members instead of paying attention but your rarely lost completely.
my path backwords to 4.1.2 from thunders 4.3 "all in one" was
billards full "md4 with count reset zip" INSTALL ROOT/SU AND CWM/TWRP AFTER FLASH FROM CWM/TWRP or it wont be there after reboot. Of course you can lay your 4.1.2 backup over top after which will have all that.
the play store will have versioning issues going backwards, but they sort themselves out eventually. Maps will likely be the most annoying
Have fun and don't panic.
Thank you guys for your responses. I ended up stealing my girlfriend's micro sd card and installed the zip found here: http://forum.xda-developers.com/showthread.php?p=32176586 and that cleared things up. Then I just reflashed the ThunderStick all-in-one and it is working fine now, thank God. And I still have both my kidneys, for now.
Glad you got it going!
Related
Disclaimer: This worked on my phone. I am not responsible if your phone turns into an expensive brick.
I know this isn't quite the update everyone was waiting for I managed to pull the 2.3.6 OTA files. I also managed to figure out how to flash them. Turns out CWM 5 offers root adb access, everything we need to update and root this phone. Note I tried CWM 6 but it said "possible loss of root" so apparently CWM 6 likes to reside on an already rooted phone.
Note this is not the most elegant solution. The most elegant would be a signed update.zip. The second most elegant would be something flashable with CWM or Odin. Too bad I don't know how to do those. I do know how to do this.
The first thing to do is make sure you are on the AT&T stock firmware. It doesn't matter if you've already flashed something else. No need to wipe cache or factory reset or anything (although if you run into problems you should try to do that step). Download it from samfirmware.com. Flash it with Odin. This will put you on stock 2.3.5. Even if you were already on 2.3.6, or rooted, or on Rogers, this will work. After the flash, boot the phone normally, wait a minute or so, and shut it down.
Now for the fun part. AT&T will not push the OTA to a non AT&T customer. The flash will also not work with a modified phone (hence the reflash to stock). How to gain root access to manually flash the OTA? If we install root, it will not install. If we install CWM, we will not have the stock recovery which is required to process the OTA. So...
How about this? We install CWM 5. You can find it here http://forum.xda-developers.com/showthread.php?t=1458153
Then we adb into the phone, and push the OTA files, and then reflash the stock recovery over CWM, and then manually reboot into OTA mode. That sounds crazy... crazy enough to work.
After you've flashed CWM, reboot into it and make sure your phone is still connected to your computer. We won't actually be using CWM, just the root access it provides over adb. Unzip the two zip files below (why use external hosting, I can store zips up to 11 MB on here) into a folder and run fota.bat. Ooo and ahh over your Gingerbread.
But what about root? Well, I posted in another thread a complicated method for rooting 2.3.6 using the root access from CWM, but how about easy? Boot your phone into 2.3.6 and let it sit for a minute or so, and shut it down. Reboot into Odin mode, and reflash CWM over the stock recovery (again). Copy the Superuser zip from the folder you made earlier to your SD card. Flash this with CWM. This is the beta of Superuser 3.2, courtesy of Rom Manager. Download the stericson busybox app from the Market if you want busybox as well.
This was a fun way to kill a weekend
Throws a signature verification failed error.
Try again with the new method
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Why go to 2.3.6? It´s better than 2.3.5 customized?
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
AraDreamer said:
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
Click to expand...
Click to collapse
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
narume said:
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Click to expand...
Click to collapse
When I was testing this, I saw that behavior if you didn't completely boot up the phone between steps (ie, flash stock firmware, boot phone, flash CWM, boot phone). I don't know what would cause it otherwise. Glad to see your phone made it.
narume said:
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
Click to expand...
Click to collapse
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Nardholio said:
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Click to expand...
Click to collapse
Ah, I see. Well, still, being able to flash to 2.3.6 is nice because if anyone ever decides to stick with 2.3.6 they can easily flash the update now. Maybe more people like you will pop up and start pushing out more useful content like this for the Glide so it won't be a dead area of development anymore.
I have been trying to get my S3 to take the update from LG8 to Ll3, and it fails no matter what I try. I am running totally stock LG8 that I rooted using the toolkit posted in the development section. I don't have any APKs that I altered, but every time I try to flash the update, I get a "status 7" error. I tried it on both internal and external SD using CWM recovery. I tried flashing stock recovery via Odin and then let the phone download it over the air and attempt to install itself, and I even tried running the update in TWRP. Every time I get the same status 7 error.
I am coming from HTC phones and have never had these kinds of issues, so I'm pulling out my hair. Can anyone offer any suggestions? I know it must be something stupid I'm overlooking, but I've searched everywhere and can't seem to find the answer.
Sounds like a bad DL. Just grab it from here. http://forum.xda-developers.com/showthread.php?t=1743923
Or here http://forum.xda-developers.com/showthread.php?t=1904099
Or odin flash LI3- http://forum.xda-developers.com/showthread.php?t=1919919
A lot less stressful
The procedure that myn posted over here is pretty staight forward and foolproof too.
Have you solved your issue yet?
I am getting the status 7 error as well even with Myn's procedure. Others are having the problem. Only thing I can think of is the current image file has changed enough to not allow the update to go through. However, I have not removed or modified any stock apks and backed my whole system up with TB right after rooting so no reason for mine to not work. Binary file should be good since it is working for other S3 users.
It's not a bad download. I have tried downloading it multiple times from several sources, and I get the same status 7 failure every time. It even fails when the phone itself downloads the update and it tries to install with the stock recovery.
cfonte100 said:
It's not a bad download. I have tried downloading it multiple times from several sources, and I get the same status 7 failure every time. It even fails when the phone itself downloads the update and it tries to install with the stock recovery.
Click to expand...
Click to collapse
I was able to get mine to work using Myn's method. Seems flashing newest CWM recovery did the trick. Was trying to flash via TWRP and didn't think it would matter but apparently it does. Just followed his post and all upgraded without issue.
Back to your issue.....what state is your phone at currently? What recovery is installed and what version are you running? Surely we can get this resolved for you.
what does the log say when it fails? I mean in addition to status 7. If you don't see anything go under advance>show log. it's probably a failure in the checks it does before the flash. Have u modified your build.prop? is your baseband and build both lg8? That log will tell you what's wrong.or as I mentioned above you could follow 1 of my links and avoid tha headache
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?
Like I'm sure this topic hasn't come up before, but I've searched for hours and I'm probably just making things worse. I also just accidentally deleted this post halfway through. It's too late and I'm too tired and I have no working phone.
Bought an SGH-I747 on E-Bay. Got a Straight Talk SIM card kit, activated it, so far so good.
Rooted it with CF-Auto-Root. Worked pretty well, took a lot of reboots, upgraded the SU from the Play Store and it got rid of Knox. So far so good. Got everything all set up the way I like it. Happy.
It was running 4.4.2. I'm assuming it was the release prior to the November 12th OTA release, but I can't say for sure.
Phone downloaded and installed an upgrade automatically. Now, it won't boot. I get the SAMSUNG logo, then the Samsung Galaxy S III logo then nothing.
I retried the CF-Auto-Root, no change.
I booted into recovery (volume up, home and power on), did factory reset, no change.
Started looking around for a way to return it to stock. Found an upgrade43.zip file somewhere (I'm sorry I can't find where I got that now). Put it on the sdcard card and tried installing it with the recovery and it fails part way through.
At this point, I think I probably need to completely overwrite everything with something stock. I just don't know how to do that. I see posts on such subjects but they all have warnings that make me think I'm going to totally brick the phone, so I'm hoping someone can point me the right way. I'm not all that Android savvy, as you can tell.
Help.
Since your phone was running 4.4.2, do not attempt to flash any ROMs using that attempt to downgrade your bootloader to anything prior to 4.4.2.
Try this to get your phone up and running:
download the latest CM11 for the d2lte and save it to an external SD card: https://download.cyanogenmod.org/?device=d2lte
dowload the latest tar.md5 version of Philz Touch for the d2lte from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
boot phone in download mode, open Odin 3.07, do not check anything except f.reset.time, flash Philz via PDA box, remove USB cable when you see the word Reset appear in the status window, remove battery, replace battery, boot into recovery, format system, Dalvik, data, and cache, flash cm11, and reboot.
Thank you for your reply. There are a few things in there I don't quite understand, but I think I can figure it out.
I was going to attempt this...
http://forum.xda-developers.com/showthread.php?t=2658486
In fact, I did attempt it with TWRP last night after I posted here and new I still wasn't going to sleep. I kept getting an error about a bad ZIP file.
Is that stock restore a bad idea?
Do not attempt to flash an older bootloader. The mjb bootloader is from 4.3 and attempting to flash it could hard brick your phone.
I suggest doing what I suggested so you can confirm the bootloader and modem installed on your phone.
OK. Thanks. Probably a good thing I couldn't get it to work then.
Thank you so much. I have a working phone again. Now I just have to get it all set back up the way I like it.
I have to say, and it's probably words straight from the devils mouth, that I kind of wish I could have restored the Samsung stock software. It's just what I'm used to. But I will take what I can get.
A few questions. I like having root. But root is what got me in trouble in the first place. Is this going to be rooted now, or will I have to do that or am I better off just leaving it alone.
Second, I'm probably going to have questions since this is so different than what I'm used to (like I already can't find the Play store). Where is the best place to ask?
If you want root, one of the easiest ways to get it is to flash supersu from your custom recovery. Most ROMs are pre-rooted.
Many custom ROMs do not include Gapps. Just download and install the Gapps version for your ROM.
If you like the TW look, flash a TW-based ROM. Check out the development threads for different ROMs.
here is a thread for Q's that has some pretty good/friendly helpers on it if you need.
http://forum.xda-developers.com/showthread.php?t=2257421
"all i can really do , is stay out of my own way and let the will of heaven be done"
How to save in to external SD card
How do you save the file into the external SD card? I am having the same brick issue with my GS3.
To save a file to an external SD card, just put the card into a card reader and save the ROM to the SD card.
I am a frequent experience Android user and have been flashing Roms since like forever.
Owning gs4 been nice installing Roms all the time however recently when I went to install new gpe ROM (new kernel seemed prime to have) coming from HDrom rls20 I downloaded currupt zip. When I tried installing currupt zip (not knowing yet it was currupt) it gave me red errors not allowing me to proceed.. Then, I turned off device got fresh dload and made sure md5 sum was legit and it was tried again of course first factory data reset with advanced system wipe the ROM proceeded to aroma installer this time.. Attempting to install I chose all my settings and it went to progress bar to install and skipped any system extraction and went straight to Apks.. Batch completed and I hadn't a ROM installed for it took it 5seconds.. I have had this problem in the past before and I sold it they returned it (didn't like condition) and bingo I was able to install Roms again (this was way back in the day with this same gs4) I'm assuming system partition not mounting because also when I tried installing that currupt file it was saying in red unable to mount system and stuff. Luckily I downloaded NK2 firmware (took 8hs) and am fine on stock but I'm hoping someone has a clue to point me in right direction.. I saw forum of somebody with similar issue their fix was pushing zip via computer adb commands then installing. I'll have to give it a try but sticking to stock for a bit. BTW this happens with every ROM just skips system files in fact cyanogenmod just hhung at installation wouldn't fail or complete. I used TWRP LATEST. Please help developers I'm sure this ones a no brainer for y'all. Except seems like issue only I've encountered for this isn't a popular thing at all on google.
SOLVED
Thanks to somebody in gs3 forums all i had to do was push adb the rom and wow it worked installed system YAY IM HAAPPPYY
Stoowyguy said:
Thanks to somebody in gs3 forums all i had to do was push adb the rom and wow it worked installed system YAY IM HAAPPPYY
Click to expand...
Click to collapse
What does it mean to "push adb" a phone's rom? Doesn't Odin automatically flash the selected rom?