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

How does the Fire boot, and why can't the bootloader be unlocked ?

Hi, having flashed a couple of fires I was curious to understand why we can't unlock the bootloader by copying one from an early (pre-5.0.1) image. Perhaps someone can critique this and fill in the gaps to help me learn?
I understand the general idea that an ARM SoC starts after power or reset by executing from adress zero in memory which must therefore be some non-volatile memory (ROM, but possibly something flashable). The general way it goes is that address zero contains a jump instruction to the entry point of some code that we call the "Boot ROM", all of which is in that non-volatile memory just mentioned.
The boot ROM has just enough capability to initialise RAM and load a secondary bootloader (SBL) into it from some other non-volatile storage such as flash memory (is this the UBOOT partition on the internal flash drive?). The SBL is what we know as the bootloader that responds to the volume-down key and can boot the system (kernel and ramdisk in 'boot' partition) or recovery (kernel and ramdisk in 'recovery' partition), or it can establish itself as a fastboot server.
This left me wondering why we cannot simply replace the SBL image with one from a pre 5.0.1 image that supports unlocking. I don't understand how downgrading can brick the device.
I don't understand the detail and haven't been able to find anything concrete to explain it. If there is, perhaps a link to it might help me. Or if someone can be kind enough to explain it ?
I was thinking that the inability to replace the SBL may be because boot ROM performs verification of the SBL to ensure that it is legit before executing it. I don't know if it does but I read somewhere that the SBL image contains a 40-byte header for this purpose and that the boot ROM contains a verification (public?) key.
I presume the boot ROM is in some flash memory that is inaccessible from the outside and I thought that it could not be modified which would mean that all the SBL versions would need to have been signed by the same key. But I think perhaps the boot rom can be modified and the key contained therein can be changed when upgrading. I am guessing - I'd like to know how this works...
anyway, enough rambling

