Database Develop

Could This mess up my phone

Ok so i was updating rom from 1.5 something to the new 1.63. However, my touch screen is broke, and now i cant update because i cant tap the screen. So its stuck at windows mobile center setup. For the time being I switched my sim to older phone. When i put my sim back into the Tilt it goes to the same screen after the G3. Im pretty sure that after i get my screen fixed, it will work, im just wondering if this could cause long term damage i.e. file corruption or something similar?

It seems that your ROM upgrade happened successfully, and you just can't finish the phone setup process (like stylus calibration, time, etc.)?
If that's the case then you should be fine once you get your screen fixed. the state your phone is in now is a fully flashed state.
Also, it isn't clear if you were upgrading an official ROM or if you had Hard-SPL installed to unlock your CID. If you have Hard-SPL it is pretty difficult to mess up the flashing process as you can always get back to the bootloader and try again. It's not impossible to brick it however as some have unfortunately found out.

rovanesyan said:
Ok so i was updating rom from 1.5 something to the new 1.63. However, my touch screen is broke, and now i cant update because i cant tap the screen. So its stuck at windows mobile center setup. For the time being I switched my sim to older phone. When i put my sim back into the Tilt it goes to the same screen after the G3. Im pretty sure that after i get my screen fixed, it will work, im just wondering if this could cause long term damage i.e. file corruption or something similar?
Click to expand...
Click to collapse
you should be able to just force the device to lose power, change the screen when you can and bootup and it should load back to the initial setup screen

You can try some of these suggestions I found in other threads. I've never tried them on the Kaiser though it shouldn't hurt anything:
_____________________________________
connect your ppc to AS then may be 2 different ways
1. install SOTI Pocket Controller-Professional
or
1. open device via as and seek file WELCOME.NOT
2. create empty file with same name
3.overwrite existing file with empty file
_____________________________________
You can also try a program called Remote Screen Alignment
http://www.codefactory.es/downloads/mobile_speak_pocket/release/MSP_RemoteAlignment.zip
http://www.codefactory.es/downloads/mobile_speak_pocket/Remote_ScreenAlignment_Manual.doc

Touchscreen broke, way to bypass welcome screen?

Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?

Try placing your finger on the Android, press the trackball, then lift the finger and press the trackball again
Tommy

IzzeLing said:
Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?
Click to expand...
Click to collapse
Flash the ADP1 software.
Edit: You'd still need touch for that, sorry.

The driver was all wonky, uninstalled, reinstalled, fastboot works now Flashed over to my new G1's state, but forgot to take off the lock screen... Flashing yet again. Everything should be good from here.
Edit: Alright, washing the G1 makes it wacky. The touchscreen works now after restoring it to the new G1's state. Weeeirrrdd.
Edit 2: Anddd now the touchscreen doesn't work :S

well.. when my touchscreen broke i used remote control software to control my ppc from pc .. thats one way to bypass welcome screen, but won't get you much further. I used it for making a backup from my phone.

just leave it off for a while and keep it someplace dry and warm so it can dry out.

You may try to modify build.prop in the rom you flash
ro.setupwizard.mode=DISABLED
I think it will skip the setup

Sorry can't help myself. In the laundry?
I guess I'm wondering what exactly you did. I'm assuming it didn't make it into the dryer....
If you need the data off it, you might be able to ADB pull what you want to keep. If I'm not mistaken, ADB is as close as we have to remote controlling for Android at the moment.
There may be some places around, like PPC Techs, that can do hardware repair. I'm guessing what will happen is you'll occaisionally get it to work for brief stints after reflashing or whatever, but it'll keep conking out until the hardware issue goes away/gets fixed. Hardware issues do that, printers, routers, sometimes PCs.
Not to be a naysayer, but I don't think changing out the software is going to help.

I washed my G1 (was in pocket of jeans under the water for about 90 seconds), and after that I disassembled it to let it dry. It was running fine up to the day I SPL bricked it.

Hey.. i split water on my phone.. it couldnt have been that much but the touch screen wasnt working.. thought if i factory reset it, it may started working..
I dont actually understand all the lingo you guys use.. but any ideas on how i can fix it?
J x
oh the main issue is i cant get past the touch android to continue set up... please i just want my android to work!!! J x

