Database Info

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...

[Q] N8000 Boot (not OS boot animation) cleared

After using Odin to perform a Nand Erase All on my n8000, the boot screen(which should be Samsung Galaxy Note 10.1 GT-N8000) turns into the Download mode screen. All features are working. How to recover. Thanks.
Add: and is still booting. Only UI change

Boot Logo Modder
Kavin Zhao said:
After using Odin to perform a Nand Erase All on my n8000, the boot screen(which should be Samsung Galaxy Note 10.1 GT-N8000) turns into the Download mode screen. All features are working. How to recover. Thanks.
Add: and is still booting. Only UI change
Click to expand...
Click to collapse
See here: BOOT LOGO MODDER :good:
And you can use your own BOOT LOGO ofcourse:laugh:

tanker32 said:
See here: BOOT LOGO MODDER :good:
And you can use your own BOOT LOGO ofcourse:laugh:
Click to expand...
Click to collapse
Exactly the same problem.
Thanks a lot for that, going to try it. :good:

Well, that worked. But after flashing another picture provided by the second post(on another thread), a even more serious problem came: Device Bricked Anything helps?

Doesn't even power on(turn on the screen) was it bricked or something else?
Help!!!! What shall I do?

Describe your problem in detail, please!
Kavin Zhao said:
Well, that worked. But after flashing another picture provided by the second post(on another thread), a even more serious problem came: Device Bricked Anything helps?
Click to expand...
Click to collapse
You must describe what exactly you did before brick the device.
1. Type of your device
2. Are you used my MOD with new picture before brick your device?
3. Did you exactly proceed step by step like I describe in my thread?
4. Was your picture in good size (1280x800 landscape mode and portrait mode 800x1280 according to type of device) ?
5. Picture must have same name, same type (logo.jpg) as is in my MOD!
6. Check your ZIP, if you have good path and structure as in my MOD exactly!
7. If you don't made a mistake and you've kept my proceed, problem is somewhere else.
Try to go to recovery, download my first type MOD and wipe cache, dalvik cache and install ZIP and don't forget reboot back to RECOVERY
and after then use system reboot !!!!! I'm waiting for your answer. Then we will try something else (according to your problem) :good:
---------- Post added at 11:18 AM ---------- Previous post was at 11:09 AM ----------
Kavin Zhao said:
Doesn't even power on(turn on the screen) was it bricked or something else?
Help!!!! What shall I do?
Click to expand...
Click to collapse
You have my answer above, but I see that even POWER ON doesn't work!
Hold POWER more than 30 sec! Then you try go to recovery... If didn't work, hold POWER+VOLUME DOWN and when you see boot logo release
POWER and then VOLUME DOWN. You should be in DOWNLOAD MODE. And then proceed with ODIN software and stock firmware. But I think
that you made mistake when you try put you picture in my MOD in ZIP file.
User jordimra in BOOT LOGO MODDER THREAD has the same problem see:
The picture attached is made ​​by me, but I think it looks like the original Samsung Galaxy Note 10.1 logo.
Edit 1: Installed "boot-logo-GT-N8000.zip" and went OK. But if I modify the "logo.jpg" inside with my own one, the device gets stuck on black (logo?) screen, and can't get into recovery.
Edit 2: Reason: bad zip structure

Thankyou for your care.
Answers:
1.N8000
2.Yes
3.Yes--perhaps
4.Didn't check that, my picture was exactly the same as The picture attached is made ​​by me, but I think it looks like the original Samsung Galaxy Note 10.1 logo.
Edit 1: Installed "boot-logo-GT-N8000.zip" and went OK. But if I modify the "logo.jpg" inside with my own one, the device gets stuck on black (logo?) screen, and can't get into recovery.
Edit 2: Reason: bad zip structure(attachment)
5.Yes
6.Yes
...and huh? how did I enter download mode just now:laugh:?
Is flashing stockrom the only way?
tick nand erase all?
tested, can only enter download mode

