How to flash 4.3 or 4.4 roms - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I just got this phone and its running liquid smooth 4.2.2. i wanted to flash beanstalk 4.4 but it kept failing the flash. can someone point me in the right direction lol. i have the sgh 1747.

Need more information, carrier specific, model, error message when trying to flash
Sent from my SGH-I747M using Tapatalk

jimchee said:
Need more information, carrier specific, model, error message when trying to flash
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
i have the att version. its the sgh i747 version. after searching i think it won't flash those because i need to update to 4.3. but i don't know how.

pitbullmommy45245 said:
i have the att version. its the sgh i747 version. after searching i think it won't flash those because i need to update to 4.3. but i don't know how.
Click to expand...
Click to collapse
Don't do it if you think you might ever want to be able to use Odin as a recovery option. Once you upgrade to 4.3 on AT&T you're stuck if something bad happens to your phone you're going to have a hard time fixing it.
If yours sure you want to do it then Odin your phone back to an early firmware as soon as it boots it will force you to take an update. It may be 4.1.2 or it may be 4.3? Not sure but you just let the phone update through ota. Or alternately there are files with instructions in threads labeled with names similar to 4.3 OTA official.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Well right now there are some disadvantages, imho, to upgrading to 4.3 stock, once the bootloader is updated you cannot downgrade to any other build at this time, but that is a call for u to make, if you want to ota to 4.3 you have to get on stock 4.1.2 which you do through odin and then ota, not what I would do at this time just to many horror stories for my taste on 4.3 right now
Sent from my SGH-I747M using Tapatalk

theramsey3 said:
Don't do it if you think you might ever want to be able to use Odin as a recovery option. Once you upgrade to 4.3 on AT&T you're stuck if something bad happens to your phone you're going to have a hard time fixing it.
If yours sure you want to do it then Odin your phone back to an early firmware as soon as it boots it will force you to take an update. It may be 4.1.2 or it may be 4.3? Not sure but you just let the phone update through ota. Or alternately there are files with instructions in threads labeled with names similar to 4.3 OTA official.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
jimchee said:
Well right now there are some disadvantages, imho, to upgrading to 4.3 stock, once the bootloader is updated you cannot downgrade to any other build at this time, but that is a call for u to make, if you want to ota to 4.3 you have to get on stock 4.1.2 which you do through odin and then ota, not what I would do at this time just to many horror stories for my taste on 4.3 right now
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
so should i not do it? lol. mine is unlocked too. i'm using it on cincinnati bell. will this erase the unlock?

No once a phone is unlocked it cannot be relocked
Sent from my SGH-I747M using Tapatalk
---------- Post added at 02:02 PM ---------- Previous post was at 02:01 PM ----------
I wouldn't do it if it involves updating the bootloader at this time but that is just my opinion and am not a developer just an advanced tinkerer
Sent from my SGH-I747M using Tapatalk

if i understand your question correctly, you're trying to flash a 4.3/4.4 AOSP-based ROM? but it keeps failing?
i'm sorta having the same problem too, whenever i flash any ROMs based off 4.3/4.4 AOSP, i get constant reboots, about 2-3 an hour.
i am using CWM for recoery, but i don't think i tried BeanStalk 4.4

jimchee said:
No once a phone is unlocked it cannot be relocked
Sent from my SGH-I747M using Tapatalk
---------- Post added at 02:02 PM ---------- Previous post was at 02:01 PM ----------
I wouldn't do it if it involves updating the bootloader at this time but that is just my opinion and am not a developer just an advanced tinkerer
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
i mean is it really hard lol? can someone give me a link to the guide.

pitbullmommy45245 said:
so should i not do it? lol. mine is unlocked too. i'm using it on cincinnati bell. will this erase the unlock?
Click to expand...
Click to collapse
It is all up to you. I have 4.3 and am happy with it. It is very stable and has decent battery life. It isn't without issues though. I have problems with it giving me the weak wifi signal message or that my Internet is too slow (10Mbps DSL? Slower than some but certainly no slouch) when it does this it disconnects and I have to manually tell it to reconnect. The other thing is in my battery stats built in the rom not all of the apps are being logged only things like screen on time, cell standby, wifi, bluetooth, basic phone stuff but none of the apps???
Why I wish I hadn't done it? Because I lost the ability to be able to recover my phone with Odin and the ability to do whatever it is I want to with the bootloaders.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I just want to flash beanstalk 4.4. I depend on wifi. So does WiFi work?
Sent from my SCH-I535 using xda app-developers app

pitbullmommy45245 said:
i mean is it really hard lol? can someone give me a link to the guide.
Click to expand...
Click to collapse
Read the stickys here and in the general section it will have nearly all of the information and tools you need. Then you can get firmware to flash in Odin from http://www.sammobile.com go there register for an account click firmwares in the top bar of the site and search for your phones model number such as mine is SGH-I747 and a Canadian phone or Mexican phone would be SGH-I747M.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

