Related
I have been following the Threads since I got my G1 for about 3 weeks now. Two days after receiving it I got the OTA update from T-Mobile before I knew it I was on RC30. After DREAMIMG.nbh and very careful reading I was able to downgrade to RC29, Root - Telnetd, and install RC30 Mod JFv1.2 then JFv1.3. Finally I installed Bootloader and got the skateboarding androids.
After a couple days of reading, I took the plunge. Let me be the first to say that as a Windows XP user, alot of this information is very confusing as I am used to a Dos type system, and all of these commands made it seem a bit more confusing than it really is.
Now that I have root and bootloader I would like to start to change the boot screen and try my hand at some Linux based stuff?
Being that I use Windows XP, it is my understanding that I can run Linux using Slax? I am very computer literate, but haven't tried my hand at programming since the days of Dos and Paschal. Are their any online tutorials that somone would recommend as a starter or is the Android Software so different that it may be better to start from scratch?
Willing to learn any pointers would be appreciated.
I may be misunderstanding you but if your looking to make any modifications to the operating system itself (which is definitely needed), I would suggest having a look at the Android source code at http://android.git.kernel.org. The back-end of the platform (kernel, etc) is all written in C. The userland stuff is written in Google's implementation of Java called Dalvik. Now that you have the dev bootloader, all you really have to do is clone the official android repository, make your changes, build and flash to the device using fastboot.
Thanx Datruesurfer
After all the reading it seemed alot of work was being done in Linux but I don't know anything about that so, I could be completely off base.
At your suggestion I looked at android.git.kernal and it seems they do a good job at explaining some things, but it still makes many references to Linux and Unix.
Would programming of Git be done in linux. I see that Git is gotten using .tar files which is Linux compressed files? So is it best to try to do programming using slax or ubuntu?
Also, are things like the boot screen modified using Linux based .png or can that be done in Windows?
Let me say sorry in advanced, as I am doing this for the first time, please say stop if I am being too n00bish.
Also...I noticed ....
that the commands given in the Git User's Manual look very familiar like the commands that were given while I was reverting my RC30 back to RC29 using the Pterminal/Telnet. Can this programming with Git be done off of the G1 Phone itself?
You're in over your head dude. If you haven't programmed in these object oriented based programming methods and you know nothing of linux, then recompiling the android source like the above poster suggested is too much.
I don't mean to dissapoint or negatively comment, but really save yourself the trouble.
If you really want to though, figure out the basics of C and java programming and start reading the source.
Brutal-Force said:
After all the reading it seemed alot of work was being done in Linux but I don't know anything about that so, I could be completely off base.
At your suggestion I looked at android.git.kernal and it seems they do a good job at explaining some things, but it still makes many references to Linux and Unix.
Would programming of Git be done in linux. I see that Git is gotten using .tar files which is Linux compressed files? So is it best to try to do programming using slax or ubuntu?
Also, are things like the boot screen modified using Linux based .png or can that be done in Windows?
Let me say sorry in advanced, as I am doing this for the first time, please say stop if I am being too n00bish.
Click to expand...
Click to collapse
A Few things...
1. Android and Git are two completely different products. Git is the revision control system used by Android. Whenever one of the developers at Google makes a change to the source code they will upload it to the repository. Then people can go revision by revision to see where modifications have been made and suggest their own if they wish.
2. The part where a Linux box would be handy is actually downloading all of the files in the repository and compiling your own build. As dirr said, you probably should hold off on this until you have a better understanding of the platform itself.
3 As far as the boot image goes, the bootloader will only accept files that have been formatted specifically for it. Once you have the image formatted, you can flash it in the SPL via fastboot (the screen with the skating androids) I believe this can all be done via windows now.
4. I think I better understand where your coming from as far as modification. You should look at http://code.google.com/android to learn about how to code in Dalvik, as that will help you out much more then learning C. Once you have a good understanding of that, you can try to build from source
Hope that helps...
Thanx for the advice.
After reading about the above suggestions, it does seem that to do something simple would only be simple for someone who has all the background programming information of different platforms. This is probably why most tutorials/procedures are written so vaguely here. I appreciate the input and I will hold off and just read up on things other "more experienced" people write about here. I have a basic understanding of what is happening, but the "language" is so complex. Maybe in baby steps I will learn, since it appears that on this forum "Android" is fairly new. And while I am watching what is happening here, I will get java for dummies or bone up on Dalvik and start reading and practicing. Thanx for the help guys, and thans JF, Koush and all the other senior members for the RC30 Mod. At least I have the skateboarding Androis
I'm Linux & BSD literate, and used to administering servers, compiling programs and kernels from source. I've also managed to root and flash my Magic, following advice found here. What I'd like to do is gather up some info on how to build ROMs for the Sapphire platform.
I'm already poking around the Android Wiki FAQ and the Dream dev forum on this site. There's quite a bit of info there but some of it is out of date and I've not found much that's Sapphire-specific. I also plan to take apart the .zip files released by Haykuro and others and compare/diff configs to get a feel for things.
My intent is to put together enough info to allow anyone to pull apart a released ROM and replace the dialler, add some language support or some extra apps, maybe make some other simple changes.
What I need is any pointers on:
1. Sapphire-specific info.
2. Any danger of bricking my Magic by messing around with home-made ROMs.
3. Anything else that might be useful.
Hopefully I'll be able to put together a rudimentary HowTo for the wiki, which others can add some fine-tuning and extra info to.
Thanks for any input.
I think this is a very good idea!
It would simplify things if everybody would understand how exactly custom ROMs are created.
1 - Be aware that there are different Magic HW versions...
2 - I don't think you can brick your magic as long as you make backups via nandroid.
3 - A few things I think should be in the wiki :
- how to completely setup a linux environment and which applications you need to be able to build custom ROMs.
- Explain how the android OS is working, explain what boot, hboot, recovery, system is, how the partitions work, etc..
- What are test-keys, what is the difference with and release-keys.
- How to sign.
- How to dump the recovery.img, boot.img without having root access.
- What to change into the recovery.img and boot.img to get root.
- How create an update.zip
- How to make backups with nandroid and how to restore them..
Agreed think this would be a fantastic idea, unfortunately it seems like the people in the know are not willing to share any of their knowledge =o(
Do keep us up to date as to what you find by dissecting the ROMs, had a look the other day briefly but didn't have time to play yet,
Also waiting for info/confirmation that as long as you just flash bad roms its not possible to brick your phone only if you play with SPL's and such
fxn said:
Agreed think this would be a fantastic idea, unfortunately it seems like the people in the know are not willing to share any of their knowledge =o(
Click to expand...
Click to collapse
Oh, I'm sure the knowledge is scattered around the place - sharing is one thing, bothering to document is quite another!
The only thing I don't expect to find openly shared is traceable leaked material, and frankly I can live without that.
OMG ROXORZ I DID IT I DID IT!!!
ok now that i have all the noobs attention please read, and stop posting stupid questions.....
(Mods, i know this is probably not what the forums need, especially as this is a repost of a sticky, but I (along with others) am tired of seeing inexperienced users post about system dumps/ROM/apps/stupid junk when all they need to do is use the search function!)
***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
misleading topic title?
Pinesal said:
misleading topic title?
Click to expand...
Click to collapse
thats the point... maybe if people see something they are wanting, they will actually read the thread.
palosjr said:
thats the point... maybe if people see something they are wanting, they will actually read the thread.
Click to expand...
Click to collapse
haha. thanks for wasting 30secs of my life... anyway, what's Eclair?
[e] still props for compiling the list, i would correct the title (FAQ?) and make sure it gets sticky... i was really wondering why noone else did something like that. you can't complain about newcomers asking question if you don't have such a list
this thread is misleading bull****, should be locked
vihil said:
haha. thanks for wasting 30secs of my life... anyway, what's Eclair?
[e] still props for compiling the list, i would correct the title (FAQ?) and make sure it gets sticky... i was really wondering why noone else did something like that. you can't complain about newcomers asking question if you don't have such a list
Click to expand...
Click to collapse
this is exactly what i was pointing out ^^^^^^ nothing against you vihil, but you were the first to bite. all this information is in a sticky at the top of the Development Forum, but noone reads it anymore. I was just trying to get it out there in the "threads that are actually read" stream.
where are the sshots?
sshots or it didn't happen
rubbachicken said:
where are the sshots?
sshots or it didn't happen
Click to expand...
Click to collapse
lmao .. please tell me you're joking right? .. did you not read ANYTHING?
Ok....But how did you get 2.0 working on your Hero?
;]
xidominicanoix said:
lmao .. please tell me you're joking right? .. did you not read ANYTHING?
Click to expand...
Click to collapse
seriously... some of these ppl should not even be a part of this forum... i am half tempted to open a poll for the banning of members that post on this thread asking how i got it to work, ask for "sshots" or ask any other stupid question pertaining to eclair...
palosjr said:
seriously... some of these ppl should not even be a part of this forum... i am half tempted to open a poll for the banning of members that post on this thread asking how i got it to work, ask for "sshots" or ask any other stupid question pertaining to eclair...
Click to expand...
Click to collapse
HAHAHAHAHAHAHAA i love this. now for real n00bs to find this and read it...
This thread should be removed... you're only adding more useless content to the forum. Kinda hypocritical.
You got me good. I was actually excited for 0.5 seconds until I read the first sentence.
I thought this would be interesting....you realize legitimate power users would click on this and now we just have wasted time. I hope this thread vanishes.
dills84 said:
This thread should be removed... you're only adding more useless content to the forum. Kinda hypocritical.
Click to expand...
Click to collapse
no more useless than the previous 6 threads on eclair or an eclair port within the past 3 days.
even if they open it they wont even read it nonetheless, its almost impossible for these nubs
my point in this entire thread is an attempt to get noobs to read important info. case in point... in 15 minutes this thread already has almost 600 views...
This thread made me happy lol. I praise your efforts, but the n00bs are out of control and there is no helping them anymore. Its just "gimme, gimme, gimme". They want everything handed to them.....
At least the XDA Wrecking Crew made an appearance before the thread got locked.
LOL
+1
/10char
I am getting rather tired of answering questions answered 10...000 times
Hello to everyone, this is my first thread
I'm not a developer (because if i am a developer i already know this things ), and that's why, as I wrote in the title, would like to know specifically how android is built.
Can someone explane me (or link me another thread) what partitions Android needs and what there is in any partition? (I already know some of those, like the System partition, the Recovery partition, Boot, Userdata, Cache..)
I would like to start learning this basic things, and maybe continue this thread with other informations.
Note 1
I know that in the internet there are millions pages within those informations, but I prefer to learn this things step by step talking (or in this case writing) with other people because if I don't understand something they can help me or explane the concept in different words.
Note 2
I'm italian, so my english is not so good....sorry for any grammatical errors
OK, so you messed up your device real bad trying to do something and it needs a full flash of the original firmware. Well, lucky you I am here to help you in your journey back to your device's roots, the good old days where everything worked just as it should.
Now, I am gonna be very honest with you about some stuff:
- This is my first XDA post and I really wish it were better formatted;
- English is not my first language, so I really hope this is understandable to everyone; (feel free to correct me)
- I have 0 responsability for whatever you do to your device, so if you f*ck your device up so bad it doesn't even turns on anymore, its not my fault.
!!!!!!! IMPORTANT !!!!!!!
The firmware provided here works ONLY for MOTO E6 PLAY, it WONT WORK with ANY variation. DONT try to install it in any device other than the bali, and if you do, DO NOT BLAME YOUR DEVICE LOSS IN ANYBODY BUT YOURSELF.
Well, that said, the procedure:
Edit:
Apparently, the Bali itself comes in more than one version (not impressive, a detail I definitely should have paid more attention to). There are the
XT2029-1, XT2029-2 and XT2029-3. In the device's configuration app, under System, in Regulatory Information, you can find which one is yours.
First, download the file correspondent to your version from here: https://motostockrom.com/?s=XT2029
Notice that the files that appear for download first aren't the most recent ones. To be certain that you downloaded the most recent build to your version, check it in the ZIP's filename, e.g.: Motorola_Moto_E6_Play_XT2029-3_MT6739_POA29.550-81_2003_20200311_9.0.zip (date is in the YYYY/MM/DD format)
From now on, I'll be making a lot of references to the downloaded file's directory structure. To mitigate any possibility of confusion, I'll be referencing the root of the directory as / and any sub-folder as /Folder/
After that, extract the files from the ZIP. Looking inside /, you'll find the firmware files under /Firmware/ and links to pretty much all you need to flash the original firmware, bootloader, recovery, and even instructions to recover the device's IMEI.
Our device has a MediaTek chipset, so SP Flash Tool is almost the sole thing that is needed to recover a soft broken device (Only problem would be if the devices scatter file weren't available, but fortunately this isn't the case).
Inside the /Driver/ folder, you'll see links to necessary drivers for the computer to correctly identify the device. Follow the links, download and install the drivers.
Refer to the /SP Flash Tool/ directory. Follow the link inside it, download the latest version of the tool for your computer's OS (Windows/Linux);
Now refer to the How To Flash link in /, be it the (Tutorial) or (Video) one, which suits you better. Follow the instructions very carefully and thoroughly and you shouldn't have any major issues flashing the firmware. After the flash is done and the device reboots, congratulations! You've made it! :victory::highfive:
DISCLAIMER:
I like to give credit where its due. Inside /, you'll find a credits file. That website isn't mine, and the development of the file and the tutorial was completely made by them, so all the credits go to the proper owners of the website. I am just sharing it here for the benefit of the community.
Well, if you have any questions, feel free to post a response. I am no Android OS developer myself (though I do develop some other stuff - Java and Python mainly - and am a OS administration and troubleshooting geek, Android is still very shady and very out of my league for me), but I'll be happy to help with anything I can.
Happy Hacking!