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.

Boot Loop Even After Reset

Hey guys, so my phone has been going in to boot loops. I would put it in recovery mode and clear the cache partition, that would get it to stop sometimes. Finally I did a factory reset. Now when its trying to set up my phone, it boot loops in the middle of that. So I used ODIN and tried to reinstall the firmware (OJ7), which was successful, but I'm back to boot loops during the phone set up process. Any ideas what to do next?

VanillaNasty said:
Hey guys, so my phone has been going in to boot loops. I would put it in recovery mode and clear the cache partition, that would get it to stop sometimes. Finally I did a factory reset. Now when its trying to set up my phone, it boot loops in the middle of that. So I used ODIN and tried to reinstall the firmware (OJ7), which was successful, but I'm back to boot loops during the phone set up process. Any ideas what to do next?
Click to expand...
Click to collapse
Have you did any modifications?

I installed an app on my phone that works in collaboration with a game. The app requires the phone to be rooted, but after researching the process to root a phone and the risk of voided Knox on 5.1.1 I decided against it and uninstalled the app. Its possible the app may have done something. But besides that there has not been any mods installed on my phone.

What causes the constant rebooting? Do I possibly have corrupted files that can be replaced with the recovery system? Any ideas would be helpful.

Is your bootloader unlocked?

Soooperstar said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
I am not sure. Can I check that from the recovery mode or download mode screen?

VanillaNasty said:
I am not sure. Can I check that from the recovery mode or download mode screen?
Click to expand...
Click to collapse
Don't think so. Have you tried to Odin Ol1?

Soooperstar said:
Don't think so. Have you tried to Odin Ol1?
Click to expand...
Click to collapse
Just got that on the Ol1 ODIN attempt.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925PVPU3BOI1_G925PSPT3BOI1_G925PVPU3BOI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Edit: Since that failed, my phone will now only go into download mode. It says "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." But Smart Switch is now saying I don't have an supported device.

VanillaNasty said:
Just got that on the Ol1 ODIN attempt.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925PVPU3BOI1_G925PSPT3BOI1_G925PVPU3BOI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Edit: Since that failed, my phone will now only go into download mode. It says "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." But Smart Switch is now saying I don't have an supported device.
Click to expand...
Click to collapse
Can you Odin previous firmware?

Soooperstar said:
Can you Odin previous firmware?
Click to expand...
Click to collapse
Soooperstar, I appreciate you taking the time to try to help me. I took the phone to the Samsung vendor. She worked on it for 2 hours and couldn't get it to stop going into boot loops. Its being shipped to Samsung now so they can fix it.
Thanks again.

Trying to get Kit Kat on this device

This is really late but I just tried getting KitKat on this device. I have the n-8013 which is the 32 gb version of the n-8010. Im trying to flash with odin
I've done flashing with odin before on this pc, i did last week. The drivers for this tab are installed. I used the same port for the tablet, put the file in, plugged it in, got the blue box and hit start, but everytime i get this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8010XXUDNE4_N8010OXADNE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried different ports, made sure the ROM was correct, and battery charged nothing changed. I read it could be the cable or charging port. I did replace the charging port a while back so it could be damaged again but I think its most likely the cable. Anyone else have this issue with other devices and find a solution. Thanks

it would also help if someone could find another way to flash without odin that isnt very hard using the sd card slow possibly, thanks

For starters you are flashing the wrong firmware .
You have N8013 and are flashing N8010 .

JJEgan said:
For starters you are flashing the wrong firmware .
You have N8013 and are flashing N8010 .
Click to expand...
Click to collapse
I read some people said it would work, can you find the n8013 because I can't, and is that the only issue?

No update for N8013 .
Sent from my SM-N920C using XDA-Developers mobile app
---------- Post added at 02:18 PM ---------- Previous post was at 02:16 PM ----------
JJEgan said:
No update for N8013 .
Sent from my SM-N920C using XDA-Developers mobile app
Click to expand...
Click to collapse
Read the guide in General section 8010 kk on 8013 is all I can suggest.
Sent from my SM-N920C using XDA-Developers mobile app

Stuck at boot and unable to change anything!

