Database Develop

***Informative Threads*** - Read before clicking "New Thread"

***Informative Threads***​Post your question / issue / success story / etc. in the appropriate threads instead of starting a new thread!
Do NOT post a new thread to ask a QUESTION!!!
If your post has a question mark in it, you most likely need to post your thread in the Q&A Section
​
[Build Indexes] - Don't ask which build is best -- choose for yourself based on the features you desire!
androidspin.com
SimonNWalker & a group of Android Community members are maintaining a site which showcases the feature sets of the latest and greatest android builds ("roms" if you prefer). Check here to see "which is best" and try them out for yourself. The site is also ripe with news about Android development and more. XDA Thread
androidrevisions.com
Sir Savant is maintaining another build database. This web app allows for sorting / filtering / etc - XDA Thread
Google Docs Build Spreadsheet - View and edit build info - Google Docs Build Spreadsheet
[Guides/Tutorials/Info]
HTC Dream overview and useful information - Wiki article
Highly recommended for beginners.
In the beginning... There was ROOT
Lots of good definitions, history, and an excellent overview of most things going on here.
SPLs for DREA100 & DREA110 (Orig, Eng, Hard)
Contains information and downloads for SPLs (Secondary Program Loader) for the Dream. A modded SPL is instrumental in restoring from backup, preventing a brick, applying builds designed for foreign markets, etc.
Nandroid v2.0 - Full NAND backup and restore tool
In-depth discussion of your best friend whilst modding your android device. A good Nandroid backup regimen will pay dividends to keep you up and running.
Basic adb/root commands for noobs
Using ADB and terminal commands for your Android phone.
Surviving a Data Wipe / Update (Reduces Force Closes, too!)
Save (most of) your data while switching between builds (wipes are not your enemy!!)
Cyanogen's recovery partition
Amon_Ra's Recovery Partition
Modded recovery and boot images
SDSPLIT repartition your SDcard on phone (w/o a PC) - NOW handles > 2G FAT!!!
An easy way to re-partition your SD card without a PC.
LucidREM's Latest JF mod scripts
The swiss army knife of build customization
Auto-lucid script by tehseano
Let's fix that SPL Pay attention too post 3
Report in here if your phone is unresponsive after applying the 1.33.2005 SPL released by Haykuro. If you can get into Recovery or the SPL bootloader screen (three skateboarding androids), this is not you.
ROM guide for HTC Dream
T-Mobile G1 User Guides/Manuals
HTC Dream Wiki
"Brick" Thread or Technical Think Tank for Bricked G1's
If your phone is stuck at your splash screen (most likely a big white "G1")...if you you think something is broken...if you otherwise think you have a brick, post here instead of starting a new thread and any online members will do everything they can to help you out. (Reading as much as possible of these threads before posting will give you lots of insight as well!!)
Benchmark your build (apps thread)
[HOW TO]
STOCK-2-CYANOGEN / Root, Recovery, Radio, Rom / Partition SD / FAQ
How To Partition SD Card With Ubuntu For Dummies
Partition sdcard w/parted,goto ext3/4 & install rom from adb. no liveCD req'd
UNROOT, get phone to STOCK firmware
Reverting back to stock firmware.
New and improved Apps to SD(more stable, more powerful, etc)
The latest tutorial on how to get apps to SD.
Convert and mount ext2 sd partition ( /system/sd ) to ext3
Tools and instructions to add journaling to your ext sd card partition (apps2sd, etc). trust me, journaling is a good thing!
Register the G1 without a sim or data plan
Increase Max Volume -- Automated, no reboot needed
ADB for Dummies Supported Operating Systems Drivers and SDK
Get Home Auto Rotate on JFv1.51
Unpack, Edit, and Repack Boot Images
Create and edit "recovery" and "boot" .img files -- this thread is not for splash images.
Custom SPLASH Image
Replace that G1 splash logo that displays when your device turns on.
Alternative way to creating a SPLASH image
View Man Pages in terminal / adb shell
Mount SD card in recovery via adb
Use ash as your login shell
[MOD]user configurable userinit.sh V0.1.4.1 for CM
config file for setting up compcache, tweaks, etc. at boot
[How to] mount SD card in recovery.
Ported Hero Programs:
HTC Camera
HTC Music
***Developer Links***
Developers - Instead of maintaining a list of builds, I've changed this list to include links to your publications (blog, twitter, main release thread, etc.) let me know when / if you want these modified or if any should be added -- I'm sure I've missed some of you!
​
JesusFreke's Blog
Haykuro's Blog
TheDudeOfLife's google code page
Cyanogen's Twitter
TwistedUmbrella's Twitter
justanothercrowd's twitter
Stericson's twitter
For links / info on particular builds, check out the AndroidSpin, Android Revisions, or the Google Docs Build Spreadsheet
This index will be updated as needed.
Please keep comments on topic!

