Database Info

[ROM][DEV][WIP]Android 2.3.7 For Motorola Fire XT XT530/XT531

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
I built a ROM from Stock Chinese XT532 SBF. This is ROM uses kernel 2.6.35.11. This ROM is the stock XT532 ROM.
Advantages:
Newer kernel version. Existing XT530/XT531 Kernels are Froyo Kernel. This kernel is the actual Gingerbread Kernel.
Newer drivers, so increased performance.
New Experimental Build Based on 2nd-init:
ROM Download For 2nd-init: http://www.androidfilehost.com/?fid=23269279319196536
Instructions on how to install 2nd-init ROM for XT530/XT531:
1. Flash back stock XT530/XT531 SBF via RSD-Lite.
2. Root and Install Bootmenu/CWM.
3. Put ROM zip in your SD Card.
4. Reboot device into CWM Recovery.
5. Wipe data/factory reset and wipe cache.
6. Install the zip from SD Card.
7. Reboot Phone.
8. Your Done.
If the ROM boots up via 2nd-init properly then we will be one step closer to CyanogenMod. This ROM uses the XT532 ramdisk and boots it via 2nd-init. 2nd-init ROM uses the stock 2.6.32.9 XT530/XT531 to execute XT532 ramdisk and runs it on top of the XT530/XT531 kernel.
Build based on boot.img and ROM
Downloads:
ROM:http://www.androidfilehost.com/?fid=23269279319196135
boot.img:http://www.androidfilehost.com/?fid=23269279319196191
flex.img:http://www.androidfilehost.com/?fid=23269279319196189
hidden.img:http://www.androidfilehost.com/?fid=23269279319196190
How to install a ROM not based on 2nd-init:
1. Install Bootmenu
2. Put ROM zip on the SD Card.
3. Download boot.img
4. Open a CMD line and cd to the folder where you put "boot.img" file.
5. Flash the boot.img via fastboot:
Code:
adb reboot bootloader
Code:
fastboot flash boot boot.img
Code:
fastboot reboot
6. Reboot into Clockworkmod Recovery.
7. Install the zip from sdcard.
8. Wipe cache/data factory reset from CWM Recovery.
9. Reboot phone.
10. You're done.
If radio isn't working, try using these instructions:
1. Download hidden.img and flex.img
2. Put the two img files in the same folder as fastboot.
3. Open a cmd file and cd to the folder which contains the img files.
4. Reboot the phone back into fastboot mode
Code:
adb reboot bootloader
5. Flash flex.img and hidden.img via this command in cmd
Code:
fastboot flash flex flex.img
Code:
fastboot flash hidden hidden.img
6. Reboot the device via this command in cmd
Code:
fastboot reboot
NOTE: These instructions also work for 2nd-init ROMs for Motorola Fire XT530/XT531.
Kernel Source:
Sorry, Motorola hasn't released the kernel source for XT532 which the ROM is based on. The ROM uses an unmodified Motorola XT532 Kernel.
Bugs:
You tell me as I don't own a Motorola Fire XT530/XT531
Credits:
@zhalx
@inyong1
@7amdoun
@saraghon
@Mazzen.kh
@aweosomeabhijeet

Is it tested?
What are the bugs?
thanks

Mazzen.kh said:
Is it tested?
What are the bugs?
thanks
Click to expand...
Click to collapse
I don't know as I don't a Fire XT. Basically I just extracted the XT532 SBF and I winzipped the ROM. I signed it and uploaded. Make sure you make a nandroid before flashing the ROM