I have an old 8013 Note 10.1 that I let my kids use, it's had CM on it forever and no issues until recently. Now it boots up to the CM bootscreen but doesn't go any further. I've booted to TWRP and tried to format and install a new ROM but it doesn't seem to even format. When I go to load a new ROM it always shows that the internal storage is the same free space (something like 513Mb). I've tried flashing PhilzTouch, TWRP, CWM, and when I reboot to recover it's still the same version of TWRP I started with. Tried flashing a stock ROM, still boots to the CM Logo. Loaded ODIN on my computer and tried flashing a stock image using ODIN and it shows it's successful, but nothing changes on the tablet. I even tried the instructions listed in this post, which should reformat everything and still - same issue.
I've attached a few screenshots of the kinds of errors and messages I get in TWRP when I try to format, do an advanced wipe of everything and still a new ROM. Any suggestions would be great! I'm ready to give up on this thing, but I still have a sliver of hope.

Re install your oriGinal frimware
Sent from my SM-J700F using Tapatalk

saismarty said:
Re install your oriGinal frimware
Sent from my SM-J700F using Tapatalk
Click to expand...
Click to collapse
As I think I mentioned, I've tried. Just to be clear I've added some screenshots and output from ODIN.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8013UEUCOI1_N8013XARCOI1_813049_REV00_user_low_ship.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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> tz.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)
Looks like everything is flashing just fine... until I reboot the tablet and get the CM Boot logo again and the tablet just gets stuck there...

What happened next
Sent from my SM-J700F using Tapatalk

saismarty said:
What happened next
Sent from my SM-J700F using Tapatalk
Click to expand...
Click to collapse
Cyanogenmod boot animation and just stuck there... just like ODIN never happened.

Try doing Odin but check Nand erase all, if you know what that does it should wipe what's holding your tablet back and then flash stock firmware, just hope it works, I don't know anything else really

Why does rooted Tab 3, SM-T210, 7.0, 8GB WiFi fail when flashing stock ROM with Odin

With the newest version of Odin flashing several ROM's, this is the log I get:
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1397 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> PBL.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
With an older version of Odin, I get this log:
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210XXBNI1_T210PHNBNI1_T210XXBNI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> PBL.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
With Odin version 1.87, it fail at 'PBL.bin' as there's no more progres.
I noticed something going on with PIT 'Get PIT for mapping', NAND fail to write and something with 'PBN.bin'.
The stock ROM I seem to need for this device 'SM-T210, Tab3, 7.0, 8GB WiFi, has these specs: KOT49H, T210XXBOB1, PHN, build date Feb 3 2015
Kernel version: 3.4.5-4081557
So what's going wrong here?

Not sure why Odin isn't working, but we can try another way.
Flash this recovery with Odin and then reboot to recovery. From here you can try to install my custom ROM for this device and hopefully that will fix any problems with the filesystem. Then you can try flashing the stock ROM back on with Odin and you might get lucky.
Recovery (created by gr8nole)
https://drive.google.com/file/d/11EI-n_P47W6L8JM1-9wQWKv_tQq9A15V/view?usp=drivesdk
My ROM
https://drive.google.com/file/d/1aiLVMTtwo2quU6S02ggxWYKw9iZF0VNf/view?usp=drivesdk
Hope this helps! Good luck.
Sent from my LG-Q710AL using Tapatalk

Partial success on Tab3, reset with TWRP 3.0.0-0 successfully!
RealWelder said:
Not sure why Odin isn't working, but we can try another way.
Flash this recovery with Odin and then reboot to recovery. From here you can try to install my custom ROM for this device and hopefully that will fix any problems with the filesystem. Then you can try flashing the stock ROM back on with Odin and you might get lucky.
Recovery (created by gr8nole)
https://drive.google.com/file/d/11EI-n_P47W6L8JM1-9wQWKv_tQq9A15V/view?usp=drivesdk
My ROM
https://drive.google.com/file/d/1aiLVMTtwo2quU6S02ggxWYKw9iZF0VNf/view?usp=drivesdk
Hope this helps! Good luck.
Sent from my LG-Q710AL using Tapatalk
Click to expand...
Click to collapse
Thanks,
I downloaded both files.
I then downloaded Odin v3.07 and fired it up and I loaded TWRP into Odin to upload onto the Tab3 device.
Then I formatted the user data as well as the cache in 'system recovery' and choose to reboot the device in 'download mode'.
Then I connected the USB cable to the Windows computer and immediatly Odin connected on Com 5.
Then I clicked 'start' and Odin started and finished succesfully!!!!
Next, the Tab3 device automatically rebooted, at login still kingoroot showed up and the AV popup messages followed by the unplanned reboot (loop).
What are the next steps to take??
Do I have to copy the large (compressed) file on flash disc, or do I need to unzip it first?
When uncompressed, I found an large .img file and an boot .img file, those cannot be uploaded by Odin, right??
So when reset was successfull and at reboot I go in 'system recovery', what do I need to do next?
Please point out the steps I need to take.