theramsey3 said:
Read the stickys here and in the general section it will have nearly all of the information and tools you need. Then you can get firmware to flash in Odin from http://www.sammobile.com go there register for an account click firmwares in the top bar of the site and search for your phones model number such as mine is SGH-I747 and a Canadian phone or Mexican phone would be SGH-I747M.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
can i root though after i get on 4.3. i was reading and it says don't do it if you want root.

pitbullmommy45245 said:
can i root though after i get on 4.3. i was reading and it says don't do it if you want root.
Click to expand...
Click to collapse
Try these links they might be of some use, I assume you have read the stickys and have a general idea of what you are up against. click below if you're sure you want to do this to your phone.
4.3 ota Rom http://forum.xda-developers.com/showthread.php?t=2387423 Follow the instructions exactly and understand once you do this there is no turning back. You can run different roms but you have to have the 4.3 bootloaders you cannot for any reason EVER download the bootloaders
This will get you root, I had to use method #2 http://forum.xda-developers.com/showthread.php?t=2538991
I take absolutely no responsibility of any bad things that happen if you use the above links. make sure you understand the tasks you are wanting to preform and the risks associated with such, 4.3 has caused MANY HARD BRICKS.

ok i just did this but i think i might of messed up. i did just as the op said and i was at the downgrading part and now my screen is on the samsung screen and just flashing

pitbullmommy45245 said:
ok i just did this but i think i might of messed up. i did just as the op said and i was at the downgrading part and now my screen is on the samsung screen and just flashing
Click to expand...
Click to collapse
Give it a few minutes to try to boot then pull the battery, boot to recovery and do a factory reset. if that doesn't work then flash the odin file again.
When you do get the 4.3 it will take several minutes to boot it will look like its stuck on the boot screen but be patient it will likely boot eventually.

theramsey3 said:
Give it a few minutes to try to boot then pull the battery, boot to recovery and do a factory reset. if that doesn't work then flash the odin file again.
When you do get the 4.3 it will take several minutes to boot it will look like its stuck on the boot screen but be patient it will likely boot eventually.
Click to expand...
Click to collapse
how long does it take? like 10 plus min?

pitbullmommy45245 said:
how long does it take? like 10 plus min?
Click to expand...
Click to collapse
No it shouldnt take ten minutes but 4.3 takes considerably longer than all the roms I have used in the past.
You are still at the stage of flashing 4.1.1 correct? if it didnt boot just reflash it(uncheck the box for auto reboot so you have to pull the battery out after you flash it) then go to recovery and do a factory reset, then reboot the phone, it should boot this time.
You did check to make 100% sure you downloaded the correct 4.1.1 file for the phones model? right?
Don't mean to make anybody sound silly just trying to figure out exactly whay is going on.

theramsey3 said:
No it shouldnt take ten minutes but 4.3 takes considerably longer than all the roms I have used in the past.
You are still at the stage of flashing 4.1.1 correct? if it didnt boot just reflash it(uncheck the box for auto reboot so you have to pull the battery out after you flash it) then go to recovery and do a factory reset, then reboot the phone, it should boot this time.
You did check to make 100% sure you downloaded the correct 4.1.1 file for the phones model? right?
Don't mean to make anybody sound silly just trying to figure out exactly whay is going on.
Click to expand...
Click to collapse
i got passed it. i guess i wasn't patient enough lol. i'm on 4.3 now. now time to try to root and flash beanstalk lol.