ogpog said:
Sorry just realised I was in the wrong forum and I can't see a delete option. Would a mod kindly move this to the "Fire Q&A, Help & Troubleshooting" for me pls.
Click to expand...
Click to collapse
Hopefully you found the appreciate threads (two) which address most of your questions. As for the OP you can modify your own posts in XDA; just replace the existing content with a few words (eg: "posted in error...deleted) and resave.

Davey126 said:
Hopefully you found the appreciate threads (two) which address most of your questions. As for the OP you can modify your own posts in XDA; just replace the existing content with a few words (eg: "posted in error...deleted) and resave.
Click to expand...
Click to collapse
I wasn't able to find them, can you point me at them, then I'll mark this as deleted... I did spend ages over a couple of days trying to find the answers.

ogpog said:
I wasn't able to find them, can you point me at them, then I'll mark this as deleted... I did spend ages over a couple of days trying to find the answers.
Click to expand...
Click to collapse
Within these threads you'll find contributors knowledgeable in the subject matter.
http://forum.xda-developers.com/amazon-fire/development/bootloader-unlock-ideas-t3289721
http://forum.xda-developers.com/amazon-fire/development/unbrick-fire-7-5th-gen-downgrade-t3388747

Thanks @Davey126, I had found the first of those posts but not the second one, which I've just had a good read of...

[CLOSED: REPLACED] [HELP NEEDED] Running a full custom ROM using the AVD tool of Andr

Hi everyone,
Today I'd like to dust an old subject that was quite discussed: emulating a custom Android ROM.
There are in threads arround here or in some Stack Overflow subjects (for instance) peoples talking about this, providing ideas or even complete tutorials.
These tutorials show how to use the SDK tools to create an Android Virtual Device to run the desired ROM.
But all these informations are purely deprecated and can't be applied exactly for new touch phones (higher than Jellybean you can't do that!)
Didn't realizing it yet and wanting to try it out I personnally downloaded the latest Android Studio software with the basic SDK tools.
I tried to run commands specified in the tutorials to test some things out (like creating an avd) and actually creating an avd this way is purely deprecated. Well.
 What a good start.
So instead I used the avd tool of the Studio software and I successfully created one.
Got into the C:\Users\%USERNAME%\.android\avd\avdname.avd folder to check components of the avd. I even read .2cow things files to know the location of the missing components (like system.img)
So I am almost done. I prepared my .img files to replace avd img basic components to test my emulated firmware out. But...
I have no idea where to start!!
I am missing some img files that would be necessary to run the avd correctly, like the kernel.img or userdata thing...
I just don't know what to replace or not, how to obtain necessary files without breaking something, I need help...
Here is finally the question of the subject:
Can somebody post out a complete updated tutorial on how to emulate a full custom rom using the AVD tool provided by Android Studio, please? (If possible of course)
This would be really nice and pretty useful for ROM development. I'm still experiencing things, trying to modify the close-to-my-devive avd I generated but this is just messing arround with things, I am pretty inexperienced so I don't think I could help...

Ok, no contribution as expected...
Fortunately I started reasearches despite the fact that I'm not a dev so I have a really really little idea of what I'm doing...
So here are what my researches led to (report with my memory, I will re-edit my post soon to add what I missed) :
Note: I used my SM-G361F pre-rooted ROM to test emulation.
==========*#1*==========
Operations:
•Created a close-to-device AVD (Same API Level etc.)
•Found out AVD dependencies folders: [C:\Users\%USERNAME%\.android \avd\x86 (I guess?)\(devicemodel).avd then another location containing kernel, system.img etc. thanks to .qcow2 files in the previously presented folder ("link" were in.)
•Made a backup of these folders **obvious**
•Edited some configurations (config.ini etc.) to make the final emulated system as close to the real device as possible to avoid incoherences
•Replaced some components of the AVD (build.prop, cache.img, userdata-qemu.img, etc.)
•Replaced the system image in the second folder
•After an hard struggle to get boot.img file of my device, decompiled it to get the ramdisk.img and kernel.img I used to replace kernel-qemu
Test:
•Starting the AVD from Android Studio
=> Outputs option "repair device"
•Attempted a repair: selected... My device SM-G361F to repair.
(=> Weird...)
•Repair seemed to work well according to the fact I could run the AVD
•Statut of the AVD: Black screen. Using power button and all doesn't make anything working: the AVD doesn't react.
=> Quiting made the emulator crash
Initial reason: see troubleshooting section
Result: FAIL
Troubleshooting:
•I shouldn't had to replace kernel-qemu by the stock extracted kernel: it has nothing to do with the actual system because it isn't purely system but device related. Will fix that next time
•ramdisk was badly recompiled: after extracting it from boot.img using Android Image Kitchen I recompiled it with the recompile.bat that ouputs two files: img-new.img (cannot figure what's its utility...) and new-ramdisk.cpio.gz that I simply renamed ramdisk.img. This could be the main reason why the AVD isn't working.
Will look up how to deal with ramdisk soon.
==========**2**==========
Operation:
•Restored the original kernel-qemu from backup
Test:
•The AVD still not show anything but quiting the emulator doesn't trigger any crash now.
Result: FAIL
Troubleshooting:
•As mentionned before will look up ramdisk.img file that seems problematic

Thread closed. But the project of emulating a custom rom is not abandoned.
Actually I didn't find a way to use the new AVD tool provided by Google to reach this goal. Instead I am heading over the new idea of creating a software generating an environment for Android emulation with given components (kernel, system, data etc. prealably extracted or, better, from a backup)
I hope I'll get help in the future because I'm pretty sure I won't be able to do such enormous task alone...
New thread here: https://forum.xda-developers.com/android/development/help-environment-builder-custom-rom-t3758360

Aio fastboot

#I am not responsible for any bricked devices!
#Thermo-nuclear war!
#OR your alarm clock failing to ring , resulting in you losing your job!
AIO FASTBOOT!​
What it entails;​AIO fastboot is a small peice of software that aims to make the whole fastboot experience less long-winded and intimidating for beginners and lazy people!
(if you have allready bricked your device multiple times and are a brick- hardened veteran , you can walk away.)
.Instructions are packed in the installation directory of the software, but here you go :
1. Make sure that adb and all relevant drivers are installed.
2. With your system boot and recovery image , name each respectively 'system' 'boot' recovery' .img , and place them in the same directory as the .exe file.
3. Try not to brick your phone.
.Please dont hesitate to notifty me about any bugs and issues
.Also, please dont hesitate to give me new ideas and request any new features!
Compatibility
Has only been tested on the p30 pro (VOG L29) an the p9lite (VNS L31)
-But should work with any device
Downloads
beta
Mod Edit : Link Removed

password please!!!

jG8Bhqy0nz5Ll8oqZZcXdViS5etrKk-HG7vtarnHpfM

Virus
Here is the result:
VirusTotal.com
Be really carefully:
(source: https://www.f-secure.com/v-descs/trojan_w32_generickd_3016333.shtml)
Trojan.GenericKD.3016333
Trojan.GenericKD.3016333 is ransomware that encrypts files stored on the affected device and demands payment of a ransom.
Regards,
k1ll3r8e

As he said ^^
Do not download / execute the file.
It's ransomware trojan which might damage your Windows Installation.
-XDA Staff

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