yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Q&A, Help & Troubleshooting] Rakuu:
No update, still unrootable.
[Captivate Q&A, Help & Troubleshooting] Bronando:
I want to flash back to stock because I'm having problems and I hope a full wipe and repartition works. I don't have a working desktop with me. I do have a custom recovery (CWM/Philz/TWRP) and mobile odin PRO (mobile odin doesn't like custom ROMs like CM though). Any way I could go back to stock without a desktop computer?
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Grab a non-bootloader version of the stock ROM (can be found in the stickies) and use mobile Odin to flash it.

That being said, it's never safe to do anything on the Cappy without a pc access or working usb.
[Captivate Q&A, Help & Troubleshooting] Bronando:
Mobile Odin doesn't work on CM or certain custom ROMs because of the error

"A compatible device has been detected but with an unexpected partition layout. Mobile ODIN cannot operate. This is a common error on CM and MIUI ROMs on some devices."

I'm trying to run it on slimbean 4.3. Got any ideas?
[Captivate Q&A, Help & Troubleshooting] BWolf56:
You said you were trying to flash stock ROM, which is all mobile Odin will flash.

If you wanna flash another ROM, do it in recovery after wiping. Make sure you have the ROM on your phone before hand though or you'll be stock with a paper weight.
[Android Q&A, Help & Troubleshooting] Rockyboy14:
I have been trying to upload my framework-res.apk and systemui but after some time it say server (IO) error

pls help, I'm uploading with latest firefox and I'm using proxy server and port.... What can i do cos i really want to install the UOT to my phone
[Android Q&A, Help & Troubleshooting] abd_kzm:
سلام

فرستاده شده از HUAWEI G610-U20ِ من با Tapatalk
[T-Mobile Samsung Galaxy S 4] redx64:
I currently am on the virgin rom 4.4.2 with M919UVUFNB4 baseband.

Everytime i have tried to upgrade to 5.0 (jfltemo , most recently candy 5) roms , there has been various issues , Can that be due to baseband versions?
[T-Mobile Samsung Galaxy S 4] av911:
Describe "issues".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
I have what's probably a unique situation, though I hope not. For background info, I bought two I747s, one white and one blue, each with issues, but I intended to put parts together to end up with one good one.

When I did a factory reset on the blue one via the recovery menu, it returned a bunch of errors along the lines of "failed to mount /data." Then when it rebooted it would hang on the Samsung logo. Back in recovery mode it returns more of the same errors just booting into recovery mode, and factory reset still returns more of the same errors and doesn't fix anything. I flashed 4.3 with Odin in an attempt to fix it, but I got the boards mixed up, and that one had 4.4 on it, not 4.1 like I thought. I'm pretty sure it's hard bricked now (that whole can't downgrade thing) because it's unresponsive to everything. Though my computer does recognize that it's plugged in, more on that later.

So I figured, fine, I screwed up, I'll just use the other board with 4.1 on it from the white phone. Except when I did a factory reset on that one, it did the exact same thing! Same errors, same problem stuck at the Samsung logo. Except this time I'm not flashing sh*t until I know exactly what I need to do to fix it. In another post where the guy had the same issue with 4.1.1, it was solved by flashing 4.3 with Odin. And another post where the guy had no idea what version he had, he just knew it was lower than 4.3, his problem was also solved by flashing 4.3, But since my last efforts failed miserably, I'm very reluctant to try it until I get some knowledgeable input. I don't remember exactly which version is on there, it's 4.1.something. I'd also prefer not to upgrade beyond 4.1 because I'd like to unlock it and from what I'm reading you can only do it for free if you're on 4.1. So I guess I need a link to an Odin flashable 4.1 package?

As for the poor blue phone that used to have 4.4.something, and was mistakenly flashed with 4.3, I've heard about JTAG but I don't quite understand it, and I'm not sure it would work in my case since a lot of what I'm reading says that bricking which occurs from downgrading is often unfixable. However, Windows recognizes that a device is plugged in when I attach it via USB. It shows up in the Device Manager as QHSUSB_DLOAD. I am currently researching more on this and the method of booting from an SD card, except I don't have an SD card reader at the moment.

Any assistance, advice, links, information, and plain ole encouragement are always welcome and appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
For the phone running 4.1, flash any stock rom in Odin. After flashing, boot into recovery and perform a factory reset, then boot the phone and use the free method to sim unlock. The important thing is to have the stock 4.1.1 dialler in order to access the hidden menu options?

For home hard bricked phone, you will have to try the debrick image method. If it doesn't work, a jtag service should be able to force flash a rom to the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
Wow, that was like a crazy fast reply!