I'm having a similar issue... My phone randomly stopped loading android.process.acore and it's messing with my heart. The touch screen doesn't respond but I can use the trackball to navigate, and every acore process force closes instantly upon activation, such as dialer, contacts, music, etc. The wonderfully helpful people at T-Mobile instructed me to do a factory reset on my G1, and it should fix the problem.
New problem: I can't get past the "Touch me, I'm an Android logo" screen. When I click Emergency Dial, it force closes because the acore processes are still messing up. The intention today was to reload the Cupcake SPL and Radios onto the phone. The issue there is that I can't touch the screen to start the USB connection with my computer.
Anyone have any suggestions aside from paying another $130 bucks??

This will do the trick
google androidscreencast it will allow you to contol your G1 via your PC
...let me know if you have resolved android.process.acore im on the same boat and a wipe and flash has yet to solve it...

same boat for me too! wow, this is three, maybe 4 of us currently experiencing same problem!
I love screen cast. Droid explorer is great too, basically a GUI for adb, and has a plugin for screen cast. Too bad you have to be online though, I'd love to use screencast offline!
I'll update if I figure out the error problem!

Well it looks like a complete wipe and a flash back to non root status is whats gonna take to fix the android.process.acore issue. BUT now w/o root, I cant access the G1 via android screen cast...so im totally stuck on the "Touch Android to begin" screen... sucks to be me lol

I think I'm in the same boat. I didn't know about the screencast application before I did a complete wipe to stock. So I'm stuck at the "touch android" as well. This phones pretty much junk to me right now.

I wonder if any of you have tried restoring your latest back up?

Yes, no help, either on the touchscreen, or the incessant errors. I think there must be some code that checks whether the touchscreen works, and sends back an error if it doesn't. I've tried almost every combination of radios and spls mixed with several different cyanogen roms going back to 4.1, both fresh installs and nand restores.
Currently I'm running the latest cyanogen, radio and hard spl. I get errors often, and can't use the phone / dialer at all without force closing. For now texts and google voice work so I have at least some communication. Ironically, I can't even unroot because none of the spls will flash dreaimg.nbh, but that probelm is in my unresponsive bootloader thread.
Sorry to hear about your predicaments allthrottle and r1ch. Strangely you are right where I'm trying to get, I have warranty coverage to fall back on.

PC crashed during flashing, recovery!

Hello
Ive finally got round to putting new radios and ROM on my diamond, a year after buying. Didnt want to before now incase i cocked it up (theres a lot of things to remember!)
Hard SPL went fine and i was putting the new radio on (1.00.25.05 in this case) when, at about 80% of the way through the install my pc froze (as its having a habit of doing at the most awkward times recently!)
I soft reset the diamond but now its at what i assume is the bootloader screen (?), its got red, green, blue and white bars and various writing, along with a message saying 'Upgrade ROM code error Please try again'
I had a hunt round and found something for another device saying how to get it back by loading a factory ROM through the bootloader menu but i dont know how to do this as i dont have a connection to activesync (phone wont go beyond this screen) etc.
If someone could explain in relatively simple steps it would help!
I should also clarify that the only way i can get this screen off is to remove all power but as soon as i put power back on it loads up direct to this screen again!)

When you device is in bootloader mode, you dont need active sync connection. just run the update utility and it will work without it, as it uses different drivers when connecting.

This turned out to be quite easy actually, i stumbled across the answer somewhere else!
Thanks for the help

Possibly a dead Kaiser, suggestions? (or purchase!)

So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here

Good luck with your phone.. I hope all goes well.. If you find out what the problem was/is, let me know

Hey godefroi, im new to all of this, just bought a messed up tilt from my friend, and i want to know if you could givve me the link for the insturctions to refalsh my tilt

Just hit up AT&T's site (which redirects you to HTC's site) and download the ROM. The file you want is "_ATT Tilt_RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe", which was the latest update for the phone.

Seems it's not fixed. After playing around with it for a couple days, it's back into bootloader and stuck there. Taking out the battery and leaving it for a few hours brings it back for a while, but it seems there's no permanant fix. Next step will be flashing HardSPL and a custom ROM. I'll update when that happens.

awww dang, that sucks. thank you for tellin me. hopin your tilt comes out ok

