Develop Bugs

[Q] Possible bricking. Recovery methods and alternatives?

Much like the others here I rooted my T-mobile galaxy s3. The root worked fine and all. Then I downloaded this font changer app (I forget the name but it required a root) I go on to select a font then I go on to reboot like it said. Then bam, my phone gets stuck on the samsung screen. I then proceeded to use odin to put the stock image back on it (I think that's what it's called) It went through. I also did the factory wipe via the recovery screen. But now my phone would turn on, show "Samsung Galaxy S3," go to a black screen, play the t-mobile jingle, and the only thing that happens is the LED flashes but still nothing on the screen. I've tried virtually everything and I still think there is something else I need to do.
Help please?

I had a similar problem, this is what I did. Try and boot into cwr by hilding the vol up +power+home when it vibrates let go. Now u should b in cwr. Now wipe everything, dalvic, factory wipe fix permission. And flash a new rom cm10 will do..
Sent from my SGH-T999 using xda premium

kipster3001 said:
I had a similar problem, this is what I did. Try and boot into cwr by hilding the vol up +power+home when it vibrates let go. Now u should b in cwr. Now wipe everything, dalvic, factory wipe fix permission. And flash a new rom cm10 will do..
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
The problem is that he may be rooted but doesn't have cwm recovery.
If that's the case then you need to flash cwm recovery first.
I would also try flashing stock rom again or after flashing cwr download nandroid backup of stock rom.
Good luck and let us know if that worked
Sent from my SGH-T999 using xda app-developers app

HajmeR said:
The problem is that he may be rooted but doesn't have cwm recovery.
If that's the case then you need to flash cwm recovery first.
I would also try flashing stock rom again or after flashing cwr download nandroid backup of stock rom.
Good luck and let us know if that worked
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
That sounds like a reasonable solution. Can I get a link to the CWM recovery file as well as a guide to it so I don't dig myself into a deeper hole? lol

Actually if you're stock recovery, factory reset should wipe everything. Including internal sd, just so you know.
If that doesn't work it'd probably be cleaner to just odin the root66 fw. But if you prefer the other way, you can find recovery files at the top of post 2 in the fw thread. Root66 is at the top of post 1.
I still need to add a few recoveries so if you don't see one you want let me know.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Actually if you're stock recovery, factory reset should wipe everything. Including internal sd, just so you know.
If that doesn't work it'd probably be cleaner to just odin the root66 fw. But if you prefer the other way, you can find recovery files at the top of post 2 in the fw thread. Root66 is at the top of post 1.
I still need to add a few recoveries so if you don't see one you want let me know.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
OMG!!! It is working now!!! Thank you so so so much!!!! lol

Hey guys,
Was trying to root my stock T-Mobile Galaxy S3, and everything was going fine but after it rebooted from Odin, the screen stayed black, and only the blue LED was pulsing. I assume it has something to do with my phone being on 4.1.1 and the S3 toolkit not liking that. I tried to flash the stock Rom to get it out of this, but now the same thing is still happening. I have tried multiple cache wipes/factory resets and multiple other stock ROMs. I always without fail get the same thing Samsung splash screen/Blue pulsing LED/start up sound and black screen. I'm getting really frustrated and worried. Can anyone help?

Misfit77 said:
Hey guys,
Was trying to root my stock T-Mobile Galaxy S3, and everything was going fine but after it rebooted from Odin, the screen stayed black, and only the blue LED was pulsing. I assume it has something to do with my phone being on 4.1.1 and the S3 toolkit not liking that. I tried to flash the stock Rom to get it out of this, but now the same thing is still happening. I have tried multiple cache wipes/factory resets and multiple other stock ROMs. I always without fail get the same thing Samsung splash screen/Blue pulsing LED/start up sound and black screen. I'm getting really frustrated and worried. Can anyone help?
Click to expand...
Click to collapse
That's actually the exact problem I just solved. You would need Odin 3.04 (well that's what I used) and you need to flash root66 like one of the previous posters here said. It recovered my phone AND rooted it. So try that and tell us what happened.

treythetree said:
That's actually the exact problem I just solved. You would need Odin 3.04 (well that's what I used) and you need to flash root66 like one of the previous posters here said. It recovered my phone AND rooted it. So try that and tell us what happened.
Click to expand...
Click to collapse
When I try the root66 it fails in odin. I used the root66_TMO_T999UVDLJA one. First, I had toolkit convert it into a .tar. Then I chose option 8 to flash a stock rom. I skipped ahead to flashing the rom and factory reset like it prompted. Then I tried to flash the .tar and it fails. ..:/. I don't know what else to do.