rootdefyxt320 said:
I don't know as I don't a Fire XT. Basically I just extracted the XT532 SBF and I winzipped the ROM. I signed it and uploaded. Make sure you make a nandroid before flashing the ROM
Click to expand...
Click to collapse
hi rootdefyxt320,
My question:
Is this different from the previous one that already tested in cwm thread?
7amdoun said:
Here is test 2:
Reverted back to 2.3.7 phone.apk to prevent FC
Changed some ADB settings
Added nvitems from our XT530
Added logcat reader for debugging, and root file manager for playing with files without having to re-flash.
Again, for whoever wants to test, please flash the new kernel first. Format data and cache partitions after flashing (right before rebooting).
http://www.mediafire.com/?j07gvesnxgg95ep
Click to expand...
Click to collapse
saraghon said:
thanks man!
---------- Post added at 11:50 PM ---------- Previous post was at 11:10 PM ----------
Good News!!!!!!!!!!!!!
After flashing the new kernel and your last zip here is the report:
1. Wifi working and finds the network and I can connect to the internet with the browser and all other apps.
2. Radio isn't working. and can't select the network mode. I think it's because XT532 is CDMA based phone and not GSM (Because it's stuck on CDMA in Network Mode).
3. ADB working.
4. Root working with Super Su.
5. Bluetooth working.
6. Sound working.
7. FM Radio working perfect.
8. GPS working.
9. Notification bar showing Dual SIM Network icon.
10. DUAL SIM Setting in Settings.
Thanks man!!!!!
I'll figure what's up with the radio and will try to fix it!
Click to expand...
Click to collapse

inyong1 said:
hi rootdefyxt320,
My question:
Is this different from the previous one that already tested in cwm thread?
Click to expand...
Click to collapse
Probably, but you can try for yourself. I'll see if I can fix RIL as it might not work.

Good
Dowloading
Voy a probar (testing)
---------------------------------------------------------------------------------
install and bootlop

flopezm said:
Good
Dowloading
Voy a probar (testing)
---------------------------------------------------------------------------------
install and bootlop
Click to expand...
Click to collapse
Did you flash boot.img via fastboot before flashing the ROM and did you wipe data and factory reset?

rootdefyxt320 said:
Did you flash boot.img via fastboot before flashing the ROM and did you wipe data and factory reset?
Click to expand...
Click to collapse
if so it was like I did,
in another attempt to make the tutorial also 2doi-nit, and I restarted the stock recovery again and again, fails to start
quetion?
who rom stock (spain, brasilian)
try with stock rom spain and brazil

[DEV][RECOVERY] TWRP Recovery 2.7.0.0

TWRP Recovery
For Galaxy Fit
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
BUGS:
If you have found a bug, please consider posting it here.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
@chraso: Hosting & for providing Compatible flags
Me: Compiling

CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.

DOWNLOAD:
http://www.mediafire.com/view/?xum64uit9a43q6s
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!

About the current build:
STABLE.
Reboot to system bug now fixed.

Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2

TpupLpasa said:
One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works.
Click to expand...
Click to collapse
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail

TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
1st - install PhilZ Touch Recovery 6.40.1.
2nd - install twrp.

My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.

Ok, thanks.
update
Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:

Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
I would advise against this. I tried it and it soft bricked my phone.
I will wait for the official release, which I hope will be soon. I really like TWRP.
jemail

TpupLpasa said:
Well...thanks...One problem that i found..it doesn't reboot to system,just goes back to recovery..I didn't try anything else..Flashing zip works..just went back to cwm
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
jemail said:
Confirmed. Reboot System reboots to TWRP Recovery not System.
Flashing zips works.
Back Up and Restore of Nandroid ROM images works.
@Bhargav97
Any progress on reboot to recovery bug?
jemail
Click to expand...
Click to collapse
iSanechek said:
Ok, thanks.
update
heh, doesn't work. I just use Windows 8.1 with the latest updates. Maybe this is a problem... Maybe not...:crying:
Click to expand...
Click to collapse
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: remooved

belyava said:
@Bhargav97, as you kindly asked me I tried to complete the recovery image.
Guys, as I don't own any Fit device, you'll have to flash this at your own risk. Though I've done this before for my device. If anything will not work - let me know. Good Luck!
DL Link: http://yadi.sk/d/IAr6Z_OvQohqq
Click to expand...
Click to collapse
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail

jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
No success I am afraid.
jemail
Click to expand...
Click to collapse
sorry, I must have made a mistake. I''ll check tomorrow. Sorry for the inconvenience