Did you ever get this resolved?
Hey man did you ever get this fixed? I cant find anything on it.
I can get to a boot loader screen and it shows USB and when I plug it into my computer I hear the sound that it's recognized but my active sync wont connect.
This is what I posted earlier and a moderator killed the post because I didn't spend hours hunting for a solution first before posting. I don't think one exists but if there is I would be glad to know it. I have flashed this phone and my older HTC Wizard dozens of times with no issues so Im not a "noob"
Earlier today I was taking a picture and the screen kind of stuck so I has to soft reboot it.
It didn't come back up. I was left at the rainbow bootloader screen.
I tried holding the camera button down and rebooting but it didn't change anything.
I tried several different combo's of holding keys down and rebooting and it always came back to that bootloader screen.
So the next thing I did was to format my cd card and downloaded KaisDiagTest1.zip and then coppied the KAISDIAG.NBH image file from the zip on to the root of the sd card.
That worked fine and I was left at a screen saying SPL 1.00.OliNex.
Next thing I did is were I think I screwed up. I flashed it with _ATT Tilt_RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign _22.45.88.07_1.27.14.09R2_Ship.exe which is the ROM from the HTC site and I think I was only supose to use a custom ROM and now after it finished flashing the ROM it rebooted and is stuck showing loading ... on the screen.
It goes past the boot loader and is stuck at loading...
Please advise if there is anything I can do.
Cheers,
Chris
godefroi said:
So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here
Click to expand...
Click to collapse

I never did. Every once in a while I can get it reflashed, but inevitably it stops working. Just like yours, I'll sfot reset it and it'll be stuck in bootloader.

Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
5) When it's finished, you will be prompted to press "SEND" to reboot. Press send and it will boot into WM but might take slightly longer.
6) Realign your pointer and tada. It's up and running.
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
I've got to warn you again, this procedure WILL delete all of your internal user storage, hence why I recommend taking out all of the cards before proceeding.

heyadrian said:
Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
Click to expand...
Click to collapse
Nope. Stuck in bootloader is stuck in bootloader. Like, stuck. No, really, it's stuck. Hard-resetting doesn't get it out.
heyadrian said:
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
Click to expand...
Click to collapse
There's no white screen, just bootloader rainbow. Also, there's no chance that I flashed the wrong radio, because this phone has never been flashed with anything but the official ROM. It's never even had a HardSPL flashed on it.

hmmm...now that you mention it has never had a hardSPL, maybe that could be the next step?
i understand that some people may want to keep a "stock" configuration in case waranty needs to be claimed or for any other valid reasons...but if the phone is out of waranty, theres little to lose.
only reason i'm suggesting it is because cmonex has a hardSPL that aims to fix EXACTLY this problem, among others (if i understand your problem and cmonex's fix correctly):
http://forum.xda-developers.com/showthread.php?t=420683
also, this thread links to a page in the wiki about your problem (or something along the same lines):
http://forum.xda-developers.com/showthread.php?t=423486
finally, a collection of hardSPL versions can be found in this "roll up" thread:
http://forum.xda-developers.com/showthread.php?t=498320
i guess you may have already gone through the above mentioned links but if not, they may open up more avenues for troubleshooting or even a permanent resolution.

Nexus One stuck in bootloader

Pardon for the long post but my Nexus One has been out of comission for a few days now so I'll list everything I've tried to make it work in an attempt someone might be able to help me!
Okay, here goes.
A couple days ago I removed the battery on my phone to install an invisible shield. Prior to that I had owned the Nexus One brand new for about a week, had it rooted first thing with the HTC Desire ROM...it was running perfectly
After the installation of the shield was complete I reinserted the battery and hit the power button. The phone booted straight to the bootloader (aka white Robots on Skateboards screen). Funny thing, I was unable to navigate the bootloader (vol up/down) without fiddling with the trackball first by pressing it a couple times) Anyway if I would reboot the phone via bootloader it would return...power off the phone it wouldn't power off just reboot to bootloader.
In this mode I could still use fastboot perfectly and I could enter the restore screen. At this point I kept attempting a reboot and it actually went through at one point and did a full boot to the OS...when I powered down and booted up again however, it was back to the same issue.
On the modaco forum they suggested I flash an alpha2boot.img as the boot image replacement for r21 desire rom as a fix, I tried this method with no success. Since, I've factory reset the phone several times replacing it with various ROMs (currently running stock) none of it fixed the problem.
I also found a way to brute force the phone into safe mode via the fastboot command in prompt: fastboot-windows reboot Using this command the phone successfully reboots, albeit into SAFE MODE. In safe mode the phone works perfectly in every way. I'm just limited in that I can't install any applications and I can't reboot properly (without a computer and command prompt).
I was doing some research on the forums and read the problem could be with the trackball. It would make sense that the phone could only boot to bootloader if the phone had the key press for the trackball triggered somehow. That said, the trackball functions perfectly when operating the phone in safe mode so I doubt this is the issue.
Another idea is that the phone is stuck in some state in the SPL or bootloader...I was wondering if there was anyway to reflash the SPL or bootloader to see if I could resolve the issue that way. (how I would do this, I have no idea)
Any help, suggestions, or advice is very appreciated. As I already unlocked my phone I have a feeling I am out of luck for warranty though I would pay for HTC to repair it if they could. I would prefer to fix it in the software however and not send it in.