-Thread Stuck-
Other stickies un-stuck.
Please do not post in this thread unless you have a suggestion on how to improve it. Off topic and dealt with requests will be deleted without warning.​
Oh, and thanks alapapa.
Enjoy
Dave

something on how to install, or update the radio would be nice.. i dont see anything, though im a noob, and it might be there and i just dont understand lol. sorry if its there already. im off to search!

Many of these links are 404 or no longer applicable.
This post needs a serious overhaul.

pretty much all of the links are 404's

[REF]Everything you wanted to know about the streak (WIP)

WARNING ABOUT NVFLASH: Do not flash any nvflash payloads that contain a p23.img or p24.img as these contain your device unique data. Flashing someone elses p23 or 24 will change your Service tag, MAC addresses and IMEI. Intentionally changing your IMEI is ILLEGAL in many countries.
---------------------------------------------------------------------------------------------------------
This thread will consolidate all the guides and common downloads that are used for the streak.
Suggestions on changes or additions will definitely be welcome to it.
Forum Searching | Posting | The Basics:
(Make sure you've read them before starting a new thread)
Forum Rules
Forum Search
Google Forum Search
XDA Mantra
Semi-Official XDA Links:
Dell Streak Wiki Page
Wiki Flashing Guide
List of stock ROMs
Custom Rom and Recovery List
Other Guides:
Stock HC 506/507 installation instructions
[Guide]Taking apart the Streak 7
Commonly downloaded tools:
ClockWork Mod - Custom recovery
Superuser7.zip - Rooting Method
Fastboot/ADB utils + drivers for Streak 5/7 and Venue
nvflash.zip base package
APX mode drivers
Other Downloads:
Front button disabler mod
Points of interest for themers/rom makers:
Restoring your device specific data
List of apps safe to remove from stock roms

----Reserved----

Pretty sure if you flash p22.img it wipes your external SD card as well.

It does, but that's slightly beyond the scope as it's 'merely' userdata and hopefully back up else where.
Device data is completely unique to a device

Just saying, some people might not want their SD card wiped where they have their titanium backup

thanks.........

Navigator
The Streak 7 makes a very fine navigation device for your car. I use sygic and have built a wooden holder for the streak.

G925v Analysis, Rooting, Dev Files & Implications

So it happened day before yesterday, 8-22-17 @ ~5:50 PM, my Verizon S6 Edge (G925VZKE [64GB]) bricked out. No LED Light, nothing on Screen, nothing as if actually Hard Bricked. No booting, No download Mode, nothing. But it's not fully hard bricked actually. When I plug the device into my PC, Windows will either pop and say the device malfunctioned or it will read as "Exynos7420". I'm not quite sure what to do about it at the moment, I've read [a little] about what to do with phones in this mode using a "USB_Down_Load_32bit"/Multidownloader. I believe it to be stuck in a Diagnostic Mode I'm not versed in. This all happened while I was in the ADB Root Shell (su:s0) while the device was powered off and charging.
I am making this thread here for any devs you would want to use the knowledge and files here, to take the project further. As I cannot currently use my device at all. And I won't be getting a replacement S6 Edge for at least a month, maybe two. I love the S6, and will still choose it over most devices. I've been dedicated to researching and posting about the Samsung Exynos7420 Hardware since September 2016. That was when I came up with the plan for The Greyhat Root Project. You may recall my other thread once in the Original Development Forum & now in General. If you search "Greyhat Root" in google. My thread will be the first result. It gained a lot of traction, very very quickly. But is now dead, and the mods probably hate me for making a new thread. But I'm not trying to put new news out there this time.
It focused on how to use Kali Linux and Metasploit. It also focused on the articles at the time that was new exploit & malware research, that boasted of the possibilities we've now come to know as the Vault7 leaks. There's probably a reason I was a victim of the malware myself and I took down most of the posts. Most of the good file and resources I posted to that thread were either flagged by end users or removed by google. The real treasure of that thread is lost to the internet now, as that was the only backup I had of some of the critical files needed for the process. If you actually look through my individual posts all over, you will find some juicy tidbits of knowledge spread around this site that I've not compiled into one. A lot of it is still over my head as it was then, and partly why I took it down then. But I've been chipping away at that knowledge base everday for 10 months going on a year now. It's possible to root this device if One can take the knowledge of how to leverage the news worthy exploits from the past 2 years into a single repo/application. "Android-InsecureBankv2" is one example of such a platform. But as a teaching platform, it is not configured to provide a SuperSu Root Solution out of the box. It would still require modification of someone else's codebase w/Learning Curve.
No I have not managed to find a way to unlock the bootloader because I do not have a copy of IDA Pro or the Hex Rays Decompiler, and if I did, I still wouldn't know to use them fully. But I have managed to find quite a number of very possible attack vectors, if I can get some serious developers to take my sentiments seriously. I proved that when the posts about dirtycow were largely ignored due to device interest, and then @droidvoider helped make some of my ideas possible with the "Greyhat Root Console" he made. Realistically at this point I only wish I were an Assembler. I'm only one guy trying to poke at a Hardware/Software Package created by multiple departments of people in a conglomerate corporation. I only bring people together. I do know that in order to disassemble the Exynos7420 sboot, you're going to need to understand U-Boot on Arm64. A Uboot version dating back to either January 2016 or August 2015. I say those two dates because, The 4BOG7 files on my device date to August 2015, the 4AOJ1 files, to January 2016. Project Zero (who does a lot of tests on the G925v btw), posted in February 2017 about they found a way to bypass the KASLR feature of the stock kernel. A Kernel I do believe we can still flash to the device. It didn't gain much attention I don't think at the time because it was only one piece to the puzzle. That exploit wasn't patched until January. I know it sounds bad when I say it like this but, what this device truly needs is a friendly Botnet-C&C-Style rootkit that has it's client and server controlled by a User-Controlled, SuperSu-Style management application. Yes, it would be a rootkit you would never want to have someone else in control of. But if SuperSu were controlled by someone else other than the end user at the time, it would be just as bad. It's just a different approach to a yet unpublished methodology.
*
** The Device I refer to is currently flashed with:
******
** Full 4 File Firmware: COMBINATION_VZW_FA50_G925VVRU4AOJ1_VZW4AOJ1_CL5133452_QB6486176_REV02_user_mid_noship.tar
** BL: G925VVRU4AOJ1 ENG sboot.bin
** AP Kernel: G925VVRU4BOG7 ENG Kernel
** TrustZone Type: t-base-tui (Filenames suggesting Mobicore present as well)
******
Trying to enter Recovery Mode with the Combo firmware, in my experience, typically sends the device into a Panic and boots into "Upload Mode" if it does not simply reboot. The combination firmware does not supply a recovery.img that I've found. And inorder to recover the ENG Combination Recovery, you would have to disassemble the OJ1 ENG sboot.bin in IDA Pro and pull it out.
During the initial boot the device will enter its own recovery mode for a moment while it does its erasing stage. I used "nand erase all, re-partition, F.Reset Time, Phone Bootloader Update options in ODIN. During this breif moment with the "Erasing..." text on-screen, the phone is available in ADB Devices and shows up in recovery mode. Meaning ADB Shell should be accesible in recovery. If that's possible that means the device keystore should be accessible as well. The Recovery images tend to be bigger because the signatures are stored in the recovery from what I've read. Can't dirtycow patch anything it can see if your shell can't change it?
Using those files, I have full su authority anytime I am in ADB Shell, the shell runs within the "su:s0" context, and not the "shell:s0" context. Any and All changes are possible through the shell. Writing a new partition Table to '/dev/block/platform/15570000.ufs/sdb' using the "partx" tool, is probably what broke my phone. So in theory installing SuperSu in System Mode should work much the same as it did on G95x S8/Plus I'm gathering. @dragoodwael was correct in supposing "sdb" to be the bootloader overall, as I do now too. Once the reboot command was issued, I lost the ability to do anything at all. All thats possible now, is to find a tool that will communicate with the driver my PC's Device Manager loaded for my phone.
Every boot.img I've unpacked using Android Image Kitchen specified that a signature of "SEAndroid Type was found". BUT, the only boot.img/Kernel that did not specify that it was an "SEAndroid Type" while being unpacked, is the Stock boot.img from the 4AOJ1 Combination Firmware. Out of the 7 boot images I've unpacked, AIK determined the OJ1 Combination boot.img did NOT have an SEAndroid Signature on it.
boot.imgs I've unpacked:
1. N920A - PB2 Eng boot.img
2. N920A - FA51 Combi - PH1 boot.img
3. N920A - FA51 Combi - PL1 boot.img
4. G925V - FA50 Combi - OG2 boot.img
5. G925V - FA50 Combi - OJ1 boot.img
6. G925V - OG7 Stock boot.img
7. G925V - OG7 ENG boot.img
I'm not quite sure what that means yet, but I do know that the zip file I have that contains the 4AOJ1 factory Binary is not a tar.md5 like usual, it is just a normal .tar. What I'd LOVE to know is, can the 4AOJ1 stock boot.img be unpacked, then repacked, and retain its flashable characteristic. Because AIK does not register a standard signature. Does that mean the Oj1 boot.img uses a different mechanism for signature verification than a standard user binary, or is it simply signed with publicly available signing keys? It's a good question, what is different about its signature compared to other stock signatures. Even if we don't understand the signatures fully.
I'm also aware of the fact, that the Combination firmware doesn't actually contain a recovery.img to flash. Probably why the Device goes into Upload Mode and Panics when trying to boot recovery after using "nand flash all" and/or "re-partition" in ODIN. But if there were a Recovery Image for the OJ1 firmware, I imagine it would not have an SEAndroid signature on it as well. So there must be something to that.
I wonder what would happen if you tried to flash the OJ1 boot.img to the recovery partition as recovery.img like in the "EasyRecowvery" project, while using the full factory binary.
Is it possible that the newer "ustar" tar format used by Samsung in ODIN packages, could be using the custom fields available in a ustar header block to hold at least part of the signing mechanism? I believe so. And I say it because on my Device, it runs the Odin3 Engine (v1.1203), which looks an aweful lot like ODIN v1.12.3. Besides the naming conventions used there, ODIN expects to send/receive images within tar archives. Specifically USTAR format tar archives. So if the ODIN Engine on the phone is anything like the PC Client application, it expects USTAR format Tar archives as well. If it expects to read in a USTAR Header block, there are custom fields possible in known locations of the official tar files. Which when parsed correctly, should lead to finding the extra data after the payload 7-Zip refers to when the tar.md5 files are extracted. I'm of the mind the "Star" utility and not the the "Tar" utility is what we should be using to create and modify ODIN firmware the way our OEM's do. That is hypothesis on my part yes, but I don't think I'm very far off base.
Here is a man page on the "ustar" utility I found interesting and extremely in-depth: ustar(1) - unique standard tape archiver - Linux man page
If you want to see a list of files involved in all of this research, please refer to this folder here: https://drive.google.com/open?id=0B_EcHdXbjhT_dDRneE56WUg3Mlk
It contains all the files I've mentioned except for the OJ1 Firmware itself. This is all I'm posting for today, it's a sad day indeed. But I have to gather the bookmarks again to post the links to articles.

Help with flashing custom rom (Moto G6)

Hi
Firstly, thank you in advance for any help you can give me. I'm completely new to this so apologies in advance for my clumsy terminology and probably lack of useful detail - obviously v happy to provide any other details that will help. I do appreciate you are all volunteers - I moved from Windows to Ubuntu a few years ago and really appreciated the community support which made it possible so I am well aware of how dedicated you all are - thank you in advance.
I've an old Moto G6 (Xt1925-5). I thought I'd try rooting it and then installing a custom rom to ensure I can update security etc.
I won't bore you with all the details of why - I don't actually need to succeed but I hate the fact that a functional phone is electronic junk after 2-3 years just because it won't update; so I thought I'd try with my old phone that I don't need to see how easy this is to do (if it is I'll move over to Android for my main phone - I reluctantly currently use an iPhone - for me the selling-your-sole-to-Apple is outweighed by the several years of useability such that I buy my iPhones 2nd hand and still get several years of secure phone use.
I did manage to install twrp, root it and then wiped the original OS in order to flash a new rom. It's OEM unlocked via code from Motorola.
The problem I now face is that whatever I try to flash gives me error 255 in twrp. I've tried many different roms mostly downloaded via links on this site - eg lineage 17 and 18, crDroid v7 (android 11), Pixelexperiance.
twrp is version 3.6.2_9-0. My PC is running Ubuntu 22.04LTS. The phone previously ran Android 9 as an upgrade from the OEM 8.
I'm attempting to do this by (1) downloading the .zip; (2) transferring over to the sd card using adb push via USB from my laptop; (3) install via twrp.
The file seems to go over to the sd card and twrp shows it and tries to install, then I get the error (seems to be 255 every time). I've also tried sending the .zip to /tmp and /sdcard - neither work: error 255 every time. If I check 'zip signature verification' most of the ROMs pass (one or two fail) but still gives error 255 when trying to install.
The text is 'Updating partition details ... done; Formatting Cache using make_ext4fs ... ; Updating partition details ... done; Wiping Cache & Dalvik ... -- Dalvik Cache Directories Wipe Complete!; Updating partition details ... done!; Installing zip file '/sdcard/lineage18...'; Unmounting system ...; Updater process ended with ERROR: 255 Error installing zip file '/sdcard/lijneage-18...'; Updating partition details... ... done
As I get the same error with multiple different OSs I suspect I've made a simple error somewhere but don't know where to start to find it.
As an aside - I don't know if this is normal or completely unrelated - the .zip files I move over seem to disappear from the phone sometimes - often if I reboot, but I can't reliably reproduce the disappearance - wiping cache etc. doesn't remove the files, rebooting sometimes seems to but not every time.
I don't really mind what OS I end up with - happy with any OS that is secure; but I suspect I've missed something really simple to give the the same error with every attempt. As I said at the beginning, this is mostly an experiment (and would be nice to have a backup phone!) so the actual OS I end up with is much less important than whether I can do it or not.
Any help greatly appreciated - thank you!

doctorwill said:
Any help greatly appreciated - thank you!
Click to expand...
Click to collapse
Hello and good morning, @doctorwill
Welcome to XDA! I hope you'll always find and get the support you require.
However. prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved the thread to
Moto G6 Questions & Answers
Ask your questions about the Moto G6 and get answers from the community! Please be as specific as possible when posting.
forum.xda-developers.com
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator

[COLLECTION] Source Codes, Archived URLs, & More! [X00H/ZC520KL] [X00I/ZC554KL]

Hello all!
For a couple of days i've been researching useful resources to revive
development for this pretty cool device, so i had lifted up my sleeves and got
myself to work on gathering, interestingly, tons of links that could be useful
for whoever still owns an X00HD or X00ID in 2022.
Since i'm someone who's totally inexpert at developing in general (so, sadly
really couldn't contribute much to the technical aspect on reviving these
devices' active development), i'm here to share the fruits of my research in
order to be of help for any developer on who wants to take back development
for such a neat device.
--------------------------
X00HD - ZC520KL​General Resources:
The following link basically contains everything someone could need, more or less- a couple of source codes, official stock ROMs, and etc. offered by the Asus company
- ZC520KL on Asus Support
Archive Links:
- Lineage OS 18.1 [Flashable ZIP file]
Source Codes - Device Trees:
- Stock Oreo ROM
- Stock Pie ROM
- TWRP for X00HD
- Lineage OS 16.0 for X00HD
- Lineage OS 18.0 for X00HD
- Lineage OS 18.1 for X00HD
--------------------------
X00ID - ZC554KL​General Resources:
- ZC554KL on Asus Support
Archive Links:
- LineageOS Recovery [flashable IMG/Image file]
Source Code - Device Tree:
- Stock Oreo ROM
- Lineage 18.0 for X00ID
- Lineage 18.1 for X00ID
---------------------------
Miscellaneous​This is where i cram in another couple of links i've found throughout my research. The following even include stock ROM & Custom ROM source codes for the models: X00P, X00L, and X00R
- asus-msm8937 on GitHub (abandoned by the author)
-- asus-msm8397-devs on GitHub (successor of the above, currently inactive)
--- Their own site
- Resources at "files.sebaubuntu.dev"
- "files.sebaubuntu.dev" captures on Wayback Machine
----------------------------
Credits (because without these people's work i could had never discovered such a plethora of resources):
The Asus Team
The Archive Team
SebaUbuntu
althafvly
JarlPenguin
RazaDroid
syahril9444
runnerscl
Every single contributor on GH who mantained the source codes!

Important Note!​If you don't know how to unlock your device's bootloader and guides are outdated around here (and also, if you don't have a laptop/pc on your hands at all):
you can always use a secondary device that you had previously rooted for the job!
Which tools should you need?​
An OTG cable (usually your Asus device should come bundled with one);
A charging cable;
Your X00H/X00I device;
A secondary rooted device (must have Android 3.1 minimum and OTG support);
The following should have ADB & Fastboot Tools installed;
How to check if my device has OTG support?​This one can be solved in 2 ways:
The app way or the traditional way
If you want to save a bunch of time testing with cables, the app way is the simplest of the bunch. Just get installed on your rooted device the app CPU Info
After installed, just open it and follow these instructions: swipe until you reach the "HARDWARE" tab > scroll on the bottom of the page > check the USB title > check OTG
If you see "Yes": congratz, you can mod/unlock your Asus phone- if you see a "No", you can't do anything about it (unless you have another rooted device around your device stash, then you could retry the procedure with that)
The traditional way, on the other hand, you need a spare USB stick
Once connected the OTG cable to the device, cram in the USB on the slot. If it can scan it and a notification pops up for exploring the USB's contents: hooray, your device has OTG support!
How to unlock your device​DISCLAIMER:​You should unlock Developer Tools and enable USB Debugging for this procedure firsthand, else you can't proceed unlocking your own device correctly!​This one's easy peasy. Just follow my steps!
Turn off your Asus device;
After turned off completely, press the following buttons together: Power + Vol. Down;
The following should boot in Fastboot mode;
Leave your Asus in one spot and take your secondary device;
Open the ADB & Fastboot Tools app;
If your root manager gives you a warning, just tap "Continue" or "Yes";
Tap on "Start server" and the ADB daemon should start in no time;
Now, connect your Asus device with the charging cable;
Attach the other end (the USB end) to the OTG slot connected to your secondary device;
Tap on the upper right corner of the Fastboot app > tap on "Fastboot";
You should see a menu with tons of buttons;
If all of the buttons are greyed out, even after refreshed- then disconnect and reconnect your Asus device and refresh until the buttons are visible;
Tap on "Device Info";
The app will spit out tons of info about your device, even your device's secret code for unlocking it (which should be exactly after a line that goes secret-key-opt- in this case, long press where the string is and copy);
Type into the bar at the bottom oem get_unlock_key and then paste the string you've copied earlier;
Tap "Execute";
Congratulations, your Asus phone is finally unlocked!
Have a good day and happy modding!

I posted in the other thread that you can find all the files here:
Files

miya0405 said:
I posted in the other thread that you can find all the files here:
Files
Click to expand...
Click to collapse
Thanks for the help!
Will probably make a post in the near future on how to get LineageOS installed on both models with an all-in-one method, since on my end it was rather tricky to perform.