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
tylerbud said:
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
Click to expand...
Click to collapse
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.
cwyman said:
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.
Click to expand...
Click to collapse
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?
Is your tab wifi or is it through a carrier?
Sent from my SCH-I545 using XDA Premium 4 mobile app
tylerbud said:
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
Click to expand...
Click to collapse
im having the same issue.. did you ever find a solution?
The French Tickl3r said:
im having the same issue.. did you ever find a solution?
Click to expand...
Click to collapse
Not as of yet
tylerbud said:
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
Click to expand...
Click to collapse
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
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.
I have tried 7 different methods to fix from safe mode to factory resetting Google
Please help.
I have the exact same issue and have tried (safe mode. Uninstalling most of apps and factory reset play store.)
I can use my partners hot spot and never reboots.
WHY?
Please some1 who can help me with this exact problem please help.
Samsung galaxy tab2 10.1
tylerbud said:
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
Click to expand...
Click to collapse
I'm trying to factory reset my Tab 2 because it keeps on restarting. It will load up all the apps but after 30 sec or so it freeze and reboot. This cycle goes on endlessly. Anyway so I want to factory reset. I go into the recovery mode and I see "command error" with the Android guy flat on his back with red exclamation sign. I cannot clear cache or factory reset or anything. I can select options and execute them but it gives error.
Now I thought might as well root or install custom recovery through Odin. Odin say Pass and the flash is all fine but its no sticking. I still don't have root or custom recovery although Odin say it went all good. Any ideas ? Also has anyone have firmware for this model in .tar so i can flash through Odin and see if it sticks. Hardware problem here I think.
even stock firmware not sticking. I can;t seem to write to nand. What if i check erase nand on odoin when flashing stock rom ?
I rooted last night which was successful but then I tried installing Xposed with Flashfire and after a reboot, it never came back up. I can get into what appears to be recovery mode and download mode but the phone doesn't do anything past that. In recovery, it says
Android Recovery
MMB29M.G930VVRU2APE1
Verizon/heroqltevzw/heroqltevzw
6.0.1/MMB29M/G930VVRU2APE1
user/release-keys
User volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Mount /system
View rcovery logs
Power off
(at the bottom)
Support API: 3
dm-verity verification failed...
If I try to flash from ADB or SD card it says "Update from external storage is disabled."
Rebooting just brings it back here.
If I reboot into bootloader, I get a bright teal colored screen with a large arrow facing down and it says, "Downloading... Do not turn off target"
If I try to flash anything from Odin (AP, BL, CP, etc....), it sees the phone and calls out it's com port, but upon flashing it FAILS within a few seconds. After a fail, it displays
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail: aboot
*****************************************************************************
If I power it off and boot directly into the "Downloading..." screen then it displays
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G930V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FAP LOCK: ON
QUALCOMM SECUREBOOT: ENABLE
AP SWREV: B4(2,1,1,1,1) K1 S3
SECURE DOWNLOAD: ENABLE
But it still fails flashing from Odin.
I am using Odin3 v 3.12 but the actual file says Odin PrinceComsy.exe
I'm dead in the water here. Did my phone just become a $600 paperweight?
You've tripped the dm-verity, basically, you've installed TWRP (or another custom recovery) without installing no-verity or removing dm-verity altogether. I believe there is a way to fix it if you look here: https://forum.xda-developers.com/note5/help/how-to-solve-dm-verity-verification-t3293306. I have not personally used this method but most people are saying it works. Just ensure if this does work install no-verity from here:https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ and install in your recovery.
Best of luck
EDIT: Just realized this is Verizon, not sure maybe wait till someone confirms this as I have an Exyons and haven't looked a lot into the snapdragon chip
So i want to root my smartphone wich i just adquired yesterday, i followed this guid http://azkazya.blogspot.mx/2017/02/blackview-bv6000-twrp-root-mt6755.html with a FAIL, the phone isnt bricked but when i apply on "update from sd" and select the supersu.rar it appears an error that saids something about OTA, and "INSTALATION ABORTED", can anybody help me please, remember my android is 7.0 as default.
resume of the root try:
download mediatek, flashtools, scatter, recovery, etc : OK
Change the recovery.img and the scatter for the one that i downloaded with flashtoosl : OK (It appears the green screen in windows and with the "green check"
Boot into bootloader: OK but it appeared a "no command" so i insisted on pressing the buttons too bootload till it pass to the screen where it appears apply update, wipe data, etc.
Load the supersu RAR file after selecting apply update from SD: OK
Then pass like 3-5 seconds and it says Installation aborted and something about OTA and scatter.
Somebody please help!!!
Still trying, somebody please help
About a month ago I updated my phone to Oreo and after that it’s been stuck in a boot loop. I tried factory resetting, wiping cache and flashing it with the stock rom, it was successful every time but no fix.
The phone also won’t charge but it shows a charging icon. Phone also turns off after no command and never turns back on.
I also received errors in red every 10 times when turning it on
BOTA: bota read partition fail
Secure check fail: invalid pit or no pit
The phone also won’t go in maintenance boot mode
And started in download mode with Samsung logo and recovery starting all at once
Can someone please give me something
IexorionI said:
About a month ago I updated my phone to Oreo and after that it’s been stuck in a boot loop. I tried factory resetting, wiping cache and flashing it with the stock rom, it was successful every time but no fix.
The phone also won’t charge but it shows a charging icon. Phone also turns off after no command and never turns back on.
I also received errors in red every 10 times when turning it on
BOTA: bota read partition fail
Secure check fail: invalid pit or no pit
The phone also won’t go in maintenance boot mode
And started in download mode with Samsung logo and recovery starting all at once
Can someone please give me something
Click to expand...
Click to collapse
First of all you must ensure you have the CORRECT firmware for your device. Check that you have.
Then flash with Odin but check "Nand Erase" in options before flash.
cooltt said:
First of all you must ensure you have the CORRECT firmware for your device. Check that you have.
Then flash with Odin but check "Nand Erase" in options before flash.
Click to expand...
Click to collapse
And what if this doesn’t work?
At the moment going into recovery mode has a lot of errors such as failed to mount /system as read-write or device is busy
IexorionI said:
And what if this doesn’t work?
At the moment going into recovery mode has a lot of errors such as failed to mount /system as read-write or device is busy
Click to expand...
Click to collapse
OK start with the easy option. Extract the PIT file from your firmware and check "re-partiton" in Odin before you start. There is a separate tab for the PIT file.
Invalid PIT means exactly that, its not the correct firmware for your device and missing PIT is also self explanatory. A genuine firmware will always have the correct PIT file for your device.
You can do the above and it'll either fix the phone or do nothing in which case you'll move to Nand Erase.