Galaxy Note II (GT-N7100) Resuscitation - Galaxy Note II Q&A, Help & Troubleshooting

Its been a long time since I booted my Galaxy Note-II (GT-N7100) as I use an iPhone and Nexus 5 as my daily drivers.
The phone wont boot past the Samsung Galaxy Note II GT-N7100 logo. I am able to access the recovery and download mode as well, and I have flashed the latest stock rom from Sammobile using the Odin. The flashing was successful. however the phone doesn't boot past the logo. Also the phone will not power up unless connected to a PC, it wont power up even when connected to a charger and will immediately shut down when the USB cable is disconnected from the PC. I flashed TWRP 3.0.2 Custom Recovery using the Odin and tried installing CM 13 based Rom through the mem card, however the log reads patching image unconditionally and also that "Failed to mount /system" (invalid argument). The phone when restarted into recovery can no longer mount the /system partition. However on flashing the stock rom using Odin, the /system partition is available for mounting. The recovery log also shows MTP enabled, but my PC doesn't detect the phone when in recovery, it only detects the phone in Download mode. I have the Samsung drivers installed. Since the phone is not being detected in recovery I am unable to use the adb.
I am out of ideas and request your suggestions other than approaching a service centre.
If I can somehow access the phone via ADB, I might be able to check the memory partitions for corrupt units, and possibly create a custom PIT file to repartition and suit the available memory units.

Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?

audit13 said:
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
Click to expand...
Click to collapse
Thanks a lot.
Tried your method and finally the phone has booted into the OS.
Had to replace the battery with another spare one in the process.
However the phone is still not being detected by the PC unless it's in Fastboot/ Download mode.

When connected to a computer, does anything appear on the phone screen? If you're using Windows, nothing new appears in device manager?

sorry to jump in this thread but i am having a similar problem
my completely stock tmobile note 2 is stuck on the samsung logo
i have never flashed it or done anything to it
my phone was working really slow, freezing up and battery draining fast
so i did a hard reset and it fixed the problem of running slow and freezing up for a week or so but battery drained fast
so i bought a replacement battery from ebay and installed it and the next day i restarted my phone and it froze on the samsung logo
i tried turning it off and on and still the same thing
any suggestions or should i start a new thread?
fyi i am a noob

Related

[Q] Galaxy Nexus stuck at Google logo, cant mount directories using TWRP/CWM recovery

Hi,
Is there any possible way to get pictures off of the phone when in this state?
- Normal startup gets stuck at Google logo
- Running TWRP or CWM recovery cannot mount any folders (/system, /data, /cache, etc.), cannot backup any folders, cannot wipe cache
- also see this error mounting /dev/block/platform/omap when in recovery
Is there any possible way to get the pictures off of this phone?
Phone got to this state after a crash. Could not power down so did a battery pull, reinserted battery, and powered on and has been getting stuck at Google logo ever since.
Phone is stock 4.3 unlocked using Nexus Root Toolkit.
On a side note at the exact same time the battery no longer charges, phone no longer powers up with battery alone, to power up I need to remove battery, connect to a compupter using usb, then replace battery. Then can power up phone normally or enter fastboot.
Thanks.
razor266 said:
Hi,
Is there any possible way to get pictures off of the phone when in this state?
- Normal startup gets stuck at Google logo
- Running TWRP or CWM recovery cannot mount any folders (/system, /data, /cache, etc.), cannot backup any folders, cannot wipe cache
- also see this error mounting /dev/block/platform/omap when in recovery
Is there any possible way to get the pictures off of this phone?
Phone got to this state after a crash. Could not power down so did a battery pull, reinserted battery, and powered on and has been getting stuck at Google logo ever since.
Phone is stock 4.3 unlocked using Nexus Root Toolkit.
On a side note at the exact same time the battery no longer charges, phone no longer powers up with battery alone, to power up I need to remove battery, connect to a compupter using usb, then replace battery. Then can power up phone normally or enter fastboot.
Thanks.
Click to expand...
Click to collapse
Have yu tried "adb pull" command..? might be helpful...
I've tried running pull files in Nexus Root Toolkit and that doesnt work. Is this running the same thing as you are suggesting? Now the phone wont turn on plugged into USB with or without the battery. argh!
razor266 said:
I've tried running pull files in Nexus Root Toolkit and that doesnt work. Is this running the same thing as you are suggesting? Now the phone wont turn on plugged into USB with or without the battery. argh!
Click to expand...
Click to collapse
do you get a device called omap 4400 driver installation message whenever you connect the usb??

