Related
Hi guys, Well after trawling through the wealth of information on this site and reading till my eyes bleed I honestly cant seem to fix this.
I was hoping and preying some amazingly talented expert here could maybe point me in the right direction.
Ok so heres whats going on. Got my HTC Desire, Told me there was a system update. So I chose to install ofcourse. Then BAM! for no reason half way through installation the phone dies. Vibrates 7 times and black screen (Searched this too) - nothing.
So pulled battery, waited for a few minutes and put in, power on. Phone gets to HTC (white screen) the freezes. Or even sometimes just switches off and vibrates 7 times again!
So I found An RUU for 3 mobile - RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.06.00.02_2_release_127568_signed
Tried running it with the phone in fastboot usb
All was going well then reached about 80% and gave me an error code 110. Telling me to download a complete RUU for my device.
Now when I power on the screen is just black, however I know it still has some functionality as I can hear the sound for device connection in Windows when I Power on holding down Vol-
now I thought I would be clever and seeing as whilst my phone was working it downloaded the "correct" update. So checked the sd card and found it in the Downloads folder. Renamed it to PB99IMG and tried booting the phone holding down the back key. But still nothing.
By the way the phone isnt rooted and is very very very new. On 3 mobile UK network.
Can anybody please give me some pointers on how I may be able to go about fixing this? Im sure there has to be some way as it still has "some functionalty" (I think lol)
Also tried the adb method of connecting or re-flashing but device is not found.
Cheers all
Sounds like the RUU is corrupt - what is the file size?
Also, is that the one your Desire came with? If not, that won't work anyway
Also, an OTA shouldn't be named PB99IMG as that's only for RUU files - you rename an OTA update.zip and flash it in recovery. Looks like you've not read enough
Hi, thanks for the quick reply.
The RUU I tried installing that failed was from:
http://forum.xda-developers.com/showthread.php?t=695667
RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.06.00.02_2_release_127568_signed.exe
Filesize is 153mb. It matched the version number that my htc shipped with and even says when running the RUU that both versions are the same. But as it failed I tried the Update from my network provider that I found on the SD card by renaming to PB99IMG.zip and holding Back and Power down.
Looks like Im buggered I suppose. Im still trying to get my phones CID as Im guessing then I can install any RUU for my phone?
I just cant access anything to get the CID
The PB99IMG can ONLY be used when extracting it from an RUU
The one you got OTA (Over The Air) isn't a full ROM - it's just a 30MB-odd update
Download the RUU from here:
http://www.4shared.com/get/t2SsuYNF...sionid=2D4E782FB44E2CF020622A15F76C1A5A.dc278
(Shipped-ROMs.com can lead to corrupt downloads)
And then follow the guide I attached to this post - it's how to extract the PB99IMG from an RUU:
http://forum.xda-developers.com/showpost.php?p=10509780&postcount=102
Thank you so much! Will try now and let you know how it goes.
Thanks again
Still no good. Its tricky as I cant see the screen to select the options. But Ive followed the guide allowing it enough time to load before choosing yes etc and still no joy. Im not even sure the PBIMG99.zip is loading.
I've even tried running the RUU again from the PC after Holding vol - and Power down and waiting for the sound in windows that its connected. But gives me error code 110 again saying it cannot read files.
Loos like Im going to have to send it back to my supplier. Although Im sure they will blame me for everything and refuse me a new handset! lol
Once you have the correct PB99IMG file, you copy it onto the root of the SD card (not in any folders) and then turn the phone on holding volume down. You don't have to do anything else as it'll find the file and ask if you want to use it
To try the RUU turn the phone on holding the BACK button to get into FASTBOOT, connect to the PC and when it says FASTBOOT USB on the screen of the phone run the RUU
Out of interest, when you boot into HBOOT when info do you see at the top of screen?
Thats the problem. My screen is blank. I used to be able to get into Hboot and fastboot and see the screen. Now I dont see anything. But Im sure its still going into hboot etc as I hear the connection sound windows makes when holding vol and power.
Hope that makes sense?
Edit. I do know that before all went wrong I had hboot 93 or something like that.
Right, sounds like you've flashed a ROM for an AMOLED Desire onto an SLCD one...
Oh! poooooooh. Well thanks for trying. I never even got to use the stupid thing! lol
There is a thread on here to try and use to sort it out - look through the Q&A section
have u fixed it please ?? I got the same problems now......
thx
SK
vyeshaun said:
Hi guys, Well after trawling through the wealth of information on this site and reading till my eyes bleed I honestly cant seem to fix this.
I was hoping and preying some amazingly talented expert here could maybe point me in the right direction.
Ok so heres whats going on. Got my HTC Desire, Told me there was a system update. So I chose to install ofcourse. Then BAM! for no reason half way through installation the phone dies. Vibrates 7 times and black screen (Searched this too) - nothing.
So pulled battery, waited for a few minutes and put in, power on. Phone gets to HTC (white screen) the freezes. Or even sometimes just switches off and vibrates 7 times again!
So I found An RUU for 3 mobile - RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.06.00.02_2_release_127568_signed
Tried running it with the phone in fastboot usb
All was going well then reached about 80% and gave me an error code 110. Telling me to download a complete RUU for my device.
Now when I power on the screen is just black, however I know it still has some functionality as I can hear the sound for device connection in Windows when I Power on holding down Vol-
now I thought I would be clever and seeing as whilst my phone was working it downloaded the "correct" update. So checked the sd card and found it in the Downloads folder. Renamed it to PB99IMG and tried booting the phone holding down the back key. But still nothing.
By the way the phone isnt rooted and is very very very new. On 3 mobile UK network.
Can anybody please give me some pointers on how I may be able to go about fixing this? Im sure there has to be some way as it still has "some functionalty" (I think lol)
Also tried the adb method of connecting or re-flashing but device is not found.
Cheers all
Click to expand...
Click to collapse
The thread Eddy referred to, was probably this..You should be able to do it even if blindfolded
UPDATE TO MY PREVIOUS POST. I HAVE INCLUDED MUCH MORE DETAIL AS TO WHAT IS WRONG NOW. ANY HELP PLEASE?:
I am stuck in HBOOT currently, Ship s-off and of course my phone is rooted. What happened was my battery died sometime on the weekend and i tried turning it on to see the HBOOT screen. None of the buttons were responding when being pressed, not even the Vol. down + Power button was working... It randomly after a day decided to turn back on, then the next day i was at college and my battery went dead again and i'm now back at the HBOOT screen. I should have kept a check on it but i wasn't aware it would happen for a second time. Anyway...
I downloaded the PD98IMG.zip file and placed it on my goldcard (i'm on T-mobile) and attempted to re flash my device via the phone and left it for 6 hours or so whilst sleeping last night as it said it was parsing files. It sat on the same screen for the whole of the time. Tried flashing via my mac with instructions from a previous thread followed everything correct apart from putting into fastboot as i couldn't select it and thought it was worth a shot anyway Anyway, I came back with a message in terminal saying 'sending 'radio' (24960 KB)... FAILED (status malformed (1 bytes))'... As you could see it said failed. quite fed up now after looking for solutions since monday and i was hoping someone could come up with a fix :/.
If anyone knows whats going on with my DHD let me know ASAP. I am 95% sure its not bricked as its charging and turning on to HBOOT.
THANKS!!!!!
have you pulled the battery? thats what I normally do
Have you switched it back on without the charger plugged in?
Well i eventually got it working some how just after i posted this, but now it has just gone off again! It seems to be every time my battery goes completely dead. I plug it in, turn it on and Hboot screen pops up and repeats the same process each time, i dont know how to stop it doing this and i generally don't know how to get it back on.
I tried the ideas suggested but i've tried these previously and tried them again but no luck... One thing now though, my volume down button doesn't respond. If there is no fix i guess i'll just have to watch my battery usage but if anyone can suggest anything i can do to get it straight back on that would be great
I actually really need my phone to work right now , it ain't happening though, its been on hboot all day once again, it happens when the battery runs out, i press the power button and doesn't even vibrate or anything of the sort, just sits there and then pops up with the green writing after like 5 seconds saying:
SD Checking...
No image
Loading... (PD98IMG)
No image or wrong image
It says something like that, its only very briefly though. If anyone knows what i mean.... my phones on t-mobile so i made a goldcard so i could flash some roms, would that have anything to do with it?
THANKS!
Hi,
What info do you see in bootloader.
SHIP S-ON/OFF or ENG S-OFF
And have you performed Radio S-OFF?
andyharney said:
Hi,
What info do you see in bootloader.
SHIP S-ON/OFF or ENG S-OFF
And have you performed Radio S-OFF?
Click to expand...
Click to collapse
Yea i have ship s-off, which is shown. I can't press the volume buttons on the h-boot screen to scroll through menu either just to add... DO you actually have any clue what this may be?
Yeah, you've messed up your handset.
Letting your battery run completely flat will damage your battery. It shouldn't however harm your handset.
What I'd recommend doing, as you already have a goldcard, download the 1.32.405.6 PD98IMG.zip put that on your card and boot into bootloader. Follow the prompts and restore your handset.
Oh my battery is fine, i know for future reference to not let it run completely dry! will that mean i won't have the rom, which i previously flashed? Do i put the PD98IMG file on the goldcard or on my normal sd that i am currently using?
There is something wrong with your phone. When your battery dies your handset shouldn't lock you in HBOOT.
Put the PD98IMG.zip on your goldcard. You will lose everything that is not backed up.
Its your call, stay stuck in HBOOT or try to recovery it.
I'll give it a try and let you know the out come, thabks! By the way, after this wht should i do to get miui back up and running, the sme as what i previously did ?
I'll go for the recovery of course haha... Thanks anyway though, i'll give it a shot and see how it goes down . I'll let you know if i have any success!
How long does it take for it to Parse the package? it automatically started doing it so.
Update: Well I have had this going for quite some time now and its continued to show the following...
Parsing...(SD ZIP)
Bootloader
Boot
Recovery
System
UserData
Splash1
Splash2
TP
TP
TP
TP
Radio_V2
Radio_Cust
Would really appreciate any help ASAP as to why this has just been in the same position for quite some time, obviously something is not right?
Im guessing this isn't very common is it? nobody seems to know what to do
wow.. stuck in the same situation... ive rooted and unlocked my partners DHD from telus... just about a week ago, it just suddenly went to the white HBOOT screen. Since then, ive been able to somehow get into clockwork by pulling the battery out, plugging in the usb cable, then inserting the batter, it would somehow take me to the clockwork mods menu screen. I was using an outdated version tho. I would be able to reboot from that menu which would start regularly booting the phone. One interesting thing tho is that the volume - button stopped working around that time.... Ive been pulling my hair out trying to make a goldcard (did it once, but havent been able to do it since i started trying again) so i can reflash the stock telus ruu. For some reason, the goldcard program im using isnt finding the mm2... just the mm1 and mm0... any ideas why? im formating a 8gb class 4 micro sd card... fat32, ive tried 32 and 64kb sector sizes... any suggestions?
Aidanio said:
How long does it take for it to Parse the package? it automatically started doing it so.
Update: Well I have had this going for quite some time now and its continued to show the following...
Parsing...(SD ZIP)
Bootloader
Boot
Recovery
System
UserData
Splash1
Splash2
TP
TP
TP
TP
Radio_V2
Radio_Cust
Would really appreciate any help ASAP as to why this has just been in the same position for quite some time, obviously something is not right?
Click to expand...
Click to collapse
I´m in the same situation.I think the PD98IMG file don´t match with previously installed ROM (radio,hboot?)...I come from a MIUI ROM,android 2.3.4 version.
I´m proudly to inform you that I did it!
All the thing was (I think) the ROM manager who flashed a wrong recovery.
How I recovered it?
Without adb drivers,without goldcard,without downgrade.
Simply I downloaded a PD98IMG file,I unzipped it and I changed the recovery.img with a 3.0.2.6 recovery version.Ahh,I deleted the radio.img,too(I don´t know if matter or not).After this,I zipped the files again and I renamed the file to PD98IMG.Copy to sdcard,wait to process PD98IMG and finally the power and volume buttons revives!
Good bye!
Hey guys, pretty much what the title of the thread says. I try to unroot my phone via the HTC sync root, and when I click on the RUU to downgrade the phone, it instantly connects and I get an error message telling me to connect the phone.
Does anyone know how to cure this? It's been driving me crazy for ages now, wish I never rooted my phone in the first place!
Any help would be greatly appreciated! Thanks...
Lol rooting is better than that stock crap from htc.
If it's disconnecting maybe reinstall the drivers. Pretty sure there is another thread around here somewhere.
Swyped...
You can also run the RUU when the phone is in fastboot. Turn the phone off, turn it on again holding the back button and when on the white fastboot screen connect to the PC and run the RUU again
EddyOS said:
You can also run the RUU when the phone is in fastboot. Turn the phone off, turn it on again holding the back button and when on the white fastboot screen connect to the PC and run the RUU again
Click to expand...
Click to collapse
Tried that mate, and now I have a black screen, I think it's bricked it.
I know its turned on though because it vibrates & my pc still recognises it.
Any idea what I do now?
My ROM or RUU whatever its called is... 2.12.110.4 & I'm on T-Mobile.
Meaple said:
Lol rooting is better than that stock crap from htc.
If it's disconnecting maybe reinstall the drivers. Pretty sure there is another thread around here somewhere.
Swyped...
Click to expand...
Click to collapse
I want to unroot because me Desire started acting weird since I rooted. Started rebooting all the time & not full booting up. Had enough of it.
Which RUU did you use? As there isn't a FroYo T-Mobile one chances are you've flashed one for an AMOLED screen and you have SLCD
EddyOS said:
Which RUU did you use? As there isn't a FroYo T-Mobile one chances are you've flashed one for an AMOLED screen and you have SLCD
Click to expand...
Click to collapse
I think this one is the one I tried first...
RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver
Then I tried...
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed
Been getting the 131 error & 140 error. I don't have a clue on what to do to fix this... As you can tell, I'm totally new to this lol.
Well, the first one wouldn't work at ALL as it's for American CDMA Desires so thank god that didn't work!!
Use this one:
http://www.multiupload.com/LEJCW182AH
EddyOS said:
Well, the first one wouldn't work at ALL as it's for American CDMA Desires so thank god that didn't work!!
Use this one:
http://www.multiupload.com/LEJCW182AH
Click to expand...
Click to collapse
Haha like I said, I'm totally new to this!
Thanks for the link mate, will try now.
BTW, will I need to do a gold card or something?
Didn't work. Got the 131 error again. Arghhh, this is driving me crazy!
To get a froyo desire branded by t-mobile you have to run a special method:
Download these two files:
CustomRUU
2.12.110.2-1.21.110.4_release3uop1mw9unpc376h.zip
1.) Move the ota on your sd card and rename it into "update.zip"
2.) Run the installer. It extracts all needed files into a folder of your choice.
3.) Installer should start script automatically. If not, run "installer.bat" manually.
4.) Follow the instructions to the end.
5.) You are now in fastboot mode. Press power button to get into hboot.
6.) Choose recovery and enter with power button.
7.) If the red triangle shows up, hold volume up button and press power button. Now choose "Apply sdcard:update.zip"
When this operation is finished, you have a desire branded by t-mobile running froyo rom.
Sometimes the phone crashes when you install apps from the market. To fix this do the following:
1.) Turn off the phone
2.) Boot phone into hboot (start it with pressed volume down and power button)
3.) Navigate to "CLEAR STORAGE" and enter it.
This comment wipes the phone (so you loose all data) and resets all settings. After a reboot the market should work.
Translated from this serious german forum:
http://www.android-hilfe.de/anleitu...369-desire-mit-slcd-rebranden.html#post746176
Ah man looks like I'm gonna need a micro SD card adapter...
Is there anyway possible that I don't have to do anything with my SD card & can just use a RUU just to fix it??
lfcjake said:
Is there anyway possible that I don't have to do anything with my SD card & can just use a RUU just to fix it??
Click to expand...
Click to collapse
You have to use an sd card to get your working again, as far as i know.
Even if you want to run a stock froyo rom without any branding, you have to create a goldcard with linux and putting it in your phone, before you can run the ruu linked by eddyos.
And by the way, micro sd card readers aren't that expensive.
MatDrOiD said:
You have to use an sd card to get your working again, as far as i know.
Even if you want to run a stock froyo rom without any branding, you have to create a goldcard with linux and putting it in your phone, before you can run the ruu linked by eddyos.
And by the way, micro sd card readers aren't that expensive.
Click to expand...
Click to collapse
Ok I'll give it a shot & will let you know the results haha.
Thanks for your help mate. Fingers crossed!
Ok can someone do a step by step guide please on how to do this.
I've done the ADB part, but when I'm on the CMD command prompt thing, I type 'adb devices'
And it says list of devices attatched...
And theres nothing there?! No serial or anything! What am I doing wrong? This is driving me insane.
Ok I found out what my serial is.
It's : HT0APPL00658
What do I do now?? Can anyone actually help me please?
I got my phone today which is on t-mobile and went ahead and rooted it and s-offed it, i unlocked the network with HTC_Desire_Unlock_v0.9.5 and all seemed ok until i tried to install a custom rom from my memory card through CWM, but it would not let me it just went to a black screen.
So i downloaded a RUU file called RUU_Bravo_TMO_UK_1.15.110.11_Radio_32.30.00.28U_4.05.00.11_release_122755
I ran the file and it started to install so i thought, it then came up with an error saying something like wrong version.so i turned of my phone and switched it back on and nothing, i cant even get into hboot or recovery
Please can someone help me out as i am a noob at this
Regards mimic
What happens when you try to power the phone on with volume down and power?
Sent from my HTC Desire using XDA App
Nothing happend but when i plug in my usb it vibrates once and is recognised in devise manager as MY HTC!!
Have you tried using revolutionary to s off it, that will flash another revovery and may kick it in to life just an idea?
Sent from my HTC Desire using xda premium
Just tried that and it says Device "/sbin/sh: getprop: not found" is not supported at this time
So you can't get to bootloader?
Sent from my HTC Desire using xda premium
nope
If i try to run another RUU it just says Error 170 USB Connection Error
What happens if you run unrevoked again? If it picks up?
Sent from my HTC Desire using xda premium
i just get this error "Device "/sbin/sh: getprop: not found" is not supported at this time"
Its possible you haven't done much research.
1) Maybe in recovery, if you pressed the power button to flash a rom, you would find it switched off the screen. Pressing power again (if this was the case) would turn the back on. You could then use trackball to select
2) RUU's starting 1.x are Eclair Roms. They more often than not do not support SLCD screens so this could have given you an SLCD Brick.
If you get wrong version, it hasn't flashed anything at that time so the RUU shouldn't have broken anything, although now you are getting USB errors, sounds like you needed to do the USB brick fix
You say when you try to get into hboot, you get nothing? define nothing clearly please? Have you removed the battery at all since any of this?
People, please understand what it is you are doing before doing it. If you dont understand something, ask before doing it. If I am right about the above, nearly bricking a phone because the wrong button was pressed in recovery has to be about the most extreme case of this sort of thing I have seen.
Yes i have removed the battery and tried to get hboot but nothing
So does this mean i am goosed then?
What do you mean nothing? does it vibrate? Please go into detail
Please can you guide me to the correct stock rom for my phone? it is on t-mobile UK?
The phone now says Android bootloader interface in device manager
Could you also tell me how to do the usb brick fix?
Yes it vibrates once and thats it.
It also vibrates once when i plug in the usb
Im not telling you anything unless you answer my questions. Sorry to be brutal, but you're not helping yourself here
Edit, Thank you.
It still looks like an SLCD brick to me. I can't for the life of me figure out how if it got wrong bootloader version though...
I dont mind you being brutal it will learn me not to make the same mistake again
I am really grateful for you helping me
mimicuk said:
I dont mind you being brutal it will learn me not to make the same mistake again
I am really grateful for you helping me
Click to expand...
Click to collapse
Ok, lets take our time with this, I dont think tonight is our night as shipped roms appears to be down so we can't necessarily get the latest TMO RUU from there. Also it may not be the latest.
Have you got:
1) A goldcard?
2) A card reader?
sorry i havent got a gold card but i have a card reader
mimicuk said:
sorry i havent got a gold card but i have a card reader
Click to expand...
Click to collapse
OK well you have the most important one that we need. Wit a card reader we can make a goldcard.
Follow the below link to make a goldcard using your reader. You need to format the card, so ensure you back it up first.
http://androidforums.com/desire-all...aq-rooting-updated-10th-august-2011-a.html#16
Wait a second for it to jump to the right point of the thread.
Incase I am not around for the entirety of this, here is what we are doing.
1) making a gold card
2) Downloading an unbranded RUU 2.28.405.5
3) Booting to fastboot and trying to run the RUU
If that fails, we are going to have to try the PB99IMG.zip method for the same rom, blind.
Get on with the goldcard and come back when you're done. Use this link: http://dl.dropbox.com/u/20471345/SUroot/Tools/PC/GoldCard Tool.rar to download the actual goldcard tool
i keep getting this error Could not locate CID in output
My girlfriend just picked up a Wildfire S on Virgin Mobile USA on Nov 25th 2011(last week) at radio shack. It came stock with android version 2.3.4(ive seen most used to be 2.3.3). I was able to use the GOLDCARD to get s-off, then used the root file. From there she has been using the phone since. Then we learn about the low internal storage. In an attempt to get more internal storage, I flashed the [ROM]Wildfire S -JikantaruROM XE™ based on the install instructions on that page. The flash went well, but.... The wifi would not connect, It was not finding any data for Virgin Mobile or sprint or anything. I then tried another rom, but same issues. I then tried to flash to one of the stock roms titled "RUU_Marvel_Virgin_Mobile_1.37.351.1_Radio_47.10.35.3029H_7.46.35.08_release_188032_signed.exe", the program got up to 22%, then the phone kinda just shut off, then the program errored out.
Now when I try to turn on the phone, it will just vibrate 3 times. I have tried powering on with power, power and volume -, no bootloader. just 3 vibrations, not vibrations with green or orange led lighting up with the vibrations(as I have found online). Does this mean its bricked??
there a way to fix it by creating a goldcard and run the ruu now press ctrl+r and type %temp% once your temp folder loads do a search in the temp folder for rom.zip rename that to to cant remember ill edit this post in a minute with the name you now copy the renamed file to the root of your sdcard and boot the phone as if you were going into hboot leave the phone for half and hour to 45 minutes to be on the safe side you the pull the battery and put it in again now try and boot your phone that worked on my mates wfs lets hope it works for you.
edit: rename it to PG76DIAG.zip its case senseitive.
p.s. most of the custom roms here are for gsm handsents and NOT cdma.
In fact ALL are for gsm. Do not flash anything before reading... Also, ALWAYS backup.
Sent from my HTC_A510c using Tapatalk
I tried using the same Virgin Mobile RUU and my phone too is dead. I tried following the directions in the 2nd post, I did not get anywhere with them...at least I have only had this thing less than a week and Best Buy will take it back.
eoghan2t7 said:
edit: rename it to PG76DIAG.zip its case senseitive.
p.s. most of the custom roms here are for gsm handsents and NOT cdma.
Click to expand...
Click to collapse
Is the correct filename not PG76IMG.zip?
I dont understand how I can create a goldcard if the phone will not power on. doesnt the sd card have to be in the phone in order to get the number from the sd card??
anyways, I think I will just bring it back to radioshack and get it replaced. What are the possibilities of finding a cdma rom for this phone??
xxcrashxx said:
I dont understand how I can create a goldcard if the phone will not power on. doesnt the sd card have to be in the phone in order to get the number from the sd card??
anyways, I think I will just bring it back to radioshack and get it replaced. What are the possibilities of finding a cdma rom for this phone??
Click to expand...
Click to collapse
If the phone vibrates three times and then flashes orange when you turn it on, you are in the radio bootloader, and not fully bricked yet.
If you hook up your usb cable, it will look for HTC Diagnostic Interface driver and install a virtual COM port for it. Then you could use putty/mutty to connect.
Now you can use radata to flash to a certain offset and size, but the image has to be in RAM, so unless you JTAG'd it, it probably wont work.
Here are more commands, but only available if you're s-off. Maybe someone else knows how we can flash in radio bootloader mode.
Code:
? [command]
h [command]
mb [StartAddr [Count [Filler]]]
mh [StartAddr [Count [Filler]]]
mw [StartAddr [Count [Filler]]]
setboot [0/1/2/3]
setatcmd [0:SIO/1:UART/2:USB/3:DPRAM]
setsmdloop [0:disable/1:enable]
setmpatch [0x1: CPU Freq/0x2: acoustic/0x4: simdoor/0x8: RTC]
setiot [0:Disable/1:Enable]
setoffmode [0:Enable/1:Disable]
setfaketemp [1:Enable/0:Disable]
eraseall [erase all setting flags]
setdiag [0:USB/1:UART/2:DPRAM/3:SIO]
partition
checksum
format
setinfo
readadc
cego
setgpio
getgpio
gpio
version
powerdown
platformid
pcbid
radata
rcdata
i2ctest
videoamptest
ram_test [n]
Headsetpullhigh [n]
oscchk
battchg
ledtest
rtcchk
wskuid
rskuid
mcpvalue
pwrkeychk
mpu_nand_acpu_rw
clock_config
wpmic [PM_VREG] [0/1]
same issue here
xxcrashxx said:
My girlfriend just picked up a Wildfire S on Virgin Mobile USA on Nov 25th 2011(last week) at radio shack. It came stock with android version 2.3.4(ive seen most used to be 2.3.3). I was able to use the GOLDCARD to get s-off, then used the root file. From there she has been using the phone since. Then we learn about the low internal storage. In an attempt to get more internal storage, I flashed the [ROM]Wildfire S -JikantaruROM XE™ based on the install instructions on that page. The flash went well, but.... The wifi would not connect, It was not finding any data for Virgin Mobile or sprint or anything. I then tried another rom, but same issues. I then tried to flash to one of the stock roms titled "RUU_Marvel_Virgin_Mobile_1.37.351.1_Radio_47.10.35.3029H_7.46.35.08_release_188032_signed.exe", the program got up to 22%, then the phone kinda just shut off, then the program errored out.
Now when I try to turn on the phone, it will just vibrate 3 times. I have tried powering on with power, power and volume -, no bootloader. just 3 vibrations, not vibrations with green or orange led lighting up with the vibrations(as I have found online). Does this mean its bricked??
Click to expand...
Click to collapse
Hi mate, i think that the Ruu was maybe the uk version of virgin mobile not usa and if im on the right line us uses cdma uk is gsm, so maybe it froze up trying to install the radio which was incompatible.
Ive also seen a thread about the 3 vibrations apparently its a hardware diagnostic mode if you search there are solutions.
djxs said:
If the phone vibrates three times and then flashes orange when you turn it on, you are in the radio bootloader, and not fully bricked yet.
Click to expand...
Click to collapse
Nope, as I stated in the first post. just 3 vibrations, not vibrations with green or orange led lighting up with the vibrations(as I have found online). anyways, I already returned the phone and got a new one. but i believe it to be the whole gsm/cdma differences. makes a lot of sense.
Can you make the directions more clear? I have a hard time understanding them.
The same think happened to me when I tried to used the (what I now know) the wrong RUU on my Virgin Mobile Wildfire S.
Same thing happened to me. My phone just vibrates 3 times then nothing. Did anyone find a fix to this?
It means its in quallcom diagnostic mode. I dunno how to get it out. But those terms in google should help.
Sent from my HTC_A510c