Post Reply

[Q] Unrooted Galaxy Tab 2 P5113, boot loop, can't presently install recovery utility

21st January 2014, 07:27 PM   |  #1  
OP Junior Member
Thanks Meter: 1
 
3 posts
Join Date:Joined: Jan 2014
Hello,

I've a Samsung Galaxy Tab 2 10.1 that I've had for more than a year.

Recently, in the last few weeks, it's developed a boot loop. In my many attempts to fix this, I've tried to put the samsung factory fresh ROM in it (P5113XACCLK7_XAC) that didn't work using ODIN 1.85, Heimdall, and never could get a good connection with Kies. I've tried to install different recovery utilities (Philz, CWM, recovery-clockwork, etc). When it boots into recovery mode, it shows the android robot and then an 'installing package' message briefly followed by a dead-android robot with a red warning sign with a 'command not found' error.

In the Android System Recovery <3e> mode, when I clear cache partition .. I get the same dead-robot error graphic with 'Error' as the message and the tablet goes back into boot-loop. When I select 'wipe data/factory reset' .. I get the same dead-robot error with the 'No Command' error message and it goes back into the Android System Recovery menu.

This tablet is behaving as if it has an unwritable file system..

Right now, I'd do just about anything to get this back to normal ROM.

Suggestions?

Thanks a lot

Tyler
The Following User Says Thank You to tylerbud For This Useful Post: [ View ]
22nd January 2014, 02:22 AM   |  #2  
Junior Member
Thanks Meter: 6
 
26 posts
Join Date:Joined: Nov 2010
Quote:
Originally Posted by tylerbud

Hello,

I've a Samsung Galaxy Tab 2 10.1 that I've had for more than a year.

Recently, in the last few weeks, it's developed a boot loop. In my many attempts to fix this, I've tried to put the samsung factory fresh ROM in it (P5113XACCLK7_XAC) that didn't work using ODIN 1.85, Heimdall, and never could get a good connection with Kies. I've tried to install different recovery utilities (Philz, CWM, recovery-clockwork, etc). When it boots into recovery mode, it shows the android robot and then an 'installing package' message briefly followed by a dead-android robot with a red warning sign with a 'command not found' error.

In the Android System Recovery <3e> mode, when I clear cache partition .. I get the same dead-robot error graphic with 'Error' as the message and the tablet goes back into boot-loop. When I select 'wipe data/factory reset' .. I get the same dead-robot error with the 'No Command' error message and it goes back into the Android System Recovery menu.

This tablet is behaving as if it has an unwritable file system..

Right now, I'd do just about anything to get this back to normal ROM.

Suggestions?

Thanks a lot

Tyler

I am not sure if this will work for you but Odin v1.85 never worked for my P5110. I had to use Odin v3.07.
22nd January 2014, 03:36 AM   |  #3  
OP Junior Member
Thanks Meter: 1
 
3 posts
Join Date:Joined: Jan 2014
Quote:
Originally Posted by cwyman

I am not sure if this will work for you but Odin v1.85 never worked for my P5110. I had to use Odin v3.07.

Alright.. I've got that version as well.. let me give it a whirl...

Output of ODIN 3.07

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5113UECLK7_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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

any other suggestions?
23rd January 2014, 12:20 AM   |  #4  
Senior Member
Flag Tennessee
Thanks Meter: 14
 
121 posts
Join Date:Joined: Dec 2013
More
Is your tab wifi or is it through a carrier?

Sent from my SCH-I545 using XDA Premium 4 mobile app
22nd April 2014, 06:58 PM   |  #5  
The French Tickl3r's Avatar
Senior Member
Flag Montreal
Thanks Meter: 27
 
167 posts
Join Date:Joined: May 2013
More
Quote:
Originally Posted by tylerbud

Hello,

I've a Samsung Galaxy Tab 2 10.1 that I've had for more than a year.

Recently, in the last few weeks, it's developed a boot loop. In my many attempts to fix this, I've tried to put the samsung factory fresh ROM in it (P5113XACCLK7_XAC) that didn't work using ODIN 1.85, Heimdall, and never could get a good connection with Kies. I've tried to install different recovery utilities (Philz, CWM, recovery-clockwork, etc). When it boots into recovery mode, it shows the android robot and then an 'installing package' message briefly followed by a dead-android robot with a red warning sign with a 'command not found' error.