My advice
Kavin Zhao said:
Thankyou for your care.
Answers:
1.N8000
2.Yes
3.Yes--perhaps
4.Didn't check that, my picture was exactly the same as The picture attached is made ​​by me, but I think it looks like the original Samsung Galaxy Note 10.1 logo.
Edit 1: Installed "boot-logo-GT-N8000.zip" and went OK. But if I modify the "logo.jpg" inside with my own one, the device gets stuck on black (logo?) screen, and can't get into recovery.
Edit 2: Reason: bad zip structure(attachment)
5.Yes
6.Yes
...and huh? how did I enter download mode just now:laugh:?
Is flashing stockrom the only way?
tick nand erase all?
tested, can only enter download mode
Click to expand...
Click to collapse
If you can go to download mode only, you don't need flash entire ROM. Forget tick Nand erase all and in Odin just flash boot.img or sboot.img, you can find here a lot of this file. But img must be Android same version as you have! Then flash sboot.img through PDA in Odin, and everything should be back in normal.:good: Just try it and then send me, how successful you've been :highfive: Regards, Peter

I have to reboot in to Ubuntu to get the tar files ready for flashing. Sadly, I found Odin cannot flash in anything(sboot.bin and boot.img) except the stock bundle and as you can see, i flashed the stock bundle. And your advice made me found another perfect thing on Google that I have always been searching for-- Dual boot
But it still cannot boot. I think I have to tick Nand Erase All to erase the trouble-causing boot picture.
Wish you good luck, Peter. Cheers:highfive:
P.S While flashing the bootloder(from the tar I made myself), it shows this:
<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> sboot.bin
and stuck here

Keep going...
Kavin Zhao said:
I have to reboot in to Ubuntu to get the tar files ready for flashing. Sadly, I found Odin cannot flash in anything(sboot.bin and boot.img) except the stock bundle and as you can see, i flashed the stock bundle. And your advice made me found another perfect thing on Google that I have always been searching for-- Dual boot
But it still cannot boot. I think I have to tick Nand Erase All to erase the trouble-causing boot picture.
Wish you good luck, Peter. Cheers:highfive:
P.S While flashing the bootloder(from the tar I made myself), it shows this:
<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> sboot.bin
and stuck here
Click to expand...
Click to collapse
Well, I'm so sorry about to hearing that. But as the poet says: "By seeking and blundering we learn." So O.K. try NAND ERASE ALL and then Flash your device by STOCK firmware with ODIN or KIES. Then let me know, how did you get... Regards :fingers-crossed: and for sure :highfive:

Operation Successful
Device successfully unbricked after Nand Erase All
Thank you Peter. It was not your responsibility to help me, but you did... and thank you again for that.
And after this post's been published, I think I'm not a new member anymore.
P.S
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8000ZSCMD2_N8000OZSCMD2_1149484_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> Erase...
<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> sboot.bin
<ID:0/006> tz.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

It's my pleasure to help!
Kavin Zhao said:
Device successfully unbricked after Nand Erase All
Thank you Peter. It was not your responsibility to help me, but you did... and thank you again for that.
And after this post's been published, I think I'm not a new member anymore.
P.S
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8000ZSCMD2_N8000OZSCMD2_1149484_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> Erase...
<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> sboot.bin
<ID:0/006> tz.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
YES! You welcome! :highfive:

It was the picture's problem. I optimized the picture to 1200x800 and it’s OK.
The zip with the optimized picture is below. Should look like the original.

hi
i have the same problem,after flashed this tablet,stuck on bootloop
no access to recovery,i tried many method but no success
i tried:
pit - 4 file - 1 file - all recovery - clear efs & repair again with odin & z3x - nand erase all & ...
but no success
tablet always in bootloop & just can put into download mode
when i turn on tablet,it's take 1 second and reboot and reboot and reboot & ... on Samsung Galaxy Note 10.1

[Q] Strange Downgrade Problem !!!

Hello @ all
I got a new Samsung Note Edge SM-N915FY, with 4.4.4 Stock Rom from factory.
I install CWM recovery and have root. All went fine. I did a good Backup and so I can start to play with.
I try Mickey fast and famous Rom and works also good and I tried other stuff around. Some of them are good and some of the offered stuff is not booting, but no problem, it is only for playing around.
I install with Odin Lollipop 5.0.1 and give this Beta a try.
For me is important I can use XPosed Framework with a SkyModul with HDMI out, ( I know this is still in development) so I decide to go back to 4.4.4 Rom.
And this is not working. I can try to install the factory 4.4.4 rom or other stuff which works before and right now after install the Phone starts with sign "Samsung Note Edge" and shuts down again and so on. No Booting possible.
I tried the Factory Stock Rom with Odin and after downloading the ROM the Download Mode said "Filesize is too big"
Backup from 5.0.1 lollipop works everytime.
Any Ideas??
Regards
Panic Brothers

Panic Brothers said:
Hello @ all
I got a new Samsung Note Edge SM-N915FY, with 4.4.4 Stock Rom from factory.
I install CWM recovery and have root. All went fine. I did a good Backup and so I can start to play with.
I try Mickey fast and famous Rom and works also good and I tried other stuff around. Some of them are good and some of the offered stuff is not booting, but no problem, it is only for playing around.
I install with Odin Lollipop 5.0.1 and give this Beta a try.
For me is important I can use XPosed Framework with a SkyModul with HDMI out, ( I know this is still in development) so I decide to go back to 4.4.4 Rom.
And this is not working. I can try to install the factory 4.4.4 rom or other stuff which works before and right now after install the Phone starts with sign "Samsung Note Edge" and shuts down again and so on. No Booting possible.
I tried the Factory Stock Rom with Odin and after downloading the ROM the Download Mode said "Filesize is too big"
Backup from 5.0.1 lollipop works everytime.
Any Ideas??
Regards
Panic Brothers
Click to expand...
Click to collapse
ii know with other phones the upgrade was a one-way proposition. Once the new bootloader was flashed you were essentially stuck on the newer firmware. Downgrading, even official firmware, resulted in bootlooping... Note 3, S4 had this little "feature" and it caused mass hair pulling...

After couple tests I think the Note Edge has this kind of "feature"
No chance to get back to 4.4.4
it caused mass hair pulling...
Click to expand...
Click to collapse
No Hairs here since couple of years but for sure this is a feature for massive Hair pulling

I just try all OdIn Versions and still I get this Message.
Is there no chance to get a Downgrade to 4.4.4??
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N915FYXXU1ANK4_N915FYDBT1ANK1_N915FYXXU1ANK4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
The Phone said:
Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image
Is it possible to get a valid PIT File for SM-SN915FY to download? I just searched around and it seems that other Note4 Owner had the same problem and it was solved with a valid PIT File.

Panic Brothers said:
I just try all OdIn Versions and still I get this Message.
Is there no chance to get a Downgrade to 4.4.4??
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N915FYXXU1ANK4_N915FYDBT1ANK1_N915FYXXU1ANK4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
The Phone said:
Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image
Is it possible to get a valid PIT File for SM-SN915FY to download? I just searched around and it seems that other Note4 Owner had the same problem and it was solved with a valid PIT File.
Click to expand...
Click to collapse
I had exact the same problem with the galaxy note 4. When i put another custom rom on the phone with odin, it works good. Then i go back to the original rom till so far no problem.Then i put a new rom on it from outside my country. Then the problems starting, everytime i get exact the same problem as you have. The Phone said:
Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image. So after i can only download the official rom from my country. very strange. Till so far no problem with my Note Edge.

On NOTE 4 was possibility to downgrade STOCK ROM (from 5.x to 4x) with Mobile ODIN. Did You try this way? But I'm not sure, if Mobile ODIN is compatible with EDGE...
@phablet

Jumbo78 said:
On NOTE 4 was possibility to downgrade STOCK ROM (from 5.x to 4x) with Mobile ODIN. Did You try this way? But I'm not sure, if Mobile ODIN is compatible with EDGE...
@phablet
Click to expand...
Click to collapse
THX for this hint ... this I did not tried out but I just checked and load the mobile ODIN and the Edge is not supported in the actuall Version. Maybe later.
So it is only chance to wait for Xposed on Samsung Stock ROM :crying:

I'M back on 4.4.4 Now !!!!
This are the steps that worked on my rooted Edge SM-N915FY
- Boot to recovery mode wipe all Data/Cache
- Boot to download mode
- Start Odin 3.09 and load (AP) the original 4.4.4 from SamMobile (N915FYXXU1ANK4_N915FYDBT1ANK1_N915FYXXU1ANK4)
- After press start all will be loaded and You get errormessage on screen Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image (Your Phone will not boot up now)
- Remove Battery and go again in the download mode
- Reset ODIN and load (AP) the custom recovery File (n915f-cwm-recovery-6.0.5.1)
After I load the recovery file the Phone starts again correct and shows 4.4.4 Version

Panic Brothers said:
I'M back on 4.4.4 Now !!!!
This are the steps that worked on my rooted Edge SM-N915FY
- Boot to recovery mode wipe all Data/Cache
- Boot to download mode
- Start Odin 3.09 and load (AP) the original 4.4.4 from SamMobile (N915FYXXU1ANK4_N915FYDBT1ANK1_N915FYXXU1ANK4)
- After press start all will be loaded and You get errormessage on screen Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image (Your Phone will not boot up now)
- Remove Battery and go again in the download mode
- Reset ODIN and load (AP) the custom recovery File (n915f-cwm-recovery-6.0.5.1)
After I load the recovery file the Phone starts again correct and shows 4.4.4 Version
Click to expand...
Click to collapse
my N915FY is already updated with lollipop (via KIES)
i never rooted the phone...
i want to go back to 4.4.4, is there any chance to do that? can i root now the phone anf follow the same steps that worked for you?

Goofy-Goober said:
my N915FY is already updated with lollipop (via KIES)
i never rooted the phone...
i want to go back to 4.4.4, is there any chance to do that? can i root now the phone anf follow the same steps that worked for you?
Click to expand...
Click to collapse
Sorry...but this I don't know. The first thing I do for my new devices is the "root" procedure and delete google apps and crapy stuff.
But why not? I think Odin and the Download Mode are possible without a rooting a device.
"Try and error" or maybe it works.
Good luck
*Edit*
you need a custom recovery like CWM oder TWRP and you must activate USB debugging in your developer options.

this is very strange that is happening to you guys, i have the tmobile version edge, used to have kitkat when i bought it, ROM from trinidad and tobago, decided to download lollipop from tmobile, did not like it, went back to trinidad and tobago kitkat, everything flashed ok, just a bootloop that resolved after i wiped cache
my phone has never been rooted, no custom recovery, no custom rom
hope this helps you out

I have 915g and to downgrade to 4.4.4 all i had to do was turn off auto reboot in odin, flash stock kitkat, boot into stock recovery, wipe data/cache and it booted.

Upgrade to 5.1.1 with ODIN fails, BL and Modem already 5.1.1