What if the phone is 4.1.2? Can I still flash 4.1.1? I'm on the hunt for a 4.1.1 stock rom now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Yes, you can flash 4.1.1 from 4.1.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
Apparently not always. I downloaded and flashed 4.1.1 with Oden 3.07, it rebooted, showed the android image like it was updating, progress bar finished, and then it just went blank. Now both phones are in the same condition of being hard bricked and showing QHSUSB_DLOAD in the device manager.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
This is strange. I have downgraded approximately 10 i747m phones from 4.1.2 to 4.1.1, unlocked using the free method, and re-flashed back to 4.1.2 after unlocking.

http://xdaforums.com/showthread.php?t=2371897

What options did you check in Odin? Where did you get the 4.1.1 ROM? I ask because the stock ATT 4.1.1 rom was apparently removed from sammobile.com.

How did you confirm that the phone was running 4.1.2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
I checked only auto reboot in Odin.

I found this link sammobile.com/firmwares/database/SGH-I747/ in this thread http://xdaforums.com/galaxy-s3-att/help/downgrade-att-running-stock-4-4-2-rom-t3170938 , 7th post

The download was going absurdly slow, so I googled the exact file name being downloaded which was, I747UCDLK3_I747ATTDLK3_ATT, and found a google drive link at https://drive.google.com/file/d/0B_UTWXKFnZoNVFdSVjJEZlMwZjA/edit which was the first result after searching for the file name if that link doesn't work. I'm downloading the slow one now to compare it to the one I got from google drive.

I'm unsure if the phone was 4.1.1 or 4.1.2, that's why I asked if it's possible to flash 4.1.1 on top of 4.1.2. I was only trying to do a factory reset originally and had no intentions of flashing anything. I just wanted to wipe out all the crap on it from the previous user so I had only glanced at the version out of curiosity to see if it was unlockable via the free method. I remember it was 4.1.something.

I have an SD card reader on order. Hopefully I'll be able to unbrick one of them.

Do you, or anyone else, have any idea why a simple factory reset would cause errors like I described and then hang on reboot? At that point both phones were 100% factory and I hadn't done anything to them except put a battery in them to power them on. I've done a factory reset on four other S3s and this didn't happen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
It is definitely possible to flash 4.1.1 over 4.1.2 because the bootloader could not be downgraded until the mjb version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
That's what I've been reading. So where did I go wrong? Any idea why a factory reset would screw up like that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Did you confirm the bootloader before flashing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
No, because I had no intentions of flashing it when I tried to do a factory reset. Then after that went bad it wouldn't boot, and I don't know how to check the boatloader when a phone will only go into recovery mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Where did you see reference to 4.1? It's possible that the modem or baseband was 4.1 but the bootloader was 4.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
Under about device and then Android version. The one where if you tap it a lot you get the jellybean android that pops up. It wasn't the baseband version because that's a much longer number with the model number in it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
That screen doesn't tell you the bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
As I said, I didn't check for the bootloader version before I ran into trouble because I only wanted to do a factory reset and I didn't intend to flash anything. I wouldn't imagine that it would have a different bootloader than the OS version unless that can happen without any user intervention because the previous owner was only concerned with selfies and games. She certainly didn't modify anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I cant explain what happened. This has never happened to me after flashing about 10 phones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
I believe it has something to do with the errors that were produced while trying to do a factory reset. What bothers me is that both phones did the exact same thing. Normally I'd say it was something I did, except that I didn't do anything but put a battery in them, boot up, find lots of junk installed, and then attempt a factory reset. On the first phone, I rebooted into recovery and tried it from there. On the second phone I tried it from inside the OS. Same results on both. The phones ran fine before that.

Any advice on how to do the boot from an SD card, or how to do the JTAG thing? I've been reading a lot but the information jumps around a lot. I'm comfortable with soldering and have an IT background if that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
It's possible that the recovery was corrupt or the partitions were corrupt.

Whenever I factory reset a phone, I always boot into recovery to do that, not from within the ROM.

Sounds to me like you did nothing wrong.

Did the previous owner have the phone from the time it was new?

Edit: for the phone that you flashed with 4.1.1, Odin said "pass" in the status window and the it auto rebooted?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
I don't know for sure if she had it from new. Yes, for both phones Odin said pass in the window and then it rebooted. I had walked away when Odin finished with the first phone. I came back and it was dead. The second one I watched and it showed the android with the wireframe in his guts and the progress bar which moved across, and then it just went blank.