Misfit77 said:
When I try the root66 it fails in odin. I used the root66_TMO_T999UVDLJA one. First, I had toolkit convert it into a .tar. Then I chose option 8 to flash a stock rom. I skipped ahead to flashing the rom and factory reset like it prompted. Then I tried to flash the .tar and it fails. ..:/. I don't know what else to do.
Click to expand...
Click to collapse
Actualy I don't use toolkit so I might be wrong, but I don't think you need to convert root66 to tar. Just skip the toolkit. Put your phone into download mode, open odin, connect your phone to pc and flash root66. Check root66 thread for some info about unziping it or converting to anything. All info should be in op. If there is nothing about it then flash it as it is. Make sure that you have phone drivers installed and turn off kies.
I hope it helps.
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 07:05 PM ---------- Previous post was at 06:49 PM ----------
I've just checked root66 thread. You don't have to convert it or unzip it. Just flash as it is. Your problem might came from converting that file to tar.
Sent from my SGH-T999 using xda app-developers app

Misfit77 said:
When I try the root66 it fails in odin. I used the root66_TMO_T999UVDLJA one. First, I had toolkit convert it into a .tar. Then I chose option 8 to flash a stock rom. I skipped ahead to flashing the rom and factory reset like it prompted. Then I tried to flash the .tar and it fails. ..:/. I don't know what else to do.
Click to expand...
Click to collapse
Unzip the fw using 7zip. Then odin flash the .tar.md5 file you just extracted.
Sent from my SGH-T999 using xda premium

Don't use toolkit for that just go to root66 thread. Download everything what you need from there and follow steps in 2 post under odin use.
Good luck
Sent from my SGH-T999 using xda app-developers app

Originally Posted by Misfit77
When I try the root66 it fails in odin. I used the root66_TMO_T999UVDLJA one. First, I had toolkit convert it into a .tar. Then I chose option 8 to flash a stock rom. I skipped ahead to flashing the rom and factory reset like it prompted. Then I tried to flash the .tar and it fails. ..:/. I don't know what else to do.
Click to expand...
Click to collapse
Actualy I don't use toolkit so I might be wrong, but I don't think you need to convert root66 to tar. Just skip the toolkit. Put your phone into download mode, open odin, connect your phone to pc and flash root66. Check root66 thread for some info about unziping it or converting to anything. All info should be in op. If there is nothing about it then flash it as it is. Make sure that you have phone drivers installed and turn off kies.
I hope it helps.
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 07:05 PM ---------- Previous post was at 06:49 PM ----------
I've just checked root66 thread. You don't have to convert it or unzip it. Just flash as it is. Your problem might came from converting that file to tar.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help, I'll try it when o get home.
Sent from my WX435 using xda app-developers app

Actually I was a bit wrong, like DocHoliday wrote, you just have to unzip it and use tar.md5 file inside. The rest is as I wrote before.
Good luck and let us know how it went
Sent from my SGH-T999 using xda app-developers app

HajmeR said:
Actually I was a bit wrong, like DocHoliday wrote, you just have to unzip it and use tar.md5 file inside. The rest is as I wrote before.
Good luck and let us know how it went
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It worked!!! Thank you both so much!! I was really getting frustrated.

Misfit77 said:
It worked!!! Thank you both so much!! I was really getting frustrated.
Click to expand...
Click to collapse
Good to hear that! If you will have some problems with sgs3 in the future you can pm me and I will try to help. Just saying that because I'm not looking into q&a very often. Good luck and happy flashing
Sent from my SGH-T999 using xda app-developers app

HajmeR said:
Good to hear that! If you will have some problems with sgs3 in the future you can pm me and I will try to help. Just saying that because I'm not looking into q&a very often. Good luck and happy flashing
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I will, thanks again!

