Develop Bugs

Vogue Stuck at HTC Screen

Hey Guys,
I was trying to flash ToO's Cricket Rom to an HTC Sprint Vogue and after the process was finished it is stuck on the "HTC Smart Mobility" screen. I used an unlocker by cokeman before flashing I I think I need to re-lock the handset to flash it back to the original sprint ROM. However I need the older sprint rom and not the new one with GPS. When I put the phone in bootloader mode this is what it says:
It says:
VOGU100
SPL-0.41 Coke
CPLD-3
Where can I get the older ROM for the sprint vogue?
Update:
I am not able to load the original Sprint ROM. It errors out everytime at about 29%

Planetneo said:
Hey Guys,
I was trying to flash ToO's Cricket Rom to an HTC Sprint Vogue and after the process was finished it is stuck on the "HTC Smart Mobility" screen. I used an unlocker by cokeman before flashing I I think I need to re-lock the handset to flash it back to the original sprint ROM. However I need the older sprint rom and not the new one with GPS. When I put the phone in bootloader mode this is what it says:
It says:
VOGU100
SPL-0.41 Coke
CPLD-3
Where can I get the older ROM for the sprint vogue?
Update:
I am not able to load the original Sprint ROM. It errors out everytime at about 29%
Click to expand...
Click to collapse
Check PPCGeeks, there is a thread with factory ROM's.

Try doing this check your registry under HKEY_LOCAL_MACHINE\Software\Arcosoft\ArcSoft MMS UA\Config\mm1\MMSCsettings\make sure you only have one entry: Cricket MMS if you have another named Default or Sample, delete them and then try again; if it fails Delete all, soft re-boot and then install your ROM. Good luck.

Planetneo said:
Hey Guys,
I was trying to flash ToO's Cricket Rom to an HTC Sprint Vogue and after the process was finished it is stuck on the "HTC Smart Mobility" screen. I used an unlocker by cokeman before flashing I I think I need to re-lock the handset to flash it back to the original sprint ROM. However I need the older sprint rom and not the new one with GPS. When I put the phone in bootloader mode this is what it says:
It says:
VOGU100
SPL-0.41 Coke
CPLD-3
Where can I get the older ROM for the sprint vogue?
Update:
I am not able to load the original Sprint ROM. It errors out everytime at about 29%
Click to expand...
Click to collapse
I'm a little confused on the issue. If you want to flash roms with GPS you need to be unlocked with Imcokes 2.31 not 0.41 unlocker. Once unlocked you can flash to the stock roms. I flash back to Sprints stock GPS rom all the time. Be careful of flashing from a GPS rom back to a non GPS rom. This could cause some issues.
If you are trying to relock your phone thats a different issue.
EDIT: After rereading. Did you try flashing from a non gps rom to a gps rom or vice versa? Your phone looks to be unlocked with a non-gps unlocker. Is the cricket rom GPS?

When flashing a custom ROM your Vogue needs to be unlock with 2.31 (GPS) or .40 (non GPS). Not too sure about cricket but would assume if you have a radio version of 3.xx.xx would be GPS. Hopefully you have not bricked your Vogue.
You may find more help at ppcgeeks.com or ppchaven.com.
You may have to resort flashing your ROM in the bootloader mode,

SAME PROBLEM with Vogue
I think I have the same problem as the one who started this thread. here is what I did:
I unlocked a Vogue with the non-gps unlocker (SPL-0.41.Coke)
then I loaded a GPS rom onto the phone (OMJ 3.09)
and now it is stuck at the HTC Screen.
I then tried to flash a stock ROM to the phone, but as descreibed above it will not fully load- it stops at 29 percent- tried it a couple times.
I then tried the OMJ 3.09 again and it still stuck in HTC Screen, and says "No radio.'
I am trying to figure out what to do. I was told by someone to load a GPS radio into it and see if it boots. I have the radio to install but not sure if thats best bet.
I was told by someone else to install nongps radio and then install a nongps rom.
One concern I have is that I will brick my phone that way (if i try to downgrade to a nongps radio after installing a gps rom...but im not sure that the gps rom actually installed a gps radio or not cuz my phone was only .41 unlocked)
Also, I cant seem to install a stock rom because it stops at 29 percent.
Any ideas?
Thanks

