sorry if these have been asked many times before, i've searched but cannot find much about it.
new to Android, coming from a WM for the past 8 years background its all foreign to me.
1) what is "adb" and how does it differ from "RC"'s? I presume RC's are just different build numbers for Android.
2) whats the difference between Haykuro, JF's builds? are any of them cupcake? how can i think about them in terms of Windows Mobile roms?
3) if I install one of the above, will the over the air updates still work? if there is an update to the OS (ie cupcake if the rom isnt) can this be applied at all or will i need to "lose everything" and wipe/flash to the new one?
again sorry for the n00byness.
1) what is "adb" and how does it differ from "RC"'s? I presume RC's are just different build numbers for Android.
adb is a way of telnet'ing from your pc to the phone, this gives you root access.
2) whats the difference between Haykuro, JF's builds? are any of them cupcake? how can i think about them in terms of Windows Mobile roms?
Haykuro and JF's builds are based on the android development branch, they are basicly updates that are based on googles on going improvements to the phones OS. Hayjuro's is based on a port from the upcomming saphire phone. Treat them as different "flavours" like schnaps etc
3) if I install one of the above, will the over the air updates still work? if there is an update to the OS (ie cupcake if the rom isnt) can this be applied at all or will i need to "lose everything" and wipe/flash to the new one?
Current custom roms change the signing keys so OTA updates are not updated onto the phone. You would have to manualy change the rom yourself.
Hope this helps
Imp
thanks,
by ADB i meant (as in the JF threads) there are three diff versions rc33 rc9 and ADB1.1
also if having to reflash with new version, presumably that would wipe everything? is there a way of backing stuff up or are backups not as bigger deals as they are for a WM based OS.
The ADB build you refer to is essentially a rooted version of the ROM that came with the non-T-mobile branded developers phone.
Regards,
Dave
Impossible said:
adb is a way of telnet'ing from your pc to the phone, this gives you root access.
Click to expand...
Click to collapse
Err no. adb (Android Debug Bridge) is a tool for debugging Android devices both physical and virtual (in an emulator instance). One of its features is to give you interactive shell access, but this has nothing to do with telnet.
Haykuro and JF's builds are based on the android development branch
Click to expand...
Click to collapse
Also wrong. JF's builds are based on officially and unofficially released current branches, not development branches. Also, they are not ground-up rebuilds of the source code in as much as they are just modifications to existing releases to add root and other goodies.
Haykuro's builds appear to be coming from some private source close to HTC. These are not based completely on the open source development branches either.
thanks,
by ADB i meant (as in the JF threads) there are three diff versions rc33 rc9 and ADB1.1
Rc33 is the current US G1 tmobile rom, Rc9 is the current UK G1 tmobile rom and the ADB1.1 is the developers rom thats carrier free. Think of these are the different between a WM "clean" rom and a carrier rom (such as att)
also if having to reflash with new version, presumably that would wipe everything? is there a way of backing stuff up or are backups not as bigger deals as they are for a WM based OS.
As for destructive flashing... the G1 can do non wipe upgrade but IMO I prefere a clean (wipe before) install. As default the G1 roms store images/music/bookmarks and other customisations to the sd card and if your syncing your contacts with gmail, they will be restored after your rom update, so even with a wipe>install you dont loose much (you loose things like text's, mms's and installed apps)
thefunkygibbon said:
thanks,
by ADB i meant (as in the JF threads) there are three diff versions rc33 rc9 and ADB1.1
Click to expand...
Click to collapse
What you're referring to is the ADP not ADB.
ADP = Android Dev Phone
ADB = Android Debug Bridge
very helpful guys, thanks. as for over the air updates is that just for OS based stuff or do apps too? (do apps even update themselves?
if you have installed apps to the SD card then wiping the device is even less of a problem i assume
If you install JF's RC33, (or RC9 if you are in Europe), you will have a phone pretty much exactly like the official ROM, except you will have root and multitouch.
If you install ADP 1.1, you will have a dev phone with multitouch and root, but you won't see protected apps.
If you install Haykuro's H build, you will have HTC's "cupcake" phone with lots of added goodies and root.
If you install Haykuro's or the Dudes G build, you will have the Google "cupcake" phone and root.
The "cupcake" builds are very usable and stable, but there are still a few bugs being worked out on them.
With any of the builds, you will also need to use the radio version for that build. (RC 33 and RC 9 are using the radio you probably already have).
The radio can be flashed either before or after, and it won't touch anything on your phone, but it will reboot twice, so don't panic if you do that and see your phone hanging for a few minutes on a different screen after the first reboot.
With all of these versions, you can also put your apps on your SD card with a little more work.
If flashing a different rom, first sync your contacts, then use something like power manager or astro to back up your apps to your SD card, that makes it easier to get everything back. You will definitely want to do a wipe to avoid problems.
It is possible to go back to official roms after updating, but you will lose root, and I don't think you will want to go back. Often times you will get the modified updates here before they are even released officially!
Wow thanks, thats pretty much cleared up my questions!
.
With any of the builds, you will also need to use the radio version for that build. (RC 33 and RC 9 are using the radio you probably already have).
Do the files provided in the threads usually contain the radio's too are they seperate downloads/installs?
With all of these versions, you can also put your apps on your SD card with a little more work.
If flashing a different rom, first sync your contacts, then use something like power manager or astro to back up your apps to your SD card, that makes it easier to get everything back. You will definitely want to do a wipe to avoid problems.
Its something i'm used to with WM phones, but its always a complete ball ache resetting everything up and installing everything.
Is it at all possible to have some kind of OTA updates hosted system set up elsewhere (such as you or me) which could deploy the updates for these "hacked" roms, much in the same way as tmobile etc do?
Do the files provided in the threads usually contain the radio's too are they seperate downloads/installs?
It will say in the threads if you need to install the radio seperately. On most of the newer builds you will need to install it.
Is it at all possible to have some kind of OTA updates hosted system set up elsewhere (such as you or me) which could deploy the updates for these "hacked" roms, much in the same way as tmobile etc do?
The only roms which notify you of updates are the JF ones. There is an app on here that you can install which will let you know if there are updates. So far, it is all do it yourself as far as updating goes.
I don't know if it is possible without a lot of work to have the updates pushed automatically to your phone. At the moment, there are so many roms, some of which are updated more than once per day at times.
I have no idea what pushing them automatically to you phone involves, maybe someone else here does.
Related
Hi,
I have a tmobile wing flashed with touch-it 2.3. The JAVA midlet manager is part of the ROM, it is an old version and I would to install a newer version. My question is, if I install a newer version will the installation be similar as an upgrade on a desktop computer or will I have 2 different versions (I am not sure it this would cause some interaction problems that is why I have tried this yet)
Or Is there any way to remove a application included in a ROM?
Thanks!
not sure about the upgrade part .. i assume the program will auto know that a newer version is being installed and will remov old ver.
as far as removing from rom, by my knowledge, the only way to do that is by extracting the rom usind the kitchen for that rom and recompiling it with stuff u want .. for this however u need to hav chef permission and kitchen
I am new with the whole cooking/flashing world, so I am not sure about the cooking thing. I will have to read about this. I guess I will have to try the upgrade thing.
Well, I tried and instead of upgrading the existing the older version of the application I have 2. This is a bit annoying since I have to install it on my already very limited internal memory. Is there ANY way to go around this, either by actually writing over the older version or removing it?
Help please!
Hi,
Some people on the forum probably noticed it already before me, but tweets from Cyanogen and JBQ brought it to my attention that the official Android 1.6 system images for the ADP1 are now available for download from HTC:
http://developer.htc.com/adp.html
I haven't installed them yet because my unofficial Cyanogen build is probably better than those in a number of ways ;-) But I did download them.
Also, these are probably required to build a real & working Donut 1.6 build from the AOSP tree.
Cheers everyone, and enjoy!
--Tim
Just wondering couple things:
1. Does it have Google Apps?
2. Do you loose root if you install this?
3. Does it mess-up recovery image?
So did anyone try it yet?
Hi Karolis,
I haven't checked the contents of the images but I expect them to have the Google apps. The 1.5 images from the same site contained them, as far as I know.
Whether or not it messes up the recovery image depends on the method of installation you choose, but you can always put back the recovery image of your choice on your ADP1.
I don't know about losing root access or not. I've heard people claim that it depends on your recovery image used. It will not include the SuperUser application but you can install that manually.
Cheers,
--Tim
HTC is an authorized Google distributer I guess:
# Use of the Google Software by You
1. You agree to use the Google Software only for purposes that are permitted by (a) this License Agreement and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries).
Click to expand...
Click to collapse
I'm going to flash just the system image and see how it goes...
Didn't wipe, going from CM 4.1.11.1 to 1.6 - boot looped.
Finally got back to recovery (Cyanogen Recovery gone!) and wiped cache + user data, and at least got it to boot. Phew!
Better get Cyanogen's recovery back pronto, so I can restore my nandroid backup.
/Mats
dude.... dont use the OTA, use fastboot and fastboot flash boot and system and reboot -w. The reason it requires a wipe is because of the differences in frameworks, apps, dependencies, ramdisks, etc.
I was waiting for this, this is going to be my default now. I don't like all the stuff Cyanogen does to builds, I preffer the official ADP builds 1000's times more.
---edit----
I flashed it right away and now I'm confused. It's 1.6 alright, but the build is different from previous ADP builds, no dev tools or spare parts or anything else. This is almost exactly what you'd probably get from a stock 1.6 build, weird...
BTW, you don't lose root with this, ADP builds are meant to be rooted, you know?
can someone confirm if you lose cyanogen's recovery image?
···
这个还不错··希望走点出update包····but··我最期待cm 4.2···
Agh someone plz post a 32a version
Gosh, what a mess. After finally getting CM recovery back in, I went for a nandroid restore, but instead made a nandroid backup, overwriting my precious backup of my phone as it was before embarking on this 1.6 adventure. Well, after reinstalling CM 4.1.11.1 (hush - I had a backup on my SD card!) at least I got all my apps back.
Why must I dive into stuff like this when I'm in a rush and really don't have the time for it?
/Mats
I don't understand. Why such interest in this build when it specifically states this is for ADP (Android Development Phones) ONLY!
If you do not OWN an ADP1, then please, this thread has NOTHING for you of interest.
marty22877 said:
can someone confirm if you lose cyanogen's recovery image?
Click to expand...
Click to collapse
You wont loose it if your flash the new system and boot partitions via fastboot. Any of the Apps 2 SD stuff won't work though.
elzee said:
I don't understand. Why such interest in this build when it specifically states this is for ADP (Android Development Phones) ONLY!
If you do not OWN an ADP1, then please, this thread has NOTHING for you of interest.
Click to expand...
Click to collapse
????
Aaaanyway... I noticed this build doesn't let you su (wrong uid for the su binary), but that can be fixed easily, just pull su and Superuser.apk from another build, boot your phone into recovery, and push su to /system/bin and Superuser.apk to /system/app, then chmod 4755 /system/bin/su and reboot.
---edit--
you might also want to rm /system/xbin/su, but I don't know if it's really necessary or not. Gonna try it.
ok, removing xbin/su did nothing apparently, so it's safe. Keep in mind though that the stock boot.img is doesn't allow you to adb remount, but you can still adb shell, then su, and then remount manually (mount -o rw,remount /system). We just need to change ro.secure in it and we're good to go.
Using fastboot to only flash boot and system worked perfectly fine for me.
Very nice and clean.
Apps2sd can still be had if you want to, just do it the manual way (creating symlinks).
Pushing the xda versions of Launcher and Messaging makes the phone very, very nice - and the only things that I feel I'm missing is the userinit.sh and compcache really....I never really noticed/cared too much about the BFS.
Pretty nice build to be honest....
elzee said:
I don't understand. Why such interest in this build when it specifically states this is for ADP (Android Development Phones) ONLY!
If you do not OWN an ADP1, then please, this thread has NOTHING for you of interest.
Click to expand...
Click to collapse
Because the G1 and ADP1 are both identical Dream handsets? And people want an official donut, rather than 1.5 with many donut features hacked in?
just wondering, will this work with rooted Dream Phones???
bootloader
i'm getting error message updating from 1.5 adp crc1:
Bootloader Version...: 1.33.2005
Baseband Version.....: 2.22.19.26I
Serial Number........: HT847GZ00498
--------------------------------------------
checking product... OKAY
checking serialno... OKAY
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2005'.
Update requires '1.33.2004' or '1.33.0004' or '0.95.3000' or '0.95.0000'.
Click to expand...
Click to collapse
i have a adp phone.
tried to roll back to stock 1.5 img or ota, same issue, is someone had this issue?
@ anyone who tried this. Which build number is this? Is it newer than 1.6_r1 (DRC79) or should I keep building the experiemental tree?
About the time when further existence of Cyanogenmod was endangered because of Google's legal claims, there happened to be a post from the author of Cyanogenmod:
Since I don't work with any of these closed source applications directly, what I intend to do is simply ship the next version of CyanogenMod as a "bare bones" ROM. You'll be able to make calls, MMS, take photos, etc. In order to get our beloved Google sync and applications back, you'll need to make a backup first. I'm working on an application that will do this for you.
Click to expand...
Click to collapse
The current state is that (supposedly) Cyanogenmod build does not contain any Google apps, BUT in fact to install Cyanogen you should first flash a development image from HTC (DRC83 or so) that contains them, and atop of this Cyanogenmod.
My question is, will the current Cyanogenmod build work without the HTC "base" files, in the way it is described in the message quoted above?
I own a Magic 32A. Could I just flash the latest Cyanogenmod update.zip (and another update.zip with appropriate kernel)?
I DO NOT want any proprietary apps on my phone.
(It will suffice if I have a web browser and a basic contact list application, without syncing.)
If anyone knowledgeable in the affairs of "update.zip" format reads this, I would also like to know if the Cyanogenmod's update.zip does only write some files to existing filesystems, or does it first erase/create new filesystems in some areas of flash memory? And what does the update.zip from HTC do (this one is certainly supposed to erase the root filesystem of the device!)? Would applying just the Cyanogenmod's update.zip leave the HTC files in place if they are already there, and how can I clean the root filesystem?
Not sure if that's how it works. Why don't you just remove the apps after?
If you really want Android without Google Apps, you can also compile from the source Android. That will give you basic functionality (phone, contacts, email) without Google Apps on it. You just need to checkout donut branch, instead of eclair's, since eclair is still on development.
Check: source.android.com and follow the documentation to checkout and compile for dream and sapphire
xaueious said:
Why don't you just remove the apps after?
Click to expand...
Click to collapse
The Google's libraries seem to be hiding in every corner, so that's not really clean.
@dferreira
Right, but it is probably some hassle (and I would duplicate some work of the people who publish their images here), also the download would take a long time with my internet connection. Why do it, if it's already done? A stock Android build from AOSP must be hanging somewhere around... but I haven't seen it yet. All the donut images I've seen on this forum had some silly modifications and were prepared to work with Google packages.
(Or is the source prepared nicely enough to work right if it compiles successfully and is put on the device? How do you put the build in an update.zip to allow flashing to a consumer device with a custom recovery image, but without engineering SPL?)
Donut branch should compile and work without a hitch. Even eclair works out-of-the-box, without camera working and 3D acceleration.
The compiled result will be recovery.img, boot.img, system.img, userdata.img... I've flashed them using fastboot Unless you know how to make a update.zip out of these, you should be all set. The update.zip only works if signed with the right certificates for non-engineering SPL devices.
The update.zip only works if signed with the right certificates for non-engineering SPL devices.
Click to expand...
Click to collapse
I wonder how do some folks from this forum do it then?
I doubt they have relations with google employees!
Do you know which kernel trees are compatible with the 3.22.20.17 radio firmware that is found in stock Magic devices?
AOSP has a kernel project and HTC has put some kernel sources at developer.htc.com, but there's only something called "HTC Magic Kernel Source Code" - no mention for which model.
Well, actually, i might do with some of the kernels that lie around the forum, but do they have any special requirements for initrd and modules, that would require modifying the flash images you get from building the Donut branch?
Seems to me that kernel is in the boot.img. You flashed it and everything works. You have not touched the radio firmware. Correct or not?
kguciek said:
I wonder how do some folks from this forum do it then?
I doubt they have relations with google employees!
Do you know which kernel trees are compatible with the 3.22.20.17 radio firmware that is found in stock Magic devices?
AOSP has a kernel project and HTC has put some kernel sources at developer.htc.com, but there's only something called "HTC Magic Kernel Source Code" - no mention for which model.
Well, actually, i might do with some of the kernels that lie around the forum, but do they have any special requirements for initrd and modules, that would require modifying the flash images you get from building the Donut branch?
Seems to me that kernel is in the boot.img. You flashed it and everything works. You have not touched the radio firmware. Correct or not?
Click to expand...
Click to collapse
Yes, the kernel is in boot.img, and it is the AOSP kernel that comes with the source code There is no radio firmware on AOSP.
update.zip is made by issuing make otapackage.
Hi buddy i thought about something like that few weeks ago and i think MarsDroid has already made some version of Android(Very lite MarsDroid SPL 7) fully without Google apps, so try it..
OK, I've built an image from donut source, coupled it with a kernel from a CyanogenMod port, and it works flawlessly on my phone!
I've uploaded the images to RapidShare, should anyone need them Links are at my website (guciek.net/en/stuff/android_builds).
kguciek said:
My question is, will the current Cyanogenmod build work without the HTC "base" files, in the way it is described in the message quoted above?
I own a Magic 32A. Could I just flash the latest Cyanogenmod update.zip (and another update.zip with appropriate kernel)?
I DO NOT want any proprietary apps on my phone.
(It will suffice if I have a web browser and a basic contact list application, without syncing.)
Click to expand...
Click to collapse
Yes, it works fine if you don't flash the 'defanged' update image first.
unfnknblvbl said:
Yes, it works fine if you don't flash the 'defanged' update image first.
Click to expand...
Click to collapse
But it wouldn't erase the whole system partition, so there could still be some files left.
Now that I realised I can flash images from recovery even without engineering SPL, it seems a safer and cleaner way.
Also, I like to have a second ext2 partition on SD card that is only accessible from a computer, and I wasn't able to do this with CyanogenMod, which instantly filled it with apps2sd data, swap files etc...
kguciek said:
But it wouldn't erase the whole system partition, so there could still be some files left.
Click to expand...
Click to collapse
No, that's why you wipe from recovery before installing.
unfnknblvbl said:
No, that's why you wipe from recovery before installing.
Click to expand...
Click to collapse
Actually wiping only erases the data partition, not the system one.
fastboot erase system -w
carz12 said:
fastboot erase system -w
Click to expand...
Click to collapse
Right, but it isn't possible for users with unmodified SPLs.
Actually, you can just flash a image of an empty yaffs filesystem to system partition (it's just a few blocks at most).
Hello,
I have a HTC Touch Diamond 100 and I installed the "Froyo FRX06 XDandroid NEW system update" review in the post "[prj] [XDANDROID] [AOSP] [FroYo | GINGERBREAD] [31.03] System Update" and everything works fine except that it doesn't recognize SDcard applications.
There's no Error Message in the screen, is just that the system doesn't recognice anything in the SDcard. I put my apps in the folder: AndroidApps-> Other. I think it's not the common fault that I have read many people have "Waiting for SDCard error. For people who have problems with sdcard message, add this to your startupmsmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave" because for instance the phone let me save the pictures i've take with the camera phone or install and recognice any app from the market.
I 've Format the card with the HP tools after initial installation and then i had restore all the files in the internal storage.
P.S. Sorry for my possible spelling mistakes but English is not my native language
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
R^7Z said:
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
Click to expand...
Click to collapse
Oh what A noob mistake xD I didn't know that apps in the "Other" folder doesn't follow the "typical rules" for instaling apps (i've come from previous releases of Android, Eclair specifically, and in that version it was only place in this folder to install apps).
I'm using froyo instead of gingerbread builts because HTC touch Diamond it's quite old and i don't know if the performance would be better or slower than froyo performace but if you recomend me to use that gingerbread bundle i would use it.
Thanks R^7Z.
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
R^7Z said:
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
Click to expand...
Click to collapse
I see what you say but honestly, right now, I'm looking for stability and performace, if you know that gingerbread build GBX0A have better performance (i supose that it's less stable because it's an alpha) than FRX06 i'll choose Ginger
Thanks again R^7Z.
When I get a new computer that's filled to the brim with bloatware, I put my cleaning gloves on and uninstall every thing on that machine until it's a clean-slate - looking like Windows was just installed.
I just got an Android phone and - surprise surprise! - it has bloatware packed in by Verizon!
Before I get ahead of myself, my device is a Droid RAZR (16GB) on the Verizon network running Android 2.3.6 using the latest OTA update of 6.12.181. (Uses CDMA, too.)
Now, when I get a new computer I do one of two things:
I manually un-install all the bloatware or
I install a clean copy of Windows.
On Android, option 1 doesn't work since the bloat is built into the device's ROM. My question is about option 2.
Now from the research I've done, a custom ROM is usually the work of a team who takes a clean Android ROM and builds on top of it, adding apps and themes.
I want to skip the middle man and just have a clean Android ROM to flash onto my device. No added applications by a team (or my carrier), just a blank slate that Google created to begin with. Sorta like installing a clean copy of Windows.
So: does anyone know where I can find this mythical ROM?
Both options you mentioned will require you to root your phone. And rooting your phone usually means that you void your warranty.
I don't think i have seen a vanilla Android ROM for the Razr, then again i haven't looked that hard.
So you have a couple of options.
1. Root your phone and manually remove the apps you don't want
2. Root your phone, install custom rom and remove the apps you don't want.
3. Root your phone, download the source code from source.android.com, compile and install.
Thanks for the heads up, I did a lot of research before this post and I have a rooted phone already. In fact, I've even installed a custom ROM but I'd much rather have a clean version of Android and build on that for myself.
I'm going to look into vanilla ROMs and if I can't find anything, I'll research into making my own ROM
Out of curiosity, why do you think that vanilla ROMs aren't as popular as modified ones? I'd imagine more people would be asking for just plain Android ROMs and installing whatever they wanted.
Vanilla ROMs aren't popular cause custom roms throw in stuff Google didn't give you.
Sent from my U8150 using XDA