Did the same thing
I did the same thing. I used the toolkit and was distracted by my son which ended up in me skipping over areas I thought I read and missed the part about JellyBean creating soft-brick.. It did install CWM though . Low and behold, I soft-bricked my phone with the pulsing blue LED from HELL. I kept having issues flashing everything, luckily the toolkit DID install CWM for me which was of no help. When I used Odin 3.0.4 it worked flawlessly with the stock rooted t999 rom which I have attached along with Odin 3.0.4.
Here is how to fix your soft-brick with the black screen and blue LED from hell:
1.) Download files attached and EXTRACT > root66_TMO_T999UVDLJA.7z AND Odin_3.0.4_Files.zip
2.) Boot into download updates screen by pressing and holding Home Button, Volume Down Button, and Power Button at same time until you boot into downloading updates screen.
3.) Plug in your phone to your pc
4.) Open Odin 3.0.4 make sure Auto Reboot and F . Reset Time are checked
5.) Click the PDA button at the right, select boot-stock-tmobile-sgh-t999
7.) Click the START button.
8.) Repeat Steps 2-4
9.) Click the PDA button at the right, select root66_TMO_T999UVDLJA.tar.md5
10.) Click the START button and you should see it install things you never saw before like BOOT, SYSTEM, MODEM, etc. (not in that order) at the top left where it shows installation progress (that little green rectangle)

Failed Root Attempt On Previously Unrooted I317UCALK7 - Bricked?