There were error messages about the partitions when I did the factory reset IIRC. Perhaps the recovery or the partition was corrupted like you said. It's just odd that both had the exact same identical problem with the exact same results. That's why I think that it must have been something I did, except that I didn't DO anything other than initiate a factory reset.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I took an i747m and reflashed stock the Telus 4.4.2 ROM.

In download mode, you should see the green Android guy with the words "Downloading...Do not turn off target" and a blue progress bar moving from left to right.

I did not check reset in Odin. Once it finished flashing the ROM, I removed the USB cable, removed the battery, replaced the battery, and booted the phone. I the Android guy with the wire frame for a few seconds, the screen went blank, and the phone started up with the Samsung logo.

Since you were getting errors with mounting the different partitions, you may have needed to flash the PIT and PDA files but I can't really say for sure as I have never encountered this problem.

I normally verify everything before I use Odin because phones that I have been given to fix have had all sorts of weird configurations.

You'll have to try the debrick guide. of use a jtag service. You could also do what I did and that is to look for people with phones that have a damaged screen and buy they at a steep discount.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
I went through the same process, except removing and reinstalling the battery, and got all the way to the end like you described except I ended up with a black screen instead of "and the phone started up with the Samsung logo." So something is screwed up in the bootloader.

Since the phone shows up as QHSUSB_DLOAD in the Windows device manager that means the hardware is working, but it doesn't know what to do with itself. I refuse to believe that there isn't some way to upload a bootloader in the phones current state. The DLOAD part suggests that it's ready to download. I've been searching about this and I found an article that had me hopeful here: http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html .

I tracked down all of the program files, drivers, and .hex things, and I followed the instructions to the letter. All I got for my efforts was an error message that says "The image download failed. Cookie (if present) not received." However, it only reinforces my belief that something can be done with the phone in this state because with the Qualcomm QDLoader driver loaded, Windows recognizes the phone as a device and assigns it a COM port. This allows the eMMC program (from the above link) to attempt to send data to the phone. That means there's an open line of communication to the phone, I just don't know how to use it properly.

I will try the SD card method when my SD reader arrives. I read somewhere that you need a class 10 SD card, but this thread http://xdaforums.com/showthread.php?t=2549068 doesn't say anything about needing a certain class of SD card. I have a class 4, 16GB card, it should work?

If that doesn't work, I suppose I could use a JTAG service. But I hate paying for something that I could likely accomplish myself if I only knew how. There are people who have other phones with the same Qualcomm chip as the S3 that end up in this predicament, and many of them have a special flash tool that they use to flash a rom while the phone is in this exact same state.

And I did buy these phones at a steep discount. Each has broken bits, but there's enough to make one good one, almost. So it's not like I fried $200 worth of phones. But still, the inability to fix something which is fixable bugs the crap out of me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I understand how you feel. I am also a "tinkerer" and always looking for a great bargain. I bought an s3 for $20 with a smashed screen. The seller assured me that the phone works except for the screen. He was right because I could hear it making all of the boot up sounds , it was detected by kies, etc. It took me about 6 months until I came across a phone with a perfect screen but a damaged USB port and microphone.

Definitely give the de-brick method a try. Good luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
Thanks, I think I'm going to need it. Do yo know if a class 10 SD card is required, or if my class 4 will work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I have never used the debrick method so I am not sure if a class 4 will work. You could always try it and get a class 10 if necessary.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
If it boots with the SD, do I still need to flash exactly what was on the phone before, or can I flash something different? Since I'm not certain what was on the blue one, where should I start with that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Can you get into download mode? If you can, you could try flashing a custom recovery and a custom rom to at least get the phone booted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
Does it matter which custom recovery or which base version of custom rom I use? I'd still like to be able to do the free unlock method to the one that was running 4.1 if at all possible. I should get the SD card reader on Friday or Saturday, but I want to have everything located and downloaded ahead of time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I recommend flashing the latest twrp via Odin. Make sure you get the tar version of twrp for the d2att. Flash it in Odin using the PDA box. Do not check auto reboot. Flash twrp, when you see the word reset in the status window, remove USB cable, remove battery, replace battery, boot into recovery. Hopefully, out works.

The free unlock method requires a stock 4.1.1 rom and 4.1.1 bootloader, not a stock recovery.

Edit: Looks like you may have to flash the bootloader before installing recovery.

http://xdaforums.com/showthread.php?t=2549068
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
Tried the SD card method today with no luck. Some people say they have better results with different brands of SD card, like Sandisk. I have a PNY, so I dunno if that's it or not. I tried writing 4 different debrick images several times with no results. I posted on the debrick thread to see if anybody following that thread has any ideas. Not sure if I want to put out the money to JTAG both phones... might sell them for parts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
If the LCDs are fine, you could get some decent money for them as the LCDs from ebay are quite expensive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
The LCDs are both broken, unfortunately. I have an LCD from a T999 that I was going to use as the T999 has it's own issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
You mean the digitizer is cracked or there is something wrong with the LCD too?

