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.
Hoping someone can help me out - I have a rooted Incredible, and went to use ROM manager to flash back to a backup made 2 months ago. Also flashed an older version of CWM recovery (because for whatever reason the newer releases never worked). The phone went to boot into recovery and do it's thing, but then the version of CWM I flashed didn't allow the phone into recovery, and now I'm stuck at the boot screen and a battery pull didn't work. I can't even power down/reboot the device (unless it's plugged in), it just goes black for a second, then HTC Incredible screen shows for 2 sec, then back to boot screen. Any ideas? I tried putting an older version of CWM onto the root of the SD, but it's not recognizing it as an available "update" on the Bootloader screen.
Thanks for any help!
You would need a PB31IMG version of CWM. You can get it here http://dougpiston.com/?page_id=85. Put it on the root of your SD card the hold the volume down+power button, and wait for it to load it, except the update and that should do the trick.
Would I need to erase the ROM manager file from the SD card so that it picks this one up? It's not picking up the .zip and prompting me to install...
I don't think you would need to do that. Make sure that the file is named correctly PB31IMG. Ive had the issue before where I named it PB31IMG.zip and I did not have to put the.zip after it otherwise it won't be recognized. Maybe that's the issue you are having...
You sir are a genius! That worked perfectly. Thanks!
Glad to help! I think the reason your wife's SD card doesn't work either, is because it is not in FAT32 format.
I've tried to search around the fourms but every seems to have rooted their phone. I never have, but it's been acting laggy and shutting itself off from time to time, I've had my Incredible for about a year and a half and just wanted to wipe it in hopes that it wouldnt shut off randomly and run faster but when i go into settings and into SD & Phone storage and do Factory data reset I end up getting stuck on a screen with a phone and a red triangle with an exclamation in the middle.
When that happens I can hold down the power button and the up volume button and try and restore from there but it always just loads my phone back up how it was, nothing gets wiped and it also puts it into auto roaming so I have to call and reprogram my phone with verizon.
Any ideas?
thisistay said:
I've tried to search around the fourms but every seems to have rooted their phone. I never have, but it's been acting laggy and shutting itself off from time to time, I've had my Incredible for about a year and a half and just wanted to wipe it in hopes that it wouldnt shut off randomly and run faster but when i go into settings and into SD & Phone storage and do Factory data reset I end up getting stuck on a screen with a phone and a red triangle with an exclamation in the middle.
When that happens I can hold down the power button and the up volume button and try and restore from there but it always just loads my phone back up how it was, nothing gets wiped and it also puts it into auto roaming so I have to call and reprogram my phone with verizon.
Any ideas?
Click to expand...
Click to collapse
It sounds like either you have a custom recovery installed (rooted), or your stock recovery may be corrupt. First i would try to do a factory reset from hboot. To do that power off the phone pull the battery and reimsert. Then hold vol down and power till a white screen pops up. Then use the vol keys to navigate to factory reset and the power button to select. If that dosent work i would do an ruu. To do that download this file http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip and place it on your sdcard in no folders, do not rename. Pull battery, replace, vol down and pwr to enter hboot. Hboot will automaticly find the file and prompt you to press vol up to update. Do so and then when propmted again press vol up to reboot. Once rebooted your phone should be like new.
Tried it in hboot and it seems to of only wiped half my stuff. Apps and everything are still there but it's almost as if they reset and are taking me through tutorials again and all my setting are back to default.
I'm downloading the ZIP file ya gave me now, i'll let ya know if that works. Thanks for your help!
Okay, took my SD card out of my phone to make sure i placed that file on it and not somewhere else, i did NOT unzip the file onto the SD card either, just simply copied and pasted the ZIP file onto the SD card, it's not in a folder either. Put the Sd card back in, turned phone off and entered hboot, hboot isn't prompting me to update though... any ideas? :\
thisistay said:
Okay, took my SD card out of my phone to make sure i placed that file on it and not somewhere else, i did NOT unzip the file onto the SD card either, just simply copied and pasted the ZIP file onto the SD card, it's not in a folder either. Put the Sd card back in, turned phone off and entered hboot, hboot isn't prompting me to update though... any ideas? :\
Click to expand...
Click to collapse
Try backing up the sdcard to your pc. Then with the pc format the card fat32, and then put the files back on. If that still dosent work, you could do an ruu.exe with your pc. Install htc sync http://dinc.does-it.net/HTC-Sync/3.0.5606/setup_3.0.5606.exe, then download and run this file http://dinc.does-it.net/Stock_Image...0_Incredible_C_hboot_1.02.0000_4.08.605.2.exe, with the phone connected to the pc. Follow the steps provided and it should reflash the phone for you.
Okay I tried to do your second suggestion first but when i ran the program it said that the phone was not connected to my computer, and to check to make sure the USB was plugged in. It was though, it was in charge only, should i have set it on something else? I was literally watching it charge.
Then i reformatted my SD card, it did find the file and it tried to update with the file in hboot but it said it had failed because the version on my phone was older.
What a pain huh?
thisistay said:
Okay I tried to do your second suggestion first but when i ran the program it said that the phone was not connected to my computer, and to check to make sure the USB was plugged in. It was though, it was in charge only, should i have set it on something else? I was literally watching it charge.
Then i reformatted my SD card, it did find the file and it tried to update with the file in hboot but it said it had failed because the version on my phone was older.
What a pain huh?
Click to expand...
Click to collapse
Having htc sync installed should give you the correct drivers. I think its suppose to be charge only mode, try it on sync mabey, worst it can do is say it cant find the phone again.
It probably said the version you were trying to install is older than the one already installed. What android version are you on again?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
says im using version 2.3.4
just tried the ruu again and put my phone in sync instead of charge only and htc sync and the ruu still say my phone isnt connected but my phone tells me it is.
The main reason I'm trying to factory restore is because none of my apps hold. I try and download new ones and they end up force closing and disappearing. Apps that I update do the same thing. My phone will keeps apps i've had if they update and disappear but they go right back to needing to be updated again. New apps just go away and if i try and redownload them they just disappear again.
Hi Folks,
It's been awhile, but I'm trying to remove bloat from our old Incredible 2 and it still retains S-OFF from using Revolutionary years ago.
The only methods I've read in this forum to root the Inc2 involve downgrading to 2.3.3 first, then rooting. I haven't looked at re-rooting this device in awhile, obviously.
Guess my question is if I can avoid downgrading and do something a bit more direct. Ideas welcome!
Thanks.
As far as I know, you still have to downgrade to 2.3.3. It's not hard. Just follow the steps.
Yes, it's not hard, I just wanted a faster path.
Now to get the darn thing to connect via USB, since the single-click solution I tried apparently messed things up.
If you can't get USB to work, you have three other options.
Download the zip file using your phone's web browser instead of your computer. Unzip the tacoroot file on the phone, and inside it will be a zip file for the 2.3.3 RUU (ROM Update Utility). Rename it to PG32IMG.zip.
If you have the file on your computer, take the SD card out of the phone and put it in your computer's SD card reader. Then put PG32IMG.zip (see option #1) on the SD card and put the card back into the phone.
If the is on your computer but you don't have an SD card reader, install ES File Explorer on the phone and then transfer PG32IMG.zip (see option #1) to the phone using either an SMB share on the computer or the ES File Explorer's FTP server (called Remote Manager in the left sidebar). Option #1 is less work, but this way wastes less bandwidth if you already have the file on your computer, because it would be file transfer over the local network instead of over the Internet.
Once you have PG32IMG.zip at the top level of your SD card, restart the phone while holding down power and volume down. This should take you to the bootloader. Inside the bootloader (or maybe fastboot, which you can get to from the bootloader), the phone will scan the SD card, detect the PG32IMG.zip file, and ask if you want to install the update. Plug the phone into a charger, then say yes. DO NOT POWER OFF THE PHONE WHILE IT INSTALLS THE RUU.
Restart the phone. The phone will now be in a fully factory default state with 2.3.3 but will still have S-OFF. In other words, the 2.3.3 RUU should solve the USB problem you mentioned.
Remove PG32IMG.zip from SD card, using either your computer or a file manager app such as ES File Explorer. Install TWRP custom recovery using the "Download - Recovery Image Method" steps on this page: http://teamw.in/project/twrp2/71
Once TWRP Recovery is installed, you'll be able to use it to install custom ROMs, kernels, gapps, etc. Other custom recoveries you could use include the latest version of 4EXT or the latest version of ClockworkMod.