Develop Bugs

Help please

I dont know whats wrong with my phone I flashed the romeo 6.5 htc sense 2.5 rom onto my phone earlier and it was working fine but then it started to act up. the htc sense was laggin and skipping alot and then i tried to flash to another rom but it kept telling me that i dont have enough memory to put the nbh file onto the explorer folder. so i go check my documents on my device but nothing seem to appear. so i did a hard reset but since then the only thing that keeps showing on my screen when i turn it on is just the 1st screen of that says touch pro 2 then it blinks to another screen and it just says windows mobile romeos initializing configuration please wait but it stays on that screen and does nothing else
help please

ariel123 said:
I dont know whats wrong with my phone I flashed the romeo 6.5 htc sense 2.5 rom onto my phone earlier and it was working fine but then it started to act up. the htc sense was laggin and skipping alot and then i tried to flash to another rom but it kept telling me that i dont have enough memory to put the nbh file onto the explorer folder. so i go check my documents on my device but nothing seem to appear. so i did a hard reset but since then the only thing that keeps showing on my screen when i turn it on is just the 1st screen of that says touch pro 2 then it blinks to another screen and it just says windows mobile romeos initializing configuration please wait but it stays on that screen and does nothing else
help please
Click to expand...
Click to collapse
Sounds like you flashed one too many times. The Custom RUU's do not reformat the ROM chip. Flash a Stock ROM like one of the HTC Official Updates. This will have the stock RUU which does format the ROM chip. Then, you can go flash any ROM you like. I had this same problem once on my Kaiser where folders would disappear.

drkfngthdragnlrd said:
Sounds like you flashed one too many times. The Custom RUU's do not reformat the ROM chip. Flash a Stock ROM like one of the HTC Official Updates. This will have the stock RUU which does format the ROM chip. Then, you can go flash any ROM you like. I had this same problem once on my Kaiser where folders would disappear.
Click to expand...
Click to collapse
@drkfngthdragnlrd
Hey mate, does it means that if I flashed too many ROM in a particular period then this problem would occurred? lol~ I didn't clearly understand what you explained.
Cheers

Help with flash
I flashed my rom and installed wm6.5 now I cannot sync to my pc with vista. Please help

what150 said:
@drkfngthdragnlrd
Hey mate, does it means that if I flashed too many ROM in a particular period then this problem would occurred? lol~ I didn't clearly understand what you explained.
Cheers
Click to expand...
Click to collapse
Not that it would occur, but something similar "could" occur. This is why in the Kaiser section they always told you to flash stock/hard reset/flash custom ROM of choice/hard reset. It's not that you need to, but doing so an help prevent weird bugs from showing up like what he explained. It's just like installing Windows on a PC, they always recommend you format the drive on each install or your install could be buggy. For best results you format so the drive is clean & no left over files that can screw with the new install. Plus, low level formating will gain back bad clusters in the hard driver/ROM chip lost during use by data corruption. This format process is disabled in the XDA made Custom*RUU.exe for various reasons. So the more ROM's you flash, the more changes occur on the ROM Chip & the more likely a bug could appear.
sdb156 said:
I flashed my rom and installed wm6.5 now I cannot sync to my pc with vista. Please help
Click to expand...
Click to collapse
Check in the ROM's thread. Also, you may need to clear the PC's sync partnerships. If you have flashed a lot the PC can only handle so many Partners. Each time you flash a new ROM, it creates a new partner as it think's it's a different device.

how do you soft and hard reset the att tilt 2? Had an old tilt and I just got this a few days ago still figuring it out

sdb156 said:
how do you soft and hard reset the att tilt 2? Had an old tilt and I just got this a few days ago still figuring it out
Click to expand...
Click to collapse
Soft Reset hole is on the side of the device. It may be under the battery door. The side with the stylus, under the secondary Mic.
Hard Reset is done by holding Send/End/Power & pressing Soft Reset with stylus. Hold the Send/End/Power keys till the Hard Reset message appears onscreen.

This was the first flash I did and after a hard rest still will not sync and nothing in the thread for the rom. I cleared all my partnerships. The phone is connected and I can transfer files to and from my storage card. Do I need to update the device driver on my pc? Any way to get my outlook 2003 contacts on the phone through my storage card or any other way?

