• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[ROM][P51xx][5.1.1] Samsung Galaxy Tab 2 AOSP-Project

Status
Not open for further replies.

Android-Andi

Recognized Contributor
Mar 3, 2013
10,846
29,198
0
andi34.github.io
Samsung Galaxy Tab 2
AOSP - Project


This Rom is based on AOSP to give the user a pure AOSP feeling.
The builds only includes device specific changes to compile and get a booting AOSP!


Code:
#include 
/*
 * I am not responsible for bricked devices, dead SD cards, thermonuclear
 * war, or the current economic crisis caused by you following these
 * directions. YOU are choosing to make these modifications, and
 * if you point your finger at me for messing up your device, I will
 * laugh at you.
 */
Downloads:
ROM Downloads for all supported devices can be found here
(Those who have a repartitioned system partition use "not-block-based" builds! Other builds won't be flashable on those devices!)

[#DONATETOME]

FAQ
Q: Will there be any updates?
A: Yes, there will, but only if i can fix a bug or AOSP releases an Update - else there's no update needed.

Q: There's a nice feature in XXX-Rom and i like to have this included - ADD IT!
A: Sorry, i'lll keep this Rom Stock-AOSP as possible. Maybe XXX-Rom is a better choice for you, if you really need this feature.

Q: How to enable root?
A: This Rom doesn't have root included. Why? Because root isn't part of AOSP. You can find the way to SuperSU Thread from @Chainfire and download SuperSU as flashable-ZIP if you need root.

Q: Is it possible to overclock the kernel?
A: Yes and no. First of all you need root and a Kernel-App like KernelAdiutor. After that you can slight OC the CPU & GPU - this Rom includes latest SlimLP Kernel.

Q: I found a bug.
A: Nice finding my friend :) Please provide needed logs - ADB will be your best friend, if you are replying in a development thread :)
There's a lot of tutorials out on YouTube or XDA on how to setup and use ADB - it's really simple!
At least you should tell step by step how to reproduce the issue.


I started creating a gerneral FAQ on my github - it includes instructions how to flash a Rom, how to get proper logs, etc. etc. etc., you can find it here

Changelog
Code:
2015-11-08 It's stock AOSP as released by Google (Android 5.1.1 R29 LVY48I), only additions
- screenshot: quick delete action
- advanced reboot menu
- Launcher3 instead Launcher2
- BootMessage: Show each app name being optimized during boot
- Show application's package name in the "App info" screen.
- Open app when clicking on icon in App Info screen

(... forgot about the releases between ...)

2015-08-07 based on Android 5.1.1_r9
XDA:DevDB Information
[P51xx][5.1.1] Samsung Galaxy Tab 2 AOSP-Project, ROM for the Samsung Galaxy Tab 2

Contributors
Android-Andi
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP

Version Information
Status: Testing

Created 2015-08-07
Last Updated 2017-04-30
 

luckywang95

Member
Jul 12, 2014
25
2
0
stuck at samsung galaxy tab page

Is it normal that it stuck at samsung galaxy tab page for the first boot after flashed? i only flashed the rom and a minimal gapps, using the latest twrp 2.8.7.1. waited for like 30mins but it still there
 

Android-Andi

Recognized Contributor
Mar 3, 2013
10,846
29,198
0
andi34.github.io
Is it normal that it stuck at samsung galaxy tab page for the first boot after flashed? i only flashed the rom and a minimal gapps, using the latest twrp 2.8.7.1. waited for like 30mins but it still there
No. Data or cache on f2fs? If yes format them back to ext 4.
Also make sure you did a clean install.
Try without gapps maybe, if it boots you can flash gapps after that.
 

Android-Andi

Recognized Contributor
Mar 3, 2013
10,846
29,198
0
andi34.github.io
I reformat everything including data, cache, internal storage, system.... all in ext4... :crying:
Wipe data, system, cache, dalvic.
Reboot recovery once.
Flash rom.
(Any error messages visible?)
Reboot.

If it boots, boot back into recovery and flash gapps.

If still not work, start clean flash again and get a recovery.log directly after flashing.
 
  • Like
Reactions: badluckbro661

luckywang95

Member
Jul 12, 2014
25
2
0
Wipe data, system, cache, dalvic.
Reboot recovery once.
Flash rom.
(Any error messages visible?)
Reboot.

If it boots, boot back into recovery and flash gapps.

If still not work, start clean flash again and get a recovery.log directly after flashing.
I tried wipe everything to ext4 again and reflashed the rom with and without gapps. also tried using twrp 2.8.4.1 to flash the rom but still the same. No error message given. Im trying one more time now... :crying:
 
Last edited:

Android-Andi

