Related
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
aikeru said:
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
Click to expand...
Click to collapse
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
deekjx said:
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
Click to expand...
Click to collapse
Did anyone try this solution?
Since the bootloader is still there all you do if not able to flash via async when in android is flash via bootloader
Moved to general as not ROM Dev.
Thanks for the information, guys!! I will have to try it out over this weekend and see how it goes...
I can confirm that flashing via bootloader works fine, also flashing from SD works as well, in fact I keep a 128MB sd with a WM kaisimg.nbh on it handy just in case I need to flash a good WM rom for some reason.
Is there an Android OS with everything working on the Kaiser?
Dukenukemx said:
Is there an Android OS with everything working on the Kaiser?
Click to expand...
Click to collapse
You can see in different post of android rom what works and what doesn't works.
actually, Bluetooth and camera never works for in android 2.x build and some other apps doesn't works
I've been running Android for a few weeks now from this thread:
http://forum.xda-developers.com/showthread.php?t=614382
I've found everything to work with the exception of Bluetooth, video camera (normal camera works fine), and the barcode scanner. Also, my battery life is cut in half, but I have an extended life battery so I get a day or two out of it.
I prefer this method as you can just boot Android at will and can soft reset to go back to WinMo.
Just to let everyone know I did flash WM back just fine since I have HardSPL 3.56 and used the stylus to press the reset + camera button at the same time to get to the tri-color screen.
From there I flashed from USB without any problems.
Thanks again for all the help!
I am having problems reverting back to WM after attempting to install android to NAND. Something happened where the only way I was able to get to the android installer would be if I had the KAISDIAG.nbh file on the SD card so it would get past the tri color hard spl screen . Well as a result, I can't get into boot loader. It shows that screen for a split second, then if I do camera + power and then reset. Then I have to pull the battery. Can someone help me? It seems like it will only go into the Android bootloader, which obviously won't allow it to install a WM rom. SD flashes are my only choice because the usb port is pretty messed up. Any help would be greatly appreciated. Thanks.
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
zenity said:
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
Click to expand...
Click to collapse
Thanks, but unfortunately this still did not work. Have any other suggestions? I think the only way will it even do anything is if I have the KAISDIAG.nbh file on the card. It recognizes that, but then goes straight to linux. IDK what else to do. Could you be a little more clear on the procedure for getting into the bootloader? Thanks.
Ok please follow these steps carefully.
1. Format the SD card, make sure you are formatting it as FAT32, not FAT.
2. Download a Winmo Rom from somewhere handy.
3. Extract the Rom to a handy folder, find the RUU_Signed.nbh file, rename that to KAISimg.nbh
4. Copy the KAISimg.nbh file to the SD card. You should only have one file on the SD card, no folders just the NBH file.
5. pull the battery from the phone, wait at least 5 minutes.
6. Replace the battery. Press Power button, and hold down camera button, until the tri color screen appears.
7. The screen should now change to a white one, and when it's checked the nbh it will ask you to press power key again. do that.
8. Now it should flash the rom, this should take a while, 5-10 minutes, once it's finished you should get a message of success.
9. Now pull the battery again, wait 5 minutes, replace the battery, and power on, you should now boot into Winmo.
Hopefully this should solve your problems, if not then let me know which setp failed and we can work on that stage.
Finally, don't panic, take it slow, it'll all work out
Thanks, but the problem starts at number 6. I am supposed to press the power button, release it, and hold the camera button till it gets to the white screen, right? It's still stuck at the splash screen. I tried holding both and that didn't work either. Anything else I can try? I hope i'm not screwed?
If I put the battery in, boot it up, then push the camera and insert the stylus into the reset hole, it gets to the tricolor screen, then for about 0.5sec it flashes the white screen with a message saying "No image File." I know for sure the .nbh file is there.
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
zenity said:
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
Click to expand...
Click to collapse
Unfortunately, as much as I wish it was, it is not the problem. I'm on a Mac, but booted windows 7 to be make sure it was formatted to FAT 32, which it was. Is there some way I can fix permissions? Every time it runs, I keep getting the error saying that it is in read only mode. I obviously need to get it into writing mode. I don't think the fix permissions option on the installer did anything either.
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Tilt Fanatic said:
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Click to expand...
Click to collapse
Alright, I'll try and sum up your experiences. Tell us if we're missing anything;
You have the following symptoms
Linux Android-installer works
Tri-color bootloader semi-works
You cannot use the USB
You cannot install polymod's Eclair build
Now, you have mentioned a couple of things you have tried, such as
Replacing the Linux NBH with another version
Fixing permissions on the SD-card
Fixing permissions through the Android-installer
Flashing a WinMO ROM through SD card
You did mention getting other behaviours when you switched to another NBH, such as "KAISDIAG.nbh" not being required.
Now, this is a long shot coming from me, as I have had no troubles with flashing, and the fact that I can use my USB, but since your phone is pretty messed up I guess it can't hurt as a suggestion;
You can flash to other NBH's I take it, as you mentioned you did a downgrade. What I'm a bit curious about is whether you did try to flash to a WinMO rom when you had downgraded to your current NBH.
Also, you said the previous NBH required you to have "KAISDIAG.nbh" on the card to even get working. Did you try and rename a WinMO-ROM's NBH to "KAISDIAG.nbh" and flash that? Might be that the flasher is really constrictive with the file names.
EDIT: Oh, and what about trying to run other Eclair builds? Just to see if you can nail it down to this being a problem of the builds or something more bound to the actual hardware/SPL/NBH's.
So first of all i must say that im a completly noob at the android instalation on kaiser
I search for a noob tutorial but i coudnt fiind can someone post here a tutorial including files thanks
Here is the Guide in Sticky
How to replace Windows Mobile with Android (Guide) by Dukenukemx
scroll down to Installing Applications Onto SD Card using Ext2
This should help. The guide help me greatly, very easy to follow.
Hope this helps.
Its not tricky, I mean even I can do it, come on
I did edit a wiki page on this, but appears to be down, so here goes, from memory.
Backup any data first, just in case, not taking any responsibility for loss of data.
Firstly ensure your SD card if formatting correctly (FAT32), use on Gparted (linux live CD) to do this, (for me, I created two ext 2 partitions as well as I thought this would work best, works for me).
You then need the HaRET application to allow you to run Android. Google "haret.exe"
Extract the files this should create the right directory.
You then need to choose a build, this is personal choice, but I'll post the one I am testing right now. milanche's CyanogenMod 6 Kaiser
Put the installandroid.tar into the folder you created above.
Move to your SD card.
Find and run HeRET.
When screen shows text, tap and hold the center of the screen until you get a menu.
Choose install (ensure the options are set to SD).
Select Install
Once done, select Quit.
This then installs Android and can take a while, just leave it to get on with it.
You should then been booted into Android.
I might have forgotten something, as I am doing this from memory, but it should be fresh since I installed this last night.
Looks good to me, nice guide, don't think you missed anything
Thatnk you Zenity, but I know I couldn't have done this without your help in the begining when I first tried it. I know how it can seem all a bit over whelming.
I know a lot of people say 'search for it' but I did that just to see what I would find, and to be honest, I didn't get anything but that was of any use, so I can sympathis the search doesn't always get you the right results.
I could not remember the direcotry names when I wrote that at work and had to do it in a hurry as the entire office can see my magnified screen so it was a quick brain dump, not as nice as I would have liked to have written it given the time (which I did on the wiki but its down).
Anyway Keeps it fresh in my mind too.
I can only do this when I'm given the right files, I got confused myself when people started talking about different zImages. I tend to go for the builds where everything is bundled into one packing, as some can seem fragmented, ie Fresh Foryo, I don't doubt that it may be a good rom, but its deleivery is complicated (for me ).
Wish I had more time an experience to make my own build, I have done a bit of linix hacking in my time with shell scripts (getting wifi cardds working ona laptop etc), Its all interesting stuff.
thanks guys u helped me alot in the end i will instal android on an ext2 partition
Dear Leona,
The link seems no longer valid, can you tell where to find the latest HaRET application? Besides, how should I format my SD card? by special software? Thanks.
Dave
If you'd have problems with using Gparted Live CD like me... just because it does not mount SD card in adapter... here is what I did to partition the SDHC 4GB card...
I booted with HARET but did not select to install.. it gracefully fails to terminal
command: su
command: fdisk /dev/block/mmcblk0
deleted all current patrition (d)
created new partitions whith calculated size (8192 for 256MB)
changed type of the first and biggest patririon to FAT32 (t => c)
written all the changes to the partition table (w)
Than you should take out the card before rebooting and format FAT32 partition in win to upload all te android boot files, rebot the phone and follow with instalation...
But I must say, now I am using Scooters Cyanogen in NAND and it it far far easier
After I choose run, then a list of Linus commands ran, then it said
:loseup:/dev/block/loops: No such file or directory
Failed
Failed to reach system.img on SD card
By the way, anywhere I can download a complete set of files for running? Thanks.
try this:
http://forum.xda-developers.com/showthread.php?t=813382&page=31
look for the 4th post...
or this:
http://forum.xda-developers.com/showthread.php?t=855733
read a lot before attempting to do anything! use the search tool too, could be of some help.
For SD Partitioning, I remembered this Thread, which might help.
http://forum.xda-developers.com/showthread.php?t=619290
Sounds like you are not holding the centre Dpad button (or pressing the centre of the screen) while haret is loading, yes this can be Hit and Miss it winds me up no end.
If you have access to a Linux machine (or boot a Live CD), as well as being useful for SD partitioning it also maybe used to try out Atools (you'll need to install python and python-tk (via the package manager)) as this will get you the right Kernels, images and configure your default.txt file for you, though I haven't managed to get the build script bit working yet, but that is down to my lack of understanding the instructions
I've never tried to do anything beyond readily available 3rd party apps. I've never jailbroken anything or rooted. I don't know how to work with ROM's and I've never used command prompts beyond installing difficult software on my desktop. (I'm using Win 7 on my PC) and I have no linux or coding experience. That said, I'm smart, I research things fully b4 I actually DO anything & I follow directions exactly when i do something unfamiliar.
I bought my Desire about 45 days ago thru USCC. Stock it's running 2.1. On Fri using UnREVoked 3.21 I tried to root. It appeared to work. I have the Superuser file at least...
However, when I followed unlockr.com's tutorials for downloading & flashing ROM's it became obvious that something was not right (screens weren't the same, options weren't the same or even close in some cases, & controls, like pushing power to go back after recovery didn't work.) The screen turned black, I had a minor heart attack & then the phone finally rebooted into it's original USCC configuration.
Now, I DID have an option to "install from SD card" but nothing that said "flash from sd card" and I'm assuming -maybe incorrectly- that there's a difference??
After 4 days of searching sites, I know there are too many posts on USCC rooting & Desire for a noob like me to know what to do. I have a mess that I need help to untangle.
Prior to my failed ROM attempt, I had installed save to sd... which I think may have moved everything to my SD card. Since rooting, I tried using Root Explorer to remove facebook, twitter, City ID etc.... EX: I can see bloatware files on my SD card, and the program SAYS it deletes them, but it reboots on exit and there's CityID again!
I can mount the SD card as a disk drive on my PC and look thru the SD card files. (some of which appear 2B duplicates. When I rooted, I installed the Hboot drivers and followed the unrevoked directions exactly. I renamed the recovery file as update and left it as a zip... but there are now two "update.zip" folders on my SD card. They are different sizes and neither contains all of the files of the other; although some of the files in each of the zip's are duplicates.
I don't know what files SHOULD be on my SD card and what is extraneous material. I don't know what I need to install to get to where I'm ultimately trying to go... which is running 2.2, getting rid of these "extra" files and gaining the ability to wifi tether my phone.
I do NOT know if I have S-off or not... and I'm not sure how to tell. AND, I'm not sure if this is the base cause of the other issues or not.
Is there anyone willing to get me thru the vast amount of material & help me to get my Desire running the way it is capable of functioning?
At this point, I'm even willing to switch carriers to get what I want if the issue is USCC's proprietary nature...
Thanks in advance to any1 willing to help out
Bethyk said:
I've never tried to do anything beyond readily available 3rd party apps. I've never jailbroken anything or rooted. I don't know how to work with ROM's and I've never used command prompts beyond installing difficult software on my desktop. (I'm using Win 7 on my PC) and I have no linux or coding experience. That said, I'm smart, I research things fully b4 I actually DO anything & I follow directions exactly when i do something unfamiliar.
I bought my Desire about 45 days ago thru USCC. Stock it's running 2.1. On Fri using UnREVoked 3.21 I tried to root. It appeared to work. I have the Superuser file at least...
However, when I followed unlockr.com's tutorials for downloading & flashing ROM's it became obvious that something was not right (screens weren't the same, options weren't the same or even close in some cases, & controls, like pushing power to go back after recovery didn't work.) The screen turned black, I had a minor heart attack & then the phone finally rebooted into it's original USCC configuration.
Now, I DID have an option to "install from SD card" but nothing that said "flash from sd card" and I'm assuming -maybe incorrectly- that there's a difference??
After 4 days of searching sites, I know there are too many posts on USCC rooting & Desire for a noob like me to know what to do. I have a mess that I need help to untangle.
Prior to my failed ROM attempt, I had installed save to sd... which I think may have moved everything to my SD card. Since rooting, I tried using Root Explorer to remove facebook, twitter, City ID etc.... EX: I can see bloatware files on my SD card, and the program SAYS it deletes them, but it reboots on exit and there's CityID again!
I can mount the SD card as a disk drive on my PC and look thru the SD card files. (some of which appear 2B duplicates. When I rooted, I installed the Hboot drivers and followed the unrevoked directions exactly. I renamed the recovery file as update and left it as a zip... but there are now two "update.zip" folders on my SD card. They are different sizes and neither contains all of the files of the other; although some of the files in each of the zip's are duplicates.
I don't know what files SHOULD be on my SD card and what is extraneous material. I don't know what I need to install to get to where I'm ultimately trying to go... which is running 2.2, getting rid of these "extra" files and gaining the ability to wifi tether my phone.
I do NOT know if I have S-off or not... and I'm not sure how to tell. AND, I'm not sure if this is the base cause of the other issues or not.
Is there anyone willing to get me thru the vast amount of material & help me to get my Desire running the way it is capable of functioning?
At this point, I'm even willing to switch carriers to get what I want if the issue is USCC's proprietary nature...
Thanks in advance to any1 willing to help out
Click to expand...
Click to collapse
i cant tell you how to fix it, but what i can say, is if you really borked it, you can take it into a uscc store saying you have no idea what happened. i used to work for uscc until about 2 months ago. until that time, out of the 3 corporate stores i was working in, not one associates knew what rooting was. and none of the "smartphone team" had either. so they would most likely just send you a replacement. good luck
I thought about that... And I really don't even mind paying for it if I need to replae the phone, I will... But I figure at this point, worst case scenario I have aphone I can "play" with and figure out IF I can do any of this stuff successfully. I've discovered in the last year that I sort of have a talent for figuring this stuff out. This is the first time I've ever needed to find help with a problem and I've built several complete systems. I'm hoping there's someone who might be willing to suggest a course of action. If you have any ideas- even if I brick the darned thing- I'm willing to give it a try!
Thanks to anyone brave enough to reply!
Bethyk
Sounds like the second tuturial you were following was trying to root your phone again, but with the older method.
Turn on your phone holding volume down. You will get a white screen with some options in the middle, select recovery (it says at the top of this screen s-off or s-on, yours should say s-on, this is how to find this out.)
When recovery loads it should say clockwork recovery, a custom recovery flashed by unrevoked during the rooting process.
Use this recovery to flash a zip of whatever rom you want. Be sure to wipe data also if changing roms or any problems arise.
I've figured this much out at this point... I did root my phont with unREVoked 3.21. However, I did NOT S-OFF the device. So I'll try what mercianary suggests & let you know how it goes! Thanks a ton!
Bethy
Are you using the mouse button at bottom of phone to select in black and green recovery screen? If you are using power button to select it will give you a blank screen.
Hey Guys,
Before I ramble on about my problems, I would like to thank all the amazing devs that work night an day to make our phones awesome. I have been reading these forums for a couple of weeks and have seen how helpful everyone in these forums are to us noobs.
I'm not new to Rooting (Rooted my G1 a while back and Jailbroke a 1st Gen iPhone way way back lol), but this is my first time Rooting my 3G Slide, which I have had since they were first launched.
I am attempting the No-PC Method described here: http://forum.xda-developers.com/showthread.php?t=896148
I have been trying since last night with no success. I have followed the process step by step, to the T, and continue to encounter the same error every time I try.
I succesfully flash the ESPRIMG.zip and then go to Recovery to apply the "update.zip" file so I can go into Clockwork Recovery, however instead of going into Clockwork Recovery it just gives me the following error:
E:failed to verify whole-file signature
I have searched the forums and none of the responses and solutions have been helpful as almost all of them are users who have already flashed a ROM on their phones as opposed to the Stock one, and a lot of them seem to be prior to this new AndRoot method.
Also, I am using this method as I do not have a USB cable for my phone or a PC for that matter, and havent really researched any Mac mathods of Flashing a Custom ROM to the phone.
Any help would be mucho appreciated!
i think you have to have the update.zip file in the root of your sd card
I reformatted the SD Card and only placed the necessary files in the root of the card. There is nothing else in the card at the moment except for the update.zip file, ROM, gapps, and radio updates. I have no idea why i keep ketting this error, from all the research I've done, this should be working, but clearly there is something I'm doing wrong :-/
yixmal said:
I reformatted the SD Card and only placed the necessary files in the root of the card. There is nothing else in the card at the moment except for the update.zip file, ROM, gapps, and radio updates. I have no idea why i keep ketting this error, from all the research I've done, this should be working, but clearly there is something I'm doing wrong :-/
Click to expand...
Click to collapse
yeah, that's not good if that's all you have there. i was working with someone over at the tmobile forums who was getting the same error (http://forums.t-mobile.com/t5/myTouch-3G-Slide/Easy-root-unroot-Froyo-for-all/td-p/649239/page/6) and it turned out they had the downloaded files in a different folder, and moving them to the root made it work... you may want to try using the files you need from this link instead: http://richard.gluga.com/2010/08/complete-guide-to-rooting-and-hacking.html
I'm a newbie to the whole programming side of computers, familar with using one though. I am going through the steps of the no pc rooting, and I read through step 6 and I thought it was confusing it says...
Install And Run Root Explorer then Copy and paste flash_img and mtd0.img to /data/local on android device multi-select copy then rm r/w in program in upper left on data local folder. I am confused with the rm r/w section there, I haven't gone through the steps, just want to have a general idea before I get in there and screw something up.
Yeah, that ones a lil tricky apparently. Root explorer can be found in the market for ~$4, but if you click the link for the tmobile forum, we found that another app (free) works just as good.
I managed to make it work last night. I'm pretty sure I kept downloading the incorrect ESPRIMG.zip file from several sites. I think I was getting the original stock ROM as opposed to the Engineering Build.
Anyways, mine's working now.
As for the step 6 on the instructions. It basically means that after you paste the files you need to go back to the android system (the folder where you can see everything thats on the android) and at the very top of the window you will see a button that says "R/W" next to something like "Mount as R/O". You just need to hit that button so you can write to the folders, then go back to /data/local and long press "Image_flasher" click on permissions and make sure everything is checked, then repeat on "mtd0.img" file.
I know its a long explanation for such a small step but I try to be as detailed as i can. Hope it helped.
Get
update.zip
Put iton ur SD card
and a ROM.zip that you like n the SD card as well..
see if that works
yixmal said:
I managed to make it work last night. I'm pretty sure I kept downloading the incorrect ESPRIMG.zip file from several sites. I think I was getting the original stock ROM as opposed to the Engineering Build.
Click to expand...
Click to collapse
^ This
I just went through the same thing - I had restored my phone back to stock and then went to re-root it. I have 2 copies of ESPRIMG, file sizes as follows:
The one that was giving me problems: 145,045,641 bytes
The one that ended up working: 143,701,302 bytes
Once I used the slightly smaller ESPRIMG the process worked perfectly. When using the other one I was getting the same error as the OP.
Hey people,
Figured I would just start my own thread.
I have a Virgin Moble CDMA and it seems to be hard bricked.
With no battery in the phone plug in the USB cable to Windows computer unit vibrates 3 times and nothing more. Computer does not recognize that there is a device connected.
I created a gold card and placed the img file (Bare minimum to fix tripple vibe brick on USCC or VMUSA) from Simonsimon34's thread on the development area.
The SD is placed in the phone plugged in the USB get the 3 vibes and nothing else happens. I have tried waiting and then pushing the volume up to see if it will vibe again....it never does.
I know I am in what is referred to as "Qualcomm diagnostic mode" I have search and can not find anything helpful.
Any other ideas would be great.
KB
I had this problem in the past.
Run the RUU found here: http://www.filefactory.com/file/c4e..._1.25_0815_PRL61007_release_219164_signed.exe
It will be a slow download and you may need to try a few times.
Close all open applications. Run the RUU, but stop at the screen where you are able to choose to view the Read Me. Go to Windows Explorer, and type %TEMP% and pick the top one. Find "rom.zip". Move that to the desktop. Format your SD card (FAT32). Rename rom.zip to PG76IMG.zip. Put PG76IMG.zip on your SD card. Then hope it works.
If you're not running Windows or you have other problems or it doesn't work, I'm sure the problems can be resolved.
Thanks for the quick response. But I have already tried this.
I should have mentioned that.
Kevin
So you did Simon's method and the RUU method?
This is basically what I did..let me know if I am missing something.
I first tried what I believe is Simons method:
1. Took SD connected to computer.
2. I then used Simple Gold card v1 to create the gold card.
* I already had my gold card image from before when the phone was still working.
3. I then placed the PG file on the SD card.
*I've tried both the PG file that I got from the temp folder that the ruu creates and I also tried the PG file on the Simon's developer thread ( the one labeled for 3 vibes)
4. Put the SD card in the phone, then connected the USB to the computer.
All the phone does is vibrate 3 times.
I then tried the RUU.
1. I installed the HTC synch software on the computer
2. Connected the phone to the computer also.
I have tried both with a gold card and a freshly formatted SD card.
3 I then run the RUU.... All I ever get is a USB error stated to make sure the phone is connected.
Kevin
kmbarreiros said:
This is basically what I did..let me know if I am missing something.
I first tried what I believe is Simons method:
1. Took SD connected to computer.
2. I then used Simple Gold card v1 to create the gold card.
* I already had my gold card image from before when the phone was still working.
3. I then placed the PG file on the SD card.
*I've tried both the PG file that I got from the temp folder that the ruu creates and I also tried the PG file on the Simon's developer thread ( the one labeled for 3 vibes)
4. Put the SD card in the phone, then connected the USB to the computer.
All the phone does is vibrate 3 times.
Click to expand...
Click to collapse
When you powered the phone on did you hold the volume up and press the power button at the same time?
Yes I have.
Ok, just a thought...
Alright, I had this same problem with my VM Marvelc. I had to send it in. Don't worry. They won't be able to check to see if you've modded because your radio and hboot are totally trashed. They should just send you a new one. (If you have a warranty of any sort.)
Unfortunately I doubt that I have any warranty, I got the phone from a relative who got it at the Elan show(payed $100). It was there X-mas show, she came home with a pile of electronics (tv, android tablet, this phone....). The phone was never activated, I was just about ready too.
My wife isn't too happy that I bricked it since I can't really afford to get another one.
I've spent about a week on it and from all the research I have done pretty much any phone that is in this state either the thread just ends or they get the phone exchanged.
I sent an email to HTC but they want me to call, I'll just try to play as dumb as possible.
Well I ended up calling HTC, come to find out my phone is still under warranty even though I bought this from relative. Looks like they just go by the serial number.
Thanks for all the help, I'll be back once I get the new one.
Kevin
Awesome. And if they ask, what happened was that you were waiting to do a FOTA, but you decided to do it. After the FOTA, this problem is occurring. (Don't tell them you were messing with ROMs.)