found answer
to anyone else with this problem- I just installed this rom: http://forum.xda-developers.com/showthread.php?t=357762
and all was well including radio.

Just thought that I would post what happened to my phone and the steps that eventually recovered it in case it helps somebody else:
My phone was stuck with "No Radio" on the boot loader screen and the SPL as "SPL-2.31.CoKe", but none of the 3.x ROMs would flash properly that I tried. So here are the steps that eventually recovered it (mostly...):
1.) I installed the ROM above from the tri-color screen (power+camera+reset). I still had no radio, but it was letting me past this and booting up to WM.
2.) I then re-flashed the 2.31.CoKe boot loader (not sure if this step is necessary but listing what worked...)
3.) I tried to install RUU_Vogue_VZW_WWE_3.14.605.1_Radio_3.37.78_Ship.exe but it failed at 10% restarting to RUUNBH screen and the installer gave me Error [290]: Invalid Command
4.) I then tried to install the latest sprint ROM straight from the HTC site:_Touch by HTC (Sprint)_RUU_PPST_Vogue_SPRINT_WWE_3.03.651.4_2_Radio_3.42.30_AM_NV_2.04_Ship this looked like it was going to fail at the same part the Verizon rom did as it rebooted at 10% to RUUNBH screen, but the Sprint installer did something (I heard the computer lose and gain connection multiple times) and eventually it went right back and continued on from 11% and finished successfully.
5.) Rebooted and I had a radio now! Rather then risking trying to install the Verizon ROM again I went straight to the custom ROM I had originally started out with: NFSFAN 6.5 V6 which is working fine for me, except the GPS which is what started out my adventure of the last 3 days...
Just a note: for all flashes except the final one I simply waited till it was at the "Tap the screen..." stage till flashing. I never let any ROM but the final one run it's customization.

[Q] Remove tmobile bootscreen?

I got a t-mobile branded DHD, and had no problems with root s-off etc. and im currently running revolution 2.0.11 ROM.
But the tmobile bootscreen is still there. Is there any possibility to remove it?
I already tried to replace the bootanimation.zip in /data/local/. So first I thought that worked because when fastboot is turned on the new bootanimation shows up on restart.
But when I go into CWM or when fastboot is turned off the tmobile logo is still showing up.
I also flashed Kernel and Radio but still no effect.
Does anyone know where this logo is stored or how it can be removed?

v0iddr0id said:
I got a t-mobile branded DHD, and had no problems with root s-off etc. and im currently running revolution 2.0.11 ROM.
But the tmobile bootscreen is still there. Is there any possibility to remove it?
I already tried to replace the bootanimation.zip in /data/local/. So first I thought that worked because when fastboot is turned on the new bootanimation shows up on restart.
But when I go into CWM or when fastboot is turned off the tmobile logo is still showing up.
I also flashed Kernel and Radio but still no effect.
Does anyone know where this logo is stored or how it can be removed?
Click to expand...
Click to collapse
Yes it's on the /splash2 partition. To nuke it you need a new splash.img. You can get one from extracting from an ruu or there is a thread for custom splash screen in the themes section of the forum.
You also need eng hboot s-off not radio s-off then you can boot to fastboot and do "fastboot flash splash2 splash.img"
-----
Someone Swyped my idea.

like mox said it's not the boot animation, its the splash, you need to have eng s-off, then find the image you want as a splash, you need to convert the .bmp to an .img, then you can flash it from fastboot using the command "fastboot flash splash1 xxxxxx.img"

thx for your fast answers!
how do i convert a bmp to img? i guess it wont work by just changing the file ending?
im so glad i wont have to see that t-mobile logo anymore now my DHD is completely liberated from all this provider crap