In the Android System Recovery <3e> mode, when I clear cache partition .. I get the same dead-robot error graphic with 'Error' as the message and the tablet goes back into boot-loop. When I select 'wipe data/factory reset' .. I get the same dead-robot error with the 'No Command' error message and it goes back into the Android System Recovery menu.

This tablet is behaving as if it has an unwritable file system..

Right now, I'd do just about anything to get this back to normal ROM.

Suggestions?

Thanks a lot

Tyler

im having the same issue.. did you ever find a solution?
22nd April 2014, 07:04 PM   |  #6  
OP Junior Member
Thanks Meter: 1
 
3 posts
Join Date:Joined: Jan 2014
Quote:
Originally Posted by The French Tickl3r

im having the same issue.. did you ever find a solution?

Not as of yet
7th September 2014, 09:48 PM   |  #7  
Junior Member
Thanks Meter: 1
 
1 posts
Join Date:Joined: Nov 2013
Quote:
Originally Posted by tylerbud

Hello,

I've a Samsung Galaxy Tab 2 10.1 that I've had for more than a year.

Recently, in the last few weeks, it's developed a boot loop. In my many attempts to fix this, I've tried to put the samsung factory fresh ROM in it (P5113XACCLK7_XAC) that didn't work using ODIN 1.85, Heimdall, and never could get a good connection with Kies. I've tried to install different recovery utilities (Philz, CWM, recovery-clockwork, etc). When it boots into recovery mode, it shows the android robot and then an 'installing package' message briefly followed by a dead-android robot with a red warning sign with a 'command not found' error.

In the Android System Recovery <3e> mode, when I clear cache partition .. I get the same dead-robot error graphic with 'Error' as the message and the tablet goes back into boot-loop. When I select 'wipe data/factory reset' .. I get the same dead-robot error with the 'No Command' error message and it goes back into the Android System Recovery menu.

This tablet is behaving as if it has an unwritable file system..

Right now, I'd do just about anything to get this back to normal ROM.

Suggestions?

Thanks a lot

Tyler

Tyler, I see that your last post was back in April, and although I'm fairly certain what your answer will be, I'd be remiss if I didn't ask anyway. Were you able to resolve this problem? If so, would you mind sharing the steps you took in your process? I have a Samsung Galaxy Tab 2 10.1 (P5113), and out of nowhere it performed a reboot and it has been looping ever since.

This has happened a couple times in the past two years I've owned the device and with my very limited knowledge regarding ROMs, flashing or rooting, I found my way to the System Recover Menu and was able to select the option to reset the tablet to factory settings. The system began the process of erasing the data and once it was complete I was able to reboot the tablet and everything worked just like new.

The process I just described has been successful for me twice before. So, yesterday when the tablet began it's reboot loop I attempted to perform the same steps as I had done in the past. This time, however, when I tried to enter the System Recovery Menu, "No Command" appeared beneath an unhealthy looking green android fellow. Whenever I attempt to select and run one of the options in the Recovery menu the command will fail and give an error.

I've been searching and reading threads all day trying to understand what is happening. Your OP has been the only one I've come across so far that resembles what I'm experiencing. Keeping my fingers crossed you may be able to provide some insight at least.

Thanks so much!

Joel
The Following User Says Thank You to MyCrazyTimes For This Useful Post: [ View ]
11th September 2014, 08:28 AM   |  #8  
Senior Member
Flag Seattle, WA
Thanks Meter: 211
 
293 posts
Join Date:Joined: Apr 2011
Donate to Me
More
Info 2 Boot loop
After I installed v4.2.2 shortly after release, I didn't like a few things (including some instability), so I went back to v4.1.1 using Odin, which at that time did the job. A few months later I reinstalled v4.2.2, and shortly after that, I noticed that Samsung pushed a significant sized patch to v4.2.2, and the instability stopped.

Sometime later, I tried again to go back to v4.1.1. Odin installed the prior version successfully, but then I entered a boot loop. I used Odin to reinstall v4.2.2, and all was well again.

No matter how many times I've tried to go back to v4.1.1, I now can't; I get the boot loop. However, I can always reinstall v4.2.2 with success. I suspect that the Samsung v4.2.2 patch changed something that now prevents going back to v4.1.1.

I don't know if this helps, but I thought I'd throw it out.
Last edited by DeanGibson; 11th September 2014 at 08:31 AM.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes