yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 10.1" Android Development] mcore09:
Startup and Reboot Issues

Beautiful ROM. Quick startup and very responsive.

I'm having issues with booting up and rebooting on my P5113.

My setup:

Dhollmen Rom KIT-KAT 4.4.2 - 2014 02 09 (Dhollmen-Rom_KK-4.4.2-20140209-p5110.zip)

Viper4Android IRS 4.4 - 20140125

Gapps 4.4 - 20140210

Recovery TRWP-2.6.3.5 p5110/13 (Dhollmen-P511X-Recovery_TRWP-2.6.3.5.zip)

Have also tried GT-P5110_CWM_6.0.4.7-Swipe-Edition.zip from this post.

From a running system, attempting to "Power Off" results in a reboot back into the ROM. Attempting to Reboot to Recovery results in a reboot into the ROM.

I can forcefully enter Recovery by holding Power and Volume Down buttons. Once in Recovery, I'm unable to reboot into the ROM! All attempts from TWRP or CWM to reboot go directly back to Recovery. The only way I've found to reboot into the ROM is to plug in the charger, hold the Power button until the battery charging indicator is displayed, and then after a moment press Power again.

I have gone so far as to do a full wipe/reset and reflashing Dhollmen, GApps, and Viper4Android IRS.

EDIT: If it helps, when I attempt to reboot to system in Dhollmen TWRP, the screen goes black as if it's about to reboot. After a few seconds of waiting I can tap the Power button and see TWRP, and it's hung up (frozen).

