Related
Android 2.0 (Eclair) for CDMA Diamond (DIAM500)
Instructions
Put the files from my zip file (zImage, modules, startup.txt) in the root of your Internal Storage
From this xda post, download the latest XDANDROID build.
From the XDANDROID 7z file, extract system.sqsh, haret.exe, initrd.gz, calibration, conf/, media/, and (optionally) AndroidApps/ into the root of your Internal Storage
From stinebd's rootfs autobuild site, download the latest rootfs, rename it to rootfs.img, and put it in the root of your Internal Storage.
If you are updating from an earlier version of Android or just want to clear your settings, you can delete data.img from the root of Internal Storage.
Run haret.exe and boot
Notes
Touchscreen calibration values are stored in the ts-calibration file in the root of Internal Storage. To re-calibrate, delete the file and restart.
The "end call" button takes the phone in and out of sleep.
Android's "Menu" button is mapped to the top-left/Home button. The 5-way pad and the scroll ring both work.
Android's "Home" button is mapped to the power button on top of the phone.
Wi-Fi is working, although Linux sometimes crashes when WiFi is turned off.
If you want to try Android 1.6: From this Android build, extract haret.exe, initrd.gz, system.sqsh, calibration, calibration_diamond, and the AndroidApps/, conf/ and media/ directories into the root of your Internal Storage.
ChangeLog
3-23-2010:
Touchscreen double-tap issue should be gone, big thanks to eval- and especially bzo
HTC wired headset and 3.5mm headphones both work
3-8-2010:
Hardware 3D is re-enabled (accidentally disabled it)
3-6-2010 Update:
Bluetooth now works, big thanks to bzo
Touchscreen should be improved
Power-off now resets the phone instead of crashing
2-25-2010 Update:
When WiFi is turned off the phone shouldn't crash
2-19-2010 Update:
Power collapse now works, so power consumption should be much lower when the screen is turned off.
WiFi should work, as long as you use a new rootfs from stinebd's autobuild site. If you tried to use WiFi in the last ~2 weeks and it failed, WiFi still may not work with this new rootfs and kernel. See this post for solutions.
2-17-2010 Update:
Microphone works without having to make a call in WinMo
WiFi still isn't working, but I'll post a patched rootfs soon to fix it
2-10-2010 Update:
Hardware 3D acceleration is working under Eclair
Brought in makkonen's fixes for battery status--they're rough, but better than being stuck at 5% all the time
WiFi is not working at the moment, but I'll lean on the XDANDROID guys to get my fix in.
2-3-2010 Update:
Linux is now using much more of the phone's memory: 180MB vs. 103MB, thanks to some patches from the Hero and Droid Eris kernel source.
Touchscreen calibration is now supported with the Feb. 2 XDANDROID build, thanks to makkonen and phh.
1-27-2010 Update:
Stability should be much improved
A new touchscreen driver is included that is a big improvement over the old one, thanks to makkonen and phh. A calibration utility is coming soon. Until then, calibration is stored at the bottom of conf/eclair.user.conf, and you can put your WinMo calibration in there with this guide.
The USB product ID has been changed in the hope that ADB will work on Windows. Try it out and post back if it works.
1-22-2010 Update:
The power button (on top of the phone) is now mapped to Home, and holding it down will show apps running in the background
Sound, data, and WiFi should all be working
1-11-2010 Update:
Tested and working with Eclair
Deep sleep should be working better (use less power)
12-26-2009 Update:
Kernel improvements:
The speaker and earpiece now work (but not the microphone)
Screen backlight control works
Rootfs improvements:
Thanks to makkonen's RIL fix, cell data works in Android without having to end the connection in WinMo first
I made a change to /init that might help mjb94, hackman238 and others that have partitioned internal storage. If you were getting a "cannot mount" error on boot, let me know if this fixes it.
12-16-2009 Post
We do have a Google wave for Android--right now it's a cross between a wiki-status-report and chat room. I'm not sure how to give a link to a wave, but it's open to everyone and called "Android on HTC Windows Mobile Phones (Diamond, Raphael, Blackstone, Rhodium, Topaz)". If anyone wants a wave invite, PM me and I have a few to give out.
Enjoy Android, and if you need help or have questions, PM me or post here
Donations are greatly appreciated , or help finding an engineering job in San Diego!
thanks mr. pippy for all your work. my wife is happy that once the microphone works i wont want to buy a new phone!
wow
you are definately making progress on the diamonds android
Is there any chance of the mic working anytime soon? I know this isn't an fast paced process but I'm just so sick of wm.
Can someone invite me to Google Wave please?
my gmail account is mike.cgy
bdusmc said:
Can someone invite me to Google Wave please?
my gmail account is mike.cgy
Click to expand...
Click to collapse
I just sent you one.
Awesome - I got it... Thanks a lot!
Wow, you're getting a lot done in a short period of time, Thanks!
Will donate as soon as I can!
the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"
For the latest version, it will boot for me, but as soon as I have a 3g connection it seems to reboot any time I touch anything.
Boots up fine
Latest build boots up and seems to run fine for several hours but after playing with it, it seems to get more and more unstable. I went 10 hours with it plugged in sleeping and then unplugged it and used it moderately for about 3 hours before it crashed. Now it's crashed 3 times within minutes of each other. Good stuff though, can't wait until it's stable enough to use full time. Diamond has plenty of nuts to run it pretty good. Sure would be nice to have a dual boot phone. No reason to upgrade and get the best of both worlds...
giovesoft said:
the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"
Click to expand...
Click to collapse
I get the same error on my Raph500. I tried from the micro SD card and from the root of the fs.
giovesoft said:
the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"
Click to expand...
Click to collapse
rothgar said:
I get the same error on my Raph500. I tried from the micro SD card and from the root of the fs.
Click to expand...
Click to collapse
Sorry, my kernels are only tested on DIAM500. The RAPH500 mtype (set in startup.txt) is 2182, you should have better luck with that. Also, this thread is for RAPH800 but there may be some RAPH500 people there.
mr pippy i still get the same error as in your other post with the failed to mount sd and the 2 partions, i tried reformatting
mjb94 said:
mr pippy i still get the same error as in your other post with the failed to mount sd and the 2 partions, i tried reformatting
Click to expand...
Click to collapse
Did you reformat or repartition? Would you happen to be one of those people who has a partitioned card? Basically, I think the layout of your MC can have as many partitions as you want on it as long as mmcblkp1 (the first partition) is a fat32 partition with the needed files on it. There's also a little info on this problem on the wiki, lavender.t posted a solution that works 100% of the time if you're able to enter keystrokes.
Willis111 said:
Did you reformat or repartition? Would you happen to be one of those people who has a partitioned card? Basically, I think the layout of your MC can have as many partitions as you want on it as long as mmcblkp1 (the first partition) is a fat32 partition with the needed files on it. There's also a little info on this problem on the wiki, lavender.t posted a solution that works 100% of the time if you're able to enter keystrokes.
Click to expand...
Click to collapse
I simply in disk utility clicked on restore and erased the disk restoring with ms-dos fat
is there another way to do this. i have access to linux and osx not windows
it only shows i have one partition so idk!
no dice. heres what i have done
ok i restore the disk in to ms-dos fat
no dice
i repartiton with a scheme of one partition
no dice
i change the partiton table no dice
i tried lavaders thing but i couldn't get the keyboard to come up
there is a new android version called eclair 2.0 here http://forum.xda-developers.com/showthread.php?t=601751 .
i also formatted from the phone
Possible fix for microphone
I haven't tested this yet, but blast3r in irc tested a workaround for the microphone this morning and said it worked:
In WinMo, start a voice call and leave it connected while you open HaRET and boot into Linux. In Android, the microphone should now work for voice calls.
MrPippy said:
I haven't tested this yet, but blast3r in irc tested a workaround for the microphone this morning and said it worked:
In WinMo, start a voice call and leave it connected while you open HaRET and boot into Linux. In Android, the microphone should now work for voice calls.
Click to expand...
Click to collapse
Yep, confirmed for me. Made a phone call with android and could talk just fine. Probably can just call voice mail with win mobile and launch HaRET. Trying that right now.
I could use some help getting my bluetooth to work. I've tried several of the CM7 nightlys, their RC4, phiremod v5, v5.2, and v5.3. They all flash just fine, and work great, except when I try to turn on the bluetooth. When I go to the settings and try to turn it on, it just spends 30 seconds trying then goes back to having it off. I've flashed and re-flashed the system, and have read everything I can find, but don't know what I'm doing wrong.
My steps.
1) Downloaded 8gb_clockwork-0.1-ext4.tar.gz
2) Burned the contained img file to an sd card (used the dd command)
3) Copied system image to sd card (ie phiremod-nook-V5.3.zip)
4) Unmounted sd card and inserted it into my rooted nook
5) Turned nook on
6) Formated /system /data and /cashe
7) installed from sd card, selecting zipped image (ie phiremod-nook-V5.3.zip)
8) when complete, unmounted sd card
9) removed sd card
10) rebooted
11) it always fails to boot the first time, but works find after a restart.
Can anybody see what I'm doing wrong?
What works for me is pressing 'fix permissions' in rom manager then reboot and badabing.
Sent via Tehduck Uberdistro Encore RC4 n.33/Tapatalk Pro
luciferii said:
What works for me is pressing 'fix permissions' in rom manager then reboot and badabing.
Sent via Tehduck Uberdistro Encore RC4 n.33/Tapatalk Pro
Click to expand...
Click to collapse
That did the trick!, thank you very much luciferii
Just a note as I try to avoid "Fix Permissions" when possible-
Anyone with this problem MAY be able to turn bluetooth on by rebooting and enabling it as quickly as possible.
This seems to work most of the time for most people. Not always..
If not, fix permissions and a reboot does seem to take care of it the rest of the time.
rogerdugans said:
Just a note as I try to avoid "Fix Permissions" when possible-
Anyone with this problem MAY be able to turn bluetooth on by rebooting and enabling it as quickly as possible.
This seems to work most of the time for most people. Not always..
If not, fix permissions and a reboot does seem to take care of it the rest of the time.
Click to expand...
Click to collapse
Why would you avoid fix permissions? It just sets things to sane values.
As for me, the fix I heard and what worked for me was to turn off Wifi, Power off, power back on, turn on Bluetooth and let it init, then turn on Wifi. Now both will turn on.
khaytsus said:
Why would you avoid fix permissions? It just sets things to sane values.
Click to expand...
Click to collapse
Two reasons:
#1) While I am not afraid to mess with root access or abilities I also try to avoid doing so whenever I can. If I don't NEED to, I don't. Same way I work on my linux computers. And if I have done nothing to mess perms up they SHOULD be ok.
#2) I think the simplest fix is best, every time. (As long as it actually FIXES the problem, of course.)
If all that is actually NEEDED is a reboot and turning on bluetooth quickly, why do anything else?
Hey there
I'd like to sell my Touchpad, and wanted to get it clean and updated for the new user
Few weeks ago I updated to CM 10.2 and used tailor
system - 600mb
cache - 200mb
media - 400mb
data - 26gb
Now I booted into webos, wanted to upgrade the catalog app and others, changed date to Jan 2013,but it seems no memory left, now if I press install catalog, or the update, the TP reboots. Under device I see 0.3Gb available
How do I give Webos more space ? Is it the media partition ? Or not at all ? I'll try to resize it but tailor is having trouble to start
Also what are the Resets Options I can use after all is updated ?
Erase USB drive ? Or should I go first with full erase ? (apps install and data+usb drives etc) then update ?
Won't it mess with android install ?
Thanks for help !
Edit : Tailor : after a while, I get Service Error (userId) org.webosinternals.tailor.nod is not running, hmm, any idea to fix this ?
Reinstalled, retrying
I ran ACMEUninstaller, and tried webos doctor, 3.0.5, 3.0.4, 3.0.0, but everytime, it gets disconnected at 4%, using original cable, also tried with samsung's one
Any idea ?
Edit : I deleted media partition from tailor, then remade it, but it said fail, then I did an ext3 one, and the media appeared, but it said system was corrupted and I should try to repair, tried several time, no success, so I plug the tablet, and windows asked to format the partition, not sure If I chose ntfs or fat32, the default one, don't know if webos needs a specific one to work.
Rebooting the tablet now, taking some time but it's reinstalling some apps I think.
I'll retry doctor after that, if partition is here and not broken as before it may work, I hope => It doesn't.
Soo, I did full reset from webos, dunno if that's me or hp, but took me 10m to log in my account... Now restoring some stuff, but it often looses connectivity to hp. Hell !
Ps2004 said:
Hey there
I'd like to sell my Touchpad, and wanted to get it clean and updated for the new user
Few weeks ago I updated to CM 10.2 and used tailor
system - 600mb
cache - 200mb
media - 400mb
data - 26gb
Now I booted into webos, wanted to upgrade the catalog app and others, changed date to Jan 2013,but it seems no memory left, now if I press install catalog, or the update, the TP reboots. Under device I see 0.3Gb available
How do I give Webos more space ? Is it the media partition ? Or not at all ? I'll try to resize it but tailor is having trouble to start
Also what are the Resets Options I can use after all is updated ?
Erase USB drive ? Or should I go first with full erase ? (apps install and data+usb drives etc) then update ?
Won't it mess with android install ?
Thanks for help !
Edit : Tailor : after a while, I get Service Error (userId) org.webosinternals.tailor.nod is not running, hmm, any idea to fix this ?
Reinstalled, retrying
Click to expand...
Click to collapse
your media partition is way too small for webos. You need at least 1 GB. I would leave it at 5GB unless you aren't planning on using webos at all.
You have to remove space from data. In Tailor you need to unmount, check, and then resize.
To clean your CM 10.2 you should be able to just clear data from CWM.
Thanks for your reply, seeing you're pretty new, it's really nice
I tried resizing to 2GB, it didn't really work, I mean tailor says partition size is 2GB, then filesystem size is 399MB, webos only finds 399, same when connected to pc, and If I try resizing it says operation failed!
Or Could I try delete that partition without breaking the webos ? Then create it again 2GB from start, not sure tailor would manage but maybe ??
Otherwise, someone told me to use ACMEUninstall, and then run webosdoctor ? Is it really safe ? (I heard about people freezing with that app in past, so I'd like to avoid bad things)
Edit : as Tailor wouldn't manage to resize I followed what someone else told me, but think that was a bad idea, not sure yet, ran ACMEUninstall, then it booted on webos, no pb, I retried to use tailor no success, so I ran webos doctor, but it lost connection after 4%... Now looking about what to do, gonna retry this...
Found this, but doesn't seem to be for the touchpad, and the code gives me nothing so, dunno what to do now
Ps2004 said:
Thanks for your reply, seeing you're pretty new, it's really nice
I tried resizing to 2GB, it didn't really work, I mean tailor says partition size is 2GB, then filesystem size is 399MB, webos only finds 399, same when connected to pc, and If I try resizing it says operation failed!
Or Could I try delete that partition without breaking the webos ? Then create it again 2GB from start, not sure tailor would manage but maybe ??
Otherwise, someone told me to use ACMEUninstall, and then run webosdoctor ? Is it really safe ? (I heard about people freezing with that app in past, so I'd like to avoid bad things)
Edit : as Tailor wouldn't manage to resize I followed what someone else told me, but think that was a bad idea, not sure yet, ran ACMEUninstall, then it booted on webos, no pb, I retried to use tailor no success, so I ran webos doctor, but it lost connection after 4%... Now looking about what to do, gonna retry this...
Found this, but doesn't seem to be for the touchpad, and the code gives me nothing so, dunno what to do now
Click to expand...
Click to collapse
[Guide] Factory condition restoration
http://forum.xda-developers.com/showthread.php?t=1426244
gives this a shot
Alright thanks I'll try this
Seems easy, if all goes well
Running webosdoctor 3.0.0 now, 18% and going, sweet , after it I'll run 3.0.5, fix the store, and all should be fine, then clean cm10.x install
But, got a little question before I'm done, can you switch webos user account, email, without reseting the TP ? (and loosing the store fix ?)
Or should I be ok just getting a new pw, for it before selling, and tell the new buyer to change email and other infos on webos site ?
Hi
I just discovered that my phone's /data (and /cache) partitions (f2fs filesystem) seem to have gotten corrupted.
my suspicion is that it didn't shutdown safely (powerloss during shutdown, maybe the battery was already emptier than the os thought it was, starting the shutdown then increased the power usage)
The battery is less than a year old. (official replacement, not done by myself)
I didn't connect my 3T to power last night (forgot about it)
I connected it to power the next morning and went to eat breakfast, when I came back it was booted up. It still recognized my fingerprint and last app sessions still have screenshots from my apps. The home screen background is still the same. My apps are all still there as far as I can see.
But: all the data is gone. My apps start like I installed them fresh from the store and opening my file manager none of my files are there any more. only 15gb of 128gb used up. (it was closer to 100gb)
Upon noticing this I immediatly went to twrp (3.2.3-10) to use it's repair feature for the partition. -> Error 139
I did the same for my /cache partition and got the same error so I suspect it got corrupted as well.
I'm running Havoc OS 2.4, Android 9.0 (didn't get around to update it and it ran smooth without any major issues for months)
Is there any way for me to backup what is still there (maybe even sector copy (dd))?
Is it possible to repair such an image in Linux or recover some of the files from it?
Is it possible that a newer twrp version actually still can repair my /data partition?
Or is all hope lost? Did my smartphone automatically reformat /data? or has it maybe not touched the partition but cannot use it correctly?
What happens in this case on Android? Would've been nicer (for me) to run into a bootloop instead so I can figure out what's going on, before any hope is lost.
I'm pretty sure encryption was turned off due to magisk/root.
Once I set up the smartphone again I'll switch ext4. I currently blame f2fs but I'm not sure.
I have backups of the important data that was on my smartphone, but if there is any way, it would be nice to recover the rest (images, videos in original resolution etc.)
:fingers-crossed:
If anyone could contribute ways for me to look into this or show me how to proceed, I would be very greatful.
and maybe it's not even f2fs's fault after all.
Regards
EDIT:
in twrp's file manager the file system looks the same btw. (/storage or /sdcard look like factory default)
EDIT2:
I managed to create an .img file from my userdata partition by using the adb command from twrp's adb shell
adb shell 'dd if=/dev/block/sda15 2>/dev/null' > sda15.img
Click to expand...
Click to collapse
I hope that will help
I'll try https://www.forensicfocus.com/Forums/viewtopic/t=17133/ once it finished transfering the img file
Suddenly, I can't boot into Manjaro, so until I get time this weekend, I'm stuck on (Barf) Windows.
When I try to boot into my Linux side, it won't go past the Rog Strix splash screen and if I try and Ctrl-Alt-Del, it takes about a minute, then reboots, but if I let it sit, it just sits there for good.
So, I've never done a bot repair off an Install drive. Can anyone give me a quick run-down? Or should I try an earlier Kernel in the boot options screen?
To get you up and running try selecting one of the fallback kennels and see if you can get booted up that way
Boot repairs are not hard specifically but they are a little involved. Basically you'll boot up into a live USB of Manjaro. Then you'll mount your root partition (e.g. /dev/sda2) to /mnt. You'll then mount your boot partition (e.g. /dev/sda1) to /mint/boot. Once you have those two things mounted then you can use "manjaro-chroot /mnt /bin/bash" to get into your system. It will look and act just like of you had booted up into your install.
From there you can update or reinstall grub, look at your last boot logs, install/update software, fix config files, etc. For your case I'd go looking through logs and see what is happening and once you know that you can fix it. When I've had boot problems it was generally because I recently changed either /etc/default/grub or /etc/mkinitcpio.conf and I just need to rollback the change.
Another thing that could have happened is stupid windows had an update and during that update it messed with the boot partition, which is generally what happens during windows updates, and you just need to run an update-grub and that generally fixes the problem. That reason alone is why several years ago I stopped dual-booting and just use Linux exclusively and use Windows VMs if I need something from windows.
Good luck! Hopefully all that helps! Here's a link to the Manjaro steps. https://wiki.manjaro.org/index.php?title=GRUB/Restore_the_GRUB_Bootloader
ironLink21 said:
Boot repairs are not hard specifically but they are a little involved. Basically you'll boot up into a live USB of Manjaro. Then you'll mount your root partition (e.g. /dev/sda2) to /mnt. You'll then mount your boot partition (e.g. /dev/sda1) to /mint/boot. Once you have those two things mounted then you can use "manjaro-chroot /mnt /bin/bash" to get into your system. It will look and act just like of you had booted up into your install.
From there you can update or reinstall grub, look at your last boot logs, install/update software, fix config files, etc. For your case I'd go looking through logs and see what is happening and once you know that you can fix it. When I've had boot problems it was generally because I recently changed either /etc/default/grub or /etc/mkinitcpio.conf and I just need to rollback the change.
Another thing that could have happened is stupid windows had an update and during that update it messed with the boot partition, which is generally what happens during windows updates, and you just need to run an update-grub and that generally fixes the problem. That reason alone is why several years ago I stopped dual-booting and just use Linux exclusively and use Windows VMs if I need something from windows.
Good luck! Hopefully all that helps! Here's a link to the Manjaro steps. https://wiki.manjaro.org/index.php?title=GRUB/Restore_the_GRUB_Bootloader
Click to expand...
Click to collapse
Windows did do an upgrade - a crappy one at that. I need to get out of the WIndows Eval program now that I stay on Linux 99% of the time