sdb156 said:
This was the first flash I did and after a hard rest still will not sync and nothing in the thread for the rom. I cleared all my partnerships. The phone is connected and I can transfer files to and from my storage card. Do I need to update the device driver on my pc? Any way to get my outlook 2003 contacts on the phone through my storage card or any other way?
Click to expand...
Click to collapse
If running XP you need ActiveSync 4.5, if running Vista/7 you need Windows Mobile Device Center 6.1. All drivers for the devices come from those programs. Have you tried manually opening Active Sync/device Center to see if it's connecting/seeing the device? Also, make sure there's no setting on the device making it act as a USB Mass Storage drive. Some ROM's give a app or setting to do this as it increases transfer rates for copying files, but it doesn't allow syncing.

I have win mobile device center and know sync. the phone will connect for usb mass storage and I can access the files on my storage card. when I connect my phone it gives me the option of outlook sync or flash drive. I select the outlook sync and the first time my pc said the device was installed successfully but no recognition from mobile device center.

sdb156 said:
I have win mobile device center and know sync. the phone will connect for usb mass storage and I can access the files on my storage card. when I connect my phone it gives me the option of outlook sync or flash drive. I select the outlook sync and the first time my pc said the device was installed successfully but no recognition from mobile device center.
Click to expand...
Click to collapse
Hum, I'm at a loss, I would post in the ROM's thread to see if anyone else has/had this issue. Maybe it's ROM related?!?!? I'm running ROMeOS without sync issues. Granted I don't sync anything, but when i open device center the device does show up. I always check this, because if the device isn't seen by WMDC, I can't get data connections while connected to USB. I have this problem a lot because I removed WMDC from startup as I don't want an app running in the BG taking up resources when I don't use it.

actually what i did was flash my rom through micro sd because my phone wouldnt load to the home screen so i wasnt able to connect to aactive sync. thank god i got my wife a tp2 also wich i was able to dl the nnhb file on the micro sd card and then just run it from my phone but yes i did flash my rom way too many times during this past weekend id say about t times in a days is there a limit of times you can flash a device per day because i dont want to fry my phone up lol silly me

ariel123 said:
actually what i did was flash my rom through micro sd because my phone wouldnt load to the home screen so i wasnt able to connect to aactive sync. thank god i got my wife a tp2 also wich i was able to dl the nnhb file on the micro sd card and then just run it from my phone but yes i did flash my rom way too many times during this past weekend id say about t times in a days is there a limit of times you can flash a device per day because i dont want to fry my phone up lol silly me
Click to expand...
Click to collapse
For future reference, you don't need to flash via SD if you are stuck. Just follow these steps.
1) Power Off
2) Hold down Volume Down button
3) Plug in USB Cable
4) Boot Loader appears onscreen & at button in White space says "USB"
5) Flash ROM via PC as normal.

yea but its not going to be connected to active sync so how do i get the nbh file onto the phone unless i can just run the ruu and it will flash

ok now everytime i try to flash my rom back to the stock one through micro sd it starts the process but then the back light turns off and then the phone stays off and i have to hard reset it can someone help me and when i connect it to the pc it has the bootloader but it says error on the bottom of the screen
do i have to flash my radio back to stock also?

I had the same problem... luckily t-mobile has a buyers remorse program... because I could not get the active sync/WMDC to work either... did you download the wifi cab on another thread? I ask because this is what did it for me? Or maybe a combo of cabs but definately linked to the wifi cab... Gettin a new phone today... if anyone figure this out, make it a sticky!

How to revert back to WM after flashing Android to NAND?

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.

Problem with "fullproof" card

So for the past week or so ive been trying to root my incredible to no avail... ive used every method posted and none work..
The two cards i tried are the 2gb card that came with my droid incredible.. formatted Fat32 1024 byte size with nothing on the card, and it didnt work on ANY method.. so then i tried my transcend 8gb class 6 card that was previously formatted to Fat32 awile ago and had a bunch of stuff on it, and nothing worked with that one either..
So then i said screw this, i went out and bought the holy card that supposidly has a 100% success rate... the Kingston 4gb class 4 card.. put that bad boy in and it dosent work either! what the hell can i do... the Kingston is brand new.. nothing on it, formatted Fat32 1024 byte size

did you format it in the phone?
Sent from my ADR6300 using XDA App

I formatted it via my PC.. Windows7 i used the format tool in My Computer... i didnt do quick format either i did the full format Fat32 1024 byte size

format it in your phone once and give it a few tries
Sent from my ADR6300 using XDA App

is this done in recovery or Hboot or what?

while phone is fully booted. menu > settings > sdcard and phone storage
scroll down to the bottom
Sent from my ADR6300 using XDA App

Just formatted the card via phone then went back into recovery and tried and no go.. ive tried it about 35 times now with this *100% successrate card* and gotten zero, also keep in mind that the design of this particular card makes it impossible to click in and out in rapid succession, it keeps getting stuck like the stock verison 2gb card does while my transcend 8gb has no problems clicking rapidly

my guess is you are doing something wrong or something is not set up right
Sent from my ADR6300 using XDA App

invisiblek said:
my guess is you are doing something wrong or something is not set up right
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I wish that was the case but i have no problem using ADB in any setting, the drivers are definately set up right as i can use ADB fine while in android and i can even get an adb reboot recovery out of it before the phones fully booted up normally as in binnys method

http://www.youtube.com/watch?v=Z8mheIkQ-1o
dunno if u saw that yet, thats the video i made the night they got root
i have a kingston 4gb class 4 and thats the method i did there
this method works 100% of the time for me too

yeah. been trying that method for an hour just as in the video and its been 0% for me lol

There is no sdcard that is going to make the method foolproof. You need to reduce your variables. Windows driver scheme can become a mess very, very quickly. I recommend booting your PC with a Linux LiveCD like Linux Mint 9 Isadora or Ubuntu 10.04 Lucid Lynx. They're both free and both distros recognize the DI out of the box. I've attached the ./loop.sh that I've used successful to bring up the adb error you're looking for--just rename the file before you run it from linux terminal. Navigate your browser in linux and download the Linux Android SDK ho ~/Downloads, and once you do, extract it to ~/Downloads. Then, to be ultra-safe, use these commands:
Code:
*open terminal*
cd ~/Downloads/ # assuming you d/l'd my file/SDK file to your home Downloads folder in Linux
cd android-linux-sdk_86/tools
sudo ./android
# this will trigger the SDK installer, just tell it to fetch all packages, then close it
rename loop.sh.txt loop.sh
chmod a+x loop.sh
sudo ./loop.sh
# you'll get an infinite loop with "adb: device not found"
At that point, pop the back cover off your DI, power it down, connect the USB cable, boot into bootloader, eject the SDcard, making sure your terminal window is visible: select Recovery menu, then start counting from the boot vibrate. Count to seven seconds (as in: one-one-thousand, two-on-thousand ...), then insert the card exactly on 7 or when the white screen scanline flickers, whichever comes first.
Hint: I like to do this with the terminal window kinda small with a maximized "Computer" Nautilus file explorer window up in the background, showing all devices. You'll notice with this view that your android devices appear, in bootloader, disappear on recovery reboot, then reappear when recovery/black triangle screen is done loading. If you've missed the timing window and the card wasn't inserted right, you'll see those two volumes pop-up, but your adb shell error message won't have changed--and you know to pull the battery and start over. If the message does change when when the drives appear: success! You can "up vol-power" and continue with whatever rooting method you like, provided you know the slight (good) differences using linux introduces versus Windows.
Good luck, you only have to do this right once, then Unrevoked2 locks it in place!

Dude, it took me forever. In the end it was finding the right time to insert the SD card for me. I would start out with it in then right before I selected recovery I would pop it out and then I would push it back in as close to the same time as the 2nd "mount tone" as I could. I have only had success with class 6 cards but both an 8 gig and the infamous 2 gig PNDY card have worked for me. I also had a prob with getting the adb shell to work after a did the push payload witch turned out to be a bad download of the "tools folder". re-downloaded it with the phone still in recovery and it was smooth sailing from there.
Don't get discouraged and have a lot og free time when you start trying the next time.

Did you try downgrading? I had no much for a week then I downgraded ands got it on the very first try. Good luck
Sent from my ADR6300 using XDA App

I tried for DAYS to get this to work... I searched every android forum on the net for tricks... I gave up... I got pissed and started again... gave up again... and finally like magic I found the right combination of bull**** trickery to make it work.
How I did it:
1. Turn off the phone normally
2. Remove sd card (I used the 2g card that Verizon sent)
3 Boot up into recovery with the Vol- /Power button method (sd card out)
4. Let the phone do it's thing
5. Run loop.bat
6. The trick here- When you press the power button to select recovery have the sd ready to go in (sitting in the slot but not clicked into mounted position)... then when you hear the second usb "ding" push it in as fast as you can- almost simultaneously with the "ding".
This got me into the error message in about two tries (after possibly hundreds of failed attempts using other methods)- after that it's pretty much downhill.
No guarantees, but it worked for me and quite a few other frustrated souls.
Keep the faith- root is definitely worth the headache

Edit: Disregard. I didn't see that rynosaur had already posted detailed steps above.
Windows needs to see the device as too many different things during the different stages (i.e. HBOOT, Recovery, Fully booted). I did it under Linux and didn't have to worry about that. If you have a Linux partition or a Linux Live Distro, try it there. The commands are basically the same except you need to preceed the adb commands with ./ as in ./adb reboot recovery

DobbsianYeti said:
I tried for DAYS to get this to work... I searched every android forum on the net for tricks... I gave up... I got pissed and started again... gave up again... and finally like magic I found the right combination of bull**** trickery to make it work.
How I did it:
1. Turn off the phone normally
2. Remove sd card (I used the 2g card that Verizon sent)
3 Boot up into recovery with the Vol- /Power button method (sd card out)
4. Let the phone do it's thing
5. Run loop.bat
6. The trick here- When you press the power button to select recovery have the sd ready to go in (sitting in the slot but not clicked into mounted position)... then when you hear the second usb "ding" push it in as fast as you can- almost simultaneously with the "ding".
This got me into the error message in about two tries (after possibly hundreds of failed attempts using other methods)- after that it's pretty much downhill.
No guarantees, but it worked for me and quite a few other frustrated souls.
Keep the faith- root is definitely worth the headache
Click to expand...
Click to collapse
the sdcard usb ding timing is key

So heres what happened, my first Kingston 4gig card didnt work after like 40 tries, so i said screw this and returned it, and then i went somewere else and picked up a second 4gb kingston
Went home, put it in my phone, rebooted recovery and got it to work instantly... got the recovery flashed... removed cityid.. pushed the update.zip and su and superuser all on my phone
however my phone would NOT chmod no matter what i did.. i tried everything, i copied and pasted the directions exactly as on the screen and it would never work, when i got to the last line that starts of 1n - or something like that it would say permission denied even though i was in su...
So anyway i said maybe it had worked, so i rebooted the phone.. i saw that superuser.apk was in my app drawer as an installed app.. then i went into terminal emulator and typed in "su" and it said permission denied.. the root didnt stick because the stupid Chmod did not work for me...
Oh and to top it off guess what else happens? Obviously when i try to go back into recovery it DOES NOT work... tried it about 35 times again now and it wont go back in whatsoever after doing it the first time.. also for me in recovery my second usb ding happens MANY seconds into the black screen.. if you start counting right when you press the power button for recovery and the white screen turns to black at like 5 seconds.. my second usb ding dosent happen until like 10 seconds... deep in the black screen

Joe92T said:
Oh and to top it off guess what else happens? Obviously when i try to go back into recovery it DOES NOT work... tried it about 35 times again now and it wont go back in whatsoever after doing it the first time.. also for me in recovery my second usb ding happens MANY seconds into the black screen.. if you start counting right when you press the power button for recovery and the white screen turns to black at like 5 seconds.. my second usb ding dosent happen until like 10 seconds... deep in the black screen
Click to expand...
Click to collapse
What's the difference now? Look at the root directory of the card. There's files there now. You need to re-format the card. The most effective formatting I (and others) have found is a split 2gig ext4 partition (linux fs), followed by a fat32 @ 1024k block allocation, long format. As soon as Android boots, it starts writing your card.

rynosaur said:
What's the difference now? Look at the root directory of the card. There's files there now. You need to re-format the card. The most effective formatting I (and others) have found is a split 2gig ext4 partition (linux fs), followed by a fat32 @ 1024k block allocation, long format. As soon as Android boots, it starts writing your card.
Click to expand...
Click to collapse
How can i format it like that using windows? The easy format tool you find when right clicking on the drive under my computer dosent have those functions

App installer not working after root PLEASE HELP!!!