Recognized Contributor
Mar 3, 2013
10,846
29,198
0
andi34.github.io
I tried wipe everything to ext4 again and reflashed the rom with and without gapps. also tried using twrp 2.8.4.1 to flash the rom but still the same. No error message given. Im trying one more time now... :crying:
It's important sometimes to reboot the recovery once after wipe.
Latest twrp you also need to confirm to allow changes on system partition (you'll be asked on booting twrp)

After flashing please use adb to pull the log
adb pull /tmp/recovery.log while still in TWRP

What's your device? P5100 or p5110?
 

luckywang95

Member
Jul 12, 2014
25
2
0
It's important sometimes to reboot the recovery once after wipe.
Latest twrp you also need to confirm to allow changes on system partition (you'll be asked on booting twrp)

After flashing please use adb to pull the log
adb pull /tmp/recovery.log while still in TWRP

What's your device? P5100 or p5110?
yes. i chose allow changes. my device is p5100. installation failed. i will get recovery.log now and upload to u soon.

---------- Post added at 10:45 AM ---------- Previous post was at 10:31 AM ----------

It's important sometimes to reboot the recovery once after wipe.
Latest twrp you also need to confirm to allow changes on system partition (you'll be asked on booting twrp)

After flashing please use adb to pull the log
adb pull /tmp/recovery.log while still in TWRP

What's your device? P5100 or p5110?
I have a new problem. Im still a new member so im not allow to pots a link or attach any file to here. how am i able to send the log file to you? :confused:
 

Android-Andi

Recognized Contributor
Mar 3, 2013
10,846
29,198
0
andi34.github.io
Tried flashing from different path?
/external_sd/[ROM][P5100][AOSP]

Maybe all th [ and ] in the path aren't good. Can't see any issue in the log...

If still not work:
On Galaxy Tab 2 logo you'll be able after some seconds to get adb access.
Please take a logcat & dmesg
 

luckywang95

Member
Jul 12, 2014
25
2
0
Tried flashing from different path?
/external_sd/[ROM][P5100][AOSP]

Maybe all th [ and ] in the path aren't good. Can't see any issue in the log...

If still not work:
On Galaxy Tab 2 logo you'll be able after some seconds to get adb access.
Please take a logcat & dmesg
but i have the same directory when i flash the cm12? :confused:

---------- Post added at 11:58 AM ---------- Previous post was at 11:12 AM ----------

Tried flashing from different path?
/external_sd/[ROM][P5100][AOSP]

Maybe all th [ and ] in the path aren't good. Can't see any issue in the log...

If still not work:
On Galaxy Tab 2 logo you'll be able after some seconds to get adb access.
Please take a logcat & dmesg
well... i tried for quite a long time. when it stuck at samsung logo, it doesnt connect to my computer. just now the recovery.log i was using my external sd card...
 

Android-Andi

Recognized Contributor
Mar 3, 2013
10,846
29,198
0
andi34.github.io
but i have the same directory when i flash the cm12? :confused:
.
ok, then it's not the cause

well... i tried for quite a long time. when it stuck at samsung logo, it doesnt connect to my computer. just now the recovery.log i was using my external sd card...
Adb should work, have you tried?

You can check on:
adb devices

You'll see if it detects the device.

Maybe download minimal adb and fastboot, easy to use ;)
 

luckywang95

Member
Jul 12, 2014
25
2
0
ok, then it's not the cause



Adb should work, have you tried?

You can check on:
adb devices

You'll see if it detects the device.

Maybe download minimal adb and fastboot, easy to use ;)
its not connected to computer... i cant use adb.... i tried installing all driver... but still cannot... adb devices shows nothing..:crying:

---------- Post added at 12:23 PM ---------- Previous post was at 12:04 PM ----------

ok, then it's not the cause



Adb should work, have you tried?

You can check on:
adb devices

You'll see if it detects the device.

Maybe download minimal adb and fastboot, easy to use ;)
sorry, just now is my usb hub not working. not the device. dmesg and logcat i uploaded to google drive. in this folder. it included the recovery.log just now.

https://drive.google.com/open?id=0B...9Ydkw3T0VfZUhWS0ticHdtYnhOQ1hWTFhhRkVtSEh3QVE

logcat is empty. but it is still in the folder.:)
 
Last edited:
Jan 5, 2015
13
2
3
Hello AndroidAndi
First, thank you for this rom and I have not had any problems during installation.
Full wipe (data, cache, dalvik, format system) and installation of Gapps tk_gapps micro-modular-5.1.1.
If you want sreens? :



Sorry for my English

Dirk
 
  • Like
Reactions: pengpengback
Status
Not open for further replies.