I have a problem with a galaxy s3. the main problem with the phone was that it would not boot up to home screen and cant go to recovery mode. I tried odin flash 4.3 but it wouldnt work saying no pit file so what i did was i try looking for one but couldnt so i use the 4.3 debrick sd file and got it stuck upgrade firmware emergency. i tried to take a pit from another S3 and still no good now i try the SD debrick again and use odin to flash 4.3. when i turn on the phone with the SD card this what happen does anyone know what cause and how to fix.
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS
BOOT RECOVERY
WRITE 159488 sectors
FLASH WRITE FAILURE
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: NONE
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
bootloader ap swrey: 1
What caused it to stop booting to begin with?
Are you trying to flash the NC2 build? (Latest 4.3)?
Did you try PIT files from our thread in the General section? If not where did the one you used come from?
Have you recently flashed or changed anything?
Are you able to get download mode without the SD?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
What caused it to stop booting to begin with?
Are you trying to flash the NC2 build? (Latest 4.3)?
Did you try PIT files from our thread in the General section? If not where did the one you used come from?
Have you recently flashed or changed anything?
Are you able to get download mode without the SD?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
my customer bring the phone here to get repair the problem was that it would be not boot up to the home screen it would get stuck at galaxy logo and reboot. I been doing basic flashing for a long time so the 1st thing i did was doing a hard reset and coudlnt get into recovery mode so I try to flashed it with odin since i don't know what android is on i just did a flash for the newest 4.3 which it didnt work it get stuck at nand write so I try different Tar file like T989UVMC6,LJ4,LH2,MJC none of them is working. I try using a 4.3 debrick sd card and it turn on, but it got stuck at upgrade firmware emergency and asking for the pit file. I try download different pit file for t999 on XDA and none of them work. I try again with the debrick SD card and try to flash it with NC3 afterward it wont boot and show that error in the 1st post.
Jimmyyy09 said:
my customer bring the phone here to get repair the problem was that it would be not boot up to the home screen it would get stuck at galaxy logo and reboot. I been doing basic flashing for a long time so the 1st thing i did was doing a hard reset and coudlnt get into recovery mode so I try to flashed it with odin since i don't know what android is on i just did a flash for the newest 4.3 which it didnt work it get stuck at nand write so I try different Tar file like T989UVMC6,LJ4,LH2,MJC none of them is working. I try using a 4.3 debrick sd card and it turn on, but it got stuck at upgrade firmware emergency and asking for the pit file. I try download different pit file for t999 on XDA and none of them work. I try again with the debrick SD card and try to flash it with NC3 afterward it wont boot and show that error in the 1st post.
Click to expand...
Click to collapse
If you get this fixed, let me know how. I have a similar issue with the phone I got on craigslist, except I can get i to ODIN through a USB jumper. It won't go into recovery or ODIN mode through keyboard combos. It was upgraded to 4.3 previously, so I can only flash 4.3+. I've tried following firmwares:
T999UVUENC2_T999TMBENC2_TMB
T999UVUEMJC_T999TMBEMJC_TMB
Initially it was loading user profile, which was locked, so I figured, I will use "erase NAND" option from ODIN to reset (since I couldn't go into recovery). Now it only loads past t-mobile 4g logo into "SAMSUNG" screen, but doesn't go past that. I wonder what can be done, if I could make it go recovery via ODIN or something like that
Jimmyyy09 said:
my customer bring the phone here to get repair the problem was that it would be not boot up to the home screen it would get stuck at galaxy logo and reboot. I been doing basic flashing for a long time so the 1st thing i did was doing a hard reset and coudlnt get into recovery mode so I try to flashed it with odin since i don't know what android is on i just did a flash for the newest 4.3 which it didnt work it get stuck at nand write so I try different Tar file like T989UVMC6,LJ4,LH2,MJC none of them is working. I try using a 4.3 debrick sd card and it turn on, but it got stuck at upgrade firmware emergency and asking for the pit file. I try download different pit file for t999 on XDA and none of them work. I try again with the debrick SD card and try to flash it with NC3 afterward it wont boot and show that error in the 1st post.
Click to expand...
Click to collapse
Ok, first thing, never try to flash anything not specifically intended for the model device you're working with.
Odin should prevent it, but otherwise it'd probably be a major hard brick.
Before anything else, take out the battery and out it back in. If it tries to turn on by itself, its a bad power button.
Check with your customer first, but you could try flashing twrp or cwm recovery with Odin, then try to boot recovery and factory reset.
If the device tries to turn on at all, the debrick sdcard method probably won't work. But try to flash NC2 firmware with Odin again, and if it fails, copy the text from Odin here.
galets said:
If you get this fixed, let me know how. I have a similar issue with the phone I got on craigslist, except I can get i to ODIN through a USB jumper. It won't go into recovery or ODIN mode through keyboard combos. It was upgraded to 4.3 previously, so I can only flash 4.3+. I've tried following firmwares:
T999UVUENC2_T999TMBENC2_TMB
T999UVUEMJC_T999TMBEMJC_TMB
Initially it was loading user profile, which was locked, so I figured, I will use "erase NAND" option from ODIN to reset (since I couldn't go into recovery). Now it only loads past t-mobile 4g logo into "SAMSUNG" screen, but doesn't go past that. I wonder what can be done, if I could make it go recovery via ODIN or something like that
Click to expand...
Click to collapse
Two things you can try. Flash with Odin again, but check the re-partition box.
Or flash twrp or cwm with odin, then try to boot recovery and factory reset.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
Two things you can try. Flash with Odin again, but check the re-partition box.
Or flash twrp or cwm with odin, then try to boot recovery and factory reset.
Click to expand...
Click to collapse
Yeah, I think repartition is the last thing I have not done. Flash twrp and cwm already tried, does not work.
Talking about repartitioninig, is there a repository of PIT files? I found a few threads where PITs are mentioned, but in each one the links are broken. This is 16Gb T999 I am looking for
You may not need it if Odin can read it from your device. But otherwise there's a thread with all pit files in General. Look over last few pages for my links.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
my mistake i wrote it wrong last night since it was closing time. i meant NC2 not NC3. here is some screen shot.
I can only boot the phone up with the SD debrick card without it i cant boot and each time it only show this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is what happen when i flash with odin
I try T-flash and this what happen
I'm afraid things aren't looking too good. In my experience, when all of this happens it usually turns out the memory had gone bad. Probably just from use and age. It is a fairly rare thing, but I have been seeing things like this more and more often the last couple of months.
If you have the ability, you could try JTAG, but I doubt it would give much different results.
It is possible to replace the memory on the motherboard, but its not something I'd recommend. The best option IMO is to buy a used device with broken screen, but good motherboard and imei off of eBay! Then swap the motherboard.
Since it's a customers device though, its up to them, but since you said before it would get to the logo screen, and now it does nothing, keep the sdcard handy so you can show them that you didn't make things worse, it was just dying to begin with.
Unless someone else here has another idea, I don't think there's much else you can do.
Sorry I couldn't help more...
Sent from my SAMSUNG-SGH-T999 using Tapatalk
I am somewhat experienced with Samsung phone since i use one myself and i repair a lot of software issues. I have a feeling after a few flash and it boot up like that with the SD card that memory is damage on the phone. I'll just explain to my customer . I think when they drop the phone it damage the memory. thank you. I do hope someone find a fix soon for the feature.
galets said:
Yeah, I think repartition is the last thing I have not done. Flash twrp and cwm already tried, does not work.
Talking about repartitioninig, is there a repository of PIT files? I found a few threads where PITs are mentioned, but in each one the links are broken. This is 16Gb T999 I am looking for
Click to expand...
Click to collapse
I figured out what was my problem with this phone. The Up/down buttons are not working.
Related
Pre-tense/irrelevant to problem:I was having issues with being able to hear calls (never had a problem with the pacman rom for the longest time) so I flash to another rom and then I got no reception period so, I flashed to stock rom to attempt to take it back to the store to which I learned my warranty experienced two months ago. some where in the process of being frustrated I ended up bricking it.
THE PROBLEM: My phone is soft brick/stuck in the loading screen/big text of SAMSUNG with a loading bar that fills up but, never ends up booting. I know my way around Odin since I did root her but, I'm having an issue just installing the stock rom again to get her working to a certain degree (I will trouble shoot my call issue once this is figured out) I referred too http://forum.xda-developers.com/showthread.php?t=1513359 to get the stock on it once again and the odin gave me a failed message. (with the others, that I have tired and can't reference since my mind is mush because of mid terms did succeed to download but, simple returned me to the problem of be stuck on the boot screen) I can probably figure it out if give enough time to work on it but, with school grinding on my brain I simply don't have the time (I really should be studying right now instead of typing this out) If you could point me to a link that contains the file to fix my problem I would be very happy.
p.s. if you didn't read the pre-tense I got soft bricked in my stock rom so no, I can't boot into recovery.)
also, thanks for navigating my typing/spelling as I am half asleep and my head hurts from 7 hours of study today. if you need more info on the problem just let me know.
sliding bandit said:
Pre-tense/irrelevant to problem:I was having issues with being able to hear calls (never had a problem with the pacman rom for the longest time) so I flash to another rom and then I got no reception period so, I flashed to stock rom to attempt to take it back to the store to which I learned my warranty experienced two months ago. some where in the process of being frustrated I ended up bricking it.
THE PROBLEM: My phone is soft brick/stuck in the loading screen/big text of SAMSUNG with a loading bar that fills up but, never ends up booting. I know my way around Odin since I did root her but, I'm having an issue just installing the stock rom again to get her working to a certain degree (I will trouble shoot my call issue once this is figured out) I referred too http://forum.xda-developers.com/showthread.php?t=1513359 to get the stock on it once again and the odin gave me a failed message. (with the others, that I have tired and can't reference since my mind is mush because of mid terms did succeed to download but, simple returned me to the problem of be stuck on the boot screen) I can probably figure it out if give enough time to work on it but, with school grinding on my brain I simply don't have the time (I really should be studying right now instead of typing this out) If you could point me to a link that contains the file to fix my problem I would be very happy.
p.s. if you didn't read the pre-tense I got soft bricked in my stock rom so no, I can't boot into recovery.)
also, thanks for navigating my typing/spelling as I am half asleep and my head hurts from 7 hours of study today. if you need more info on the problem just let me know.
Click to expand...
Click to collapse
Have you tried booting into recovery?, if not try that by holding both volume up/down and holding power until it vibrates, if able to get into recovery try factory reset (not sure what recovery you were using, so if its stock it would be just an option, if custom recovery then wipe > factory reset.
If you are unable to get into recovery, then I suggest booting to download mode (volume down + power) and flashing TWRP using Odin3 v1.85, depending which ROM (4.12/4.22/4.3 etc) you had last successfully booting, use one of the following links:
4.12, 4.22 Rom use: http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.6.0.0-hercules.tar
4.3 Rom use: http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.6.1.0-hercules.tar
Select PDA in Odin and whichever recovery*.tar you downloaded, once that is flashed reboot into recovery and try wipe > factory reset, then reboot and see if still stuck in boot loop.
If you have trouble flashing the recovery make sure you have the right version of Odin and its a good idea to have the latest USB Drivers which can be found here: http://forum.xda-developers.com/showthread.php?t=2038555
Another thing I noticed is that the link you posted is not actually your stock rom, it can be found here:
Latest Official Koodo Stock 4.1.2 http://forum.xda-developers.com/showthread.php?t=2258338
or Koodo Stock 4.0.4 (scroll down on this page and find Koodo T989D 4.0.4 http://forum.xda-developers.com/showthread.php?t=1858435
It has the stock recovery too, if you want to truly go back to stock to return phone for repairs etc.
Almite said:
Have you tried booting into recovery?, if not try that by holding both volume up/down and holding power until it vibrates, if able to get into recovery try factory reset (not sure what recovery you were using, so if its stock it would be just an option, if custom recovery then wipe > factory reset.
If you are unable to get into recovery, then I suggest booting to download mode (volume down + power) and flashing TWRP using Odin3 v1.85, depending which ROM (4.12/4.22/4.3 etc) you had last successfully booting, use one of the following links:
4.12, 4.22 Rom use: http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.6.0.0-hercules.tar
4.3 Rom use: http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.6.1.0-hercules.tar
Select PDA in Odin and whichever recovery*.tar you downloaded, once that is flashed reboot into recovery and try wipe > factory reset, then reboot and see if still stuck in boot loop.
If you have trouble flashing the recovery make sure you have the right version of Odin and its a good idea to have the latest USB Drivers which can be found here: http://forum.xda-developers.com/showthread.php?t=2038555
Another thing I noticed is that the link you posted is not actually your stock rom, it can be found here:
Latest Official Koodo Stock 4.1.2 http://forum.xda-developers.com/showthread.php?t=2258338
or Koodo Stock 4.0.4 (scroll down on this page and find Koodo T989D 4.0.4 http://forum.xda-developers.com/showthread.php?t=1858435
It has the stock recovery too, if you want to truly go back to stock to return phone for repairs etc.
Click to expand...
Click to collapse
okay, the 4.12, 4.22 rom has given me the hope now to not give up (the "teamwin" with a blue wavy background shows up but disappears to the vibration ever two seconds with the screen off this was the only thing that happened when I tried to boot into recovery before the odin flash, till I release vol up+down, and the power button to which the samsung and loading bar reappears.)
my last successful boot was on this http://forum.xda-developers.com/showthread.php?t=2485228&highlight=telus (I know I'm an idiot for picking a telus stock rom instead of a koodo one but, I wasn't thinking straight.)
also with the me being an idiot thing, I don't think I'm use odin correctly to simply flash a new stock rom (the ones you have listed in particular). I am using it as such: push PDA and select a file (I could select the TWRP and flash it successfully for the 4.12 easy enough) the only box I have checked off is auto reboot. but, with the stock rom's you provided the files are not showing up for me to select. I'm assuming this is me missing a simple step in the process and I would tinker with it till I could select it but, know I'm scared ****less to **** up the little progress I have made.
here is a picture if that was too wordy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and here is a direct link in case that looks as bad in the post as it did in the preview http://i.imgur.com/XKiXJ0h.png?1
but, so far THANKS SO MUCH, any progress in what looked hopeless makes me feel so much better.
sliding bandit said:
okay, the 4.12, 4.22 rom has given me the hope now to not give up (the "teamwin" with a blue wavy background shows up but disappears to the vibration ever two seconds with the screen off this was the only thing that happened when I tried to boot into recovery before the odin flash, till I release vol up+down, and the power button to which the samsung and loading bar reappears.)
my last successful boot was on this http://forum.xda-developers.com/showthread.php?t=2485228&highlight=telus (I know I'm an idiot for picking a telus stock rom instead of a koodo one but, I wasn't thinking straight.)
also with the me being an idiot thing, I don't think I'm use odin correctly to simply flash a new stock rom (the ones you have listed in particular). I am using it as such: push PDA and select a file (I could select the TWRP and flash it successfully for the 4.12 easy enough) the only box I have checked off is auto reboot. but, with the stock rom's you provided the files are not showing up for me to select. I'm assuming this is me missing a simple step in the process and I would tinker with it till I could select it but, know I'm scared ****less to **** up the little progress I have made.
here is a picture if that was too wordy
and here is a direct link in case that looks as bad in the post as it did in the preview http://i.imgur.com/XKiXJ0h.png?1
but, so far THANKS SO MUCH, any progress in what looked hopeless makes me feel so much better.
Click to expand...
Click to collapse
First off you're not a idiot!, the file you originally downloaded should of worked too, for our Jelly Bean roms prior to 4.1.2 we had separate official releases for Koodo 4.0.4 and Telus 4.0.3, once 4.1.2 was released it was only available thru Samsung Kies, until some great folks here on these forums made downloadable roms of the release, so Koodo SGH-T989D and Telus SGH-T989D are both the same rom when it comes to JB 4.1.2, here although is the difference you might of missed, the one you originally downloaded is a flashable ZIP which can only be flashed from recovery(TWRP), the one that I linked is a zip that has to be unpacked and flashed with Odin in Download mode.
So are you now able to get into recovery? btw, sometimes you might need to flash the recovery a couple times for it to actually work, because if you can get into recovery you might just need to do a wipe/factory reset to get phone to boot.
If you really want to flash that rom from my link you just need to unpack it and then go into download mode and use Odin to flash the file.
try flashing stock tar with odin, not just the rom but full stock, radio recovery everything. if you get stuck in a boot loop after flashing stock, go to stock recovery and choose master reset. Should fix your stock boot loop. if it does not work then attempt to flash twrp recovery, if you can get that then you can attempt to flash a rom which might work.
p.s. for issues with reception signal I usually just flash the latest radio after every rom flash, just incase a rom overwrites something necessary.
well, now I tried the TWRP flash (successful everytime) 5 times and after attempting to get into recovery I have had the same results as before.
now that I understand that the roms have to be extracted I attempted that and I got this (i.imgur) fRv6pP2.png (apparently I can't post links now) I attempted at least 3 times and got the same result. Am I doing something wrong? Also is there any other variants of the TWRP recovery you sent me, It seems like it is so close to getting into recovery but, falls short every time. At the moment I'm thinking that getting a recovery (once I'm in recovery I should be out of the woods.) is this phones best chance unless you have any other suggestions.
if the rom is a zip file, it should only be flashed using twrp do not extract roms. If trying to return to stock, it is a tar file you need, it should be flashed using Odin.
for the t989d koodo, with odin you should be flashing this file here for stock, http://www.hotfile.com/dl/203997277/0885f39/T989DTLUMC4_T989DOYBMC4_KDO.zip.html
extract this zip, which would give you a .tar file. Use that .tar file in odin under pda.
sliding bandit said:
well, now I tried the TWRP flash (successful everytime) 5 times and after attempting to get into recovery I have had the same results as before.
now that I understand that the roms have to be extracted I attempted that and I got this (i.imgur) fRv6pP2.png (apparently I can't post links now) I attempted at least 3 times and got the same result. Am I doing something wrong? Also is there any other variants of the TWRP recovery you sent me, It seems like it is so close to getting into recovery but, falls short every time. At the moment I'm thinking that getting a recovery (once I'm in recovery I should be out of the woods.) is this phones best chance unless you have any other suggestions.
Click to expand...
Click to collapse
That rom in the picture of Odin is not the official JB 4.1.2 rom for T989D, it's the T-Mobile T989 rom, which I'm not even sure if it's possible to be flashed onto the T989D.
I'd download the JB 4.1.2 T989D stock rom from either the link I posted or the link the person above this post, they are both the same file, it is the official release for our Koodo, Telus phones.
Another option you could try is to download and install Samsung Kies and see if it can fix the issue, but make sure you try to odin the official rom first, or Kies might not even recognize your phone.
SUCCESS!!! I flashed the odin file that mikeysmith281 posted and the original recovery right after that and I finally got into recovery and now everything is back to normal. thanks so much.
I will be going back to my beloved pac man rom once I get a little breather from my midterms but, in case I have an issue with reception/ the ability to pick up a call I understand now that I simply flash the lastest radio.
p.s. stupid question: are radios device specific or ROM specific? I can't say I look extremely hard for the pacman radios since I didn't quite understand how it could work for the longest time and simply stop working for no reason but, it would make sense why I never found them if they are simply on a per phone basis.
p.p.s once again THANKS SOOOOO MUCH!
sliding bandit said:
SUCCESS!!! I flashed the odin file that mikeysmith281 posted and the original recovery right after that and I finally got into recovery and now everything is back to normal. thanks so much.
I will be going back to my beloved pac man rom once I get a little breather from my midterms but, in case I have an issue with reception/ the ability to pick up a call I understand now that I simply flash the lastest radio.
p.s. stupid question: are radios device specific or ROM specific? I can't say I look extremely hard for the pacman radios since I didn't quite understand how it could work for the longest time and simply stop working for no reason but, it would make sense why I never found them if they are simply on a per phone basis.
p.p.s once again THANKS SOOOOO MUCH!
Click to expand...
Click to collapse
Good to hear!, as far as radios for our phone, there is only 2 possible radios that can be used if running a JB 4.1.2 or newer based rom, the radio is flashed from recovery, pretty sure that for Canada the Telus radio is best, here is a link you might want to bookmark.
http://forum.xda-developers.com/showthread.php?t=1895400
You will be on the Telus radio now since you just flashed stock 4.1.2 rom, if you ever run into issues with radio signal that are not your mobile providers issue, then just reflash the radio.
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
KorGuy123 said:
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
Click to expand...
Click to collapse
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
Larry2999 said:
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
Click to expand...
Click to collapse
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
It's time to start reading. Before doing any flashing/modding, you should make sure you understand what you're doing and know the risks.
Now as for Odin, it's quite straight forward. Phone needs to be in download mode, you put the PDA file in Odin and flash (if it's a Odin one-click, just need to hit start). One thing is to not interrupt it! Especially if flashing bootloaders cause that will brick your phone. Also, don't downgrade bootloaders.
There are a few guides in the sticky, I suggest you take an hour or two reading them so things like that don't happen again (or that you know what to do if it does).
GL!
baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
Alright. If wipe/reset didn't work, you'll need to restore full stock 4.3 via custom recovery. Here's what we need to do....
1) Download the Odin flashable *.Tar file for custom recovery. I prefer TWRP because of the GUI so that's where I'm pointing you to ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore file for 4.3 from the thread below... If you are using TWRP, then the first link is the one you need
http://forum.xda-developers.com/showthread.php?t=2658486
3) Copy the stock restore zip file to a good quality (micro) SD card
4) I presume you have Odin already so you will use this to flash custom recovery to your phone. Run Odin.exe on your PC. If you are using Odin v.3.09 then you need the AP tab. For all other versions, use the PDA tab. Navigate to the custom recovery *.Tar file you downloaded earlier and place this in the PDA (or AP tab). Leave the default settings as is and do not check/uncheck any boxes other than the default settings.
5) Boot the phone to download mode via the 3-button combo (Volume Down/Home/Power). When you get to Odin (Download) mode, press volume up to continue. Connect the phone to your PC with a good quality micro USB cable. Wait until Odin has recognized the device then click on the Start button to start firmware installation (flashing). Wait for the flashing to end and the <Pass> message. Disconnect the phone from the PC and pull the battery to stop auto reboot.
6) Place the micro SD card with the stock restore zip in your phone. Replace the battery and boot to recovery mode. If you were successful with the firmware flashing above, it should boot you to custom recovery.
7) Select install from external card and navigate to the stock restore zip file. Select this file and swipe the screen to start firmware installation. Wait for installation to complete. Then clear your cache/dalvik and reboot to system.
This will hopefully do it.
I've seen this asked a lot. People try and flash the new modem and/or bootloader on their rooted devices, and neither stick. Why?
The Note 3 bootloader is programmed in such a way that it will refuse to accept a new modem if the binary is marked as CUSTOM instead of SAMSUNG OFFICIAL in the bootloader. The thing that the bootloader checks for is the kernel. Meaning the kernel you have to have in order to flash the modem is the stock one. However, we're all pretty much already on custom ROMs with custom kernels, so it says custom even if you flash back the stock kernel.
How to flash a new modem and/or bootloader:
1. Flash the stock kernel via ODIN or some other method
2. Download and run Triangle Away
3. The phone will shut off after running the app. Reboot into Recovery mode normally (Hold Volume Up + Home after you feel the initial vibration)
4. When the Triangle Away menu comes up, hit Volume Up to reset the phone to "OFFICIAL" (nothing is erased or modified except for that, don't worry).
5. Press Volume Down to go straight to Download mode. You'll see it says SAMSUNG OFFICIAL next to System Binary.
6. You can ODIN over the modem.bin and/or the bootloader file (both in one shot works) now, or you can use Mobile Odin just for the modem file if you have it/want to. ODIN's easier.
I just did this. It's my second time updating a modem on this phone. It worked the last time and it worked this time.
Proof (the last two are my custom ROM, which is NF1 based. So ignore those):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Product F(RED) said:
I've seen this asked a lot. People try and flash the new modem and/or bootloader on their rooted devices, and neither stick. Why?
The Note 3 bootloader is programmed in such a way that it will refuse to accept a new modem if the binary is marked as CUSTOM instead of SAMSUNG OFFICIAL in the bootloader. The thing that the bootloader checks for is the kernel. Meaning the kernel you have to have in order to flash the modem is the stock one. However, we're all pretty much already on custom ROMs with custom kernels, so it says custom even if you flash back the stock kernel.
How to flash a new modem and/or bootloader:
1. Flash the stock kernel via ODIN or some other method
2. Download and run Triangle Away
3. The phone will shut off after running the app. Reboot into Recovery mode normally (Volume Up + Home after you feel the initial vibration)
4. When the Triangle Away menu comes up, hit Volume Up to reset the phone to "OFFICIAL" (nothing is erased or modified except for that, don't worry).
5. Press Volume Down to go straight to Download mode. You'll see it says SAMSUNG OFFICIAL next to System Binary.
6. You can ODIN over the modem.bin and/or the bootloader file (both in one shot works) now, or you can use Mobile Odin just for the modem file if you have it/want to. ODIN's easier.
I just did this. It's my second time updating a modem on this phone. It worked the last time and it worked this time.
Proof (the last two are my custom ROM, which is NF1 based. So ignore those):
Click to expand...
Click to collapse
So what you are saying is that what I have done with my phone for the last 3 new firmwares shouldn't be possible.
I have been on CM11(temasek's version) for about 8 months, and I have upgraded my modem and bootloader only, never flashing the full firmware, and never using Triangle away.
I always turn my phone completely off, take battery out, put battery in, use three button combo to enter download mode, plug phone into computer and odin flash JUST the modem and bootloader, reboot my phone, and BOOM, profit!
You can't odin flash the modem and bootloader and get them to stick if you use the OS or a reboot application to enter download mode. Theory has been proven, and it is this way on the S5 also.
Your theory is just that...a theory.
idtheftvictim said:
So what you are saying is that what I have done with my phone for the last 3 new firmwares shouldn't be possible.
I have been on CM11(temasek's version) for about 8 months, and I have upgraded my modem and bootloader only, never flashing the full firmware, and never using Triangle away.
I always turn my phone completely off, take battery out, put battery in, use three button combo to enter download mode, plug phone into computer and odin flash JUST the modem and bootloader, reboot my phone, and BOOM, profit!
You can't odin flash the modem and bootloader and get them to stick if you use the OS or a reboot application to enter download mode. Theory has been proven, and it is this way on the S5 also.
Your theory is just that...a theory.
Click to expand...
Click to collapse
Enough people have had trouble updating their Note 3's after flashing a custom ROM that my theory holds true. Your situation, while interesting, is an outlier.
Also I never said you had to flash the full firmware...
Sent from my SM-N900T using Tapatalk
Product F(RED) said:
Enough people have had trouble updating their Note 3's after flashing a custom ROM that my theory holds true. Your situation, while interesting, is an outlier.
Also I never said you had to flash the full firmware...
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Flashing the full firmware should still work right?
Only when flashing a new modem and/or bootloader is when it may not always stick, right?
Thugnificent69 said:
Flashing the full firmware should still work right?
Only when flashing a new modem and/or bootloader is when it may not always stick, right?
Click to expand...
Click to collapse
If the system binary says "CUSTOM", I believe it's permanent unless you use Triangle Away. So you would need to flash a stock kernel, use Triangle Away, and then flash the full firmware. If you were to just flash the full firmware, the firmware would update, but the bootloader and modem would not.
I believe (emphasis on believe) the reason is that the bootloader flag (CUSTOM when you flash a custom kernel/ROM) is there for security. Meaning, if someone tampered with the phone, there's a good chance something was compromised (in say, a business situation). So Samsung programmed the phone to restrict updating the modem and bootloader (which may have been modified maliciously) in order to preserve any evidence. Again, it seems like a totally farfetched theory, I know. But that's what I think.
The one or two threads I read already expect you to be on a custom rom and have some recovery, when in fact I believe if coming straight from Stock Recovery and Stock Rom, then Stock Recovery WON'T Let you flash a custom recovery...
So how then? Could I just root my LG Optimus G Pro (E980) with maybe TowelRoot and then install from Play Store Flashify and load a custom recovery img off this thread http://forum.xda-developers.com/opt...overy-zip-twrp-2-8-1-0-lg-g-pro-e980-t2967855 and attain getting a custom recovery?
How do I get into Custom recovery, not sure if it took, it said insecure boot and something else after rebooting from flashify do I hold power and volume up or down and home key or?
"Secure booting error
Cause: boot certification verify"
Is what it exactly says...
Finally after playing around some I installed GPRO_Recovery_6.0.4.4.apk and then got CWM to install somehow I noticed moved twrp zip to the innersd card since for some reason cwm didn't wanna go into extsd card and then flashed twrp 2.8.1.0 successfully.
I should retitle this half baked TWRP Semi functionality with ZER0 Community Support. LoL
Is there a flashable zip of CWM and no one still told me how to enter security, I'm now getting a double LG Splash screen and second one just sits and hangs, trying to install either PhilZ recovery with hopes of it detecting my external sd card unlike the half baked TWRP with semi functioning touchscreen drivers.
So again, I know I do or think it's powered off Volume Up and Power button, but how long do I hold in the power button, 3 seconds, 5 seconds, 10 seconds, 15 seconds? Too long and not releasing it just shuts the phone down.
Am I gunna get any help or is this all echoed shots in the dark thrown out aimlessly that nobody GAD to answer and help out?
It's important to me to have a fully functioning recovery, I don't wanna boot into the darn thing just to look at the screen and not do diddly squat with.
To get to the recovery screen with power + volume up button at the same time. There is a version of cwm 6.0.47 that's in flash able zip file, you can get it in the optimus general section. That's the most reliable version, it will not cause you the recovery boot loop. The easiest way is to use freegee if you haven't try it already.
How many fracking times to I gotta boot into TWRP before damned touchscreen decides to work again, jesus christ I wanna murder the dumba55 who released this half baked nonsensical p.o.s. it's bloody b.s. I swear to god!!!
There is a better version of Twrp in the lg optimus g pro original Android development section. It still doesn't read the external SD card thought.
hawkwind212 said:
There is a better version of Twrp in the lg optimus g pro original Android development section. It still doesn't read the external SD card thought.
Click to expand...
Click to collapse
Thanks finally I got a rom to install by copying it to internal storage while booted up in TWRP, used MiUi now to install FreeGee and try to get CWM to install again.
There is a zip file of cwm you can flash from Twrp in the optimus general section if freegee doesn't work out. It's the same version as the freegee 's. However, it's not a touch screen version of cwm, but it will not get you into the recovery boot loop when you open the recovery with power+volume up buttons.
hawkwind212 said:
There is a zip file of cwm you can flash from Twrp in the optimus general section if freegee doesn't work out. It's the same version as the freegee 's. However, it's not a touch screen version of cwm, but it will not get you into the recovery boot loop when you open the recovery with power+volume up buttons.
Click to expand...
Click to collapse
How do we fix the bootloop in PhilZ recovery?
---------- Post added at 12:41 PM ---------- Previous post was at 11:49 AM ----------
Looks like I'm gunna be flashing stock all over, last night I changed my build.prop in CloudyGX_V1.0 cause I thought it needed it, then it wouldn't boot up at all this morning, so I went into PhilZ recovery and reflashed CloudyGX_V1.0 and it successfully installed but wouldn't get out of reocovery bootloop, so I tried flashing this (worksinallrecovery)TWRP-2.6.1.0-E980-LOKIFIED.zip and now it acts as if there's no recovery at all installed and just sits at the one LG splash screen, no double lined white font message or anything, just sits and sits and sits there doing nothing.
Trying this: http://forum.xda-developers.com/showthread.php?t=2302660 and I can't even get it to go into download mode... Guess it's time to take the phone to a repair shop and see what they can do, I don't get it though I just flashed another recovery zip found here file found here: https://docs.google.com/file/d/0BziXHIJy7TsjZ0xqd0RNQWNGV0k/edit in PhilZ and then this started happening, I extracted the recovery zip zipped in together with everything else and then bam.
I did later on realize that half a minute or so after TWRP loads then finally touchscreen starts working, I just wished external sd card would be picked up in it.
Yea, I was going to tell you to flash Twrp to get out of the boot loop or there is a zip file just for getting out of the recovery boot loop. Look on philosophy thread for more info on that. Also, there is suppose be a script that fix the recovery boot loop with the touch version of cwm, but I not sure how well it works, that's why I stay with version 6.0.47. Too bad that Twrp doesn't read the SD card, it looks good though other than that.
hawkwind212 said:
Yea, I was going to tell you to flash Twrp to get out of the boot loop or there is a zip file just for getting out of the recovery boot loop. Look on philosophy thread for more info on that. Also, there is suppose be a script that fix the recovery boot loop with the touch version of cwm, but I not sure how well it works, that's why I stay with version 6.0.47. Too bad that Twrp doesn't read the SD card, it looks good though other than that.
Click to expand...
Click to collapse
Waiting to hear back from the cellphone repair store, I was completely stuck, it wouldn't do anything. So I guess after that hopefully start back at square 1.
Well the cellphone repair store said they ran all the software they could find for the LG Optimus G Pro (E980) and still couldn't get it to come out of the very first LG Splash screen, looks like maybe now it's time to send it in to be JTAG'ed and hope that fixes it.
I'm having a similar issue, after I rooted with Optimus G Pro Manual Root Tool, I used GProRecoveryTool to install cwm. But after I got into CWM I tried the installing this twrp zip and ever since I tried booting I'm greeted with "Secure Booting Error! Cause : boot certification verify". I can't boot into recover nor rom lol. Easy on me though, it's my first LG device
I also just noticed that It's not recommended to install on stock rom....well I did haha
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What next? Someone told me to hold down both volume keys and plug in the phone to my computer and viola I got into download mode...
I'm asking here cause some of the LGFlashTools Tutes are for different models, using I guess LGE980_20130314_LGFLASHv151
Do I just click OK button no need to do anything PRL & SCRIPT and keep UPGRADE DL Checked and USB?
I've got the BIN_LGE980AT-00-V20g-ATT-US-APR-28-2014+0.tot file
Emmanuel U said:
I'm having a similar issue, after I rooted with Optimus G Pro Manual Root Tool, I used GProRecoveryTool to install cwm. But after I got into CWM I tried the installing this twrp zip and ever since I tried booting I'm greeted with "Secure Booting Error! Cause : boot certification verify". I can't boot into recover nor rom lol. Easy on me though, it's my first LG device
I also just noticed that It's not recommended to install on stock rom....well I did haha
Click to expand...
Click to collapse
Usually after that screen custom recovery should load. I'm awaiting further steps to my above posted question.
n1nj4Lo said:
Usually after that screen custom recovery should load. I'm awaiting further steps to my above posted question.
Click to expand...
Click to collapse
I can't boot into recovery or rom, only download lol. I'm gonna be trying this soon.
n1nj4Lo said:
What next? Someone told me to hold down both volume keys and plug in the phone to my computer and viola I got into download mode...
I'm asking here cause some of the LGFlashTools Tutes are for different models, using I guess LGE980_20130314_LGFLASHv151
Do I just click OK button no need to do anything PRL & SCRIPT and keep UPGRADE DL Checked and USB?
I've got the BIN_LGE980AT-00-V20g-ATT-US-APR-28-2014+0.tot file
Click to expand...
Click to collapse
Is that the version you got of the xda ogp forum here? Yes, it's usually with the usb cord plug into your device already, hold down both volume and power buttons at the same time, then plug the other end of cord into your computer. If that doesn't work, some time take out the battery helps. I forget the steps, but follow the soft brick repair guide and you will not go wrong. Also, if you do get it to start flashing, make sure you get a 100% completion, do not interruption the flash process regardless what the guide says.
I just checked my phone with Galaxy Tools and it's showing a different version for the software, baseband, and bootloader.
The ROM is the Sprint Hybrid-X 3.0 COG5...could this cause a problem with the phone not running right?
Software version is COG5
Baseband version is COK1
Bootloader version is COJ6
I need to get everything the same but I can't flash any firmware tar files in ODIN, they all fail.
In recovery my "/system" won't stay mounted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can help you with this. You definitely need to update your bootloader. I'm not sure how you managed to update the kernel to OK1 and not the bootloader. The modem is OK1 and that's fine. It will work on all roms. If you want to continue running my Hybrid-X 3.0 rom you should go ahead start fresh by downloading the latest official samsung OK1 rom tar package. Search the general threads here in the sprint N4 forum to find a link. Once you have that downloaded you need to extract it with 7zip. Inside the extracted folder will be the actual tar file that u will flash in odin. But first you will need to backup anything you need to back up from you sd-card and internal storage. Next, reboot to TWRP recovery and do factory reset a few times then press "advanced wipe options" and wipe all of the partitions except internal storage and micro-sd card. do this two or three times repeatedly. You must do this BEFORE you odin the OK1 tar or else you will have left over data and it will cause problems. So wipe everything FIRST. Once you do this, while you're still in recover, go back to reover home screen and then select reboot and reboot to Download mode. Then launch odin and then connect your phone to your pc & usb cable. Use the AP button and select the tar you extracted earlier. It will verify the md5. Once that finishes then you can start the flash process. When it finishes you will be fully updated to OK1. At that point you should be able to odin TWRP again then the rom of your choice.
Edit: If you can't odin the OK1 tar and it fails then you will need to do this... download the OJ6 tar ball. extract it like usual. Then flash it in odin. If it fails then do this... Open odin. Don't connect your phone yet! click on the "options" tab and check the "re-partition", "auto reboot" and "reset time" options. then flash OJ6 and watch it work. Let you phone boot up completely! Then do the device activation, prl and profile updates in settings BEFORE you flash any other custom rom. This will set you straight.
tx_dbs_tx said:
I can help you with this. You definitely need to update your bootloader. I'm not sure how you managed to update the kernel to OK1 and not the bootloader. The modem is OK1 and that's fine. It will work on all roms. If you want to continue running my Hybrid-X 3.0 rom you should go ahead start fresh by downloading the latest official samsung OK1 rom tar package. Search the general threads here in the sprint N4 forum to find a link. Once you have that downloaded you need to extract it with 7zip. Inside the extracted folder will be the actual tar file that u will flash in odin. But first you will need to backup anything you need to back up from you sd-card and internal storage. Next, reboot to TWRP recovery and do factory reset a few times then press "advanced wipe options" and wipe all of the partitions except internal storage and micro-sd card. do this two or three times repeatedly. You must do this BEFORE you odin the OK1 tar or else you will have left over data and it will cause problems. So wipe everything FIRST. Once you do this, while you're still in recover, go back to reover home screen and then select reboot and reboot to Download mode. Then launch odin and then connect your phone to your pc & usb cable. Use the AP button and select the tar you extracted earlier. It will verify the md5. Once that finishes then you can start the flash process. When it finishes you will be fully updated to OK1. At that point you should be able to odin TWRP again then the rom of your choice.
Edit: If you can't odin the OK1 tar and it fails then you will need to do this... download the OJ6 tar ball. extract it like usual. Then flash it in odin. If it fails then do this... Open odin. Don't connect your phone yet! click on the "options" tab and check the "re-partition", "auto reboot" and "reset time" options. then flash OJ6 and watch it work. Let you phone boot up completely! Then do the device activation, prl and profile updates in settings BEFORE you flash any other custom rom. This will set you straight.
Click to expand...
Click to collapse
lemme explain the whole "situation" real quick---
I flashed the stock rooted deodexed rom a while back, soon as it was posted and it ran perfectly, no reboots, no freezing, not a problem ever.
Last Monday I was charging the phone, it fully charged and I hit the home button and the screen wouldn't lightup/open...first time I ever had this happen on this phone. I yanked the battery, put it back in and it wouldn't boot.
tried to re-flash the rom after factory reset and when it booted i got the MMC Failed/can't do normal boot error.
reflashed the stock frmware in odin and that failed, odin said I need a PIT file...found the PIT file to flash with the unrooted stock firmware, failed in odin.
I managed to restore from TWRP, which worked until I rebooted then got the same "can't do regular boot" error after it booted ...I checked TWRP and the "/system" is unticked and even when I check it to boot it doen't boot and always go back to unticked.
I finally re-installed this rom and it's working now but as you saw above everything is different (firmware, etc.)
I want to get it to where I can at least use it again and at the best revert to unrooted stock to send to samsung for repairs of whatever caused the initial problem since the phone is only 3 months old.
Thanks for the response btw:good:
broad_st_bully said:
lemme explain the whole "situation" real quick---
I flashed the stock rooted deodexed rom a while back, soon as it was posted and it ran perfectly, no reboots, no freezing, not a problem ever.
Last Monday I was charging the phone, it fully charged and I hit the home button and the screen wouldn't lightup/open...first time I ever had this happen on this phone. I yanked the battery, put it back in and it wouldn't boot.
tried to re-flash the rom after factory reset and when it booted i got the MMC Failed/can't do normal boot error.
reflashed the stock frmware in odin and that failed, odin said I need a PIT file...found the PIT file to flash with the unrooted stock firmware, failed in odin.
I managed to restore from TWRP, which worked until I rebooted then got the same "can't do regular boot" error after it booted ...I checked TWRP and the "/system" is unticked and even when I check it to boot it doen't boot and always go back to unticked.
I finally re-installed this rom and it's working now but as you saw above everything is different (firmware, etc.)
I want to get it to where I can at least use it again and at the best revert to unrooted stock to send to samsung for repairs of whatever caused the initial problem since the phone is only 3 months old.
Thanks for the response btw:good:
Click to expand...
Click to collapse
Your phone has a hardware failure. If you have insurance through Sprint, take it in to a Sprint owned store. They won't be able to fix it, and will offer to replace it.
Sent from my SM-N920P using Tapatalk
followed the first set of instructions and it failed, on the phone screen under the odin info it said write fail, no pit file,read fail
LMMT said:
Your phone has a hardware failure. If you have insurance through Sprint, take it in to a Sprint owned store. They won't be able to fix it, and will offer to replace it.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I have full insurance but when i brought it to the store the "tech specialist" saw the "SEANDROIDENFORCING" at the top of the screen and saw it was rooted and blamed the root
broad_st_bully said:
I have full insurance but when i brought it to the store the "tech specialist" saw the "SEANDROIDENFORCING" at the top of the screen and saw it was rooted and blamed the root
Click to expand...
Click to collapse
tinker with the phone and try to get it back to a regular stock firmware. even if it won't boot up. that will get rid of the red and yellow text at boot screen. formatting System may also clear the red and yellow text.
it will still show when booting twrp though.
never take a rooted phone to Sprint lol 98% of their employees either think it's witchcraft or are too afraid of repercussions for servicing a rooted device. the warrantee void the phone refers to is manufacturer warrantee though and has nothing to do with Sprint. it's aggravating.
I agree. it definetely sounds like hardware failure. Do like the previous poster said. Odin the stock OJ6 or OK1 rom and then go back to the sprint store and see what they can do for you. If it's hardware related and you do have TEP "Total Equipment Protection" on your line then they will order you a free replacement. Don't let them bully you into filing an insurance claim. this is not physical damage therefore you DO NOT have to file an insurance claim. They will tell you to file insurance but you have to explain to them that it is not physical damage to the phone and let them know you are a little wiser than that.