Related
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.
Last night when i connected my phone to the PC through ZUNE software, i was notified i have a software update from HTC. I proceeded with the upgrade, properly following the instructions. Problem was the update stopped at 9/10, even after i waited for 20 minutes still no change (phone is still working that time).
But when i tried to do RESTORE my phone through ZUNE again (i was worried software update was not fully successful) i received an error 80180083 ("the data received was corrupt or not valid") around 70% status. It asked me to disconnect phone. Now the phone is stuck with a picture showing me to connect my phone to the pc. When i do this, it will try to do a restore again but will repeatedly fail the same as before.
Even if i do a HARD reset (power BUTTON + up&down VOLUME), i will still get the same screen showing me the picture to connect my phone to the PC. Nothing seems to correct this problem (i consulted Microsoft Answers website for this, no clear solution so far and some people submitted their phones to HTC).
Anybody recently encountered this? Let me know how you resolved this problem...
Thanks!
bluegreenwhite said:
Last night when i connected my phone to the PC through ZUNE software, i was notified i have a software update from HTC. I proceeded with the upgrade, properly following the instructions. Problem was the update stopped at 9/10, even after i waited for 20 minutes still no change (phone is still working that time).
But when i tried to do RESTORE my phone through ZUNE again (i was worried software update was not fully successful) i received an error 80180083 ("the data received was corrupt or not valid") around 70% status. It asked me to disconnect phone. Now the phone is stuck with a picture showing me to connect my phone to the pc. When i do this, it will try to do a restore again but will repeatedly fail the same as before.
Even if i do a HARD reset (power BUTTON + up&down VOLUME), i will still get the same screen showing me the picture to connect my phone to the PC. Nothing seems to correct this problem (i consulted Microsoft Answers website for this, no clear solution so far and some people submitted their phones to HTC).
Anybody recently encountered this? Let me know how you resolved this problem...
Thanks!
Click to expand...
Click to collapse
Just found this link hope its of some help to you
http://support.microsoft.com/kb/2484484
Thanks for your help but I just sent in my phone for repair. Apparently the motherboard was replaced.
When i redid my update after getting back my phone, it was definintely faster. The update was succesful!
The major difference is the amount of memory space on my phone - previously my remaining space was ard 600mb (lots of music) compared to post repair (14G). Maybe that made my previous update difficult. I think it's best to remove files before doing the update, esp when it nearing full.
Just my 2 cents...
Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus
lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.
Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:
I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!
Phone starts with moving halo and "wissen"... "Is it wiping my phone?"
Just now I took my Nexus 6 out of my pocket because it was very warm.
The screen was all black with in the middle a big Halo moving with the disturbing message "wissen" beneath it.
"wissen" is Dutch for wiping, deleting or removing...
Turning the phone off is possible by holding down the power button for 6 seconds, but then it turns on again after 3 seconds showing that same screen again.
After some fiddling I was able to find a method to turn it off.
I can start the phone by holding down the power button and the volume button (down) which will start the recovery program.
There I can turn it off.
Although I have unlocked the phone and ran modded firmwares I switched to standard factory Nexus 2 years ago and haven't had a rooted phone for all that time.
Recently I installed the 7.1 OTA updated.
I'm afraid this is something like a remote wipe.
It also doesn't ask me to give my PIN which is normal for it to do.
What is happening?
Some more info: Yesterday I bought the "AIO All-in-one Toolbox " after using the free one for 3 weeks. Could that be involved?
It may be formatting and encrypting your data partition.
Yes, but why?
It just went into my pocket this morning....
I came one step further.
As I was still able to get it into fastboot loader I exited with "volume up"
Then it went into an almost normal boot. This didn't require the pin it normally needed.
The device went into a full factory reset.
I thought I would be up and running fast, but after entering my new gmail account/password I got the message that I needed to wait another 24 hours because I did a password reset.
I did this password reset of my Google account out of safety. Now I'm being punished for this....
Luckily I have a spare Motorola G3 with its own SIM, so I can at least use my phone.
I can't even use my Nexus as a phone nor can I go to settings. Maybe if use another Google-account.
Did some more research...
The last Exchange sync was while cycling to work.
Didn't use the phone then nor later.
Because my Google-account is locked I can't do anything with my Phone (not even phone), so I decided to flash an alternate rom on it.
I flashed lineagos and also rooted the device again.
Although I did root my Nexus 6 in the beginning this is the first custom ROM I have on it. I still need to install gapps.
Now I can start using my Titaniumbackup again that I bought several years ago.
I still have no idea how it could have gone into wiping. I put the phone in my pocket while it was screenlocked. The device needs a pincode to unlock.....
I am still unable to use Google Apps. I can run the app, but it doesn't let me install apps.
On the stock rom I was just stuck (stuck rom, haha)..... at the installation screen unable to even make a phone call....
Does someone have any idea???
frater said:
...
Does someone have any idea???
Click to expand...
Click to collapse
My idea is that you have the N6 unprotected in your pocket. Moving or cycling caused activation of a factory reset.
I'm just putting this here to hopefully help someone else not lose their mind after a bad December update. I just got my OTA for my 4XL on VZW about 40 minutes ago. MY PHONE JUST BOOTED.
After applying the update and the phone restarting, per usual, I noticed the lock screen was super sluggish and intermittently not responsive. More concerning still, it said my PIN was invalid, which I KNOW it wasn't. So.... I rebooted. Just held power for a second, and clicked Restart in the menu. That may have been where I went wrong. For the next 25 or so minutes, I had nothing but a black screen. No sounds, no vibrations, nothing registered when plugging into my PC. Even holding the power key for 30+ seconds or attempting safe mode or bootloader did not work.
In retrospect, I am now considering that even though the phone initially rebooted and was at the lock screen, Android may still have been in the process of updating which could cause the slow down and maybe even the invalid pin. Mostly, I think that may be what happened when I rebooted the phone, I basically did it in the middle of it finalizing the update which very well could have caused all sorts of issues.
TLDR: I don't think I did anything to fix it, I gave up after 1000 times of trying and set it down, then about 5 minutes later (off the charger) it just started booting up. So don't throw your phone at the wall if it doesn't turn on right away after the update.
lessthanzach said:
I'm just putting this here to hopefully help someone else not lose their mind after a bad December update. I just got my OTA for my 4XL on VZW about 40 minutes ago. MY PHONE JUST BOOTED.
After applying the update and the phone restarting, per usual, I noticed the lock screen was super sluggish and intermittently not responsive. More concerning still, it said my PIN was invalid, which I KNOW it wasn't. So.... I rebooted. Just held power for a second, and clicked Restart in the menu. That may have been where I went wrong. For the next 25 or so minutes, I had nothing but a black screen. No sounds, no vibrations, nothing registered when plugging into my PC. Even holding the power key for 30+ seconds or attempting safe mode or bootloader did not work.
In retrospect, I am now considering that even though the phone initially rebooted and was at the lock screen, Android may still have been in the process of updating which could cause the slow down and maybe even the invalid pin. Mostly, I think that may be what happened when I rebooted the phone, I basically did it in the middle of it finalizing the update which very well could have caused all sorts of issues.
TLDR: I don't think I did anything to fix it, I gave up after 1000 times of trying and set it down, then about 5 minutes later (off the charger) it just started booting up. So don't throw your phone at the wall if it doesn't turn on right away after the update.
Click to expand...
Click to collapse
Were you rooted ?
reboot took longer than normal, should have left it
factory reset will clear up everything lol
prgopala said:
Were you rooted ?
Click to expand...
Click to collapse
I am not rooted. Gave up my rooting back when it made Google pay and Pokemon Go a complete ***** to use, even with magisk. So I've left this stock out of the box.
lessthanzach said:
I'm just putting this here to hopefully help someone else not lose their mind after a bad December update. I just got my OTA for my 4XL on VZW about 40 minutes ago. MY PHONE JUST BOOTED.
After applying the update and the phone restarting, per usual, I noticed the lock screen was super sluggish and intermittently not responsive. More concerning still, it said my PIN was invalid, which I KNOW it wasn't. So.... I rebooted. Just held power for a second, and clicked Restart in the menu. That may have been where I went wrong. For the next 25 or so minutes, I had nothing but a black screen. No sounds, no vibrations, nothing registered when plugging into my PC. Even holding the power key for 30+ seconds or attempting safe mode or bootloader did not work.
In retrospect, I am now considering that even though the phone initially rebooted and was at the lock screen, Android may still have been in the process of updating which could cause the slow down and maybe even the invalid pin. Mostly, I think that may be what happened when I rebooted the phone, I basically did it in the middle of it finalizing the update which very well could have caused all sorts of issues.
TLDR: I don't think I did anything to fix it, I gave up after 1000 times of trying and set it down, then about 5 minutes later (off the charger) it just started booting up. So don't throw your phone at the wall if it doesn't turn on right away after the update.
Click to expand...
Click to collapse
Hey got the same issue as you. Either it's stuck on a black screen (adb works), either it hangs on Applying update when starting the phone. Can't seem to get past this crap... I'm trying with a patched magisk image btw, not sure if it's the issue, I already applied the magisk adb commande in order to remove the magisk modules but to no avail.