[Q] ROM update fail, cannot flash with Odin

Hi,
My brother's SGH-T989D phone (Koodo / Telus) crashed during an android update. Now, the phone boots to a black screen with the taskbar on top. There is no menu screen anymore. No apps at all. Doing a factory reset via the recovery mode does not change anything.
My PC does not detect the phone. Therefore, I am unable to install a new ROM with Odin. Here are all the infos I have :
1. The phone boots, but there is absolutely nothing except the task bar (I can toggle the wifi and bluetooth on and off, thats it...). There phone says preparing SD storage upon booting. There are no SD card and SIM card.
2. The phone is able to go into recovery and download modes.
3. My PC does not detect the phone. I know the Samsung drivers, Odin v3.07 and USB cable are working properly because I am able to connect my own phone which is also a SGH-T989D.
4. In recovery mode, there is a dead android with a red triangle with an "!" in the background.
5. It used to have the stock gingerbread Koodo ROM, and was probably updated over the air to the newest ICS from Koodo.
6. The phone was never rooted or messed with. I don't think it was ever connected to a computer before.
7. It is not under warranty anymore.
I've spent hours trying to get it recognized by the computer. I've tried putting the ROM on the SD card and applying the update via external storage in recovery mode. I get a message about Signature verification failure.
I've tried cleaning the micro-usb slot. Blowing in it resulted in the computer saying "Unknown device malfunctioned" a single time, which leads me to believe it only did that because some saliva created a short somewhere in there. The connections look clean.
I'm about to throw this phone off the building. What is wrong with it?
**EDIT**
Forgot to mention...the phone does charge when connected to the usb cable.
kamikazee1989 said:
Hi,
My brother's SGH-T989D phone (Koodo / Telus) crashed during an android update. Now, the phone boots to a black screen with the taskbar on top. There is no menu screen anymore. No apps at all. Doing a factory reset via the recovery mode does not change anything.
My PC does not detect the phone. Therefore, I am unable to install a new ROM with Odin. Here are all the infos I have :
1. The phone boots, but there is absolutely nothing except the task bar (I can toggle the wifi and bluetooth on and off, thats it...). There phone says preparing SD storage upon booting. There are no SD card and SIM card.
2. The phone is able to go into recovery and download modes.
3. My PC does not detect the phone. I know the Samsung drivers, Odin v3.07 and USB cable are working properly because I am able to connect my own phone which is also a SGH-T989D.
4. In recovery mode, there is a dead android with a red triangle with an "!" in the background.
5. It used to have the stock gingerbread Koodo ROM, and was probably updated over the air to the newest ICS from Koodo.
6. The phone was never rooted or messed with. I don't think it was ever connected to a computer before.
7. It is not under warranty anymore.
I've spent hours trying to get it recognized by the computer. I've tried putting the ROM on the SD card and applying the update via external storage in recovery mode. I get a message about Signature verification failure.
I've tried cleaning the micro-usb slot. Blowing in it resulted in the computer saying "Unknown device malfunctioned" a single time, which leads me to believe it only did that because some saliva created a short somewhere in there. The connections look clean.
I'm about to throw this phone off the building. What is wrong with it?
**EDIT**
Forgot to mention...the phone does charge when connected to the usb cable.
Click to expand...
Click to collapse
IDK if this will help you. IF the phone isn't rooted or a custom recovery installed I don't believe you can reinstall the ROM. It does say 'signature verification error' so you might be able to turn off MD5 checking before install. It will be in the settings menu if TWRP is used. I don't believe its an option to do if on stock recovery.