pitbullmommy45245 said:
ok i got passed that. i got to the part where you flash 4.3. it was going through the flash then it got to a part where two errors came up in red (i couldn't see what they were it rebooted right after) and then it rebooted but got stuck on the att ball and wouldn't reboot. then i went into recovery and it was all red and blue and the android had a triangle with a red exclimation mark. i just tried to reflash but it keeps doing the same thing. it gets stuck on the att ball.
Click to expand...
Click to collapse
Do you still have custom recovery (Which one do you have) or do you have the stock recovery?
Edit: I see you edited your post after I quoted you to respond, glad you got it going, now just follow the guides as written for root, I had to use method #2, but you should try method 1 first.
Good luck

Related

Upgrading to T-Mobile 4.3 via OTA

Just checked for updates as described in other threads and it found the latest 4.3 update. I have read both positive and negative responses to the update. Some found things they used in 4.1.2 that are being taken away. Some like the new features in 4.3. It will vary from person to person whether the ROM is better for them or not. Fact is, all devices (current and future) are moving forward.
Should I just install the update? Should I make a copy of my current setup with one of the recoveries, then odin back, and run triangle away?
Strange. I went ahead and updated. Even after doing two complete resets, I still have SU app from 4.1.2. I guess it carried the program during the upgrade process?
apicia said:
Strange. I went ahead and updated. Even after doing two complete resets, I still have SU app from 4.1.2. I guess it carried the program during the upgrade process?
Click to expand...
Click to collapse
it basically dirty flashed the new update over your 4.1.2. I honestly didn't care much about the KNOX boot loader since my warranty is already over. but, I find not having to flash devil kernel so much easier w/ less lag.
Sent from my SGH-T889 using xda app-developers app
youStolemylaptop said:
it basically dirty flashed the new update over your 4.1.2. I honestly didn't care much about the KNOX boot loader since my warranty is already over. but, I find not having to flash devil kernel so much easier w/ less lag.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Hopefully someone will develop something that resets the KNOX counter. Triangle worked for 4.1.2, but does not work in 4.3 for me.
BTW, what 4.3 ROMs do you like, since we have the new bootloader? I just installed TWRP and trying to decide on a ROM.
apicia said:
Hopefully someone will develop something that resets the KNOX counter. Triangle worked for 4.1.2, but does not work in 4.3 for me.
BTW, what 4.3 ROMs do you like, since we have the new bootloader? I just installed TWRP and trying to decide on a ROM.
Click to expand...
Click to collapse
Me, personally, I did like JediMasterX till' I ran into a bunch of problems. so I went to the At&T forum. & I downloaded DN3. Its an amazing ROM & the features are just spectacular.
Sent from my SGH-T889 using xda app-developers app
youStolemylaptop said:
Me, personally, I did like JediMasterX till' I ran into a bunch of problems. so I went to the At&T forum. & I downloaded DN3. Its an amazing ROM & the features are just spectacular.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Works on our T-Mobile without issue? I don't need Wifi calling.
apicia said:
Works on our T-Mobile without issue? I don't need Wifi calling.
Click to expand...
Click to collapse
exactly why I didn't care much for the T-Mobile ROMs. it works spectacular. w/ the new boot loader you won't have to flash devil kernel to get WiFi working. and there's no data drops. + we get the N3 features.
Sent from my SGH-T889 using xda app-developers app
youStolemylaptop said:
exactly why I didn't care much for the T-Mobile ROMs. it works spectacular. w/ the new boot loader you won't have to flash devil kernel to get WiFi working. and there's no data drops. + we get the N3 features.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Which of the three versions did you use? LTE edition?
youStolemylaptop said:
exactly why I didn't care much for the T-Mobile ROMs. it works spectacular. w/ the new boot loader you won't have to flash devil kernel to get WiFi working. and there's no data drops. + we get the N3 features.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Can you please give us the link to the Rom you are using?
Sent from my SGH-T889 using xda premium
I am installing DN3 and am in their installer. It asks me whether I want the N7105 version... or the i317 or i317M. I read to install the ATT version, but what's the difference in the M and non-M version?
So I have a question I hqvent been on in a while and last I checked the newest update came with a locked bootloader. I know it did for the s3. I liked the newest software on the s3 but I jus5 cant stand all that bloat and not having full control of my phone. That s3 was killing me. I just got my note2 back from samsung with a nice new screen and of coure they forgot to send the spen with it. Not that I use the stupid thing anyway but still come on. Anyway is the bootloader locked on this one also and how hard is that to get around?
apicia said:
I am installing DN3 and am in their installer. It asks me whether I want the N7105 version... or the i317 or i317M. I read to install the ATT version, but what's the difference in the M and non-M version?
Click to expand...
Click to collapse
theyre for different companies i believe. as how ours (T889) also has a T889v ( i think thats the right letter) version as its for a different conpany. I installed using the ATT one. there's really no difference because you're just going to flash a tmobile modem over it.
premiatul said:
Can you please give us the link to the Rom you are using?
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2541860
mojorisin7178 said:
So I have a question I hqvent been on in a while and last I checked the newest update came with a locked bootloader. I know it did for the s3. I liked the newest software on the s3 but I jus5 cant stand all that bloat and not having full control of my phone. That s3 was killing me. I just got my note2 back from samsung with a nice new screen and of coure they forgot to send the spen with it. Not that I use the stupid thing anyway but still come on. Anyway is the bootloader locked on this one also and how hard is that to get around?
Click to expand...
Click to collapse
yes the boot loader is locked. I don't believe there's a workaround it yet. but I'm even sure. you can scroll around through the threads and see if there is. what I did was just update it anyways and tripped my KNOX boot loader to ox1. I didn't have warranty anyways so I'm not tripping over it. and then I just rooted it, flashed cwm and started to flash ROMs.
Sent from my SGH-T889 using xda app-developers app
Thank you. So is the root process the same? Usually i flash twrp with odin then install su permissions then I flash away. Or do I have to use another method? Really all I want is the modem software so I could just wait till someone pulls it out they usually do. I always liked c heckin out the latest stock rom but always changed back to aokp.
mojorisin7178 said:
Thank you. So is the root process the same? Usually i flash twrp with odin then install su permissions then I flash away. Or do I have to use another method? Really all I want is the modem software so I could just wait till someone pulls it out they usually do. I always liked c heckin out the latest stock rom but always changed back to aokp.
Click to expand...
Click to collapse
I wrote instructions on how I rooted. there could be other methods to. this is easiest for me! http://forum.xda-developers.com/showthread.php?t=2562994
if you're going to end up on aokp, you should just stay on the 4.1.2 boot loader. the update to me is really only for TW roms because the stock ROMs are working just fine w/o the new boot loader.
Sent from my SGH-T889 using xda app-developers app

I guess my Note 2 is bricked?

Well I give up... I have finally done something that I can not fix. I can normally google and find my own answers and I never have to ask anyone but this time is different.
I have the I317 Note 2, Everything was fine, I was running a stock rom earlier this week and the phone started acting funny. So I though screw it, Ill just go back to stock. So i downloaded.KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar and used Odin to flash the stock firmware. I DID do a full wipe before I went back to stock. It worked fine for 2 days. It kept wanting to download an update. So it did. When it restarted from the update that the phone downloaded it got stuck on the Samsung screen.
I thought no big deal, I will just reflash the stock firmware and start again... FAIL same thing happened. It wont get past the Samsung screen even after leaving it on that screen for a hour. So then I tried to get into recovery... it wont let me.Then I reinstalled the stock rom and waited for boot, then I flashed CWM and tried to get in to recovery that way. No luck.
I feel like I need to do a wipe and start all over but I cant figure out how to do a full wipe without recovery. There has got to be something easy that I am missing but I cant figure it out. I will keep on searching with hope that someone tells me what I am doing wrong or what to do.
THANKS
If its still able to go into download mode and odin recognizes the device your good just be patient and download the correct firmware.
Sent from my SAMSUNG-SGH-I317 using xda premium
There are some issues with the OTA update from LJ2 to MH3, which it appears you still have sitting on your phone. You can try booting recovery and clearing cache - that should get rid of the OTA file.
The thread below has some information on how to update from LJ2 up through MH3 and then MK6. It's intended for those who already have the MK6 bootloader - if you don't already have that or want that, you'll want to stop at MH3 and consider your options.
http://forum.xda-developers.com/showthread.php?t=2618447
Do you know did I use the correct firmware? I have had to run Odin a couple of times before but its a no go this time... I can not get into recovery. Even if I run Odin now with TWRP and restart it still wont let me into recovery... Can I use Odin to to a full wipe?
Were you on 4.3 previously? Via OTA?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
yes I did upgrade to 4.3 when it came available then I went to a custom rom. Then full wiped and downloaded what I thought was a stock rom and here I am.
Are you saying I need to download the 4.3 stock firmware and that is my issue. What i downloaded was from September 2013
For a (hopefully) quick solution, see post #2 here, specifically the param/tz file:
http://forum.xda-developers.com/showthread.php?t=2618447
That should get your access to recovery back and allow the mh3 ota to complete.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Trust in Odin it never fails.
Sent from my SAMSUNG-SGH-I317 using xda premium
Zen Arcade said:
For a (hopefully) quick solution, see post #2 here, specifically the param/tz file:
http://forum.xda-developers.com/showthread.php?t=2618447
That should get your access to recovery back and allow the mh3 ota to complete.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
WOW that worked!! I just got my phone into Recovery for the first time in over 24hrs now! I did a full wipe and now I am going to try and reinstall the factory rom that I have. Unless you tell me something different...
Thank you very much, I dont understand it but so happy to have a different screen!
Which factory rom? Where are you ultimately looking to get to?
100% back up and running! Thank you again
Zen Arcade said:
Which factory rom? Where are you ultimately looking to get to?
Click to expand...
Click to collapse
One that would work.... LOL I really dont have a preference other then I did not care for 4.3 I ended up with 4.1.1 and I couldn't be more happy. If they ever get 4.4 I would try that.
Its funny 4yrs ago I had the Sprint Evo. I changed roms more often then I changed shirts it seamed. I never had the issues or anything like what I ran into yesterday. I was so careless just trying every rom that was released. Because of that I will always remember the EVO as my favorite phone.
Those were simpler times...
I assume you want root and know how to get it.
Since you have the mk6 bootloader you will need to avoid odin flashing any packages that contain bootloaders in the future. See my mk6 thread for details.
If you want to get to 4.1.2 there are rooted cwm packages for ma4, mc3, and mh3 available. Wherever you end up, I recommend freezing the AT&T Software Update apk from within Titanium Backup or equivalent to ensure that you don't get a forced ota update at some point in the future.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Can't Unbrick My T-Mobile Galaxy S4

Hello there, I'm stuck here with what seems to be an unbrickable TMO Galaxy S4. I've tried just aboout everything under the sun and it's still stuck in bootloop. Heres a list of things I've tried and hopefully someone and help me get this thiing up and running soon.
1. Factory Reset, then flash the MDL firmware thru odin. It passed, restarted then finishing installing in the stock recovery. Went to the Samsung Galaxy S4 screen, blacked out then rebooted = FAIL!
2. Install a custom recovery, wiped the entire phone(formatted data, wiped system, data, cache, internal, dalvik cache and did an factory reset. Then flashed Darth Stalker X1. It tried booting the first go then the screen went haywire and the phone got incredibly hot. pulled battery and it booted all the way up and a few hours later back to bootlooping but now that last fix doesn't work anymore. FAIL!
3.Updated to the MK2 firmware, wiped everything again, tried booting. Still bootloop. Installed Custom recovery Wiped everything and tried 2 different roms 1 including the X1 from before. Still Bootloop. FAIL!
4. Now I've updated to the lastest firmware, NB4. Downloaded and flashed NB4 roms like Insane Kit Kat V9 and more. Still the same results. Only time I even got a glimpse at a boot animation is when I flashed a CM based rom but its still bootlooping. FAIL!
I'm so lost on what to do next, I just need some guidance to get me on the right track to success. Please anyone who knows anything help me.
Here's some pictures of the phone
Flash back to latest stock using Kies.
Teknodad1974 said:
Flash back to latest stock using Kies.
Click to expand...
Click to collapse
Can you help me in doing that? I clicked on Firmware upgrade and intialization but now its asking for the info on the back of the phone which is not there.. Now what?
donutkidd said:
Can you help me in doing that? I clicked on Firmware upgrade and intialization but now its asking for the info on the back of the phone which is not there.. Now what?
Click to expand...
Click to collapse
If you can't do it through kies just use Odin. The official nb4 firmware doesn't work but Fenny fixed it. Go to the link provided and download his fixed nb4 full firmware and flash it. Uncheck auto reboot, once done pull the battery and boot in recovery and do a factory reset and wipe cache and dalvik. Post your results. http://forum.xda-developers.com/showthread.php?p=52924856
Sent from my SGH-M919
donutkidd said:
Here's some pictures of the phone
Click to expand...
Click to collapse
Looks like you've done quite a bit to fix this problem, but I'll throw in a few suggestions. May not work, but it won't hurt. Some of this might seem redundant, but who knows; it might help.
First, because KNOX has already been tripped, I'd try to flash a non-TouchWiz ROM via recovery. Once you've flashed CM11 or whatever you choose, I'd grab the charging cable that came with the phone and flash the NB4 firmware via Odin. (The reason for flashing a non-TW ROM then restoring to the factory image is that I've always encountered problems when restoring the stock image from a TW ROM like still having user data intact and other odd stuff. Flashing non-TW guarantees everything is gone.)
If you can't boot from that I'd try to manually update your modem to NB4. I know it should have flashed via Odin you updated to NB4, but I've noticed that sometimes the modem doesn't update when flashing the factory firmware in Odin. I've never updated my bootloader past MDL; just custom recovery and updated modem/baseband) and when using Odin to restore back to MDL, my modem will still say NB4. It wouldn't really cause a problem with MDL bootloader and a newer modem, but I could see how there could be a conflict if you still have the MDL modem and newer bootloader.
Good luck.
mrzhadow said:
If you can't do it through kies just use Odin. The official nb4 firmware doesn't work but Fenny fixed it. Go to the link provided and download his fixed nb4 full firmware and flash it. Uncheck auto reboot, once done pull the battery and boot in recovery and do a factory reset and wipe cache and dalvik. Post your results. http://forum.xda-developers.com/showthread.php?p=52924856
Sent from my SGH-M919
Click to expand...
Click to collapse
Okay flashing now..
mrzhadow said:
If you can't do it through kies just use Odin. The official nb4 firmware doesn't work but Fenny fixed it. Go to the link provided and download his fixed nb4 full firmware and flash it. Uncheck auto reboot, once done pull the battery and boot in recovery and do a factory reset and wipe cache and dalvik. Post your results. http://forum.xda-developers.com/showthread.php?p=52924856
Sent from my SGH-M919
Click to expand...
Click to collapse
lordcheeto03 said:
Looks like you've done quite a bit to fix this problem, but I'll throw in a few suggestions. May not work, but it won't hurt. Some of this might seem redundant, but who knows; it might help.
First, because KNOX has already been tripped, I'd try to flash a non-TouchWiz ROM via recovery. Once you've flashed CM11 or whatever you choose, I'd grab the charging cable that came with the phone and flash the NB4 firmware via Odin. (The reason for flashing a non-TW ROM then restoring to the factory image is that I've always encountered problems when restoring the stock image from a TW ROM like still having user data intact and other odd stuff. Flashing non-TW guarantees everything is gone.)
If you can't boot from that I'd try to manually update your modem to NB4. I know it should have flashed via Odin you updated to NB4, but I've noticed that sometimes the modem doesn't update when flashing the factory firmware in Odin. I've never updated my bootloader past MDL; just custom recovery and updated modem/baseband) and when using Odin to restore back to MDL, my modem will still say NB4. It wouldn't really cause a problem with MDL bootloader and a newer modem, but I could see how there could be a conflict if you still have the MDL modem and newer bootloader.
Good luck.
Click to expand...
Click to collapse
Okay I've tried both suggestions and I'm still stuck. It has to be something wrong with my system status or something.. Even after erasing everything possible and flashing the fixed NB4 firmware thru odin it still says custom system status but the binaries says Samsung Official. Any suggestions for this??
donutkidd said:
Okay I've tried both suggestions and I'm still stuck. It has to be something wrong with my system status or something.. Even after erasing everything possible and flashing the fixed NB4 firmware thru odin it still says custom system status but the binaries says Samsung Official. Any suggestions for this??
Click to expand...
Click to collapse
Read this http://www.androidayos.com/2014/03/...-s4-m919-t-mobile-unbrick-and-recovery-guide/
Sent from my SGH-M919
mrzhadow said:
Read this http://www.androidayos.com/2014/03/...-s4-m919-t-mobile-unbrick-and-recovery-guide/
Sent from my SGH-M919
Click to expand...
Click to collapse
Smh nothing is working but I'm starting to think the reason why is because it's not officially SGH-M919 since after flashing every official firmware I found from MDL to NB4 and system status still comes up as custom. I will try and flash the m919n in the morning. Good idea or no?
Sent from my SM-G900T using XDA Premium 4 mobile app
donutkidd said:
Smh nothing is working but I'm starting to think the reason why is because it's not officially SGH-M919 since after flashing every official firmware I found from MDL to NB4 and system status still comes up as custom. I will try and flash the m919n in the morning. Good idea or no?
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't realize it wasn't the Sgh-m919! You are correct about flashing the wrong firmware. You first need to figure out which variant your phone is so we can find the correct firmware. My apologies I was under the impression that you had a m919 when you said it was a tmo s4.
Sent from my SGH-M919
mrzhadow said:
I didn't realize it wasn't the Sgh-m919! You are correct about flashing the wrong firmware. You first need to figure out which variant your phone is so we can find the correct firmware. My apologies I was under the impression that you had a m919 when you said it was a tmo s4.
Sent from my SGH-M919
Click to expand...
Click to collapse
Yea that's the thing, I was under the impression it was an m919 as well that's why I posted the pics. When I initially got the phone it had m919 when booting and in the download mode. But after all those testing I'm now assuming that the previous owner change it somehow to show m919 instead of what it really could be. So the question now is what variant this is or how to figure out what it is?
Sent from my SM-G900T using XDA Premium 4 mobile app
donutkidd said:
Yea that's the thing, I was under the impression it was an m919 as well that's why I posted the pics. When I initially got the phone it had m919 when booting and in the download mode. But after all those testing I'm now assuming that the previous owner change it somehow to show m919 instead of what it really could be. So the question now is what variant this is or how to figure out what it is?
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Take the battery cover off and you will see the groove where you are supposed to stick your finger to pry the battery. Look just below it and you will see some numbers. Mine say GM919. What does yours say?
Sent from my SGH-M919
mrzhadow said:
Take the battery cover off and you will see the groove where you are supposed to stick your finger to pry the battery. Look just below it and you will see some numbers. Mine say GM919. What does yours say?
Sent from my SGH-M919
Click to expand...
Click to collapse
This is everything I see there - - > GM919 #6-4 >PC+ABS<
Sent from my SM-G900T using XDA Premium 4 mobile app
donutkidd said:
This is everything I see there - - > GM919 #6-4 >PC+ABS<
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How about the battery? Does it say Near Field Communications under the Samsung logo?
Sent from my SGH-M919
mrzhadow said:
How about the battery? Does it say Near Field Communications under the Samsung logo?
Sent from my SGH-M919
Click to expand...
Click to collapse
Yep says that as well.
Sent from my SM-G900T using XDA Premium 4 mobile app
donutkidd said:
Yep says that as well.
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Usually when you have a clone none Samsung phone all these things would be missing. I'm just going 1 by 1. I think you may have a different carrier phone. But which one!!?
Sent from my SGH-M919
---------- Post added at 08:46 PM ---------- Previous post was at 08:44 PM ----------
Sent from my SGH-M919
mrzhadow said:
Usually when you have a clone none Samsung phone all these things would be missing. I'm just going 1 by 1. I think you may have a different carrier phone. But which one!!?
Sent from my SGH-M919
---------- Post added at 08:46 PM ---------- Previous post was at 08:44 PM ----------
Sent from my SGH-M919
Click to expand...
Click to collapse
You think there's a way to figure thru recovery? Running adb commands or something?
Sent from my SM-G900T using XDA Premium 4 mobile app
donutkidd said:
You think there's a way to figure thru recovery? Running adb commands or something?
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This may be a little easier. I found a site with ask identifying marks for all S4 variants. Take a look and see which one you have. Then we can go from there.
http://www.etradesupply.com/blog/find-models-samsung-galaxy-s4-series-2/
Sent from my SGH-M919
---------- Post added at 08:53 PM ---------- Previous post was at 08:52 PM ----------
mrzhadow said:
This may be a little easier. I found a site with ask identifying marks for all S4 variants. Take a look and see which one you have. Then we can go from there.
http://www.etradesupply.com/blog/find-models-samsung-galaxy-s4-series-2/
Sent from my SGH-M919
Click to expand...
Click to collapse
I'll help you as much as I can!
Sent from my SGH-M919
mrzhadow said:
This may be a little easier. I found a site with ask identifying marks for all S4 variants. Take a look and see which one you have. Then we can go from there.
http://www.etradesupply.com/blog/find-models-samsung-galaxy-s4-series-2/
Sent from my SGH-M919
---------- Post added at 08:53 PM ---------- Previous post was at 08:52 PM ----------
I'll help you as much as I can!
Sent from my SGH-M919
Click to expand...
Click to collapse
Yea I truly appreciate your time also I will send you an little donation later today.
Sent from my SM-G900T using XDA Premium 4 mobile app