Reflash the stock ROM and see if that helps.

mortzz said:
Reflash the stock ROM and see if that helps.
Click to expand...
Click to collapse
He said he's running stock rom...
@ OP, if everything was absolutely perfect before putting the shield on, and everything to crap immediately after finishing the shield, then obviously something went wrong during the install.
The obvious yet unfortunate conclusion is that some solution got inside or something, most likely inside the trackball. =\

Detail exactly what you did when you installed the invisible shield.
Did you get you phone wet at all?

Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?

Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?

So I called it quits on fixing this phone and I'm sending it out to HTC does anyone know how I go about getting restore back to factory settings?

Well you can't relock the bootloader, but if you can use fastboot when your phone's on the booatloader, you can use that to wipe the phone.

Oh wow, sorry to hear it.
If your phone will not boot without the help of fastboot, I wouldn't worry to much about what state Android is in (factory, or custom rom). HTC will attempt to boot the phone, toss it in a bin, and then send you a replacement.
Or that is my assumption anyways. A friend had a similar issue; he unlocked his phone and decided after flashing the Desire rom, that he wanted to stay stock with what came on his Nexus for a while. After flashing the stock images back, his phone looped into bootloader. Off to HTC it went and within a week he had a new phone.
Best of luck!

Sorry to post in such an old thread, but I'm having the exact same issue. Even the part with the invisible shield. Didnt install it myself, the idiot at best buy used too much of the liquid I guess. Did you send yours in or what? I managed to get the phone to work for about a month then it started acting up again today. Wont boot into anything other than safe mode, or fastboot. When it boots into safe mdoe, the phone turns off within a few seconds then goes straight to the boot animation. Would love to get this issue settled, really annoying

i am having same problem. fasboot doesnt even find my phone. i got into safe mode but when i turned it off and back on it went back to fastboot

Same
I am getting the same problem! this really sucks. I think the phone might have gotten a little bit wet, just a few drops of water, and that may have caused this. Should I just call HTC and send it in?
btw, the phone was working fine, even with the very little moisture that was wiped from it. But, I took out the battery when I got home, and this happened.

so is this because on invisibleshield? cuz i just ordered mine today!!

I think its from a little bit of moisture getting into the trackball. I've been doing many "tests" trying to figure out the problem, and my almost final conclusion is the trackball not working good. Most of the time I try to start-up the phone i get into safemode, and once I have gotten into the normal way of things, but the trackball wasn't working well. I think I might have to cal htc, and that sucks because I am going out of the country in 4 days... I won't be able to take my nexus if I can't come up with a way to fix it myself.

I DID IT!
Well, I think I did.
My theory that moisture was the cause of this bootloader stuckness is quite correct. I took a towel, and rubbed the trackball to it for a good 5-10 min, then I did it for another 5-10 min wiping while pressing down on the trackball. I'm very sure that there was some moisture extracted from the device. The trackball is working now. I now do not have to call HTC or send it in.
I kept on booting into fastboot and then recovery, being unable to press buttons, but then I rebooted again into safe mode, where the trackball wasn't working either. I kept moving around the trackball, and then I figured it out, because I felt a slight bit of moisture. Now, it boots up normally, I can access the recovery, and all selection is working.
But, I have a bad feeling that this problem will come back to haunt me. It's good for now though.
Phone is working great as usual.

Can confirm the same issue.
Drop of water on the trackball.
Rebooted into an unresponsive fastboot.
Fastboot reboot command from the computer got me into safemode.
Rolling the trackball while pressed fixed it, the phone boots properly now.