Have I bricked my 8125? - 8125, K-JAM, P4300, MDA Vario ROM Development

I flashed my g4, using shell tool, to core 2.0n. After the hard reset it just sits at the boot screen listing ipl 2.25, spl 2.25, gsm 02.25.11, os 10.2.0.8.
When booting it to the boot loader I try to flash with the htc 8125 rom, but this fails with error 274 or 260.
Any help would be appreciated.

Splooshie said:
I flashed my g4, using shell tool, to core 2.0n. After the hard reset it just sits at the boot screen listing ipl 2.25, spl 2.25, gsm 02.25.11, os 10.2.0.8.
When booting it to the boot loader I try to flash with the htc 8125 rom, but this fails with error 274 or 260.
Any help would be appreciated.
Click to expand...
Click to collapse
Some G4's can't be flashed with the ROM on the HTC site, but can be flashed with the Wizard Love ROM. I'd try that. It's saved me several times.

Or try a hard reset before flashing another rom. See if it fixes the problem

If your phone makes it to the boot screen it isn't bricked.

It isn't bricked. It shouldn't be. If he flashed the Core 2.0n it's impossible that a OS only ROM would brick it because it doesn't touch the bootloader or the extended rom. Plus, from what i understand the ShellTool flashes OS only and that means even if the ROM he was trying to flash contained an IPL/SPL , then only OS would be flashed.

The fact that it even gets to the bootloader screen is proof enough it isnt bricked.... reinstall the carrier update and try something else.

Oh Sorry, he tried to reinstall the carrier ROM .. disregard.

I tried the love rom, but it errors out with error 300, invalid argument ( I think it looks like italian) =/
I've rebooted my pc, did a couple hard resets on the phone and verified the phone is being detected. The USB sync driver is loading. Seems every flash utility cant see the phone even when in the boot loader.
BTW it fails at the point where it tries to verifiy the information on my phone. if that helps.

Is your PC XP or Vista? If its Vista, it can't talk to a phone in bootloader mode. If you are XP then you should be fine but then I'm not sure why you can't flash the Wizard Love rom...

I'm using xp.

When you put it into boot loader mode, is USB in the lower left corner?

Splooshie said:
I'm using xp.
Click to expand...
Click to collapse
Have you tryed a hard reset ?

yes twice the second time when it rebooted I forced it to boot the boot loader before it tried to boot the OS.

And you have tryed taking out your SD card, and flashing the Wizard Love rom directly from the RUU (not with ShellTool) ?
You have enough battery ?

I have been using the flash utility, I don't know how to use shell tool without the scripts, and I can't install any of the cabs since it wont boot into the OS. I just tried on another xp machine and both the cingular rom utility and the love rom failed to communicate with the phone.
any other ideas?
edit: oh and I should have near if not 100% battery ( been plugged into a pc since the problem started and it was 100% when I started this mess. =) SD card has always been removed.

FYI, even though it has been plugged into the computer, it may not have enough battery. From my experiences, it drains the battery even if it is plugged in. Luckily, I have a second wizard so when my first battery drained (and wouldnt recharge even when plugged into the wall) I just popped the second battery in and i could flash it again. See if you can find a charger or something for the battery, and then once it is charged, let me know and I will give you a ROM i have that saved my other wizard (which is a G4 and no it isnt wizard love)
-Nstefanelli-

it seems to be charging, the orange light is on and the phone is off.

ok in a few i'll PM u a link to the ROM.. i havent used it in a while so i might have to gather it up..
-Nstefanelli-

well I tried the rom and it said error 300 this version cannot be used with your phone try a newer version (best I can figure from the italian?)

Splooshie said:
well I tried the rom and it said error 300 this version cannot be used with your phone try a newer version (best I can figure from the italian?)
Click to expand...
Click to collapse
Are you sure you don't have a G3 ? Hmm, I think you have a G3 and that's why it doesn't work. Try and flash the Tmobile 2.26
If your ipl 2.25, spl 2.25, then you defenively have a G3 CID UNLOCKED
Go back to Button's 1.05 ROM, CID UNLOCK it and then flash the Tmobile 2.26 and then flash Core 2.0n
Don't use ShellTool !

Related

I want my phone back help!

ok so I previously had NBD 7.6 on my phone and it was running fine. then I decided it was time to upgrade to 8.3 I went through the flash process using the shell tool straight from 7.6 to 8.3. however the hard reset did not work right away and my phone did what I think was a soft reset. where it gets stuck in the splash screen with the IPL SPL GSM and OS numbers. my phone is a G4 and I have heard that you can't use the RUU to flash new roms you have to use the shelltool. however I am trying to flash back to the original love rom and am having no luck because my computer does not recognize my phone and nothing comes up in my computer however it is connected because it makes the noise when I plug it in. so how can I flash back to the t-mobile love rom without putting Cert_SPCS.cab and EnableRapi.cab files on my phone?
Wizardlove should work. Perhaps you could elaborate on why wizardlove doesnt work.
Another suggestion is that you could flash back to the rom that your device was shipped with.
ok so my thoughts on why it doesn't work is because the Cert_SPCS.cab and EnableRapi.cab are unable to be placed on my mda before I flash. also it doesn't seem to be flashing anything at all because when I flash it and do a hard reset it comes up with my os being 6.6.6.666 which is scary and wasn't there when I used to have the original shipped rom. I have tried flashing wizard love twice both for 30 minutes and the shelltool never says it is done so I unplug and do a hard reset. any ideas?
squishymax said:
ok so my thoughts on why it doesn't work is because the Cert_SPCS.cab and EnableRapi.cab are unable to be placed on my mda before I flash. also it doesn't seem to be flashing anything at all because when I flash it and do a hard reset it comes up with my os being 6.6.6.666 which is scary and wasn't there when I used to have the original shipped rom. I have tried flashing wizard love twice both for 30 minutes and the shelltool never says it is done so I unplug and do a hard reset. any ideas?
Click to expand...
Click to collapse
You havent mentioned bootloader mode so i suspect your flashing wizard love with shelltool? correct me if im wrong. Put the phone in bootloader mode and flash wizard love using the RUU.
The original rom that was supplied with your device can in most cases be downloaded from their website. For example my device is branded I-mate so I obtained the latest rom from I-mate's website.
yeah my device is CID Locked and whenever I try to flash using the RUU the program loads up and I click next for like 2 screens and then when the mini screen that says verifying the information on your pda phone pops up vista kills it and says it has stopped working. so I have never been able to use the RUU when flashing to a new rom. and I have the lastest RUU as well. and yes my phone is in bootloader screen when I try to flash it.
I figured it out. It was easy. Vista can lick my balls! I went to a comp with XP and everything went smooth. after 5 hours of sweating and searching. @$%#%!

ERROR 262 - Bricked phone with Radio Rom Upgrade - SOLVED -

