Database Info

Boot process hangs after "Samsung Galaxy Note 10.1" logo

Hi,
I hope someone is able to help me and I did not create a new frisbee.
After unrooting my N8000 by flashing stock with ODIN with result:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8000XXCMA5_N8000OXACMA5_828057_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Now the tablet hangs on the first logo after boot. Recovery is not accessible. Tried now serveral ways:
- Flash with different stock roms (4.0.4, 4.1.1, 4.1.2)
- Flash with different CWM
- Flash with stock recovery
I can acces ODIN download, I cannot access recovery or system.
Any ideas?

astymov
Sorry to push this but if I cannot change the situation I will need to send it from Egypt to Europe tomorrow :crying:. Thanks for your understanding.

Just checking but when you flashed with ODIN did you untick "Re-partition"?
If you didn't you will need the pit file to repartition the note before doing anything else, not sure where to get...
---------- Post added at 07:36 AM ---------- Previous post was at 07:34 AM ----------
Also to check again to see if you're going into recovery, with power off you hold volume up and power in until the samsung logo appears, release power button but continue holding in volume up until recovery appears... Might be simple but so many people do it wrong...

It took me 2 flashings of the original stock rom. Mine hung on the logo after the first flash. Worked after the second time

I tried to flash it with different ROMS now several time, flashed different CWMs and stock recoveries without any positive result. In the beginning I tried to flash withour re-partition, yesterday I organized a PIT file but as well no success, re-partitioning is not possible. I think, the partition table is protected on the N8000. Anyway, tanks for your help, I will send it to service today (with custiom binary download 11 counts ).

cameldive said:
I tried to flash it with different ROMS now several time, flashed different CWMs and stock recoveries without any positive result. In the beginning I tried to flash withour re-partition, yesterday I organized a PIT file but as well no success, re-partitioning is not possible. I think, the partition table is protected on the N8000. Anyway, tanks for your help, I will send it to service today (with custiom binary download 11 counts ).
Click to expand...
Click to collapse
sorry to hear, did you try flashing the same ROM 2 times consecutively after a wipe and factory reset? not sure I was clear in my first post

jaydubbbbs said:
sorry to hear, did you try flashing the same ROM 2 times consecutively after a wipe and factory reset? not sure I was clear in my first post
Click to expand...
Click to collapse
I tried to flash it several times, with same and diefferent roms w/o positive result. Wipe and factory reset was not possible anymore as I was not able to get into recovery anymore. Anyway, the tab is on the way to a service station now. Thanks for your help.

note 10.1 is blocked in booting

hello
I have the Samsung Galaxy Note 10.1 in 8013 16 GO there, exactly.
I intallé anderoid jelly bean 4.1.1 OTA and did not finish the tablet and restart nonstop. I started handling but nothing goes as planned, ODIN said fail Action! and my tablet is in download mode. And when I reboot I have a small andriod man with the percentage bar with the screen that pops by gray bars. suddenly I think I scrub the tablet and I do not really know what
thank you in advance for helping me because odin know my tablet (the tablet comes into download mode and not in recovry mode) it may not complete the installation with the following message:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

3achour said:
hello
I have the Samsung Galaxy Note 10.1 in 8013 16 GO there, exactly.
I intallé anderoid jelly bean 4.1.1 OTA and did not finish the tablet and restart nonstop. I started handling but nothing goes as planned, ODIN said fail Action! and my tablet is in download mode. And when I reboot I have a small andriod man with the percentage bar with the screen that pops by gray bars. suddenly I think I scrub the tablet and I do not really know what
thank you in advance for helping me because odin know my tablet (the tablet comes into download mode and not in recovry mode) it may not complete the installation with the following message:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Re download factory rom and flash again in odin.. . You can also go in the recovery and clear cache and so on.. This will often stop a boot look . But it looks like you have a bad d/load

I'd agree with that.
I find it best to download the roms from Sammobile as they generally provide an MD5 sum you can check to make sure its not a bad download. Especially when using ODIN 4.03/07... ODIN 4.03 does the check before it flashes and ODIN 4.07 checks when the .tar file is selected.

temp
how temp for odin finish their installation
I think it's hang on: "<ID:0/006> NAND Write Start!! "

erica_renee said:
Re download factory rom and flash again in odin.. . You can also go in the recovery and clear cache and so on.. This will often stop a boot look . But it looks like you have a bad d/load
Click to expand...
Click to collapse
I have not access in the recovery mode

3achour said:
how temp for odin finish their installation
I think it's hang on: "<ID:0/006> NAND Write Start!! "
Click to expand...
Click to collapse
odin did not finish the installation process about 2 hours and even post thank you for helping me

