The other day my P3300 was somewhat slow and I decided to give it a soft reboot. Ever since it keeps on rebooting. It reaches the phase where you may enter your pincode but when it wants to load the user interface it reboots again.
Sometimes I have luck and after 5 loops or so it finally gets into full WM5.
If I remove the SD card the problem dissappears. So I expect it's the card (which never corrupt(ed/s) on me).
Another option would be it has run out of main memory. I'm a little short on that one. Would it reboot if memory was too low?
I think a hard reset or format of the SD card would solve it but that is the easy way. I want to know the reason so it won't happen again.
HTC P3300 T-mobile Compact III
2GB Sandisk microSD
WM5 and updates original as a danish virgin
I installed the Artemis SD patch
I had this a few times and the only way around it was a hard reset followed by a recovery of the phone from SPB backup.
It always seemed to follow me installing software, but never the same application so I thought it had corrupted something in the startup. You can try booting without the card installed and it should be OK, then you may be able to work out what app ./ reg entry is causing it.
HTH
I rebooted without card and it worked
i put the sd card in my cardreader and defaced some .exe's in my autorun folder (the 2527 folder). Than it worked again. Until... a few days ago it started all over again.
did the same procedure but there was no .exe anymore in the autorun folder.
I dont want to do hard reset. Do you guys have any clue if i can see in the register what it tries to run?
it's defenitely one program doing this. It boots straight into WM5 and is responsive but after let's say 3 seconds BOOM there it reboots again.
Mine did the same, deleted a few folders from the storage card Program Files\ folder, think from memory the progs causing mine to reboot were CE Converter Pro, Pocket Weather & E Wallet Pro, but as already mentioned it can be any number of different programs, I didn't delete any reg entries, just the actual folders on the memory card, it seems to be a common problem I a very serious bug as far as I'm concerned, definitely one that needs addressing.
Hi,
Using MDA III, with Tom-Oops-Black-v1.0-WWE ROM, and the TT_Nav_7.450.9028_black.cab file. When I click the CAB, and choose the install location, the message Installing TT_Nav_7.450.9028_black.cab... remains on screen for ever, with no change in the progress bar.
I have tried soft and hard resets, with the same issue. Other CAB files install ok.
I have tried several TomTom7 CABS
Please advise if you have seen this, and a possible fix?
You could try installing tomtom to your sd card using another rom. Then putting oops back on. Tomtom runs straight of my sd card i installed it once and every hard reset or new rom i just need to make a shortcut.
worth a try
cool, i'll try that via my other device which works, thanks. I wasn't sure if it needed registry or windows system changes.
try format your sd card, copy totmtom.cab file and run it. Always works for me
Thanks people
Zetsumei,
Thanks, I just copied the install form the other working device, and pasted onto the other devices SD Card, works perfectly.
Freo73,
Good advice, I was going to do that when I got home, because I do not have the micro SD adaptor. I did copy the CAB file to internal memory, and the install also hung there...
For now, this issue is resolved.
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.
I have been successfully using the Android builds on my TP2 without any issues. However, when I tried Rhobuntu (which is very exciting by the way!), I have had problems since I shut it down to reboot.
When trying to launch any programs that are installed on the SD card, either through a proper cab install or by trying to run Haret off the SD card, I get the following message:
[highlight]
The file 'filename' cannot be opened. Etiher it is not signed with a trusted certificate, or one of its components cannot be found. If the problem persists, try reinstalling or restoring this file.
[/highlight]
I am still able to access all the files from Windows Mobile 6.5. I can open data files such as mp3 or jpg.
If I try to install a cab file (from the SD card or the main memory after copying it there), it tells me the file is from an unknown publisher etc, and I can choose to continue. However, it then tells me that the installation was unsuccessful.
Prior to using Rhobuntu, I could install and use applications on the SD card with out any problems.
I have searched the forums and the internet, but I can't find any answers that are applicable - plenty of questions like mine though!
One example is on the first page of the Rhobuntu sticky thread, but it appeared to go unanswered:
http://forum.xda-developers.com/sho...opened+signed+trusted+certificate#post5771699
Help please!
Ed
Ed,
It was I who posted the question in the other thread. Unfortunately, I never got a solution to the problem so I ended up performing a hard reset.
I had the same issue again when I ran Rhobuntu so I've pretty much given up on it.
Sorry I can't be more helpful.
R.
snalbansed said:
I have been successfully using the Android builds on my TP2 without any issues. However, when I tried Rhobuntu (which is very exciting by the way!), I have had problems since I shut it down to reboot.
When trying to launch any programs that are installed on the SD card, either through a proper cab install or by trying to run Haret off the SD card, I get the following message:
[highlight]
The file 'filename' cannot be opened. Etiher it is not signed with a trusted certificate, or one of its components cannot be found. If the problem persists, try reinstalling or restoring this file.
[/highlight]
I am still able to access all the files from Windows Mobile 6.5. I can open data files such as mp3 or jpg.
If I try to install a cab file (from the SD card or the main memory after copying it there), it tells me the file is from an unknown publisher etc, and I can choose to continue. However, it then tells me that the installation was unsuccessful.
Prior to using Rhobuntu, I could install and use applications on the SD card with out any problems.
I have searched the forums and the internet, but I can't find any answers that are applicable - plenty of questions like mine though!
One example is on the first page of the Rhobuntu sticky thread, but it appeared to go unanswered:
http://forum.xda-developers.com/sho...opened+signed+trusted+certificate#post5771699
Help please!
Ed
Click to expand...
Click to collapse
make Hard-reset . (you will lost all you data on the phone)
Works after hard-reset
Thanks dicko, walter.
I finally gave up and did a hard reset, and before setting everything up again I tried Rhobuntu again, like dicko had.
This time, I can use Rhobuntu, and go back to Windows, and everything still works. Phew!
Differences between last time and this - I don't know if any of them are relevant:
1/ This time the Windows only has stock Vodafone ROM Win 6.5 plus TomTom as it automatically installed when I put the SD card in. Last time lots of other programs were installed also.
2/ This time I used the latest Rhobuntu release - 19032010 on the fileshare, 18032010 according to the first post that the filed share was linked from. It was xfce. Last time I was using 12032010.
3/ This time I chose Reboot when I was finished with Rhobuntu. Last time I chose Shutdown.
Now to rebuild my Windows system!
**Disclaimer so that this doesn't get deleted. I looked at all the posts and tried to search, couldn't find any answers and I made this thread HERE because I doubt anyone in "General" would know what I'm talking about. This is more of a development question.**
----------
Ok, I am actually having two problems.
1) Normally when I plug my phone in the computer and choose "disk drive" mode, a screen pops up on my PC titled "Removable Disk (J)" That's actually not the right one because right behind that screen I get another pop-up titled "Removable Disk (K)" and that's actually the one with the folders and everything that I'm supposed to use (the root of the sd card folder.) So I hit cancel on (J) and am on my way using (K).
Well over the weekend, on Friday, I rooted my phone using toast's way and then I went camping without doing ANYTHING else.
Then I come back last night, everything is working fine and I installed ROM Manager on there because I wanted to flash Pete's "BuglessBeast". Since my internet connection in my basement is super slow I decided to just leave it at that and work on it at work today. Well here I am.
Problem: Phone was not connecting to computer. It kept giving me errors and then asked me to Format my card. After about half hour of trying to get it to connect I said "fine.. I'll just format it and factory reset my phone and root all over again and do all this. Well now.. phone is only connecting to (J) drive. (K) never appears.
2) Also, after rooting and finding out that ROM Manager won't work for me I have to manually download the file, I tried to go into recovery mode and every time I selected "sd card: apply update.zip", I keep getting the same error saying "FILE NOT FOUND ON SD CARD".
Any help please?
Am I doing something wrong?
Is there a way to start over, all over again?
With the problem running (where you can see both disks), right click on "My Computer" and select "manage", then go to "Disk Management" and see if your SD card is partitioned or something. That's very unusual and should only present itself if your SD card is partitioned and it's seeing both partitions.
arozer said:
**Disclaimer so that this doesn't get deleted. I looked at all the posts and tried to search, couldn't find any answers and I made this thread HERE because I doubt anyone in "General" would know what I'm talking about. This is more of a development question.**
----------
Ok, I am actually having two problems.
1) Normally when I plug my phone in the computer and choose "disk drive" mode, a screen pops up on my PC titled "Removable Disk (J)" That's actually not the right one because right behind that screen I get another pop-up titled "Removable Disk (K)" and that's actually the one with the folders and everything that I'm supposed to use (the root of the sd card folder.) So I hit cancel on (J) and am on my way using (K).
Well over the weekend, on Friday, I rooted my phone using toast's way and then I went camping without doing ANYTHING else.
Then I come back last night, everything is working fine and I installed ROM Manager on there because I wanted to flash Pete's "BuglessBeast". Since my internet connection in my basement is super slow I decided to just leave it at that and work on it at work today. Well here I am.
Problem: Phone was not connecting to computer. It kept giving me errors and then asked me to Format my card. After about half hour of trying to get it to connect I said "fine.. I'll just format it and factory reset my phone and root all over again and do all this. Well now.. phone is only connecting to (J) drive. (K) never appears.
2) Also, after rooting and finding out that ROM Manager won't work for me I have to manually download the file, I tried to go into recovery mode and every time I selected "sd card: apply update.zip", I keep getting the same error saying "FILE NOT FOUND ON SD CARD".
Any help please?
Am I doing something wrong?
Is there a way to start over, all over again?
Click to expand...
Click to collapse
development is not for posting questions, q and a is for posting questions (hence the name)
you probably built an ext container before (partitioned the card, using one of the recoveries). if you partition the card, they will come up as two disks when you plug the usb in. when you 'repaired' it, it formatted the whole thing into one block. by formatting, you've erased anything you had on it. you'll have to put the files you want back on the card.
arozer said:
Any help please?
Am I doing something wrong?
Is there a way to start over, all over again?
Click to expand...
Click to collapse
ive seen quite a few windows users on here name their file update.zip but have hidden file extensions turned on so in reality the name is update.zip.zip which will not work.
if thats not the issue, something sounds very wrong with your microsd card.
not sure why you had two partitions, J and K, but seems to hint at app2sd or had two partitions setup on the microsd card ...
my friend had one go bad on him yesterday, i had never seen it before but perhaps there is something defective.
otherwise, a reformat of the card, should bring it back to new.
Thread Moved to Q&A.
[Fixed]
joeykrim said:
ive seen quite a few windows users on here name their file update.zip but have hidden file extensions turned on so in reality the name is update.zip.zip which will not work.
if thats not the issue, something sounds very wrong with your microsd card.
not sure why you had two partitions, J and K, but seems to hint at app2sd or had two partitions setup on the microsd card ...
my friend had one go bad on him yesterday, i had never seen it before but perhaps there is something defective.
otherwise, a reformat of the card, should bring it back to new.
Click to expand...
Click to collapse
THANK YOU SOOOO MUCH!
Ok. That worked.
That was actually the problem. =D
I thought my phone was going all sorts of crazy.
Thank you thank you thank you.
---
Now installing bugless beast. Hopefully the phone will connect to my computer now.
Edit: everything seems to be running fine now.
Thanks joey.