Samsung S3 (tmo) soft bricked, encrypted, USB debugging off

Hi,
Summary: Was running Cyanogenmod 10.2.0 and tried to update to 10.2.1. Phone won't boot. Using CWM recovery 6.0.4.3. Factory Reset reports that it can't mount / clear /data (due to encryption?). Can get phone into CWM recovery and Download mode. Haven't been able to successfully connect to PC (ADB or Odin) even though I have samsung drivers.
I do have an unencrypted SD card in the phone so my normal way of flashing is to connect SD card to PC, download, then in CWM recovery to install ZIP from SD card.
Looking to get into any good state - Cyanogenmod 10.2.1, or 10.2.0, or heck go back to stock.
**** I think the answer might be use ODIN and flash back to stock, I see some guides but haven't been able to get ODIN to "see" my phone *****
Details
I had downloaded Cyanogenmod update to phone using "About this phone" menu and when I tried to "Install it" from that window the machine booted into recovery, immediately failed, and rebooted. The phone is encrypted (work requires this) and I discovered Cyanogenmod saves the download to encrypted phone storage and CWM recovery doesn't support encryption.
Downloaded 10.2.1 to my SD card and flashed it. (no back-up, no wiping of cache). Installed successfully, reboot asked me for my encryption password, Android optimized apps, rebooted, encryption password, then blue spinner spins forever.
From here I started my troubleshooting:
- I flashed back to 10.2.0 then flashed Gapps again, no change.
- Reading about boot.img I installed ADB and SDK Manager and tried connecting and flashing boot.img. ADB devices shows up empty. I have installed Samsung drivers.
- Researching going back to Stock points me to installed Triangle to reset my custom ROM count - but I can't boot.
Thanks in advance.
Matt
[Solved] This is for anyone who happens to read this wondering if their phone is screwed. Relax! If you can get into Download mode and Odin can see your phone, you'll be o.k.
Turns out the machine and cable you use do matter. I tried for days connecting using my MAC running Windows 7 Virtual Machine. Once I switched to my Win7 laptop and used the original Samsung cable things starting working out more smoothly.
Steps:
1) Get Odin (mine was 3.09) and run as admin. If you see an error in Korean it's because you have to unzip the entire Odin folder.
2) Get stock firmware for t-mobile. There's only 1 firmware file, I didn't need a PIT nor a specific recovery step. The t-mobile firmware includes everything I needed. Flashing failed in Odin saying Complete Write failure. This had me stumped for hours and hours. When I switched to stock cable and Win7 laptop it succeeded. I never had to check Nand erase all or repartitian (almost did in desparation though). Flash took about 10 minutes but eventually PASSED.
3) However, when it rebooted it asked for encryption key and my old one didn't work. Turns out their are more steps. This scared me.
4) Reboot into recovery (up, home, power) which gave a bunch of scary error messages. Actually those listed at the bottom in http://forum.xda-developers.com/showthread.php?t=1840030.
5) Factory Reset then Wipe Cache
6) Reboot
Now I'm back at stock and breathing a sigh of relief. Unclear if I'll ROM back to Cyanogenmod.
I spent hours and hours reading discussions and going down one dead end after another. I'd say it was like looking for a needle in a haystack but it was the complete opposite. It was like looking for a specific needle in a sea of needles. Every search query yielding tantilizing results and a plethora of step by step guides that ultimately didn't work. A very frustrating experience all around. Good luck to anyone who reads this.
Hi Matt
Similar thing happened to me last night. I am/was using Omni-Nightly build. I plugged it in to the charger before bed, and it rebooted, saying upon reboot - "Encryption Failed" and saying the only way to recover would be to wipe the machine and start again, it then rebooted and all I get is the Samsung boot screen.
Tried rebooting, wiping, everything, Odin, Android Toolkit, nothing works. It shows up on my Linux PCs but not accessible, but not windows at all.