v0iddr0id said:
thx for your fast answers!
how do i convert a bmp to img? i guess it wont work by just changing the file ending?
im so glad i wont have to see that t-mobile logo anymore now my DHD is completely liberated from all this provider crap
Click to expand...
Click to collapse
this tool here will do it all, covert the image and flash the splash for you
http://forum.xda-developers.com/showthread.php?t=794638

Bricked?

My phone will go into the bootloader (no custom recovery installed) where I can use fastboot but the phone wont get past the htc logo. I have installed the stock software by having the phone in the bootloader and fastboot mode and I have tried the PC10IMG.zip flash but neither seem to make a difference even though they both seem to complete without errors. I have also tried to flash individual img files with fastboot but the phone just returns a signature failed message. Basically am I out of luck with this phone? I tried talking to HTC and they cant help me unless I provide a receipt, since I bought the phone used I dont have one... and I dont have an account with the provider (Bell) that this phone is branded for.

flindil said:
My phone will go into the bootloader (no custom recovery installed) where I can use fastboot but the phone wont get past the htc logo. I have installed the stock software by having the phone in the bootloader and fastboot mode and I have tried the PC10IMG.zip flash but neither seem to make a difference even though they both seem to complete without errors. I have also tried to flash individual img files with fastboot but the phone just returns a signature failed message. Basically am I out of luck with this phone? I tried talking to HTC and they cant help me unless I provide a receipt, since I bought the phone used I dont have one... and I dont have an account with the provider (Bell) that this phone is branded for.
Click to expand...
Click to collapse
Do you even know what you are doing? just asking cause you are not giving much info to go on. What are you trying to do in the first place and why do you not have a custom recovery installed?

flindil said:
My phone will go into the bootloader (no custom recovery installed) where I can use fastboot but the phone wont get past the htc logo. I have installed the stock software by having the phone in the bootloader and fastboot mode and I have tried the PC10IMG.zip flash but neither seem to make a difference even though they both seem to complete without errors. I have also tried to flash individual img files with fastboot but the phone just returns a signature failed message. Basically am I out of luck with this phone? I tried talking to HTC and they cant help me unless I provide a receipt, since I bought the phone used I dont have one... and I dont have an account with the provider (Bell) that this phone is branded for.
Click to expand...
Click to collapse
Do you have eng hboot installed?
if you have ,no, its not bricked you can easily format your phone flash a custom recovery
and install any rom you want. if this is the case ,i can help you with that.

im assuming you have firmware 1.34 so you can try to just flash back the original 1.34 wwe rom for the htc desire z.

Need Help Getting Phone to Boot!

Hey Guys,
I'm reaching the point of frustration now. To try and cut a long story short, I had the Android Revolution 6 ROM on my rooted/unlocked HTC One X, and decided to update it to Android Revolution 13. I followed all the instructions, went to boot it, and it just sat on the HTC logo for an hour at which point I knew something went wrong. I repeated the steps, including wiping data using super wipe, without success either. I then decided to just select the "Factory reset" option on the boot menu, but this has also failed to boot after 30 minutes. I can also no longer boot into recovery. I've tried reloading CWM and other recovery ROM's onto the phone, but the phone resets as soon as they load.
At this point, I just want to get some form of OS on my phone. My phone is Unlocked, S-ON and has a CID of OPTUS001. I don't know if Factory reset will work if the phone is unlocked. It's all very time consuming as you normally don't know if the boot process has locked until you've waited ~20 minutes. I can't find my original ROM from when I bought the phone either, so I assume I need to obtain another one from somewhere, but I don't have any idea about CID compatibility, etc, and I'm finding this all very confusing and frustrating. All help is much appreciated. I have a feeling I need to replace my boot.img with a stock boot.img, but once again, where do I get that?
Thanks

the phone doesn't boot because you don't have the latest firmware installed, you need HBOOT 1.31 but you can't install it cause your CID is not compatible with it, you sjould go back to ICS and wait...

Did you load new firmware 1.31? This firmware is not compatible with Your CID... Did You read carefully this thread — http://forum.xda-developers.com/showthread.php?t=1924003
Sent from HOX with ARHD 13