xdausernl said:
Thanks,
I downloaded both files.
I then downloaded Odin v3.07 and fired it up and I loaded TWRP into Odin to upload onto the Tab3 device.
Then I formatted the user data as well as the cache in 'system recovery' and choose to reboot the device in 'download mode'.
Then I connected the USB cable to the Windows computer and immediatly Odin connected on Com 5.
Then I clicked 'start' and Odin started and finished succesfully!!!!
Next, the Tab3 device automatically rebooted, at login still kingoroot showed up and the AV popup messages followed by the unplanned reboot (loop).
What are the next steps to take??
Do I have to copy the large (compressed) file on flash disc, or do I need to unzip it first?
When uncompressed, I found an large .img file and an boot .img file, those cannot be uploaded by Odin, right??
So when reset was successfull and at reboot I go in 'system recovery', what do I need to do next?
Please point out the steps I need to take.
Click to expand...
Click to collapse
Boot into recovery with vol+, home, and power then click install. Find my .zip file, click it, and then swipe to install the zip. Once it's done you should be good to go. If you have any problems report back. It should get you into my ROM no problem, though. Also, my ROM has lots of extra features and I made it possible to somewhat theme the OS on the fly. (It'll be mostly gray at first as it's the default for the color picker) You'll find numerous extra options in settings (including in Dev options) and a second settings app with a lot of my own mods in it.
You may also want to wipe data, cache, and dalvik cache if you have any issues.
Sent from my LG-Q710AL using Tapatalk
---------- Post added at 05:43 PM ---------- Previous post was at 05:37 PM ----------
Here's a link to my ROM's thread so you can check it out.
https://r.tapatalk.com/shareLink?ur...share_tid=3510449&share_fid=3793&share_type=t
Sent from my LG-Q710AL using Tapatalk

There's no 'install' button I can click on ...
RealWelder said:
Not sure why Odin isn't working, but we can try another way.
Flash this recovery with Odin and then reboot to recovery. From here you can try to install my custom ROM for this device and hopefully that will fix any problems with the filesystem. Then you can try flashing the stock ROM back on with Odin and you might get lucky.
Recovery (created by gr8nole)
https://drive.google.com/file/d/11EI-n_P47W6L8JM1-9wQWKv_tQq9A15V/view?usp=drivesdk
My ROM
https://drive.google.com/file/d/1aiLVMTtwo2quU6S02ggxWYKw9iZF0VNf/view?usp=drivesdk
Hope this helps! Good luck.
Sent from my LG-Q710AL using Tapatalk
Click to expand...
Click to collapse
RealWelder said:
Boot into recovery with vol+, home, and power then click install. Find my .zip file, click it, and then swipe to install the zip. Once it's done you should be good to go. If you have any problems report back. It should get you into my ROM no problem, though. Also, my ROM has lots of extra features and I made it possible to somewhat theme the OS on the fly. (It'll be mostly gray at first as it's the default for the color picker) You'll find numerous extra options in settings (including in Dev options) and a second settings app with a lot of my own mods in it.
You may also want to wipe data, cache, and dalvik cache if you have any issues.
Sent from my LG-Q710AL using Tapatalk
---------- Post added at 05:43 PM ---------- Previous post was at 05:37 PM ----------
Here's a link to my ROM's thread so you can check it out.
https://r.tapatalk.com/shareLink?ur...share_tid=3510449&share_fid=3793&share_type=t
Sent from my LG-Q710AL using Tapatalk
Click to expand...
Click to collapse
Thanks, I'll check the link later, for now I want to have your ROM installed first.
When I boot into 'system recovery' there's no 'install' to click on.
In 'Android system recovery <3e>'
Following are the only choices available:
appy update from ADB
apply ..... from external storage
wipe data/factory reset
wipe cache partition
apply ... from cache

xdausernl said:
Thanks, I'll check the link later, for now I want to have your ROM installed first.
When I boot into 'system recovery' there's no 'install' to click on.
In 'Android system recovery <3e>'
Following are the only choices available:
appy update from ADB
apply ..... from external storage
wipe data/factory reset
wipe cache partition
apply ... from cache
Click to expand...
Click to collapse
If you still have 3e recovery, you need to reflash TWRP. Then boot into TWRP. There you will have an install button.
Sent from my LG-Q710AL using Tapatalk
---------- Post added at 07:35 PM ---------- Previous post was at 07:32 PM ----------
Are you running Jelly Bean or KitKat?
Sent from my LG-Q710AL using Tapatalk

KitKat or Jelly-Bean, I'm not sure
RealWelder said:
If you still have 3e recovery, you need to reflash TWRP. Then boot into TWRP. There you will have an install button.
Sent from my LG-Q710AL using Tapatalk
---------- Post added at 07:35 PM ---------- Previous post was at 07:32 PM ----------
Are you running Jelly Bean or KitKat?
Sent from my LG-Q710AL using Tapatalk
Click to expand...
Click to collapse
Don't know, it's Android 4.4.2 ... think KitKat unless Jelly-Bean has also 4.4.2, so I'm not sure.
How can I tell?
After reflashing, it doesn't reboot into TWRP.

xdausernl said:
Don't know, it's Android 4.4.2 ... think KitKat unless Jelly-Bean has also 4.4.2, so I'm not sure.
How can I tell?
Click to expand...
Click to collapse
That means you're on kitkat. Go into download mode again, reflash TWRP with Odin, boot into TWRP with vol+, home, and power, then click install and select my ROM. (You need to put the ROM zip in internal storage or on sd. You may have to toggle between Internal Storage and SD in TWRP to see the file.)
Sent from my LG-Q710AL using Tapatalk

RealWelder said:
If you still have 3e recovery, you need to reflash TWRP. Then boot into TWRP. There you will have an install button.
Sent from my LG-Q710AL using Tapatalk
---------- Post added at 07:35 PM ---------- Previous post was at 07:32 PM ----------
Are you running Jelly Bean or KitKat?
Sent from my LG-Q710AL using Tapatalk
Click to expand...
Click to collapse
RealWelder said:
That means you're on kitkat. Go into download mode again, reflash TWRP with Odin, boot into TWRP with vol+, home, and power, then click install and select my ROM. (You need to put the ROM zip in internal storage or on sd. You may have to toggle between Internal Storage and SD in TWRP to see the file.)
Sent from my LG-Q710AL using Tapatalk
Click to expand...
Click to collapse
Is it possible that I'd need a newer version of TWRP to get into TWRP at reboot?

xdausernl said:
Is it possible that I'd need a newer version of TWRP to get into TWRP at reboot?
Click to expand...
Click to collapse
No, that's the latest and greatest for that device.
Sent from my LG-Q710AL using Tapatalk
---------- Post added at 08:09 PM ---------- Previous post was at 08:08 PM ----------
When you flash twrp again, make sure auto reboot isn't checked... Then you can use the button combination to get from Download mode to TWRP.
Sent from my LG-Q710AL using Tapatalk

RealWelder said:
No, that's the latest and greatest for that device.
Sent from my LG-Q710AL using Tapatalk
---------- Post added at 08:09 PM ---------- Previous post was at 08:08 PM ----------
When you flash twrp again, make sure auto reboot isn't checked... Then you can use the button combination to get from Download mode to TWRP.
Sent from my LG-Q710AL using Tapatalk
Click to expand...
Click to collapse
Right, we'll do ... brb

RealWelder said:
No, that's the latest and greatest for that device.
Sent from my LG-Q710AL using Tapatalk
---------- Post added at 08:09 PM ---------- Previous post was at 08:08 PM ----------
When you flash twrp again, make sure auto reboot isn't checked... Then you can use the button combination to get from Download mode to TWRP.
Sent from my LG-Q710AL using Tapatalk
Click to expand...
Click to collapse
xdausernl said:
Right, we'll do ... brb
Click to expand...
Click to collapse
I took the steps you just pointed out, but still ... when I reboot into recovery mode I'll find Android system recovery <3e>
Did I do something wrong?
At the Tab3 there's no progres bar at all, is that the way it should be when flashing?

Is it possible that Kingoroot has anything to do with it?
Below the log from Odin 3.07
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210.TWRP.3.0.0-0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!

xdausernl said:
Is it possible that Kingoroot has anything to do with it?
Below the log from Odin 3.07
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210.TWRP.3.0.0-0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
Click to expand...
Click to collapse
Try a different usb port and/or cable. Yes there should be a blue progress bar at the bottom of the download mode screen while flashing. It should also say (1successful, 0 failed) if it works.
Sent from my LG-Q710AL using Tapatalk