jemail said:
The recovery image you supplied causes a long boot freeze at initial Samsung Logo followed by reboot and long boot freeze and reboot.... etc.
Boot to recovery using hardware keys produces the same result.
This image completely screws the boot image too, you cannot normal boot after flashing the recovery image. Reflashing the previous working recovery image does not help. I have to restore a recovery image using ODIN to get back to a functional recovery.
No success I am afraid.
jemail
Click to expand...
Click to collapse
Ok, try this one

belyava said:
Ok, try this one
Click to expand...
Click to collapse
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail

jemail said:
Success!
Install Zip -> works.
Back up -> works.
Wipe -> works.
Restore -> works.
Reboot System -> works.
Reboot Recovery -> works.
Great work.:good:
Will continue to test and report any bugs.
jemail
Click to expand...
Click to collapse
There are a lot of method nowadays for unpack-repack and most of them fails to make a proper repack, so you'll have booting problems like you had when you tried to do it yourself. I just told @belyava to do unpack-repack because he did this with the recovery (TWRP - had same reboot to system issue) of his device successfully. Thanks @belyava for this help.
Everything expected to work. However, you can always report bugs with a proper recovery logfile.
Updated download link with a new mediafire link. The latest build can be now labelled as STABLE build.

hi anyone have got it if possible in rar zip for this recovery.

ahmetakin said:
hi anyone have got it if possible in rar zip for this recovery.
Click to expand...
Click to collapse
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.

swat4samp said:
Why do u need a flashable package when u can install it simply via terminal emulator?
@jemail will u kindly check the time taken while backup and restoring rom? Just to know whether this is better than CWM.
Click to expand...
Click to collapse
I can't speak for your ROM, but for me back up ( 3 1/2 mins max) and restore (3 1/2 mins max).
jemail

Ok yesterdeay install with terminal emulator thanks.

[RECOVERY][D290n] TWRP Recovery for LG L Fino (JANUARY 2016)

* Your warranty is now void.
* You are making these modifications to your phone
* I accept no responsibility of the consequences, if any for flashing this recovery
Click to expand...
Click to collapse
Team Win Recovery Project 2.x, or TWRP2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Instruction:
1. Root your phone
2. Install Terminal Emulator from Google Play
3. Download .zip
https://mega.nz/#!UdVQgbrJ!SNvnCLhJ6JAeH89FTRdkeEzBcE6W6AAUugJrw7yCJ_g
4. Unzip files
5. Put files on external SD (/storage/external_SD)
6. In Terminal type:
su
dd if=/storage/external_SD/recovery.img of=/dev/block/mmcblk0p17 bs=2048
dd if=/storage/external_SD/aboot.bin of=/dev/block/mmcblk0p6
Click to expand...
Click to collapse
7. Done!
To reboot into recovery use Power Menu or Terminal:
su
reboot recovery
Click to expand...
Click to collapse
To flash stock ROM restore original aboot.bin, otherwise phone can brick!
1. Download: https://mega.co.nz/#!2woA0JyC!TJcUMG0sXWnkhvJTR1i7oELNF5SKj_iiaDlu2HyLtXs
2. Change name to: aboot.bin
3. Copy file to external_SD
4. In terminal type
su
dd if=/storage/external_SD of=/dev/block/mmcblk0p6
Click to expand...
Click to collapse
Now you can flash stock.
YOU CAN FLASH STOCK WITHOUT RESTORING ORIGINAL ABOOT.BIN, IT SHOULDN'T BRICK
Link to original thread: http://forum.android.com.pl/f1558/twrp-dla-lg-l-fino-d290-n-504813/
All credits goes to @kylevessPL

Yea man, I'm even goin' to try change device name from D295 to D290 because I have taken patched aboot from DUAL.

Thanks for the share but my phone says D290n so this works only for the D290n? Also is there a way to backup the aboot?

Original aboot is linked in the thread. It works only for D290n, you can find recovery for D295 on forum.

dzemiik said:
Original aboot is linked in the thread. It works only for D290n, you can find recovery for D295 on forum.
Click to expand...
Click to collapse
Thank you, my d290n is now running the recovery

