Related
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.
Download link: MT3GV1.5_NBN1.5.zip
MD5:
1c962a4767659f86776fe6daf3052cf7 MT3GV1.5_NBN1.5.zip
This is the result of the work/messing around I did in this thread.
I started with the T-Mobile OTA stock ROM available here:
signed-opal-ota-150449.95700137.zip
I then:
1. Rebuilt the kernel with the same config as the ROM, except with the addition of the netfilter features required for tethering. (Kernel source is slightly newer than in the ROM as yesterday there were a few security related patches added to the repo.) The wlan.ko driver was rebuilt to match the new kernel as well.
2. Added the Superuser app and the Tethering app.
3. Removed the T-Mobile recovery and radio images. They are redundant at best, bricks waiting to happen at worst.
4. Re-packed and re-signed the ROM. (Only the ROM zip was signed so it would install via our recovery images. The internal apks were left alone.)
The result should be an experience identical to the stock software you had out of the box, but with the possibility of running apps that require root as well as tethering. Speed is the same, features are the same, apps are the same, etc.
There are plenty of great custom ROMs here if you're looking for more, but this will work if you're going for simple with no surprises.
UPDATE: Donut /1.6 update is on page 3.
UPDATE: Donut /1.6 DMD64 update is on page 4.
Is this for 32B or 32A?
This is for 32B.
awesome
hey man great job this is exactly what i want!!! great job!!!
atomtom, thank you for doing that. It's been working great the last 24 hours, no hidden gotchas or surprises from the updated kernel/wifi driver.
Thank you!!!...This is EXACTLY what I was looking for ..expecially for my friends who want root for wifi tether!!
Clean and Stock
Thanks for this ROM. I like clean and simple builts and this fullfill my tethering needs with my Viliv S5. I installed it today on MyTouch 3G.
Hi there
I installed this rom last night and by morning the phone was complaining about memory and had a bunch of processes force close.
Is there a mem leak or anything with this rom?
Not that I know of, but I only tested it for a few hours and then went on to Cyanogen for my daily use. Considering how similar this is to the stock ROM I would be very surprised if there was a memory leak.
Standard debugging questions: What SPL and radio are you running? Did you do a wipe before installing? Do you have a log we could look at?
I'll put this ROM back on my phone and see how well it's doing tomorrow.
Noticed an issue. The SU you are using isn't ideal. With tethering it was fine but as soon as I typed Su in terminal emulator, it starts the superuser permissions app, but it comes up blank. If I go back, its stuck waiting for Su permission. Zenthought.org has/had one I used, its from the JF and cyanogen builds. If u decide to use it make sure u change the Su binary too.
atomtom said:
Not that I know of, but I only tested it for a few hours and then went on to Cyanogen for my daily use. Considering how similar this is to the stock ROM I would be very surprised if there was a memory leak.
Standard debugging questions: What SPL and radio are you running? Did you do a wipe before installing? Do you have a log we could look at?
I'll put this ROM back on my phone and see how well it's doing tomorrow.
Click to expand...
Click to collapse
Hi there
I am running SPL 2005 (aman_ra mytouch root guide)
32B radio from htc site for google ion 2.22.19.26I
recovery 1.2.0G (aman_ra)
I have been going back and forth trying to find the rom that works best for me so yes i have done the format/wipe. Also since i want to be sure i might even run the following ontop of the format/wipe
fastboot erase system -w
fastboot erase boot
I dont erase recovery since i dont think i need to.
Please let me know.
Also - I would LOVE it if you could provide the same rom but with HTC keyboard/dialer.
flamingblue8z said:
Noticed an issue. The SU you are using isn't ideal. With tethering it was fine but as soon as I typed Su in terminal emulator, it starts the superuser permissions app, but it comes up blank. If I go back, its stuck waiting for Su permission. Zenthought.org has/had one I used, its from the JF and cyanogen builds. If u decide to use it make sure u change the Su binary too.
Click to expand...
Click to collapse
Yeah, the one that is available stand-alone is older than the one that comes with other ROMs. When I tried installing the newer apk pulled from Cyanogen 4.0.1 it would fail due to the key used to sign the ROM internals.
adb install Superuser.apk:
Code:
159 KB/s (14979 bytes in 0.091s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
adb logcat:
Code:
E/PackageManager( 58): Package org.zenthought.android.su has no signatures that match those in shared user android.uid.system; ignoring!
W/PackageManager( 58): Package couldn't be installed in /data/app/org.zenthought.android.su.apk
If anyone knows how to sort this out let me know and I'll update it.
That said, su still worked perfectly when I installed Better Terminal Emulator. (Of course, Better Terminal Emulator doesn't work to begin with. Try typing in a number.)
hmm interesting. when I was using just the stock ROM, then used 1click root, went into CM-recovery, followed by your directions, adb mount -a, then adb push the SU in reference, zenthought's, I had no issue. I then pushed the wlan.ko you put up, and flashed boot.img, rebooted, and finally installed the Superuser.apk, and I had NO issues whatsoever. i've got a nandroid backup of that system setup, in case there is anything of interest in there. I would have to boot back into it and remove my txts/mms/contacts, but i'd gladly share it for analysis.
I noticed the myTouch NBH appeared earlier, im going to try downloading that on my WinMo Wing (it connects to the wifi at the college im at but my G1 and myTouch won't.) i'll try flashing the NBH then your ROM, see what happens... oh and yes, I obviously wiped before installing ur ROM.
ROM has Superuser Permissions and Superuser Whitelist? Whats the difference and are they both needed?
Superuser Whitelist is the name of the apk that manages which app gets root access, su is the command line tool that actually performs the actions requested as root.
speedyls91 said:
Hi there
I installed this rom last night and by morning the phone was complaining about memory and had a bunch of processes force close.
Is there a mem leak or anything with this rom?
Click to expand...
Click to collapse
After last night and today of normal use, and leaving it on overnight, I haven't seen any behavior out of the ordinary.
I spent the last hour or so playing around with the donut update, but there are problems.
I downloaded the COC10 to DRC92 update zip and looked through it. Appears to be a new boot.img, a handful of files, and a bunch of binary patches. I made the following changes:
1. New kernel with the netfilter features enabled, but otherwise same sources and config.
2. Replaced the wlan.ko patch with the full file that goes with the new kernel since the one we're upgrading isn't the original and the patch won't apply.
3. Changed the update script to not try to patch the wlan.ko and skip over the version/key checks.
The update (applied manually via the recovery image) went fine, but there are problems with one of or both of WiFi Tether and Superuser. When attempting to start tethering there is just a general failure error but nothing bad in the log screen. In addition the Superuser app no longer honors the "always yes" setting. There are newer versions of both apps so I'll check those out later tonight/tomorrow.
Wow, doesn't sound good. Maybe leave out Wifi tether? I have been using a better su whitelist app, I think u may want to use it. I am using stock Donut at the moment, runs GREAT, so if I can help this would be great. What I am going to do is load my nandroid backup, clear out some garbage, and if you want I can send u my system.img and u can pick it apart appropriately to take a look at the SU I have along with the whitelist app. Perhaps that will solve the problems.
Wifi Tether is kinda the whole point so leaving it out isn't an option (or rather, having the user install it manually won't help). I think getting the new Superuser app working is a higher priority though. Unfortunately a system image of a stock ROM won't do any good. The problem is that the Superuser app ties in to the system in a way that requires them to be signed with the same key (or a shared key, something I haven't looked in to yet.)
Code:
I/PackageManager( 78): /system/app/Superuser.apk changed; collecting certs
E/PackageManager( 78): Package org.zenthought.android.su has no signatures that match those in shared user android.uid.system; ignoring!
My guess that the system is signed with T-Mobile's production key but Superuser is signed with a test key that is used on the fully custom builds. So it works fine with stock Android, Cyanogen, etc., but not here since I only changed the kernel, not the keys.
Obviously I can't re-sign Superuser.apk with T-Mobile's key so I have to re-sign the system with the test key. Unfortunately I have no idea 1) which file this is specifically, or 2) how to do it even if I knew.
Any suggestions are of course appreciated.
You mentioned that before. But even on the stock COC10 ROM, I pushed THAT su (from the last JF ROM,1.51) into /system/bin and then installed the apk into /data/app and it worked previously. If you wouldn't mind, plz send the new boot.img and I'll try flashing it through fastboot, as well as cm-recovery so I can use the root access adb to push the su into the stock donut. Which spl has fastboot enabled? I'll PM u my email.
Hi I'm new here and have a few questions. I downloaded some apps off the web but when they are updated I cannot update them using the market. Is there any way for me to update them or add them to the "My Downloads" list in the market? If I root my phone, but do not install a custom rom will I still get ota updates, be able to install market apps, and so on?
Details:
Phone: Nexus One (T-Mobile Version)
Android Version: 2.2 FroYo FRF50 (love it)
If you guys need baseband and kernel information let me know. Also, what it different in stock froyo vs cyanmod vs any other rom? Sorry if this is in the wrong place to post this and the length.
Hi there, as of right now all that I can point you towards for you apps would be an app called apktor that can be found in the market the rest you will have to figure out on your own. Or you could also just redownload these apps through the market...
From what I have read besically when you root your phone you give up any chance to be able to OTA update. BTW I have a Telus Milestone so I am not sure about the phone you have because it might be different but I think it would be a global rule of Rooting= No OTA... Although while being rooted you can install apps from the market.
About the custom roms you will have to do some reading untill the Milestone's boot gets cracked I won't have a chance to play around with any roms, I guess best advice would be read read read and read some more. And after you have done all that reading, choose a couple of roms that interest you try each one for atleast a day and find the one that you like. If there was a best rom, there wouldn't be such a wide variety of them...
~PsyCl0ne
Nope, even if your phone has root you can still update apps via the market. I know because I updated my apps via this way. 2 Rules apply though.
1) The apps that you downloaded off the web are freeware and are also on the market.
2) The apps that you downloaded off the web AREN'T warez. (I'd suspect that's what you're trying to do, but do correct me if i'm wrong)
It is highly unlikely that in following these 2 simple rules you still can't update via market.
Ok, since not everyone is using CM6 on an EVO I thought I'd share this outside that thread.
This should allow the Market to show the missing (protected) apps on Froyo. I've implemented it for the Gapps FRF91 Hdpi pack for now. Any HDPI Devices with deodexed Roms using this should work with this fix. It may work with other HDPI releases, but I've only tested it on FRF91 w/ CM6.
Wipe Market Data/Cache......Settings>>Applications>>Manage Apps>>ALL>>Market
Reboot Recovery
Wipe Cache
Wipe Dalvik Cache
Flash "MarketUpdateFroyoHdpi.zip"
Reboot
Accept Market Terms
On the off chance this borks your Market, just reflash your rom or the the Gapps pack.
If any other Froyo Markets have this problem, it shouldn't be too hard to implement the same fix.
Mirror: http://www.megaupload.com/?d=QIBIFHBM
If it doesn't work with your device/rom please specify both so that it will be easier to diagnose.
Big thanks to kallt_kaffe for leading me in the right direction.
It could be I've done something wrong, but this isn't working for me using Sapphire 0.7.0 (from droid-life) on my Droid (the original ). I've tried 2x (especially after finding where to do the dalvik cache wipe in clockwork) with installing it as an update.zip and just installing it as-is. I've been testing by trying to get comic strips back installed on my phone and app brain keeps telling me that mileage has an update though my phone doesn't agree.
I looks like that is using a different Google Apps version. I'll dl and try to patch it for you.
Here, give this a shot. Should work for all FRF84B Builds.
I don't have a device to test on, but this should do it.
does this work with g1 32b cm6
I'm not sure. I'd guess the g1 is an mdpi device though. If the mdpi market is locked (didn't think it was), I could apply the same fix. Also, is this for cdma or gsm?
Hi.
Great work!!!
I got it working with the MDPI version.
I just copied classes.dex from your fix to cyanogen's gapps-mdpi-FRF91-3.zip and I got Market unlocked.
If it's ok, can you share your secret/patch technique?
Did not appear to work for Acer Liquid Froyo. Still have problems accessing certain apps that I used in 2.1 ( AutoHTN Beta for example), APPBrain sees the app, but can not access it through the market.
Hi there
What about Android 2.1.1?
my phone is Motorola XT720, anything for that?
also, How do you "Flash" the application in recovery mode
any way i can do this using adb?
thanks
Aous
Galaxy S I9000 froyo 2.2
Hi,
I have the galaxy S, Froyo 2.2
Kernel version: 2.6.32.9
[email protected]_7_2#1306
Build Number: FROYO.JHJPD
I've tried to flash the both files that were posted here without any success,
and i can't find anything that will make the android market free.
Please help....
Question??
Do anyone know if this .apk works with Huawei IDEOS U8150-D??
(On custom rom based in Wind italy rom)
Today I became the owner of one of these babies, but I just found out that in China, I obviously get a chinese model, which does not include google apps, including the market, maps, navigator, etc. Now some of those I may be able to get via my phone, but ideally I would just like to have the market and the google apps suite installed on my device.
Can someone tell me how I can get this sorted? I would imagine this means rooting and flashing a new ROM? Is there another method? I like the whole layout and gui actually, so if I could get a stock US or UK ROM (assuming it includes google apps and market...), then that would serve me just fine...
Any suggestions?
You might be able to use the Google Apps from the Cyanogen page, I'm guessing you'll want the Tegra version shown towards the bottom of the page? http://wiki.cyanogenmod.com/index.php?title=Latest_Version
I'd download the package, extract and install each app one by one and check that they work with Honeycomb.
Google Apps contain the proprietary Google applications that come pre-installed with most android devices. Due to licensing restrictions, these apps cannot come pre-installed with CyanogenMod and must be installed separately. CyanogenMod does not require Google Apps to function properly, however, to take full advantage of the Android system, Google Apps are recommended.
These apps include Gmail, Maps, and the Android Market, just to name a few. More information can be found here: Google for Android
NOTE: You will need to flash the correct Google Apps for the type of device you have. Please refer to the chart to find out which Google Apps package is needed for the device.
Click to expand...
Click to collapse
I'll look into that. thanks.
Now I understand I would have to root my unit, which I have nor problems with doing. I'm using a Mac though. Which ROOT guide should I follow?
Also, if I decide to install a new ROM rather than flash the google app package from cyanogen, which one would be best to choose? I get the feeling there are a couple out there. I see a PRIME v1.2, I see a Ti-X V3, and I read something about blob v4/v5.
Any ideas what I should choose? I would like one that at least gives me the google apps (incl market and maps), but also has all the assets working (wifi, gps, both cameras, etc). It doesn't have to be a complete makeover, stock layout is fine for me.
Someone else will need to give advice on the rom's, I don't even have my Transformer yet. I didn't even consider the flashing aspect, I was just thinking that you could extract the apk's and install them, but that may not be the correct way. Perhaps root and a new rom will be the best option.
There's also a rom over at Modaco, another to consider perhaps.
http://android.modaco.com/category/509/asus-eee-pad-transformer-transformer-modaco-com/
right, so maybe some of the others can tell me the differences between the ROMs available? I think it may be a good idea to start a sticky that summarises what ROMs are available, and what guides to use for rooting and installing ROMs. All including links ofcourse...
Until then if someone could give a heads up on the ROMs available, as asked above, that would be great
ksporry said:
right, so maybe some of the others can tell me the differences between the ROMs available? I think it may be a good idea to start a sticky that summarises what ROMs are available, and what guides to use for rooting and installing ROMs. All including links ofcourse...
Until then if someone could give a heads up on the ROMs available, as asked above, that would be great
Click to expand...
Click to collapse
That would be too difficult to keep up with, besides if you read the ROM descriptions it will have the differences listed. Modaco and PRIME! have the latest update included, TI-X doesn't. Modaco has the stock honeycomb icons and PRIME! Asus icons.
Thanks for letting me know.
I found this one online as well: TF101_BLOB_ROOT
It seems to utilise adb to push the ROM onto the unit.
As for the other ones, they seem to utilise CWM. I assume I follow these instructions to get CWM installed?
http://android.modaco.com/content/a...od-recovery-for-the-asus-eee-pad-transformer/
Is that also the latest, or are there more recent versions of CWM for the TF101?
I‘ve got a Chinese model too,and i have the same problem.Actually,i just need Google Market...
Please keep this thread being updated,thanks!