Hi guys,
My SP3 stucks on bootloader
Spl Version is Typhoon SPL 2.5.0102 (I think it might be CID lock)
i had tried many of the things but no avail
I installed many of the roms ,it only changes spl version from 2.5.... to some other 2.XXXX version and then stuck on bootloader
i can't even use spv-service to unlock it
i don't want to use imei-check.co.uk and spend $40 on it
Please Guide me to solve this problem
Maybe you flashed your phone with 3rd party ROM without doing supercid. So try to flash your phone with original rom.
my phone was unlocked form super CID and i already tried to flash it with original rom but nothing happened . It starts and stuck on boot loader
Hey all,
I'm working un unbricking a hermes100 and I've been able to get the latese HARDSPL V7 on the device. I can boot the OS and get to desktop and what not but I can not flash a radio or flash ANY rom with a radio included. I've tried flashing from SD and it hangs at 11% everytime when it gets to GSM. Once it hangs I soft reset the device and it goes to bootloader. To get back to OS I have to flash the HardSPL again via SD card. Then I can boot phone again.
I think maybe it's bad blocks in the GSM??? I'm not sure. I've tried all the steps in the wiki regarding "unbricking your hermes" with no luck.
Any help would be great.!
Corrupted radio rom is a !00% brick at this stage.... No surefire way to fix, Sorry...
Well took the old girl shooting No more worries!
ultramag69 said:
Corrupted radio rom is a !00% brick at this stage.... No surefire way to fix, Sorry...
Click to expand...
Click to collapse
I have had a similar problem with my 8525. Once i upgraded using the hard spl 7 i started having freezing and locking up issues. I then tried to reflash the radio and it got stuck 11% everytime with stock rom as well. My phone was then stuck in boot loader so I used titan_exit boot loader and bam it was back up and running. Phone still has issues doesn't recognize pin.
I tried flashing my first ROM on to the GSM unlocked HD2, the rom came with both the RUU and the nbh files, however, after i finished the onscreen wizard from the ruu, when i went to boot up my phone, it is stuck at the HTC screen.
I can boot into serial mode, and can do a system restore. But it is still stuck at the HTC screen when booted.
What should I do to get the ROM on to the device and have it boot normally?
any help is appreciated
you can still boot the phone into the bootloader correct?
when in bootloader connect your phone to your computer with your usb cable
once the connection is established it should change from 'serial' to 'usb' in the bootloader
now from your computer, flash your phone's stock rom
if you are on tmo us make sure the rom is compatible with the US version
also make sure if you are tmous that you do not flash a radio with .51 in it
you didn't say what phone or what rom, but I suspect you need to flash a matching radio.
read the thread of the rom you flashed and there will likely be a recommended radio.
hey guys. so i got my hands on a buddy's hd2 to help flash but entering the tri-color bootloader and trying to flash it to a 6.5 rom, it shows that it does not have a previous image.
anyway, i go on trying to flash it but everytime is says error: corrupted image file.
any help?
edit: it's world wide HD2
edit 2:
it's just stuck on HTC Screen. plain white with HTC in the middle. does not go into WinMo6.5
HardSPL. Looks like you don't have it.
got 2.08 HSPL
The update utility never shows a previous version when you enter bootloader manually, because it pulls that info from the registry, which is inaccessible from bootloader.
i managed to flash the Energy ROM winmo6.5 using an sd card.
it stays on the splash screen and does not boot to OS. :\??
you need to flash the custom ruu inside the custom rom itself. not an sd card
only if i could. i cant access OS.
Dear all,
Some time ago some guy came over to me to have his phone (HD2) reflashed. I installed the HardSPL, eMagldr 1.13 and the 400mb file-system as needed for the rafdroid version I installed. Everything worked out fine. But now he has manually flashed CWM without changing filesystem etcetera and took out SD card and formatted it. The phone did actually boot in CWM, and he sold it to me. Now I wanted to do a factory reset, but the phone wouldn't boot anymore, nothing. I tried flashing back stock ROM, but the phone will not be found. I cannot even reflash the 400mb filesystem, it says RSPL.cpp missing... I'm running out of ideas and I'm starting to panic a little. So here are my problems:
- Phone crashed when booted into AD RECOVERY;
- Phone does not start up in any way, when lucky stuck forever in CWM bootlogo (for over 60 minutes);
- When booting into bootloader (volume down + power), a text "loading" should appear, but it doesn't;
I have no clue what to do from here. I don have the T-Mobile version of the phone I do know that . But it seems not to respond to anything which sucks. But I do get into MAGLDR with the menu choices so the device can not be ****ed up too bad.
Please advise me on this
Anteino said:
when lucky stuck forever in CWM bootlogo (for over 60 minutes);
Click to expand...
Click to collapse
Cwm doesn't have a boot logo, please explain?
When booting into bootloader (volume down + power), a text "loading" should appear, but it doesn't
Click to expand...
Click to collapse
Only if you have a correctly named leoimg.nbh on the SD card, and the SD card is 4gb or smaller, please confirm?
RE
You're right about the logo i meant CM ( cyanogen ) sorry for that, and no my sd is 4Gb and I named the file LEOIMG.nbh with capitals so going to try that ou tomorrow, but it still doesnt explain why my computer did not find my device with RUU update.. :s
Thanks for your help though you gave me some ideas
Leoimg in capitals should be ok,, correctly extracted from a stock rom? (People still sometimes make the mistake of simply renaming the whole romname.zip file, without extracting the ruu_signed.nbh file first)
Anteino said:
You're right about the logo i meant CM ( cyanogen ) sorry for that, and no my sd is 4Gb and I named the file LEOIMG.nbh with capitals so going to try that ou tomorrow, but it still doesnt explain why my computer did not find my device with RUU update.. :s
Thanks for your help though you gave me some ideas
Click to expand...
Click to collapse
When you try to run the RUU, does it say USB in the white bar of bootloader? if not you have adriver issue and need to install Active Synce(Windows XP) or Windows Mobile Device Center(Windows Vista and 7).
RE:
Yes it does say USB and I managed to do a vodafone update from the HTC site. Though I don't know if it was a vodafone branded device, but that shouldn't matter right?
Anyway, I'm stuck forever in the "HTC" screen in green letters. So this time I'm stuck way earlier. But I'm going to give it half an hour and see what happens. I had to run the update three times before it succeeded so I doubt it.
But another thing, now I ran the update MAGLDR will be restored in its factory form right? And recovery and **** has been removed so I could try to reinstall them and go on from there if the phone won't boot, right?
RE:
Now I can't even get into MAGLDR. The phone is stuck in the first bootscreen saying HTC for over 3 hours now, I turned off my phone and I'm running the update again now, getting errors again. What do you advise? I still got an 8GB sd cart in it but I read somewhere that is OK.
If you flashed a stock rom, magldr is gone, magldr is a hacked together bootloader from the dft hackers,,, there is no "factory form".
Most 8gb or larger cards wont flash nbh files, but some do,
If you downloaded the rom from HTC using your phones serial number, then yes, its voda branded.
I suspect some corruption, some variant of stuck radio, .
I'd start by trying to use hspl2.exe to set hspl 1.66.0000 then flash the stock rom from SD taking careful note of the blue writing during the flash,
As Samsamuel said if you flashed a stock ROM MAGLDR is gone4 and you will have to re install MAGLDR, You being stuck at the splash screen could be caused be the stock ROM you flashed not being the correct stock ROM cause if you flashed it via SD card you removed HSPL and there for if it is not the correct ROM it will not boot. Also if you flashed it via RUU and it is a older ROM version the HSPL 2.08 that you have might no be compatible with the ROM causing it to stick at the splash screen. Maybe this will help some.