Good news!
I've patched stock aboot.bin from our D290 to be able to have bootloader unlocked. It works so good
Now our device is recognised as D290N, not as D295 (DUAL).
Link to new aboot:
https://mega.co.nz/#!r053XZRC!LlD5VMuG07uUKqq9pK-1OfbMh_lfKLH_4qnlqzPXVSA
Just flash like previous.

Worked on D290G!!!

Hello everyone, can someone please upload SystemUI and Settings stock apks? just messed up mines.

ScouserCL said:
Hello everyone, can someone please upload SystemUI and Settings stock apks? just messed up mines.
Click to expand...
Click to collapse
Catch it out!
Settings.apk - https://mega.co.nz/#!btgQ3SoY!sSCvok9lUy2m2OzaWDEUqGGQiQwqFHdktccXiRYY2Vc
SystemUI (various versions) - https://mega.co.nz/#!D1RDUKxR!-JL8BXoS2ww-vIyv6oABihX79ryqWqcNzG3RQUXwZoo
https://mega.co.nz/#!ylZW1JaR!SrTgfQ90S9mdaUOdWx_qXLvQaWum74h79I7-xXRvr2A
https://mega.co.nz/#!D0Zz1brQ!q8DiV487X_r-PrVEFZk7SiQ_5KQiVQEGj6W1LbYAyh0
https://mega.co.nz/#!K0RgEAjL!Bc8QXgU1MmTY6Go5FKl97SFrdyqJJLkgPiODSk2NlsE

kylevessPL said:
Catch it out!
Settings.apk - https://mega.co.nz/#!btgQ3SoY!sSCvok9lUy2m2OzaWDEUqGGQiQwqFHdktccXiRYY2Vc
SystemUI (various versions) - https://mega.co.nz/#!D1RDUKxR!-JL8BXoS2ww-vIyv6oABihX79ryqWqcNzG3RQUXwZoo
https://mega.co.nz/#!ylZW1JaR!SrTgfQ90S9mdaUOdWx_qXLvQaWum74h79I7-xXRvr2A
https://mega.co.nz/#!D0Zz1brQ!q8DiV487X_r-PrVEFZk7SiQ_5KQiVQEGj6W1LbYAyh0
https://mega.co.nz/#!K0RgEAjL!Bc8QXgU1MmTY6Go5FKl97SFrdyqJJLkgPiODSk2NlsE
Click to expand...
Click to collapse
You are da real MVP!!!

The links to megaupload has expired. Can you upload this files again please

Here
https://mega.nz/#!k4pw2DrT!nHfWEMxjIzfiD_1HsRZsq-sx2rHY-bLdr964LtmAIgs

ty bro

kylevessPL said:
Catch it out!
Settings.apk - https://mega.co.nz/#!btgQ3SoY!sSCvok9lUy2m2OzaWDEUqGGQiQwqFHdktccXiRYY2Vc
SystemUI (various versions) - https://mega.co.nz/#!D1RDUKxR!-JL8BXoS2ww-vIyv6oABihX79ryqWqcNzG3RQUXwZoo
https://mega.co.nz/#!ylZW1JaR!SrTgfQ90S9mdaUOdWx_qXLvQaWum74h79I7-xXRvr2A
https://mega.co.nz/#!D0Zz1brQ!q8DiV487X_r-PrVEFZk7SiQ_5KQiVQEGj6W1LbYAyh0
https://mega.co.nz/#!K0RgEAjL!Bc8QXgU1MmTY6Go5FKl97SFrdyqJJLkgPiODSk2NlsE
Click to expand...
Click to collapse
Could you please explain what changes you've done?.
Thanks

Ky$h said:
Could you please explain what changes you've done?.
Thanks
Click to expand...
Click to collapse
I haven't maken any changes. Original apks for Black and White ThemeUI.

kylevessPL said:
I haven't maken any changes. Original apks for Black and White ThemeUI.
Click to expand...
Click to collapse
Oh.. Ha-ha ok

For people who are scared of bricking I recommend using adb shell when your device is connected via USB.