[Q] Need Help Unbricking Galaxy Note 2 SGH-I317

I ran into a problem when I tried to root my phone. I had experience rooting before with a Samsung tablet so I was surprised with this problem.
Phone Info:
AT&T Galaxy Note 2 SGH-I317 OTA updated to Android 4.4 before attempting the root
Things didn't go as planned and got hung up during rooting process... Now the phone is stuck with the message about Firmware update
interrupted. I'm not entirely sure how to proceed next and I was hoping to receive some advice from other users who are more experienced
in this area.
I remember reading somewhere that once a device has KitKat 4.4 installed.. you can't use a previous version to restore or something like that.
I hope to have someone respond back to me soon... and please, if you could, give me detailed/step-by-step instructions or advice so I can understand what you mean.. since I'm not an expert in this particular area.
Remember, before the soft-bricking, my phone was running Android 4.4 that was recently installed by AT&T.... so I need a method what works with that.
Yes, I am still able to get into Download Mode...
SBM_from_LA said:
I ran into a problem when I tried to root my phone. I had experience rooting before with a Samsung tablet so I was surprised with this problem.
Phone Info:
AT&T Galaxy Note 2 SGH-I317 OTA updated to Android 4.4 before attempting the root
Things didn't go as planned and got hung up during rooting process... Now the phone is stuck with the message about Firmware update
interrupted. I'm not entirely sure how to proceed next and I was hoping to receive some advice from other users who are more experienced
in this area.
I remember reading somewhere that once a device has KitKat 4.4 installed.. you can't use a previous version to restore or something like that.
I hope to have someone respond back to me soon... and please, if you could, give me detailed/step-by-step instructions or advice so I can understand what you mean.. since I'm not an expert in this particular area.
Remember, before the soft-bricking, my phone was running Android 4.4 that was recently installed by AT&T.... so I need a method what works with that.
Yes, I am still able to get into Download Mode...
Click to expand...
Click to collapse
Try this method to get you back up and running
http://forum.xda-developers.com/showthread.php?t=2618447
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks for the quick reply
Thanks for the recommendation... However, I did come across that posting but it didn't seem to apply to my particular problem.. I'm not running 4.3, but Android 4.4 on my phone... One thing I'm not sure about is... I tried flashing the original 4.1.2 to my phone (followed instructions from another site on resolving soft bricks) and that process failed... I'm not sure if I need to completely start all over with my phone or if 4.4 is still installed...
terpin32 said:
Try this method to get you back up and running
http://forum.xda-developers.com/showthread.php?t=2618447
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
SBM_from_LA said:
Thanks for the recommendation... However, I did come across that posting but it didn't seem to apply to my particular problem.. I'm not running 4.3, but Android 4.4 on my phone... One thing I'm not sure about is... I tried flashing the original 4.1.2 to my phone (followed instructions from another site on resolving soft bricks) and that process failed... I'm not sure if I need to completely start all over with my phone or if 4.4 is still installed...
Click to expand...
Click to collapse
You cant flash 4.1.2 you have to go to 4.1.1 first then go to 4.1.2 idk y just how it is
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 01:13 AM ---------- Previous post was at 01:11 AM ----------
That link is just a way to get the phone back working mine did that after doing an update and the only thing i could do is download mode and i did that and it got me back up and running
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Phone Is Working Now
I just wanted to thank you for the information you supplied to me. I followed the instructions exactly... after it PASSED in Odin, it did do the hang at the Samsung logo... and I was able to get back into Recovery Mode and do the Factory Reset and Reboot. I'm glad I came here.. I learned something new..
Once again... thank you
SBM_from_LA said:
I just wanted to thank you for the information you supplied to me. I followed the instructions exactly... after it PASSED in Odin, it did do the hang at the Samsung logo... and I was able to get back into Recovery Mode and do the Factory Reset and Reboot. I'm glad I came here.. I learned something new..
Once again... thank you
Click to expand...
Click to collapse
Np man anytime
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

