Database Develop

AOSP N (7.0) for Z5 DUAL(E6683)

AOSP 7.0 For Xperia Z5 DUAL (Abandoned currently)
Hello guys,
It takes a long time for Sony devs to add the support the dsds variant, but it's finally coming
Now I've built the AOSP 7.0 for Sony Xperia Z5 Dual.
Currently working:
*Dual Sim support
*GPS
*Bluetooth
*SMS
**Newly solved : SD card detection credits to @HaoZeke
Currently NOT working:
+Camera (Well, it's kinda work -- Sharp focus but inverted)
Current status: Broken
+Fingerprint(Sometimes doesn't work)
Supporting devices:
Currently tested on E6683, not sure about E6633.
Don't try it on other devices.
PLEASE PLEASE PLEASE back up you data ( including sd card) before flashing...
Boot.img
https://drive.google.com/file/d/0B_n...ew?usp=sharing
Credits to @HaoZeke
System.img
https://drive.google.com/open?id=0B5wyhen_cbdrTTRoc19OZW9HOWM
Userdata.img
https://drive.google.com/open?id=0B5wyhen_cbdrbW9GZGdMTmpVOWs
***UPDATE:
For recovery, download this and flash using fastboot. Then flash Gapps, and the device will be ready to use as daily driver.
(Credits to zacharias.maladroit)
http://forum.xda-developers.com/xperia-z5/development/twrp-3-0-2-cm-aosp-roms-t3373008
Procedure to get it working:
1. Unlock the bootloader
2. install adb and fastboot on your computer (Can be found easily on Google)
3. open the command windows
4, Type: fastboot -S 256M flash boot /replace with your own route/boot.img
5, Type: fastboot -S 256M flash system /replace with your own route/system.img
6, Type fastboot -S 256M flash userdata /replace with your own route/userdata.img
7, Type fastboot flash recovery /replace with your route/recovery3.0.2.img
8, Flash opengapps in the recovery
9, You're all set
****Make sure to do a full wipe before flashing the ROM.****
Please do not expect updates because I built the ROM only by exactly syncing the repo created by Sony dev. I'll update the ROM asap if there are any update in the official repo.
Sorry for bad English
Press the thanks button if you found it useful!
Credits: sonyxperiadev for all the effort on the ROM
@HaoZeke for making SD card detection work.

Great! I would definitely support this project! Keep up the goodwork!

Rom boots fine on E6633 but the sim cards don't work and camera doesn't even open.

mistercyko said:
Rom boots fine on E6633 but the sim cards don't work and camera doesn't even open.
Click to expand...
Click to collapse
For SIM Card I really don't have a clue.... It works well on my phone. I'm sorry that I can't help because I'm not a developer.
Camera can be opened by enabling the 23MP mode in settings -> extended settings -> disable the 8mp mode.

JerryLaiHMmmmmm said:
For SIM Card I really don't have a clue.... It works well on my phone. I'm sorry that I can't help because I'm not a developer.
Camera can be opened by enabling the 23MP mode in settings -> extended settings -> disable the 8mp mode.
Click to expand...
Click to collapse
You have E6633? and the sim card works?
Please tell me exactly the steps you sued to install it.

mistercyko said:
You have E6633? and the sim card works?
Please tell me exactly the steps you sued to install it.
Click to expand...
Click to collapse
I have a E6683, as stated in op.
The steps is full wipe-> install imgs by fastboot.

JerryLaiHMmmmmm said:
I have a E6683, as stated in op.
The steps is full wipe-> install imgs by fastboot.
Click to expand...
Click to collapse
Oh ok. Op said he wasnt sure about E6633 but it seems that sim support still doesn't work on it.
I have been dying to have aosp on my dual E6633 but all roms don't support dual sim e6633 .

JerryLaiHMmmmmm said:
Procedure to get it working:
1. Unlock the bootloader
2. install adb and fastboot on your computer (Can be found easily on Google)
3. open the command windows
4, Type: fastboot -S 256M flash boot /replace with your own route/boot.img
5, Type: fastboot -S 256M flash system /replace with your own route/system.img
6, Type fastboot -S 256M flash userdata /replace with your own route/userdata.img
7, Type fastboot flash recovery /replace with your route/recovery3.0.2.img
8, Flash opengapps in the recovery
9, You're all set
Click to expand...
Click to collapse
Just tried it on my E6683 DSDS
- did a clean format of all partitions
- flashed 4 imgs via fastboot
- booted nicely
- lost everything on my phone memory
- no SD card detected anywhere
- Camera does'nt even start
- SIM functions are OK

Thanks for the brilliant work... Have you perhaps asked one of the senior devs about the SD card thing...? That's the only thing keeping from jumping this as daily driver.....

HaoZeke said:
Thanks for the brilliant work... Have you perhaps asked one of the senior devs about the SD card thing...? That's the only thing keeping from jumping this as daily driver.....
Click to expand...
Click to collapse
Sorry everyone, but these days I'm really busy with my homework and tests... So I won't be able to update the rom that often.
But relax, I'll dig deeper into it later and I WON'T GIVE UP THIS ROM.

JerryLaiHMmmmmm said:
Sorry everyone, but these days I'm really busy with my homework and tests... So I won't be able to update the rom that often.
But relax, I'll dig deeper into it later and I WON'T GIVE UP THIS ROM.
Click to expand...
Click to collapse
Hey, I don't know if this is relevant but the SD card detection problem is because the precompiled kernel which is in the sony repos is built for the E6653 not E6683, which has it's kernel configuration set up here....
https://github.com/sonyxperiadev/device-sony-sumire/blob/master/aosp_e6683.mk

E6683 Kernel.
Hey I just compiled the kernel for the e6683 from source and updated the bootimage...
This fixes the SD Card issue...
Also, a word of warning; flashing userdata wipes the internal SD card as well....
https://drive.google.com/file/d/0B_nq_4gY-k85akpqTUJTR05Oc2M/view?usp=sharing

HaoZeke said:
Hey I just compiled the kernel for the e6683 from source and updated the bootimage...
This fixes the SD Card issue...
Also, a word of warning; flashing userdata wipes the internal SD card as well....
https://drive.google.com/file/d/0B_nq_4gY-k85akpqTUJTR05Oc2M/view?usp=sharing
Click to expand...
Click to collapse
Good work! Would you mind if I use this boot image as default in my OP?

JerryLaiHMmmmmm said:
Good work! Would you mind if I use this boot image as default in my OP?
Click to expand...
Click to collapse
Sure you can I'd be honored if you mention me there too

Thanks for the rom. Great work.
Both the sim cards work. Data Works. Wifi Works.
Camera opened the first time and was able to take photos. But never opens again.
I have rooted it. No problems there. Adaway does not work though. Cant update hosts file.
Most of the times the rom is butter smooth, but there is occasional stutter.
Bluetooth works. NFC works. Bluethooth audio works.
External SD card works. Thanks to @HaoZeke.

ganeshbiyer said:
Thanks for the rom. Great work.
Both the sim cards work. Data Works. Wifi Works.
Camera opened the first time and was able to take photos. But never opens again.
I have rooted it. No problems there. Adaway does not work though. Cant update hosts file.
Most of the times the rom is butter smooth, but there is occasional stutter.
Bluetooth works. NFC works. Bluethooth audio works.
External SD card works. Thanks to @HaoZeke.
Click to expand...
Click to collapse
The camera seems hit and miss. I read somewhere that the stock camera "jams" the device so don't use it. Usually and oddly, whatsapp's internal camera opens in a few tries...

Damn the camera! This is my daily driver.
Footej camera (front camera works)

is there any possibility of another update for this ROM in near future ???

chinmoy32 said:
is there any possibility of another update for this ROM in near future ???
Click to expand...
Click to collapse
Asking ETA is against the xda rule my friend.. Woww.. u got 12 thanks only for asking ETA ? :laugh:

Rajeev said:
Asking ETA is against the xda rule my friend.. Woww.. u got 12 thanks only for asking ETA ? :laugh:
Click to expand...
Click to collapse
welll................... to be honest I was not asking for ETA technically !! I was asking for yes or no type of answer , whether this is dead or alive !!!
as I am looking for nougat HAL to be more friendly to camera modifications and all.

LOCKED: How to Reset Pattern? (Urgent)

Hello,
My Device: Oneplus 3T
I have installed multirom on my mobile with Resurrection and MIUI installed ROMs. Although i insert the correct pattern, some how both the OS not accepting the pattern after reboot and my phone is locked . Please help me to unlock/reset the pattern.
Note: I have TWRP 3.0.3 (Multirom) installed in my device and the phone is rooted.

Amitshahc said:
Hello,
My Device: Oneplus 3T
I have installed multirom on my mobile with Resurrection and MIUI installed ROMs. Although i insert the correct pattern, some how both the OS not accepting the pattern after reboot and my phone is locked . Please help me to unlock/reset the pattern.
Note: I have TWRP 3.0.3 (Multirom) installed in my device and the phone is rooted.
Click to expand...
Click to collapse
Boot into TWRP and go to the file manager under advanced. From here cd to data/system/ and delete the 2 .key extension files along with the lockscreen.db files. This will remove your lockscreen from your primary rom. You can do the same with secondary. This is a known MultiROM bug and a quick search in the thread would have provided you with the answer.

cmbdom said:
Boot into TWRP and go to the file manager under advanced. From here cd to data/system/ and delete the 2 .key extension files along with the lockscreen.db files. This will remove your lockscreen from your primary rom. You can do the same with secondary. This is a known MultiROM bug and a quick search in the thread would have provided you with the answer.
Click to expand...
Click to collapse
Thanks for your reply, but i already found those solutions and tried too.
But still the Resurrection OS is locked. while the internal OS which points to MIUI is unlocked and not asking anything. should i reinstall the 2nd OS of Resurrection?
Now there are no .key files or lockscreen.db files in /data/system.

Amitshahc said:
Thanks for your reply, but i already found those solutions and tried too.
But still the Resurrection OS is locked. while the internal OS which points to MIUI is unlocked and not asking anything. should i reinstall the 2nd OS of Resurrection?
Now there are no .key files or lockscreen.db files in /data/system.
Click to expand...
Click to collapse
You now need to travel to your secondary rom's install location (ex. Internal Storage). I'd assume you installed it to the userdata partition so travel to sdcard/MultiROM/ then continue to data/system/. If it is not in this location then take a quick Google search for the partition you installed it to.

cmbdom said:
You now need to travel to your secondary rom's install location (ex. Internal Storage). I'd assume you installed it to the userdata partition so travel to sdcard/MultiROM/ then continue to data/system/. If it is not in this location then take a quick Google search for the partition you installed it to.
Click to expand...
Click to collapse
Thanks, this seems something would have worked if I didn't had deleted and reinstalled the OS. sorry I can't wait so reinstalled it. I will try to follow this next time if I face the same issue. thanks...

cmbdom said:
You now need to travel to your secondary rom's install location (ex. Internal Storage). I'd assume you installed it to the userdata partition so travel to sdcard/MultiROM/ then continue to data/system/. If it is not in this location then take a quick Google search for the partition you installed it to.
Click to expand...
Click to collapse
[Solved] :good:
Thanks, this one really worked for me.. the path was sdcard/multirom/roms and then data/system.

Amitshahc said:
[Solved] :good:
Thanks, this one really worked for me.. the path was sdcard/multirom/roms and then data/system.
Click to expand...
Click to collapse
This happens whenever you set a lockscreen pattern while using MultiROM on any of the installed ROMs.

[RECOVERY][T713] TWRP 3.3.0-0 Touch Recovery [OFFICIAL]

Team Win Recovery Project 3.x, or twrp3 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.
DOWNLOAD: https://dl.twrp.me/gts28vewifi
BUGS:
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY][T713] TWRP 3.3.0-0 Touch Recovery [OFFICIAL], ROM for the Samsung Galaxy Tab S2
Contributors
LuK1337, luca020400, Olivier
Source Code: https://github.com/TeamWin
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2017-01-27
Last Updated 2019-04-15

-snip-

LuK1337 said:
-snip-
Click to expand...
Click to collapse
Thanks. It's great to have a proper version of TWRP.

No love for 2015 versions on TWRP site

it works with T719, so thank you

deleted

It also works with the T813. Great to have a real recovery on this device.

Ever since TWRP 3.1.0-0 twrp can no longer read my encrypted data partition probably due to commit f628cbfc5e77a3a358c95ef7f1e47bbb1505b9d0 on the TeamWin github for the gts28vewifi (I can't post the direct link because my account is too new).
Is there any reason the encryption blobs were swapped out and how would I go about getting twrp to read my encrypted data partition again. I've already tried wiping everything, reflashing and reencrypting but it didn't help.

radiocarbon said:
Ever since TWRP 3.1.0-0 twrp can no longer read my encrypted data partition probably due to commit f628cbfc5e77a3a358c95ef7f1e47bbb1505b9d0 on the TeamWin github for the gts28vewifi (I can't post the direct link because my account is too new).
Is there any reason the encryption blobs were swapped out and how would I go about getting twrp to read my encrypted data partition again. I've already tried wiping everything, reflashing and reencrypting but it didn't help.
Click to expand...
Click to collapse
I am on it.

radiocarbon said:
Ever since TWRP 3.1.0-0 twrp can no longer read my encrypted data partition probably due to commit f628cbfc5e77a3a358c95ef7f1e47bbb1505b9d0 on the TeamWin github for the gts28vewifi (I can't post the direct link because my account is too new).
Is there any reason the encryption blobs were swapped out and how would I go about getting twrp to read my encrypted data partition again. I've already tried wiping everything, reflashing and reencrypting but it didn't help.
Click to expand...
Click to collapse
Actually, I think the issue with decryption is with qcom_common. The following commit is needed (which exists on the android-7.1 branch): https://github.com/TeamWin/android_...mmit/c4dab0d6d73f05b70091761e536b751dc9328f49

radiocarbon said:
Ever since TWRP 3.1.0-0 twrp can no longer read my encrypted data partition probably due to commit f628cbfc5e77a3a358c95ef7f1e47bbb1505b9d0 on the TeamWin github for the gts28vewifi (I can't post the direct link because my account is too new).
Is there any reason the encryption blobs were swapped out and how would I go about getting twrp to read my encrypted data partition again. I've already tried wiping everything, reflashing and reencrypting but it didn't help.
Click to expand...
Click to collapse
Please try latest ( 3.1.1-1 ) build.

LuK1337 said:
Please try latest ( 3.1.1-1 ) build.
Click to expand...
Click to collapse
It works now, thank you very much.

Hi, would this be compatible with gts210veltexx

Alpha1BA said:
Hi, would this be compatible with gts210veltexx
Click to expand...
Click to collapse
No, T813 recovery probably is.

Hello, think I need some help with setting up this particular tab... None of the recovery images listed on the official site (plus the unofficial one here) work properly. Any 3.1.0+ one would say "Failed to mount /data (invalid arguments)" and not show me my internal storage and data (shows /system and SD card alright though), and lower version ones would just boot to TWRP splash screen then reboot, without getting to the main menu. I'm running the latest Nougat update (T713XXU2BQD3) if that matters.

AndyYan said:
Hello, think I need some help with setting up this particular tab... None of the recovery images listed on the official site (plus the unofficial one here) work properly. Any 3.1.0+ one would say "Failed to mount /data (invalid arguments)" and not show me my internal storage and data (shows /system and SD card alright though), and lower version ones would just boot to TWRP splash screen then reboot, without getting to the main menu. I'm running the latest Nougat update (T713XXU2BQD3) if that matters.
Click to expand...
Click to collapse
You can't mount data if you come from stock. It is encrypted and twrp doesn't support it so you got to format it to ext4 in order to mount it.

LuK1337 said:
You can't mount data if you come from stock. It is encrypted and twrp doesn't support it so you got to format it to ext4 in order to mount it.
Click to expand...
Click to collapse
Ugh. It had been a while since I touched any recent Samsung devices, didn't know I had to do extra work around encryption. Used a lot of other devices but TWRP handles all of them with a default key, that's why I'm quite baffled why it doesn't here. Thanks for the quick save though.

AndyYan said:
Ugh. It had been a while since I touched any recent Samsung devices, didn't know I had to do extra work around encryption. Used a lot of other devices but TWRP handles all of them with a default key, that's why I'm quite baffled why it doesn't here. Thanks for the quick save though.
Click to expand...
Click to collapse
Samsung uses different encryption and we only support AOSP one.

LuK1337 said:
Samsung uses different encryption and we only support AOSP one.
Click to expand...
Click to collapse
Alrighty, can understand. Can there be a notice somewhere up this thread or the TWRP device landing page about it?

Is LineageOS 14.1 the only rom for this t713wifi. I cant find any stock rooted.

[TWRP] Weird file names and cannot find zip

When I flashed TWRP and try to flash Magisk, all folders and files under /sdcard or /data/media/0 are random characters like lh1masdNxhSj. When I copy a zip to internal storage, TWRP cannot find the zip.
So I tried to sideload, and when I am inside TWRP and do adb devices, it is an empty list.
Now I have no way to flash zip and root. Please help

Use unofficial TWRP

fishersfish said:
Use unofficial TWRP
Click to expand...
Click to collapse
Really? Ok will try

popoxee said:
Really? Ok will try
Click to expand...
Click to collapse
Also make sure you dont have a lockscreen set. Otherwise it will fail to decrypt too.

reeved said:
Also make sure you dont have a lockscreen set. Otherwise it will fail to decrypt too.
Click to expand...
Click to collapse
It works now! Surprisingly the official one didn't work but the unofficial one works...
Thanks a lot

[OFFICIAL] [REBASED] [EMUI 5] TWRP 3.4.0 for P9 Lite 2016

What is TWRP?
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system which are functions often unsupported by stock recovery images. It is, therefore, often installed when flashing, installing, or rooting Android devices.
WARNING
Code:
* We are 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 us for messing up your device, we will laugh at you.
Bugs:
On official build, MTP Name and Serial Number is broken (fixes already merged to src, working on hotfix build and rebase)
You tell me here or in Telegram Group
Download:
Official
Hotfix Build (reupload)
Rebase
Note: MTP Name on Rebase Build is set to "P9 Lite 2016" on all models. Don't worry, it's not a bug. I have to add libinit later.
Sources:
Device Tree (Official + Hotfix)
Kernel Source (Official)
Device Tree (Rebase)
Kernel Source (Rebase)
My other Works for P9 Lite:
Click me
Telegram Group for P9 Lite development:
Click me

sir

I have installed your fixed version and I can't mount internal memory to flash downloaded zip files

lionen said:
I have installed your fixed version and I can't mount internal memory to flash downloaded zip files
Click to expand...
Click to collapse
are you on emui?

GG2501YT said:
are you on emui?
Click to expand...
Click to collapse
Yes, I'm on stock b371

lionen said:
Yes, I'm on stock b371
Click to expand...
Click to collapse
try to format internal storage to ext4

GG2501YT said:
try to format internal storage to ext4
Click to expand...
Click to collapse
Don't write nonsense please.
P.S.: Data cannot be decrypted in TWRP 3.4.0-0.

-Alf- said:
Don't write nonsense please.
P.S.: Data cannot be decrypted in TWRP 3.4.0-0.
Click to expand...
Click to collapse
That ain't nonsense, since this worked for me just fine.
I formatted data in ext4 and everything worked and still works

TheTimeLord32 said:
That ain't nonsense, since this worked for me just fine.
I formatted data in ext4 and everything worked and still works
Click to expand...
Click to collapse
"internal storage" and "data" are two different things.

Works fine here! Good job dev

-Alf- said:
"internal storage" and "data" are two different things.
Click to expand...
Click to collapse
Yes but i did that on another huawei device and it worked there too.

GG2501YT said:
Yes but i did that on another huawei device and it worked there too.
Click to expand...
Click to collapse
In TWRP you can format data , wipe data, wipe internal storage, but it's impossible to FORMAT internal storage, I quote: " try to format internal storage to ext4" . Comprende? Peace!

GG2501YT said:
Rebase
Note: MTP Name on Rebase Build is set to "P9 Lite 2016" on all models. Don't worry, it's not a bug. I have to add libinit later.
Sources:
Device Tree (Rebase)
Kernel Source (Rebase)
My other Works for P9 Lite:
Click me
Telegram Group for P9 Lite development:
Click me
Update: I have rebased my TWRP for VNS. Would be nice if you can test it on all hi6250 devices supported. Report your bugs here or on my Telegram Group
Click to expand...
Click to collapse