Develop Bugs

Unfixable Soft Brick??

So basically I was on stock 4.3 TW rom and tried flashing HyperDrive ROM. Everyhting went through but I did get any Data to work for the life of me.
Tried flashing back to a 4.4 GE rom, and got "com.phone.android" crash error right after boot up. Couldn't do anything with the phone at all.
Tried flashing another .zip I had, same thing with the phone.
Tried flashing stock rom throgh Odin, same thing.
Now after a couple other flash tried etc, my whole SDCARD is wiped, and can't use fastboot.
I can get into recovery but thats about it. Tried sideloading a rom with the same com.phone. issue.
About to drown this ****ing thing and use my warranty, at a complete loss now.

re: issues
jzero88 said:
So basically I was on stock 4.3 TW rom and tried flashing HyperDrive ROM. Everyhting went through but I did get any Data to work for the life of me.
Tried flashing back to a 4.4 GE rom, and got "com.phone.android" crash error right after boot up. Couldn't do anything with the phone at all.
Tried flashing another .zip I had, same thing with the phone.
Tried flashing stock rom throgh Odin, same thing.
Now after a couple other flash tried etc, my whole SDCARD is wiped, and can't use fastboot.
I can get into recovery but thats about it. Tried sideloading a rom with the same com.phone. issue.
About to drown this ****ing thing and use my warranty, at a complete loss now.
Click to expand...
Click to collapse
Since you have only posted the issues you are having with your phone but not your
phone's specific model I cannot help you more than the following.
What I can tell you is if you really want to fix the issues you are having you need to forget
about going into recovery mode and instead make sure you can go into "Download Mode".
Once you can get your phone into download mode you will need to find and download the official
stock Odin flash firmware specific to your phones model and flash your phone using Odin.
Good luck!

You've posted in Tmo S4, Nexus 4, i9505 threads at the minimum. Please make sure you're in the right forums. But in any case, you've overwritten many files by doing dirty flashes. Your best bet is to go into download mode (Vol Down + Home + Power), connect phone to computer, open up Odin, select PDA/AP, and then choose the stock file for your phone model and version.

.. slightly off-topic, but.. Isn't a "soft-brick", by definition, fixable? Otherwise it'd be a 'hard-brick'?

coyttl said:
.. slightly off-topic, but.. Isn't a "soft-brick", by definition, fixable? Otherwise it'd be a 'hard-brick'?
Click to expand...
Click to collapse
Soft-brick is exactly what it is, it is a software issue in which case you can usually Odin back to stock and get it working again. A hard-brick is when you can no longer flash any new software onto the phone and the only way to repair it is using a JTAG device which majority of the people don't have. It essentially becomes a paperweight. But all hope is not lost. There is a service that you can send your phone in and for about $25 or so, they will have it fixed and back to you within a week. The company has good reviews so it's worth it if you've bricked your $600 device.

xdapowerapps said:
Soft-brick is exactly what it is, it is a software issue in which case you can usually Odin back to stock and get it working again. A hard-brick is when you can no longer flash any new software onto the phone and the only way to repair it is using a JTAG device which majority of the people don't have. It essentially becomes a paperweight. But all hope is not lost. There is a service that you can send your phone in and for about $25 or so, they will have it fixed and back to you within a week. The company has good reviews so it's worth it if you've bricked your $600 device.
Click to expand...
Click to collapse
Okay, that's what I was thinking. Thanks!

Failed to mount /data and frozen after factory reset, HELP!

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.

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.

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.

Yes, you can flash 4.1.1 from 4.1.2.

audit13 said:
Yes, you can flash 4.1.1 from 4.1.2.
Click to expand...
Click to collapse
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.

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://forum.xda-developers.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?

I checked only auto reboot in Odin.
I found this link sammobile.com/firmwares/database/SGH-I747/ in this thread http://forum.xda-developers.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.

It is definitely possible to flash 4.1.1 over 4.1.2 because the bootloader could not be downgraded until the mjb version.

That's what I've been reading. So where did I go wrong? Any idea why a factory reset would screw up like that?

Did you confirm the bootloader before flashing?

audit13 said:
Did you confirm the bootloader before flashing?
Click to expand...
Click to collapse
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.

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.

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.

That screen doesn't tell you the bootloader.

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.

I cant explain what happened. This has never happened to me after flashing about 10 phones.

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.

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?

