Samsung Galaxy Tab 2
GT-P5110
Android version: 4.2.2.
Hi there, I have a rooted device running on CyanogenMod 10.1.3-p5110, with a custom recovery CWM 6.0.2.7
After 3 years (or so) of smooth operation it started to slow down and getting unstable from time to time, so I decided to factory reset.
I did the factory reset from CWM following the regular regular instructions, however after reset completion the devices booted back to the original CM10, with all the original data (nothing was cleaned at all or reset). I tried several times from - cleaning cache, date, system, dalvik cache, factory reset ... still the same result.
I also tried to replace the CWM with TWRP (GT-P5110_TWRP_3.0.0-0.tar.md5) - same result, it shows success but if I restart to recovery, it goes to CWM 6.0.2.7
If I boot into recovery (CWM) and flash any rom, it shows success and then reboots (guess what) into the original CM 10 like nothing happened.
I tried to flash the stock firmware using Odin. I got an original firmware "P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5" from a reliable source (sammobile)
Model:GT-P5110, Model name:GT-P5110, Country:Czech Republic, Version:Android 4.2.2, Changelist:1709803, Build date:Wed, 18 Sep 2013 06:13:11 +0000, Security Patch Level: N/A, Product code:XEZ, PDA: P5110XXDMI1, CSC5110OXXDMJ1
Every time I flash the original stock rom with Odin, the ID:COM box in Odin goes green and everything looks just fine but after reboot the tablet restarts to the original CM10. I was using Odin3-v1.85, as well as newer versions of the tool - namely Odin3_v3.07, Odin3_v3.11.1, all with the same result.
I even tried form very scratch - repartitioning the device using a .pit file "signed_espresso_20120220_16G.pit", flashing stock using Odin, same result.
I also tried flashing rom Heimdall Suite - same result
I have no problem to connect to the device using ADB shell and communicate with the device ...
However, I am not any Android guru, so I cannot "decode" what I get.
To me it seems like I somehow messed up my partitions or mounts and thats the reason for the strange behaviour.
So now I am stuck in strange state, which I cannot call a bootloop ... seems like I am running some sort of cached system or someting and I am unable to get out of with any standard tool available. As I said ... device is rooted, running CWM and I can boot to any mode I want ... download, recovery, system.
Any help will be more than appreciated.
You could have an faulty emmc firmware or your emmc reached end of life.
You are from europe? I know someone who can fix it for you.
You can also read the faq on my github userpage for more information about your bug.
kozyn said:
Samsung Galaxy Tab 2
GT-P5110
Android version: 4.2.2.
Hi there, I have a rooted device running on CyanogenMod 10.1.3-p5110, with a custom recovery CWM 6.0.2.7
After 3 years (or so) of smooth operation it started to slow down and getting unstable from time to time, so I decided to factory reset.
I did the factory reset from CWM following the regular regular instructions, however after reset completion the devices booted back to the original CM10, with all the original data (nothing was cleaned at all or reset). I tried several times from - cleaning cache, date, system, dalvik cache, factory reset ... still the same result.
I also tried to replace the CWM with TWRP (GT-P5110_TWRP_3.0.0-0.tar.md5) - same result, it shows success but if I restart to recovery, it goes to CWM 6.0.2.7
If I boot into recovery (CWM) and flash any rom, it shows success and then reboots (guess what) into the original CM 10 like nothing happened.
I tried to flash the stock firmware using Odin. I got an original firmware "P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5" from a reliable source (sammobile)
Model:GT-P5110, Model name:GT-P5110, Country:Czech Republic, Version:Android 4.2.2, Changelist:1709803, Build date:Wed, 18 Sep 2013 06:13:11 +0000, Security Patch Level: N/A, Product code:XEZ, PDA: P5110XXDMI1, CSC5110OXXDMJ1
Every time I flash the original stock rom with Odin, the ID:COM box in Odin goes green and everything looks just fine but after reboot the tablet restarts to the original CM10. I was using Odin3-v1.85, as well as newer versions of the tool - namely Odin3_v3.07, Odin3_v3.11.1, all with the same result.
I even tried form very scratch - repartitioning the device using a .pit file "signed_espresso_20120220_16G.pit", flashing stock using Odin, same result.
I also tried flashing rom Heimdall Suite - same result
I have no problem to connect to the device using ADB shell and communicate with the device ...
However, I am not any Android guru, so I cannot "decode" what I get.
To me it seems like I somehow messed up my partitions or mounts and thats the reason for the strange behaviour.
So now I am stuck in strange state, which I cannot call a bootloop ... seems like I am running some sort of cached system or someting and I am unable to get out of with any standard tool available. As I said ... device is rooted, running CWM and I can boot to any mode I want ... download, recovery, system.
Any help will be more than appreciated.
Click to expand...
Click to collapse
Once I had same problem with Motorola xoom and guess what was realy the problem. It was the external SD memory remove it then flash the stock rom.. If problem persists see with Andi
Thank you for your response. To me it also seems like faulty emmc. I have check the frequently asked questions on your blog and the description there exactly matches with what I'm experiencing on my device. Yes I am from Europe, Czech Republic. I have already tried to get in touch with two people who have the proper tooling to flash the firmware (JTAG). Hope I get some response fast and the solution is going to work. Still if you have someone in the CZ that you can recommend I'm grateful for any advice.
@zidane: All of the above steps where performed without external SD card.
kozyn said:
@zidane: All of the above steps where performed without external SD card.
Click to expand...
Click to collapse
Don't lose hope Try latest recovery 3.0.2.5 and the cm13 22/9 by Andi (made specially for certain cases like yours the files are in his folder the link in his signature ) if nothing happens then I guess dev Andi will be glad to help you fix your Emmc. contact him to provide you with the contacts..
Good luck
zidane01 said:
Don't lose hope Try latest recovery 3.0.2.5 and the cm13 22/9 by Andi (made specially for certain cases like yours the files are in his folder the link in his signature ) if nothing happens then I guess dev Andi will be glad to help you fix your Emmc. contact him to provide you with the contacts..
Good luck
Click to expand...
Click to collapse
@zidane01: thanx for cheerin' up
I have tried to replace my CWM 6.0.2.7 with TWRP 3.0.2.5, 3.0.2.6. from a .zip file using current recovery. Result is the same as described - after I reboot to recovery (using advanced option in CWM) it boots back to the original CWM 6.0.2.7. Flashing latest CM13 (as of 27/9/2016, downloaded from Andi's site) from CWM 6.0.2.7 ends with error. The tablet seems like READ ONLY not matter what I do. Maybe I am doing something wrong. I can describe the procedure step by step in detail, if you wish.
kozyn said:
@zidane01: thanx for cheerin' up
I have tried to replace my CWM 6.0.2.7 with TWRP 3.0.2.5, 3.0.2.6. from a .zip file using current recovery. Result is the same as described - after I reboot to recovery (using advanced option in CWM) it boots back to the original CWM 6.0.2.7. Flashing latest CM13 (as of 27/9/2016, downloaded from Andi's site) from CWM 6.0.2.7 ends with error. The tablet seems like READ ONLY not matter what I do. Maybe I am doing something wrong. I can describe the procedure step by step in detail, if you wish.
Click to expand...
Click to collapse
sounds like that you have a faulty emmc. same what android-andi said.
@kozyn Hi buddy.. have the same thing on a p5110 -- emmc is in read only mode and I can't seem to PM Andi for some contacts.
Can you help me recover this galaxy tab2 pls? Appreciate your time
Related
I have soft bricked and then recovered a lot of devices but this one has me stumped. I tried to install a custom kernel that I compiled myself using odin. When that didn't work I tried to copy the image using dd. My theory is that I wrote to the wrong block device and broke something. When it wouldn't boot I figured it was no big deal, I'll just revert to stock. I have tried flashing the stock rom with Odin and by using Kies emergency recovery. Both seem to succeed but whenever I boot I just get stuck at the samsung logo which displays on the screen forever. I can still get into download mode and recovery mode just fine.
Things I have tried:
- Factory reset (I've done this many times from stock recovery and TWRP)
- Cache wipe (Also tried several times from stock recover and TWRP - in TWRP I tried all the different wiping options)
- Flash stock ROM
- Turn off device and wait for more than an hour (since there is no way to do a battery pull)
My understanding is that the bootloader must be functioning otherwise I would not be able to get as far as I do. And since flashing stock ROM doesn't do anything there must be a partition with corrupt data that is not being rewritten when I install the ROM. Any ideas what this might be? Are there any resources I can use to completely repartition the device?
Any ideas are appreciated.
I fixed my problem so I just though I'd post the solution here in case someone finds this on Google or something.
It seems that I did indeed corrupt a partition that is not rewritten when you flash a stock rom or do an emergency system restore with kies (which I believe does nothing more than download the stock rom and then flash it). I actually had to buy a second device and use dd to copy over all the partitions and then returned the second device
So if you have this problem you might have to ask someone on this forum to give you an image of whichever partition you broke.
Hello.
First of all - I did try to search my problem but it is unique and I did not find the answer.
I am new to flashing ROM's and recoveries, but I do understand a little bit.
Here is my situation:
I bought a tab 2 10.1 inch wifi EUR version in a carboot sale for 20 quid. The guy showed me that it boots, and everything works, EXCEPT, it will do random restarts and sometimes drop the wi-fi signal.
When i got home it was running CM 10.2 something rather and it had a PhilZ 5.0 touch recovery. Obviously this was rooted. I wiped everything using odin 3.07 and it was restored to original samsung firmware and software. However the tab is either 1. Stuck in boot loop at samsung logo OR 2. loads to the welcome screen then freezes - restarts - stuck on boot logo.
I have tried to put a new recovery on it CWM 6.XXX but with no luck. When i try to install from SD card I get this error: E: failed signiture verification.
Anyone have any ideas what I should try to do now?
Thanks
Are you sure that before you flashed the new ROM you did a thorough reset and format of the system / data partitions? I've had similar symptoms from doing less than fully clean flashes.
Also I've seen lots of people have trouble with cwm (including me), so I've moved on to TWRP ( version at least 2701) or the Philz 6.something.
My best experience was with TWRP / full reset, format / omnirom for KitKat.
Good luck. Report back what works for you.
Marc
Frankenscript said:
Are you sure that before you flashed the new ROM you did a thorough reset and format of the system / data partitions? I've had similar symptoms from doing less than fully clean flashes.
Also I've seen lots of people have trouble with cwm (including me), so I've moved on to TWRP ( version at least 2701) or the Philz 6.something.
My best experience was with TWRP / full reset, format / omnirom for KitKat.
Good luck. Report back what works for you.
Marc
Click to expand...
Click to collapse
Yes i wiped everything i could. There were no errors given when wiping.
Will try TWRP recovery and see if that changes anything.
Thanks
Okay this is a weird one, Note 10.1 runs out of battery a few nights ago, go to plug it in for charging and it hangs on the "samsung galaxy note 10.1 screen". I had been running Cyanogen 11 for a few months just fine and before that Omni (Both 4.4.2) no dramas with CWM recovery 6.0.3.6. I can still get to Download/ODIN mode and CWM.
Now here is the fun part(s)
1. Firstly I tried reflashing the roms from CWM, after all I flashed both of them from the same recovery and they were still on the external sdcard. Both gave set metadata recursive status 7 error messages.
1.NB Whenever I selected the internal storage to search for a zip CWM would close immediately (crash?) and go back to the galaxy note 10.1 screen and hang there still. Also does this on other options, so I can't reach the backup I made on the internal storage
2. After googling that it seems that 6.0.3.6 can't flash 4.4.2 roms so I flash a later version using ODIN, it says success on the PC side, yet nothing changes in tablet, same when trying with twrp. CWM 6.0.3.6 won't budge
3. Try flashing the official rom (N8010XXUCMK2_N8010XSACNA2_HOME) from sammobile using ODIN, same problems as before, download mode shows the bar filling up so does ODIN, says it passed, still nothing.
4. Try old 10.2 Cyanogen build, no error message but still hangs on samsung galaxy note screen
5. Try repartitioning whilst flashing, various .pit also used, no dice. However I can now mount /data from cwm still can't mount /efs
6. Read about eMMC bug possibly being induced by Cyanogenmod, open up tablet to to check numbers on eMMC module, doesn't match any of the affected numbers.
7. Try above steps multiple times, including flashing each right after each other.
8. Cry
9. Look at new tablet options (Damn no good ones with softkeys)
10. Back to desperate flashing ODINing and scrolling through CWM
So any ideas?
Don't you have any other backup, from a sammy rom, that should restore your efs,
Two days ago happened to me the same thing.
What I've done was
1. Flash the Pit file from the leaked 4.4.2
2. Restore a backup from a 4.1.2 Sammy rom
3. Full wipe in recovery. Efs error was gone
4. Restore the backup again and boot up.
5. Update the recovery
6. Wipe again
7. Flashed the Gnabo Rom V5
Now everything it's working pretty damn good.
Hope you can solve the issue.
jika23 said:
Don't you have any other backup, from a sammy rom, that should restore your efs,
Two days ago happened to me the same thing.
What I've done was
1. Flash the Pit file from the leaked 4.4.2
2. Restore a backup from a 4.1.2 Sammy rom
3. Full wipe in recovery. Efs error was gone
4. Restore the backup again and boot up.
5. Update the recovery
6. Wipe again
7. Flashed the Gnabo Rom V5
Now everything it's working pretty damn good.
Hope you can solve the issue.
Click to expand...
Click to collapse
Where exactly is the PIT file I should be looking for? Been looking for a while now.
My P5100 is acting strange. Short after booting it gives errors about gapps and other apps being stopped. Those messages keep popping up, so nothing else except rebooting/shutting down is possible.
Everything I try to change (in the short time before the errors pop up) is gone after a reboot.
I tried flashing several new roms with the recovery. They all where flashed succesfully according the recovery, but still after reboot the old omni rom is back.
I tried flashing stock roms with odin, they flashed succesfull according ODIN, but still, after a reboot the old omni rom is back
I tried flashing Andi's latest TWRP build with ODIN and my current recovery. ODIN and recovery said it was succesfull but after reboot there is still the old recovery.
So basically it seems this damn thing is insome kind of read-only mode......
Any idea howto fix this ?
This is what is currently installed on the tablet :
TWRP 2.8.7.2
omnirom 5.1.1-20151116-2332-p5100-HOMEMADE
kernel 3.0.101-Omni [email protected] #1
zorka said:
My P5100 is acting strange. Short after booting it gives errors about gapps and other apps being stopped. Those messages keep popping up, so nothing else except rebooting/shutting down is possible.
Everything I try to change (in the short time before the errors pop up) is gone after a reboot.
I tried flashing several new roms with the recovery. They all where flashed succesfully according the recovery, but still after reboot the old omni rom is back.
I tried flashing stock roms with odin, they flashed succesfull according ODIN, but still, after a reboot the old omni rom is back
I tried flashing Andi's latest TWRP build with ODIN and my current recovery. ODIN and recovery said it was succesfull but after reboot there is still the old recovery.
So basically it seems this damn thing is insome kind of read-only mode......
Any idea howto fix this ?
This is what is currently installed on the tablet :
TWRP 2.8.7.2
omnirom 5.1.1-20151116-2332-p5100-HOMEMADE
kernel 3.0.101-Omni [email protected] #1
Click to expand...
Click to collapse
Something strange I just noticed.... In download mode it says "downlaod" instead of "download". Is this normal ? see screenshot
probably the same as this.......
http://forum.xda-developers.com/galaxy-tab-2/help/gt-p3100-boot-loop-recovery-information-t3307456
zorka said:
probably the same as this.......
http://forum.xda-developers.com/galaxy-tab-2/help/gt-p3100-boot-loop-recovery-information-t3307456
Click to expand...
Click to collapse
Find the 4 firmware files for tab 2 series, I tried but can't find working links anywhere. That may recover some cases of bricks and errors. I requested on other forums but, still found none available.
The emmc bug, has only one solution until now, replacement.
Hi all,
I have a P5110 tab 2.
I rooted and installed CM 10 on this device some time ago, and it's been working fine for many months.
Recently, it's started rebooting itself from the OS - i.e not at boot logo etc - it actually gets into the OS, lets you do a few things for a few seconds, then thows you out and reboots.
This device has an older version of CWM on.
I can boot into CWM Recovery, have tried wiping dalvic, cache, - everything - but still the reboots.
Have tried to load twp from zip via CWM, it says installed ok. I reboot, go back into recovery, and its still this old version of CWM.
With this being an older version of CWM, it wont let me install the later versions of CWM.
Im thinking of reflashing the stock rom (4.x.x afair), to hopefully stop the reboots, so I can get into the OS and flash the later version of TWRP, so I can then flash a later version of CM.
All a PITA!
Question is - why does the p5110 keep rebooting, out of the OS?
I read somewhere that this could be a hardware issue - chip over heating or something.
Is this device worth bothering with?
Second question - why wont CWM let me install TWRP (from Zip in external SD, .img is in the zip) - even though it says it has installed it?
Any thoughts or assistance greatly appreciated!
Could this be the "dreaded emmc chip" issue?
If this was indeed the issue - would it boot to the OS at all?
I'm assuming not, and therefore this isnt the issue - can someone confirm?
http://forum.xda-developers.com/galaxy-tab-2/general/discussion-alternative-tab-2-emmc-bug-t3306862
Maybe it is. You said you tried to flash the later versions of cwm but it didn't work yes? I think one of the symptoms is that you can't flash anything on the device because it became read-only. I may be wrong though so kindly check
EDIT: Maybe do a factory reset? If everything is still there after the wipe, 99% your emmc got read-only.