What's wrong with the T999? It's the t-mobile version of the s3 as you probably know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
On the I747s, both of them have cracks in the LCD itself, one of them also has cracked glass. The board is fried on the T999. No power, no detection in Windows, no flashing, no nothing. The LCD is fine, though the glass is cracked on top. I was going to use the LCD from the T999, the glass from an I747, and whatever board I could manage to unlock. They were $20 each, so I could probably sell the T999 LCD for $40 on ebay and only be out $20.

Or I could JTAG both boards for $25 each, build my phone with one and sell the remaining I747 board for $45, breaking even on that one. But I would still end up spending an extra $25 to get a phone together. So either way I loose $20 or spend another $25.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I understand. I have to tell you that it is very difficult to separate the glass from the LCD. For the glass, I would just get a cheap one from eBay because the chance of cracking the glass will separating it from the LCD is tough.

To see what's wrong with the t999, swap parts with the i747 and see what happens. Maybe the t999 board works and the t999 LCD doesn't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
I got one to boot with a class 10 Sandisk Ultra Plus with an image called debrick-SGH-I747U-CUEMJB3.img. It hangs at the ATT globe if I let it try to boot all the way. I can get into the system recovery menu though. What, exactly, should I do now? You said to get the tar version of twrp for the d2att. That's slightly Greek to me but I'll figure it out and work on locating it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Are you able to get into download mode? You need download mode in order to use Odin to flash TWRP, a custom recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
Whatever happened in my previous failed flashing attempts, both are on 4.3 now. Got into download mode, flashed twrp, and both boot. At first it was only with the SD card. Then I flashed a new bootloader on both and they boot on their own now. So they're both all fixed up and I'm very happy.

Unfortunately both are locked to ATT so I have to work on that now, but at least they're both working again. Now I'm not so mad at myself. Thanks for all your assistance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I'm very glad you got it working. If you intend to sim unlock the phones, you should unlock them using a stock ROM as you need the stock dialler to enter the unlock code.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
I would like to unlock them but I suppose, since they're on 4.3, I have to purchase an unlock code. Or, rather, two unlock codes. Unless there's another way?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
There is no other way once the phones are running a 4.3 bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
That's what I thought. Oh well, it's better that than having two bricks, that's for sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
So the LCDs are okay?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
No, both LCDs on the I747s are bad. When you shine a light on them from the side you can see there are tears/cracks in the LCD wafer itself, even though only one of them has cracks in the glass. I used the LCD and housing from the T999 to do the debricking and flashing. Unfortunately, that display has cracked glass too. I had planned on using the T999 LCD, the glass from one I747, and the board that used to have 4.1 on it from the other I747 to make one unlockable GSM S3, and then maybe sell the remaining I747 board to recoop some of the cost.

I did manage to get the T999 to boot after having it all apart. It runs 4.1.2 and is locked to t-mobile. I'm not sure if that means it's unlockable or not, but the phone is pretty yucky on the inside. It even smells. So I don't know if I want to try to unlock it and use it. I may part everything out and try to find an S3 that's already unlocked. I'm kinda eyeballing an I9300.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I think the T999 on stock 4.1.2 can be downgraded to stock 4.1.1 using Odin and unlocked using the free method.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
The thought of doing that makes me nervous after the fiasco I just went through. Also the phone would have to be washed inside and out, or something. It looks like it was in a dogs back pocket for the last two years. I've never seen crud like this on the inside of a device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Well, you could take a chance and downgrade the ROM. I have downgraded the stock 4.1.2 ROM to stock 4.1.1 on about 10 i747m phones, unlocked them , and upgraded via OTA to the latest ROM. The phones remained unlocked after installing stock upgrades and custom ROMs. Your choice but I understand your hesitation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DrvLikHell:
Does the T999 use the same procedure as the I747 with Odin? Would I just have to find the correct T999 4.1.1 ROM then? Is there anything else I'd have to flash to it?

Also, do you have any suggestions for removing the crud and getting the smell off of the phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Flashing with Odin is the same for the i747 and T999.

Match the model # to the firmware on sammobile.com.

Boot into download mode on the T999 to make sure you see nothing about warranty bit. If you see nothing, you should be safe to flash the stock 4.1.1 ROM.

I would use pure alcohol and a cotton q-tip for starters. For the smell, place it inside a bag or jar with some baking soda and seal it for a few hours.