meganukebmp said:
For people who are scared of bricking I recommend using adb shell when your device is connected via USB.
Click to expand...
Click to collapse
better yet, just flash recovery.img with Flashify and enjoy! (the best part is... no need to change the "aboot.bin")
https://mega.nz/#!AxFBWICK!Ix-BMcgnsrI9QL9iSd_oJCkofwhzQC-LtbGY7Nj39jA

the_naxhoo said:
better yet, just flash recovery.img with Flashify and enjoy! (the best part is... no need to change the "aboot.bin")
https://mega.nz/#!AxFBWICK!Ix-BMcgnsrI9QL9iSd_oJCkofwhzQC-LtbGY7Nj39jA
Click to expand...
Click to collapse
Has this been tested on D290N ?

proudlytm said:
Has this been tested on D290N ?
Click to expand...
Click to collapse
I have a D290 and works!

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

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

Thank you Andi! I've been hoping for this! Up and running, really really smooth.
Sent from my GT-P5110 using Tapatalk

Thank you Sir.. Can't wait to try it out.
Sent from my Nexus 6 using XDA Premium HD app

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

luckywang95 said:
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
Click to expand...
Click to collapse
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.

Hello
p5110
installed no problem
thanks
regards

Android-Andi said:
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.
Click to expand...
Click to collapse
I reformat everything including data, cache, internal storage, system.... all in ext4... :crying:

luckywang95 said:
I reformat everything including data, cache, internal storage, system.... all in ext4... :crying:
Click to expand...
Click to collapse
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.

Android-Andi said:
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.
Click to expand...
Click to collapse
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:

luckywang95 said:
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:
Click to expand...
Click to collapse
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?

Android-Andi said:
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?
Click to expand...
Click to collapse
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 ----------
Android-Andi said:
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?
Click to expand...
Click to collapse
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?

luckywang95 said:
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?
Click to expand...
Click to collapse
Copy it on pastebin.com , posting here remove the http:/www and you'll be able to send

Android-Andi said:
Copy it on pastebin.com , posting here remove the http:/www and you'll be able to send
Click to expand...
Click to collapse
i have sent it to you through private message. i will do it again here.
drive.google.com/file/d/0B3WN3t7uFUZvcFh1cTRlVzdacEU/view?usp=sharing
its google drive.

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

and for your information. i tried flashed the latest cm12.1 by you as well. no problem on booting and now booted to homescreen. :good:

luckywang95 said:
and for your information. i tried flashed the latest cm12.1 by you as well. no problem on booting and now booted to homescreen. :good:
Click to expand...
Click to collapse
Good to know... Mh... Could you get me a logcat and dmesg?
I had a similar issue on p3110, but i am sure i fixed it on p5100 before compiling... Maybe something else is wrong then...

Android-Andi said:
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
Click to expand...
Click to collapse
but i have the same directory when i flash the cm12?
---------- Post added at 11:58 AM ---------- Previous post was at 11:12 AM ----------
Android-Andi said:
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
Click to expand...
Click to collapse
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...

luckywang95 said:
but i have the same directory when i flash the cm12?
.
Click to expand...
Click to collapse
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...
Click to expand...
Click to collapse
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

Android-Andi said:
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
Click to expand...
Click to collapse
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 ----------
Android-Andi said:
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
Click to expand...
Click to collapse
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.

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

[ROM][XC][O][8.0][UNOFFICIAL]OmniROM

