My Samsung Note II suddenly couldn't boot. It stays on the splash screen showing GT-N7105.
So I downloaded the stock ROM and tried the instructions at http://forum.xda-developers.com/showthread.php?t=2032849. I can connect, and the top left of the phone shows:
ODIN MODE
PRODUCT NAME: GT-N7105
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0
AP SWREV: 02
The Odin I am using is 3.09. There is no indicator of the progress of any download. I let it run for eight hours. Nothing seems to be happening. The Message box shows:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7105XXUFNJ1_N7105OLBFNJ1_N7105XXUFND3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
Then when I finally unplugged the phone:
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
How long does the download normally take and is there progress or status shown somewhere?
Thanks.
SimpleSimon2 said:
My Samsung Note II suddenly couldn't boot. It stays on the splash screen showing GT-N7105.
So I downloaded the stock ROM and tried the instructions at http://forum.xda-developers.com/showthread.php?t=2032849. I can connect, and the top left of the phone shows:
ODIN MODE
PRODUCT NAME: GT-N7105
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0
AP SWREV: 02
The Odin I am using is 3.09. There is no indicator of the progress of any download. I let it run for eight hours. Nothing seems to be happening. The Message box shows:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7105XXUFNJ1_N7105OLBFNJ1_N7105XXUFND3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
Then when I finally unplugged the phone:
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
How long does the download normally take and is there progress or status shown somewhere?
Thanks.
Click to expand...
Click to collapse
If you suddenly can't boot or even flash, then read about SDS.
yaro666 said:
If you suddenly can't boot or even flash, then read about SDS.
Click to expand...
Click to collapse
The phone boots but is stuck with the "Samsung Galaxy GT-N7105" screen. And I can see the download screen (Vol Down, Home, Powerr). Is this still considered a SDS?
SimpleSimon2 said:
The phone boots but is stuck with the "Samsung Galaxy GT-N7105" screen. And I can see the download screen (Vol Down, Home, Powerr). Is this still considered a SDS?
Click to expand...
Click to collapse
you mean it powers on, but doesn't boot. You can't flash, so compare to SDS.
If you can't do anything then emmc swap is the solution
This is not SDS. I had the same issue with my N7100. I flashed it with odin with the latest 4.4.2. Find the latest o.s for your phone and region. and follow the instructions word by word. Also, try changing the cable and the usb port on your computer.
You can see a green droid picture and a progress bar under it in your phone screen, while the flashing process is going in your phone. I think, the cable may be faulty or change the usb ports and redo it again. Good Luck....
Related
Help!
Phone kept crashing on occasion after an install of BBM for android. An Uninstall and Factory Reset in the settings did not help.
2 days ago it crashed and after powering it back on I get the:
Downloading Do not turn off target !!
&
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: NONE
QUALCOMM SECUREBOOT: ENABLE
I tried flashing back to stock via ODIN 3.6/3.7 but all I get is the below:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I747MVLDMF1_I747MOYCDMF1_1189444_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I've searched but this is as far as I can get
Kies firmware recovery was no help either.
Please Help!
I don't know what you did, but it looks like you need to send it to Samsung. If there isn't a PIT partition, that's bad, and you wouldn't want to mess with those, or you might end up with even worse a brick.
My phone randomly stopped working the other day. When its off, it'll start up on its own (without the power button being touched) but only get past the "samsung" screen a couple times and then shut back off. I tried flashing the stock firmware via odin but it fails every time (I've used versions 1.86, 3.04 and 3.09). As of now, my phone is totally useless. All I can do is put it into download mode. Any ideas?
This is what odin says every time
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone Screen:
ODIN MODE
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER AP SWREV: 3
SW REV CHECK FAIL : Fused 3 > Binary 0
Odon is failing because you are trying to downgrade the firmware. After 4.3 you cannot do this anymore. It looks like you probably updated to 4.4.2 via ota. Correct? If so there is no firmware you can flash as att refuses to release it.
Take your battery out and put it back in. If it tries to turn on by itself your power switch is bad and needs replacing.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Hi, I am not sure if I am posting at the proper forum but I know all the capable developers are here and I hope someone can help me. Please let me know if it is not. I tried to root my tab pro 8.4 with the original firmware by following a guide I found online using Odin to do the updating. Everything step seemed to be working but the tablet did not reboot and not it is stucked at the 'Downloading... Do not turn off traget!!' screen. On Odin side, it said "Pass" on top. I waited for a while but it did not reboot. After some research online, I tried to hold down the power key for a few seconds and the screen turned black and the the same 'Downloading...' screen came back. I tried holding down the power, up volume and home keys but got the same results everytime. Would anyone have any idea what had went wrong and how I can get my tablet working again? On the 'Downloading...' screen, it is showing the following at the top left hand corner:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SM-T320
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1,T1, R1, A1, P1
WRITE PROTECTION: Enable
UDC START
Thanks in advance.
ernsterw said:
Hi, I am not sure if I am posting at the proper forum but I know all the capable developers are here and I hope someone can help me. Please let me know if it is not. I tried to root my tab pro 8.4 with the original firmware by following a guide I found online using Odin to do the updating. Everything step seemed to be working but the tablet did not reboot and not it is stucked at the 'Downloading... Do not turn off traget!!' screen. On Odin side, it said "Pass" on top. I waited for a while but it did not reboot. After some research online, I tried to hold down the power key for a few seconds and the screen turned black and the the same 'Downloading...' screen came back. I tried holding down the power, up volume and home keys but got the same results everytime. Would anyone have any idea what had went wrong and how I can get my tablet working again? On the 'Downloading...' screen, it is showing the following at the top left hand corner:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SM-T320
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1,T1, R1, A1, P1
WRITE PROTECTION: Enable
UDC START
Thanks in advance.
Click to expand...
Click to collapse
What root method are you using? Try again this time make sure auto reboot is selected in odin.
Or... Force a reboot by holding Power, vol up and down, and home buttons for about 10 seconds and it should reboot. Or just tick auto reboot in odin
Airtioteclint said:
What root method are you using? Try again this time make sure auto reboot is selected in odin.
Click to expand...
Click to collapse
I followed blog.flexispy.com/root-galaxy-tab-pro-8-4/ and used CF-Auto-Root-mondrianlte-mondrianltexx-smt325.tar.md5. The auto reboot box and F. ResetTtime box were automatically selected when I started Odin3 v3.09. No other boxes were checked. The following is the listing under the message box:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-mondrianlte-mondrianltexx-smt325.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I got the big green PASS! at the top. When the tabpro tried to reboot, it showed 'Could not do normal boot' and 'ODIN MODE' in red' along with some other information as what I have listed on my original post and just stay on that 'Downloading...' screen.
Thanks!
ernsterw said:
I followed blog.flexispy.com/root-galaxy-tab-pro-8-4/ and used CF-Auto-Root-mondrianlte-mondrianltexx-smt325.tar.md5. The auto reboot box and F. ResetTtime box were automatically selected when I started Odin3 v3.09. No other boxes were checked. The following is the listing under the message box:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-mondrianlte-mondrianltexx-smt325.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I got the big green PASS! at the top. When the tabpro tried to reboot, it showed 'Could not do normal boot' and 'ODIN MODE' in red' along with some other information as what I have listed on my original post and just stay on that 'Downloading...' screen.
Thanks!
Click to expand...
Click to collapse
Ooh, I think you flashed the wrong model. There's no telling what dsmaged has been done. You have the wifi model or the lte?? Here's the wifi model link http://download.chainfire.eu/383/CF...ifi-mondrianwifixx-smt320.zip?retrieve_file=1
Oh no! That's bad! So what can I do now?
ernsterw said:
Oh no! That's bad! So what can I do now?
Click to expand...
Click to collapse
Try Flashing the stock firmware in odin. Because you are still able to get into download mode hopefully that's a good sign. Just to be sure you have the wifi model correct? Get the full firmware here
http://forum.xda-developers.com/gal...320xar1ank1-extracted-stock-firmware-t2954549
My tabpro is the 8.4 wifi version. Should I even bother to try flashing the correct firmware to see if it works first or just go with the stock firmware? Thanks for you help!
I flashed the stock firmware and everything got back to how it was before. I was then able to root the device with the correct link you provided. Thanks very much for you help!!
I was running Cyanogen Mod on my phone, but my camera was acting odd, so I decide to flash back to stock to see if this would fix the issue.
I downloaded a stock firmware, and went through the steps to flash my phone. It seemed to work, but after completion, my went into a reboot loop.
When I try to flash again, i get the following output from odin
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_stock_system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My Download mode screen reads the following:
ODIN MOde
PRODUCT NAME: SCH-I605
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
RP SWREV: A3
I tried this with a few firmwares, and a few versions of ODIN. I can get into download mode, but holding power, menu and volume up won't get me into recovery mode.
Did I just kill my phone?
I wanted to add a small tidbit. Could a reboot loop, and the error in ODIN be caused by a low battery?
I managed to make progress, but I am not quite there yet.
I flashed the PIT file from here downloadandroidrom [dot] com/file/GalaxyNote2/rooting/GalaxyNote2UnlockVerizon.zip (sorry, can't post a real link yet)
And after that, I was able to get past the failed step, and ODIN actually completed. However, right now, when I try to turn on my phone, nothing happens. When it's plugged in, it's just showing the battery icon, and the charging light is not on.
I ordered an external battery charger from eBay, to make sure that I have a full battery, but is there anything else I can do in the meantime?
EDIT:
I managed to fix it. Flashing the PIT file, and then flashing an official firmware did the trick. I think the first ROM that I tried was the problem.
Hey,
I have some old samsung ace 2 that I was experimenting around with, wanted to try and get some 5.1.1 ROM on it. But first I figured I needed to get some kernel on it, though I did something which now means that during bootup it is stuck on the samsung galaxy ace 2 logo. I can access ODIN mode, though cant access recovery mode. The battery mode also seems to be broke too as it just displays a loading symbol. So far I have flashed the EK kernel on it with what seems to be a success according to ODIN mode. Also note that Samsung KIES tries to connect to my device in ODIN mode but it never connects and troubleshooting doesnt do anything.
I tried to flash stock firmware to it through the odin software whilst my phone was in odin mode, though it displays a bunch of stuff in the odin pc software then attempts to reboot my phone though it just gets stuck on the boot logo again without odin really doing much here are the logs:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8160XXLD8_ready_to_root_ANT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> kernel.bin.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Reckon my device is still salvagable from this hole I have dug myself in?
i am also having the same problem. tried to flash stock firmware with and without pit, still can't work :crying:
and i don't have jtag and don't know how to use it even if i have jtag :crying: