heyy i really need you'e help, im trying to fet to the bootloader id the diamond but i always end's up in the rgb screen, so please tell me what to do...
From the wiki:
http://wiki.xda-developers.com/index.php?pagename=Diamond_FlashfIS
I have a similar problem. But mine is looking for movihand.mtg file then it goes to loading screen and it hangs. I wanted to flash the Deepshining 8 lite also.
I have a lot of files in my internal storage do i need to clear them and leave only the DIAMING.nbh thanks
i have spl 1.40 also thanks
Hope I can help!
Hey! First to 'avior.almo' You need to make sure you have flashed HardSPL to your device before trying to flash ANY ROM to your device (cooked, or custom, or otherwise!) If you are unsure of what I mean, or have any trouble, see sticky threads #2 and #4 of 'Diamond ROM development' http://forum.xda-developers.com/forumdisplay.php?f=430 (I use HardSPL Olinex 1.40)
Once you have this all in place, then flashing from the SD card is easy; you simply need to download the ROM you wish to flash, extract it (if it's downloaded as a .zip or .rar file) so you can find an '.nbh' file. The '.nbh' file is the ROM itself, and the file that you wish to flash. Once you have extracted the ROM you wish to flash (if you needed to extract at all. You may have downloaded the .nbh file as it is) then whatever the .nbh file name is, you need to rename the .nbh file to 'DIAMIMG.nbh' (without quotation marks).
Once you have done that, you need to copy it to your device's internal memory. To do this, connect your Diamond via USB, and when asked on your device screen, choose the 'Disk Drive' type of connection. Once complete, you can then navigate to the root of your (SD card) Internal Storage by accessing 'My Computer' through Windows explorer, Your device drive letter may be different depending on how many hard disks/CD drives you have in your system. (Mine is drive E Anyway, access your internal storage drive, whatever letter it may be on your system. It will appear under 'Drives with removable storage'. This is where you need to copy the 'DIAMIMG.nbh' file to. (To rdelsol: No, you don't need to clear your internal storage of any files or folders, as long as you have enough space in your internal storage to paste the ROM (.nbh file) that you wish to flash, in the root directory. E.g. 'E:' drive. It can be in there along with your 'program files' folder, or your 'my pictures' or 'my videos' folders. Flashing shouldn't delete any files or folders you have in your internal storage either. Even after flashing, 'DIAMIMG.nbh' should also still be there! (After flashing, you can delete that file)) And I noticed that in your post, you typed 'DIAMING.nbh' whether that was just a typo or not, I don't know, but it needs to be 'DIAMIMG.nbh', if so, that may be where you're going wrong.
So, now that we have the ROM image file in the root directory of your internal storage, you need to enter your device into bootloader mode, which is achieved by (while the device is on) holding down the 'VolDown' and 'back' (<-) buttons, while pressing the little red reset button (under the battery cover). Keep hold of the voldown and back buttons until your device displays the tri-colour screen. The instructions are then shown on-screen of what to do next (PROVIDING YOU HAVE HARDSPL INSTALLED, see beginning of post). Your device should detect the ROM image file (saved as DIAMIMG.nbh) and prompt you to press the power button to begin the flash. All going well, your device will display a progress bar, that when reaches 100% will say 'Update Success'
Now you need to press the red reset button again. After that, your device should begin setup of the new ROM as if it had just been bought. Alignment of screen, and maybe time and date setup, for example. Good luck with flashing and setup!
I have done many internal flashing, but today I tried again installing a new custom rom. Strange thing is that the bootloader says that it can´t find any image file and then quits to boot loader screen. I´ve tryied renaming the file using caps and without caps, and also with old radio in order to just test the flashing capability of the internal memory. No luck.
The phone did flash the same image from customruu. Now i´m thinking that it has to do with my messing with the internal memory for partitioning an ext2 and running (badly) android.
I realocated the ext2 partition and made the fat32 the whole internal memory. i´m not sure if i need to re-format the memory throught linux...
Any ideas why I can´t seem to run the internal flashing anymore?
Related
i read around for methods on flashing a rom. this is my first time .i did a back up with hpb backup and put hard spl 2 on my phone. from what i read sdcard is the best route to go . my question is do i need to erase everytihng off of my card before doing the rom? or can i leave it all there put the ruu file on there and get started ? maybe i should ask is there a tutorial to how to do the different methods?
a side note how do i know if a rom is friendly to changing the orientation when you slide for the keyboard
Natureboyhcg said:
i read around for methods on flashing a rom. this is my first time .i did a back up with hpb backup and put hard spl 2 on my phone. from what i read sdcard is the best route to go . my question is do i need to erase everytihng off of my card before doing the rom? or can i leave it all there put the ruu file on there and get started ? maybe i should ask is there a tutorial to how to do the different methods?
a side note how do i know if a rom is friendly to changing the orientation when you slide for the keyboard
Click to expand...
Click to collapse
No you don't have to take everything off the card. Make sure your card is 2gig or smaller and not SDHC. Here is a link to the instructions in the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlash
As far as the keyboard orientation you could search in the rom's thread for any reference to it or just flash the rom and see for yourself.
KK13 said:
No you don't have to take everything off the card. Make sure your card is 2gig or smaller and not SDHC. Here is a link to the instructions in the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlash
As far as the keyboard orientation you could search in the rom's thread for any reference to it or just flash the rom and see for yourself.
Click to expand...
Click to collapse
im confused, does the card need to be 2gb or smaller, not sdhc, to properly do hardspl or general. cause ive read the phone only supports 2gb or smaller microsd. but i have also seen the 16gb or 32gb thread, ive seen others saying about using larger than 2gb cards in their phones. im awaiting the delivery of my phone currently and i have a 4gb microsd i use in my htc excalibur i was planning on using. so im majorly confused as to if im going to be able to use it or not, or if i just need a 2gb to do the intial hardspl then ill be fine w/ my 4gb once i go to a cooked rom.
would greatly appreciate some clarity on this all from someone.
WM05 and bootloader only support 2Gb or less though there is an sdhc patch for WM05.
WM06 had the patch to support SDHC cards from 4Gb up to 32Gb. WM6.1 and WM6.5 are also SDHC compliant.
You need a 2Gb or less sd card to flash an OS or different SPL as the bootloader only supports 2Gb or less. Its not upgradeable.
Now that everythings clear as mud,
Cheers...
You could also pick up a 1 gig (or even a 512meg) card on the cheap to do your flashing, and use the 4 gig for your everyday storage in the phone. Then have the best of both worlds!
psylink said:
im confused, does the card need to be 2gb or smaller, not sdhc, to properly do hardspl or general. cause ive read the phone only supports 2gb or smaller microsd. but i have also seen the 16gb or 32gb thread, ive seen others saying about using larger than 2gb cards in their phones. im awaiting the delivery of my phone currently and i have a 4gb microsd i use in my htc excalibur i was planning on using. so im majorly confused as to if im going to be able to use it or not, or if i just need a 2gb to do the intial hardspl then ill be fine w/ my 4gb once i go to a cooked rom.
would greatly appreciate some clarity on this all from someone.
Click to expand...
Click to collapse
You need a smaller than 2gig card for flashing. Everything else you can use your 4 gig card. (As Ultramag69 and Boog321 say) The original question was to do with flashing hardspl or roms only.
KK13 said:
You need a smaller than 2gig card for flashing. Everything else you can use your 4 gig card. (As Ultramag69 and Boog321 say) The original question was to do with flashing hardspl or roms only.
Click to expand...
Click to collapse
HardSPL only needed to install once, after that you can install whatever ROMs you like many times.
True, but if you use the sd card method to install roms you will still need a 2Gb or less sd card...
ultramag69 said:
True, but if you use the sd card method to install roms you will still need a 2Gb or less sd card...
Click to expand...
Click to collapse
Hi Ultramag
I have a problem installing with sdcard.
Have followed the Wiki, have discussed with you previously, Boog and anagarika still no solution. I have elaborated step by step what I did in separate thread.
Do you mind have a look and advise some?
http://forum.xda-developers.com/showthread.php?t=316726&page=34
StefanHou said:
Hi Ultramag
I have a problem installing with sdcard.
Have followed the Wiki, have discussed with you previously, Boog and anagarika still no solution. I have elaborated step by step what I did in separate thread.
Do you mind have a look and advise some?
http://forum.xda-developers.com/showthread.php?t=316726&page=34
Click to expand...
Click to collapse
Did you try formating the SD card on a desktop (or laptop) computer and not phone with Memaid?? Maybe that has something to do with it. Is it a 2gig card or less than 2 gig??
As KK13 said, try a pc to format the card as the steps are right.
Double check that the .nbh is named hermimg.nbh as I know of at least 2 people who named it herming.nbh, small mistake but a critical one.
Remove and insert the sd card then reboot to tri-colour screen. Might do something.
But I strongly recommend using the PC to format the sd card FAT32.
Cheers...
ultramag69 said:
As KK13 said, try a pc to format the card as the steps are right.
Double check that the .nbh is named hermimg.nbh as I know of at least 2 people who named it herming.nbh, small mistake but a critical one.
Remove and insert the sd card then reboot to tri-colour screen. Might do something.
But I strongly recommend using the PC to format the sd card FAT32.
Cheers...
Click to expand...
Click to collapse
Onya dude .. you have a better way with words !!
ultramag69 said:
As KK13 said, try a pc to format the card as the steps are right.
Double check that the .nbh is named hermimg.nbh as I know of at least 2 people who named it herming.nbh, small mistake but a critical one.
Remove and insert the sd card then reboot to tri-colour screen. Might do something.
But I strongly recommend using the PC to format the sd card FAT32.
Cheers...
Click to expand...
Click to collapse
OK, will find SDconverter and try the suggestion, thx KK and Ultramag
*Newbie* Custom ROM Flashing Guide
Just follow the steps start from 1. Don't skip step unless it is an optional step.
PC Requirement: Windows XP, ActiveSync [Don't try to flash with Vista if you are new], 7zip Installed (Google it)
Connect your device to your computer and make sure the ActiveSync icon appeared on your phone before proceeding. 50% or above bettery is a must. Your phone won't charge when flashing.
1. HardSPL (A Big Big Must)
I asume you are using the original ROM from manufacture as HardSPL won't work with custom ROM.
Download HardSPL V7 from here. Unzip the whole things. Execute the "RUUWrapper" thing and select "Force Using SSPL". Check all the boxes in all the steps and continue with updates. Look at your phone and press "Yes" to everything that prompted. Then your phone will restart in Tri-Color mode [a.k.a bootloader] and start flashing HardSPL.
In this case if any errors appear on your computer screen before the update progress start, soft reset your phone, let it boot into Windows and start RUUWrapper again.
If error appear during flashing progress, then you might in deep hell. Try not to worry. Manually put your device into bootloader (Hold On/Off Btn + Left OK Btn, then push the soft-reset btn). Then start the RUUWrapper again.
End of the step you should see 'HardSPL 2.10Olipro' in bootloader mode.
2. Radio Flashing *Optional*
You can choose not to flash your Radio Stack if you satisfy with the existing. Additional, Radio Stack flashing is the main cause of device bricking (the death of your device)
Choose and download your Radio ROM here. Do some research about the Radio ROM that fits you and your country. Recommended the latest 1.56.70.11. Unpack everything and you will see something similar to HardSPL (RUUWrapper). Don't run RUUWrapper this time.
Let's do the safe way. Format your MicroSD card into FAT32 (Kill yourself if you don't know). Then copy the RUU_signed.nbh into your MicroSD. Then rename RUU_signed.nbh to hermimg.nbh. Put your MicroSD into you phone.
Manually put your phone into bootloader mode. Then a different screen with grey background should appear shortly. Press On/Off btn to start flashing. After the process done (it will tell you when it is done, don't try to judge yourself if you feels that 50% is done), soft-reset your phone.
During flashing, put your phone aside and enjoy your coffee. Don't touch it before it ends as this is dangerous. Don't ever fail radio flashing. Careful, careful and careful.
End of this step, you should see R 1.56.70.11 during Windows Boot.
3. Custom ROM Flashing
First, download Dopod 838 Stripped ROM. Then unpack it. Delete your previous hermimg.nbh in MicroSD which you use to flash Radio Stack. Then copy RUU_signed.nbh from Dopod 838 Stripped ROM to your MicroSD and rename it to hermimg.nbh. Put your device into booloader and start flashing like how you flash you radio rom. After it done, give your device a Hard-Reset (Hold Left + Right softkey and press Reset. Slide you keyboard then press R and SPACE). This official ROM from Dopod is very important which need to be flashed before you flash your custom ROM.
Then the last step is get your custom ROM loaded. Download custom ROM from this forum (Recommended from TAI_sw or JoshKoss).
Then simply follow the steps in Dopod 838 Stripped ROM Flashing.
(Then copy RUU_signed.nbh from Custom ROM to your MicroSD and rename it to hermimg.nbh. Put your device into booloader and start flashing like how you flash you radio rom. After it done, give your device a Hard-Reset (Hold Left + Right softkey and press Reset. Slide you keyboard then press R and SPACE).)
Yes. I have grammar mistakes. Sorry!
That's your ROM and don't expect every ROM is stable. You will see some bugs in Custom ROM. Post your bugs at their own thread.
Anything just PM me.
Thanks
-Ziv-
zivkong said:
*Newbie* Custom ROM Flashing Guide
Just follow the steps start from 1. Don't skip step unless it is an optional step.
PC Requirement: Windows XP, ActiveSync [Don't try to flash with Vista if you are new], 7zip Installed (Google it)
Connect your device to your computer and make sure the ActiveSync icon appeared on your phone before proceeding. 50% or above bettery is a must. Your phone won't charge when flashing.
1. HardSPL (A Big Big Must)
I asume you are using the original ROM from manufacture as HardSPL won't work with custom ROM.
Download HardSPL V7 from here. Unzip the whole things. Execute the "RUUWrapper" thing and select "Force Using SSPL". Check all the boxes in all the steps and continue with updates. Look at your phone and press "Yes" to everything that prompted. Then your phone will restart in Tri-Color mode [a.k.a bootloader] and start flashing HardSPL.
In this case if any errors appear on your computer screen before the update progress start, soft reset your phone, let it boot into Windows and start RUUWrapper again.
If error appear during flashing progress, then you might in deep hell. Try not to worry. Manually put your device into bootloader (Hold On/Off Btn + Left OK Btn, then push the soft-reset btn). Then start the RUUWrapper again.
End of the step you should see 'HardSPL 2.10Olipro' in bootloader mode.
2. Radio Flashing *Optional*
You can choose not to flash your Radio Stack if you satisfy with the existing. Additional, Radio Stack flashing is the main cause of device bricking (the death of your device)
Choose and download your Radio ROM here. Do some research about the Radio ROM that fits you and your country. Recommended the latest 1.56.70.11. Unpack everything and you will see something similar to HardSPL (RUUWrapper). Don't run RUUWrapper this time.
Let's do the safe way. Format your MicroSD card into FAT32 (Kill yourself if you don't know). Then copy the RUU_signed.nbh into your MicroSD. Then rename RUU_signed.nbh to hermimg.nbh. Put your MicroSD into you phone.
Manually put your phone into bootloader mode. Then a different screen with grey background should appear shortly. Press On/Off btn to start flashing. After the process done (it will tell you when it is done, don't try to judge yourself if you feels that 50% is done), soft-reset your phone.
During flashing, put your phone aside and enjoy your coffee. Don't touch it before it ends as this is dangerous. Don't ever fail radio flashing. Careful, careful and careful.
End of this step, you should see R 1.56.70.11 during Windows Boot.
3. Custom ROM Flashing
First, download Dopod 838 Stripped ROM. Then unpack it. Delete your previous hermimg.nbh in MicroSD which you use to flash Radio Stack. Then copy RUU_signed.nbh from Dopod 838 Stripped ROM to your MicroSD and rename it to hermimg.nbh. Put your device into booloader and start flashing like how you flash you radio rom. After it done, give your device a Hard-Reset (Hold Left + Right softkey and press Reset. Slide you keyboard then press R and SPACE). This official ROM from Dopod is very important which need to be flashed before you flash your custom ROM.
Then the last step is get your custom ROM loaded. Download custom ROM from this forum (Recommended from TAI_sw or JoshKoss).
Then simply follow the steps in Dopod 838 Stripped ROM Flashing.
(Then copy RUU_signed.nbh from Custom ROM to your MicroSD and rename it to hermimg.nbh. Put your device into booloader and start flashing like how you flash you radio rom. After it done, give your device a Hard-Reset (Hold Left + Right softkey and press Reset. Slide you keyboard then press R and SPACE).)
Yes. I have grammar mistakes. Sorry!
That's your ROM and don't expect every ROM is stable. You will see some bugs in Custom ROM. Post your bugs at their own thread.
Anything just PM me.
Thanks
-Ziv-
Click to expand...
Click to collapse
Hi Ziv
I have flashed over twenty or more cooked ROM, and they are successfully done through Active Sync. As you see in my signature, My IPL is 1.04 and my SPL is 2.10 Olipro.
I have also followed Ultramag and KK suggestion to format the SDCard using PC. And still stuck in bootloader (3 colors) and one more: it states 'Serial' in the bottom color (white).
I also bought the new 1GB SDCard, but the problem persit.
So, is there any other suggestion to try?
StefanHou said:
Hi Ziv
I have flashed over twenty or more cooked ROM, and they are successfully done through Active Sync. As you see in my signature, My IPL is 1.04 and my SPL is 2.10 Olipro.
I have also followed Ultramag and KK suggestion to format the SDCard using PC. And still stuck in bootloader (3 colors) and one more: it states 'Serial' in the bottom color (white).
I also bought the new 1GB SDCard, but the problem persit.
So, is there any other suggestion to try?
Click to expand...
Click to collapse
Ultramag, KK13, Boog & Zocster
Have tested using SD Converter and formatted it with PC, still no use. In the boot loader screen, I stucked with 'Serial' in the white bar. Is this meaning something to you? Any other work around?
Man, I don't have a clue. The only issue I ever encountered was thinking my card was formatted fat32 when it wasn't.
I think this is now beyond me.
StefanHou said:
Ultramag, KK13, Boog & Zocster
Have tested using SD Converter and formatted it with PC, still no use. In the boot loader screen, I stucked with 'Serial' in the white bar. Is this meaning something to you? Any other work around?
Click to expand...
Click to collapse
Well now .. you've got me too. I have only had "serial" showing in the boot loader once and it was because I had the wrong sd card in with no HERMIMG file. Once I put the right one in with the file and reset the device it was ok. All I would suggest is to do a Hard reset and follow all the steps again one by one, triple checking everything. Maybe write everything you do down and post it back here.
Also check your spelling of hermimg.nbh as a simple error will screw up everything...
Also put sd card in then reset to bootloader, hold in all the buttons - ok, power and reset with stylus, until the bootloader comes up.
Cheers...
KK13 said:
Well now .. you've got me too. I have only had "serial" showing in the boot loader once and it was because I had the wrong sd card in with no HERMIMG file. Once I put the right one in with the file and reset the device it was ok. All I would suggest is to do a Hard reset and follow all the steps again one by one, triple checking everything. Maybe write everything you do down and post it back here.
Click to expand...
Click to collapse
KK13, Boog and Ultramag
OK this is what I did last night:
1. Flashing to the shipped AT&T Stripped ROM
2. Having it reflashed with the HardSPL V7 (to ensure the file is non corrupted, I re-downloaded it from some links in some thread and check the file size, they are all the same )
3. Reformating my SD Card with PC for FAT32;
4. Copy the nbh file and rename it with HERMIMG.nbh (recheck three times and I think I get it right. btw, is there any different to write it in capital? );
5. Press OK and Power, then stick the reset button.
6. Go to the boot loader (with 'Serial' on ht white screen)
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
aikeru said:
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
Click to expand...
Click to collapse
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
deekjx said:
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
Click to expand...
Click to collapse
Did anyone try this solution?
Since the bootloader is still there all you do if not able to flash via async when in android is flash via bootloader
Moved to general as not ROM Dev.
Thanks for the information, guys!! I will have to try it out over this weekend and see how it goes...
I can confirm that flashing via bootloader works fine, also flashing from SD works as well, in fact I keep a 128MB sd with a WM kaisimg.nbh on it handy just in case I need to flash a good WM rom for some reason.
Is there an Android OS with everything working on the Kaiser?
Dukenukemx said:
Is there an Android OS with everything working on the Kaiser?
Click to expand...
Click to collapse
You can see in different post of android rom what works and what doesn't works.
actually, Bluetooth and camera never works for in android 2.x build and some other apps doesn't works
I've been running Android for a few weeks now from this thread:
http://forum.xda-developers.com/showthread.php?t=614382
I've found everything to work with the exception of Bluetooth, video camera (normal camera works fine), and the barcode scanner. Also, my battery life is cut in half, but I have an extended life battery so I get a day or two out of it.
I prefer this method as you can just boot Android at will and can soft reset to go back to WinMo.
Just to let everyone know I did flash WM back just fine since I have HardSPL 3.56 and used the stylus to press the reset + camera button at the same time to get to the tri-color screen.
From there I flashed from USB without any problems.
Thanks again for all the help!
I am having problems reverting back to WM after attempting to install android to NAND. Something happened where the only way I was able to get to the android installer would be if I had the KAISDIAG.nbh file on the SD card so it would get past the tri color hard spl screen . Well as a result, I can't get into boot loader. It shows that screen for a split second, then if I do camera + power and then reset. Then I have to pull the battery. Can someone help me? It seems like it will only go into the Android bootloader, which obviously won't allow it to install a WM rom. SD flashes are my only choice because the usb port is pretty messed up. Any help would be greatly appreciated. Thanks.
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
zenity said:
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
Click to expand...
Click to collapse
Thanks, but unfortunately this still did not work. Have any other suggestions? I think the only way will it even do anything is if I have the KAISDIAG.nbh file on the card. It recognizes that, but then goes straight to linux. IDK what else to do. Could you be a little more clear on the procedure for getting into the bootloader? Thanks.
Ok please follow these steps carefully.
1. Format the SD card, make sure you are formatting it as FAT32, not FAT.
2. Download a Winmo Rom from somewhere handy.
3. Extract the Rom to a handy folder, find the RUU_Signed.nbh file, rename that to KAISimg.nbh
4. Copy the KAISimg.nbh file to the SD card. You should only have one file on the SD card, no folders just the NBH file.
5. pull the battery from the phone, wait at least 5 minutes.
6. Replace the battery. Press Power button, and hold down camera button, until the tri color screen appears.
7. The screen should now change to a white one, and when it's checked the nbh it will ask you to press power key again. do that.
8. Now it should flash the rom, this should take a while, 5-10 minutes, once it's finished you should get a message of success.
9. Now pull the battery again, wait 5 minutes, replace the battery, and power on, you should now boot into Winmo.
Hopefully this should solve your problems, if not then let me know which setp failed and we can work on that stage.
Finally, don't panic, take it slow, it'll all work out
Thanks, but the problem starts at number 6. I am supposed to press the power button, release it, and hold the camera button till it gets to the white screen, right? It's still stuck at the splash screen. I tried holding both and that didn't work either. Anything else I can try? I hope i'm not screwed?
If I put the battery in, boot it up, then push the camera and insert the stylus into the reset hole, it gets to the tricolor screen, then for about 0.5sec it flashes the white screen with a message saying "No image File." I know for sure the .nbh file is there.
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
zenity said:
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
Click to expand...
Click to collapse
Unfortunately, as much as I wish it was, it is not the problem. I'm on a Mac, but booted windows 7 to be make sure it was formatted to FAT 32, which it was. Is there some way I can fix permissions? Every time it runs, I keep getting the error saying that it is in read only mode. I obviously need to get it into writing mode. I don't think the fix permissions option on the installer did anything either.
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Tilt Fanatic said:
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Click to expand...
Click to collapse
Alright, I'll try and sum up your experiences. Tell us if we're missing anything;
You have the following symptoms
Linux Android-installer works
Tri-color bootloader semi-works
You cannot use the USB
You cannot install polymod's Eclair build
Now, you have mentioned a couple of things you have tried, such as
Replacing the Linux NBH with another version
Fixing permissions on the SD-card
Fixing permissions through the Android-installer
Flashing a WinMO ROM through SD card
You did mention getting other behaviours when you switched to another NBH, such as "KAISDIAG.nbh" not being required.
Now, this is a long shot coming from me, as I have had no troubles with flashing, and the fact that I can use my USB, but since your phone is pretty messed up I guess it can't hurt as a suggestion;
You can flash to other NBH's I take it, as you mentioned you did a downgrade. What I'm a bit curious about is whether you did try to flash to a WinMO rom when you had downgraded to your current NBH.
Also, you said the previous NBH required you to have "KAISDIAG.nbh" on the card to even get working. Did you try and rename a WinMO-ROM's NBH to "KAISDIAG.nbh" and flash that? Might be that the flasher is really constrictive with the file names.
EDIT: Oh, and what about trying to run other Eclair builds? Just to see if you can nail it down to this being a problem of the builds or something more bound to the actual hardware/SPL/NBH's.
Hi I am using hardspl 3.34
I decided to put android on my kaiser as I love it on my desire..
I flashed the latest android kernel from kallt_kaffe, when booted error messages came up about not being able to mount various locations..and a final one "unable to open persistent property directory"
I tried pressing the D pad to load an Android nbh from and boot and nothing.
I have since tried to reflash both winmo and android kernel images from the sd card and through USB but nothing flashes.
If I try with the sd card, naming the image KAISimg.nbh all I get is a white screen with loading on it..nothing more.
when I try via usb it gets as far as trying to flash the rom, then comes up with a communication errror.
anyone any ideas what has happened and how to fix it.
Regards
Robbie
You've downloaded and flashed the kernel (which allows you to run Android), but have you downloaded an Android build yet?
It sounds like you're missing the androidinstall.tar file in the andboot folder of your SD card.
Find a build in this forum, download the build (should be about 80/90mb or so when zipped) and then place the file in /andboot/
If you've already done this, apologies if that was patronising in any way!
The Kaiser is somewhat picky when it comes to SD cards, it may not read KAISIMG.nbh even if everything is fine. My 1GB Kingston card, for example, is useless when it comes to flashing this way, I had to buy a new 4GB card so I could sort out a rather useless Android build.
Thanks NatAvery
I have the andboot folder with the tar file in, but as I get errors from the android kernel i think that is why it doesn't read it.
My main concern is my inability to flash anything..I have tried a different sd card as you suggested and I still have the same problem, it comes up as loading the KAISimg.nbh but goes no further.
Robbie
Hi Vampires,
Did your issue resolve?.........since even i have a similar issue. I flashed HardSPL first & then flashed a rom from then whenever i switch on the phone it comes to this screen as if loading and is stuck with the error you mentioned ' unable to open persistent property directory'
And this happen to me just like it happen to me .......in the pursuit of having android on the phone.
I'm not able to flash any other rom's just stuck on this screen.
I have the same problem. I also use hardspl 3.34
I flashed the kernel installed the built, bu i didn´t pick the right display setting..
everytime I try to reflash it only says loading.. (left it for about 2 hours)
any ideas?
still looking for a solution, please anyone with usefull info help ..
i had similar problems before, my system is:
HTC tytn ii (kaiser 130)
Hard SPL 3.34, radio 1.70.19.09
DZO's kernel and froyo 15-07 (latest thas it), NAND flashed
4gb SD card
(109mb internal phone memory after 1st boot)
Haret Install (SD card, run side by side with WinMo)
- dload kallt_kaffe froyo, extract and put andboot in SD card, root, not subfolder
- rename default-kaiser.txt into default.txt
- edit default.txt change panel-type into 2 (panel 1 got some issue with res)
- run haret.exe
- don't press d-pad (center) just yet, wait until message 'press d-pad/volume to ..' then immediately press and hold d-pad until you're in install menu.
- select install, ok
- next, select fix permission (optional, but it fix some prob)
- select quit
- let it boot, no need to press d-pad anymore.
- you may get "unable to open persistent property directory", but no worries, restart phone, run haret again, if still the same, reinstall, sometimes twice install should fix it. (don't ask me why)
NAND flash
- dload DZO's kernel and OS build file.
- use Loser's NBH editor to change panel type to 2, and keyboard type. it will then save as KAISIMG.nbh
- put KAISIMG.nbh into SD card, root.
- make folder andboot inside SD card at root, and copy dzo's android build, rename it to androidinstall.tgz (tar/tgz)
- press and hold power btn + camera btn, reset with stylus
- press power again to flash kernel, then reset after complete
- now it will try to boot android, immediately press d-pad when you see 'press d-pad/volume..' and install (sys on NAND, data on NAND), next step same as haret above.
- you're now officially android.
note: additionally you can also try 'sys on NAND' + 'data on SD Card', --> use this EXT2 partitionto partition your sd card
side note:>
zImage = is the haret version of the KAISIMG.nbh file, it's the kernel.
androidinstall.tar/tgz = the android OS files
hope this helps.
Attn: if you're experiencing battery stucked at 15% or something, go into boot menu (d-pad), backup data, flash winmo rom, charge to 100%, then reflash+reinstall android, restore data. that should fix it.
Hi
I have rooted my phone with unrevoked, s-off'ed with alpha rev 1.8, partitioned 1gb of my 4 gb card to ext 3 and installed Gingerbread F1 V3 Ap2SD ENG.
On first load of the rom i can see that my SD card FAT 32 storage has been reduced but the only other memory internal memory which was at 147mb when i first booted the rom.
All apps are installing to the internal memory by default with only the option of moving to the SD FAT 32 partition. and there is no option to move to the sd ext3 part as there is no option - so I have lost 1gb off my sd card.
What have i done wrong?
on a 2nd note i appear to have a call delay when answering the phone my radio version is 32.49.00.32U_5.11.05.27 - do i need to update this ? will it solve the problem ? my carrier is vodafone UK.
appreciate the help
ararararar... Sorry had to do something.
This has been explained SO many times by me included. The way a2sd works is by symlinking the folder containing the apps(/data/app) to you ext-partition.
You cannot see this partition listed in the system info, as the partition is not supposed to be there. The system have no way of knowing that you are using an ext-partition, as it just installs apps to /data/app, however as it's symlinked to ext, they are actually being placed in sd-ext/app.
This means that you will only see you internal memory, but it still works. Your apps will just take up less space on internal, as the apk file is placed on the ext-partition. They will still take up some space for data and dalvik cache.
edit: bonus info. Install "quick system info" or "titanium backup" from the market to see the size of your ext-partition in those apps.
edit2: and if i did not make my self clear. The partition-size info in the system settings is not supposed to be a partition manager. It's written to be userfriendly, and it only provides the regular user with the partitions they should care about(/data and /sd-card). If you want a detailed view of all your partition(and there is more than a few) go get root explorer. It'll let you play around with all the partitions mounted.(you won't have access to recovery, bootloader and so on from here)
Ok thanks. I'm new to this and there's so much info to take in
With regards to the radio is there a simple way of flashing as I have alpha rev installed the method via recovery wont work. I see alot of people talking about doing this through a terminal but I could not find a comprehensive guide for this like the xda root guide. Thanks.
Darren
Sent from my HTC Desire using XDA App
Well i take it that your cache partition is too small(this is why people using alpharev cm hboot cannot use recovery for this). In that case you have already flashed another hboot(using "fastboot flash hboot hboot.img") if you haven't done this, you cache-partition should not be too small, and the recovery method should be able to do this just fine. If you have done this, use the same command to flash the radio eg "fastboot flash radio radio.img"
Either way it is very unlikely to fix your call delay(read: it won't fix your problem, as it's got nothing to do with the radio). It's a problem caused by some incompatibility between the htc libs and GB. It's quite common on GB roms apparently. Wait for HTC to release the real GB update, and we might very well be able to solve this problem.
dazzr123 said:
Ok thanks. I'm new to this and there's so much info to take in
With regards to the radio is there a simple way of flashing as I have alpha rev installed the method via recovery wont work. I see alot of people talking about doing this through a terminal but I could not find a comprehensive guide for this like the xda root guide. Thanks.
Darren
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Install android sdk:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Copy the downloaded radio.img to e.g. partition C: on your computer (if you downloaded a zip, extract the radio.img from there). Check the md5sum!!!
Boot your into fastboot mode (start it with pressed back and power button) and connect your phone to your computer.
Now open command prompt on your computer and type
Code:
fastboot devices
It should list your device now. If it does, type
Code:
fastboot flash radio C:\radio.img
(in case your radio.img was copied to C: ).
Now, observe the computer and be patient TOUCH NOTHING!!
The process will copy the image to your phone, write the image to the radio partition and perform some magic be patient TOUCH NOTHING!!
Watch the little indicator at the top of your phone screen.
Once the process appears to finish (it may not say complete) wait a further FULL 60 SECONDS and be patient TOUCH NOTHING!!
Then, and only then, reboot your phone.
Click to expand...
Click to collapse
A nice guide about adb/fastboot can you find here:
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
Flashing radio is a risky thing. Because if there something is wrong, your phone won't be more than a paperweight.
I just received my replacement G2 (after two decades of owning a cell phone, I finally joined the ranks of those spilling drinks on them) and am in the process of rooting it. I'm using this guide from the Wiki and everything has been working however I'm stuck at the downgrade process. After I run 'adb reboot bootloader', I press the power button as instructed but absolutely nothing happens.
I've checked and double checked the MD5 as well as that the file is named PC10IMG.zip and not PC10IMG.zip.zip but every time I follow the steps, still nothing happens.
when you boot into bootloader it should automatically search for a couple different files on sd card, do you see the text scrolling?
if so it is either not on the root of sdcard (not in any folders)
or it is not named correctly (windows hides extensions sometimes, but it looks like you know this)
or sd isnt mounting (bad tray or whatever)
or sd isnt partitioned to fat32
only reasons why it wouldnt find it
but either way fastboot is safer so why not just use this method? it should be in the guide you linked