Hi all
I thinks I've done a big mess. Following the xda guide to install modified ROM via ODIN, I've upgraded BL and Modem to 5.1.1
Now, the red string appears on the left top of the screen: INVALID MAGIC STRING
This is the guide
Do exactly step-by-step the following things:
- Unplug your Phone (IMPORTANT!)
- Turn your Phone completely off (This is IMPORTANT)
- Start your Phone in download mode on this way: Press Vol down + Home + Power buttons till the screen turns on, press Vol Up to continue (Only enter download mode on this way, otherwise it won't work!!)[/B]
- Open Odin 3.10.6 on your PC (Make sure you're using this version of Odin, other versions won't work correctly maybe!)
- Click on the 'BL' button, and load in your BOOTLOADER tar.md5 file for your model
- Click on the 'CP' button, and load in your MODEM tar.md5 file for your model
- DON'T TOUCH ANYTHING ELSE (you can brick your phone if you choose other settings in Odin)
- Now Connect your phone to your computer (DO NOT connect your phone before this step, otherwise it won't work!)
- Click on the Start button
- Wait till it finish flashing.
- Your phone reboots automatically after flashing.
- Always check after flashing: Settings -> About device -> Baseband; that should show the same modem build number noted as here.
And also check if the bootloader got flashed correctly by downloading an AndroidTerminal app, and enter this command: getprop ro.boot.bootloader
Unfortunately, after this procedure I can't rollback to 5.0.2, neither I can't install 5.1.1. stock firmwares (from sammobile) with ODIN. It goes always FAIL:
<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
<ID:0/003> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please anyone of you can help me to unblock my device? Whatever firmware is good if device will work again.
Thanks
Rob

Cant root samsung j700t, please help, wont boot into twrp

model - sm-j700t
version - 6.0.1
kernel version - 3.10.61-9815749
odin - 3.07 and 3.1
twrp - 2.8.7 and 3.0.3
developer options both usb debugging and oem unlock enabled
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
OK i've done this about 5 times. i dont have a problem with w.e version of odin or twrp i use(or so it seems). every attempt is successful. I literally, for the life of me, can not boot into twrp recovery to install supersu. i've watched all the videos and after twrp is flashed the phone booths directly into twrp. my phone reboots normally and i have to turn it off and turn it back on holding volume + up, which ig boots into the regular boot up? it tries to install something, fails, and then goes to the i guess regular boot up. People have even suggested holding volume+up after twrp is flashed but the phone reboots normally anyway. I dont know what im doing wrong I cant get it to boot into twrp. please help

Hold the home button + volume up as soon as you see Removed!!
Sent from my SM-A310F using Tapatalk

Darkfang2u2 said:
model - sm-j700t
version - 6.0.1
kernel version - 3.10.61-9815749
odin - 3.07 and 3.1
twrp - 2.8.7 and 3.0.3
developer options both usb debugging and oem unlock enabled
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
OK i've done this about 5 times. i dont have a problem with w.e version of odin or twrp i use(or so it seems). every attempt is successful. I literally, for the life of me, can not boot into twrp recovery to install supersu. i've watched all the videos and after twrp is flashed the phone booths directly into twrp. my phone reboots normally and i have to turn it off and turn it back on holding volume + up, which ig boots into the regular boot up? it tries to install something, fails, and then goes to the i guess regular boot up. People have even suggested holding volume+up after twrp is flashed but the phone reboots normally anyway. I dont know what im doing wrong I cant get it to boot into twrp. please help
Click to expand...
Click to collapse
Soon as u see pass is how i do it,vol down,home, and power.hold till goes black.then slide vol to up position while u hold the other buttons. Hold till u see twrp booting.DO NOT use vol up first and whatever buttons he said it is NOT correct actually at all.,sorry to the dude who said to do that i mean no disrespect but u are incorrect. Also, make sure u format data, then flash root zip then encryption breaker then reboot if not u will be screwed and not be able to make nandroids. I have posted this on both j7 twrps numerous times. Good luck and sometimes it takes a couple times.

Make sure you have just the right version of TWRP man. I've had this happen the first time. Some versions are for the other J7 models. Get one from the j700t development thread and flash it again. Make sure as soon as you flash TWRP and Odin reboots the device, pull out the battery as soon as you see the Samsung splash screen. This is to prevent stock from overwriting the recovery. Finally, press and hold power up, home and power until it finally boots into TWRP. Message me if this doesn't work

Both versions work on our phone

J700t
Put this file in Odin and it should work for you.
I used it for both of my j700t. download.chainfire.eu/1138/CF-Root/CF-Auto-Root/CF-Auto-Root-j7eltetmo-j7eltetmo-smj700t.zip
You will need to copy and paste this to Google I can't post links.
Also those twrp files don't work on some of these j7 devices for reasons unknown to me.

Darkfang2u2 said:
model - sm-j700t
version - 6.0.1
kernel version - 3.10.61-9815749
odin - 3.07 and 3.1
twrp - 2.8.7 and 3.0.3
developer options both usb debugging and oem unlock enabled
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
OK i've done this about 5 times. i dont have a problem with w.e version of odin or twrp i use(or so it seems). every attempt is successful. I literally, for the life of me, can not boot into twrp recovery to install supersu. i've watched all the videos and after twrp is flashed the phone booths directly into twrp. my phone reboots normally and i have to turn it off and turn it back on holding volume + up, which ig boots into the regular boot up? it tries to install something, fails, and then goes to the i guess regular boot up. People have even suggested holding volume+up after twrp is flashed but the phone reboots normally anyway. I dont know what im doing wrong I cant get it to boot into twrp. please help
Click to expand...
Click to collapse
PM me brother, I'll get you setup.

Depends one the baseband version you have. if its aqc3 or aqf1 twrp is not compatible with those.
---------- Post added at 06:02 PM ---------- Previous post was at 05:38 PM ----------
check the cf auto root website for sm j700t you can root with that now.