RealWelder said:
Try a different usb port and/or cable. Yes there should be a blue progress bar at the bottom of the download mode screen while flashing. It should also say (1successful, 0 failed) if it works.
Sent from my LG-Q710AL using Tapatalk
Click to expand...
Click to collapse
RealWelder said:
It should also say (1successful, 0 failed) if it works.
Click to expand...
Click to collapse
That Odin does
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210.TWRP.3.0.0-0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
But on the Tab3, nothing at all ...
Previously I also was able to browse the Tab3 with the current USB cable, but since that thing with AV software is going on ... followed by the unplanned reboot (loop) it no longer is browsable.
B.t.w, I don't have another cable.
I also remain unable to edit settings (stop and/or remove programs) no matter in what mode I'm working in, still these popup keep coming.
By the time I'm done or in the proces of ... then there's the unplanned reboot again, really annoying.

xdausernl said:
That Odin does
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210.TWRP.3.0.0-0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
Ok so it seems to be flashing it, but when you go into recovery it's still stock 3e recovery?
Sent from my LG-Q710AL using Tapatalk
---------- Post added at 09:18 PM ---------- Previous post was at 09:12 PM ----------
Look through this thread and it might help. My TAB3 got dropped into the bathtub by my daughter so I don't have a working one to help. I still remember a lot of ot because I spent a lot of time tinkering with it, but it might be something simple I'm forgetting.
This is the original thread for the recovery.
https://r.tapatalk.com/shareLink?ur...share_tid=2437219&share_fid=3793&share_type=t
Sent from my LG-Q710AL using Tapatalk

RealWelder said:
Ok so it seems to be flashing it, but when you go into recovery it's still stock 3e recovery?
Sent from my LG-Q710AL using Tapatalk
---------- Post added at 09:18 PM ---------- Previous post was at 09:12 PM ----------
Look through this thread and it might help. My TAB3 got dropped into the bathtub by my daughter so I don't have a working one to help. I still remember a lot of ot because I spent a lot of time tinkering with it, but it might be something simple I'm forgetting.
This is the original thread for the recovery.
https://r.tapatalk.com/shareLink?ur...share_tid=2437219&share_fid=3793&share_type=t
Sent from my LG-Q710AL using Tapatalk
Click to expand...
Click to collapse
I found someone responding on the thread you just provided, with exact same trouble, but couldn't find an answer other then the ones you already came with....

How is it possible that Odin start the flashing and closes it successfully as we saw, but on the Tab3 there's nothing being written. That just doesn't make sence.
I mean, how can that be?
Is writing being refused by something like Kingoroot and how can I prevent this?
When logged into Tab3, I simply don't have enough time to get things done.
This is due to the AV popups that take that much time to get through and when I do ... less then a minute later the unplanned reboot kick in.
And after the reboot, nothing has been changed ....

xdausernl said:
How is it possible that Odin start the flashing and closes it successfully as we saw, but on the Tab3 there's nothing being written. That just doesn't make sence.
I mean, how can that be?
Is writing being refused by something like Kingoroot and how can I prevent this?
When logged into Tab3, I simply don't have enough time to get things done.
This is due to the AV popups that take that much time to get through and when I do ... less then a minute later the unplanned reboot kick in.
And after the reboot, nothing has been changed ....
Click to expand...
Click to collapse
Odin can be pretty picky. I think you should try a different USB port and cable.
Sent from my LG-Q710AL using Tapatalk

RealWelder said:
Odin can be pretty picky. I think you should try a different USB port and cable.
Sent from my LG-Q710AL using Tapatalk
Click to expand...
Click to collapse
The newest versions of Odin fail right away.
The Odin versions 1.85, 87 gave me a statusbar on the Tab3, yet flashing failed.
The Odin version 3.07 seem to finish flashing, though on the Tab3 there's no progressbar and on reboot there seem to be no changes.
Till today I used a Nokia branded cable, it's a data/charge cable, they told me that'll do exactly what it needs to do.
As wroted before, I was able to browse the Tab3 from my Windows computer ... so I thought that the cable did what it was supposed to do.
I've been trying all of the other USB ports too, still the same results ...
But you're saying that USB cable could exactly be the cause of my problems with that Tab3 device regarding flashing that thing?
Next week, I'll have another (regular) micro B USB cable, let's see what that does ...