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)
?
Related
Do any of you have a program that I could use to sync my phone to my Computer via usb? I've tried several versions of Tera Term with no success. I reached the point where I was ready to pull all of my hair out and then I remembered... I don't have anyway. Oh well. Please help I really want to upgrade my rom but I want to back up the old first. Thanks, Vern.
i think i don't understand what you're trying to do!?
Don't you use ActiveSync for Syncing with your PC?
And wtf is Tera Term???
This is what I'm trying to do:
Originally Posted by kdenninger
To back up the firmware on the MDA to an SD card (a VERY GOOD IDEA if you intend to fool around with new firmware!)
1. Get a 128MB SD card. They're cheap - under $20.
2. Insert said card.
3. Go to http://forum.xda-developers.com/viewtopic.php?t=37386 and download the aWizard utility. CID-unlock your phone. (You only need to do this ONCE, even if reflash in the future.)
4. Get a terminal program that can speak over the USB port. There is a patched version of Terraterm out there, along with a few others. You need a way to connect to the device over the USB port as an ascii terminal.
5. Turn off the phone.
6. Holding the CAMERA key, press the power button for 2-3 seconds. Continue holding the CAMERA key until it comes up in the tri-color screen.
7. Connect the USB cable. Wait until ActiveSync tries to start. CTRL-ALT-DEL Windows and kill the process wcescomm.exe (ActiveSync's communication driver)
8. Now start your terminal program and point it at the USB port. Hit RETURN and you should get a command prompt. You are now talking to the phone's boot loader in terminal mode.
9. Type "r2sd all" and hit RETURN.
10. If you get a security level violation, you DID NOT CID-unlock the device. Go back to step #1.
11. The ROM image (all of it) will be written to the SD card. Several messages will be displayed while this is in progress. Note that this is NOT - I repeat - NOT - a filesystem-formatted dump - it is a RAW image of the ROM with some checksum information included. Anything on the SD card will be destroyed - don't do this with a card that has data on it you care about!
12. You can stick this card somewhere to be used for restoring. If you want to save the image off the card to your computer, stick the SD card in your computer and then dump 128MB of the card starting at the front (the actual dump is about 80mb but will always be less than 128MB, so that's "safe".) You will need a tool like "psdread" or any other tool that can do byte-level I/O to the SD card in your PC's reader for this.
To restore a SD-card image dump to the Wizard:
1. Write the image to the SD card. Again, this is NOT a filesystem - its a RAW image! Unless you saved the image to the card from the Wizard initially you will need a tool that can do a raw write to the SD card in your computer.
2. With the Wizard OFF, insert the card into the SD slot.
3. Hold BOTH the CAMERA and VOICE keys and press the power button for 3 seconds. Release POWER.
4. Look CAREFULLY at the Wizard screen. The backlight WILL NOT BE ON! It will tell you to press the VOICE button if you wish to restore the SD card image. This message only appears for a few seconds and the backlight is OFF! If you wait too long you will end up at the tri-color bootloader screen. Press the VOICE button (if you still have it down, let up on it then press again.)
5. The restore will run. Note that the backlight IS NOT ON during this process! You may need a flashlight (or very bright ambient light) to be able to read the progress meter.
6. When the process is complete it will tell you to press "any key". Do so and you're back in the tri-color bootloader screen.
7. Turn off the Wizard with the power button. When you turn it back on, it will hard reset just as if it was brand new off the firmware you just restored.
Note that this is the ONLY way to recover from a bricked phone if you try to load the wrong firmware file using one of the "forcible" methods (e.g. aWizard) on a non-CID-unlocked phone, and have bypassed the normal protection methods as ActiveSync cannot get back in there under these circumstances.
I strongly recommend that if you're going to futz with firmware, that you get yourself a 128MB card, make one of these dumps, and TEST the restore before you play around. This will recover from almost any botch - the only exception is loading a firmware file via some means (e.g. "aWizard") that the phone cannot execute at all.
Note that I do not know if this will get around the "boot loader version is too high" problem - I'm not willing to try it until I have an official T-Mobile update with a newer boot loader.
This same method for both dump and restore works on the SDA as well.
13. Overclocking the MDA (do so at your own risk!)
Quote:
Originally Posted by Scaw
Use Smartskey, read about it in this article on my HTC Wizard Blog. No specific ROM required, overclocking integrated. You need to download OMAP Clock seperately, it is available from the same article. A small tutorial in PDF format is included in the .zip with Smartskey. Don't forget to remove the ";" (without the quotes) at the beginning of the overclock settings in the configuration file!
How fast you can clock it depends on your device, it's just a matter of trial and error. 240 seems to be safe for the majority of HTC Wizard owners. No need for extra tools to wake overclocking up after a soft reset or standby. I haven't noticed severy battery drain, I can easily use my device a whole day and come home with the batterie well over 50% charged.
It's just a great little program. The integrated overclocking comes as a bonus to the tweak that the program was actualy made for, remapping buttons so you can open the start menu without using your stylus and close programs without using the stylus.
Have a look around on the HTC Wizard Blog, there is lots of other stuff that you may find useful.
And Number 4 is WTF Tera Term is. Thanks.
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.
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 !
First of all I would like to say hi to everybody, this is my first post on this awesome forum I found just today. I would also like to say that I bought my first smartphone a few days ago(HTC Wildfire of course) and when browsing on the internet trying to find out stuff I could do with the new found device I found a lot of people reffering to something called 'rooting' and 'flashing' and 'ROMs' and that doing this enables your phone to have a lot more new functions and stuff like that.
Therefore I have some questions to ask you nice people, so here they are:
- What is 'rooting', 'flashing' and what are 'ROMs' in the first place?
- I found a lot of abbrevations when people described 'rooting' their phones which I did not understand so I'm kindly asking if anyone could please explain the process clearly? (is this the correct process? -> forum.xda-developers.com/showpost.php?p=7895908&postcount=127 , if it is what is the OTA update?)
- If someone could please explain the process of 'flashing' to me?
- Are there any recommendable 'ROMs' I could try?
I truly thank anyone who would be able to explain this to me and take their precious time to do so. I'm sorry if my questions seem silly but I'm extremely new to the smartphone android thing and therefore I don't understand everything.
Thank you again for your replies, ciroman
- What is 'rooting', 'flashing' and what are 'ROMs' in the first place?
Rooting = gives you/apps on the phone acess to root acount in android wich gives you acess to do things wich you can not do normally. read more about root and superuser(su) here: http://en.wikipedia.org/wiki/Superuser
ROM = is sort of the operating system wich most often comes in zip files and is possible to flash to the phone with a custom recovery. this often include apps and modifications wich is made of the person who makes the ROM. also includes superuser acess (root) not allways but often.
custom recovery = a recovery mode wich allows you to do backup of your current settings and evrything else you have on the phone. also makes it possible to flash ROMs wich you have saved on the SD-card
Flashing = this is when the recovery takes your zip file and exctract it to your phone. when this is done you have a new "operating system" on the phone
- I found a lot of abbrevations when people described 'rooting' their phones which I did not understand so I'm kindly asking if anyone could please explain the process clearly? (is this the correct process? -> forum.xda-developers.com/showpost.php?p=7895908&postcount=127 , if it is what is the OTA update?)
Yes this looks like the process of rooting/installing a recovery.
OTA = Over The Air
- If someone could please explain the process of 'flashing' to me?
wont explain this.. it should be explained somewhere else..
- Are there any recommendable 'ROMs' I could try?
There are only a few ROMs out at the moment..
The only one I can recomend for you rigth now is wildpuzzle ROM by danne_jo there is more ROMs out but I dont know how stable theese are.
Click to expand...
Click to collapse
I dont garantue that this info is 100% correct and anyone who feels like please correct me if im wrong.
I also take no responsibility for any damage made to your phone by following any of the above information.
Thank you so much for your quick explanation. I must say though that searching for how to flash and root this phone was quite painful for a newcomer like me-took me hours to find the first part and then some to find the second.
I hope following these two guides will get me there
shinelt said:
Prep
Before beginning the process, I would recommend doing the following to your phone:
(1) If you have the original unrevoked root installed, uninstall it by using "Menu", "Settings", "Applications", "Manage Applications" and scrolling to "Unrevoked" at the bottom. Tap it, click "Force Stop" at the bottom and then "Uninstall", "OK" to uninstall it. Then power off/on your phone just to be sure.
(2) If you haven't already installed the OTA 1.47 update, do it now: "Menu", "Settings", "System Updates", and "HTC software update" at the bottom, then click "Check Now" to get the 1.47 update. If you do this update, it takes up to 10 minutes so be patient and let the phone reboot (a few times) until it is done. Then once the update is done, power off/on one last time to get a clean start.
(3) Set your phone to "Charge Only": "Menu", "Settings", "Connect to PC", tap "Default connection type" and select "Charge Only".
(4) Enable USB debugging: "Menu", "Settings", "Applications", "Development", and put a check in "USB debugging".
The root process
(1) Go to Control Panel on your system and uninstall any "HTC" software such as "HTC Sync".
(2) Download the unrevoked3 install package: Go to
unrevoked3 recovery reflash tool, v3.0 and click "Download for Windows". Save the "Reflash-bundle.exe" file somewhere that you can find it on your system.
(3) Using Explorer, run the "Reflash-bundle.exe" file you just downloaded. It'll ask where to install it. Don't just accept the default: change the install location to a folder you can remember: it's just going to unzip some files there: it isn't really a software installer.
(4) Once the files have unzipped, go to the folder you chose in the above step. You should find an "hboot driver.htm" file in that folder: double click on that to open the html instructions on how to install the drivers. Follow the instructions in the html file starting with downloading the actual driver files at the very top. When you download those driver files and unzip those, those are the files (the folder) you'll point to in subsequent steps in those instructions. When done with the html instructions, you should have drivers installed and shouldn't have to come back to this step.
(5) At this point, if you needed to install the drivers, you are probably still sitting at a boot menu on your phone. UNPLUG the phone from USB and select "Fastboot" and then "Reboot" to reboot the phone to restart it. Before the next step, your phone should be on and booted up in its normal operating state (not some boot menu).
(6) If you are running anti-virus software, turn it OFF or disable it now.
(7) Now go to the folder where you unzipped the reflash bundle (step 3 above). In XP or older systems, just double click the "Reflash.exe" file. On Vista and Win7 systems, I'd recommend right clicking on "Reflash.exe" and selecting "Run as Administrator". While this may not be necessary, I know that some USB drivers get really mad if you try to access the USB port without admin privileges (sorry, I'm a coder so I run into that stuff and warn you so you don't have to) so I did it as a precaution.
(8) You should get a window with "Unrevoked 3" on it (on the computer of course). Just follow the instructions in smaller font below "Unrevoked 3" to finish rooting. Note that when it says "Waiting for device", it wants you to plug your phone into the computer via the USB cable. Note that it wants the wildfire to be fully booted normally (not in the Hboot or recovery menus). The prompts at this point are very specific so no need to repeat them. If all works as it is supposed to, the only thing you really have to do is scroll to an item on the phone and select it when instructed. The rest is automated and should result in a "Done" message. The whole thing at this point took maybe one minute so it isn't something you have to wait for or stare at for a long time so if something gets "stuck" for a while... there's likely a problem.
(9) Don't forget to turn your anti-virus software back ON.
Now, when I followed these steps on my Win7 x64 system, reflash.exe detected the phone and started working (we're in step 8 here) but about 4 messages into the process I got the "communications lost... try again" message that unrevoked refers to on today's Twitter. Some say that (contrary to step 1) installing HTC sync actually solves the problem. I didn't try that. After about 6 tries on my Win7 system and even pulling some "tricks" to try to pause reflash.exe at certain points, I gave up and simply booted my old XP laptop and repeated the above steps and it worked perfectly the first time. At the point of the failure, you hear the two tone usb-device-disconnected sound followed by a use-device-connected sound about 20 seconds later. Somewhere in between is where the "communications lost" message appears so it looks like some sort of USB ack/nack issue. Hopefully it'll be resolved soon. My best advice if you get that error: try a new machine. The XP machine that worked perfectly for me had never seen any HTC software. Maybe that helped. And maybe after I uninstalled the HTC software on my Win7 x64 system (the one that didn't work) I should have rebooted before continuing: I didn't because it didn't prompt for a restart and I couldn't find anything "HTC" running in task manager.
do wipe data/factory reset
put all files to sd from puzzle rom. ( go to partitions menu > mount usb storage)
(put those 01 , 10 , 52 ,300 , 400)
go to nandroid> backup
go to install zip from sdcard
and install files from 01 to 400.
go back and press reboot system now.
Click to expand...
Click to collapse
fireplayer said:
I'm just as n00b as you on this. But I'll help you out...
1. After using unrevoked once - reboot your Wildfire.
2. Go to first page on this thread that you read right now.
3. Download the things you want to flash - all links are in the 1st post. - put them on your SD-Card - start with flashing 0001_WildPuzzleROM_v2.zip first - to do this - download that file and save it - anywhere on your SD-card (somewhere you'll remember where you put it). Download and save all you want from 1st post on this thread - to your SD-card...do NOT open the zip files - just copy them to the SD-card.
4. Turn off your Wildfire
5. Turn on your Wildfire while holding Volume Down button - you have to have your SD-card with all the files you want - inside your phone now.
6. This get's you to the boot screen. Wait for HBOOT to say no image...blabla..
7. Push Volume Down to get to option "Recovery" - press Power button.
8. Phone will Reboot to a white HTC screen - and from there go to ClockworkMod Recovery screen - if you did everything correct.
9. Press Volume Down several times - until you get to option "nandroid"
10. Press the round button at the bottom of your Wildfire - the one you use to take pictures when using Camera functions, let's call it the Camera button.
11. You see "Backup". Press Camera button, and wait until it's done backing up your system. Do NOT turn off your phone! Wait until it's done. It will say Backup complete!
12. Next if you want. But only if you want - you don't have to - you can Wipe / Factory Reset your phone, saves a lot of ROM space and Memory. Phone WILL be slightly faster if you choose to do this - but all your programs and settings will be gone - Your choice.
IF you do NOT want to Factory Reset your phone, skip steps 12 & 13.
IF you want to do this then push Volume Down until you get to option "wipe data/factory re" (probably reset, but only show until re on my phone) and then press the Camera button.
13. As to make sure you really want to do this, you need to confirm... push Volume Down until you reach option "Yes -- delete all u" - then press Camera button and wait.
14. Now you can start flashing. Push Volume Down until you reach option "install zip from sdcard" Press Camera button.
15. Push Volume Down until you reach option "choose zip from sdcard". Press Camera button.
16. Find where you put the files you downloaded from post 1 on this thread. Choose 0001_WildPuzzleROM_v2.zip. Press Camera Button.
17. Push Volume Down until you reach option "Yes - Install 0001_W". Press Camera button. Wait for it to be done.
18. Repeat steps 14-17 with the other files you want to flash. IF you want to Flash files that are 0900 or higher. Reboot and change Wallpapers before you do.
To reboot Press Power button to go back and Press Camera button on option "reboot system now". Then repeat steps 5-7. If you need help changing wallpapers too let me know and I'll try to explain that too.
When done flashing the files you want. Reboot. And you're done.
First reboot after flashing Wild Puzzle Rom takes a very long time. Be patient.
I hope this guide made sense. If there's anything unclear let me know and I'll be happy to clarify. Thanks and Good Luck!
*EDIT* Just saw that someone else made a guide too, well at least there are people wanting to help us n00bs. Thanks. and I think both guides should work. Hopefully you'll make some sense of them *ENDS EDIT*
Click to expand...
Click to collapse
Thanks again!
Obviously this guide owes a huge bunch of thanks to "TheManii", "Giveen" and other folks who can't be named on this forum. I have tested this on both a Streak 7 WiFi and a Streak 7 4G. In both cases they had the Stock Honeycomb already on them. So if you are coming from some other version of Android you may wish to reconsider
1) Download the Fastboot+ADB.zip file for Clockwork Mod 5.0.2.7 from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
2) Download the Clockwork mod 5.0.2.7 file from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
3) Go into Settings->Applications and turn on "Run Applications from Unknown Sources"
4) Go to Development Settings and select "USB Debugging"
5) Unpack the Fastboot+ADB file into a directory on your computer where you can find it again
6) Attach the Streak to your PC, and copy the "Drivers.zip" file from the root directory of the Streak (/sdcard) to the same directory where you unpacked the Fastboot file
7) Turn off your Streak after you have copied this file, and disconnect it from the PC
8) Unpack the drivers.zip file and find the "Setup.MSI" file. Execute this file to install the drivers you will need
9) Put your Streak into Fastboot mode - i.e. turn it off, then turn it on by pressing the Power button while holding the Vol DOWN (-) at the same time. This can take up to 20 seconds
10) You will get some red text followed by a white line saying something about Fastboot USB downloading is active
11) Connect the streak to the PC now, and it should install an Android ADB driver. Depending on what you have already setup you may get some drivers installed successfully, and some not. In general if you've been following this guide, you'll be ok
12) Open a command line for the folder where you have fastboot and your recovery image (ClockWorkMod) - in windows navigate to the folder, and hold the shift key while right clicking
13) On the command line type the following:
fastboot -i 0x413C flash recovery recovery.img (where recovery.img is the ClockworkMod or other recovery file)
14) On the command line type the following:
fastboot -i 0x413C reboot
15) Your device should now reboot
16) To get it to reboot into CWM, turn the Streak off, and then turn it on again while holding the Power Button and Volume UP (+) at the same time. This may take up to 30 seconds
From here you would follow the normal CWM options to install just the root files (Superuser7 for one example) or install a custom ROM.
It turns out steps 9 - 15 are also a great way to fix the problem when your Streak comes up and starts asking for a Password when you never setup a password. For some reason installing one of the custom ROMS also installs a version of CWM that is not as recent as the 5 series, which can lead to issues with the signature verification (i.e. when things go "boom", Android sees the partition as encrypted rather than just "locked"). So steps 9 - 15 allow you to put in a later CWM which does a proper wipe, and you're back in business. Have to reinstall apps, but the data is left alone.
Just in case I'm not the only one who has run into this
Ok, I used this guide to modify my Dell Streak 7 wifi. After I was done my screen kept flickering and I put it back to stock thanks to AndroidOVERALL putting together a post on how to complete the restore.
I have searched about the screen flickering but didn't find a resolution. Maybe I missed it, but it seemed that others had the same issue and it was either a hardware problem, the brightness was adjusted, or auto rotate was disabled. I tried adjusting the brightness settings and many other settings but the issue was not resolved until I returned everything to stock.
I have a Dell streak 7 wifi, US version with Honeycomb.
Please point me in the right direction if this issue has been resolved and I missed it. If not any suggestions?
Did you load a custom ROM after following these steps, or did you just reboot aft getting CWM installed. Usually the flickering comes from an issue with the video driver (so can be software if a bad driver, or hardware if it's only marginally in spec).
For any one who gets to the end of the steps and now can boot in go CWM but doesn't know what to do about getting rooted.
Very very Simple.
Download Superuser7.zip
http://www.tablet-cables.com/streak/tools/root/Superuser7.zip
Have your Streak booted normally and USB cable hooked up.
Move to the internal Memory Superuser7.zip
power off device
Power back on using Vol UP & Power Button
Select 2. Software upgrade via update.pkg on SD card and press power
CWM will load.
Select install zip from sd card and power to enter.
select Choose zip from internal sd card and power.
use Vol UP to go backwards to your files and select Superuser7.zip and hit power
move down to YES - Install Superuser7.zip and hit power
thats it. its rooted.
goto ++++++++ Go Back+++++++
and reboot system now
and let it reboot.
Not necessary, but I'd suggest running Superuser and hitting the Knob icon top right (settings) and scrolling down and updating Super User.
Hope this helps someone who may not know where to get Superuser7 and what to do after following the great guide above.
thanks!
nothing sucks worse than a bad download -- happend TWICE! (dayum!)
got rewt?
Help?
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
blastedmax said:
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
Click to expand...
Click to collapse
It's saying that it is looking for an SD Card and not finding it, so that certainly makes sense. However, it sounds like it is looking for "update.pkg" rather than "superuser.zip", so is it possible you accidentally selected the "Update" option in CWM rather than the option to select a file?
He doesnt have clockwork mod installed, you must have CWM installed to flash zips
OK, I have a new Streak 7 t-mobile with HC 3.2. I plug it to the pc running xp sp3, and it needs drivers for MTP and Streak7. I pointed to the Fastboot+ADB folder I extracted for the Streak7 driver and it installed Android ADB Interface. Pointing there for MTP fails to find a driver. I can't get to the internal SD to get the drivers.zip because my computer won't recognize the Streak until the MTP driver is installed. After installing an MTP driver from the net, I can see the internal and external SD. I copied everything to a single folder labelled STREAK in c:\ and unplug the Streak from the pc. I put the Streak into fastboot mode (Volume - & Power), wait about 10 seconds, then plug it into the usb port. The computer see the Fastboot device and needs a driver. I point it to the STREAK folder (former Fastboot+ADB) but it didn't find a driver it liked. I tried to install manually, but there is no Android 1.0 or Android ABD Interface devices in my list. I do see Android USB Devices, but it is empty when I click on it. ANYBODY else get this, and how do I move forward? I followed the guide to the letter, and appreciate all the work & effort you guys put into making these root methods available. The Streak7 is a cool little device, but I think it will be cooler once I root it. I have rooted my Epic 4g and the wife's Evo 4g on this same computer, and I do have the Android SDK installed (even though I don't know how to use it).
OK, so I used all the same files I have here and was able to successfully get Clockwork flashed & gain root. I dunno why the xp machines don't like these files. I tried 3 other xp laptops before getting to my wife's Windows 7 laptop, which worked just as described in the very well-written guides. #MindBottling!
I cannot even find the drivers.zip in step6. WIN7x64 and a brand new tmobile streak 7. where is this thing? I looked through all the folders and subfolders.
Drivers.zip is in the main directory of the Streak. Open up ES File Manager or a similar program and you should see it. To get it to your PC, attach the Streak via USB and let it mount as external storage (default behavior I believe).
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Since this should be a common file for all SD7 units, can someone please email that file to me so i can get past step 6. [email protected]
cidand1 said:
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Click to expand...
Click to collapse
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
That said, I also can't guarantee this process will work for someone starting with Froyo. I do know there may be an issue with which version of CWM you can use in that case. As such, you may want to check one of the other guides to be sure.
EwanG said:
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
Click to expand...
Click to collapse
Explain please? Shouldn't drivers be present no matter how it's shipped? Mine came with Froyo with drivers, I OTA'd to HC and I still have them.
Ya I bought this from dell directly about 3 weeks ago. From what I have been reading on XDA, mine is definitely different. Its a tmobile streak 7.
Android 2.2.2
Kernel : 2.6.32.9
OEM ver: GLUNB1A133633
Build : 15420
Another thing I noticed is that even trying to load CWmod through fastboot, my computer does not recognize the DS7 in fastboot mode. The drivers in the fastboot+ADB zip file dont work on my computer as fastboot drivers (or maybe I should try another CPU). My cpu is an AMD 64; running win7 pro 64; i need some serious help.
I think I bricked!
Ok I followed the directions from here to root my tablet.
http://www.cesgeekbook.com/2011/12/root-dell-streak-7-with-honeycomb-32.html
All went well! Everything worked and I was rooted! did the Superuser7. Clockwork came up and installed. All went right! So I was pleased. I figured I would later than put on a ROM cause it was late. Well was going to do so and tried to go into clockwork via ROM manager. Didn't work! Kept rebooting! So I figured I would try the pother way "Press Power and +" then click to Install from SD Card to go into Clockwork. That didn't work either! Then Now it won't reboot at all! I can get into fastboot and I can get into the bootloader. But that's it! I tried to do a Factory Reset and nothing! it just stays on the Dell boot screen. Anyway to fix the problem? If so, please give me step by step directions on how to do it.
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
EwanG said:
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
Click to expand...
Click to collapse
Didn't know about the Rom Manager issue. I guess it's only good to use on cell phones? Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers. But since it's not reading the tablet. I can not reinstall CWM. The version I installed was the one from the 1st page. It's a fairly simple thing to do. But just need to get the device to be read by my laptop.
I have contacted Dell and explained to them the problem. They did say that I can return it to get it fixed. but still kind of hoping I can do it from home.
Marvelous0ne said:
Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers.
Click to expand...
Click to collapse
Not sure what you mean when you say the laptop is not reading the tablet in fastboot mode. When in fastboot it should NOT show up as attached storage. The best way to tell if it is "really" seeing the Streak 7 is in step 13 - which uses an id rather than a device name so that it should work even if the tablet isn't fully identified. If you try to perform step 13 while in fastboot, what message are you getting?