UNOFFICIAL Omnirom
Code:
#include
/* * Your warranty is now void.
* * I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Instructions
* Backup everything if something goes wrong
* Wipe System, Cache and Data
* Install zip-file
* Flash oem-partition, see second post
All the source code for the os is available in the Omnirom Github repo.
What works?
Data (2g, 3g and lte)
Calling
Torch
Installation of Gapps
Camera
WIFI
Known Issues
NFC doesn't work
Downloads
My mediafire -folder
Thanks humberos, jerpelea, kholk, omnirom devs and many others.
XDA:DevDB Information
Omnirom, ROM for the Sony Xperia X Compact
Contributors
DJHasis
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2017-10-29
Last Updated 2017-12-04

Until Sony updates their Firmware to allow flashing of oem partition, this is a workaround to flash this partition thru TWRP recovery and using dd.
Download and unzip SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_loire.zip from https://developer.sonymobile.com/open-devices/list-of-devices-and-resources/
Create a sparse oem.img from the downloaded binaries.
Code:
$ simg2img SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_loire.img oem.raw
Then flash the oem partition (workaround, until Sony updates stock image with oem partition writable)
Boot to TWRP recovery by powering off the phone completely, hold VOL-DOWN and POWER and wait for TWRP boot.
Or, fastboot boot twrp.img
Code:
$ adb root
$ adb push oem.raw /sdcard/
$ adb shell
# dd if=/sdcard/oem.raw of=/dev/block/mmcblk0p39
Thanks NielDK for the instructions https://forum.xda-developers.com/showpost.php?p=74130466&postcount=2

great job, man!!! Ill give it a try asap! thanks a lot!

Do you need to flash the OEM image to boot to system or it is just made to boot to twrp?

XperiaGUY47 said:
Do you need to flash the OEM image to boot to system or it is just made to boot to twrp?
Click to expand...
Click to collapse
To boot to system.
Sony hasn't updated the bootloader to support oreo so we need to manually update the oem partition.

DJHasis said:
To boot to system.
Sony hasn't updated the bootloader to support oreo so we need to manually update the oem partition.
Click to expand...
Click to collapse
But can i do it with adb n fastboot tool too? Or its not going to work?

XperiaGUY47 said:
But can i do it with adb n fastboot tool too? Or its not going to work?
Click to expand...
Click to collapse
I haven't much used fastboot so I don't know how well adb works with fastboot. I just booted to twrp and used adb like in the instructions.
Of course you don't need adb if you put the raw-file on the sd-card directly with your computer. Then put the card to your phone. Boot to twrp and use twrp's terminal to write "dd if=/sdcard/oem.raw of=/dev/block/mmcblk0p39" .

DJHasis said:
I haven't much used fastboot so I don't know how well adb works with fastboot. I just booted to twrp and used adb like in the instructions.
Of course you don't need adb if you put the raw-file on the sd-card directly with your computer. Then put the card to your phone. Boot to twrp and use twrp's terminal to write "dd if=/sdcard/oem.raw of=/dev/block/mmcblk0p39" .
Click to expand...
Click to collapse
Ok, but can you add the oem.raw image here because i am such a newbie. I haven't just touched the OEM stuff so i don't know much. So as i understand:
I need that oem.raw image and twrp
And then boot into twrp
Go to terminal
Write: if=/sdcard/oem.raw of=/dev/block/mmcblk0p39
Push enter
Reboot
And no sony logo stuck and boots right into omni?
(Edit) and put the oem.raw to /sdcard/

XperiaGUY47 said:
Ok, but can you add the oem.raw image here because i am such a newbie. I haven't just touched the OEM stuff so i don't know much. So as i understand:
I need that oem.raw image and twrp
And then boot into twrp
Go to terminal
Write: if=/sdcard/oem.raw of=/dev/block/mmcblk0p39
Push enter
Reboot
And no sony logo stuck and boots right into omni?
(Edit) and put the oem.raw to /sdcard/
Click to expand...
Click to collapse
So after you have backed up every thing.
You need to wipe the system and data with twrp.
Then you can install my zip-file with twrp.
Then you need to make the oem.raw file like in the instructions with your pc.
Then you can copy that file to your sd card.
After that you can boot to twrp, open the terminal and write this " dd if=/sdcard/oem.raw of=/dev/block/mmcblk0p39 ". And push enter.
After that you can reboot your phone and every thing should work .

New build uploaded.
Mainly bug fixes for kugo and parts of omnirom.

@DJHasis Some people over at the [Nougat 7.1.X][X Compact - F5321] Android Open Source Project thread were discussing the green camera issue, thought it might help you figure out the issue...

Sony has updated the Vendor image. It contains alot fixes and now camera works.
I downloaded it and converted it. Every one can download it from my mediafire-folder.

Hey, Thanks for your Work. Is it usable AS daily Driver ?

StarSix01 said:
Hey, Thanks for your Work. Is it usable AS daily Driver ?
Click to expand...
Click to collapse
I've been using for almost two weeks.
Sometimes it might crash but devs are improving the code quite fast and the latest version is quite stable.
I'm compiling a new version on semi daily basis so you'll get the latest changes quite fast.

harryharryharry said:
@DJHasis Some people over at the [Nougat 7.1.X][X Compact - F5321] Android Open Source Project thread were discussing the green camera issue, thought it might help you figure out the issue...
Click to expand...
Click to collapse
Thanks for telling me about it. I read the post and I now know that the camera issue has been fixed.

New build uploaded. More bug fixes.

Hi! After a few days using, this rom, heres my "report":
- First boot time is so long, so be patient until it finished his work.
- Camera works perfectly with the roms cam software, there are 20,3MPx and the Automata focus continously, picture taking about a minisec.. self cam works to. But, I think the pictures a little dark...
- I found an "error".. If i set up the omni alarm and choosed the alarm sound to " random music ", it cant play any mp3 from my sd card. The phones internal storage play works good, but not from sd card...
- Supersu 2.82 SR5 zip did good the root thing
- and a big headcache... Google play... I can't install any of them. I tried lot of them. OpenGapps mini, micro, pico... Every time when i try to set up my account, its just "checking info ", and nothing else, just force stop after a few minutes. I tried it after a clean install. I tried adter root. I tried immediately after omni zip + raw combination. None of them work for me...
- about battery life, i think its normal, but i used it withouth google apps... So not many sync was the background...
- wifi doesn't work, it's simple not turning on
Anyway, i like it, i think after some time, it will be good as Omni 7.1.2. Keep up the good work OmniTeam! And thanks for your homemade to!

Hey there,
Is wifi working now?
Regards, Chris

dhchris said:
Hey there,
Is wifi working now?
Regards, Chris
Click to expand...
Click to collapse
Hi!
On 11.04 the wifi doesn't turn on. Its not working. On the 11.08 I don't try it. BUT...
I've got a working gapps. I don't really know how to do that, but The steps was:
After wipe data, system, cache, etc then flashed Omnirom homemade zip, after that dd the raw image. Then before bootes up i flashed " A-GAPPS-arm64--8.0-01102017.zip ", then supersu latest SR5. After boot, the gapps setup FC. Then dirty flash homemade.zip after that another gapps, what was " open_gapps-arm64-8.0-nano-20171104.zip ", then came the supersu, and then went to reboot. Now a little more time was the boot than before. After its boot up normal i've got working google account setup, and orher google things. Why i do that now? Because until "A-Gapps" the google account setup just show "checking info" screen, and never goes on. After "A-gapps" its immadietly go to FC. Just the "a-gapps" dirty flash doeant help. The whole process again with "a-gapps" dont. Just that if i flashed second time an open nano version...
I hope its help if somebody got similar problem.

lba810701 said:
Hi!
On 11.04 the wifi doesn't turn on. Its not working. On the 11.08 I don't try it. BUT...
I've got a working gapps. I don't really know how to do that, but The steps was:
After wipe data, system, cache, etc then flashed Omnirom homemade zip, after that dd the raw image. Then before bootes up i flashed " A-GAPPS-arm64--8.0-01102017.zip ", then supersu latest SR5. After boot, the gapps setup FC. Then dirty flash homemade.zip after that another gapps, what was " open_gapps-arm64-8.0-nano-20171104.zip ", then came the supersu, and then went to reboot. Now a little more time was the boot than before. After its boot up normal i've got working google account setup, and orher google things. Why i do that now? Because until "A-Gapps" the google account setup just show "checking info" screen, and never goes on. After "A-gapps" its immadietly go to FC. Just the "a-gapps" dirty flash doeant help. The whole process again with "a-gapps" dont. Just that if i flashed second time an open nano version...
I hope its help if somebody got similar problem.
Click to expand...
Click to collapse
I installed open gapps pico and I didn't have any issues. Also I didn't install supersu, instead I installed Magisk Manager and I don't have any root issues.
Wifi doesn't work and Sony's people are working on it.
Here every one can see the situation for our phone https://developer.sonymobile.com/open-devices/current-platform-functionality/#8956