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
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
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.
HEY guys
need some help
well i did everything like in the manual .
the 3 button work for me and i followed the entraction .
i update the phone but i cant get into the black screen (dos) install
noting worked i press in the center so long and noting worked
right now i am in kind of truble cuz i did hard reset after to get back into windows mobile and i am stuck in newpan telecom screen white screen
cant get my phone back up online
please help!!!
I'm not sure what you mean??? Have you flashed an android NBH (kernel) to your phone or are you trying android from sd card using haret? If you have already flashed an android nbh then doing a hard reset won't work because windows isn't in NAND anymore so there is nothing to restore. You will need to get a windows mobile nbh from the windows mobile section of the forum and put it on the root of your sd card and rename it to KAISIMG.NBH. You then need to hold down the camera button and power button together and the phone should turn on and go to the tri-colour screen where it will ask you if you want to flash your phone, press the power button and when it says it is complete reset the phone using your stylus. In terms of your problems getting into the install screen so you can install android, have you tried holding down the centre button on the dpad, or once the writing has started scrolling hold down the centre of the touchscreen should also work.
hey thanks for replay i worked from this menu :
#1 Does your Kaiser already have HardSPL? If not then get that done. Recommended to install 3.34 HardSPL.
#2 Does your Kaiser have a relatively new radio rom? If not then get one. Recommended to have 1.70.xx.xx and up.
#3 You don't need to SIM unlock you Kaiser, but it's a nice and easy precaution. Download KaiserUnlocker.exe to unlock your SIM. If you've already flashed your phone with Android, you'll need to flash back Windows Mobile 6.1. Go to the end of this post and it'll explain how to flash back to Windows Mobile. Bellow, you can see how easy the application works. Make sure your Kaiser is synced with your PC and follow steps 1 through 3. This means Windows Mobile Device Center, if you don't already have it. You should already have HardSPL from step #1, but this is an easier method to get it if you haven't done it yet, and you can always upgrade to 3.34 later, as this installer installs 3.29.
#4 Install a Android kernel. You can get the latest kernel from Dzo's site. Only download the newest Kaisimg file and choose the .nbh file that fits you. For example, "panel2" is for Kaiser owners with type 2 LCD screen, and 320 is if you want 240X320 resolution. Alternatively, you can download a kernel from kallt_kaffe, as he can make some changes which might not immediately show up on DZO's site.
You'll need to edit the NBH file using Loser's NBH Editor. The tool is very simple to use. Change resolution to the desired resolution you want, HW3D to the type of Android build you're using, Panel Type to the type of LCD screen you have, and finally keyboard type to the keyboard language you use. If you need more information on what panel type is, go to this link. The older and more complicated method to edit the NBH file can be found at the very bottom of this post.
#5 When you're done editing the .nbh, save it and rename it to KAISimg.nbh and place it on you memory card. You may want to put the KAISDIAG.NBH, but I've found it not necessary.
#6 Place the SD into your Kaiser and hold the Power button and camera button down, then take your stylus and hit the reset button. Follow the instructions on the screen to flash your Kaiser. When flashing is done, reset the device with your stylus. Make sure you see the confirmation that it is done.
!!WARNING ALL DATA ON YOUR PHONE WILL BE LOST!!
If the above method doesn't work, you can try this suggestion below.
Originally Posted by zenity
If you are experienced at flashing Winmo using KaiserCustomRuu,exe through activesync, then you can do the same with the KAISimg.nbh, just rename it to RUU_Signed.nbh and copy it to a folder on the pc along with Kaisercustomruu.exe, flash as you would with winmo.
#7 Download your favorite Android build. I use Incubus26Jc's Super Eclair, but you can use anyone you want. Only Donut builds like Myn's Warm Donut has everything working 100% on the Kaiser. Eclair builds are currently missing Camera and BT audio.
#8 On your SD card make a folder called andboot and place the androidinstall.tar file in there. It could also be called androidinstall.tgz. You may have to change settings in Windows to see extensions.
#9 Place the SD card in your phone and power on your Kaiser. When you see text on your screen hold down the D-pad. D-pad is that button in the center of your up, down, left, right buttons. Keep holding down the D-pad until you see something like this appear on your screen.
#10 Select sys on NAND, then data on NAND. Once done then select Install system and wait for it to finish. Once it's done select quit and it'll begin booting into Android.
right now i tryed to flash back to windows mobile with KAISIMG.NBH KAISDIAG.NBH
in sd card but the kaiser is restarting every 5 sec
damn i think i lost my phone
Have you got into the tri-colour screen yet? If not then pull your battery out and put it back in. Hold down the camera button while you press the power button and this should take you to the tri-colour screen which will detect the KAISIMG.NBH on the root of your sdcard. If you do not go to the tri-colour screen you have either not pressed both buttons simultaneously (i.e. pressed power before camera) or you have a hardware failure. Nothing that you have flashed will effect the tri-colour screen as this is hard coded onto the mainboard and cannot be overwritten.
First of all - I am a Sprint customer with the Latest Htc Rom -stock
List of problems and actions taken.
Problems
Soft reset reboots with phone in Airplane mode.
When the end key is pushed not long pressed but pushed it puts phone into Airplane mode.
Battery run time is not about half or even less than it was before.
Actions taken
Removed battery for about 10 minutes and tried a hard reset. Got to the screen where you are supposed to hit volumn up to restore to original and well the volumn up button gets pressed but nothing happens. So after waiting for about 15 minutes I do a soft reset to get back to the HTC Sense screen (today screen). I take the phone out of Airplane mode cause from reset. I hit the volumn up button and it works fine. I tap the end key and it puts me back in Airplane mode.
So I reflash stock rom back in that by the way wouldn't go until I unlocked the phone with HardSPL. Apon first reboot it still boots with phone shutting down into Airplane mode. Turn phone back on then turn power off. Take battery out. Replace battery. While holding Talk ad End buttons I tap power on for hard reset. Goes through try colored screen then to the volumn up option screen. I tap volumn up and nothing still happens.
I'm looking at Task 29 but I am worried about the volumn button not working.
Anyone have any ideas on what direction to take. Thank you
Hootyhoo said:
First of all - I am a Sprint customer with the Latest Htc Rom -stock
List of problems and actions taken.
Problems
Soft reset reboots with phone in Airplane mode.
When the end key is pushed not long pressed but pushed it puts phone into Airplane mode.
Battery run time is not about half or even less than it was before.
Actions taken
Removed battery for about 10 minutes and tried a hard reset. Got to the screen where you are supposed to hit volumn up to restore to original and well the volumn up button gets pressed but nothing happens. So after waiting for about 15 minutes I do a soft reset to get back to the HTC Sense screen (today screen). I take the phone out of Airplane mode cause from reset. I hit the volumn up button and it works fine. I tap the end key and it puts me back in Airplane mode.
So I reflash stock rom back in that by the way wouldn't go until I unlocked the phone with HardSPL. Apon first reboot it still boots with phone shutting down into Airplane mode. Turn phone back on then turn power off. Take battery out. Replace battery. While holding Talk ad End buttons I tap power on for hard reset. Goes through try colored screen then to the volumn up option screen. I tap volumn up and nothing still happens.
I'm looking at Task 29 but I am worried about the volumn button not working.
Anyone have any ideas on what direction to take. Thank you
Click to expand...
Click to collapse
Which model is your device? You can find the model number above the barcode that is under your battery. It will be in the form of RHODxxx where "xxx" is a three digit number. From here, I'll be able to help you a bit better once I know which model you are using.
Thank you for the reply. The model# is M8RHOD400. Since my first post I have tried flashing other Roms and I think it was the Sharkie Rom that actually said it could find the end key file. Other than that all the other Roms I tried pretty much do the same. When end key is tapped it shut phone off. Plus the volumn up still doesn't work at the hard reset state. It works normal otherwise but when I try to hard reset it will not go past the first screen that says press vol. up to reset. Thanks again so far.
Hootyhoo said:
Thank you for the reply. The model# is M8RHOD400. Since my first post I have tried flashing other Roms and I think it was the Sharkie Rom that actually said it could find the end key file. Other than that all the other Roms I tried pretty much do the same. When end key is tapped it shut phone off. Plus the volumn up still doesn't work at the hard reset state. It works normal otherwise but when I try to hard reset it will not go past the first screen that says press vol. up to reset. Thanks again so far.
Click to expand...
Click to collapse
Ok, so the first thing we need to test for is hardware fault. To do this, you will need to perform a task29 and then flash the latest Sprint ROM. After that, try to see if you have the same problems. Please do not install anything while testing. If it works fine like this, then we will need to do some specific testing on the custom ROMs to narrow down the cause.
Things have changed a bit. Long morning. I tried flashing a few ROMs to see if any would fix it. I know a feeble attempt. Well one went bad and never got past the splash screen when it went to restart. Won't connect to ActiveSync. So I tried reflashing from SD card. and I get to
RHODIMG.nbh
OS -
Press Power button
to start update image
Press VolDn button
to cancel update image
The problem is I press power button and nothing happens. I press any buttons and nothing happens. I pulled the battery and reinstalled it and got the same again. I tried to run Task 29 but how. Won't load. Tried renaming rbh file but got the same results as above. I need a way to hard reset without buttons and its obvious that nothing working outside of windows. I'm lost.
Hootyhoo said:
Things have changed a bit. Long morning. I tried flashing a few ROMs to see if any would fix it. I know a feeble attempt. Well one went bad and never got past the splash screen when it went to restart. Won't connect to ActiveSync. So I tried reflashing from SD card. and I get to
RHODIMG.nbh
OS -
Press Power button
to start update image
Press VolDn button
to cancel update image
The problem is I press power button and nothing happens. I press any buttons and nothing happens. I pulled the battery and reinstalled it and got the same again. I tried to run Task 29 but how. Won't load. Tried renaming rbh file but got the same results as above. I need a way to hard reset without buttons and its obvious that nothing working outside of windows. I'm lost.
Click to expand...
Click to collapse
First of all, you should stop trying to update with the SD card. That's the problem you're having, so we need to try something different. Flash it via USB. You don't need an Activesync connection. It just needs to change from SERIAL to USB at the bottom of the bootloader screen. Once that happens, simply run the RUU and it will flash to your device. Do task29 first. Then do the stock Sprint ROM. Task29 cannot be flashed via SD anyway. The NBH file in task29 is a filler file. It's the actual RUU in it that is modified to perform the wipe.
So, let's try this again.
1. Get into the bootloader by holding voldown while turning the device on.
2. Plug it in to a USB port on your PC.
3. Once the text at the bottom of the screen changes from SERIAL to USB, begin running the task29 RUU.
4. Once the progress bar gets to 99% on the task29 flash, hold the voldown button again and await the restart.
5. Once it restarts into the bootloader and the text changes again, begin flashing the latest Sprint ROM.
6. Allow the ROM to boot up all the way and settle down, then give it one soft reset.
7. When it comes back again, go ahead and test it out to see if your problems persist.
8. Report back here with the results, and we'll move on from this step.
Task 29 doesnt seem to working because it reboots back to the last rom. Everything is still there. I really don't think that any of the hardware buttons work outside of working in the OS and at startup. IE volumn works when unit is on or when putting unit into bootloader mode but Volumn button does not work when trying to do a hard reset or a Task 29. Power button turns on unit, turns off unit, puts into bootloader mode, starts hardreset. I have loaded a Custom Rom just because maybe with the X button on the bottom and bigger it might be easier. I'm all ears from here on out. Its seems I need to clear ROM or Cmos without button usage. I don't know if that makes any sense to you but like I said I'm all ears on what to do now. Thanks for the little lesson on flashing without Activesync. Feeling kinda stupid about that one. Thanks for the help so far.
Hootyhoo said:
Task 29 doesnt seem to working because it reboots back to the last rom. Everything is still there. I really don't think that any of the hardware buttons work outside of working in the OS and at startup. IE volumn works when unit is on or when putting unit into bootloader mode but Volumn button does not work when trying to do a hard reset or a Task 29. Power button turns on unit, turns off unit, puts into bootloader mode, starts hardreset. I have loaded a Custom Rom just because maybe with the X button on the bottom and bigger it might be easier. I'm all ears from here on out. Its seems I need to clear ROM or Cmos without button usage. I don't know if that makes any sense to you but like I said I'm all ears on what to do now. Thanks for the little lesson on flashing without Activesync. Feeling kinda stupid about that one. Thanks for the help so far.
Click to expand...
Click to collapse
I don't know where you got your task29 utility from, but you cannot run it from SD. It HAS to be used with the RUU that came with it. It is the modified RUU that runs the task29 function. Just to eliminate the confusion, I'm uploading a modified RUU to this post that is very simple to use. Extract it from the archive and follow these instructions.
1. Connect the device (in bootloader) to your PC and wait for USB to show in the bootloader.
2. Run the RhodiumWAdvancedRUU.exe
3. Select the third radio button that says "Perform task29 only."
4. Uncheck the box that says "Restart utility when task29 completed."
5. Hit Next and keep going through it until it flashes.
6. Once the progress bar gets to 99%, hold your voldown button and wait for the reboot.
7. Once you are back into the bootloader, wait for USB to show up on the screen again and then flash the stock ROM.
8. Once the flash is complete, allow it to boot once and settle, then soft reset.
9. Once it restarts, test the problems again.
10. If the problems persist, we can move on from here.
Note: If you want to make sure that the task29 utility worked, feel free to try and boot it after performing the task29 and see how far it gets. If it gets stuck at the bootscreen, then you know it worked. Simply pull the battery, or hit the reset button, and power it back on while holding voldown to return to the bootloader and continue with step 7.
I cannot find the uploaded file that you sent, but also I am not trying to run the Task 29 file from SD card. I'm trying from the comp but like I said, when in any mode other than Windows, I really believe none of the buttons work. Volumn down at 99%. Volumn up on a hardreset. The buttons work to get me into the various mode either from Windows or at startup, but once into the special modes I think I don't get any buttons. That and the fact that the only thing the endkey button does in turn phone on and off but doesnt end anything is peculiar to a person like me. Anyways I didn't get your Task 29 file yet.
Thanks again
Hootyhoo said:
I cannot find the uploaded file that you sent, but also I am not trying to run the Task 29 file from SD card. I'm trying from the comp but like I said, when in any mode other than Windows, I really believe none of the buttons work. Volumn down at 99%. Volumn up on a hardreset. The buttons work to get me into the various mode either from Windows or at startup, but once into the special modes I think I don't get any buttons. That and the fact that the only thing the endkey button does in turn phone on and off but doesnt end anything is peculiar to a person like me. Anyways I didn't get your Task 29 file yet.
Thanks again
Click to expand...
Click to collapse
That's because I forgot to upload it. Sorry. here it is.
I know you feel that way, but there are a few things we can try. We just need to go step by step to rule things out. Please trust me on this. I'm trying to keep from saying that your phone is having hardware troubles, because I think it is fixable as it is now. We just have a certain order to attack it from.
I do appreciate the help I have always gotten from this site and thank you. The worries that I have are actually getting any buttons to work when doing any work on the phone outside of the windows format. I noticed that at 99% I am to tap the vol. dw button and I don't think thats gonna work. From my desktop computer exsperience that I have I know there is actually 3 modes happening that work in conjunction with one another. CMOS MSDOS and Windows. I don't think its a windows issure and I don't know what else there is in these phones that work, but I will try this program and thank you again. I will let you know where I at with it in a few.
Hootyhoo said:
I do appreciate the help I have always gotten from this site and thank you. The worries that I have are actually getting any buttons to work when doing any work on the phone outside of the windows format. I noticed that at 99% I am to tap the vol. dw button and I don't think thats gonna work. From my desktop computer exsperience that I have I know there is actually 3 modes happening that work in conjunction with one another. CMOS MSDOS and Windows. I don't think its a windows issure and I don't know what else there is in these phones that work, but I will try this program and thank you again. I will let you know where I at with it in a few.
Click to expand...
Click to collapse
Even if holding voldown doesn't work, you will still be able to boot back into the bootloader. task29 will clear the internal memory of everything. There won't be anything to load, so it will hang on the splash screen if it tries to load. Don't worry. We're going to try everything we can before we call it quits. This is a unique problem, but I think it can be fixed. Like I said, we just have to go in order.
Okay. First of all I'm sorry for the void between your last message and now. Its been a wild week so far. Thanks again for the help so far. With that said and done heres were I am at. I tried your Task 29 software and it did seem to be different at visualy. Possible problem is, is that when it rebooted after following your instructions, it did not go to the tri colored screen but to a blueish looking screen with the words Touch Pro 2 across the center. It almost looked like a splash screen, but never went any farther. So I'm not sure if that was acceptable or not as a proper task 29 but I did go ahead and load the stock rom into it and it went find. After the first reboot it started up with Airplane mode on. I shut it off and turned on the phone again. Everything was okay. You can only assign the phone button and nothing else that I know of so I couldn't see what was assigned to the end key so I pushed it. immediately it stuck the phone back into airplane mode again. Push or I should say tap and it took it out of it. I realize that by default the phone set the long press end key to shut the airplane mode on and off, but I am tapping and only tapping as I always have in the pass. Well so I got the idea of trying a different Rom in hopes that something will program the key to not shut the phone function off everytime I accidently tap the end key, I tried a few and Sharkies seems to surfice for the moment. By tapping the end key only brings up the Comm Manager instead of shutting the phone function down. Funny thing is though is that also was Sharkies default for long press. The problem has become with that now is that it has been just popping up by itself over and over. So I started tapping the end key when it popped up and suddenly it seems that it worked until I realized the the end key doesnt seem to be working at all. It clicks but thats it. So what to do now. Good thing at this time is the fact that I dont have to worry anymore about accidentally tapping the end key.Good chance it could be the button it self. I don't know. What ya think?
Hootyhoo said:
Okay. First of all I'm sorry for the void between your last message and now. Its been a wild week so far. Thanks again for the help so far. With that said and done heres were I am at. I tried your Task 29 software and it did seem to be different at visualy. Possible problem is, is that when it rebooted after following your instructions, it did not go to the tri colored screen but to a blueish looking screen with the words Touch Pro 2 across the center. It almost looked like a splash screen, but never went any farther. So I'm not sure if that was acceptable or not as a proper task 29 but I did go ahead and load the stock rom into it and it went find. After the first reboot it started up with Airplane mode on. I shut it off and turned on the phone again. Everything was okay. You can only assign the phone button and nothing else that I know of so I couldn't see what was assigned to the end key so I pushed it. immediately it stuck the phone back into airplane mode again. Push or I should say tap and it took it out of it. I realize that by default the phone set the long press end key to shut the airplane mode on and off, but I am tapping and only tapping as I always have in the pass. Well so I got the idea of trying a different Rom in hopes that something will program the key to not shut the phone function off everytime I accidently tap the end key, I tried a few and Sharkies seems to surfice for the moment. By tapping the end key only brings up the Comm Manager instead of shutting the phone function down. Funny thing is though is that also was Sharkies default for long press. The problem has become with that now is that it has been just popping up by itself over and over. So I started tapping the end key when it popped up and suddenly it seems that it worked until I realized the the end key doesnt seem to be working at all. It clicks but thats it. So what to do now. Good thing at this time is the fact that I dont have to worry anymore about accidentally tapping the end key.Good chance it could be the button it self. I don't know. What ya think?
Click to expand...
Click to collapse
On task29, it removes the entire ROM from the device's internal memory. There was nothing to boot up, so it stopped at the splash screen. That's how task29 works.
Well, this allows us to completely remove the possibility of the software's effect on your problem. What is happening is that the device is recognizing a short press as a long press. Since the button commands are interpreted by the SPL, we've got one last thing to try before declaring hardware fault. We'll need to flash the stock SPL, again to see if that clears it up. To do this, I'd ask that you flash the latest stock ROM to your device. After this, you'll need to go back to the CDMA Hard SPL thread and grab the latest stock SPL. Flash that to your device. Then boot it up and see if the problems persist. If it continues to register short presses as long one, then you have a hardware fault. If this fixes it, then you should be able to flash Hard SPL again and load another ROM with no problem.
Accidental post