I wanted to try an AKOP ROM or two on my completely stock, never rooted Note 2 running the OTA UCALK7 update. I followed the guide here (flash the SU injected stock UCALJ2 image) to root and now my note gets stuck at the Samsung logo. I have tried the following:
Downloaded the completely stock UCALJ2 unrooted image and flashed via ODIN.
Tried flashing both stock and rooted ROMs on another computer using the stock USB cable.
Flashed CWM touch via ODIN after flashing rooted UCALJ2 image, it can boot to CWM but fails miserably most likely to the lack of root.
My guess is it's bricked because sammy closed the root hole in the UCALK7 update and flashing back to rooted UCALJ2 isn't enough to bypass the patched exploit. Is there an ODIN flashable complete UCALK7 image that I can try (I've looked to no end, all I can find are rooted zips flashable via CWM) or am I really up the creek?

Pull the battery.
Hold the Center Home Button + Vol Down + Power
Slide the battery in.
If you do this right you can get into odin before the Samsung logo. I just had the same problem because I flashed the wrong recovery. It worked for me.

shakabra said:
Pull the battery.
Hold the Center Home Button + Vol Down + Power
Slide the battery in.
If you do this right you can get into odin before the Samsung logo. I just had the same problem because I flashed the wrong recovery. It worked for me.
Click to expand...
Click to collapse
Thanks but I can get into Odin and flash the stock ROM just fine. It then reboots and gets stuck at the Samsung logo.

Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium

twanskys204 said:
Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
The three finger salute lol:thumbup:
Sent from my GT-N7105 using Tapatalk 2

twanskys204 said:
Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks - I actually figured that part out since my second post. The phone boots after the factory reset however I don't get phone/data service. I've since tried flashing the two AT&T modems I could find, atti317ucalj2modemfixed.zip and ATT K7 Modem - Baseband.zip. Neither resolve the issue.

Cheack ur apn
Sent from my SGH-I317 using xda premium

twanskys204 said:
Cheack ur apn
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks but I can't even enter the network configuration settings - it tells me to insert a SIM. My SIM is in the phone.

I'm having other problems too which I think are partition related. Apps are acting funny, saying there isn't space on the phone (dropbox can't download anything, etc). I'm trying to get TriangleAway installed so I can just RMA it but I can't even download it to my phone. Also a CWM fix permissions fails even though I grant it root access.

It's really simple..download firmware from Sammobile.com flash it in Odin.. u might get stuck on the Samsung screen, if that happens factory reset. Make sure your downloading right file...u r now messing with Odin and it doesn't forgive
Sent from my SGH-I317 using xda premium

twanskys204 said:
It's really simple..download firmware from Sammobile.com flash it in Odin.. u might get stuck on the Samsung screen, if that happens factory reset. Make sure your downloading right file...u r now messing with Odin and it doesn't forgive
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
I know what you're saying, I'm definitely using the right file and process. I'm a pretty seasoned veteran when it comes to rooting/odin/RSD/fastboot, etc. I've run custom ROMs on dozens of phones since the G1. What's happening to me is apparently not a common failure with the note 2 or GS3. Is there a PIT file available for the AT&T Note 2? I see one for the Verizon Note 2 but I wouldn't dare try to flash that.

There is a pit file around but I really don't think it's that.
And also just checking don't mean to insult ur intelligence but if u are using Odin it will be a .tar, if it's a recovery its I .zip
Sent from my SGH-I317 using xda premium

twanskys204 said:
There is a pit file around but I really don't think it's that.
And also just checking don't mean to insult ur intelligence but if u are using Odin it will be a .tar, if it's a recovery its I .zip
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Yeah, it's a tar file I'm flashing through Odin, got it from SamsungUpdates: Samsung-Updates.com-SGH-I317_ATT_1_20121005095854_bpaaavv07o.
I also tried flashing the stock ROM in deodex'd zip form after I got a custom recovery on there, still no dice. The non-functioning modem and lack of proper root/storage affects both Sammy and CM/AKOP based ROMs. I don't know about the modem part but I've seen weird things like this when the NAND starts going bad and things written to it don't "stick." I don't think that's the case here since it's only on its 4th or 5th flash. More than likely the latter problem is a file system issue. I have no idea about the radio.
I'm going to try and exchange it tomorrow. At least I got the flash count cleared and I'm back on a stock ROM (with the same problems).

[Q] What does RQT_CLOSE mean?

I am at the point where my AT&T Note 2 SGH-i317 either displays the Samsung Note II screen or I can go into the Odin screen. It will not open recovery.
If I try to install CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 using Odin, I get the message from the title.
Odin appears to load the factory 4.1 rom but I end up with the same message at the end.
I had successfully restored 4.1 using Odin and then the phone auto updated to 4.3. After that, I followed the instructions for installing Jedi Master but the phone won't restart. I tried to use the same files I got 4.1 back with (this has worked twice before from 4.3) but they will no longer work. Is there anything I can do to get the phone working again?

mid_life_crisis said:
I am at the point where my AT&T Note 2 SGH-i317 either displays the Samsung Note II screen or I can go into the Odin screen. It will not open recovery.
If I try to install CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 using Odin, I get the message from the title.
Odin appears to load the factory 4.1 rom but I end up with the same message at the end.
I had successfully restored 4.1 using Odin and then the phone auto updated to 4.3. After that, I followed the instructions for installing Jedi Master but the phone won't restart. I tried to use the same files I got 4.1 back with (this has worked twice before from 4.3) but they will no longer work. Is there anything I can do to get the phone working again?
Click to expand...
Click to collapse
Which version of odin are you using?
Can you enter stock recovery or only download mode?
If you can get into stock recovery if it says anything about knox then you have the new bootloader, which you should if you updated to 4.3 via an ota update or an odin file. If you have this we can skip a few steps. If you don't, we will basically be starting from the beginning.
Assuming you have the newer bootloader, this is what I need you to do.
Go to teamw.in and download the latest twrp and make sure it's the recovery.img.tar.md5 flash that through odin.
In the mean time start a fresh download of jedi masterx2. When that download finishes make sure you verify the md5 sum. This is key. One digit off and the entire download is bad and you'll end up bootlooping again.
Once you have twrp and a good download of jmx2 boot into twrp. Do a system wipe and then flash the rom.
Let me know how it works. Just be patient and we can get this fixed for you. As long as you can power on you can recover your phone and make it work.
Sent from my SM-N900T using XDA Premium 4 mobile app

I use an app called hash droid to verify md5
Sent from my Jedi MasterX Note 2

kushXmaster said:
Which version of odin are you using?
Can you enter stock recovery or only download mode?
If you can get into stock recovery if it says anything about knox then you have the new bootloader, which you should if you updated to 4.3 via an ota update or an odin file. If you have this we can skip a few steps. If you don't, we will basically be starting from the beginning.
Assuming you have the newer bootloader, this is what I need you to do.
Go to teamw.in and download the latest twrp and make sure it's the recovery.img.tar.md5 flash that through odin.
In the mean time start a fresh download of jedi masterx2. When that download finishes make sure you verify the md5 sum. This is key. One digit off and the entire download is bad and you'll end up bootlooping again.
Once you have twrp and a good download of jmx2 boot into twrp. Do a system wipe and then flash the rom.
Let me know how it works. Just be patient and we can get this fixed for you. As long as you can power on you can recover your phone and make it work.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odin shows the Knox flag, so I assume I am on 4.3.
I cannot find this file, "recovery.img.tar.md5".
The most likely looking file I found was this, but it isn't an md5, "openrecovery-twrp-2.6.3.1-t0lteatt.img.tar".
In fact I find no files with an "md5" extension on that site.

mid_life_crisis said:
Odin shows the Knox flag, so I assume I am on 4.3.
I cannot find this file, "recovery.img.tar.md5".
The most likely looking file I found was this, but it isn't an md5, "openrecovery-twrp-2.6.3.1-t0lteatt.img.tar".
In fact I find no files with an "md5" extension on that site.
Click to expand...
Click to collapse
I apologize. For the recovery.img it needs to be the tar extension.
Once you push that to the device you're back in business.
Sent from my SM-N900T using XDA Premium 4 mobile app

kushXmaster said:
I apologize. For the recovery.img it needs to be the tar extension.
Once you push that to the device you're back in business.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I gave you a thanks because I truly appreciate the attempt to help me, but that wouldn't load either.
Fortunately the guy at the Samsung counter was able to use a Samsung loader to force 4.3 and the phone is working again.

Just curious - is your knox warranty counter back to zero in download mode?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

mid_life_crisis said:
I gave you a thanks because I truly appreciate the attempt to help me, but that wouldn't load either.
Fortunately the guy at the Samsung counter was able to use a Samsung loader to force 4.3 and the phone is working again.
Click to expand...
Click to collapse
Hmm that us interesting. I wonder why it wouldn't load...
What version of odin do you use? I've been using 3.07 for a long time with no issues.
I'm curious about the knox counter as well.
Sent from my SM-N900T using XDA Premium 4 mobile app

Zen Arcade said:
Just curious - is your knox warranty counter back to zero in download mode?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Neither counter reset. It still displays the count for custom roms and a "1" for the Knox toggle.

kushXmaster said:
Hmm that us interesting. I wonder why it wouldn't load...
What version of odin do you use? I've been using 3.07 for a long time with no issues.
I'm curious about the knox counter as well.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's 3.7

That's good and weird at the same time.
Its good because its what we expected AND that the Samsung person fixed your phone even though you tripped the KNOX bit.
Its weird because the Samsung person fixed your phone even though you tripped the KNOX bit.

Stuck in brickloop, Tried odin stock firmware, no go

Hello all!
So I bought a SGH M919 s4 off craigslist for 150 knowing that it wouldn't boot past the Samsung galaxy s4 boot screen, Thinking it would be an easy fix by flashing the stock firmware through odin. Well that's not the case, I've tried just about everything I am capable of...
1.Both odin 3.0 7 and odin 3.0 9 both flash and the device passes but on the boot screen it says booting recovery and just sticks there, It stuck on that over night so I am being patient.
2. I've tried flashing 4.3 which fails right away leading me to believe the phone was updated to 4.4.2 at some point in time.
3. It wont let me boot into stock recovery or I've even tried flashing TWRP, CWM and it pass's but still will not let me boot into those recovery's either.
4. Tried rooting the phone a couple times and that passes in odin but does nothing after that.
5. I ve tried different phone cables, I haven't tried a different computer yet.
6. The only thing I can get into on the phone is download mode and it says this on the screen
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0X0
KNOX WARRANTYVOID: 0X1
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: enable
eMMC BURST MODE enable
I don't remember seeing those last two things on the list normally if I can recall. Any help will be greatly appreciated and possibly a donation if we can get this thing fixed. Thanks.

Repartition it with the pit file while youre installing the firmware.
Last 2 strings are normal.
Sent from my SGH-M919 using XDA Premium 4 mobile app

ShinySide said:
Repartition it with the pit file while youre installing the firmware.
Last 2 strings are normal.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply, Do you know where the pit file can be found or what do I write in the pit file box?

Ok so I pulled the pit file from another T-Mobile s4 I have and flashed that with the stock firmware and that didn't work. The phone I pulled the pit file from is on 4.3 still so I'm assuming that's why it didn't work???

Quickvic30 said:
Ok so I pulled the pit file from another T-Mobile s4 I have and flashed that with the stock firmware and that didn't work. The phone I pulled the pit file from is on 4.3 still so I'm assuming that's why it didn't work???
Click to expand...
Click to collapse
Na that wouldnt matter. Your pit file is for your partition layouts. Which dont ever change.
I really cant think of anything else of why you can't get into recovery or boot the phone with everything you've tried. You might just need to Jtag the device
Sent from my SGH-M919 using XDA Premium 4 mobile app

ShinySide said:
Na that wouldnt matter. Your pit file is for your partition layouts. Which dont ever change.
I really cant think of anything else of why you can't get into recovery or boot the phone with everything you've tried. You might just need to Jtag the device
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the help, I might jtag it or just try to find a used motherboard :laugh:

Quickvic30 said:
Thanks for the help, I might jtag it or just try to find a used motherboard :laugh:
Click to expand...
Click to collapse
The OP mentions that you tried flashing 4.3 and you speculated if it had been updated to 4.4.2. Just out of curiosity, have you tried flashing the stock 4.4.2 firmware?

lordcheeto03 said:
The OP mentions that you tried flashing 4.3 and you speculated if it had been updated to 4.4.2. Just out of curiosity, have you tried flashing the stock 4.4.2 firmware?
Click to expand...
Click to collapse
Yes I've been to flashing 4.4.2 and it passes Odin. I think maybe you meant have I tried flashing 4.2.2? I have not tried flashing 4.2.2 firmware yet, I might try that but 4.2.2 didn't have the Knox counter did it?
Sent from my SM-G900A using XDA Free mobile app

Quickvic30 said:
Yes I've been to flashing 4.4.2 and it passes Odin. I think maybe you meant have I tried flashing 4.2.2? I have not tried flashing 4.2.2 firmware yet, I might try that but 4.2.2 didn't have the Knox counter did it?
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
No, I meant 4.4.2. It was a dumb question, but sometimes it's the simple things you overlook. Like I said, the OP only said you tried flashing MK2. You won't be able to flash anything pre-KNOX so there's no need in wasting the time downloading the MDL firmware.
An idea would be to power the phone off, boot straight to download mode, flash NB4, pull the battery when it's complete, boot straight back to download mode and re-flash NB4. I know that you have to do that sometimes for the modem to stick, perhaps you could try that with the firmware itself. Hey, worth a shot. Good luck.

lordcheeto03 said:
No, I meant 4.4.2. It was a dumb question, but sometimes it's the simple things you overlook. Like I said, the OP only said you tried flashing MK2. You won't be able to flash anything pre-KNOX so there's no need in wasting the time downloading the MDL firmware.
An idea would be to power the phone off, boot straight to download mode, flash NB4, pull the battery when it's complete, boot straight back to download mode and re-flash NB4. I know that you have to do that sometimes for the modem to stick, perhaps you could try that with the firmware itself. Hey, worth a shot. Good luck.
Click to expand...
Click to collapse
I think I might have tried flashing twice in a row but I'll try it again since I haven't tried that since I've flashed the pit file. Thanks for the tip and I'll report back after the double flash.
Sent from my SM-G900A using XDA Free mobile app

So I flashed it, pulled the battery and flashed it again and still the same thing......:sigh: lol Time to look for another wrecked phone for spare parts

Bought a phone off cl with a cracked screen and swapped the motherboard into the phone and it works like a champ now! :thumbup:
Sent from my SM-G900A using XDA Free mobile app

Soft Bricked? Stuck at boot screen.

Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?

BWolf56 said:
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?
Click to expand...
Click to collapse
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.

BWolf56 said:
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.
Click to expand...
Click to collapse
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's in your System folder. Should be able to navigate to it using your recovery.

BWolf56 said:
It's in your System folder. Should be able to navigate to it using your recovery.
Click to expand...
Click to collapse
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?

donutkidd said:
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?
Click to expand...
Click to collapse
Hopefully it is. And I duno about the command, you'll have to look that one up (or perhaps someone here knows it).

If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk

Ok I will try that when I get home.
Sent from my SM-N900T using XDA Premium 4 mobile app

DocHoliday77 said:
If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Ok I did the getprop ro.bootloader command and it's I747UCDLK3. I have already tried the lk3 Odin but let me try to re download a fresh copy of it.
Sent from my SM-N900T using XDA Premium 4 mobile app

No dice, I even downloaded a 4.1.1 lk3 rom. It flashed and said successful so I rebooted and back to the blue Android. Is it possible NY partitions or whatever are corrupt and if so anyway to fix it?
Sent from my SM-N900T using XDA Premium 4 mobile app

I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.

DocHoliday77 said:
I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.
Click to expand...
Click to collapse
I honestly think I tried what you suggested already but just to triple check I will do so again in the morning and report back with hopefully good news.
Sent from my SM-N900T using XDA Premium 4 mobile app

@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?

DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
No, nothing for 4.1.1 (LK3).
I don't think that's his issue though. Last time I saw that issue was on the S1 (Captivate) and the solution was to use Heimdall.
If the repartition doesn't work though, I'm not exactly sure what will.

DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.

donutkidd said:
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.
Click to expand...
Click to collapse
Do you have the actual link to that thread? Search is derping on me.

BWolf56 said:
Do you have the actual link to that thread? Search is derping on me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ouff that's one bad issue, it can take a while to figure out which partition got messed up. And sadly, I can't be much help there :/