You forgot that you need to update the firmware to 1.31.
You can also just install ARHD 9.7.2. Ensure you have the latest CWM 5.8.4.0
faatboot flash recovery recovery.img
and then flash the boot image:
fastboot flash boot boot.img
fastboot erase cache
And then copy the ROM on using recovery mount USB and flash it.

Thanks for all the help guys. I managed to get a stock recovery.img back onto the phone, and by re-locking the phone I was able to use the latest Optus RUU from htcruu.com.
So at least I've now got a working phone again.
Moving onto why ARHD didn't work, I had no idea about the firmware 1.31 compatibility requirement. I thought all HTC One X's were created equal. I didn't know about this CID nonsense. Can someone explain how I find out when my phone's CID becomes compatible, or perhaps a way to change my CID or some other means of getting Jelly Bean onto my phone. Apologies for being a noob.

wardrop said:
Thanks for all the help guys. I managed to get a stock recovery.img back onto the phone, and by re-locking the phone I was able to use the latest Optus RUU from htcruu.com.
So at least I've now got a working phone again.
Moving onto why ARHD didn't work, I had no idea about the firmware 1.31 compatibility requirement. I thought all HTC One X's were created equal. I didn't know about this CID nonsense. Can someone explain how I find out when my phone's CID becomes compatible, or perhaps a way to change my CID or some other means of getting Jelly Bean onto my phone. Apologies for being a noob.
Click to expand...
Click to collapse
without S-OFF no chance to change CID. Regarding CID compatible - http://forum.xda-developers.com/showthread.php?t=1924003

wardrop said:
Thanks for all the help guys. I managed to get a stock recovery.img back onto the phone, and by re-locking the phone I was able to use the latest Optus RUU from htcruu.com.
So at least I've now got a working phone again.
Moving onto why ARHD didn't work, I had no idea about the firmware 1.31 compatibility requirement. I thought all HTC One X's were created equal. I didn't know about this CID nonsense. Can someone explain how I find out when my phone's CID becomes compatible, or perhaps a way to change my CID or some other means of getting Jelly Bean onto my phone. Apologies for being a noob.
Click to expand...
Click to collapse
now you're on stock right? when you'll get the OTA update then you can install JB custom roms...

matt95 said:
now you're on stock right? when you'll get the OTA update then you can install JB custom roms...
Click to expand...
Click to collapse
Yeah, but I'm going to put on ARHD 9.7 I think.

Optus not compatible with JB yet

[Q] Serious problems after manual FASTBOOT FLASH

Long story.
Was originally a UK Orange branded HTC Desire HD, running OTG updated 2.3.5, unrooted
I originally unlocked the stock device using the HTCDev method, all went to plan. I then installed clockworkmod and from there installed jellytime 10.
All good so far. I then applied a sim unlock code so we could use other SIMs in the device. Although the unlock code was accepted, with a 'Success' message, we could not get the phone to log on to other networks. Googling this problem suggested that the SIM unlock needed to be done under the stock rom. So I went looking further and found these two files:
RUU_Ace_Orange_UK_1.84.61.2_Radio_12.28g.60.140f_26.05.05.27_M3_release_170856_signed.exe
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe
Both of which were supposed to be compatible with the phone.
Neither would install when run on an XP machine with the correct HTC drivers installed. So I extracted the ROM.zip from the WWE RUU above, opened it with winrar, and manually FASTBOOT FLASHed the .img files within, including boot.img, lib,img, recovery.img, and others. Some would not copy or install, but those above definitely did. (flashing at 5 am!)
However, none of this worked, so I rebooted into clockworkmod and reinstalled jellytime 10 and its boot.img.
Now, no matter what rom i put on it, the rom cannot access the sdcard (although hboot and CM have no problem doing so) and the phone can see no cell networks.
the phone current state is:
ACE PVT SHIP S-OFF RL
HBOOT-2.00.027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011,9:06:24
Anybody got any ideas on how to fix my phone?

You unlocked the bootloader with 2.00.0027? I had a Canadian Desire HD with the same bootloader and I couldn't unlock the bootloader until I upgraded to 2.00.0029.
I followed the guide in this forum to unlock my bootloader, get s-off, root, load 4ext, and load a custom rom. By doing all of this, my phone automatically became carrier unlocked.