Hello Everyone!
I just rooted using UnRevoked 3.0. I was installing apps on to sd card and suddenly (while installing free spades from Market) the phone just sat there at "Installing spades" and never completed. Even worse now NOTHING installs. Not even the OTA Sprint voice mail upgrade app. What I did notice is that I can't format the SD card, the option button is grayed out. When I try to unmount the card I get this error:
"Sorry! Activity SD & phone storage (in Application Settings) is not responding."
I have the option to FC or wait and if I try and wait, the message just loops. Is there ANYTHING ANYONE can tell me about this. Please, please help!!!!

Try restarting the phone and see if that helps.

restarting doesn't work, re-running Unrevoked doesn't work. I don't know what else to do. Am I just app-less now?

It happens. Sometimes it takes a few hours to go back to normal, at least in my experience. Is it working for you yet?

Amy7 said:
Hello Everyone!
I just rooted using UnRevoked 3.0. I was installing apps on to sd card and suddenly (while installing free spades from Market) the phone just sat there at "Installing spades" and never completed. Even worse now NOTHING installs. Not even the OTA Sprint voice mail upgrade app. What I did notice is that I can't format the SD card, the option button is grayed out. When I try to unmount the card I get this error:
"Sorry! Activity SD & phone storage (in Application Settings) is not responding."
I have the option to FC or wait and if I try and wait, the message just loops. Is there ANYTHING ANYONE can tell me about this. Please, please help!!!!
Click to expand...
Click to collapse
I encountered a problem similar to this with my Evo. Basically the card stopped working and said I need to format it, but then it wouldn't let me actually format it. I contacted HTC and apparently they had a "bad batch" of the cards and they'll replace it for free, when they have some in stock. My advice would be to contact HTC or Sprint.

Not working yet. But one thing I forgot about is that after I rooted it I also installed "Choose install" from the Market and set the default to the storage card. I wonder if I should try and unroot my phone. I'm stuck there to because if I understand things right I would have to access my sd card to load a new zip file on it in order to unroot. My pc will no longer let me browse my device.

donnie_darko said:
I encountered a problem similar to this with my Evo. Basically the card stopped working and said I need to format it, but then it wouldn't let me actually format it. I contacted HTC and apparently they had a "bad batch" of the cards and they'll replace it for free, when they have some in stock. My advice would be to contact HTC or Sprint.
Click to expand...
Click to collapse
Thanks for the tip. That could be why I can no longer browse the device from my pc. I will give that a shot. Thanks!

Amy7 said:
Not working yet. But one thing I forgot about is that after I rooted it I also installed "Choose install" from the Market and set the default to the storage card. I wonder if I should try and unroot my phone. I'm stuck there to because if I understand things right I would have to access my sd card to load a new zip file on it in order to unroot. My pc will no longer let me browse my device.
Click to expand...
Click to collapse
You will need access to an SD card to unroot. My advice would be to either buy another one or just borrow a friend's or something. Why do you want to unroot anyways?

Aerodynamix said:
You will need access to an SD card to unroot. My advice would be to either buy another one or just borrow a friend's or something. Why do you want to unroot anyways?
Click to expand...
Click to collapse
I don't really want to, I just thought I would have to do that to try and go back to "stock" or if I'm using the word right, back to the way it was when I got it. I thought it might be my last resort to fixing it. I would still re-root again so I can try and figure out how to get rid of all of sprints bloatware.

Just an update - I bought me a new sd card from buy.com, a 16 gb for about $30. It fixed the problem for a little bit. I started installing my apps, got a good amount of them on there and it happened again! I'm starting to wonder if you just can't install very many apps for this phone or by some odd coincidence I got a 2nd bad storage card????. Weird. I might start a new thread for this but thanks for all you who participated. You rock!

when it's stuck on install can you go to your manage applications option in settings and see if they're all stuck on 'computing' too?
Because this sounds all too familiar.

mmmtacos said:
when it's stuck on install can you go to your manage applications option in settings and see if they're all stuck on 'computing' too?
Because this sounds all too familiar.
Click to expand...
Click to collapse
I have the same issue (seems to have started after I started using modinstallocation). About one in ten times I'm able to get my sd card apps back after battery pulls and multiple reboots, but not this time. When I go to manage apps, all the SD card apps are 'computing'.

