Related
I haven't seen an easy step by step guide for getting ANDROID 2.2 aka (Froyo) on the HTC HD2 .
Just download this file here: http://x.vu/HD2ANDROID
extract and run.
thats it!
ENJOY
The link is not working
Hi,
look here:
Development Thread > http://forum.xda-developers.com/showthread.php?t=719646
Android Builds > http://gamesquare.co.uk/
with friendly greet
starbase64
starbase64 said:
Hi,
look here:
Development Thread > http://forum.xda-developers.com/showthread.php?t=719646
Android Builds > http://gamesquare.co.uk/
with friendly greet
starbase64
Click to expand...
Click to collapse
ok,it works fine but i have some problems!I can make calls but i cant hear my caller neither he.I can also send sms.I have the last energy above with 2.12.50.02_2 radio.Now its ok!Also how can i see my contacts or to sync with what application?I am hearing very very slowly the other person?Do you know why?
noolis said:
ok,it works fine but i have some problems!I can make calls but i cant hear my caller neither he.I can also send sms.I have the last energy above with 2.12.50.02_2 radio.Now its ok!Also how can i see my contacts or to sync with what application?I am hearing very very slowly the other person?Do you know why?
Click to expand...
Click to collapse
Hi Noolis. Let me tell you that just like you, most people on the HD2 (including me) are waiting patiently for the Android OS to work as perfect as any other native Android Device. The guys on the main thread are working very hard for this to happen.
Just bookmark the following thread and visit it everyday. read the information on the 3rd post, and try their work in progress at your own risk. enjoy
this is the thread: http://forum.xda-developers.com/showthread.php?t=719646
Bookmark it, it'll make it easier for ya!!
i keep gettin a green screen then it freezs, i downloaded the zip to the sd card then i extract all the files then run the haret and it goes all the way to the drawling of the android and about a min. after it gets a green screen , what am i doing wrong please
i got that green screen as well but after a new restart it worked perfectly...
And before that i did have the error message "waiting for SD card" for a long time.
Even I dont know how I get Android running on my HD2...
Maybe just restart and retry, who knows!
Good luck
Android probably won't be working right for a number of months. Its ok though. The apps are nice but WinMo is still ok for apps (no calc on droid is as good as the panoramic one, Igo Primo > Igo Motonav, etc). By the time droid apps are leaps and bounds better, android should hopefully be working great on the hd2.
I say, just peek at it once in a while but don't really worry about it for another couple months.
Can somebody make a video for the new rom out?
How to make the Anroid OS working on the HD2 - Step-by-step instructions, FAQ, Tweaks
UPDATED! Read the informations & FAQs below...
For those who have got difficulty in making the ported Android builds working on their HD2, here is a step-by-step description!
Accessories:
- First thing you need to have is: The newest Jmz Android dual-boot program, which can be found HERE! The program must have installed in the Device memory!
- Another thing you have to have is a freshly-formatted SD Card (I recommend 2GB or bigger, but in theory the Android will work with a 1GB or less (the least is 512 MB) card...)
- A ported Android ROM (e.g. 2.1, Froyo, Desire ROM, usw.) You can find some working builds HERE! (Desire ROM, Froyos, Ubuntu builds)
Instructions:
- Firstly, install the latest Jmz dual-boot app (v3) into the Device memory!
- Download the Android build and copy it into the ROOT of your freshly-formatted memory card! Normally you just have to copy the files into your card, but in some cases you have to copy the whole folder though... (for more infos check out the build's README file, if it has got one)
- If it's needed, RENAME the "zharet" file to "haret" and the only txt file (Unluckily I don't know what its name is at the moment, I remeber to "README.txt" or sgh, but now I don't have any builds in which the name of these files are not these names) to "startup.txt"!
- Instert the card to your HD2!
- Restart your device!
- When the boot-screen appeares and starts, choose the "Boot Android" option!
- Wait for the Android build finally starts up (it takes 2-3 minutes or more, it depends on the ROM)
- Use and enjoy it!
If you still have problmes with the installing, send a PM or reply a comment!
I hope I could help with this.
[Please excuse me if I made any grammatical mistakes...]
IMPORTANT! You're really ought to make a full-system-backup before trying ANY of the ported builds out! (I recommend the SPB Backup, but of course, another backup progs are such suitable... either of them will do it!)
For example one of these builds blew my Sense 2.5 sky-high, and unluckily I didn't do a system-backup before I had tried the ported Froyo build out. As a result, I had to modify and customize my Sense again...
And according to my friend, due to an Android build, his 3G-data connection setup has also been laid down... so be careful, for all that that the most of these releases are "harmless"!
UPDATE (updated at 07/19/10):
For example I've just tired this build: "New Froyo build by dan1j3l V1" (description and DL link can be found here...), and it works very well on my HD2! It is fast, smooth enough, all of the wireless connections are working (just like BT, Wi-FI), and so on... worth a try!
IMPORTANT UPDATES AND FAQs
Q: Some people asked me how could the sound working without starting CLRCAD manually...
A: The Jmz dual-boot application automatically starts it, you needn't do it manually!
Q: Why is it not necessary to run "(z)haret"?
A: The answer is the same: the Jmz automatically does it...
If you have still have issues with the Android builds (e.g. with the backlight), try out these tweaks:
- To prevent your device from freezing when it tries to sleep, set the screen's timeout to 30 minutes in the ANDROID settings!
- Turn off "Automatically adjusted backlight" in the WinMo settings (or in the Sense 2.5 settings, makes no difference), and set both backlight option to 100%!
- UNCHECK the "Dim backlight if device is not used for XY minutes" option, and "Turn off device if it's not used for XY minutes" as well! (At the "On Battery Power" or "On External Power" section, it depends on what power-option you'd like to use your phone in...)
If your build doesn't show, or shows wrong the battery-meter (e.g. your battery is fully charged, but the build shows a "?" mark insted of the precentage or ask you to recharge it, etc.) (... and if it's not able to handle it), download this file and copy it into the root of your SDCard, and replace the original with it!
DOWNLOAD (FTP Mirror)
Unconfirmed tweaks:
- If you are able to run the builds in no way, try to format your SD Card in FAT32 filesys. It answered the problem for some people...
- In theories, HSPL is needed to run the ported Androids, but this assertion is unconfirmed at the moment!
not being funny but shouldn't you have posted this in general as android isn't exactly a theme is it ?
Not it's not a theme but the other half of the thread section is Apps. I take Android as as App when it's not a flashed OS.
just installed android using this guide, very helpful so thanks.
im using 2.2 Froyo build by dan1j3l and it seems to work very well. data connection seems slower then on WM, the battery meter doesnt work (and i cant charge the phone or connect it to the PC) when the phone goes into standby, it keeps the backlight and buttons on. also have the issues that many users are experiencing with calls. also when i reboot into windows mobile, the time and date reset!
just to help people out that maybe dont have much experience with this (such as my self) maybe you could add things such as radio ROM requirements, and perhaps a list of things that arnt working accross all ROMs (i think the call issue would be an example of this). you can find it through searching, but its nice to have it all in one place
if it helps i think you need radio 2.08 or above but not 2.12 (2.11 is the latest radio that works), as well as HSPL installed. the 'green screen' seems to be a big issue, but i just removed the battery and re-inserted it and it worked fine
matthewharmon102 said:
just installed android using this guide, very helpful so thanks.
im using 2.2 Froyo build by dan1j3l and it seems to work very well. data connection seems slower then on WM, the battery meter doesnt work (and i cant charge the phone or connect it to the PC) when the phone goes into standby, it keeps the backlight and buttons on. also have the issues that many users are experiencing with calls. also when i reboot into windows mobile, the time and date reset!
just to help people out that maybe dont have much experience with this (such as my self) maybe you could add things such as radio ROM requirements, and perhaps a list of things that arnt working accross all ROMs (i think the call issue would be an example of this). you can find it through searching, but its nice to have it all in one place
if it helps i think you need radio 2.08 or above but not 2.12 (2.11 is the latest radio that works), as well as HSPL installed. the 'green screen' seems to be a big issue, but i just removed the battery and re-inserted it and it worked fine
Click to expand...
Click to collapse
if you are using any of the android builds ie dans froyo or desire there are a couple of different zimages that you can replace in your android file. these will sort out the dimming isssue and have camera working, calls are perfect on my 2 different versions although 1 has accelerometer & no camera and the other is the opposite way round, battery is charging and indicators are working but i havent tried all the zimages to say what else they have up their sleeve so to say.
In regards to radio it needs to be a min of 2.08.50.* mine is 2.12 and calls are clear as a bell although browser can be a bit of hit & miss at times, it is getting better as different builds come out so well just have to be patient til a rom is eventually released.
i keep getting a green screen after the drawling of the android , it will drawl the android a couple times before the green screen pops up and freezes and i cant find anyone to help me out , ive read the directions but the last pass 24 hrs nothing but a green screen
Excellent guide Kromosome !
But I have the same issue as matthewharmon102.
In plus my HD2 it not responding after going to sleep ...
I'm confident that in the next release some of this issues will be solved.
Thank you guys
android not working
i have installed Jmz dual-boot app (v3) into the Device memory.....after restart boot menu appears ,i selected android it starts installing haret...after some time my screen went dull wit some lines and freezed.... Android is not working...am getting mad..plz help me out... :-(
android not working in my HD2
i have installed Jmz dual-boot app (v3) into the Device memory.....after restart boot menu appears ,i selected android it starts installing haret...after some time my screen went dull wit some lines and freezed.... Android is not working...am getting mad..plz help me out...
Hey everybody!
Some people asked me about the instructions, so I've modified my guide, and I wrote some important informations into it, and I integrated a FAQ section (that will probably increase), which is worth to be checked out!
I've also written down what you should do if your device freezes when you try to awake it, or if your screen goes dull after the Jmz starts installing the "haret", and tries to set the Android OS up!
If you have issues (especially backlight-issues), don't forget to check it out!
Hail Everybody!
As we know the Android developers are working hard to make it run smooth on our HD2.
There still bugs here and there but for sure we will get this great thing smooth like our WM OS soon!
Keep up the great work!
Yes, I definitely mean “wonderful” and “experts.” It is astonishing how much time, effort, and expertise the people who write the ROMs, etc., do for others, just to help us enjoy our cellphones. So, it is with no disrespect that I offer these comments on the instructions the experts give to us noobies to help us try to make our phones work better when they post “complete” instructions about how go to about this.
#1 – Odin.
There’s lots of advice to get Odin, but there are lots of Odin versions out there. Usually (generally in the computer world) what works when there’s a recommendation to get a program is to find the latest version. Even if a forum posting has a link to get a program, we figure that was the latest version available when the post was made and it still makes sense to get the currently latest version. That doesn’t work here. The latest Odin version I found was Odin 4.28. 4.28 totally fails to recognize my Samsung Droid Charge. But, if I use the ones referenced in the postings here (e.g. Odin3 v1.85) it recognizes my phone immediately. I understand the feeling that if we’re noobies we should just follow the directions exactly as written, but a little footnote about how this is different than everything else with computers would help.
I’m sure it isn’t true, but Odin seems to come from a mystical cloud location without any existence in our 3 dimensional universe. So, there seems to be no home website to explain that the latest version shouldn’t necessarily be used by everybody. And, there seems to be nobody on the forum who takes credit for upgrading Odin. Very mysterious.
Also – there’s at least three ways I’ve seen adamantly expressed as the proper way to connect a phone to Odin. #1 – simply attach the phone to the computer in the usual “download” mode, and Odin will find it.
#2 – Take out the phone battery for 5 seconds, replace it, then boot into recovery mode by holding down the up-volume, power, and home keys until “Samsung” flashes twice.
#3 – Take out the battery and don’t return it. Plug the phone into the computer, booting into recovery mode like #2.
As far as I can tell, #2 and #3 were needed for prior versions of Odin. Still, we noobies do Google this process, and it’s scary getting these conflicting directions about how to proceed. So, since you are obviously trying to make things less scary and confusing for us, you could mention this too.
Part of the problem is that there are various “Here’s how to replace your stock ROM with a better one” postings. Maybe each of them works perfectly, and there are many paths to enlightenment. Still, it’s worrisome for a noobie to try to figure out which of these paths to bet our phone on. (Of course, it’s also difficult for people trying to actually achieve spiritual enlightenment to decide on a path, so maybe this confusion is just an inevitable part of human experience.)
(cont. below)
#2 – CWM – Clock Work Mod.
I’m still confused about the need and timing of this one. Some sources say it’s entirely optional, just allowing other cool stuff done later. Others seem to say it’s important to install (flash through Odin) this before installing the new ROM. And, then there seem to be some ROMs that Odin can flash that do it all at the same time. And, then, there’s the issue of what order things are to be done in. If we just use Odin to flash a new Gingerbread ROM, can we, or should we, use Odin to flash in CWM?
As a noobie, I’m inclined to the “the less I mess with, the less chance I have of screwing everything up.” So, I think I’d like to skip the CWM while installing my new ROM, and wait to use CWM until I find some additional cool feature I can’t add without it.
#3 – ROM’s.
Where’s Consumer Reports when we need them? There are apparently various ROM’s we could use to improve our phones (e.g. Samsung Droid Charge). They are listed with somewhat cryptic explanations. Those explanations are probably perfectly explanatory for experts, but as a Noobie I don’t get a clear sense of direction from reading them. For example, Android 2.2 ROM’s (Froyo) are still listed, along with 2.3 (Gingerbread). Why would anybody want 2.2 if 2.3 is available? I assume there’s some reason I should be considering, but have no idea what it is. Among the 2.3’s, there’s also the “bloated” vs. “debloated” versions. Many of the unremovable (until rooted) stock apps seem to be both useless and resource drainers. But, I don’t know if I’m ready to give up all of them. And, the “debloated” versions are written by programmers, not people who want to devote their lives to writing up detailed commentaries about what is, and is not, debloated and why. Is there any reason not to just keep all the stock apps, and freeze or uninstall them with Titanium Backup later, as I identify the ones I do not want?
I feel anxious when I read somebody’s post about their newly released ROM, with lots of compliments, then comments that some feature now isn’t working. It’s hard enough to get answers about how to deal with the stock ROM.
I’m also confused about the difference between the “kernal” and the “ROM”. My impression is that “kernal” is which version of Android we use. “ROM” is broader, including extra’s like CDM and CDW, and Voodoo, etc. Or, not?
Part of the problem, obviously, is that the ROM writers have to do a different version for every [email protected]#$%^&*! phone that is made. Apparently even with the Samsung Galaxy family, there are enough differences that the ROM’s are customized for each one. (My prior phone was a Vibrant.) I am grateful that we have choices, and that these ROM’s are available, at all, but it would help to get a little more commentary (i.e. recommendations) about which ones are best for those of us just wanting a better ROM.
#4 – Voodoo. This is like the other issues. It seems like a great thing, to make the file system more efficient and do things like improve the sound system. But, it’s also confusing about when/if to install it in relation to the general ROM update.
So, maybe one of the wonderful experts will clarify these things here, or tweak their general instructions, for the benefit of noobies. Regardless, I again express my appreciation for all they’ve done for us.
There's a whole lot of "it depends" in this.
#1 - Odin may be up to 4.28, but Odin3 is newer than Odin. That's pretty self explanatory on its own.
#2 - You need CWM. Period. But, if you are flashing a full Odin ROM, it already comes with it, so you won't have to go into it unless you want to flash a theme or a new kernel. If you are installing a CWM ROM image, you need to flash CWM first.
#3 - Froyo (2.2) is still the only offical release for this phone. Gingerbread (2.3) is coming, but it's still in beta, and not officially released. The only GB releases we have are leaked and are not official final builds, therefore, they are not guaranteed to be of the quality or stability of Froyo, and, more importantly for us, there is no source available for the GB releases yet, so we don't have a lot of the cool tweaks available. So, it really does depend on what you are after.
#4 - All the current ROMs pretty much support it out of the box. If you are going with a stock ROM instead, you need a Voodoo enabled kernel to activate it. If you're ever in doubt of whether you have it and if it's enabled, install Voodoo Control and look at the lagfix section of the app.
I built a web page that has compiled all of the software you need to root, kernel update, ROM, and recover your Droid Charge with direct links to all of the software in one place.
http://www.toms-world.org/android
Plus it comes with very detailed instructions on how to do any one the activities mentioned above.
For those experts who do know how to do all of this, I'd like to see some collaboration and opinions on my directions. I'm only one person so I can't think of everything that could be added as far as a tutorial.
My idea is that a lot of us that know how to do this stuff should start a place where people can find the information they need for the Droid Charge all in one place without having to go from thread to thread, page to page, etc. Having it all in one place would benefit the Droid Charge community greatly.
Thanks for the replies.
Also, answering my own questions,
Not only is CWM necessary, but the remove battery 1st instructions, at:
http://forum.xda-developers.com/showpost.php?p=14692818&postcount=1
are correct. The other instructions I found that didn't include this stop didn't work -- Odin just sat there.
Also, at about page 11 of that xda thread, it says (correctly) that after ODIN says it's done, it's OK to unplug your phone, despite the large, brightly colored screen that says "Downloading... Do not turn off Target!!!"
Also, the kernal is different than the OS. So, first we find and install a rooted kernal (I guess this is like the most fundamental part of the phone's operating system), then pick a ROM (i.e. version of Android) to install.
Yes, now that you pointed it out, I agree it should have been obvious that ODIN3 is a later family version of ODIN, so no matter how high the version of ODIN we find, it's not going to be up the ODIN3 level. ...sigh
In the case of loading GummyCharged, you don't need to pick a kernel. The GummyCharged package contains an already rooted kernel (iMoseyOn's Lean Droid Charge Kernel) so basically if you load GummyCharged you have a kernel flashed along side it.
The only time you have to flash a new kernel is if you want to run a different kernel than the one contained in your ROM. Or if you want to update the kernel to a newer version of the kernel.
The kernel is the heart and soul of an operating system. It does all of the work in coordinating memory and process allocation. Think of it as a traffic cop.
trparky said:
In the case of loading GummyCharged, you don't need to pick a kernel...
Click to expand...
Click to collapse
Thanks. Your description of the kernel is much better than mine.
Another bit of noobie confusion:
The GummyCharged thread at
http://forum.xda-developers.com/showthread.php?t=1163123
says to install through CWM, after rooting. So, I already installed a new kernal, so I could have root.
As I understand better, now, I hope -- even with GummyCharged -- I had two choices, as there are two GummyCharged versions available. One is the two-step process (new kernal, then new OS). The other is to do both at the same time, through ODIN, which would have been easier.
I did install a new kernal, through CDW, seeing that path more clearly.
http://forum.xda-developers.com/showthread.php?t=1104634
Just a note that when my phone rebooted, Titanium Backup said I did not have root privileges. On a hunch, I just rebooted again, and that solved the problem. TB is happy, and so am I.
Then install a new OS through CWM.
Another thread that might have some useful information for you can be found here -> http://rootzwiki.com/showthread.php?4643-HOW-TO-quot-Clean-quot-install-GummyCharged-FE-2.0. Theres a lot there (maybe too much?) but if nothing else there are a number of useful links. I hope it helps!
Off topic: trparky I tried to send you a pm yesterday but my computer was acting up - not sure if you got it or not.
Thanks for all the help. Everything seems to be fine. This is just sort of a summary & wind-up post of another noobie's experience and successful quest for cellphone happiness.
First, there seem to be three ways to do scary things to the e-guts of my cellphone.
#1 -- Odin3 (a.k.a. Odin, but Odin3 v.x is the one that works for Samsung/Verizon Droid Charge [SDC]). Odin3 runs on the computer, with the cellphone properly tethered to the computer, and can insert stuff, like CWM. So, mostly the first step is to use Odin3 to insert CWM (superseding the stock recovery program). From some post it seemed it's possible to skip this step and do everything from Odin3, but that post also said that approach wasn't for noobies, even though it seemed easier to me. Odin3 is an elegant program, but you have to find somebody's Betty Crocker instructions for how to use it.
#2 -- Use the ordinary SDC file tethering to put .zip files onto the SDCard, because CWM uses those to install things like kernels and OS's (versions of Android). Sometimes the kernel and OS come bundled. Sometimes not. I ended up flashing a kernel first, then an OS with a bundled kernel, and everything seems fine.
#3 -- there's some other program, starting with an "H" that can also work like Odin, I think, but I ended up anxious enough figuring out #1 and #2, so didn't want to learn a whole other approach that might, or might not, somehow have been better, so I ignored this approach.
After I had my new root kernel, I used Titanium backup to freeze the bloatware. At that point I sort of chickened/burned out because there were too many choices of which version of Android to flash. I decided I didn't really need any of them, since my phone would be efficient enough without the bloatware running to give me everything I needed. What originally got me to start flashing my Android phone was when I would (repeatedly) receive calls on my old Samsung Vibrant, but the phone was so busy doing some [email protected]#$%^&*! thing that it wouldn't let me answer the call. With a more advanced phone (my new SDC), and frozen bloatware, I was confident I wouldn't have that problem, so just stopped there ... ... ... until I was horrified to receive another call which my SDC told me about but was too busy doing some [email protected]#$%^&*! thing that it wouldn't let me answer the call. OMG, it's happening again! At that point the choice of which version of Android to use because less important, because I was sure that nobody's custom Android would let that happen. So, I went with the GummyCharged Froyo [GummyChargedFE_2.0.zip]. At this point, I'd worked with CWM enough that it was all easy. Downloaded the file, copied it to my SDCard, booted to recovery, erased files & Dalvik cache, flashed the GummyCharged, and restarted. Lovely.
One nice aspect I'd not anticipated was that somebody has thoughtfully improved the process, so immediately my phone started re-downloading and installing the apps I had before. It's kind of a hassle to have to re-do all that manually, so special chops/thanks to the GummyCharged team for that feature. My phone works fine. I've tried, and happily failed, to make it too busy to let me answer a call.
What's left? I have to make donations to the Gummycharged people, whose software I now use, and the person who tweaked CWM that I use. It feels like I should make a donation to the Odin3 trolls, but haven't seem a request for that, nor have any who they are or how to do that.
I'll also be keeping my eye on the developing Gingerbread kernels, occasionally, until it looks like those are so mature that there's no reason to not confidently install & flash (through Odin or CWM, both of which I not feel fairly comfortable with) the upgrade.
On the off chance that anybody's still reading this, I do have one last question:
Can I delete the GummyCharged .zip file from my SDCard. I remember, back when I flashed my Vibrant, that I later deleted a seemingly useless .zip file called "update.zip", and that caused a problem. File isn't huge, so except for my mild OCD, no big problem in just leaving it there.
Thanks, again, to the wonderful experts who've helped me and so many others through this.
angelsix said:
...
#3 -- there's some other program, starting with an "H" that can also work like Odin, I think, but I ended up anxious enough figuring out #1 and #2, so didn't want to learn a whole other approach that might, or might not, somehow have been better, so I ignored this approach.
Click to expand...
Click to collapse
I believe the program is called Heimdall - this is more often associated with Mac users, as ODIN is a Windows program.
angelsix said:
...
One nice aspect I'd not anticipated was that somebody has thoughtfully improved the process, so immediately my phone started re-downloading and installing the apps I had before.
Click to expand...
Click to collapse
I'm not positive, but I believe this to be more of a Google thing. Whatever apps you've downloaded from the market are linked to the google account used on the phone, so once you sign back in on your phone post-flash, those apps (whatever ended up being stored as downloaded-by-you by google at least) start getting pushed to your phone.
angelsix said:
...
On the off chance that anybody's still reading this, I do have one last question:
Can I delete the GummyCharged .zip file from my SDCard. I remember, back when I flashed my Vibrant, that I later deleted a seemingly useless .zip file called "update.zip", and that caused a problem. File isn't huge, so except for my mild OCD, no big problem in just leaving it there.
Click to expand...
Click to collapse
You can delete the file, but this is essentially the installer file - if you ever have need to re-install it later on, you will need that (or a more up-to-date one if such a thing exists) file again. I tend to be an electronic pack rat myself, but you can delete the file from your SD card without any immediate adverse effects. If I remember right, the "update.zip" of old was associated with some earlier variants of CWM - without it you would not be able to get to the "custom" recovery (i.e. CWM) to flash things. Seems like such things are no longer necessary anymore, at least not with the recent versions.
dwitherell said:
I'm not positive, but I believe this to be more of a Google thing. Whatever apps you've downloaded from the market are linked to the google account used on the phone, so once you sign back in on your phone post-flash, those apps (whatever ended up being stored as downloaded-by-you by google at least) start getting pushed to your phone.
Click to expand...
Click to collapse
That is correct, and it's something that I strongly dislike, as I have installed plenty of things from the Market that I have since uninstalled and no desire to restore. If you skip account setup when you are first setting up the phone, and then manually go into Settings->Accounts & Sync, it will skip this, which is yet another reason to like aftermarket roms, as the stock roms will not allow you to get to the launcher until you set up a Google Account.
Hello all and especially to any that can help,
I recently purchased a Droid X from a co-worker who had upgraded to a Droid Razr (carrier Verizon, Android 2.3.4, model MB810). I found out later that the phone had already received the .621 OTA update and was unrootable (someone may have found a method by now).
I did 2 days of researching before I attempted any changes in the phone and found that although a reversal of the .621 update was impossible (again the info on this may have changed), the Milestone X's sbf could be used. I downloaded the flasher program and 2 sbf's for the Milestone X, tried both and liked the larger one better. The phone now reads as a Milestone X (carrier Alltel, Android 2.3.5, model MB809).
The question I have is "what is the best custom ROM to use with this device"?
Cares and Don't Cares:
1) Carrier: I won't be placing this device on any carrier's network - Wifi and Bluetooth are good enough for me. I will be using a hack I found on these forums to be turning off the carrier radio later. This also means I won't be needing this device to have any phone functionality. This is basically going to be used as a mini-tablet replacing my 3 Craig tablets (#1 broke, #2 has damage to a daughter board - I think a chip burned out, #3 is refusing to reliably boot, made #1.5 from parts of #1 and #2).
2) Bluetooth keyboard connectability: The only program that hints at this is Bluekeyboard JP and it mainly uses Apple products. I have a Freedom i-Connex keyboard I would like to use and maybe others in the future.
3) Multiple mounting points: Currently this device only offers 2 points, even after rooting: a fake CD-Rom, and the sd-card. If there is a way to create a folder/directory and make it USB accessible, I would love to know how. I use my portable devices as reference file storage.
4) Reduced bloatware: I won't be needed phone software (see #1) and I don't need the prepackaged games nor social software (they cause more trouble then they are worth to me - namely see the news about TWD - texting while driving - accidents, social website enabled stalking, and other physical and informational damage). Also, other than program(s) to backup the installed ROM/RAM (Nandroid?), no prepackaged backup program (seen that most people prepack Titanium, I like Astro file manager better).
5) I know this one may be next to impossible to get; WINE: emulating a whole OS just for 1 program is wasteful. I would love to have a mobile copy of "DC Creator" (character and gadget builder) from Mike Love for DC Heroes and Blood of Heroes (Mayfair Exponential Gaming System program, I updated the dc_data.dat file to include new powers from Blood of Heroes and the Web, file is now over 70k).
6) ICS: I know that people are working on this one for this device, several problems to go (like the camera), and a thanks goes to them for even attempting this.
During my research, CyanogenMod 7 and 9 kept coming up. If I read my info right, these are not actual OS updates but instead mods that give some next gen functionality to the current roms (Froyo gets Gingerbread mods, Gingerbread gets Honeycomb/Ice Cream Sandwich mods). I haven't tried either yet so I don't know if any of these would help me or load my system down more.
My thanks to the whole device hacking community for enabling us to get the most out of our devices (whether it be android, iOS, PSP, PS2, ..... you get the point).
Sorry for the long post but I wanted to get as much info to whoever could help as possible.
i need ur help
dear i need ur help i have samsung nexus s i have install miui rom but after installation the mobile signal is not working plz tell me what can i do 'i am waitting for ur prompt respose
thanks
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Miui or cyanogenmod9
this roms are perfect
Thank you for the information. I'll dl both next time I'm near a high-speed connection (dial up at home sucks, thank you CenturyLink for avoiding my area for yet another year).
Hmm, MIUI appears to be only useable if you are upgrading from Froyo - I'm Gingerbread and I don't know if it will revert back to Froyo - remember this phone has already received the infamous .621 OTA update. It was probably a fluke I found that the Alltel SBF worked. So MIUI appears to be out of the question.
The Cyanogenmod 9 links I found appear to be dead when I checked from work (blocked?), but I also found no information on requirements. I see that you need both that and the Gapps files to use this.
Has anyone else gone the path that I have to SBF and root my device (Verizon Droid X Gingerbread 2.3.4 -> SBF -> Alltel Milestone X Gingerbread 2.3.5, rooted) and applied a custom rom afterwards?
Anyone have complete instructions on how to install CM9 for the Droid/Milestone X ->still a noob here<- that has taken the same path as me (and any further information on getting the camera working, last update looks to have been in February)?
Thanks again for any help.
Anyone know of a stable download link for Cyanogenmod 9?
All links I have found are either dead (404), 'server down for maintenance', or access denied (403).
Hi Folks.
Just picked up a very nice old EVO Shift and would like to root it.
Certain problems have arisen immediately and I hope someone can direct me in how to solve them, please.
To start with - right this minute all I have is an old XP PC, so the tools for newer OSes will not work for me right now.
I have searched here and in general extensively and found many possible answers - but cannot get anything to succeed yet.
The HTC Dev site allowed me to join, but instead of getting to the bootloader unlocking area it just demands that I log in over and over - so I cannot do it that way.
(I tried maybe 5 different browsers, clearing cookies, cache & all that - same results.)
Kingo has a specific tool for this - but apparently it just uses the HTC Dev site in the background and it fails as well.
The htcsupertoolv3 opens - but it also depends upon that site and also fails.
Many sites recommend downgrading the phone from 2.3.4 to 2.2 - but their files were uploaded aeons ago and I have not been able to find a complete solution anyplace.
The phone connects fine to my PC, I have the drivers & ADB & I've been working at this most of the day today without success.
Right now seems like a good time to give myself and the phone a rest and to resume tomorrow when I get some time...
Any help will be hugely appreciated.
Thanks
vtsnaab said:
Hi Folks.
Just picked up a very nice old EVO Shift and would like to root it.
Certain problems have arisen immediately and I hope someone can direct me in how to solve them, please.
To start with - right this minute all I have is an old XP PC, so the tools for newer OSes will not work for me right now.
I have searched here and in general extensively and found many possible answers - but cannot get anything to succeed yet.
The HTC Dev site allowed me to join, but instead of getting to the bootloader unlocking area it just demands that I log in over and over - so I cannot do it that way.
(I tried maybe 5 different browsers, clearing cookies, cache & all that - same results.)
Kingo has a specific tool for this - but apparently it just uses the HTC Dev site in the background and it fails as well.
The htcsupertoolv3 opens - but it also depends upon that site and also fails.
Many sites recommend downgrading the phone from 2.3.4 to 2.2 - but their files were uploaded aeons ago and I have not been able to find a complete solution anyplace.
The phone connects fine to my PC, I have the drivers & ADB & I've been working at this most of the day today without success.
Right now seems like a good time to give myself and the phone a rest and to resume tomorrow when I get some time...
Any help will be hugely appreciated.
Thanks
Click to expand...
Click to collapse
Wow.
Is there no hope for this very nice older phone ??
As of now I have managed to find all but the ShiftRR tool and hope someone here still has that & will help me.
Thanks.
Can you test this Tap,Tap port on your Galaxy A32-5G please?
It's not my app. It's an app that is posted on XDA at that forum page on April 6th, 2022.
Let me know if it works for you as it might save a lot of people time & effort in that it sounds like a great idea for an app to backport Android 12 features.
EDIT: I was asked to further explain what it does!
Note: That means nobody clicks on links! Sigh.
As far as I can tell from the XDA thread in that first link (that nobody ever seems to click on, sadly) the app just adds the Android 12 tap-on-the-back feature to earlier Androids.
Nothing more than that (as far as I know).
1. Side load Tap,Tap version 1.3 from Github.
2. Walk through the setup steps
3. Let us know if the Tap,Tap port works on your A32-5G please
a. Please let me know WHICH Galaxy A32-5G works (mine is the SM-A326U).
b. Also let me know which settings work, for example:
Device Size = for example, "Legacy 160mm [6.3in] (Large)"
Sensitivity = for example, "1st Very High" indent
c. Let me know what application you launched with the double tap on the back
(and whether or not you removed the case to get it to work)
Again, I repeat, this isn't my app. It's an app on XDA developers. I'm just a user. Like you. I tested it and it seems to work for others (according to the XDA thread) but it didn't work for me.
It could be me. It could be my phone. It could be anything. That's why I'm asking for others to add value. It's not any more complicated than that.
I tried it on mine, I also have the SM-A326U and it didn't work. I tried the same sensitivity settings and the device size settings. It might have something to do with the fact that I've heavily modified my phone(debloated, disabled, etc) but I was unable to get it to work.
platless said:
I tried it on mine, I also have the SM-A326U and it didn't work. I tried the same sensitivity settings and the device size settings. It might have something to do with the fact that I've heavily modified my phone(debloated, disabled, etc) but I was unable to get it to work.
Click to expand...
Click to collapse
Hi platless,
THANK YOU for responding as I spent a lot of time testing this and documenting it and asking on the original thread and even asking the developer (who, I know, is busy developing), and I just couldn't get it to work on Android 11 either.
I didn't know if it was just the way my phone was set up, or, more likely, whether it was due to the specific phone model (the developer told me he can't test every model and I easily concur with him on that).
Like you, I've debloated my phone, and mine is also heavily modified (I use no Google apps nor is the phone set up with a Google account for example), so we're both kind of similar that way.
What I did NOT know (until you posted) was whether anyone else on the SAME MODEL as I was on got it to work, which is an IMPORTANT datapoint which you just provided.
Thanks. I'll give up on trying to get it to work for two reasons:
a. You confirmed it won't likely work on ANY SM-A326U, and,
b. I moved the SM-A326U to Android 12 which has the feature!
The only thing left, I guess, to help others, is for those with the SM-A326U who are still on Android 11 and who have NOT heavily modified their SM-A326U to test it; but at this point, I will give up on trying to get it to work for the two reasons stated above.
Thanks for being kind hearted though, and testing it out for the team!
GalaxyA325G said:
Hi platless,
THANK YOU for responding as I spent a lot of time testing this and documenting it and asking on the original thread and even asking the developer (who, I know, is busy developing), and I just couldn't get it to work on Android 11 either.
I didn't know if it was just the way my phone was set up, or, more likely, whether it was due to the specific phone model (the developer told me he can't test every model and I easily concur with him on that).
Like you, I've debloated my phone, and mine is also heavily modified (I use no Google apps nor is the phone set up with a Google account for example), so we're both kind of similar that way.
What I did NOT know (until you posted) was whether anyone else on the SAME MODEL as I was on got it to work, which is an IMPORTANT datapoint which you just provided.
Thanks. I'll give up on trying to get it to work for two reasons:
a. You confirmed it won't likely work on ANY SM-A326U, and,
b. I moved the SM-A326U to Android 12 which has the feature!
The only thing left, I guess, to help others, is for those with the SM-A326U who are still on Android 11 and who have NOT heavily modified their SM-A326U to test it; but at this point, I will give up on trying to get it to work for the two reasons stated above.
Thanks for being kind hearted though, and testing it out for the team!
Click to expand...
Click to collapse
I forgot to mention I'm also on Android 12. I was unable to get it to work, how were you able to get it to work on Android 12? And no problem, I'm always down to test stuff!