audit13 said:
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?
Click to expand...
Click to collapse
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.

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.

Bricked Note 8 AT&T SGH-I467

I've searched, I've tried but to no avail have I been able to fix my poor note 8..and I'm hoping someone can help!
I HAD a stock 4.4.2 Note 8 (AT&T version I-467) running, and I went with the Kingroot method to root. The device rooted but ran like a dog, and in my infinite wisdom did a wipe/reset to see if that would help.
Now here is where I stand:
1) The device boots to a screen saying unauthorized firmware
2) I can get to download mode (power+vol. down+Home)
3) I can NOT get to the screen with (power+col. up+Home)
I have tried Kies, and it won't take the serial number/model number, and Odin can only seem to flash the boot loaders. I have tried 4 different ROM's from samsung (with different international codes), and none of them are able to update the system (they all fail at about 90%). I've tried the all in one toolkit, and since I can't enable USB debugging at this point, it never recognizes the device as attached.
I've tried manually flashing with Odin TWRP, Phils, and stock recovery,(in the hopes of getting one to take so I could load a new ROM from SD card) and they all fail as well.
When I split any of the system images I can load a boot loader file from them, and it succeeds, but everything else fails.
Can anyone point me in the right direction, or am I completely hosed?

Sparkinman said:
I've searched, I've tried but to no avail have I been able to fix my poor note 8..and I'm hoping someone can help!
I HAD a stock 4.4.2 Note 8 (AT&T version I-467) running, and I went with the Kingroot method to root. The device rooted but ran like a dog, and in my infinite wisdom did a wipe/reset to see if that would help.
Now here is where I stand:
1) The device boots to a screen saying unauthorized firmware
2) I can get to download mode (power+vol. down+Home)
3) I can NOT get to the screen with (power+col. up+Home)
I have tried Kies, and it won't take the serial number/model number, and Odin can only seem to flash the boot loaders. I have tried 4 different ROM's from samsung (with different international codes), and none of them are able to update the system (they all fail at about 90%). I've tried the all in one toolkit, and since I can't enable USB debugging at this point, it never recognizes the device as attached.
I've tried manually flashing with Odin TWRP, Phils, and stock recovery,(in the hopes of getting one to take so I could load a new ROM from SD card) and they all fail as well.
When I split any of the system images I can load a boot loader file from them, and it succeeds, but everything else fails.
Can anyone point me in the right direction, or am I completely hosed?
Click to expand...
Click to collapse
+1 on that, I'm stuck in an exact same situation. No help from Samsung either. After rooting with Kingroot my tab started acting like crazy with flickering screen and random reboots, did exactly like you did.
There are many with similar issue and as per my research most of them have given up. Getting a system image dump from a rooted tab running 4.4.2 might be the only way out. Unless of course Samsung/AT&T decides to release full odin flashable image.

I was in a similar situation from trying to fix a eff problem and took my sgh-i467 to a Samsung Experience Center located in many Best Buys and they fixed it free of charge. They were not able to fix my issue with a corrupted EFF file that is keeping my 4G from working though as I had hoped. If you have a Best Buy around with the Samsung Kiosk in it I would give it a try. I ended up trying a few different ones to fix the eff issue and some of the employees at the Samsung centers were about as smart as a head of cabbage (they laughed at me when I said my Note 8 was the issue and said "you can't have a Note 8 the Note 5 just came out") but some were at least helpful and listened when I told them they have the tools to fix my tab (reflash it back to life) and they did. Hopefully they can help you.

man Im in the same exact situation.. And I cant seem to find any help anywhere. I cant locate a stock 4.4.2 kit kat odin flashable file anywhere for the n5120

Sparkinman said:
I've searched, I've tried but to no avail have I been able to fix my poor note 8..and I'm hoping someone can help!
I HAD a stock 4.4.2 Note 8 (AT&T version I-467) running, and I went with the Kingroot method to root. The device rooted but ran like a dog, and in my infinite wisdom did a wipe/reset to see if that would help.
Now here is where I stand:
1) The device boots to a screen saying unauthorized firmware
2) I can get to download mode (power+vol. down+Home)
3) I can NOT get to the screen with (power+col. up+Home)
I have tried Kies, and it won't take the serial number/model number, and Odin can only seem to flash the boot loaders. I have tried 4 different ROM's from samsung (with different international codes), and none of them are able to update the system (they all fail at about 90%). I've tried the all in one toolkit, and since I can't enable USB debugging at this point, it never recognizes the device as attached.
I've tried manually flashing with Odin TWRP, Phils, and stock recovery,(in the hopes of getting one to take so I could load a new ROM from SD card) and they all fail as well.
When I split any of the system images I can load a boot loader file from them, and it succeeds, but everything else fails.
Can anyone point me in the right direction, or am I completely hosed?
Click to expand...
Click to collapse
please help me i need de 4 files repair from this tablet