audit13 said:
You unlocked the bootloader with 2.00.0027? I had a Canadian Desire HD with the same bootloader and I couldn't unlock the bootloader until I upgraded to 2.00.0029.
I followed the guide in this forum to unlock my bootloader, get s-off, root, load 4ext, and load a custom rom. By doing all of this, my phone automatically became carrier unlocked.
Click to expand...
Click to collapse
I have the ability to flash whatever ROM i wish, but any and all that I've tried give me zero network availability. Can't enable it. Wifi works fine - but no cell ability.

When testing, is the bottom sim cover installed? Have you tried flashing a different radio?

audit13 said:
When testing, is the bottom sim cover installed? Have you tried flashing a different radio?
Click to expand...
Click to collapse
Yes, the antenna was in place when no network was available.
If you can tell me what radio to flash for an Orange branded UK Desire HD - and more to the point, where to find it! - I'd be happy to give it a try, provided I can get hboot to allow me to flash the radio.

SimonButt said:
Yes, the antenna was in place when no network was available.
If you can tell me what radio to flash for an Orange branded UK Desire HD - and more to the point, where to find it! - I'd be happy to give it a try, provided I can get hboot to allow me to flash the radio.
Click to expand...
Click to collapse
Here's a list of radios: http://forum.xda-developers.com/showthread.php?t=877295

audit13 said:
Here's a list of radios: http://forum.xda-developers.com/showthread.php?t=877295
Click to expand...
Click to collapse
Thank you. I've previously tried two from that list, Orange UK 1.84.61.2 / CSL-HK CHT 1.84.832.2 and HTC 3.12.405.1 WWE.
I had great difficulty installing them as the fastboot flash radio radio.img process would fail, saying remote not allowed.
I was unable to s-off the phone using the methods most pages talked about (froyo/gingerbread exploit), the AAHK was unavailable and frankly, I don't really know what I'm doing.
The WD98IMG.zip method refused to install the zipped radio.img. As a workaround I extracted the rom.zip from the HTC WWE RUU above, unzipped it to a folder, replaced recovery.img with CM recovery.img and also replaced the radio.img with the one from the Orange RUU. Zipped the lot back up, put it on SD card, and hboot picked it up and flashed it.
This got me a working ROM with CM recovery, at which point I installed jellytime11. Then I fastbooted and flashed the boot.img. Once in Jellytime (and here's a tip - if it fails to boot, go and format the cache again) the radio started working. Don't know how stable it is and given how difficult it seems for me to change the radio rom, I will need a good reason to change it again.
Never flashed a rom before three days ago.

I was also having issues with the radio after rooting, unlocking the BL, and getting s-off so I just loaded the most recent radio and it worked.
My baseband is 12.69a.60.29u_26.17.14.11.m.
It's easier to flash roms with s-off as you can just install from cwm without having to extract certain files from the zip.

SimonButt said:
Long story.
Was originally a UK Orange branded
Noticed that you was on orange UK I have a T-Mobile stock RUU in my dropbox. Orange and T-Mobile are joint. Not sure if this would flash back to stock or weather it would flash at all but to T-Mobile because they are the same. If you know what I mean?
IceCreamSandwhich ( LorD ClockaN ) S-OFF DHD
Click to expand...
Click to collapse

ykdr-scott said:
SimonButt said:
Long story.
Noticed that you was on orange UK I have a T-Mobile stock RUU in my dropbox. Orange and T-Mobile are joint. Not sure if this would flash back to stock or weather it would flash at all but to T-Mobile because they are the same. If you know what I mean?
IceCreamSandwhich ( LorD ClockaN ) S-OFF DHD
Click to expand...
Click to collapse
Yes please, send me a link to your dropbox file. Always handy to have a backup.
Radio problem now solved, I got hold of a working AAHK and just ran the phone through that.
Splash screen flashed - bootanim next!
Click to expand...
Click to collapse