Related
Hi guys.
I was using the installed the FInixNOver 3.0.1 ROM onto my SPV M700 and it was great. I've had it for about 2 weeks without any problems.
Last night I looked at my phone, only to realise that it was completley dead. This didnt shock me to much because the battery was running low, and i decided to let it die completley before recharging it again.
I charged my phone overnight and switched it on this morning, but the phone would freeze at the 'FInixNOver' splash screen (the numbers at the bottom of the screen would appear overlaying the splash, but the phone wouldnt go pass this point).
The only way to turn off the phone from this state is to eject the battery. I have tried removing the sim card, turning it back on in as many ways as possible but to no avail. I am able to get to the TriColor test screen (im running IPL-0.50 / SPL-1.30.Olipro) but with all the custom roms available, they all use the ROMUpdateUtility which requires the phone to have established an activesync connection initially (but this would mean my phone would have to be 'on completley' - so this is catch 22.)
For the record, my phone/battery died while my wired handsfree was attached (dunno if thats of any interest to anyone or the rom baker).
But it looks like the only way i'll be able to flash my phone is by finding a way to install the .nbh file without using the RUU method. Because I can put my phone into test mode manually.... any help or guidence would be very much appriciated.
Thanks.
Ok can you get it into bootloader? power/camera buttons and reset?
sorry didnt read fully.
right get your device into bootloader first,
then open active sync (are you using xp)
then open connection settings and disable usb connection,
put your device into bootloader mode, then run any rom upgrade, i prefer the WM6.1 pdaviets from HERE (Username: PDAVIET / Password: pdaviet)
Your pda does not need active sync with ruu's, so no catch 22. if you turn off usb connection in active sync, you can still run ruu and it will be recognised, unless you are using vista, where you need to change your HTC SYNC drivers.
Thanks for your quick response...
Yes I can get into boot loader using the power and camera buttons (or holding the power and camera buttons when resetting the phone)...
When the phone is in boot loader mode, active sync doesnt even detect the phone anyway, but nevertheless, I have followed your instructions and disabled the USB Connection. (BTW, yes i am using XP)
The phone is still in boot loader mode, so now i try and execute the ROMUpdateUtility.exe and go through the steps, at the 1st step i tick the tickbox and click next, and the 2nd step i tick the tickbox and click next. (this step says DO NOT enter the bootloader manually? - but i have havent i?) anyway, when i click next, it says... "Verifying the information on your Trinity... Please Wait..." for about 10 seconds, and then i get a message "ERROR [260] : CONNECTION"
What am i doing wrong?
Huumm.. why dont you flash your phone throw the sd card??
Read this link:
http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing
try to flash your phone with some official rom and after that flash it with any other you want!
manos_23 said:
try to flash your phone with some official rom and after that flash it with any other you want!
Click to expand...
Click to collapse
I would recommend this option above, to be safe, i usually get them error messages when the battery is below 50% or sometimes i try it again and it works. it does state do not manually enter bootloader but i always do it this way.
also make sure active sync is not still running in taskmanager under the alais: wcescomm.exe and WCESMGR.exe, end them both.
I've just tried using an official ROM, but the problem still occurs with the 'connecting'. It doesnt seem that the computer picks up a connection to the phone whatsoever.
Should i be concerned that at the bottom of the bootloader screen it says "serial", is this correct?
Im starting to get annoyed now.
Bye,
the bottom of the sreen mast say "usb" not serial.
it seems there is a problem, if it states serial. as it should say usb. try THIS
Seems like the problem was that my USB lead was loose and made a bad connection, hence why the bootloader showed 'serial' and not 'usb'... as soon as i wiggled it and heard the 'connection noise' in windows, i knew i was good to go, and so using the RUU worked fine to reupdate my phones ROM.
Thanks for your help.
My only question is that why did it happen in the first plave?
WIZZKID - I just saw your post here now. I have to tell you that I also saw "SERIAL" at the bottom of the bootloader screen and not "USB". As I said I returned it to get another phone but maybe I will try something else for now instead of a P3600i. I will monitor your thread to see how it turns out for your phone, because it seems that we have the same problem.
if you see "serial" instead "usb" your problem is in the usb cable, usb port from your computer or in the usb connector from your trinity!!!!!
I was having the same problem that you have!! my problem was from my usb from mine trinity!! see if the conector is at good conditions !!!
Well as some of you may know, I got my Trinity replaced for sticking at the WM splash screen after a few days. This second one - I have had it ONE night - and the same thing has happened with incomplete booting. This time I have been trying all night to flash the phone to an official ROM, but I cannot do it (apparently) because I can't establish a connection via ActiveSync. When I stick the data cable in while in bootloader I see SERIAL replaced by USB and when I try the flash I get a "270" error (cannot connect to phone) and the phone re-boots to the sticking plash screen. What should I do now?
ladies and gentlemen...
we've got a lot of mixed messages in this thread.. please make sure you're posting the right thing. no need to disable USB when manually going in to bootloader to flash (at least in xp).. Also, you can ignore the part of the RUU that says 'do not manually enter bootloader' (you should really read the guide on my site)
foxuniform- can you please give some details..
1) are you running xp or vista
2) have you flashed hard-spl? if so what version?
in the mean time, try a couple of things.. first, flash hard-spl (even if you already have it, but from the sound of it i think you don't have it on your device).. if that works, try to flash an official ROM. Can also try to use splxploit, then flash hard-spl, and then flash official ROM (there's a guide on my site if you're unsure)
please post your results
*edit*
here are the steps for SD card upgrade, but i HIGHLY recommend flashing Hard-spl first..
try to do it from SD card. how?
Extract the .NBH file from your prefered ROM upgrade: In windows use winrar (right click) to extract the contents of the exe file. In Linux / MacOS use cabextract (http://www.cabextract.org.uk/) .
Rename the .NBH file to TRINIMG.nbh and copy it to the root folder of your miniSD card.
With miniSD card inserted on the phone, start the bootloader (hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom).
You should see the screen pictured on the left, confirm flashing on screen by pressing the power button.
Flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
When flashing completes soft-reset your device.
Make sure your SD has FAT32 and has no label. There have been reports that if SD has a label the bootloader can not access the TRINIMG.nbh
racerx_ I have carefully read your response and suggestions, and thanks for your expertise input on the matter. I am fairly new to this stuff so read below carefully as you may find errors in the way I tried to go about doing what I was hoping to accomplish.
First let me answer your questions. I am running Windows XP. The phone is in it's completely natural state in that I have not flashed it in any way. The ROM I was TRYING to flash to the phone while it was not starting properly (this is where I manually entered bootloader) is an official ROM from the HTC website (please note everyone that when I registered my P3600i on the HTC website it came up as the Dopod 810). Anyway, that never worked. ActiveSync never detected the phone (and I guess that's the reason I could not do anything as far as flashing goes). I HARD-RESET my P3600i and it booted normally. I re-installed all the stuff I had on it, from memory card to various .cab files, and the phone is working beautifully thus far. I will report if anything funny happens again.
I have to ask you racerx_, if I CAN flash hard-SPL on the P3600i according to the lovely guide on www.trinityguides.info. I have been of the opinion that things don't work for the P3600i as they did for the P3600, and that has been echoed by many P3600i users on this forum who are ready and waiting to try out some cooked ROMs (myself included).
For the sake of record, my phone is running rom version 3.00.707.17 and radio version 1.46.00.11. I patiently await your response.
woaaahhh..
i didn't notice the 'i' in your previous post... yeah, as far as i know, these ROMs are not flashable on your p3600i.. sorry..
**correct me if i'm wrong somebody**
Yeah I kinda thought that would be your response. By the way - do you think that this phenomenon of sticking at the Windows Mobile splash screen (both the P3600 and P3600i models apparently) has anything to do with something users do with the devices, or you figure it's an inherent software glitch of some sort? I am wondering if I should try a different model or hold on to my P3600i? Hope it's not something that'll happen again - I fly for a living and it's not gonna be good to have the thing screw up on me away from base - I really count on it for everything from casual keeping in touch on Messenger to viewing my work schedule. I love the Trinity though - it's one of my all-time favourite HTC phones.
hmm... i don't think its inherent in the Trinity.. (not a hardware issue.. in my opinion)
its been a while since i followed the posts on it, but always seems to be software related.. sometimes ROM-specific problem. Personally, i've probably flashed as many ROMs as anyone and the only time i ever encountered problems was with the official HTC WM6 ha.. go figure.. I think ppl did find that hard resets before and after flashing are helpful as well..
i love my trinity, and there's not much else on the market to make me want to trade it in (is it just me, or have pda's kind of stopped getting cooler).. i'd stick with it..
Hey guys,
I have the Bootloader all happy and running but after flashing the Radio (I did this because I thought it would fix random crashes and GPRS crashing) the OS just hangs in boot even after hard resetting.
How do I go about flashing when in Bootloader mode?
Cheers,
Callum
EDIT: I tried with the TTY app (mtty) but it fails to show a USB port. I noticed that Windows XP just sits on acquiring network address.
Hey.
You must deactivate AcitveSync --> "Allow USB Connections" and kill all ActiveSync Processes.
If you have Vista you need other Drivers. Search in google 'VistaRUU'.
You could Flash VIA SD Card from Bootloader, just try to search a little bit in google.
cu
pOpY
If you have installed in the past Hard SPL, you should be able to flash a new ROM from the bootloader screen. Simply choose Hard SPL on the installer.
I have a SIMILAR ISSUE I I have issues with an old Hermes not gonna get into it, but I gotta outta what I thought was my WORST mess ever. Now my 8525 boots (I have the Official AT&T WM6 ROM) see all the opening screens and BOOM it JUST HANGS on the TOUCHSCREEN CALIBRATION screen!!! Touchscreen is completely UNRESPONSIVE so are 90% of the rest of the buttons I can power off and use the side scroll Blackberry dial, and I think the Right SOFT KEY brings UP a USELESS menu, BUT I AM STUCK AT THE CALIBRATION screen no touchscreen I have done A Hard Reset 1000 times, I can connect via ActiveSync with my PC, cant Flash Anything though I get ERROR 260 So I just have a booting 8525 stuck on th4e calibration screen
ANY IDEAS??????????/
nicknowsky said:
I have a SIMILAR ISSUE I I have issues with an old Hermes not gonna get into it, but I gotta outta what I thought was my WORST mess ever. Now my 8525 boots (I have the Official AT&T WM6 ROM) see all the opening screens and BOOM it JUST HANGS on the TOUCHSCREEN CALIBRATION screen!!! Touchscreen is completely UNRESPONSIVE so are 90% of the rest of the buttons I can power off and use the side scroll Blackberry dial, and I think the Right SOFT KEY brings UP a USELESS menu, BUT I AM STUCK AT THE CALIBRATION screen no touchscreen I have done A Hard Reset 1000 times, I can connect via ActiveSync with my PC, cant Flash Anything though I get ERROR 260 So I just have a booting 8525 stuck on th4e calibration screen
ANY IDEAS??????????/
Click to expand...
Click to collapse
check out this link
http://forum.xda-developers.com/showthread.php?t=382578
If you've Hard SPLed your hermes, try the sd card method. 1st, you need to back up your card, format it fat 32 then copy the .nbh file onto from the rom of your choice. rename the nbh file to "Hermimg.nbh" then insert into phone. put hermes into bootloader and follow the prompts. this will reflash another os. Hope this gets you out of your pickle... cheers
I couldn't find an answer for this so I hope someone can help.
My friend's XDA Orbit won't boot.
It goes to the blue O2 screen (first screen when turning on, showing IPL, SPL etc) waits a short while, and then the screen flickers/shimmers - and that's all it does. No more loading.
I guess this is probably the point where the green Windows logo is normally shown (I have several HTCs but not an Orbit so I am guessing).
Now I know I can try a hard reset but there are valuable things on there so I don't want to try that.
Is there a way to get the information from the phone?
Is there a program/s that will allow me to boot from SD card and recover files?
Is there a way to connect using a pc (and sync program) and browse the phone and copy things over to my pc?
I tried starting up in bootloader mode (holding down voice-recorder button while soft resetting) and that worked fine but as I said, I don't want to install any roms and wipe anything that was already on the phone.
The phone is standard (factory rom), no new apps were added and nothing was changed on the phone.
Any ideas please?
try to reinstall os
I have the same problem: http://forum.xda-developers.com/showthread.php?t=599000
Try to flash new ROM, maybe it helps you.
Hey, xda-devs.
I need a bit of help. I was trying to flash Eclair 2.1 Polymod to NAND on my AT&T Tilt on T-Mobile's USA network. I was previously using Dutty's Diamond v1 and Myn's Warm Donut from haret.exe
Unfortunately, I was kind of stupid while flashing - I decided I was going to flash KAISIMG.nbh *before* I actually put the /andboot folder on there. (This was due to a lack of research on my part because I only looked at one how-to which omitted the /andboot step.)
"Well that's fine," I thought, "I'll just put the /andboot on there with the polymod inside and re-flash KAISIMG.nbh!" I did this, and it's still not working... which doesn't make alot of sense to me. My KAISIMG.nbh has no issue flashing, but when I restart the phone I get stuck at the first HTC splash with the planet & whatever.
I've tried multiple panels for the KAISIMG.nbh, I made sure nothing else was on the SD card, and I even tried a hard reset of my phone, still to no avail.
So tell me, xda-devs. Did I brick my phone? I don't think I did because it actually powers on and all that jazz, it just won't load the android install program.
dont think it is bricked
if you can get into the 3 colored bootloader screen it is not bricked. just flash wince rom and you should be able to use your phone again.
if you flashed an android nbh you should get the linux logo and see bunch of text scroll over your screen. it you hit the dpad you should get into the installer menu.
Maybe you didn't actually flash the nbh?
did you get into the tri colored bootloader screen and then did you hit power when prompted?
the android kaiser nbh normally doesn't have a splash screen, so your old wince splashscreen will remain.
hope this help, more details from your part would help us help you.
Hey, thanks for replying
Yes, I get the tri-color screen but I'm not getting the linux logo or anything of the sort. I'm getting the old splash screen that came with the phone. When I passed the tri-colored screen I get the prompt to press the power button, then it flashes KAISIMG.nbh, (Although it says something like "File - KAISIMG.nbh" and "OS - " then nothing after OS... dunno if that helps)
But I'm glad to know I didn't brick it!
I experimented with various KAISIMG.nbh files found here. I believe those are Android KAISIMGs although I don't know since I can't read them with my text editor.
It could be the problem I have once in a while on my Kaiser. Try removing the battery and hold down the power button. Put the battery back in and turn on your kaiser. You should start seeing the scrolling text.
As far as I know that's normal. Happens once in a while.
Dukenukemx said:
It could be the problem I have once in a while on my Kaiser. Try removing the battery and hold down the power button. Put the battery back in and turn on your kaiser. You should start seeing the scrolling text.
As far as I know that's normal. Happens once in a while.
Click to expand...
Click to collapse
Negative, no change... How long should I hold it down?
You're holding down the button to release any power left in your phone. Sometimes, it can be a hit or a miss.
If all else fails, invoke the loader by holding down power button + camera button, and then press the reset button with the stylus. Do this quickly when you turn on your phone, and you can problem load WM back onto your phone.
I think Android needs a custom HardSPl on Kaiser.
As far as the old splash screen is concerned, thats normal, flashing the nbh does not replace the splash screen, after flashing the nbh you usually have to pull the battery, wait a bit, then restart the phone, it takes a little time before the linux kernel boots the lcd panel, so at first it shows the splash screen for some time.
The screen will go weird briefly, followed by the scrolling text as linux kernel boots, watch for the 'hold dpad to enter installer' line, then press dpad centre button.
Don't worry about the need for a 'custom' HSPL, the hard-spl most of us use seems to work fine for majority of users, also although radio 1.71.09.01 is recommended, android will work fine with earlier radios, some even say it works better with some earlier radios, ( can't confirm this, since I seem to have no problems with anything radio related).
If you need to reflash WM, you can do this either using the bootloader in usb mode, or by putting a WM rom in SD renamed to kaisimg.nbh and flash by doing the power+camera method.
zenity said:
As far as the old splash screen is concerned, thats normal, flashing the nbh does not replace the splash screen, after flashing the nbh you usually have to pull the battery, wait a bit, then restart the phone, it takes a little time before the linux kernel boots the lcd panel, so at first it shows the splash screen for some time.
The screen will go weird briefly, followed by the scrolling text as linux kernel boots, watch for the 'hold dpad to enter installer' line, then press dpad centre button.
Don't worry about the need for a 'custom' HSPL, the hard-spl most of us use seems to work fine for majority of users, also although radio 1.71.09.01 is recommended, android will work fine with earlier radios, some even say it works better with some earlier radios, ( can't confirm this, since I seem to have no problems with anything radio related).
If you need to reflash WM, you can do this either using the bootloader in usb mode, or by putting a WM rom in SD renamed to kaisimg.nbh and flash by doing the power+camera method.
Click to expand...
Click to collapse
Yeah, that's the problem - I've flashed the .nbh, then taken the battery out for 10+minutes (including the method mentioned above of draining the power) but the screen never changes from the first splash page. I never get the scrolling text.
EDIT: I have a theory that maybe I should try the Panel 1 kaisimg.nbh instead of Panel 2 but since I don't have a computer that has a micro-SD slot it's a pain in the ass getting files on/off of there so I'll have to try it later. I'm also going to try with another built (Probably Myn's) to see if that works.
I got myself a cheap sd card reader and microsd adapter, makes life so much easier, however if you don't have access to one at the moment, just remove any sd in the phone, disable activesync, put the phone in bootloader, connect to usb cable, flash a WM rom, ( try a Stock HTC one from the wiki pages, this wipes everything, os,bootsplash,radio and gets rid of any traces of any custom roms).
And try running from SD to identify your panel type, etc, saves some time when flashing nand if you don't have to guess
Following the instrcutions tp flash back to WM:rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH. Place the SD into your Kaiser and hold the Power button and camera button down, then take your stylus and hit the reset button.", after I pressed the power button again, tri-color screen changed to a whie screen with "Loading..." showing. There was no progress bar below as usual. After about 5 minutes, I reset it, Kaiser runs android system well: I can even install a new anroid system. Just can't flash any NBH file, even Android small NBH file. Tried with a newly formarted fat32 card also. It always stop at "Loading.. " screen.
Anyboby can help me?
alwayssomewhere said:
Following the instrcutions tp flash back to WM:rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH. Place the SD into your Kaiser and hold the Power button and camera button down, then take your stylus and hit the reset button.", after I pressed the power button again, tri-color screen changed to a whie screen with "Loading..." showing. There was no progress bar below as usual. After about 5 minutes, I reset it, Kaiser runs android system well: I can even install a new anroid system. Just can't flash any NBH file, even Android small NBH file. Tried with a newly formarted fat32 card also. It always stop at "Loading.. " screen.
Anyboby can help me?
Click to expand...
Click to collapse
1st
I have never used the stylus reset to flash nbh. (good thing too because I broke it long before switching to android)
just holding the camera button while powering on gets me to the tri-color and then a white screen telling to press power button again to flash.
2nd
I have had freeze-ups on that screen while "loading" and it is usually because of a bad/corrupt nbh file or not making sure all caps in file name KAISIMG.NBH
just a thought...
mnjm9b said:
1st
I have never used the stylus reset to flash nbh. (good thing too because I broke it long before switching to android)
just holding the camera button while powering on gets me to the tri-color and then a white screen telling to press power button again to flash.
2nd
I have had freeze-ups on that screen while "loading" and it is usually because of a bad/corrupt nbh file or not making sure all caps in file name KAISIMG.NBH
just a thought...
Click to expand...
Click to collapse
Tried with KAISIMG.NBH, nothing different!
Anyway, Thanks!
Try clearing everything on the sdcard and leaving only the KAISIMG.nbh and remove the diag file too.
You should have one file (KAISIMG.nbh) on your sd.
NOTE: If the phone is off you only need to hold the camera and press the power button. If the phone is on just hold the camera and press the reset button. There's no need to hold the reset AND power button.
Since you can access the bootloader there is another way to flash, by USB.
You will need to do a little preparation.
If using XP disable Activesync by going to connection settings and uncheck 'Allow USB Connection'.
Then make a temporary folder somewhere handy, I usually use c:\flashtmp, but anything is good.
In this folder goes KaiserCustomRUU.exe, and the NBH renamed to RUU_Signed.NBH.
Once you have all this, put kaiser in Bootloader, it should say Serial at the bottom, attach the USB Lead, and wait until it say USB at the bottom, then run KaiserCustomRUU.exe and follow the instructions.
You should be able to flash Radio, splash, or OS with this method.
i usually do it the way zenity describes...its easier for me to keep up with all of my nbh
the few times i did it from SD i DID NOT have kaisdiag.nbh...other threads said it was unnecessary, so maybe its even bad
btw everyone i found that KaiserCustomRUU.exe will take a nbh named anything as long as its the only one in the DIR. found this by forget full accident
One thing zenity forgot to mention was that you need to remove kaisimg.nbh from your sd before putting into bootloader. Or just remove your sd
loserskater said:
One thing zenity forgot to mention was that you need to remove kaisimg.nbh from your sd before putting into bootloader. Or just remove your sd
Click to expand...
Click to collapse
you can techically leave it there. in spl there is the option to not load the .nbh...after selecting that you can plug in USB like normal
Ah yes, I did forget the removal of the SD card, it may not be necessary in this case, but generally it's a better practice, saves confusion.
Didn't know about customRUU accepting any NBH though, always good to learn things
Regarding KAISdiag, I have never used it, so leaving it out is safe, in fact I'd only use it as a last resort for bad flashes or problems that require it.
zenity said:
Since you can access the bootloader there is another way to flash, by USB.
You will need to do a little preparation.
If using XP disable Activesync by going to connection settings and uncheck 'Allow USB Connection'.
Then make a temporary folder somewhere handy, I usually use c:\flashtmp, but anything is good.
In this folder goes KaiserCustomRUU.exe, and the NBH renamed to RUU_Signed.NBH.
Once you have all this, put kaiser in Bootloader, it should say Serial at the bottom, attach the USB Lead, and wait until it say USB at the bottom, then run KaiserCustomRUU.exe and follow the instructions.
You should be able to flash Radio, splash, or OS with this method.
Click to expand...
Click to collapse
Tried as your instruction with SD card and SIM card removed, when going to step to run KaiserCusomruu.exe, there is always a "communication error showed on PC screen, and recovery didn't make any difference.
I noticed that my SPL is SPL-3.34.0000, instead of SPL-3.34.0000. May it is beacause I flashed stock rom befored. How can I flash Hardspl in android system. I don't know how to copy jumpspl.exe to kaiser in android system.
You should be able to flash a stock winmo rom using the above method, since stock does not need HardSPL.
Sent from my HTC Kaiser using Tapatalk
zenity said:
You should be able to flash a stock winmo rom using the above method, since stock does not need HardSPL.
Sent from my HTC Kaiser using Tapatalk
Click to expand...
Click to collapse
Thank you for your help!
I downloaded the stock rom for my kaiser, and finally I flash back to WM following your instruction. Before, I tried a wrong stock rom.
By the way, the battery problem has been solved for Android system? I have 2 pcs of battery.