Try the forum thread started by djjiz, https://forum.xda-developers.com/galaxy-note-8-0/help/i467-4-4-2-t3537302... He posted the files and yes I was able to bring back my previously bricked AT&T Note 8.

SM-G925F Stuck at factory reset, unable to enter the recovery mode and flash firmware

Hello and sorry if this is the wrong category...
It's my first time making a thread on xda.
I've been looking for an answer for the past 2 hours, but I still have a bricked phone... As the title says, I can't enter the recovery mode anymore. I tried to do a factory reset (when I could enter the recovery mode) and the phone got stuck at erasing. Now I can't enter the recovery mode anymore. I downloaded a new firmware from sammobile for the SM-G925F. The firmware works since I used it on an other phone and everything worked just fine. The problem is, when I open Odin and add the .tar file to AP, it gets stuck at nand write and sometimes on boot.img. The phone isn't showing that it's downloading anything (it has no progress bar). At this point I have no idea what to do...
Some extra info that could be helpful:
The phone was bootlooping when I got to fix it;
I work in a kind of phone repair store where customers bring their phones for hardware and software repair. I do the software;
I've installed new firmwares on multiple phones and I never had something like this... Normally some time with google and xda could help me to find a working way to fix the problem, but as I said... I've been looking for 2 hours and the problem is still here;
I'm not a pro with Android and phones. I just like to learn new things and I'm still learning.
Could it be a hardware problem?

Can you show me your phone's download mode image to see where could be the problem?
Also, make sure you are flashing latest firmware, if you are downgrading it - than you will get such boot errors.

*Update*
I found out what was wrong. The eMMC chip was broken.

[Samsung] Galaxy Tab 3 SM-T210 / "Firmware upgrade encountered an issue"

Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie

Hyldran0 said:
Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Click to expand...
Click to collapse
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?

xdausernl said:
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
Click to expand...
Click to collapse
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.

Hyldran0 said:
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Click to expand...
Click to collapse
It is quite easy to turn the device off, for that to happen you have to press and hold the on/off button. You'll see that the device will shutdown and try to reboot and then finally shuts down again and stay off, then release the on/off button.
Are you sure trying to flash the correct firmware with correct changes, etc??
Please share with us the device and Android version, as well as the stock ROM version with changes you're trying to flash.
Put (copy and paste) the output of Odin below.
Another way to get the firmware flashed is by using Heimdall, but for that to happen you first need to rename the extension of the stock ROM (remove .md5 and leave .tar) and than extract all seperate pieces that are contained within the stock ROM.
All those extracted pieces from the stock ROM you have to upload seperately onto Heimdall and try to flash them to your tablet, one by one.
Heimdall you'll find 'here' or use FWUL instead which has Heimdall pre installed, download is to be found 'here' and install it on a USB medium a stick, to put FWUL onto USB, use Balena-Etcher and the download is to be found 'here'.
Micro USB cable does work, but if you're unsure, try another one and make sure using the correct drivers too.
Using Odin, make sure the tablet is recognised and 'connected' in Odin, also make sure 'repartitioning' is unchecked.
If you've used the wrong Odin version, flashing will fail!

You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!

Hyldran0 said:
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Click to expand...
Click to collapse
You're welcome.

Hi, complete novice here, does anyone know where I can get a working Firmware for my Tab 3 v7 (SM-210)?
I have searched through various forum articles here, and tried to install with several builds but none will install. The only one that gets anywhere near is the JASBR build by gr8nole. It appears to install, but on restart, the TAB just sits on the "Samsung Tab3" start screen.
I read that I may need to flash the firmware 4.4.4 (Kit Kat), but can't find it!
The unit is not totally bricked (yet), as I can run TWRP 2.8, with which I created a backup of the original build, but when I try to restore the backup, it fails at just over 31%.
Can anyone help please?