So I'm currently running one of JesusFreke's Cupcake builds on a rooted G1, but my Maps and Market apps recently stopped working after installing the paid version of Power Manager. Wanting to rectify the problem (and eager to try out a Donut build anyway), I decided to download the latest CyanogenMod. Noticing that his download links didn't work, I looked through the forums and realized that he had pulled everything THE NIGHT BEFORE due to the C&D from Google. Great timing, right?
I'm excited to see that Cyanogen has continued his work with the release of CyanogenMod 4.1.999, but realize that he can no longer release any of the Google apps. His new installation instructions (http://forum.xda-developers.com/showthread.php?t=567610) require having working versions of all those Google Apps in the first place to back up. The process seems straight-forward for those lucky enough to have already had CyanogenMod 4.1.11.1 before it was pulled, but I am unfortunately in an entirely different boat.
Any suggestions on how to transition from a JF 1.5 build with broken Google apps to the latest CyanogenMod 1.6 build with working Google apps? If nothing else, any saints out there that happen to have CyanogenMod 4.1.11.1? Thanks for any advice any of you can give me to restore full functionality to my beloved G1.
Sean
cutlassdude70 at gmail.com
Did you actually read all of the instructions? You need to flash an HTC ROM and then 4.1.999. There is no requirement for 4.1.11.1.
Or get the all-in-one:
http://forum.xda-developers.com/showthread.php?t=569825
cutlassdude70 said:
So I'm currently running one of JesusFreke's Cupcake builds on a rooted G1, but my Maps and Market apps recently stopped working after installing the paid version of Power Manager. Wanting to rectify the problem (and eager to try out a Donut build anyway), I decided to download the latest CyanogenMod. Noticing that his download links didn't work, I looked through the forums and realized that he had pulled everything THE NIGHT BEFORE due to the C&D from Google. Great timing, right?
I'm excited to see that Cyanogen has continued his work with the release of CyanogenMod 4.1.999, but realize that he can no longer release any of the Google apps. His new installation instructions (http://forum.xda-developers.com/showthread.php?t=567610) require having working versions of all those Google Apps in the first place to back up. The process seems straight-forward for those lucky enough to have already had CyanogenMod 4.1.11.1 before it was pulled, but I am unfortunately in an entirely different boat.
Any suggestions on how to transition from a JF 1.5 build with broken Google apps to the latest CyanogenMod 1.6 build with working Google apps? If nothing else, any saints out there that happen to have CyanogenMod 4.1.11.1? Thanks for any advice any of you can give me to restore full functionality to my beloved G1.
Sean
cutlassdude70 at gmail.com
Click to expand...
Click to collapse
well i assume you know how to flash...
wipe ext
repair ext
facotry wipe
flash
and btw flash this instead
http://forum.xda-developers.com/showthread.php?t=569825
its cyanogen 4.1.999 but someone made it easy and complied everything in just one flash.(including google apps)
cyanogen himself cannot do this due to the C&D from google, but someone else can.. techniically still illegal, but no legal action has been taken.
Many thanks for the helpful replies! When I read Cyanogen's instructions and he mentioned the Android 1.6 Recovery Image, I didn't realize that it actually included the Google apps. Like I said, I'm a noob... I was able to follow the instructions to a T and am now running CM 4.1.999. Thanks again for the help!
While this may seem like a simple quick "YES" answer, I know there are some differences - because I've unlocked MANY MyTouch(es) - and never seen one NOT find the code to unlock.
This Fender would NOT unlock, that's how I ended up with it.
I'm a long time iPhone user, and want to dabble with Android - so this is my chance. I'd like to root it, and see what's the fuss. But want to make sure it's possible before I try.
Do you want to root it or unlock it? There's a difference between the two.
If you want to unlock it, just buy the unlock code or wait 3 months if you bought it with T-Mobile and they will give you the unlock code so you can use it with any provider that uses a sim card.
If you want to root it, there's two threads that I have seen that I have seen in the development forum that give you a step by step procedures.
Cursordroid has even released a Fender rom with root for when you decide to do this.
any chance of grabbing that music app from it? Looks sweet...
I want to root it, even tho I don't know what advantages that would have yet. I'm an iPhone guy ... have been for a couple years now, so I wanted to see what Android was about now.
What are the real advantages of rooting? (sorry - I know this is major noob stuff)
Everything to get you started about rooting and unlocking is a stickied thread in the "Android Development" sub-forum.
I would not judge Android 1.6 too harshly. Remember that it is not the latest build. For a fairer comparison against the iPhone OS 3, Nexus One's 2.1 or Droid's 2.01 is better.
Of course, you can always install a custom 2.1 ROM like Manup456's, but right now, all Eclair ROMs are a bit buggy, and the GUI is not as smooth as can be.
According to what i'm reading, the fender edition is new hardware - and there is no advantage to rooting yet anyway... because there are no compatible roms yet.
Araltd said:
According to what i'm reading, the fender edition is new hardware - and there is no advantage to rooting yet anyway... because there are no compatible roms yet.
Click to expand...
Click to collapse
check out http://forum.xda-developers.com/showthread.php?t=622530 fender edition root info and the only "fully" working rom
I read couples of threads and realize that if a CM mod is wanted, MS2 must have its bootloader unlock.
Since most work is done in /system partition, why do a bootloader modify is needed?
According to the update.zip, we can modify /system partition already, so why do we need bootloader unlock?
CyanogenMod needs its own kernel.
I guess that, since cyanogen is based on gingerbread now,
it runs with a more up-to-date kernel than the milestone's.
The locked bootloader and the efuse thing prevents updating the kernel.
It's possible that someone, using Cyanogen source, makes a backport running on our kernel, but I think it's a huge work...
However, the clever guys from freemymoto.com have created a hack that is capable of launching an other kernel after the legit one starts.
If salvation comes (Cyanogen alleluia ), it will certainly come from this project.
Actually, the hack works on DroidX, and Droid2. So it is 99.9% sure that with some work, it may run on milestone 2 as well.
So, to get Cyanogen work on MM2, we need :
- A very good developer, with android (of course !), linux kernel and kinit knowledge, able to port freemymoto's hack, and Cyanogen
- Hardware drivers for the Milestone (bluetooth, lan, gsm, 3g, touchscreen...)
If we find the golden dev, I personnally think that CyanogenMod could be out for milestone2 sooner than what most people think...
momus87 said:
CyanogenMod needs its own kernel.
I guess that, since cyanogen is based on gingerbread now,
it runs with a more up-to-date kernel than the milestone's.
The locked bootloader and the efuse thing prevents updating the kernel.
It's possible that someone, using Cyanogen source, makes a backport running on our kernel, but I think it's a huge work...
However, the clever guys from freemymoto.com have created a hack that is capable of launching an other kernel after the legit one starts.
If salvation comes (Cyanogen alleluia ), it will certainly come from this project.
Actually, the hack works on DroidX, and Droid2. So it is 99.9% sure that with some work, it may run on milestone 2 as well.
So, to get Cyanogen work on MM2, we need :
- A very good developer, with android (of course !), linux kernel and kinit knowledge, able to port freemymoto's hack, and Cyanogen
- Hardware drivers for the Milestone (bluetooth, lan, gsm, 3g, touchscreen...)
If we find the golden dev, I personnally think that CyanogenMod could be out for milestone2 sooner than what most people think...
Click to expand...
Click to collapse
I LOVE YOUR REPLY!
Well, this is the first reply to me in this forum.Ya...nobody reply me before...so bad..
Milestone has also a locked bootloader, but a CM7 port running on it. That is what makes me want to do something on my MS2.
I'm a C++ programmer, so I learn everything about this these days.
Thank you, really.
And I think I'd read all the freemymoto.com site RIGHT NOW~~
Well, if you think you can be the golden dev, you just made my day...
If you try this, I (and almost everybody here) will at least help providing the hardware drivers.
But the first step is to make the hack work on MM2...
Edit : For the milestone1, the bootloader security has been compromised using a leaked unofficial rom build,
which lead to custom kernels, without needing a hack like freemymoto's.
In fact, freemymoto's hack is based on a milestone1 project, which was abandoned after the rom leak.
It circumvents both bootloader lock and efuse by starting a second kernel after the first one.
(What I couldn't figure out is what happens of the first one... Still in memory? Still using some ressources?)
I read the site yesterday, however sadly, I don't have any experience about writing drivers of cell phone.
So I just sent a e-mail to them to ask if I can provide any help and what to do.
Hope I can help. I'll try my best.
For about the second kernel...I guess I have to read source to know what happened to them...
Anyway, thank you for your reply. At least I get a way to help^^
I didn't mean that we will have to write the drivers from scratch. But we will have to find them.
Hopefully, most of them are open-source. Wifi/bluetooth per example, is handled by a wl1271 chip. Drivers are available on texas instruments website...
You should get in touch with Pizzaroll, who is also trying to make the hack work on milestone2
It's really good news that there maybe a hack bootloader, i like my mm2 but it is really a pity that no much ROM.
liuyanghejerry...
Polish team try to broke bootloader with Boinc (many computers calculate 1 thing), maybe You and Yours friends can join to project?
In China lives maaaaany peoples, this can be speed up calculations
I don't think that distributed computing is the solution...
Even if the boinc project lets us find the signing key, we will have to do the same for the efuse thing.
The freemymoto's hack is a solution to circumvent both of these protections, and doesn't need any computing.
We only need someone to modify some parts of the code to make it work on Milestone2.
Tomszyn said:
liuyanghejerry...
Polish team try to broke bootloader with Boinc (many computers calculate 1 thing), maybe You and Yours friends can join to project?
In China lives maaaaany peoples, this can be speed up calculations
Click to expand...
Click to collapse
Currently I'm studying kexec method now, thanks to PizzaRoll and momus87's help^^
Well, in fact, I like to program and burn my brain. However, the Boinc method seems not really interesting...
Well Boinc is the best solution if you want to use bruteforce.
But even with a whole army of core i7, bruteforcing a 1024bits key is unthinkable actually...
Is this eFuse thing harder to break than the one used in iPhone? If it is then Mr Jobs should adopt a similar approach.
OTA_update_062_to_068_17_delta_image.pkg
Like OP says, version 068 is out now for E-Mobile users.
Judging from the size I believe it is still a 2.3.5 rom, the SPro still doesnt officially have ICS yet, but they're have it in testing for months now.
so basically not much different from other ROM?
So, I've got a Droid X I am planning on giving over to a friend of mine. Its too old and I'm too busy to bother much with selling it, plus he's a good guy and his current phone is like the saddest thing ever (a half broken ZTE piece of garbage held together with tape and running like Android 1.6). I haven't messed with the Droid X in over a year, and because of its locked bootloader, I know its somewhat complicated, with "2nd init" ROMs and the like.
At this point I'm not too sure what I'm looking at with it. I goofed around last night and got it somewhat up to date, with an AOKP-ICS ROM on it. It was already rooted and I have CWM on it as well, so its not a bad starting point.
The phone doesn't have any data / phone plan attached to it at all, which is usually OK in the short term since I can get it on WiFi, but now the WiFi just isn't working. I can SCAN for WiFi networks, but when attempting to join any, the phone immediately gets kicked back off the network.
Tested it on like 3 different networks. What's weird is it was working fine last night.
I'm showing a Baseband Version of BP_C_01.09.13P and a Kernel Version of 2.6.32.9 built on August 20th, 2011.
Build version says IMM761.
Mod Version says aokp_shadow_build-39,
The CWM I have installed on the phone is only 2.5.0.8! That seems really old, but again I don't wanna update it if it'll break things
I would like to update it as much as I can but I know I need to be careful so as to avoid breaking things.
Any advice is appreciated. I planned on putting the most functional / stable ICS ROM I could find onto it, which I would imagine is a matter of some debate. Is there some really good ROM I should look at, like a "final" build of CM9 or AOKP for this phone?
I would start off by SBFing back to .602, just to get a clean start and root.
Check that everything is working then flash Recovery Using Droid 2 Bootstrapper.
I don't believe there are many Ice Cream Sandwich ROMs that are fully working.
I highly recommend Vortex Reloaded (VXR), though. It is a fully working Gingerbread ROM with excellent battery life.
From there, you can update ClockworkMod Recovery to the latest version using ROM manager.
Sent from my Galaxy Nexus using Tapatalk 2