Hi to all,
I have an AT&T TILT HTC 8925,
ROM: 1.57.502.2
RADIO: 1.27.12.11
VE: 22.45.88.07H
Installed the kaiser-HardSPLv1 with no problems.
After this I Flashed (via USB) Q-Mobile_v1.2 ROM, that went perfect. Made a soft reset and then a Hard Reset after this I configured the phone.
After everything was working I made a Radio flash with KAIS Radio Only 1.27.12.17 CustomRUU, all seemed normal until it got to 95%, it suddenly interrupted the update (error 262), and took me to recovery dialog 1-4 steps which I did.
From that moment until know I get the tricolor screen with the following text:
RUUNBH​KAIS 1*0
SPL-1.56.0000
CPLD-8
USB​
Click to expand...
Click to collapse
And when I try to flash ANY ROM, It gets past the tricolor screen, to a white screen with a percentage bar that gets to 0%, after a minute or so the customRUU screen goes to error 262 and I get to the recovery screen, etc...
I run on WinXP SP2, and have already tried several roms with the same result, with the exception of original ATT RUU_Kaiser_CINGULAR_WWE_.exe, it then gets to 1% and displays error code 294 Invalid Vendor ID.
When I tried the MicroSD method with the rom it gets to the tricolor then the "Loading..." screen, and keeps there (I waited for about 30 min)...
There was no SIM or MicroSD card on the phone at the moment of flashing, and I did dump the original ROM to the 4 raw parts as per instructions.
I live waaay out of the countries with AT&T or HTC servicing routes, so I am stuck with it until I fix it, which I know I can do, and to be honest with myself, can't afford to waste the money spent on this thing.
Until now the best similar thing I found about this was with the hermes unbrick phone thread, and I am not sure this works on the KAISER, but to be honest, I get cold sweats to use any more procedures (without reconfirmation) on this as I have a phone that at least still shows "some" signs of life.
After reading days of threads (my eyes are burning) I know the knowledge is within this site, but I need guidance since I am new to this thing (smartphone flashing) although familiar with computers.
Any kind of help will be very appreciated and valued.
Best Regards.
----------------------
As an update, I solved this thing. Thanks for your help.
After seeing that there was some sort of problem with the boot mode screen not showing the kaiser-HardSPL data, I went in that direction. After some suggestions and much trying I decided to download all / any original roms I found in here for my phone (ATT Tilt) then I worked my way from top to bottom based on the versions of the radio.
The one that solved my problem was 1.5.502.3 Radio 1.27.12.11 although strangely it shows on my phone after the successful flashing. 1.5.502.1
Just out of curiosity I went and installed again kaiser-HardSPLv1 and it gets to this text on tricolor screen:
Kais1*0
SPL-.JumpSPL
CPLD-8
Doing a hard reboot (camera button + soft reset) gives me a different screen:
Kais1*0
SPL - 1.56.0000
CPLD-8
Really don't know if this is normal, and after flashing a cooked rom I had to reinstall it (kaiser-HardSPL).
I have now reflashed QMobile rom and have no problems. Although I didn't flashed again new radios
For flashing the Original rom I did make sure of the following steps in addition to normal ones (Just in case)
1) Disconnected fisically from LAN (Unplugged LAN Cable)
2) Disabled all firewall protections
3) Disabled all antivirus and spyware protections
4) Run RUU original files
5) Pray
Thanks again people
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
I just tried it again (See I am not so scared anymore), and received the same results (Radio upgrade fails on 95%).
I have burned the original ROM back and all is well again!
I also can't get past the same screen and try as I might Activesync won't recognise the phone. When going through the recovery process on Kaiser Custom RUU it says its recovered but then when trying to go through the update it sticks on 0% and then says there are communication problems etc.
On the tricloloured screen it says
KAIS130
SPL-1.81.0000
CPLD-8
Will a hard reset do anything?
Any help much appreciated.
Bump
Now managed to boot via MTTY but power off etc returns me to bootloader screen
Looks to me like you guys have had problems flashing hardspl. Your tri-colour screen should have:
KAIS130 MFG (or Kais 120 etc)
SPL-1.0OliPof
CPLD-8
I don't know about the CPLD number but you MUST have the OliPof SPL. Check this after running hardSPL to make sure that it's there before flashing another ROM.
If you have this but still get trouble flashing, try going to the tri-colour screen and then run the kaiser_RUU.exe to upgrade.
http://forum.xda-developers.com/sho...ked. (One without a radio)
- Flash a radio...
i had the same thing with my MDA Vario 3,but with no success finding the original ROM, since I`m from a small country. I`ve tried to reboot to normal screen via MTTY but it gives me the error: Command error . So - now I`m left with two options: to dump and reconstruct an original ROM from the same type of phone or to find what`s wrong with MTTY.
Anyone had a similar problem, I mean with MTTY and command error???
yes, i`ve searched trough the posts regarding this problem but I didn`t find any saying that MTTY gave this error.
any idea?
THX in advance!
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Martinhdk said:
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Click to expand...
Click to collapse
if you`re reffering to my problem-how can I copy the JumpSPL1.56-KAIS.exe file and execute it from the phone if I can`t boot it normaly,it always stays in tri-color boot screen?
actually, I`ve bricked my phone with that HardSPL procedure.It was the first step for unlocking. I`ve copied the JumpSPL1.56-KAIS.exe file, executed it and then rebooted and tried to flash with the modified ROM from the jockyw2001`s unlocker. it stopped at 95% and now it seems that it is still CID locked and bricked in boot mode. i`ve already said what MTTY gives as an error.
any idea what may be the problem?
like always:the problem is in RTFM
while i was working on my Kaiser i was doing lots of other things on other computers so i`ve skipped the step with flashing the HardSPL,that`s why all went wrong now,as i`m at home i have more time to read the posts and i`ll try with the jockyw2001`s procedure from the MTTY, with the task8 command.
hope it will help,unless the only solution is to dump the same ROM....
i`ll higly apreciate if anyone has a different solution....
will post results
The problem is that I can't flash the phone with anything be that HardSPL or the original Orange ROM or whatever you care to mention because the PC can't communicate with the device via the USB cable after Activesync ceases to operate. As such everything works up until the % progress bars come on both screens and then they stay at 0% before the communication error message appears.
Funny thing is that the phone is communicating with the PC as USB/Serial alternate depending on whether the cable is plugged in or not and the PC recognises the USB device when its plugged in and when Activesync isn't controlling the situation.
I've been stuck like this with a Hermes but not the Kaiser (yet). As far as I'm aware, you don't need activesync running to run a rom upgrade. If you are in bootloader mode (tricolour screen) you can run the upgrade directly with activesync not connected. If hardspl isn't installed then you should flash the original rom, and if you're unlocked then any rom should do.
Also it might be worth trying the SD card method for flashing. But either way I'd use the original rom and then when you get the phone working again keep trying with HardSPL until it's successful - don't flash any other roms without it.
Laubscherc said:
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
Click to expand...
Click to collapse
Thanks for your help.
I did try other "original" rom I got in here http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
The version corresponding my rom is (1.57.502.2 (radio 1.27.12.11)), however I got the error code 294 Invalid Vendor ID after 1%.
I did try the ftp address you mentioned, but I can't login neither anonymously nor with user & psw for xda-developers.
I would like to try the rom you are referring to, please give me another link to download the file.
Best Regards.
Martinhdk said:
http://forum.xda-developers.com/sho...ardware devices list.
Thanks for your help.:)
Click to expand...
Click to collapse
Stuck in Tri color screen
I have been fighting the same issue for several days. Radio gets to 95% and errors. Then hung up in tri color screen. I used MTTY - "set 14 0" command then "boot" command inMTTY to get the phone to boot. I have had to do this a number of times, sometimes more than once per incident. Hope it works for you too. P.S. once you have a successful flash the phone returns to normal operation until then it will go back to tri color screen on reset. I just flashed a startup splash screen to get mine back to normal.
pennco can you expand in further detail on what you actually did with MTTY cause I have the EXACT same problem....

