Anyone know what the issue is here please?
00018003
LEOIMG.nbh - FAIL
RADIO_V2 - RSA FAIL
Tried flashing through AS, no joy, so now trying using SD
Whatever ROM i try to flash i get this same message
Erm......HELP PLS!
LOL, anyone?
I can't help but wonder how the hell i'm gonna charge the battery as it won't let me in it's current state, due to failed flash
I have the same problem? Anybody help??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try another rom can help
radio fail, or stuck radio, is pretty terminal, usually.
It has occasionally been bypassed by flashing a custom rom which doesnt try to update the radio, and sometimes the 'chill phone in fridge' trick works, , , it seems there are a few different sets of circumstances that lead to 'stuck radio', some overheating, some bad blocks, and i think sometimes the spl refuses to change too, in such circumstances.
i've the same problem.. how i can solved the problem?
bladenet said:
i've the same problem.. how i can solved the problem?
Click to expand...
Click to collapse
as sam notes, try flashing a radioless ROM, try the fridge trick, try flashing again,
Related
Hi,
I've experienced something strange.
The Dopod 818 Pro of a friend of mine started with being unstable (random restarts).
Once the Dopod 818 Pro stucks at the "Windows Mobile Screen", she unplugged the battery and inserted it again. Started that thing and it stucks at the black screen where all the Versions are mentioned.
I've decided to reflash the RUU 2151327_21513121_021921. Now this phaenomen happens:
When I turn it on then I see this screen. (Pic1)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after about 7 seconds the screen turns white with vertical lines (Pic3)
and restarts with this screen (Pic2)
Has anyone experienced this problem so far?
...
I've noticed that the Radio Version is not displayed after the first restart. Do you think that a Radio upgrade would solve this problem?
Or is a HTC RMA request the only way out?
thank your in advanced for your help.
kind regards,
phurx
try to reflash your ROM again, it could be help
ok thank you.
I'll let you know.
kind regards,
Phu
ok, I've tried to flash it several times but the problem isn't solved.
Shell I try a Radio Upgrade?
How can I do it by the bootloader?
thank you.
kind regards,
phu
So yeah, I just went through the process of putting on the 2.40 Olipro bootloader, the new radio, and the new dcd 2.3.2 rom on, and my camera doesnt work. I get this error (Unable to initialize camera. Failed to set up the camera device.):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas as to how to resolve this? In all honesty, I just received this phone as a replacement to mine that died, and I never did try the camera before I put all these new roms and whatnot on. So it could just be a bad camera I guess. But any ideas as to how to diagnose/resolve this would be awesome. Thanks.
daniel981 said:
So yeah, I just went through the process of putting on the 2.40 Olipro bootloader, the new radio, and the new dcd 2.3.2 rom on, and my camera doesnt work. I get this error (Unable to initialize camera. Failed to set up the camera device.):
Any ideas as to how to resolve this? In all honesty, I just received this phone as a replacement to mine that died, and I never did try the camera before I put all these new roms and whatnot on. So it could just be a bad camera I guess. But any ideas as to how to diagnose/resolve this would be awesome. Thanks.
Click to expand...
Click to collapse
Read the last couple of pages of the DCD 2.3.2 thread...apparently it is not compatible with the new 3.35 radio. This might be another symptom.
http://forum.xda-developers.com/showthread.php?t=371314&page=86
Hi friends,
Las week I tried to upgrade my herald but something went wrong and my pda crushed few times. (It looked like video card driver error on PC)
I tried ro reload WM5 but could not manage. I tried few times, but could not manage.
Before I crashed to the black screen, it was womething like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IPL 4.17.0001
SPL 4.17.0000
Please help me and explain what to do (in a way , understandable by dummies!)
Thanks in advance..
Have you tried the "how to fix a brick" thread?
It's a step by step guide on how to fix this.
Also, it helps to know what you were trying to flash. If you were flashing HardSPL, it's one thing, but if you were just updating to a newer version of the stock HTC ROM, then you may be having a problem going back to the default wm5 since the wm6 ROM updated your SPL. Try the stock wm6 ROM again.
There are many many guides to help you with this scattered around here so don't worry, one way or another, you'll get your phone working again.
I've already rooted this thing like 3 or 4 times and gone back to stock for repairs since I'm flashing for Cricket. Now it wont root. Here's the entire Root CMD:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The first few times I did it, it worked flawless. But now I've tried 3 times, and it just goes about with this error.
Never seen that one, maybe try downloading the root file again?? Just a thought... seems like its not installing superuser properly
Sent from my rooted froyo Fascinate
Ok, that worked. I also ran it directly from CMD this time instead of clicking Start_Root.bat... Thanks.
same problem
I am having the same problem, I have tried it manually also but with the same results. It seems like the rage.bin loads properly because I get a reply stating so. It hangs up on the changing of permissions even when I try it manually, any thoughts? I did so the Verizon OTA and now when the phone reboots it tries to load some other verizon junk I was thinking maybe the .bat file is timing out can I change the delay in the file?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just as the picture above shows, when flashing kernels made by devs, it says 1bad blocks encountered in the fastboot window, and when flashing finished and try to start up the phone, the phone just vibrate once and lose response. The screen even doesn't turn on.
I have unlocked the bootloader.
The only way to fix the phone after flashing a kernel is using the flashtool to flash a ftf file.
Do you guys know why this thing gonna happen?
you flashing kernel that arent compatible maybe?
from my ARC using I.See.Ass
rashid.fairus said:
you flashing kernel that arent compatible maybe?
from my ARC using I.See.Ass
Click to expand...
Click to collapse
Nope, I have flashed kernels made by Doomlord, Jasonstein, FXP, non of the worked.
you have broken nand
send phone to service for nand replacement (of board replacement)
dun know the non-unicode language will affect the DOS code or not , cause u using the chinese non-unicode .... need ask those pro to conform