[Q] need at&t s3 4.1 debrick image

plz any one help me
.i tried 4.3 at&t s3 debrick image by using this thread http://forum.xda-developers.com/showthread.php?t=2660566
.but it didn't help me out
I suggest using our debrick thread here in this same section.
http://forum.xda-developers.com/showthread.php?t=2549068
Not all bricks are fixable, and if you've ever updated to 4.3 or above, older images will not work.
If you need further help please be as detailed as possible about the device and what happened.
Good Luck!
(If you determine you really do need the 4.1.1 debrick.img and can't find it let me know.)
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
I suggest using our debrick thread here in this same section.
http://forum.xda-developers.com/showthread.php?t=2549068
Not all bricks are fixable, and if you've ever updated to 4.3 or above, older images will not work.
If you need further help please be as detailed as possible about the device and what happened.
Good Luck!
(If you determine you really do need the 4.1.1 debrick.img and can't find it let me know.)
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
i detailed what i did to my at&t Samsung galaxy s3 i747
.my at&t s3 i747 running 4.1.1
.i tried to put 4.3 through Odin(its almost done the work)
.but after finishing work my phone gets automatically rebooted(while android updating)
.and failed by turned off(total dead)
that's what happened.i tried lot of debrick images from 4.1.1 -4.3 of at&t s3 i747
.........but when i used connecting my phone to charger without battery,the red LED blinked
So Odin said PASS and it rebooted? That part is normal. And are you saying that after it rebooted, it said Android is Updating and then it just died?
If i am reading that correctly, I don't know that this debrick method will work for you. It leads me to suspect that there is a deeper hardware problem, possibly with the memory I'm guessing.
It's still worth a try though. From what you described, you are going to need the 4.3 debrick.img though. The 4.1.1 image won't work after flashing 4.3.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
So Odin said PASS and it rebooted? That part is normal. And are you saying that after it rebooted, it said Android is Updating and then it just died?
If i am reading that correctly, I don't know that this debrick method will work for you. It leads me to suspect that there is a deeper hardware problem, possibly with the memory I'm guessing.
It's still worth a try though. From what you described, you are going to need the 4.3 debrick.img though. The 4.1.1 image won't work after flashing 4.3.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
dude its working(from your thread)
.but it didn't work without debrick SD card
.i need help.....And i want my phone to run 4.4.2(on at&t s3 i747).....
And thanks dude your threads are awesome..:good:
harijohn said:
dude its working(from your thread)
.but it didn't work without debrick SD card
.i need help.....And i want my phone to run 4.4.2(on at&t s3 i747).....
And thanks dude your threads are awesome..:good:
Click to expand...
Click to collapse
Ok. So you are able to boot download mode, correct? Let's get it booting on its own for now, we can worry about updating after.
Download the MJB 4.3 firmware from here:
http://forum.xda-developers.com/showthread.php?t=2722660
Extract the .tar.md5 file
Remove the sdcard
Flash the MJB firmware in Odin
Reboot.
If it hangs during boot up, reboot into recovery and factory reset. (This will wipe internal sd unless you flash a custom recovery first).
At this point you should be back up and running normally. Let me know how it goes and Good Luck!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Ok. So you are able to boot download mode, correct? Let's get it booting on its own for now, we can worry about updating after.
Download the MJB 4.3 firmware from here:
http://forum.xda-developers.com/showthread.php?t=2722660
Extract the .tar.md5 file
Remove the sdcard
Flash the MJB firmware in Odin
Reboot.
If it hangs during boot up, reboot into recovery and factory reset. (This will wipe internal sd unless you flash a custom recovery first).
At this point you should be back up and running normally. Let me know how it goes and Good Luck!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
------------------------------------------
dude i put stock s3 4.3 bootloader.
and its working fine without the debrick image SDcard...
what should i have to do after that to get a 4.4.2?
That's awesome news! Glad to hear it's fixed!
You have a couple of options to update from here. If you are with AT&T, got to Software Update in the About Device menu. Might take a day for the ota to become available.
Alternatively, enewman17 has two threads in the General section for updating from MJB to NE4. One will fully update everything to 4.4.2. The other will only update your base firmware, leaving your rom, kernel and recovery as is.
I recommend reading both OP'S and the last few pages of each thread. Then pick which one you want to use.
If you have rooted or flashed anything since debricking your phone, I highly recommend using the one that only updates the base firmware.
If you are still 100% pure stock, either one should work fine. (I do still prefer the base firmware update personally, but either should work ok.)
If you have any questions about them, feel free to ask. And congrats on fixing your device!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
That's awesome news! Glad to hear it's fixed!
You have a couple of options to update from here. If you are with AT&T, got to Software Update in the About Device menu. Might take a day for the ota to become available.
Alternatively, enewman17 has two threads in the General section for updating from MJB to NE4. One will fully update everything to 4.4.2. The other will only update your base firmware, leaving your rom, kernel and recovery as is.
I recommend reading both OP'S and the last few pages of each thread. Then pick which one you want to use.
If you have rooted or flashed anything since debricking your phone, I highly recommend using the one that only updates the base firmware.
If you are still 100% pure stock, either one should work fine. (I do still prefer the base firmware update personally, but either should work ok.)
If you have any questions about them, feel free to ask. And congrats on fixing your device!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
==============================================
dude thanks i had updated my phone to 4.4.2
:good::good::good::good:
if any updates to 4.4.4 please let me know dude
*************************************************************
and once again thanks bud
:laugh:

Categories

Resources