mda bricked(???) while trying to upgrade

so yea, iono what happened to my mda. i cant seem to turn it on. when i press the reset and camera buttons, it worked before and brought me into bootloader. and that was actually all i could do. now, i cant even get it on, iono whats happened to it. im trying and atempting rigorously to charge it so i can try to fix it. but the charge light dusnt even come on... i dont know what happend. please help me analyzed. i really want to fix this back ._.''
You may need to use the factory charger to charge your device. I keep hearing the problem people experience when trying to charge a completely dead battery with a usb charger. the factory charger is 1amp while usb is half that. that may be why it wouldnt charge.
also, when the phone is in bootloader (tricollor bars) the power does not turn off.
you may need to charge your device completely before turning it on; then flash the original rom to it.
anothor thing about flashing while in bootloader:
If you connect the usb and XP does not recognize it, you have to unplug it, reset the device, then connect the usb again. as soon as you hear the found hardware noise, open the rom upgrade utility. flash. should work.
when posting a question such as this, it helps to provide as much information about the device and the circumstances under which it failed. this being an electronic forum, it is difficult to play detective to find out what you did wrong to mess up the machene.
also remember that it is a machene. it can not ousmart you, but you can outsmart it.
Which is your device,what were you doing when this happened,were you trying to flash a rom ?
bricked Cing. 8125
my device just bricked on my while updating also. not sure why, i use a Cingular 8125. i flashed it to the t-mobile 1.2 rom (like i always do) and then tried flashing it to a new rom and about halfway through it bricked up. now activesync wont even recognize it. how can i fix this?
Bricked up is an over used word on these forums. If it does nothing no lights no charge when you put a fully charged battery in it, then its a brick.
Anyway here is me repeating myself yet again. A Wizard WONT CHARGE A BATTERY without windows mobile running. So charge the battery in another wizard or orbit or buy an external desktop charger /cradle with a spare battery slot or a new battery because it wont charge it
Not really...
Wizard can charge without powered on (when not bricked). It just can't charge if the battery is too flat.
starkwong said:
Not really...
Wizard can charge without powered on (when not bricked). It just can't charge if the battery is too flat.
Click to expand...
Click to collapse
It will charge a completely "flat" or dead battery with the original factory charger. the one that has the output of 1amp, not the usb, which is .5amp
so yea, sorry about this confusing post. sop what i was trying to do was changing my wizard love rom to XM6r5...but i dont know how
what i did was use shelltool and pooped it. but now iono how to really fix it. im still confused now cuz i cant boot up at all. i can get into the bootloader r/g/b screen
but iono how to fix it from there
sound to me like you may not have unlocked your device?
maybe.
try this: reset your phone with the reset button;
put it in bootloader (tricolorscreen) reset holding the camera button while untill it is in bootloader;
plug in the usb;
run the update utility.
as it updates, it will seem to freeze at 100%. do not unplug it.
I recomend you flash the love rom first.
but it says it cant even connect when i pplug my usb to the pc and device
th pc dun really "see" it
and the ruu, dont you need active sync on as well or sumthin? nothin shows up
m1k0e said:
but it says it cant even connect when i pplug my usb to the pc and device
th pc dun really "see" it
and the ruu, dont you need active sync on as well or sumthin? nothin shows up
Click to expand...
Click to collapse
try reseting it. then put it into bootloader; then plug it in; then run the flasher.
if you unplug it while it is in bootloader, then plug it in again it will not read.
exit everything (meaning flashing utility unplug usb; reset phone)
then try it again.
just a side note, dus it matter which ruu im using to do this? or should i use the wizard love first?
okayt so i have tried it, but curiously, how do i know if its actually working when i do that? cuz everytime im in bootloader and open ruu, it goes at first, but the status dusnt move past 0% and then an error message comes up. does it matter ifi supposedly have other programs open in the b/g?
I think it matters which ruu you are using depending on if you have a G4 or G3.
If you have a g4 then use the ruu for a g4.
the guy who designed the wizard service tool would know.
I would flash to the factory rom though to fix any issues first.
what is your IPL SPL? G3 or G4?
well, at least we know that your phone is not bricked. It will get fixed under the right circumstances.
It could be that your battery is not charged all the way.
remove the battery, then put it back in. charge it fully (overnight) and try to flash it to the factory rom.
well i upgraded my rom to wizard love previously, so apparently its a g4 now. i want to upgrade to the XM6r5 ruu but im not too sure.
maybe u could help locate me a few stable and nice roms for g4?
but thanks so far
when i run the RUU, i keep getting an errormessage 260, saying it cant connect my phone to the pc.,..
have you gotten it unbricked yet?
need more infoon your phone and it's current state.
everytime you post a message (it seems) you do not give enough information.
ipl spl current rom ...
I dont know any of these things. untill I do, I can't help you.
If you search the G4 forum you will find information on flashing your phone if it is a G4. (you may need to soft spl or hard spl your phone) look to the G4 forum for information for that.
just because it had the love rom does not mean that it is a g4. all roms that have OS ONLY can be flashed to a G4. If it has SPL/IPL (bootloader) Or extended roms can not be flashed to a G4
oh. haha sorry. now it just boots straight into the bootloader with "ruu" on the upper right hand corner.
ipl is 2.26.0001
spl is 2.26.0001
m1k0e said:
oh. haha sorry. now it just boots straight into the bootloader with "ruu" on the upper right hand corner.
ipl is 2.26.0001
spl is 2.26.0001
Click to expand...
Click to collapse
Its a G4,you can only upgrade through either SoftSPL or HardSPL,read about this in the G4 sub-forum posted as stickies.
but how would i use hardSPL thru only bootloadeR?
update: everytime i restart my phone, it keeps booting up into the bootloader screen with "RU" on the upper right of the screen
m1k0e said:
but how would i use hardSPL thru only bootloadeR?
update: everytime i restart my phone, it keeps booting up into the bootloader screen with "RU" on the upper right of the screen
Click to expand...
Click to collapse
ok,download official carrier's rom, get into Bootloaders,hook up the phone with pc via usb,Now Check,if small usb appears at the bottom of the Bootloader screen,if its there than Run the Ruu in the rom to flash it,but if it doesn't appear,its not establishing connection with pc and phone.There might be a connectivity problem,it cud be usb cable,mini usb port of the phone or usb input of pc.
Yes! you can only do HardSPL if its working normal,you can even try to flash wizard_love rom and if it flashes,then go for HardSPL.but official carrier's rom will be more appropriate and recommended,it will also remove any Extended_Rom corruption,if any.