Help -- Might Have Bricked Tab S 10.5

As the subject line says, I'm worried I bricked my Tab S. Awhile back I flashed my tablet to IronRom. I hadn't used it in awhile and this morning I attempted to update via OTA Updater. I was able to download the update and reboot into TWRP for the install, but the tablet froze while I was wiping the cache and I had to restart. I was able to reboot into TWRP and installed the ROM (without erasing cache or data) but now I can only boot as far as the "Galaxy Tab S" screen. I can no longer boot into TWRP, though I can boot into Download Mode, but my computer won't recognize the tablet. Is there anything I can do or am I screwed?
Edit -- My computer recognizes the tablet when I open Kies, but it tries connecting for a few minutes then times out.
CarQuery8989 said:
As the subject line says, I'm worried I bricked my Tab S. Awhile back I flashed my tablet to IronRom. I hadn't used it in awhile and this morning I attempted to update via OTA Updater. I was able to download the update and reboot into TWRP for the install, but the tablet froze while I was wiping the cache and I had to restart. I was able to reboot into TWRP and installed the ROM (without erasing cache or data) but now I can only boot as far as the "Galaxy Tab S" screen. I can no longer boot into TWRP, though I can boot into Download Mode, but my computer won't recognize the tablet. Is there anything I can do or am I screwed?
Edit -- My computer recognizes the tablet when I open Kies, but it tries connecting for a few minutes then times out.
Click to expand...
Click to collapse
Reflash tarp through Odin and then try to reboot recovery. I have my Tab S 10.5 LATE on that same room, no problems.
If your computer can't recognize your tablet in the Odin program, try using another USB cord.

Samsung GT-N5110 - Stuck in Boot Loop, Can't flash Due To "Write Error!!"

I have a Samsung Note 8 GT-N5110 (WiFi only) that is stuck at the Samsung logo.
This started after there was an attempt to flash a non-stock firmware and the device powered off before it was done.
When I attempt to enter Recovery Mode (Volume Up + Home + Power) it displays "Write Fail!" in upper left of the screen.
I am able to enter "Download Mode", so I've tried flashing a stock firmware using Odin.
I've tried both a One-Click recovery based on ODIN3 v1.81 and also tried Odin3 v3.12.10.
Each time, Odin fails, with a message:
write fail!!
SW REV. CHECK FAIL. DEVICE:2, BINARY:1
I've tried various versions of firmware, and nothing seems to work.
I've tried disconnecting the battery for a minute or so, and it still fails.
Any ideas what else I can try?
I have screen shots and detailed logs of what I've been getting, if that helps.
Thanks!
Believe it or not, I still have this device, and have not been able to get it to work!
So, I'll just revive this zombie post more than 2 years later, and see if anyone has any idea on what to do.
I'm in the fourth (fifth? sixth?) week of corona-quarrantine, so plenty of time to look into this!
The tablet needs more power than the computer's USB port can deliver. Thus, it will slowly drain the battery while connected to the computer and working via ADB, Odin or Heimdall. Seems like that has been the case in your earlier attempt, resulting in a corrupt flash memory. I can't tell if it's really defective or just corrupt and in need of formatting.
I'd try to:
1) Charge the battery
2) Copy LineageOS to the MicroSD card
3) Boot into download mode and install TWRP only via Odin or Heimdall. If this works,
4) Boot into Recovery (TWRP, not the stock one!), connect the charger to keep it powered and go from there (wipe and repair the internal flash, install LineageOS)
If this doesn't work, try if you can find any service functions in Odin or Heimdall to wipe and repair the internal flash.
Good Luck!
Ektus.
Hi Ektus,
Thanks for your help!
I will try as you suggested, and see what happens.
I'll let you know how I do.
Thanks!
I had similar problem. What I did is just change the USB cable to new.

Categories

Resources