You need to download the rom again to see if it's not a corrupted copy. Use a PC to download it from sammobile.com.
If the flash file you are using is corrupt you can flash it til this century ends and it won't work...
If it still doesn't get past nand write then I believe you may need a pit file to repartition your internal memory. THIS IS A VERY DANGEROUS OPERATION. Make sure you have the correct pit file and if possible get it with an MD5 checksum so you know there is nothing wrong with the downloaded file. It MUST be for your device or bricking may occur, it MUST not be corrupted or bricking will occur.
Good luck and remember, you have been warned...

Galaxy Note 10.1 GT-N8000 Stuck in Bootloop, Can't Access Recovery

Hello all,
My tablet note 10.1 N8000 (3G, Wi-Fi, 16 GB) suddenly got stuck in bootloop. I was not trying to flash anything when it did so, nor did I flashed anything recently before the bootloop (although it seemed to constantly freeze before the bootloop when trying to switch between my two whatsapp accounts that I have using Titanium Backup which allows creating more than one account in all apps).
I did however root the device when I bought it in 2012 and it was the only time I did so, and I still have USB debugging mode on.
The device would bootloop in the first Samsung logo most of the time, but on rare occasions it would move to the second animated logo and get stuck repeating the animation forever.
I can only access Odin Download mode, but cannot access recovery mode (when I try to do so, it shows the first Samsung logo, then attempts to go into recovery but only shows a lit black screen then reboots).
Here are the steps I did (might help some of you, but unfortunately didn't help me):
1) I tried flashing a custom recovery (CMW, Philz touch, TWRP, and stock recovery) through Odin (Odin 3 version v3.10.6):
- Put the .tar file in AP slot then put device in download mode (power key + volume down), then plug device into my computer.
- Check only auto restart and F. time reset.
- Here's what it says after flashing:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> 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)
2) I tried flashing stock rom through Odin:
(Roms I tried: N8000XXCMF1, N8000XXUDOF1, N8000XWALG7, N8000XXCMA2, N8000XXUDOF1)
- I put the .tar.md5 file in AP and follow same steps above, here's what Odin says after flashing:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<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)
3) I tried following the post here:
http://forum.xda-developers.com/galaxy-note-10-1/general/n8000-stuck-samsung-logo-t3212923
I followed everything until the part where I have to access recovery (because I could not access recovery still to flash rom from recovery). Here's what it says in Odin after it's done:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300_Repair_efs.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> efs.img
<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)
But again it did not work even though it always says "PASS"! And I also tried flashing stock rom after trying this method through Odin, shows success but still stuck in bootloop.
I don't know what else to try really. I will not take it to support to fix it, either I fix it myself or use it as a cutting board.
If anyone has any ideas please reply. I'm sure there are more things to try.
EDIT:
- Is there a way to clear cache without accessing recovery (since I can't access it)? Lots of people say it worked after clearing cache.
- Is Nand erase all an option? I wish someone would explain it in details instead of telling me not to do it without saying exactly why.
- Could the problem be in hardware? How can I know if so?

NaND ERASE WILL KILL THE PRODUCT .

JJEgan said:
NaND ERASE WILL KILL THE PRODUCT .
Click to expand...
Click to collapse
So you mean that it will erase everything even the Odin download mode and the Samsung logo? Why would they include this option then? I don't see any practical use of it :/

No help?

RHAddict said:
So you mean that it will erase everything even the Odin download mode and the Samsung logo? Why would they include this option then? I don't see any practical use of it :/
Click to expand...
Click to collapse
Odin is a tool that we are able to borrow .
You could try recovery via KIES .

RHAddict said:
No help?
Click to expand...
Click to collapse
HI RHAddict,
It happened to my Note GT-N8000, if a Hardware failure. If you send to SAMSUNG service center it will cost u around US$ 200 for motherboard replacement. But i manage to find a mobile service center, the technician said it only 1 of the chip in motherboard out of service. I got my tablet fixed just US$ 50-60. Now is working as is it before.
TQ

My Samsung 8010 has just gone exactly the same way. Cannot enter recovery mode, just get a blank lit screen for a second then goes back into a reboot cycle and never gets past the Samsung logo. Did you get anywhere with fixing it, or have you given up? Was thinking of taking mine to a service centre, but probably not worth it?

Successful Flashing via Odin but stuck at Samsung Logo and cannot access recovery

Hi,
I'm a new member for this community with a bit of a limited experience in Flashing.
My Samsung Galaxy Tablet 10.1 GT-N8000 was stuck in a boot loop when turning on and even when charging.
I decided to check the xda forums and similar threads regarding my issue to try out some resolution to my problem:
What I have tried so far was:
1. Tried doing the standard hard reset which was Power + Volume +/Up = No response
2. Tried Flashing the Stock ROM I got from sammobile for my region using different versions of Odin( just to check)
The flash goes successful with the following logs in Odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006> param.bin
<ID:0/006> recovery.img
<ID:0/006> sboot.bin
<ID:0/006> system.img
<ID:0/006> tz.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
But when it reboots its stuck at the Samsing Galaxy Note 10.1 logo and it stays there for the longest without a hint of turning off.
As per reading previous threads about the same concern, I tried to:
-Access the recovery by pressing Power+Volume up - the screen will display the Samsung logo, then go to a blank screen the just reboots back to the "infinite logo".
-As I was desperate, I already had tried to re-flash the tablet together with a PIT file and the firmware above as well as a combination of the PIT file and just TWRP(openrecovery-twrp-2.6.1.0-p4notewifi) or Philz Touch (philz_touch_6.12.8-i9500.tar), it results to the same blank screen > reboot> infinite logo scenario.
I'd like some humble assistance from established members who had resolved this issue as I am in dire need for having this tablet fixed.
Thanks a bunch and in advance as well

Possible probable wrong PIT file used .Certainly you used wrong model recovery its not I9500 is it .
See multiple identical posts .

JJEgan said:
Possible probable wrong PIT file used .Certainly you used wrong model recovery its not I9500 is it .
See multiple identical posts .
Click to expand...
Click to collapse
Thanks for the reply.
The I9500 that I tried was for recovery file, but since it did not work, I also tried the TWRP as indicated in the post but still it had the same results
*Correction - the recovery file I used for Philz Touch was philz_touch_6.48.4-n8000.tar.md5 as JJEgan stated I used the the wrong model of recovery*
The PIT file that I used was the same one that was on this post : https://forum.xda-developers.com/galaxy-note-10-1/general/n8000-stuck-samsung-logo-t3212923 - Since he reported success in his endeavor to revive same device, I used the same PIT file, but still the same results.
If anyone could still help out, I'll be more than grateful.

thunderhavoc said:
Thanks for the reply.
The I9500 that I tried was for recovery file, but since it did not work, I also tried the TWRP as indicated in the post but still it had the same results
*Correction - the recovery file I used for Philz Touch was philz_touch_6.48.4-n8000.tar.md5 as JJEgan stated I used the the wrong model of recovery*
The PIT file that I used was the same one that was on this post : https://forum.xda-developers.com/galaxy-note-10-1/general/n8000-stuck-samsung-logo-t3212923 - Since he reported success in his endeavor to revive same device, I used the same PIT file, but still the same results.
If anyone could still help out, I'll be more than grateful.
Click to expand...
Click to collapse
Hello, did you ever find a solution? I'm facing a similar problem with my unit.
Thanks.
Sent from my SM-N920C using Tapatalk

I'm facing a similar problem with my unit.

Lack of information does not help.OP is i9500 not Note 10.1.
Read the thread. Search your problem.

[Q] Stuck in cm.bin while flashing new stock rom

Hi there,
I'm stuck on odin with this log
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 3446 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> cache.img
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I already add Nougat on my phone this was the image.
G920FXXU5EQL4_G920FOPT5EQL4_G920FXXU5EQLB_OPT
Click to expand...
Click to collapse
i have flashed this before with Odin v3.12.3
My story
Yesterday i root my phone with this image below by chainfire and it was working perfectly
CF-Auto-Root-zeroflte-zerofltexx-smg920f
Click to expand...
Click to collapse
However the propose to root was not working very well so i unroot with superuser. And since that dont solve the problem i wipe Delvin/cache/data to have a full clean install.
So it start to say that i need an urgent recovery from Smart Switch, but for some reason that program dont detect my phone (add problems previosly also)
to overpass this i enter in download mode and flash with the the rom i mention above with odin v3.13.1.
i read in some places that cm.bin has to do with the version and i cant downgrade. But i'm using the same version i had before so dont think is that.
Also i try to make a new image without the cm.bin but when i'm placing the md5 file in odin he returns an error saying "binnary file is not ok"
Any help!!

Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920F
Region: DBT
Auto: Selected
Manual: Unselected
Binary Nature: Unselected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download the most updated firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, try to flash it via Odin.

Havent test the one from the app but i was already download this from SAMMOBILE. But i check the name and it's the same.
https://www.sammobile.com/firmwares/galaxy-s6/SM-G920F/OPT/download/G920FXXU6ERC9/217601/
i think was bad luck that was an update yesterday and i actually update it, so that's why my previous rom wasn't working. This release came out today afternoon
So if you have this kind of problem just check if there's a new release.
Solved thanks guys.