Error 260 Update Error

Hi
I get this problem too often and I dont know why and what I did do when I dont get it. This is the case.
Now I have flashed the g3 wizard with one of the wm6-manilla roms. I have succeded with this once so I have followed the guides with the unlocking and downgrading etc. Now I have downloaded a new cook and try to install it by starting the rom update utility wizard.
Problem is that the installation ALWAYS fails now. It starts, the device disconnects from activesynk, waits another 30 seconds then fails to restart the device so I get the dreadful Error 260 update error and the phone is dead. I remove the battery, restart the device and try again and my hair turns grey.
I figure I need to downgrade first so I try all the differens RUU's that are pointed out in the guides (CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe, ruu_prodigy_226102_22610105_022511_tmous_wwe_ship.exe, Xda_MiniS_LaunchROM_v154102.exe) but always the same problem.
What am I missing?
WinXP
AS4.5
IPL 2.26
SPL 2.26
Once downgraded and CID unlocked,a G3 device will remain CID unlocked forever,there's no need to downgrade everytime you flash a new rom.Just simply flash a new rom whenever you desire.So don't reflash Button's Rom 1.05 before every flash,its just required to flash once to get IPL/SPL 1.xx for CID unlocking,after which there's no need to reflash it again.
Error 260 is due to open port,so reboot your pc and Soft Reset the phone,hope it'll work fine.If you have reflashed Button's Rom 1.05 and downgraded,it wud be better if you perform the CID unlocking procedure again through lokiwiz02b or WST_4.2.2,after that upgrade to IPL/SPL 2.xx by either flashing T_mobile 2.26 or any official aku 2 rom,then upgrade to any wm6.1 rom.
You can even take out the battery and leave it for 30 minutes,after that put it back and try to flash.
Hmm.. now I have rebooted the pc and disconnected the battery for 30 mins. No luck. Still the same error.
There must be something I have missed. I have flashed with several roms before w/o any trouble.
I am connected to activesync as a guest on usb-cable.
Oh i didnt downgrade because it failed that too. So right now im on a wm6 manilla pretty good rom but the wifi's gone
Try flashing from bootloader:
* Hold down the camera button and then softrest without letting go of the camera button.
You should se a pretty tri color screen with IPL/SPL Information.
* Connect Wizard to PC using usb and wait for windows to detect the drivers if they are not already installed.
* Start your RUU and follow the steps.
Normally this error occurs when trying to flash under vista, if this is the case visit a friend who has XP and take some coffee
It gets worse im afraid.. and I am under XP.
Now the phone wont pass the t-mobile bootscreen. It gets stuck when showing the IPL/SPL information.
I fail to enter the bootloader. Hopefully im doing something wrong.
I have tried this:
1) Holding down cam-button and pressing soft-reset. The phone boots as normal but stucks at same place.
2) soft-reset and when sceen goes black, hold cambutton. Doing this makes the boot halt totaly and the screen remains black. Looks like it turns off cause the softreset wont work and I have to press the powerbutton to get life signs again.
How (exactly) do I get it into bootloader?
Evolution... i managed to do a hard-reset and got the phone to boot up again. So back to square one with not being able to use the ubs+ruu
hmm very strange.. in a desperate attemt to get into bootmode i held down the voice-button instead of the cam-button and then power-on. Not it worked! Mystic....
***
update! problem solved
In case anyone else reads this. I rebooted the pc for the 10th time, rebooted the phone at the same time and (a dramatic paus here) i pulled the usb-cable and placed it in another slot in the pc. And there it goes...
I dont work with computers... i work against them!