greyopaque said:
I have the same issue (seems to have started after I started using modinstallocation). About one in ten times I'm able to get my sd card apps back after battery pulls and multiple reboots, but not this time. When I go to manage apps, all the SD card apps are 'computing'.
Click to expand...
Click to collapse
i got mine all back today. I wiped the Dalvic cache from clockwork mod, and everything came back after a reboot about 5 minutes later.

[Q]Phone randomly shuts down using Virtuous Unity 2.35

For a few weeks i have been getting these total random shut downs of my DHD running the latest Virtuous Unity 2.35.
I saw that happening live 2 times on specific occasions/functionality calls:
1)After switching the DHD on and inserting the PIN to unlock the sim card...few secs and BAM....everything goes down. This happens from time to time.
2)Few secs after running the camera app...some loading goes on and BAM...here we go again...cell goes off
What the hell is happening, should i worry about the phone hardware or is it some wipe/format i didn't do properly prior to flashing the rom.
The problem is i noticed it also with other custom roms...but with those it never happened while i was using it, instead it happened getting the phone out of my small shoulder bag.
I am really afraid my cell has something wrong with the hardware...i was angry as hell and i tried to do some "heavy shakin" to see if the battery was not retained to its place as it should have but nothing happened...cell always on...
What should i do?
PS: i must say i tried almost 15 roms last 2 weeks but always used the related full wipe files/used a decent format/wipe procedure.
plz help me
---------------------------------------
Some tech stuff maybe you need to know
Device: Desire HD
Rom: (current) Virtuous Unity 2.35 (those days i flashed more than 10 roms, MIUI included)
Status: S-OFF HBOOT-0.85.2007 (CID-11111111)
Radio: 26.09.04.11_M2
RIL: 2.2.0131HM
Kernel: Stock that comes with VU
So that you know that's what i always did prior to flashing any ROM (currently using 4EXTRecovery 2.1.3 RC2) :
1)format system
2)format cache
3)format data
4)wipe data/factory reset
5)FLASH ROM
--------------------------------------
EDIT1: I noticed, just to keep you posted, that on the recovery menu the SD appear to be "not well partitioned", i don't know if it may be the cause.

Do you have app2ext working?
I'm guessing here. Try backing up your SDcard on a pc (preferably via cardreader) and giving it a thorough format with one partition only. You may need to delete the partitions first. I can't tell you how unless I know your operating system. If you continue having the shutdown issue afterwards you would be able to cross out SDcard problems at least.

Hi ROBINGAZI, thanks for your fast reply.
ehm, what is exactly app2ext?
I don't have a card reader right now, does it really change if I mount the SD via the phone? Anyways, i got a machine running WIN 7 x64.
hope this step will clear out the problem

Plug your phone to the computer as disk drive.
copy everything you have on the sdcard to a directory in your computer.
then click start>control panel>administrative tools> computer management.
a window will appear and you should see "storage"
in storage you will find "disk management".
you should be able to see your phone's SDcard there. right click and then delete the partition into unallocated space. Then right click and create a partition (fat32). format the partition.
if needed remount the sdcard to your computer (not the phone)
copy only one zip file (the rom you want to flash) to the SDcard (preferably something reliable like stock or something very close to stock).
unplug the phone and reboot into recovery. Do a full wipe...format everything apart from the sdcard if you think it is proper.
flash the rom and see what happens.
this way you can at least rule out the SDcard for causing your problems.
PS: Dont restore via nandroid...you could be putting the problem back into your phone.
BTW: Does your phone shut down properly or the screen goes blank like it would if you unplug a computer. Anyway make sure you dont just have a loose battery cover or battery before you try this out.

Thanks again.
Yeah my phone screen just goes blank like it would if you remove the battery from it while on.
I restored the SD card and it works properly. installed Revolution HD 5.2.6
As i stated earlier i also tried to shake the phone to see if the battery had some kind of faulty retention system but the phone stays on.
So i really can't understand what is the problem.
PS: I was curious, is there an application that tells you the entire life of a battery? meaning since when it started to operate?

NEW UPDATE ABOUT THE MATTER:
It's DEFINITELY the battery...i don't know why, i don't know with what criteria but it's the battery.
Yesterday i switched it with my brother's phone, obviously another DHD. Since then i have had absolutely no problem of any sort. He, instead, is experiencing random shut downs...
i think that the "problem is sloved" so to speak
the question about the battery app remains...or maybe there is a way to see the battery entire life cycle with a system file.