Hello guys
I just want to say i'm no where near an expert on this, and i feel i have tried to fix this issue but made it way worse in the process so please be gentle.
This morning i woke to my Samsung Note 2 N7100 just hanging on the samsung start up screen. Tried all the normal things, taking bat out, restarting many times etc. No luck, just kept hitting the samsung screen and freezing.
After some goggling i found my way to the Recovery screen (power+vol up+home) but when it was loading there was a lot of Red Error messages. It loaded the options screen and i tried to do a factory reset. A lot more error messages to basically then say failed. Tired it a few times and even tried to clear the cache but kept failing.
So i tried loading it into Kies, which didn't connect to the phone so i couldn't reinstall the software.
So i decided maybe i need to flash the phone. I downloaded a stock Rom for the phone (i was on Kitkat so found that version) Used odin and half way through the install it came up failed.
Since then the phone only displays the "Fireware upgrade encountered an issue. Please select recovery mode in Kies"
So i went back to Kies but still couldn't find the phone. It also won't let me go back into recovery mode, only into download mode.
I thought maybe i'd give the flashing another go but this time when i flashed it, it just hangs trying to find Pit but eventually fails saying no Pit.
From research it appears that the partition is buggered. All the research i've done seems to say stay away from messing with the partition. some people say its Emmc thats gone and its game over but others say there is hope still.
I can still access the Download menu and the product name is still GTn7100, Binary still samsung official so i am holding out hope there is some life left in it. I'm on my last legs now so open to all offers for solutions. Please assist if you can
Thank you in advance
Andy
If you're able to get in download mode.. Maybe try flashing a custom recovery (TWRP) which you could try full format in it then install a ROM using it.. Also, maybe trying to use a CM based one? Though you might need a external SD card to move files from PC to your phone.
I don't know if this would work, but try it.
Sent from my Galaxy Note II using Tapatalk
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.
Symptoms: Over a period of weeks, possibly months, the phone started rebooting itself more and more frequently. Now I have reached the point where my phone bootloops, often at the Note II logo, sometimes it goes on and gets stuck on the ROM's logo for ages then bootloops again. Occasionally after an age (hours) and if I am lucky the ROM may load up but then it soon starts bootlooping again. I also noticed that one time there was some graphical distortion on the ROM's animated logo. TWRP Recovery and Download Mode both work perfectly fine.
What I have done Wiped everything, reinstalled the ROM through recovery which achieved nothing. I then tried a fresh install of the stock ROM with ODIN (update bootloader ticked). Although the ODIN install went fine, I still have exactly the same problem.
What should be my next step? Repartion with PIT?
Well I went ahead and re-partitioned with a PIT file, still no luck. I guess this must be a hardware issue.
makeyourself said:
Well I went ahead and re-partitioned with a PIT file, still no luck. I guess this must be a hardware issue.
Click to expand...
Click to collapse
You have what is known as Sudden Death Syndrome (SDS). In short the eMMC chip has failed. It or the motherboard needs to be replaced.
Flashing PIT will not help
Sorry about that
Check battery , update phone software .go to a repair centre , u may fry it like me .
Sent from my GT-N7100 using XDA-Developers mobile app
Hi everyone I'm hoping someone can help. My note 7 had the boot loop. I was stuck in recovery mode and had DM verity and failed to set up dirty target errors. Smart switch wouldn't recognise my phone to do an emergency firmware recovery. I tried to reflash firmware using Odin and had no joy. Kept trying and eventually got it to flash. It died right at the end of the flash and I got a green screen saying the firmware failed to install and to do an emergency firmware recovery. At least now smart switch found my phone so I did the recovery. After it had taken hours to download it flashed 100℅ on the pc but when the phone rebooted and I got the little android dude saying installing new firmware. The counter on the phone started going up but jumped to 32% from 25℅ then stopped. Then said erasing rebooted and was back stuck in recovery but with just the DM verity error. If I flash the AP through Odin the exact same thing happens. Fails at 32℅ then does the same. Is there anyone come across anything similar or any suggestions? I I'd really appreciate it thanks.
zanderswigan said:
Hi everyone I'm hoping someone can help. My note 7 had the boot loop. I was stuck in recovery mode and had DM verity and failed to set up dirty target errors. Smart switch wouldn't recognise my phone to do an emergency firmware recovery. I tried to reflash firmware using Odin and had no joy. Kept trying and eventually got it to flash. It died right at the end of the flash and I got a green screen saying the firmware failed to install and to do an emergency firmware recovery. At least now smart switch found my phone so I did the recovery. After it had taken hours to download it flashed 100℅ on the pc but when the phone rebooted and I got the little android dude saying installing new firmware. The counter on the phone started going up but jumped to 32% from 25℅ then stopped. Then said erasing rebooted and was back stuck in recovery but with just the DM verity error. If I flash the AP through Odin the exact same thing happens. Fails at 32℅ then does the same. Is there anyone come across anything similar or any suggestions? I I'd really appreciate it thanks.
Click to expand...
Click to collapse
I'd advise you to take it back to Samsung and enroll for the recall. Regardless of the combustible battery, This is one of the primary reasons why they initiated the recall. This cannot be resolved even at Samsung service centre. So call Samsung and hand it over to them for recall.
I had the same issue. Couldn't recover.
Yup the recall is the perfect opportunity to save yourself from disaster.
Sent from my Nexus 5X using Tapatalk
Yeah that's what I thought. I'm already enrolled but now they say my carriers handling it. Just thought I'd throw it out there just to see if anyone's had the issue with getting stuck at the same percentage each time. I was doing my best to get it running as itll be at least a couple of weeks for a replacement they say. Knowing my carrier it's probably going to be months. May end up just getting something else it's a shame because when it worked it was great but they've done such a terrible job of getting it ready for general release. Thanks anyway bud.
Are you using the original or at least a high quality cable? Have you tried different USB port on PC? Even try a different PC. Also, try a slightly older version of Odin. If any of these make a difference, you at least have an indication that its worthwhile to keep trying.
Sent from my SM-N930T using Tapatalk
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.