Any help?
[Galaxy Tab 2 10.1" Android Development] schurgatzi:
Thx for the answer .. so i gonne download the rom later and gonne give it a try. Will Report :D
[Galaxy Tab 2 10.1" Android Development] samsgun357:
I just saw this post from Android-Andi, it may be your issue...???

IDK if someone doesn´t know how to do a EFS Backup and if all of you already have it ?

I now read 3rd time of broken EFS because people flashing CWM wich wasn´t build for our device.... device won´t boot with a broken EFS Partition.

Here´s how to Backup EFS: http://xdaforums.com/showpost.php?p=50182886&postcount=2

Eat Play Google
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
[MENTION=4625647]samsgun357[/MENTION] same got reported for Dhollmen-TWRP before in my Recovery-Thread... i asked for a logcat and asked for a recovery.log - i got nothing = not my problem....

[MENTION=4045206]mcore09[/MENTION] do you have the JB-Bootloader? Maybe it´s a problem if you don´t have it... you only have it if you have been on Stock 4.1.x or 4.2.2 (Odin, OTA or KIES) or if you flashed it manually.
[Galaxy Tab 2 10.1" Android Development] tuxafgmur:
[MENTION=5153662]Android-Andi[/MENTION], I'm a little confused I guess.

What should I do with this story about recovery? :confused:

P.S. I don't follow your Recovery thread and I can't find where mentioned to me for a warning.
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
[MENTION=5117218]tuxafgmur[/MENTION] no offense :D sorry if you got me wrong. i am really happy to have you here for P51XX because i don´t own this device and you are the only P51XX owner&developer.

someone reported the same problem using your TWRP in my Recovery thread too --> http://xdaforums.com/showpost.php?p=50057375&postcount=56 & http://xdaforums.com/showpost.php?p=50087665&postcount=67

IDK if it´s only a problem using your TWRP or if same happens to someone using the TWRP i provided. I asked for a logcat from recovery and for a recovery.log to take a look on it and hope to find the problem - but bleagueswas unable to get a log and i told him without a log a problem not exist if he´s the only one faceing this problem (i also asked first time in CM11 thread when it got reported = no log = no problem for me).

idk your TWRP build-flags and can´t say if there is something different between our TWRP´s.

Now i see that mcore09 also tried my CWM swipe - it must be a problem on user-side.

IDK if all of them have updated their bootloader, maybe that could be a reson?
[Galaxy Tab 2 10.1" Android Development] tuxafgmur:
[MENTION=5153662]Android-Andi[/MENTION], I think you're wrong.

I'm not sure about any of these issues TRWP related.

When I first installed TRWP same thing happened to me, but it was coming from CWM, after fail instalation.

Subsequently I have had no problems of any kind and it works like a charm.

There is another issue.

You recommend a particular update-binary file. Days ago I saw it and I downloaded and tried it.

There was no way to install with this file. (I can't do)

I'll take my own update-binary as I think it is working correctly.

P.S: I think bootloader has nothing to do here.

P.S: First time (If user had any problems previously) new recovery must be flashed by Odin or Heimdall. Next time, no problem with zip.
[Galaxy Tab 2 10.1" Android Development] mcore09:
No, I don't have JB-bootloader (not sure where to look either).

I'm coming from a custom 4.1.2-based ROM. I initially tried flashing Dhollmen using my older version of CWM, which resulted in a Status 7 error and I figured out that I needed to upgrade CWM. I did so (by flashing it to the aforementioned build for p5110/5113), then flashed Dhollmen. When I discovered the boot/reboot issues, I then flashed TWRP to no avail.
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
[MENTION=4045206]mcore09[/MENTION] please try flashing a recovery using odin or heimdall and report back if it fixed it.

about the bootloader read here, idk if it will fix it: http://xdaforums.com/showpost.php?p=50077564&postcount=611

please don´t forget to backup efs first, if you wan´t to give it a try: http://xdaforums.com/showpost.php?p=50182886&postcount=2

[MENTION=5117218]tuxafgmur[/MENTION] google changed the way getprop works, that´s why some update-binary won´t work - it can´t read the getptop lines from updater-script. i cherry-picked a patch to make TWRP 2.6.3.5 compatible with old update-binary.

there are ~ 900 downloads of TWRP 2.6.3.5 (p5100 and p5110 together), cwm 6.0.4.7 ~ 700 downloads, advacned cwm 6.12.8 ~ 100 downloads. i think you´ll have a lot of downloads for your TWRP, that´s why i think there must be something wrong on user side and the only thing i can think about: jb-bootloader. idk if it has something to do with it, but i remember weired graphic glitches on boot when i flashed CM 10.2 first time without the JB-Bootloader. Other people confirmed working of those recoverys (i also shared my recoverys in a german forum - no negative feedback), that´s why i am sure now it´s not related to the recoverys,
[Galaxy Tab 2 10.1" Android Development] cop3rth:
+1

i have the same issue also, sd card pointed out it has 0.00 total space, although i can unmount n mount it back

but its accessible in cwm recovery

is there any solve for this?

and i did clean install using latest rom Dhollmen-Rom_KK-4.4.2-20140209-p5100

using 64Gb micro sd class10 if that helps

other than that rom works really well

thanks b4 ^^

Cheers~
[Galaxy Tab 2 10.1" Android Development] tuxafgmur:
+1

I know: Google change & little patch. My recovery is pached.

Last Sunday I'm thinking to rework TRWP, but I have no time enough and maybe ---> new testing = new problems :(

P.S. Graphic glitches on boot are only issue by old bootloader. It is not problem.
[Galaxy Tab 2 10.1" Android Development] samsgun357:
64gb sdcards have to be formatted a certain way(don't recall the format) and the ROM/kernel have to support that format. Hopefully someone who knows exactly can help with this???

Watch, as I combine all the juice from my mind...
[Galaxy Tab 2 10.1" Android Development] Scalar1111:
U have to format the SD Card with Fat32. Windows 7 can't do this, but here is a Video where u can see how it works. [YOUTUBE]lm3hH8dF-2w[/YOUTUBE]. Its in German, but it is easy to understand, i hope its help u.

Greets Scalar
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
But maybe the old bootloader breaks the Recovery? Only different that´s possible if i can see it right, because it´s working for many other user without that issues...

But... we still got no locat from recovery and no recovery.log :p

All about my TWRP config´s for Tab 2 ;)

P51XX

TWRP-Flags

https://github.com/omnirom/android_...ob/android-4.4/BoardConfigCommon.mk#L129-L142

twrp.fstab:

https://github.com/omnirom/android_device_samsung_p5100/blob/android-4.4/rootdir/twrp.fstab

https://github.com/omnirom/android_device_samsung_p5100/blob/android-4.4/p51xx-common.mk#L40

P31XX

to fix touch

https://github.com/omnirom/android_...android-4.4/rootdir/init.recovery.espresso.rc

https://github.com/omnirom/android_device_samsung_p3100/blob/android-4.4/p31xx-common.mk#L38

Flags

https://github.com/omnirom/android_...ob/android-4.4/BoardConfigCommon.mk#L129-L142

twrp.fstab

https://github.com/omnirom/android_device_samsung_p3100/blob/android-4.4/rootdir/twrp.fstab

https://github.com/omnirom/android_device_samsung_p3100/blob/android-4.4/p31xx-common.mk#L41
[Galaxy Tab 2 10.1" Android Development] tuxafgmur:
I think it is not bootloader problem as this must only load kernel and print welcome screen. :confused:

Once the recovery kernel take control no longer able to think it influences any more.

Who is the user to send these log ?

Can you remind him?

:confused:
[Galaxy Tab 2 10.1" Android Development] cop3rth:
thank you for the suggestion, my micro sd is formatted as exFat

so i re-format it as FAT32 and now it works as it should be, detecting 59.46GB

and all my files are accessible

thank you :D

Cheers~
[Galaxy Tab 2 10.1" Android Development] schurgatzi:
Have installed and tested this rom this morning.

But no luck ... cant get sound working with dock.

Ofc the tablet speaker are working, but thats not the goal of putting the tab in the dock

and connecting a sound jack to the dock also.

Any help?
[Galaxy Tab 2 10.1" Android Development] mcore09:
I flashed GT-P5110_TWRP_2.6.3.5.tar.md5 from this post using odin. It succeeded without error. Unfortunately, my boot/reboot issues are unchanged.

I went one step further and tried to flash JB-Bootloader (P5110_JB_SBL.tar.md5) from this post as you suggested, but receive this error from odin:

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5110_JB_SBL.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> Sbl.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

UPDATE: Previous write error above was using Odin 1.85. I used Odin 3.07 and succeeeded in flashing JB-Bootloader. However, boot/reboot issues persist.
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
efs backed up?

maybe try a different odin version.

else start from scratch. try on your own risk:

wipe system, cache, dalvic, data - without that you will get bootloop.

reboot download Modus

flash stock 4.1 rom for your device (this will update the bootloader too)

setup, and start from 0.
[Galaxy Tab 2 10.1" Android Development] mcore09:
I was able to flash JB-Bootloader (see update to previous post).

Yes, I backed up EFS. Also wiped system, cache, dalvic, data then tried flashing Dhollmen ROM/Gapps and starting over. Symptoms persist.

Not sure how to proceed with the rest of your recommendations - what is Modus?

Thank you for all your help!
[Galaxy Tab 2 10.1" Android Development] orion2323:
I just bought a Tab 2 10.1 P5113 and decided to try this ROM

Very simple to install...everything is up and running

Did it using TWRP

Looks good, feels good.....only time will tell :)

Thanks OP for your hard work and dedication
[Galaxy Tab 2 10.1" Android Development] tuxafgmur:
HI, [MENTION=4045206]mcore09[/MENTION]

It is best to start from scratch.

Here are the steps that you should follow:

Download Stock 4.1 or 4.2 from here: http://live.samsung-updates.com/

Find the Rom nearest your country , but is true regardless of the same region (Europe, North America, South America, Asia, etc)

Download Odin3-3.07 or Odin3-1.85 (I've never used any of them since I have not Window$)

Restart your device in Download Mode (you'll see Android Logo on screen)

Flash your Stock system and restart

If all went well, you'll have an "Original Stock" device.

Now your are ready to go:

Root your device as usual.

Flash Andy's GT-P5110_TWRP_2.6.3.5.tar.md5 using Odin.

Restart to Recovery.

If all went well, your problem had gone.

Now you are ready to:

Install my Recovery if you like.

Install Dhollmen Rom if you wish .

Install any other Rom if you want.

Regards
[Galaxy Tab 2 10.1" Android Development] wmwamidi:
The downside with Fat32 is that one can not copy files bigger than 4GB to the SD card. So bear this in mind if planning to carry huge files with you. My 64GB SD works great with CM11 but not this ROM. Any cure?
[Galaxy Tab 2 10.1" Android Development] christty31:
c'mon guys!

using KK last version of this ROM, but is battery crazy....

in stand by mode (sleep) from 72% to 12% in 2 days... :((
[Galaxy Tab 2 10.1" Android Development] orion2323:
So after a week or so, I decided to go with a different Android version, 4.3.1

Nothing rom with this ROM, it was due to known issues with KitKat 4.4.2

I had audio issues in certain games (distorted sound), game lag in certain games, and also Dice player doesn't seem to like Katkiss 4.4.2, I actually had the same issue with 4.4.2 on my Asus TF101 and had to go back to 4.3.1 as well.
[Galaxy Tab 2 10.1" Android Development] mcore09:
Thanks again. I have tried these steps several times. By flashing stock 4.1.2, my shutdown/boot/reboot problems are solved. I can then root the device using Auto-Root, and shutdown/boot/reboot still works perfectly. But if I then flash TWRP or CWM (tied both), problems return. Alternatively, if I root the old fashioned way (most recent CWM + SuperSU), problems return.

So the result is that I can have stock rooted 4.1.2, but cannot find a way to exist with a custom ROM without causing shutdown/boot/reboot issues when flashing TWRP/CWM in preparation.

I think that tonight I will try restoring my EFS backup (from stock 4.1.2) after flashing TWRP. Does that sound like a next logical step?
[Galaxy Tab 2 10.1" Android Development] 1369:
1st, I'm completely blown away by how smooth and fast this ROM is. Excellent work [MENTION=5117218]tuxafgmur[/MENTION]! If you have a way to donate, I would gladly send send cup of coffee your way.

The only question I have is in regards to the toggles. I can't get the "Current User" toggle to show the image and name. As of right now, it just shows the default unknown image.

If anybody knows how to change this, I would greatly appreciate it and thanks will be given of course.
[Galaxy Tab 2 10.1" Android Development] bafforosso:
I'm also really disappointed by the battery life on KK, I use to be able to go approx 7 days in deep sleep with the previous android version, now I'm happy if there's still some power left after 3 days. I'm trying with "Always Allow Scanning" disabled, hope it'll help.
[Galaxy Tab 2 10.1" Android Development] nachordez:
Yes, there is an anomalous draining during deep sleep, but not just on this ROM, and not for everyone (perhaps only 511x? Which one is yours?). I know tux is trying to guess (I sent him some logcats, don't know if they'll help...), but it's something obscure and difficult to catch...

from gt-p5110
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
Thank you for mentioning this. Odin 1.85 seems to get outdated. I have used it short ago for another device and it also failed....although the notebook I used is usually absolutely reliable.

I have removed it from my bootloader flashing guide now.

(PS does anybody have experience with Odin 3.09? I downloaded it today, it was sticked together with some 4.2.2 stock ROM for the P5110....I didn' t read about it in context to our Tab yet)
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
I do not think so :p

idk what's your problem.... but you didn't bought a varizon tab, right?

Edit: maybe boot into recovery and run a recovery-log. also run a logcat if possible. please attach both files here.
[Galaxy Tab 2 10.1" Android Development] mcore09:
No, this is a p5113 (Wi-Fi only model)
[Galaxy Tab 2 10.1" Android Development] bafforosso:
Thanks for the info.

I've got the 5110, same as you.

If there's anything in my abilities I can do to help, please tell me, I'll gladly do.
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
please attach recovery.log and logcat from recovery.
[Galaxy Tab 2 10.1" Android Development] christty31:
regarding battery drain issue, i have P5100 model WIFI+3G...

i like the KK ROM but battery drain is waaay too much :(
[Galaxy Tab 2 10.1" Android Development] tuxafgmur:
I have p5100 too.

I have not battery drain at all.

Can you test with Wifi "Always Allow Scanning" unselected? - (this option should never be enabled )

Before I've prepared this Rom I've tested Mokke and Omni.

I did not find excessive battery consumption, but from the first tests at Dhollmen, I appreciated a marked decrease in consumption.

[MENTION=4479038]nachordez[/MENTION] send me logcats from his device but I can't find nothing anomalous, for now.

I continuous research.
[Galaxy Tab 2 10.1" Android Development] dmcdonnell:
I have a P5100 with no battery issues. I am using CM11 nightly and Dhollmen Kernel (both up to date). When flashing the first time, I wiped and formatted system, data and cache. cmupdater keeps me up to date and I wipe cache and dalvik after each nightly update. I have not had a single force close since my first install on Feb 1st.
[Galaxy Tab 2 10.1" Android Development] mcore09:
Attached.
[Galaxy Tab 2 10.1" Android Development] TheWall-[ITA]:
I have a P5110 and I'm on AOKP at the moment, but I'm experiencing same battery drain. I disabled the "Alway allow scanning" in WiFi option and battery seems to be really better ;)
[Galaxy Tab 2 10.1" Android Development] nachordez:
That obviously improves, but that's not the point we are talking about. With no WiFi, no scanning, no GPS, being deepsleep, doing really nothing, and graphic showing tab as doing nothing, sometimes starts to drain battery very noticeably. But there's no signal about what drains in battery graph, nor BBS, no strange wake lock, nothing strange in log cat....mystery... And happen in different roms in this tab to different users..... But not everyone. Really strange.

from Nexus 4
[Galaxy Tab 2 10.1" Android Development] TheWall-[ITA]:
Oh ok, I saw the post by tuxafgmur asking for testing to disable that feature and so I replied with my experience. :)

Let's hope he'll find out the problem :fingers-crossed:
[Galaxy Tab 2 10.1" Android Development] tuxafgmur:
New Recovery files avalables to download in post #2 :good:
[Galaxy Tab 2 10.1" Android Development] mcore09:
Sorry, I just realized that the logcat I provided earlier was empty. Attached is logcat from normal startup, as well as attempted shutdown (where p5113 only reboots, won't shutdown).

You asked for a logcat from recovery, but I'm not sure how to do that.
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
i look into it in the evening.

didn´t found anything wrong in recovery.log yesterday.

(maybe logcat empty every time in recovery? i´ll test it myself :p )
[Galaxy Tab 2 10.1" Android Development] Myhigh:
I'm in the same boat. Prior to the rom upgrade I had plenty of standby life. Now the tablet won't last almost over night off the charger. In use battery is very acceptable too.
[Galaxy Tab 2 10.1" Android Development] nachordez:
[MENTION=5117218]tuxafgmur[/MENTION] posted on Cm thread

http://xdaforums.com/showthread.php?p=50507146

Perhaps related?

from Nexus 4
[Galaxy Tab 2 10.1" Android Development] ebs512:
the only problem i found with this rom was the play store didnt auto restore the apps from stock like slimkat did
[Galaxy Tab 2 10.1" Android Development] nachordez:
Yup. But I even prefer this so! I prefer to reinstall faster through TB :)

from gt-p5110
[Galaxy Tab 2 10.1" Android Development] tuxafgmur:
There are countless apps by Google (Gapps)

Each of us uses a certain, ignoring the rest.

Why I would install something that you may not need? :angel:
[Galaxy Tab 2 10.1" Android Development] tuxafgmur:
I think modem not related because P5110 does not have modem.

Delete /data/media directory also delete internal /sdcard (one is a link to the other)

This post also mentions TvoutService_C but my Rom do not start this service except P5113 models.

The only relevant In your logs is

D/Tethering( 441): Exception adding default nw to upstreamIfaceTypes: java.lang.NullPointerException

I am studying this, but for now I think is Gapps related, the worst option as it would very bad deal.
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
[MENTION=4543339]ebs512[/MENTION] reported the same issue. Maybe there´s something wrong with P5113 ... idk.

[MENTION=5117218]tuxafgmur[/MENTION] any idea why P5113 haveing problems P5110 don´t ?

On Tab 2 7.0 P3113 don´t face such issues...

maybe [MENTION=4045206]mcore09[/MENTION] can try flashing the recovery.img using Heimdall and see if it fixes it.

Edit:

[MENTION=5117218]tuxafgmur[/MENTION] for P31XX we don´t have TvoutService in Kernel, maybe that could be the problem? Maybe we can remove such lines from init.espresso10.rc and see if this will change anything... only general different´s i can see between P31XX and P51XX
[Galaxy Tab 2 10.1" Android Development] nachordez:
Yes, I also have this bad feeling...

Anyway, will try to wipe/format everything when I have time enough to see what happens (this days I really need my tab daily). Something obscure could be lurking there... I have that in my to do list since some days.

Thanks

from Nexus 4
[Galaxy Tab 2 10.1" Android Development] wmwamidi:
Uncertain

Probably ebs512 was not clear enough. What I think he means is auto install of application synchronised to a google account. Most ROMS inkl. Dhollmen 4.3.1 synchronise apps after flashing. This one requires one to either re-install all apps or resort to TB. TB is not that reliable when it comes to restoring to a totally new rom.
[Galaxy Tab 2 10.1" Android Development] tuxafgmur:
[MENTION=5153662]Android-Andi[/MENTION], as I changed TvoutService on Dhollmen Rom I was checking not unduly activated, but I have seen the logs from [MENTION=4479038]nachordez[/MENTION] that is not so.

Since my Rom, randomly, also suffers from this problem (and a user of a Spanish forum states that it also occurs on a Motorola device) not think that's what drains the battery, plus in your case, would be continuous.

I am not aware. Can you resume the issue?
[Galaxy Tab 2 10.1" Android Development] tuxafgmur:
Yes, I think this also.

What do you suggest?
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
[MENTION=5117218]tuxafgmur[/MENTION] i have no idea about the recovery thing... [MENTION=5061733]CSP III[/MENTION] seems to own 2 P5113 withput haveing recovery problems :p

i think it´s on userside.... maybe Heimdall will do the trick.
[Galaxy Tab 2 10.1" Android Development] ebs512:
This tablet (p5113) is not mine but a co-worker of my girlfriends. On 4.2.2 she kept getting an update firmware message and downloaded the 64mb update but it would not install said something about Kies(Samsung Software) or take it to Samsung Repair. The software method did not work. She wanted all her apps from when she was on stock, I had a backup but must have deleted it when I did the 1 step root/recovery/busybox method. This rom is nice but since I can't get all the apps she originally had to automatically update I'll have to stick her with SlimKat which does automatically update all the apps she had from 4.2.2 stock, thanks for the work but if this was not the issue I would have left the rom on her tablet for her.
[Galaxy Tab 2 10.1" Android Development] tuxafgmur:
Well. I think you say [MENTION=4045206]mcore09[/MENTION] ;) but I understand the issue.

I think it's really impossible he did not solve problem using heimdall.

I used Odin only one time (just for first root) but Heimdall (terminal mode) work very well.

Only a corrupt partition justifies this problem (wrong pit file) but is not logic, as he use stock Rom.