Htc TOuch Pro Stucked on Startup

i've already did a research.
Manage to Go bootloader.
But i cant seem to reflash my rom.
Stuck at 0% and theres an eror that came out.
It's strange.
For the first attempt it was a sucess and i managed to stock the Original SPL
So after doing that i tried the Hard-SPL.
Stuck at 0% eversince.
What phone do you have?
GSM or CDMA?
For almost if not all ROMs here you MUST HAVE hardSPL!!!
Oh i did have rom previously.
And i wanted to try lunacieROM
so i did flash it.
and it's stuck on the Black Screen after sucessfully reflashing.
So i went to the bootloader.
Reflash the Stock SPL
and wanted to reflash the Hard SPL
but it failed.
Its GSM.
Don't know why you flashed back to a stock SPL but I assume after flashing to a stock SPL you should FIRST flash your (or a) stock ROM and start from scratch (stockSPL --> hardSPL --> new ROM).
the problem is
after goin back to stock spl.
i dont think i can flash other roms.
including hard spl
or any other roms.
any idea?
And it get stuck at 0%
everytime i try to hard spl.
thats the thing thats been bothering me.
rullly said:
And it get stuck at 0%
everytime i try to hard spl.
thats the thing thats been bothering me.
Click to expand...
Click to collapse
What PC do you have (OS)?
You get a reliable active sync connection?
Did you try to put the phone into bootloader mode (tri-color screen) while DISCONNECTED from USB - will read "serial" at the bottom of the screen- and connect USB while in tri-color screen - should change to USB?
That are some basics to check and to test.
You COULD try to connect the phone in storage mode that it forces your PC to install Qualcom USB/NDIS drivers.

Categories

Resources