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.
Related
This thread is about installing Android natively on your Vogue so it completely replaces Windows Mobile.
[size +1]Important: This thread is now out of date, if you want to flash Android, use the new "norootfs" NBHs.[/size]
There are 2 installation methods:
If you are already running android from your sd card then use method 2, if you want a fresh install of android 1.5 from a windows machine use method 1.
For both methods, you must have a HardSPL installed, if you have flashed a custom wince rom before then you will, otherwise read one of the other threads on XDA about how to do this.
Method 1:
------------------------------------------------------------------
download the following:
http://www.mediafire.com/?zldjhfnkzk2
Unzip it and follow the instructions in README-ANDROID.txt.
All you have to do is copy the androidinstall.tar file to your sd card and run ROMUpdateUtility.exe on your PC.
Now Donate:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Method 2:
------------------------------------------------------------------
Check here for NBH files containing a linux kernel and initrd to allow you to flash android to your vogue and wipe windows completely.
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
The ROMs are dated and there are three versions.
They are identical except the resolution; 240x320, 320x428 and 320x480.
You will also need a new rootfs:
http://it029000.massey.ac.nz/vogue/files/rootfs.zip
This rom will copy your rootfs, system and data to nand (the internal storage of the phone) so you will only be running from nand. To do this, make sure you have a working setup (using system.sqsh and data.img without partitions) and install the new rootfs. Make sure it still works.
Make sure you have a carrier rom to go back to. Android currently doesn't let you change any of the radio parameters so you would have to flash back to a carrier rom to re-provision your phone.
Now create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Now flash the rom corresponding to your resolution and wait.
There are 3 ways to flash a rom.
1. Use ROMUpdateUtility under windows (this may not work on these roms, i haven't tried it). Rename the nbh file to RUU_signed.nbh.
2. Use HTCFlasher under Linux, this is what I have been doing and although a bit quirky, it does work. A binary that fixes a few things with HTCFlasher is on the website.
3. Rename the nbh file to VOGUIMG.NBH, put it on an SD card and boot the phone while holding down the power and camera keys.
When it starts, it should be running from nand. The tmp and cache dirs are still mounted from sd, so you do need the sd card in there but it's not really used much.
If something goes wrong or you haven't copied the correct files, press volume up while it is booting (after the two vibrates preferably). It will display a message saying that its in recovery mode. You should be able to plug the phone into a computer and the sd card will appear as a usb drive. You can also connect using adb.
There are a few limitations, rootfs must be less than 13M, system must be less than about 90M and data must be less than about 128M. This means unless you use a very stripped down system with apps2sd, hero probably won't work.
I've put a linux adb binary on the files page that fixes the annoying history 'feature' too.
Remember, this will completely wipe windows mobile and all your data from the phone. Run android from SD first to make sure you like it and don't want to be able to easily go back to windows mobile.
I've spent a lot of time on this so I would like people to donate if they use it.
This is my paypal:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Woot!
Doing this now =)
dzo said:
I've spent a lot of time on this so I would like people to donate if they use it.
This is my paypal:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Click to expand...
Click to collapse
I'm paypaling 5 bucks right now.... and I dont have a Vogue, I have a kaiser, but hey, $5 is long overdue for all the work you've done for the kernel... if NAND support hits the kaiser, I'll probably throw another $5-10 your way.
*paypaled - I normally dont do this kind of stuff, but its the holiday season, the MSM Android project has made SO much progress cause of DZO, if everyone just donated $5-10, it would at least be a nice gesture for all the work he's done*
I just registered to say thanks for all the hard work! I'll paypal you some cash once I get it up and running! I have a couple questions...
First, what works and doesn't work with this version? Bluetooth, tethering, nav?
Second, what version of android is this?
After flashing android using this method, can you still force the phone into the bootloader? I am assuming this is how you would flash back to windows.
Thank you, dzo. This is incredible work!
Now that you've gotten this far, can you answer some questions for those of us considering making the switch to Android:
What is/is not working in this build?
What version of Android is this?
What are the advantages of running one resolution over another?
Will we require new drivers to sync to our PCs when running Android instead of WinMo? Are they available for all OSes? (XP, Vista, 7, OSX, Linux)
How can we return to WinMo if necessary?
What's next in your development goals? With any ideas, can you give any sort of time frame on what we can expect and maybe when?
If I understand correctly, theres "NO" build in here, you play with builds in your DS, and when you are ready and like one..you just use that system.sqsh data.img rootfs (provided) and..the nbh, all in the root of the sd card. And it will flash the nand with your files! So..thats it!
Nice one dzo, hoping for you to get to kaiser
Hey Martin, I can't even use these flashable images, but if it weren't for you I wouldn't even be running Android via haret, plus you've answered so many of my questions and I've never donated. So, since you're actually now, I'll donate $10.
flashing from windows
Can someone try flashing from windows, then use mtty and run
Code:
set 16 0
task 3
I had to do that to get my test phone out of bootloader last night even after flashing from Linux. But it's up and running 'the new old fashioned way' now.
gswarriorfan said:
I just registered to say thanks for all the hard work! I'll paypal you some cash once I get it up and running! I have a couple questions...
First, what works and doesn't work with this version? Bluetooth, tethering, nav?
Second, what version of android is this?
Click to expand...
Click to collapse
nothing that hasnt already worked works there is no change...
dj13241 said:
After flashing android using this method, can you still force the phone into the bootloader? I am assuming this is how you would flash back to windows.
Click to expand...
Click to collapse
yea camera + power + reset hole
Shidell said:
Thank you, dzo. This is incredible work!
Now that you've gotten this far, can you answer some questions for those of us considering making the switch to Android:
What is/is not working in this build?
What version of Android is this?
What are the advantages of running one resolution over another?
Will we require new drivers to sync to our PCs when running Android instead of WinMo? Are they available for all OSes? (XP, Vista, 7, OSX, Linux)
How can we return to WinMo if necessary?
What's next in your development goals? With any ideas, can you give any sort of time frame on what we can expect and maybe when?
Click to expand...
Click to collapse
i can answer a few
1 nothing that wasnt already working this isnt a build!!!, this is a way for VOGUE users to be able to put a working build "data.img and system.sqsh" they already have working on their phone and to be able to get rid of android
2 this isnt a build
3 320x240 shows more on screen 320x428 and 320x480 show more on screen but it is a little blurry
4 you will require adb drivers located on http://code.google.com/p/vogue-android and as far as i know they work on vista 32 and win 7 32 bit and there are different ones also located at vogue-android for win 7 64b
there are adb drivers for linux in the android SDK located here http://developer.android.com/sdk/1.6_r1/index.html make sure you download 1.6r1 though! 1.5r3 doesnt work for our devices in linux
5 just reflash any wm rom (that works with vogue of course)
mrkite38 said:
Can someone try flashing from windows, then use mtty and run
Code:
set 16 0
task 3
I had to do that to get my test phone out of bootloader last night even after flashing from Linux. But it's up and running 'the new old fashioned way' now.
Click to expand...
Click to collapse
you could also use the bootloader cmd prompt in htc flasher and do:
Code:
set 16 0
ResetDevice
Does this have lcd density set? Because eclair is density 120, but looks better in 320x428 with 160 density. If not, is there a way to set density after flashing?
Ahhh ok I get it now. I'll still donate when I get it up and running. Thanks!
OMFG!!!! dzo you are something else!!!
I just got my Vogue a few weeks back and I am surprised on how well Android runs on this thing (I have a Raphael as well, but no comparison to this)
Having a flashable rom to a WM device... unbelievable...
Kudos for your work man!!!!
I guess the question on a lot of people's minds right now is this... how do you go back to WM?
you could also use the bootloader cmd prompt in htc flasher and do:
Code:
set 16 0
ResetDevice
Click to expand...
Click to collapse
I tried that and it came back in bootloader with 'RUUNBH' in the upper right corner. Then I added the task3 and it booted normally. Who knows, maybe I did something else funny.
I used htcflasher on my newly-reloaded ubuntu laptop, but I wasn't able to get it to work under windows. So I thought that maybe flashing from windows was ok, but it just needed a kick through mtty to get going.
What do those two bootloader commands do? Not that it really matters since dzo says the newest version should work from windows anyway...
egzthunder1 said:
I guess the question on a lot of people's minds right now is this... how do you go back to WM?
Click to expand...
Click to collapse
Boot back to bootloader and flash it! Did that myself last night.
Also, how do we make a smaller data.img? I keep getting 256MB versions.
scizzle said:
Does this have lcd density set? Because eclair is density 120, but looks better in 320x428 with 160 density. If not, is there a way to set density after flashing?
Click to expand...
Click to collapse
There's no density set on the kernel cmd line, I'd have to make another nbh for that.
However, since system can now be made r/w you should be able to edit /system/default.prop to change density.
Do:
adb remount
adb pull /system/default.prop .
edit the file and change ro.sf.lcd_density
adb push default.prop /system/
reboot
Thanks you so much dzo. i got this working, now im going through all my android files on my computer to find a build that i like, and wanna keep as my main build, but one thing, does the data really have to be less than 128mb? because almost all my android builds are alot bigger which is annoying.
but other than that it worked like a charm. thanks so much.
p.s. once i get some $$ (the 15th of december [my payday]) and find a permanent build i'll send some donations for you hard work.
dzo said:
There's no density set on the kernel cmd line, I'd have to make another nbh for that.
However, since system can now be made r/w you should be able to edit /system/default.prop to change density.
Do:
adb remount
adb pull /system/default.prop .
edit the file and change ro.sf.lcd_density
adb push default.prop /system/
reboot
Click to expand...
Click to collapse
Legend! Thank you. I will try it as soon as I can figure out the data.img haha.
scizzle said:
Also, how do we make a smaller data.img? I keep getting 256MB versions.
Click to expand...
Click to collapse
jamezelle said:
i used the following commands to make a new data img
Code:
dd if=/dev/zero of=~/data.img bs=1048576 count=128
mke2fs -F ~/data.img
to make a blank 128 mb data.img file in my home folder
Click to expand...
Click to collapse
- I can now confirm that flashing the nbh with the ruu works from Windows.
- dzo, I have a panel type 3 us sprint vogue. everything booted up fine, the buttons work, but the touchscreen isn't. Will post logcat / dmesg in a bit.
edit: uploaded zip w/ logcat and dmesg
This thread puts all the necessary steps together for sucessfully run the Android-release from THIS thread on the X1. Since many seem to have problems with that this may become handy
So lets get started!
What you need:
- latest XPEROID-release, fatsal-xperoid-20100221.7z, get it here
- 7zip to extract it, get it here
- sd-card, using fat32-filesystem with 500MB free space
What you need to do with it:
1. Extract fatsal-xperoid-20100221.7z on your computer. This will give you the following files:
- calibration, wlan-firmware
- haret.exe, runs the linux-kernel and android
- initrd.gz, initial ramdisk, needed for linux to boot (phase one)
- modules-2.6.27-00888-g339bdfc-dirty.tar.gz, linux- and android-driver for wlan
- rootfs.img, contains files needed for linux to continue boot (phase two)
- STARTUP.TXT, contains the parameter for haret.exe and boot-options for linux-kernel
- system.sqsh, contains all android system files
- zImage, contains the linux-kernel
- conf/*.user.conf, configuration files for android
- AndroidApps/*.apk, applications for android, installed during boot
2. Delete all the *.apk-files from the AndroidApps-directory. They are not needed for running android. You should keep the directory, just delete all files in it.
3. Download some essential android apps here, you will get essential_apps.zip. Extract it and put the apk-files into the AndroidApps/ folder.
4. go to conf/ and delete eclair.user.conf, then rename eclair.user.conf~ to eclair.user.conf. That will disable the swapfile.
5. open startup.txt and remove the mem-option mem=102M. This was suggested by hotlein here. That will increase the memory from 102m to 182M and improve android speed alot.
6. Copy all files and directories to the root of your sd-card. Do not create any directory, just copy them to the blank sd-card.
7. Put the sd-card in your phone if not already done. On the X1 open the sd-card and run haret.exe. You will get alot text running across the screen. During the boot-process, one file is created.
- data.img (256M). This file contains all the files normaly stored on the android-phone. Your settings, Applications, media, etc. You can always delete this file to reset android. It will be recreated.
First boot takes a while to complete, so be patient. Finally you should get the android welcome screen. Follow the on-screen-instructions and you are done!
Changing some settings
- IMPORTANT: Disable GPS in settings -> location & security -> Use GPS satellites, because it will hang the device!
- Turn off locks screen when holding red call button. Spare parts -> End button behaviour -> Nothing. That will simplify the shutdown procedure. Credits go to Reversedhex: Post
Now let's stop android
1. Press and hold the end-call-key. The phone starts to vibrate like crazy, ignore that.
2. After a few seconds a menu pops up. Dont release the button yet, keep holding it! If you changed end button behaviour, you can release it now.
3. Press down on the digi-pad. You may press it three times to go to the shutdown-option.
4. Now you can release the end-call-key. If you do not hold it, you will end up in the android lock screen.
5. Select shutdown option and confirm. Then android shuts down.
If you try another kernel-image (that is replacing zImage), the system may lock up during shutdown. Then you have to soft-reset your phone. But you should always try to shut android down.
Now you can update the linux-kernel:
1. Download the kernel-image, get the latest here. That gives you zImage_kovsky_20100325.zip.
2. Extract zImage_kovsky_20100325.zip to get zImage. This is the linux kernel.
3. Copy zImage to the root of your sd-card. You should always back up your existing zImage so you can go back.
4. Download wlan-modules, as they must match the kernel-image, get them from here. That gives you wlan-modules_20100325.zip.
5. Extract wlan-modules_20100325.zip to get modules-2.6.27-01006-ga30aafa-dirty.tar.gz. This archive contains the wlan modules. Do not extract this. Simply put this on the root of your sd-card. On android startup this file will be extracted on the modules copied for you.
As suggestet by angusmcb (post), i used for the latest kernel the latest cross-compiler.
Latest kernel from xdadev-repos with backlight control and correct battery readout, get it here. The archive also contains matching wlan-modules.
Troubleshooting
Q. Android will not boot
A1. check if all needed files are present
A2. check if you have enough free space on card. Android creates two big files during first boot, so you will need at least 384M free space.
A3. you can try to delete data.img and swapfile to reset android. This helps if you messed up settings in android.
Q. Wlan wont start
A1. check if file calibration on sd-card-root
A2. check if file modules-*.tar.gz matches kernel-image
A3. you may try to enable wlan in windows mobile before running haret.exe
Q. How to stop android from using data connection
A. go to settings -> wireless & networks -> mobile networks -> access point names and delete all apn-settings
Q. Android-screen is upside-down
A. Slide out keyboard -> android switches to landscape. Then slide keyboard in -> android switches to correct portrait.
Q. I have no ringtones
A1. Put the ringtones in the MEDIA\AUDIO\ringtones folder (post, post for folder structure)
A2. Take a look at this post. Some characters make the android media scanner crash.
Q. I can not enter pipe-symbol. Where to find keymaping
A1. Press function key, followed by shift key, followed by commer key (right hand side of space bar) (linuxtux post)
A2. For keymapping in general take a look here. That is the default android keymapping.
Q. I want live wallpapers
A. Here you go. But be prepared for performance loss.
Q. I can not send SMS
A. Check this post by jimipoh. It might help.
Done for today
reserved for future updates
also reserved for future updates
and this, too
vdelf, are you going to be taking over development for Android on the X1 as well? Or will this be instructions to get fatsal's functioning?
What the F?
♥♥♥
Good luck~♥
Muo said:
vdelf, are you going to be taking over development for Android on the X1 as well? Or will this be instructions to get fatsal's functioning?
Click to expand...
Click to collapse
This thread is mainly about how to get android working. I am trying to speed android up by partitioning the sdcard as fatsal mentioned. If it works there will be a HOWTO for that, too.
Until then i will continue to work the linux-kernel for X1-android until it is done (or i loose my X1, too )
This is pretty consize. I hope it sums up all the main points of fatsal thread on android
With zImage_kovsky_20100313.zip system always lock up during shutdown
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
gbajzelj said:
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
No no no! Your doing it wrong!! D:<
gbajzelj said:
i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
Unfortunately, due to certain hardware limitations of the X2, boot time of the X1 kernel on the X2 can take a little longer. About 1.2 seconds after the sun explodes and extinguishes all life on Earth 4 billion years in the future, is a good estimate.
Sorry
vdelf, will you be committing regularly to gitorious? Or do you have a scratch repo for messing around with?
vdelf said:
also reserved for future updates
Click to expand...
Click to collapse
i always get an error saying mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount the sd card, cannot continue
/bin/sh: cant access tty; job control turned off
anybody has any idea? i am using sandisk mobile ultra 8gb mirco sdhc
i had the bin/sh error too , first time.
when simply retrying -> it booted up to the "exploding X".
however, that screen froze on me.
i seem to get more progress though than with the material from the original threads.
the material from this topic has gotten me further than ever before. as i speak i'm booting a fresh one with the new kernel (from the start). it's upside down, but i hope this one works 'out of the box'.
persistence is paramount, as time passes the chance on reaching satisfaction approaches 1. how this satisfaction is achieved is up to you; may it be through running XPEROID, purchasing an android phone or simply giving up.
I managed to get it back to the "exploding X" screen (using the first file, not the kernel update).
It seems to be stuck in the X screen though, it's looping (and stalling a little) for 20 minutes now. Last time I soft-resetted the phone after about 10 minutes of X-screen, and it mangled my sd card (meaning I had start from scratch). There is no text (or error message for that matter), so I don't know what is going on.
Is anyone familiar with this?
EDIT:
I paused my attempts for now. Same result over and over. I'm not able to find anything on this in the original thread (or possibly when I read every single post I might find something), search reveals nothing to me.
gbajzelj said:
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
You have to use a version of haret that supports your phone. As X1 and X2 have not identical hardware (or do they?) someone has to code X2-support to haret. Until then it will not work.
In startup.txt there is this line
Code:
set mtype 2006
This is for kovsky X1. For X2 there has to be a different value, but dont ask me about that
dawen said:
i always get an error saying mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount the sd card, cannot continue
/bin/sh: cant access tty; job control turned off
anybody has any idea? i am using sandisk mobile ultra 8gb mirco sdhc
Click to expand...
Click to collapse
It seems that your sd-card has no partition. If you use linux, you can check this very easy. On windows, you can try to reformat the card.
You can also try another card.
Woudnt it be possbile/smarter to put the android on your xperia's internal memory (when you have 300+mb free?) or woudnt there be any diffrence in speed?
can you install apps from the market
or do you have to manually do it (pasting the apk to the sd)
?
Happy new Year and thank you for yor feedback, I may be late to the party but my work is killing my spare time. So, Iam trying to update the walkrthough to cope with the ongoing developments.
On a side note I've upgraded my xperia to an android device but Iam keeping it for jailbreaking purposes
Lets get it on!
Assuming your device is covered in the compatibility list you have to have the device rooted.
For how to Root (HARD-SPL) Your Xperia X1 check Here!!
Then its a matter of OS, in this thread we are talking about HTC Devices that run WinMo as a native Operating System. This hack works only in Linux enviroment so we need Android to run on the device.
How to run android depends on the particular device so one must go to the respective thread.
For Xperia its this thread
The Froyo Development has stopped but the current version is far superior than what we used some months ago.
In short dowload the xdandroid stuff, put the unrared files on your sd's root and boot through HARET once.
-
We now should be at a point that our device boots normally to The 2.2 froyo android version through Haret. Then we have to replace the module and zImage files with the PSfreedom respective ones plus the psfreedom.ko file. All these should be placed and overriten in the root folder of the SDCard.
Here is the latest Payload for Xperia
(need some help with the changes, but Iam impressed so far with the outcome)
All the preliminary work is done, now for the ****ty "do this everytime you wanna play back ups" job
Assuming the phone is off...
Turn it on
Wait for winmo to boot then run HARET from the device's file manager
Wait till android fully boots and navigate to the menu->DevTools->Terminal Emulator
in the terminal you must enter the following lines...
su(enter)
cd(space)/sdcard(enter)
insmod(space)psfreedom.ko(enter)
Click to expand...
Click to collapse
At this point the phone is ready
Pull out the power cord of the PS3 (or flip the backswitch to off)
insert the phone at the first usb port (preferably with the shortest USB cable you can find)
flip the switch or insert the power cord
wait 3 to 4 seconds
press power on followed quickly by eject
you should hear 3 short blips
it takes 5 seconds for PS3 to boot
and DONE.
if it doesnt succed just repeat the process. if it never suceeds then you don't run @ 3.41 FW
[UPDATE#0] I Updated the PSFreedom Files link from the "Homebrew only" Free version to the Backup Enabled "Full" Version. Still Ver 1.0 though...
[UPDATE#1] It definatly needs 4,5 tries, I cannot get it to work in the first try...
[UPDATE#2] Everytime I try to run a backup my FAT PS3 Freezes... and to think I came this close...
[UPDATE#3] Stupid me, didn't check it out in the above compatibility list... tried another one works like a charm
[UPDATE#4] If you are 100% sure you did everything right and still you cannot perform the exploit on the console you should not turn off the device and boot it again, you can have it in terminal mode as long as you wish and perform the exploit on the PS3 again and again... This is also usefull when the console freezes or crashes, you just perform the power cycle only!!
Well There goes one day of my life I think I covered more than the basics, If you thing I helped you I would appreciate a line or two
[UPDATE#5] Went out today and felt like spending 300 Euros, got my self a Slim one. I will be testing it later today...
[UPDATE#6] I found out that the PS3 Slim model has a much greater success rate for the hack to work. Also, I tried all the steps and bypassed the active sync stuff and I can confirm that by bypassing it, IT WILL NOT WORK
[UPDATE#7] 5 Days into this and 3 with the slim model, slim works better BUT, the problems occure because of the xperia hardware/xdandroid port... it works but not always, its nerve wracking I know, so do the Developers of PS Freedom as they updated their wiki Raphael page page in the problems worning section.
aaaanyway, Tomorow Iam upgrading my HDD my old one is full.
[UPDATE#8] 11 days later and I have updated my fat ps3 to 3.42 and kept my slim hacked. Its a tedious work to enable every time xdandroid and the psfreedom hack but as I said it is free, anyway, having the slim console AND a very short cable (mine is 10cm) works EVERY SINGLE TIME, no probs with that. I had though 2 issues of console freezing... I don't know if it is the hack or my new HDD (7200rpm) nothing serious though...
[UPDATE#9] I've tried to replace the active sync step and connected the device to ps3, first time it worked, second time it failed...
[UPDATE#10] Well, thats it for me, I could no longer cope with the tedious steps in order to play for an hour, I've bought a jailbreak clone and flashed my xperia with a diffrent rom and formatted my SDcard. for the time being, Iam no longer using the Raphael hack...
[UPDATE#11] As it turns out my jailbreak clone is not upgradable (it was damn cheap after all). Anyways, I browsed to PSFREEDOM.com to see the development of the raphael hack and to my surprise i found out two things...
a) This thread is hotlinkedvia this page http://psfreedom.com/wiki/Sony_Ericsson_XPERIA_X1, which is kinda cool I guess...
b) I found out (probably need to read my thread a little bit more ) that more recent hermes payloads are been released for xperia...
So, I will refresh any broken links, start again, and keep updated this first post agains the willings of our beloved sony
[Update#12] The true reason that I returned is that my fat PS3 pulled a YLOD on me and left me empty handed this holiday season, so I dusted off my jailbreaked one
Click to expand...
Click to collapse
I did this process again and again but when ps3 start up nothing happened but top of screen this message appeare that the usb device was unknown
ldghn said:
I did this process again and again but when ps3 start up nothing happened but top of screen this message appeare that the usb device was unknown
Click to expand...
Click to collapse
The same thing happened with me the first few tries, this message means that the process is not right, I solved this issue by re formatting xdandroid again and carefully placing and overrighting the files...
When you are 100% certain that the procedure is right (according to my walkthroug) then its only a matter o timing... keep trying mate.
First time i run android use original the module and zImage file and then replace them with ps fredoom files or from first i use replaced files??
ldghn said:
First time i run android use original the module and zImage file and then replace them with ps fredoom files or from first i use replaced files??
Click to expand...
Click to collapse
I think its very clear that you have to boot on android at least once with the original files....
(the initial install and calibration)
I reinstall android 2 times and this time whne i connect device to ps3 no message about unknown device have been shown but ps3 dont show nothing ( manager.pkg) for install
I dont know what problem's.
ldghn said:
I reinstall android 2 times and this time whne i connect device to ps3 no message about unknown device have been shown but ps3 dont show nothing ( manager.pkg) for install
I dont know what problem's.
Click to expand...
Click to collapse
So you finally done it!!
Under the GAME section on the XMB you should see a new item called "Install Package Files"
take a usb drive and put inside (root) the manager then insert it in the other free usb slot.
Press X at the "Install Package Files" and Install the manager...
Jim P said:
So you finally done it!!
Under the GAME section on the XMB you should see a new item called "Install Package Files"
take a usb drive and put inside (root) the manager then insert it in the other free usb slot.
Press X at the "Install Package Files" and Install the manager...
Click to expand...
Click to collapse
My problem is in step that you said
I connect usb drive with manager in but "Install Package Files" dont be apparent
ldghn said:
My problem is in step that you said
I connect usb drive with manager in but "Install Package Files" dont be apparent
Click to expand...
Click to collapse
Then you didn't do the exploit... back to the drawing board my friend
Thank You soo much! It works on first try
error
so i managed to get android runnig via fatsal.
when i try to follow your terminal instructions it gives me back errors!
so i figured out actually the right comand is cd(space)/sdcard!!!!
but when i try to do the same with endboot it says no such folder!
so i tryed the next step the insmod psfredoom.ko it does something then i connect to my ps3 do the power trick and all but the most that i get on my ps3 is that "an unkwon device is connected" and nothing else! any suggestion?
trinolmf said:
so i managed to get android runnig via fatsal.
when i try to follow your terminal instructions it gives me back errors!
so i figured out actually the right comand is cd(space)/sdcard!!!!
but when i try to do the same with endboot it says no such folder!
so i tryed the next step the insmod psfredoom.ko it does something then i connect to my ps3 do the power trick and all but the most that i get on my ps3 is that "an unkwon device is connected" and nothing else! any suggestion?
Click to expand...
Click to collapse
What I have gathered together in this walkthrough is what many people suggested and some other people including me found usefull and working.
You probably don't have the proper file arrangement in your SD card
and the actual command line is "cd sdcard" to access the sd card and thed "cd andboot" to access the "andboot" folder where the PS Freedom files reside.
hope I helped
trinolmf said:
so i managed to get android runnig via fatsal.
when i try to follow your terminal instructions it gives me back errors!
so i figured out actually the right comand is cd(space)/sdcard!!!!
but when i try to do the same with endboot it says no such folder!
so i tryed the next step the insmod psfredoom.ko it does something then i connect to my ps3 do the power trick and all but the most that i get on my ps3 is that "an unkwon device is connected" and nothing else! any suggestion?
Click to expand...
Click to collapse
hi all,i have the same problems,dont existing the folder"andboot" i creat it ?
thx
hi mr i while insert cd andboot write in terminal can't cd to andboot and while connect to ps3 write an unknwon device is connected please help me thanks
teksound said:
hi all,i have the same problems,dont existing the folder"andboot" i creat it ?
thx
Click to expand...
Click to collapse
yeah. earlier I placed EVERYTHING in the root instead of making a folder called "andboot" so I'm going to do that again and see what I get. I think it's a bad psfreedom.ko file.
People...
When you installed xdandroid on your xperia the guy who made the port said that you have to create an andboot folder to place the android kernel inside...
so by default you have an andboot folder.
then its a matter of overiting 2 files there... simple as that.
Finally i did it
It works for me now
Perhaps i am stupid, but i cannot get it to work. This is how i do it:
Copy the android files to the sdcard and boot it in the phone with the haret.exe (takes a loooong time to boot). Reboot the phone back to WM, copy over the files module and zImage file, boot back into android with haret, startup terminal, write in the commands and so on. I start up the PS3 as instructed but i only get the message unknown USB and I cannot see any install pkg file.
I have tried and read all the instructions but I cannot understand what I am doing wrong, anyone have a tip?
helps needed
i have been trying make it work all day with no luck. mine is a uk version X1 with original rom. i followed instruction step by step and even reinstall the andriod port several times. however, still not working. always appear unknown usb device on ps3 screen. the only thing i didnt do is that flashing the SPL. is it a necessary step? what's the purpose for flashing the SPL?
actually, the module files from android and the one from psfreedom didn't have the same name... is this an issue ? witch name we have to keep ?
thx for the tuto !
editi guess sdcard is incorrect/confusing for my situation, it's the entire system up to root folders is stuck in a read-only type state.
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected]ost #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
plasticsoldier said:
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected] #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
Click to expand...
Click to collapse
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
plasticsoldier said:
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
Click to expand...
Click to collapse
I would suggest trying to restore down to WebOS 3.0. In that procedure you literally wipe EVERYTHING on the internal partitions in novaterm and start from absolute scratch. Therefore, if it a software issue you could solve the problem. However, if it is a hardware issue, you'd be kinda screwed.
Yeah, none of the methods I've ended up finding about this problem or other bricked problems are working at all.
i checked at work when i bought it, which of course the 11th was the year mark... but I do have android installed so even if i can get any chance of them honouring it so close they'll probably be like "oh you have android, that'll be $$$ for us to do anything. thanks!"
So I guess I now I have a paperweight with some features.
cdzo72 said:
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
There is a thread in the General forum about how to restore and downgrade. Have you tried that thread ? It is usually a great way to try and get that last restore before sending it back to HP.
73 de VE6AY
Sent from my HP Touchpad, running the latest CM9 nightly, from the XDA Premium App
how are you adding and deleting files when in android? which version of android do you have installed? have you tried different rom versions? have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to? it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard? are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android? have you run "fix permissions"? Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
sstar said:
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
Click to expand...
Click to collapse
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
cdzo72 said:
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer, this would tend to suggest that the problem is software based corrupted or otherwise. I am trying to find a program that will allow me to read/format the Android partition on my windows computer and will let you know if come up with anything.
Regards
i guess i should change the title slightly.. it's not sdcard, but basically the entire touchpad contents. go to root and delete whatever i want and it doesn't matter. connect it and format with windows and it doesn't actually matter.
haxin said:
how are you adding and deleting files when in android?
Click to expand...
Click to collapse
i've added and deleted just by using mtp. i've also deleted the files on the android side with the video player (vplayer) i've installed es file explorer (which after restart is gone) and deleted with that. i've also gone into webos and installed internalz pro and deleted files that way, which it then seems to work until i of course do anything related to restarting.
some of the files i've put on, i've had it recognize briefly. so for the video file, start it, then it gets really choppy/glitchy playing it. so stop it, go back into the vplayer and it's back to the old stuff
which version of android do you have installed? have you tried different rom versions?
Click to expand...
Click to collapse
android version 4.0.3. nothing else will install. if i add files while in android, when i boot into cwm they are gone. if i mount usb in cwm and add them they stay briefly but when i try to flash them they fail.
have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to?
Click to expand...
Click to collapse
i have not tried adb yet, just not as familiar using it properly, i will give it a try though.
i am using windows 7 on my laptop currently. i do have a pc upstairs that i barely use that has vista, but i don't know how that would make a difference to the touchpad
it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard?
Click to expand...
Click to collapse
yeah as i put above i guess saying sdcard was a bit confusing/misleading (my bad, sorry!), i didn't really know what else to call it at the time or how to explain myself properly at first.
are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android?
Click to expand...
Click to collapse
i can move/delete/modify anything which has absolutely no effect to the device. i've used es file explorer and gone up to root and deleted everything and the system runs fine. says the system is empty with lots of free space (its the 32gb model) but restart or even go into recovery and everything is once again there.
have you run "fix permissions"?
Click to expand...
Click to collapse
i've run it a few times. just acts likes it's working and then says done. i've even gone into the mounts and storage in cwm and formatted sdcard/cache/data/system. does nothing at all in the end of things
Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
Click to expand...
Click to collapse
it was just something to try to get somewhere right. it never gets past 12%. always fails to reboot.
I am currently letting the battery drain and see if it dying and then being charged will do anything. probably not. but who knows. i talked to a "tech" on the chat support (i never mentioned android) who told me that having preware installed in webos causing it to become corrupt and they "don't knowledge of preware installed devices" exact words. no idea what that means haha don't have knowledge, don't acknowledge...
anyhow. i've not quite given up. i just don't really see it turning out any differently from the previous times. i do appreciate all the feedback and help very much though
ok so heres what I would try. First try flashing a new fresh rom. download one that you want to your computer like cm9 nightly or aokp or whatever you feel like. then boot into CWM recovery connect the touchpad to the computer via usb. then connect to the touchpad with adb. I'm not sure how to do this in windows because it's been so long since I've done it on a windows box, I always use linux.
adb has alot of options, you can move files to and from the device, you can uninstall or install app packages, and more. this way you can adb push the rom .zip to the touchpad's sdcard while youre in cwm recovery. this way you dont have to reboot the touchpad and risk having the file disappear, you can just go to 'install zip from sdcard' and then 'choose zip from sdcard' in cwm recovery after you adb push the rom, you should see it in the folder you pushed it to on the sdcard.
If you arent familiar with how to use adb from the command line or the terminal this might not make alot of sense and i dont know how better to explain it than that. Also yes windows 7 vs windows vista does make a difference there are issues with novacom installing properly, that's why you would have problems running acmeuninstaller or acmeinstaller2. if you look around you should find some videos or how to's that can probably explain it better. Hope this helps.
http://www.webos-internals.org/wiki/Novacom_with_Windows_7
http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-5.html
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
ve6ay said:
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
Click to expand...
Click to collapse
Probably the best suggestion yet given that everything else has been tried.
Good luck.
****EDIT****
Before you attempt the step above I have just noticed a difference between between cwm and. TWRP2.2 which I have installed on my Touchpad via goo manager. If I open recovery via goo manager and then select wipe it gives me 4 options cache, davlik, factory reset AND system which i think says will remove your rom . I don't see the forth option available with the regular cwm/clockwork. Just a thought.
All the best with whatever you try next.
sstar said:
Probably the best suggestion yet given that everything else has been tried.
Good luck.
Click to expand...
Click to collapse
this would work, however you have to fix you novacom/novaterm issues on your windows machine before you'll be able to do any of this. the reason acmeuninstaller, acmeinstaller2 arent working is likely because youre on a windows7 64bit box and Palm-sdk, the novacomd.exe, noverm.exe, and javaruntime apps and drivers arent setup right. just make sure you have the proper javaupdates on your computer then you can install preware in webos, preware has some nice tools that will delete the entire android install partitions, one is called 'remove android' and the other is called 'tailor' you run them from within webos. after you do that then in webos you should do a full device reset. you'll find it in the "info" tab under settings in webos. this will delete and reformat the whole /media ,(aka sdcard) partition. so you will lose all the files you have stored on both webos and android. that format will take a long time probably like 30 min or more. after thats done. reboot the hp and run webosdoctor. now i know for sure this will work because ive done it on mine. remember to put the touchpad in developer mode in webos first to install preware. you can do that by typing webos20090606 into the webos search bar and hitting enter. I'll put links from my box.com accou t to everything you need.
https://www.box.com/s/479acdb6ef9c99fc7b92
https://www.box.com/s/1aed4722990aad251570
edit: also I'm not sure if youre on the 16gig 32gig or 64gig pad, the webosdoctor that i linked is for 32gig wifi only US version. if thats not what you have then youll need to get the doctor for for specific touchpad. or you could create a webosmetadoctor but thats a whole nother project.
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
plasticsoldier said:
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Click to expand...
Click to collapse
ok no one will be able to help you fix this issue unless you give complete details of the problems. when you say " novacom/novaterm stuff doesn't work" we cant really help specific error details is what i need. I dont mind helping you fix this but you have to be a little more specific on exactly what,where, and how youre installing and running and mounting apps and directories.
your problem IS fixable but you need to slow down and really do things exactly step by step.
Ok so back to ./adb. now when you boot in to CWM recovery on he touchpad DONT do anything in CWM just plug it into the computer. do not mount it as a usb storage and dont mount or unmount the sd partition LEAVE IT.
you can then use ./adb from the command line or terminal on the computer to move the files to the touchpad' or install apk's uninstall apk's you name it. This will require that you know some linux terminal commands. for example to move a new rom zip to the internal sd card or into any other folder you can use ./adb push command to run a root shell on the android device itself you can use ./adb shell and then change folder and file properties from readonly to rw. this can all be done while the touchpad is patiently waitng in CWM recovery. this way when youre done installing or uninstalling apps from the device and moving flash zips to it, you can disconnect the .adb connection with ./adb disconnect or just type exit from the terminal till it closes. unplug it then you will be able to pick up the touchpad and install zip from the sdcard, keep in mind you dont want to choose 'apply u[date from sdcard' you want to use the 'install zip from sdcard option' you can read up more on how adb works. it is probally the most important part of hacking android.
with that being said. novaterm is the palm webos version of .adb. this is why when you boot into webos recovery to do things like acmeinstaller and acmeuninstaller2 the novaterm novacom and novacomd apps have to be installed correctly on the computer or else you wont be going anywhere fast. some screenshot examples of how it should appear below.
https://www.box.com/s/432e63a83215f00eea6a
https://www.box.com/s/970bc29542a05f98f036
https://www.box.com/s/63c0f656e8354f7f2d6a
https://www.box.com/s/cbe3266467ae8e3ebabe
https://www.box.com/s/005e56a61a178dd17fa4 some better resolution images.
Plasticsoldier said
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Yes there is
Firstly tailor does exist, it is a beta and the facility to dl must be enabled.
Read this and scroll down to Enabling beta test feeds and follow the instructions , when you get as far as using the Linux command you CAN copy and paste thank God.
http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true . After that reboot into Webos and launch preware. Go into managed feeds as per the instructions in the link above and install Tailor. Reboot again and the app will work. It looks very good actually.
But before attempting to actually use Tailor please read the article I have posted below it is only 7 pages long but will explain how to use Taylor properly as it is a powerful tool.
http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html
I have done all of this , this morning so if you have any problems pm me or ask in this thread.
I sincerely hope that this helps, it should be the answer to your problems.
@haxin: sorry, wasn't trying to be unhelpful when everyone is being helpful to me. I shall be more detailed in future responses. I think i was getting frustrated and had had a busy exhausting day so it didn't help me come across clearly/properly.
OK, so I had preware installed already, so I removed it, went into developer mode, used the linux commands, reinstalled preware, added Tailor.
(i've done this a few times, because I didn't remove the cable after doing the linux commands for preware, then i accidentally hit the wrong buttons and it connected to 'usb drive' mode and wouldn't connect on the pc side and got stuck on the "ow disconnected me properly next time" screen).
So it gives me the following options
USB (media)
Android (system)
Android (cache)
Android (data)
Unused Space
the 'usb media' starts mounted and will mount again if unmounted. If I use 'check filesystem' it'll pass. So then I try 'delete partition' which pretends to delete, then it takes me to the unused partition which is still at 16mb. so i try to use "check filesystem' again and it fails. try repair and it fails as well
I've tried mounting the android parts just to see, they just sit there processing that they are trying to mount. trying to delete or anything else fails as well.
and now after trying things, any of the 'cards' will try to open and just sit there grey. and with my usb cable not plugged in it still is giving me the option to enter usb drive mode. and with this i have to restart and go through the steps again of adding Tailor which is getting tedious.
I restarted, went through the motions to get back to Tailor. trying out resizing just to see how that goes. So far 15%. not sure what will happen when done, but we will see.
This is getting long, so i'll end this part and update on anything and also try to familiarize myself with adb a tad more
here simple application that will enabled UMS mode for External sdcard
root needed.
how to use:
safe way on version 2.5 is :
enable UMS Mode when cable usb is unplug
Back to Charge mode when cable usb is unplug
safe way on version 3.0 is :
do it on condition usb plugged
note:
if you plug into player or some device player , and you found that it cannot found the USB drive
in this case just do this
settings -> connectivity -> usb connection type
and do press or repress the "Charge Only"
in version 3.0 you will notice 1 triangle on task bar, its normal , it telling you mass storage is currently unmount
2 icon on task bar is telling you the mass storage successful unmount you can take it out
those of notice are normal if we do unmount the mass storage in android api level.
all the information about how to do it i found on XDA forum.
i do some research also code this app
version 2.1
fix sometime fail to mount back to external_sd folder
version 2.5
fix sometime got to bluescreen on windows
version 3.0
fix bluescreen on windows
using different approach to unmount the external SD card
version 3.2
bring back native method to mount and unmount, its speed up abit when using native method
by check the box to enable native mode
version 3.3
support Jelly Bean
thanks are goes to XDA Members
UMS_mode.apk
UMS_MODEv2.1.apk
UMS_Modev2.5.apk
UMS_ModeV3.0.apk
UMS_ModeV3.2.apk
UMS_ModeV3.3.apk
its working good tnx mate
Thanks for app. It is amazing
Best regards,
It does not mount back SDcard to /mnt/sdcard/external_sd after disconnect, so have to reboot after use it.
MTP is working but external_sd is empty.
your welcome guys,
@m0b :
i think you forget click on "back to charge mode"
bullghost said:
your welcome guys,
@m0b :
i think you forget click on "back to charge mode"
Click to expand...
Click to collapse
No, i try it, but it does not help, only reboot.
m0b said:
No, i try it, but it does not help, only reboot.
Click to expand...
Click to collapse
try the version 2.1,
i fix it
bullghost said:
try the version 2.1,
i fix it
Click to expand...
Click to collapse
now ist fine for me, tnx!
m0b said:
It does not mount back SDcard to /mnt/sdcard/external_sd after disconnect, so have to reboot after use it.
Click to expand...
Click to collapse
With the first version I have access to the card. After disconnecting I have to reboot the phone, so I can regain access to the card.
bullghost said:
try the version 2.1, i fix it
Click to expand...
Click to collapse
Version 2.1 gives reproducible blue screens with Win7 x64 SP1 at the first link when I confirm the superuser, or in further tries, when connect the USB cable.
Only uninstalling the apk helps to solve the problem.
A little off topic:
After UMS_mode.apk does not work for me, here is another way to access both memory cards in the P880 (and any other Android-Device) from Windows OS:
Install Total Commander (Shareware): http://www.ghisler.com
Install Total Commander Plugin "Android ADB" (Freeware): http://www.totalcmd.net/plugring/android_adb.html
Android device driver has to be installed too!
Through links, both SD-Cards appear with 3 differen pathes in the P880 operating system.
The external SD-Card has its mount point in (!) the internal SD-card:
Code:
Internal SD-Card:
\\\ADB\LG-P880\data\media\
\\\ADB\LG-P880\mnt\sdcard\
\\\ADB\LG-P880\sdcard\
2. external SD-Card:
\\\ADB\LG-P880\data\media\external_sd\
\\\ADB\LG-P880\mnt\sdcard\external_sd\
\\\ADB\LG-P880\sdcard\external_sd\
Bud Cord said:
A little off topic:
After UMS_mode.apk does not work for me, here is another way to access both memory cards in the P880 (and any other Android-Device) from Windows OS:
Install Total Commander (Shareware): http://www.ghisler.com
Install Total Commander Plugin "Android ADB" (Freeware): http://www.totalcmd.net/plugring/android_adb.html
Android device driver has to be installed too!
Through links, both SD-Cards appear with 3 differen pathes in the P880 operating system.
The external SD-Card has its mount point in (!) the internal SD-card:
Code:
Internal SD-Card:
\\\ADB\LG-P880\data\media\
\\\ADB\LG-P880\mnt\sdcard\
\\\ADB\LG-P880\sdcard\
2. external SD-Card:
\\\ADB\LG-P880\data\media\external_sd\
\\\ADB\LG-P880\mnt\sdcard\external_sd\
\\\ADB\LG-P880\sdcard\external_sd\
Click to expand...
Click to collapse
thanks bro , here version 2.5 will fix the bluescreen
Thanks a lot! useful for syncing with doubleTwist. can't stand the LG PC Suite its too slow.
Sent from my LG-P880 using xda premium
version 3.0 relase fix bluescreen again,
if you suffer on always media scanning you can turn it off on
setting -> application -> find "Media Storage" -> disable
Wow!
This is the greatest thing created for this phone so far.
MTP is painfully slow, doesn't work with cars/stereos/etc, requires installing drivers everywhere I go, crashes all the time, doesn't allow access with a file path, and somehow caused my sd card to wipe itself three times in two weeks, so this was a major issue for me that was making me regret buying the phone.
Initially after installing this app (v3.0), I had to repeatedly toggle UMS/MTP mode and plug/unplug my phone from the computer several times before it finally started working, but now it's perfect.
If you have a paypal or flattr link, and I'll send something your way. Or put it on the Play Store so I can buy it and update
Thanks!
thanks
ben! said:
This is the greatest thing created for this phone so far.
MTP is painfully slow, doesn't work with cars/stereos/etc, requires installing drivers everywhere I go, crashes all the time, doesn't allow access with a file path, and somehow caused my sd card to wipe itself three times in two weeks, so this was a major issue for me that was making me regret buying the phone.
Initially after installing this app (v3.0), I had to repeatedly toggle UMS/MTP mode and plug/unplug my phone from the computer several times before it finally started working, but now it's perfect.
If you have a paypal or flattr link, and I'll send something your way. Or put it on the Play Store so I can buy it and update
Thanks!
Click to expand...
Click to collapse
thank you , as far as you like it , is enough for me
ben! said:
This is the greatest thing created for this phone so far.
Click to expand...
Click to collapse
I can not confirm unfortunately.
I wanted to give the app still a second chance and have installed 3.0.
Then I restarted the phone, without starting the APP before.
Now it hangs on startup LG boot logo.
Even without the second SD card the same problem.
Any idea without factory reset or flashing KDZ?
My phone is still stuck in boot, but I have an access via adb shell to system.
Unfortunately I have no permission to access "/data"
Could anyone tell me the aplication name of this UMS-Tool under "/data/data" ?
I only found "com.noshufou.android.su" in classes.dex, but don't know wether this is right:
Code:
[email protected]:/data $ run-as com.noshufou.android.su
run-as com.noshufou.android.su
run-as: Package 'com.noshufou.android.su' is unknown
[email protected]:/data $
Ok, I guess it's not quite working perfectly for me now that I've used it a bit more, but I still love it.
1) it's really tricky to get it working initially. I almost always have to toggle it multiple times and sometimes reconnect the usb cable.
2) like someone else mentioned, it never remounts the SD card so I have to restart the phone to get it working again after I'm done.
I have not had any problems on boot like BudCord.
I'm running stock firmware 10f.
Anyone have v3 hosted any where else? I can't download from media fire.. no captcha support..
Tried stock browser, dolphin, and chrome..
Any chance to get it working on mac os x (10.6.8) ?
For the moment it is the only default i found with this phone : the lack of "connections" with Apple's OS :/
PS : I searched on the web and I found a solution for Mac OS X users : Android File Transfer (on the official website).
Sorry I can not the url because I am new on this forum.