Hi Forum,
I've read about 50 responses on fixing a bricked HTC Desire Z, but unfortunately, nothig has solved my problem as yet, so I need to ask for considered advice:
I have an unrooted bog-standard HTC Desire Z.
This morning, it started updating applications, and I foolishly hit the button to 'Update All' applications. This was where it started to go wrong and it seemed to jam up.
After about 30 minutes, it was still completely locked up, and I had to take the battery out. When the battery was put back in, it just went to the HTC logo, and wouldn't go past it.
Having spent the day googling, I got to the boot screen, which reads:
vision pvt ship s-on
hboot-0.85.0013
radio-26.10.04.03M
eMMC-boot
Apr 11 2011,23:36:27
The options below this were 'Fastboot', 'Recovery', 'Restore Factory Settings', and another. (Sorry, I forget).
Recovery pauses for a few seconds, then shows an HTC logo, then a green and black icon with arrows circling a phone, then it turns off, buzzes 6-7 times, and locks up with no lights on. To get any more action, I had to take the battery out.
Fastboot provides some other options, but none of them seem to actually do anything other than starting from the point of power-on with volume down again.
Restore Factory Settings locks up for over an hour, and I have to take the battery out again.
The online guides seem to suggest creating a Goldcard, but I can't see how I can do this without being able to boot up the phone
Other guides suggest usind ADB. I've installed this, but to use it, I need to enable USB debugging on the phone. Which I can't do without being able to boot up the phone.
I've tried putting a PC10img.zip file on the SD card, which it does read, and verifies,but having seemingly processed this file, it doesn't change any of the other behaviour.
I tried to run an RUU, which appeared to work for a while. (Downgrading from 2.42.405.2 to a lower ROM) but this failed about halfway through with a 'USB Error' and no behaviour has changed.
I'm getting a little frustrated. Does anyone have any ideas that I can try?
Please bear in mind, I do not have the ability to boot the phone to turn on USB debugging, etc.
Thanks,
Ian.
Wrong section. Try Desire Z forum. Different device, different solutions (sometimes)
---------- Post added at 08:53 PM ---------- Previous post was at 08:51 PM ----------
tutorial for goldcard is here.. skip the part where they get the CID wit hthe phone and use this (copy with no spaces, commas) and use an SD USB adapter, then follow the tut.
Then boot into fastboot mode, plug in via USB and run a RUU.. think this is the newest WWE one
Thanks for your help.
Do I still need the goldcard to install the stock RUU?
Regards,
Ian.
if you have the branded RUU for your network then no. If you want to use the one I posted then yes.
For chris sake, STOP FEEDING N00BS!
Terepin said:
For chris sake, STOP FEEDING N00BS!
Click to expand...
Click to collapse
LOL I can't help it... I'm like Sherlock to solving cases with helping people with their phones :L
still... sometimes it feels like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
I am trying to run AlphaRev-X on a HTC Desire (CDMA) running HBOOT 1.06 but all I am getting it "Waiting for device..."
As far as I am aware, all drivers are installed perfectly fine.
USB Debugging is enabled.
Any ideas?
Exit HTC Sync? Just a reminder, as I've forgotten that a couple times, with similar results..
mmceorange said:
Exit HTC Sync? Just a reminder, as I've forgotten that a couple times, with similar results..
Click to expand...
Click to collapse
I don't have HTC Sync installed on the PC, so I don't think it could be that.
Could it be enabled somewhere on the phone? I'm currently in Charge Only mode.
Is this to get s-off?
What happens after a long time of 'waiting for device...'?
Not quite sure which stage you're at, but when I used AlphaRev I realised 2 things...
1. I had to 're-select' the phone each time it booted (but I was using a VM)
2. Right at the start when AlphaRev is trying to find the phone details, a message asking for super user permissions appeared on my phone - you need to accept it.
Also, you are using a HTC Desire, so you should be able to use AlphaRev1.8 (http://alpharev.nl/). I believe AlphaRev-X is for other devices? (correct me if i'm wrong)
pyko said:
Is this to get s-off?
What happens after a long time of 'waiting for device...'?
Not quite sure which stage you're at, but when I used AlphaRev I realised 2 things...
1. I had to 're-select' the phone each time it booted (but I was using a VM)
2. Right at the start when AlphaRev is trying to find the phone details, a message asking for super user permissions appeared on my phone - you need to accept it.
Also, you are using a HTC Desire, so you should be able to use AlphaRev1.8 (http://alpharev.nl/). I believe AlphaRev-X is for other devices? (correct me if i'm wrong)
Click to expand...
Click to collapse
There is no mention of it working for the CDMA version of the Desire on that page
I guess hboot drivers were installed correctly?
My only idea is to try this:
Install htc sync. Now uninstall only htc sync (not the drivers) and reboot computer. Boot your phone in fastboot mode, start alpharev x and connect your phone to your computer.
MatDrOiD said:
I guess hboot drivers were installed correctly?
My only idea is to try this:
Install htc sync. Now uninstall only htc sync (not the drivers) and reboot computer. Boot your phone in fastboot mode, start alpharev x and connect your phone to your computer.
Click to expand...
Click to collapse
Installing HTC Sync worked, although now it's getting stuck on Beta key accepted - thank you for participating!
This is all rather frustrating
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
King Mustard said:
Installing HTC Sync worked, although now it's getting stuck on Beta key accepted - thank you for participating!
This is all rather frustrating
Click to expand...
Click to collapse
Did you uninstall htc sync and rebooted your computer?
MatDrOiD said:
Did you uninstall htc sync and rebooted your computer?
Click to expand...
Click to collapse
I'm sure an idiot, I skipped over that part.
Many thanks!
Sorry for my enthusiasm, but here is my problem:
I want to install Android Revolution on my HTC DHD.
I've done all these steps:
- Successfully created a GoldCard
- Successfully dowgraded from 2.3.3 to 1.32
- Successfully permrooted via Visionary+
- Successfully Radio S-OFFed, SuperCID + SimUnlock via this tool
- Now failed on ENG S-OFF via this tool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I opened it as Admin, I am on a Radio-S-OFFed and Permrooted Device with Software <1.7x, I checked "Yes, I have Radio-S-OFF" (or how it was called), I connected my phone via charge only, I enabled USB Debugging, I have all adb drivers (HTC sync), I accepted the superuser request on my phone and I so I have done EVERYTHING mentioned in the threads, which I Have read 2 times before doing it, but now this stupid error and I don't know how to proceed.
I hope you guys can help me. I did of course not reboot my phone, and I am continuosly charging it right now to prevent running out of battery.
EDIT UPDATE: I tried the tool now without the box checked, gives me "connection error" (yes I again accepted superuser request)
Ok, ok nevermind guys, figured it out myself:
Thanks to ratman33 and myself for trying out weird thingds
Ratman33 said:
I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!
Click to expand...
Click to collapse
But this alone did not work for me. I needed to go to Menu>Settings>Applications and then check "Fastboot" so that it's enabled. Then disconnect your phone from the PC and WAIT min. 5 seconds. Then connect it again and run the tool, and it gives you success message!
But: Can I now be sure everything went right?
Alskarl said:
Ok, ok nevermind guys, figured it out myself:
Thanks to ratman33 and myself for trying out weird thingds
But this alone did not work for me. I needed to go to Menu>Settings>Applications and then check "Fastboot" so that it's enabled. Then disconnect your phone from the PC and WAIT min. 5 seconds. Then connect it again and run the tool, and it gives you success message!
But: Can I now be sure everything went right?
Click to expand...
Click to collapse
It should be. I guess there is only one way to find out, reboot in bootloader and see the results.
or you could have tried with your Wi-fi turned on and connected to a network.....that's the way it worked for me
Dear XDA Community,
This post will be as detailed as possible for those who enjoy detail.
It’s about the problems my EVO has been experiencing over the past 3 months and, after trying to fix the problems though IRC it seems that the attention should be brought to the forums for a larger audience. It was 3 months ago when I flashed a rom ( cannot remember the rom ) and my EVO took a turn for the worst.
What Happened :
When the rom was flashed and booted for the first time everything seemed normal but, the rom started to freeze at random. At first I though it was a normal process due to new ROM’s installs but, it kept repeating it over and over until it went into a boot loop syndrome.
Prior to these problems I did my daily clean/wipe dalvik rituals for ROM consumptions.
After 15 - 30 boot-loops my battery dies and the crusade begins.
I begin looking for another ROM to flash, to rid the sickness the previous ROM infected my EVO with. I installed my favorite (SalvageMod) and, the problems began to show. Salvage installed perfectly fine (as always) but, my phone started to lag, the speed was reduced to about 35 - 50%. It’s noticeable big time. The camera stopped working and everything seemed to be falling apart.
(RECENT)In panic I started looking for ways to RUU so I can avoid any other problems. This is when I noticed that usb was not accessible. I couldn’t mount my device; [CLICK HERE FOR VIDEO], so I used a SD card reader to RUU my phone and get it back to stock.
Phone is back on stock settings but, no root and, without usb support revolutionary.io is lightyears ahead of my time.
Problems :
Not mountable through usb cable [SD Card Reader option / Software Error]
System lag noticeable slower (BestBuy rep even confirmed its unresponsiveness)
Device will not charge when on [Either mount / Software Error],
Camera problems.
[Click Here For Second Video]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So can you guys help a member get his EVO back in business, my wallet would greatly appreciate it.
Thanks,
samthewildone
Aspiring Mathematician
Well, the easy way out is that now that you're back on stock and a rep has agreed the phone is not working properly and you have no USB, trade it in
I would right click on that device and uninstall the drivers. then hook the phone up to the PC and see if it automatically installs the correct drivers or find better drivers.
This may have been covered, and it looks like there's a lot more going on then just drive issues, but to get this phone into a state in which you can root it and wipe it again, you need to eliminate that variable.
Not saying that the USB drivers are even an issue, but its something worth exploring first and foremost.
Tried that, as in my thread. I uninstalled and reinstalled drivers and, it just keeps showing what that picture shows above. The phone isn't damaged but, the software is borked due to a bad bad kernel or ROM flash.
Not a solution to your problem, but if you are still s-off then you don't need Revolutionary. You can put a PC36IMG of a (reliable, ie Amon Ra) recovery on your SD card. From there you can wipe thoroughly and try flashing something else.
Unfortunately it seems like some sort of hardware failure, so the only fix could be getting a replacement.
Supersonic Evo 4G | MIUI | Tapatalk
Seems like you've gone through the same steps I would've gone through to fix it. Apart from the possible driver issue the phone should still charge when plugged into a wall charger. The fact that it doesn't, in tandem with the inability to access USB via computer, tells me that most likely you've got a hardware failure. Take it to Sprint and get a replacement. Problem solved.
TL;DR: Really three questions
What kind of effort can/should we expect from Google Support?
Is there an escalation support path for real troubleshooting?
What's the best course of action to attempt to determine root cause?
The Setup
While driving to work this morning my stock Pixel 2 XL (locked, not rooted etc.) entered a boot loop then settled on this error (image):
Code:
Android Recovery
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device
I couldn't do much since I was driving but I selected 'Try again' a number of times when traffic stopped before giving up.
When I arrived at work I continued fiddling with it for a few hours, select 'Try again', power off, power on, fastboot etc.
Although debugging was enabled prior, could only see a device in fastboot or when in adb sideload mode.
When I attempted to go into recovery mode it would just take me back to the same screen.
I just assumed I'd have to wipe and start over
About 2 hours ago I was getting ready to factory reset/wipe the phone but thought I'd try fidgeting once more like I had been doing all day.
I don't know what I did but it booted to a screen displaying this error:
Code:
No valid operating system could be found.
The device will not boot.
Visit this link on another device
g.co/ABH
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then the phone turned off.
I turned it back on, and I don't think I did anything differently, and suddenly it booted normally.
The only unusual thing I saw was a notification stating that Android was finishing up system updates - or something to that effect.
With the phone up, I backed up what little data had not yet been backed up, booted into safe mode then booted back into normal mode.
So far so good...?
My Complaint
I contacted Google support earlier in the day and the experience was just sad.
The person said that I would need to factory reset my phone.
But then quickly said that before doing so I would need to backup my data.
So I asked "How?" and they said "plug it into your machine and you can see it on your computer"
I went along with their script, specifically asking for detailed step by step instructions on what to do, how to do it and what to look for.
When I said it didn't work they said I would have to take it to a repair center first to get it repaired then once fixed I could back it up then perform the factory reset.
*smh*
Later, about 2.5 hours ago now, once the phone came back up, I backed up what little data needed backing up and contacted support a second time.
This time, the person said: "Now, if we need to restart the phone and check if the boot looping is triggered or not. If it does, then we need to do some troubleshooting steps here."
So I naturally asked "What are the troubleshooting steps if it enters into that state again?" but they couldn't provide any.
I just want to know root cause. Since this was an OS boot problem, surely there's a log somewhere that might reveal what happened or at the very least provide a clue. Right?
I am helping someone with this phone, so I don't have all the details, but I know the phone was rooted and most likely it was running stock Android 10. It had been working fine until a factory reset (from Android settings I am assuming) was done on it.
1. Now when it turned on, it displays the "Bootloader unlocked" warning:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. After the message, it goes to the Google logo for a second and then to the TEAMWIN splash screen, and it just stays there. I have to long-press the power button to power it off.
3. I can get into the bootloader using the power and volume-down keys, and the "Barcodes", "Restart bootloader" and "Power off" option work, but "Start" and "Recovery mode" just take me back to step 1 and then 2.
So, I cannot get into "Recovery mode". I have also connected the phone to my pc (Ubuntu), but the OS does not detect it, so I cannot use fastboot either.
Any ideas on how to fix this?
If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....
73sydney said:
If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....
Click to expand...
Click to collapse
After connecting a working and identical phone to my PC, I found out that the reason my PC didn't detect this phone was that the USB port on phone was dirty and the connector didn't go all the way in.
After I cleaned the USB port I was able to flash the stock ROM to it. I was getting an error mid-way through, so I removed the "-w" as per your advice, tried again and it worked. The phone works now. Thank you 73sydenay!
I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.
droidmart said:
I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.
Click to expand...
Click to collapse
Hi,
You could press edit > advanced and edit your title with:
[SOLVED] Pixel 2 XL (rooted) bootlooping to TEAMWIN splash after factory reset
Cheers...
Sébastien.