Related
Hi, i've been using LeeDroid for a few months now and all has been well, however yesterday my Desire turned itself off and now won't come back on. Each time i try and power it up it freezes at the Alpharev S-Off screen. I went into the menu's with volume down + power, but i can't get into my recovery - it takes me to the same frozen screen as does trying to reboot etc. And i don't think it's being recognized by usb either. So i really don't know what to do now.. is my phone bricked? I was a complete noob before rooting and flashing a custom rom before, so now that i've hit a problem i'm clueless all over again. Any help would be greatly appreciated
can you use fastboot? If so just flash a new recovery and all should be fine... chill out it can be fixed
What would i need for that? That's going into new territory
j3nni said:
What would i need for that? That's going into new territory
Click to expand...
Click to collapse
Can you access recovery? If no can you access bootloader (vol down + power on)
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
j3nni said:
I can get onto the menu with the options 'fastboot, recovery, clear storage and simlock' if that's what you mean? The recovery option takes me back to my frozen alpharev screen, but i can get onto fastboot and after reading around i can get my pc to recognize it from fastboot usb from my pc using cmd.. Am i going the right direction at all? Eek. What i don't get now is the recovery image i'm supposed to use
Click to expand...
Click to collapse
Use amon_RA ... Download and flash onto ur phone and ur phone should be fixed
Plenty of guides around man, good way of learning fastboot
to use fastboot you need to download several things. Instead of using fastboot with cmd, I'd just recommend using fastboot commander, which does the job for you. In order to use that however, you will need the adb drivers, and Java SDK.
Once you've got all that, simply boot into fastboot, run "fastboot commander.exe", go into the "misc" tab, wipe Recovery, system, cache, boot, and userdata. Once you've done that download recovery, navigate to the "Hboot, radio & Rec" tab on fastboot commander, select recovery, find the recovery.img you just downloaded, and flash it. Once you've done that just boot into recovery and install any ROM you want.
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
j3nni said:
Thanks for the replies guys. I did what you said to do (using fastboot commander), and when trying to boot into recovery to install my ROM it froze again at the alpharev screen. I'm stuck again now. When the files show up as you turn on into fastboot, i'm getting this..
SD Checking...
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nhh]
No Image or Wrong Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99IMG.nhh]
No Image or Wrong Image!it's saying my pb****.img files arn't found
which i gather can be normal. Other than that i'm stumped again
Click to expand...
Click to collapse
try do a full wipe of everything like I've mentioned before and then a different HBOOT
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
j3nni said:
Okiedoke, how do i use a different hboot? And where do i find one from? At the moment i believe it's 0.93
Click to expand...
Click to collapse
www.alpharev.nl download a HBOOT and flash it through fastboot. Just make sure to check MD5 (you need a MD5 utility AFAIK)
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
j3nni said:
I'm not sure which one is the right one for my ROM, i'm using LeeDroid.. Sorry for all the questions!
Click to expand...
Click to collapse
For any sense UI ROMs you would use the Sense HBOOT, remember to nandroid backup before you do so! because you might find that you get a bootloop after flashing the HBOOT.
And don't worry about asking questions! it's what we're all here for.
By the way if you don't know what different HBOOTs do: they change the partition sizes for /system /cache and /data. So by using a different HBOOT instead of the stock one you may get more storage for apps etc. if you choose one with a larger /data partition.... if that makes sense
Ok the sense one it is =)
Ah i see! Thanks for explaining cos underneath the nerd in me would have been wondering what it did lol.
Not sure how to get a nandroid done when i can't get into recovery though
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
j3nni said:
I still havn't got anywhere with my problem, if anyone could advise me further i'd really appreciate it, as this is really stressing me out now.
The only screen i can still ever see is a frozen alpharev screen, and i still can't enter recovery. I've cleared everything using fastboot commander and flashed a new recovery which did nothing. Then i took the next advice and flashed a new hboot. The hboot has changed on my hboot menu (vol down + power) but still goes to the frozen alpharev screen when i try to go to recovery or turn the phone on. I then flashed a LeeDroid rom, which came up with an error at the end of it..
"sending 'zip' (173060 KB)... OKAY [ 23.469s]
writing 'zip'... FAILED (remote: not allowed)"
And that's as far as i've got.
Reading further i've been trying to work out how to flash a stock ruu to see if that works. However my phone was a branded Orange UK phone before so there is no ruu for that. So my question is, bearing in mind i can't get into the phone at all, how can i go about downgrading the hboot and installing a htc stock ruu. Can anyone point me to the right files i would need. I really don't know what i'm doing and i think the amount of searching i've been doing is just confusing me further
Click to expand...
Click to collapse
Hi.
As I can see the only way to restore is using a RUU to go back to stock then root and S-Off the phone again.
First: Preparation.
1. If you have a custom HBOOT (e.g.: 6.93.0001) you need first to flash the HBOOT Downgrader (found on alpharev site), then flash the RUU.
2. You will gonna need a Gold Card if your phone was branded.
Second: Starting
1. Make your Gold Card using someone's else phone (it has to be running Android) - the Gold Card is unique per SD Card, not per phone.
2. Use this tool to make the Gold Card: HERE
3. Guide how to make a Gold Card in Linux: HERE
4. get the latest RUU WWE 2.29.405.5. Extract the PB99IMG.zip file from the RUU: here it is how: http://forum.xda-developers.com/showthread.php?t=880268 -2nd post.
5. Reboot in bootloader (Volume-Down + Power)
7. Select fastboot
8. Flash the HBOOT Downgrader (don't forget to check the MD5 of the file you have downloaded from alpharev)
9. Extract the PB99IMG.zip and put it on root of SD Card.
10. Reboot in bootloader (scroll to REBOOT and select)
11. It will automatically load the img and ask you if you want to install
12. Check Yes and follow onscreen progress.
13. Wait untill it finnishes
14. I think it will reboot itself, if not scroll down to the Reboot obtion and press Power button to select.
IMPORTANT WARNING!!!
droidzone said:
Whatever you do, DO NOT turn off the device manually unless the software tells you to. If something goes wrong, dont switch off phone. Keep the phone on while trying a solution. Newer RUUs dont usually wreck a phone, and with a goldcard, you can always recover. But, the flash SHOULD NOT be interrupted by switching off or disconnecting the cable.
Always start with a battery with >50% power (full recommended).
Click to expand...
Click to collapse
Or if you want to go to stock and it is an unbranded phone you can just run ur ruu when the phone is in fastboot
Sent from my HTC Desire using XDA App
Think i may be the happiest girl in the world today lol i finally got it all fixed. I had a bit of trouble making the goldcard as at first my sd card kept saying it needed to be reformatted after, but after formatting it with SD Formatter program rather than Vista's own, it worked. All the rest went without a hitch. Now just gotta root, s-off and grab my new ROM and this past week can all get forgotten about =)
Thankyou so much to everyone that helped!
Incase anyone does read this far, is the procedure still the same as when i first used it back in April.. from here? http://forum.xda-developers.com/showthread.php?t=1016084
It is still the same.
If you like sense -
http://forum.xda-developers.com/showthread.php?t=1054435
░█░ [ROM][28/06] ✰.Reflex S v2.1.7 Gingerbread 2.3.3· ░█░ · |SenseGingerB 2.1+3.0|
You might like it...
need to exchange the phone, so i need to revert the phone back to fully stock. phone currently has cyanogenmod 7. just want to make sure i'm doing this right...
so as i understand it, following the g2\desire z wiki, i can just use clockword mod recovery to install the stock image and flash it with CWM right, via the "flash alternate recovery" option?
and more importantly, the wiki says that to install the stock rom, i need to make sure my main version is not higher than 1.19.531.1, but i was not able to find my version. i booted into hboot, which number is that? and regardless, if i use misc_version to set the main version, does it matter what version i have? also, i used gfree to root before, and still have the original partition 7 saved on my pc, if that matters. thanks
Here follow my guide, it describes how to return to stock. Only change you might want to make is use a proper stock rom to flash instead of my modded ones.
-Nipqer
thanks! how do you flash stock recovery???
i did fastboot recovery recovery.img and it said:
"sending 'recovery' (4652 KB)... OKAY [1.021 S]
writing 'recovery'... FAILED <remote: not allowed>
finished. total time : 1.031s
Fastboot flash recovery only works on eng hboots or htcdev unlocked hboots.
-Nipqer
Sent from my HTC Vision using xda premium
so then what can i do? thanks again
Use the xda wiki to get full root. That will give you recovery in the process
-Nipqer
Sent from my HTC Vision using xda premium
Similar-sounding problem
I've attempted to install ClockworkMod and CM7 on my G2 with Gingerbread 2.3.4, and have wound up putting it in a semi-bricked state. (Whole process went fine on my old G2 last year, but had to return that due to a wifi problem). Here's what I've done so far:
1. Started the root/CW process (http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Rooting). Once I got to the psneuter step, I got "Failed to set prot mask (innappropriate ioctl for device)", which I figured meant I needed to do the downgrade, since that was the only difference I could see between my new G2 and the old one (which had Froyo when I went through this process).
2. Downgraded to Froyo (http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Firmware_Downgrade_(Froyo). That seemed to go just fine.
3. Re-did the root/CW process. That also seemed to go just fine, until I rebooted into CW, at which point I got:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
At this point, attempting to select any of the items in the CW menu just showed the hat-with-ring logo, no text. I figured I must have screwed something up, and decided I'd best roll back to stock (I'd just done that on my old G2, so I could send it in, and that process had also worked fine).
4. Rolled back to the original PC10IMG.zip (http://theunlockr.com/2010/12/01/how-to-unroot-the-t-mobile-g2-htc-vision/ but without the OTA part). When I rebooted, I got the green-on-white "HTC" screen, for at least 10 minutes. Retried several times. Using power-volumedown, I could still get into recovery, which was still Clockwork, but with the same errors as in step 3. I could still connect via ADB (when in Clockwork) and get a root shell with that, at this point.
5. Big goof: I decided I should rollback to stock recovery. Did that using the http://forum.xda-developers.com/showthread.php?t=834545 guide. Rebooted. Phone still sticks at the initial HTC screen, forever. Using power-volumedown, I can get to the screen whose name I do not know, the one that's white with three skateboarding androids at the bottom, and the "Fastboot, Recovery, Factory Reset, Simlock, System Info, Image CRC" menu.
6. Recovery now takes me to what I presume is stock recovery, which has a "E:Can't mount /cache/recovery/command" message at the bottom of the screen. Menu is "Reboot system now, Apply sdcard:update.zip, Wipe data/factory reset, Wipe cache partition." Factory reset and wiping the cache partition, then rebooting, still results in the eternal HTC screen.
7. If I do reboot and do power-volumedown to get back to the three-skateboards screen (someone please tell me the actual name, so that I can sound like less of an idiot), I can select fastboot, and then connect via fastboot-windows. I haven't done anything with that yet, however, as I figured I've gone too far already without stopping to ask for help, and don't want to cut myself from off from fastboot the way I cut myself off from adb.
Right now, I just want to get the phone to a usable state again. Not expecting any hand-holding, but I'd appreciating someone pointing me to the start of the path back.
...the three skateboards screen is called bootloader
is it still s-off and what hboot-number does it show?
At the top of the bootloader (thanks!) screen, I get:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1010000)
MICROP-0425
RADIO-26.01.00.17_M2
eMMC-boot
Sep 8 2010, 15:56:38
ok, this looks good.
first i would flash a recovery.img through fastboot (you do have eng hboot so it should work)
download the 3.0.2.4 image from here and put it into your platform tool folder:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
then connect your phone to pc go to your platform tool folder and type:
"fastboot flash recovery recovery.img"
enter recovery and wipe data&cache&dalvik cache afterwards flash a new rom...
if you get the same error as before, have a look here:
http://forum.xda-developers.com/showthread.php?t=1448441
Thanks immensely. Going to try this in the morning (hitting 2am for me). Just one final question: at the "flash a new ROM" step, should that be the stock T-Mobile ROM, or does it matter? My original intent was to install CM, so if it makes no difference I'll go with that, but right now I'd be happy just to have a phone that boots, so if I need to I'll use stock and count my blessings.
emamid said:
Thanks immensely. Going to try this in the morning (hitting 2am for me). Just one final question: at the "flash a new ROM" step, should that be the stock T-Mobile ROM, or does it matter? My original intent was to install CM, so if it makes no difference I'll go with that, but right now I'd be happy just to have a phone that boots, so if I need to I'll use stock and count my blessings.
Click to expand...
Click to collapse
no do not flash a stock rom (you will get in troubles doing this with a rooted phone and s-off)... cm7 is a good way to go
if you don´t mind pls hit the thanks button
damnit... now i can't seem to downgrade the new phone, with the 1.22 firmware. following the cyanogenmod wiki, at the step where you enter:
Code:
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
adb shell
i get a whole bunch of:
Code:
An error occurred while running the exploit (-1) (errno: 25)
Scanning region fffe0000...
An error occurred while running the exploit (-1) (errno: 25)
adb shell
adb: permission denied
$
help, what am i doing wrong?
first of all you do have gingerbread (2.3+)? because you asked this in a different thread...
and you did chmod it as described in the guide?
hoffmas said:
first of all you do have gingerbread (2.3+)? because you asked this in a different thread...
and you did chmod it as described in the guide?
Click to expand...
Click to collapse
nope, it's android version 2.2, but the build number is 1.22.531.8, so that means i have to downgrade it, right?
you need a different guide for a froyo downgrade - try this guide:
http://forum.xda-developers.com/showthread.php?t=905261
i´m not sure if it works... other thing you could do is make a official update to gingerbread and then downgrade with the guide you used before.
hoffmas said:
if you don´t mind pls hit the thanks button
Click to expand...
Click to collapse
Weird, I had to open the page in Firefox rather than Chrome for the "Thanks" button to show up.
---------- Post added at 03:03 PM ---------- Previous post was at 02:43 PM ----------
hoffmas said:
ok, this looks good.
first i would flash a recovery.img through fastboot (you do have eng hboot so it should work)
download the 3.0.2.4 image from here and put it into your platform tool folder:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
then connect your phone to pc go to your platform tool folder and type:
"fastboot flash recovery recovery.img"
enter recovery and wipe data&cache&dalvik cache afterwards flash a new rom...
if you get the same error as before, have a look here:
http://forum.xda-developers.com/showthread.php?t=1448441
Click to expand...
Click to collapse
Installed clockwork, and can get to it through the bootloader. However, when I try to wipe the cache -- or select any of the other menu items -- I just get the hat-and-ring logo, with nothing else. Power button takes me back to the CW menu again. No error messages at any stage, but nothing happens either.
Should I proceed with the steps in the second link you pointed to? Or does this sound like a different problem?
Hm don't know... Maybe try to find out if your cache is corrupted or your emmc chip. So yes follow the link i posted, but before you do the same as the op there (means using your sdcard instead of emmc) try everything else... (i think nipqer posted a link there related to corrupted cache...)
Sent from my HTC Vision using XDA App
Thankfully, I didn't have to go through hardly any of the contortions CollegeBound had to in that thread. Installing 4EXT was enough -- it was able to get past the "E:Can't mount /cache/..." errors (which started again when I used fastboot to erase the cache), whereas Clockwork was stymied by them. Did an update using a CM ROM, and everything seems fine.
Thanks again for your help. I don't think T-Mobile would have let me RMA two phones in two weeks.
It all goes like this - I wanted to root my WPS to solve space problem, although, there was a solution for it without rooting, I figured I will be wanting to use some apps that need root access and some roms sooner or later.
So I did a search and found few ways to root my phone. Being a lazy ass I decided to use "the simple" one click solutions - gingerbreak (http://forum.xda-developers.com/showthread.php?t=1044765) or Root Unlocker (http://www.unlockroot.com/) This was no success. Gingerbreak kept rooting when I launched the app, but Root Unlocker displayed " FAIL TO GET SHELL ROOT". I figured that problem with Gingerbeak might be that I updated the software to the latest version -
Then I went on and tried another tutorial(http://forum.xda-developers.com/showthread.php?t=1195275). Everything was fine till I selected Recovery from bootloader. It got stuck with white HTC logo. Took out the battery tried to use newer version of ClockworkMod Recovery, but still was a no-go. I also can't do a factory restart. I can't do it from bootloader or settings > SD & phone storage > Factory data reset. (But could do it at first. Before trying to root my device I did a factory reset once.)
Is there a way to use another Recovery (not CMR) or force Recovery from fastboot? As I found there are some other people that got stuck with similar problem.
Other problems:
My phone doesn't show up in HTC Sync. Althought, when I tipe adb devices in cmd, it shows up. I did turn my AntiVirus off when I installed HTC Sync, but it still didn't display my phone.
I also found that I can't boot when I connect powered off phone to my pc. I have to take off my batery.
Here are my specs:
Model HTC Wildfire S A510e
It shows Marvel in bootloader.
Phone was S-OFF when I bought it.
Android 2.3.5
HTC Sence 2.1
Software number 2.26.401.3
I bought my phone without a contract from a local internet shop. I am from Baltics.
The phone might be somewhere from Europe.
My bet would be Poland. (guessing that manual language is Polish, but I might be wrong)
Thanks in advance.
UPDATE!
I took the original recovery img from http://forum.xda-developers.com/showthread.php?t=1426611 and flashed it. All went well. I did a restart (after doing this I was able to boot power my device while connected to pc) and had another try with CMR recovery, but it didn't work. I also I tried http://forum.xda-developers.com/showthread.php?t=1406321 recovery img, but it didn't help, I still can't get into.
How to root Wildfire S S-OFF the easy way
First download this
Put it in your memory card
then press and hold voldown+Power
It will load the bootloader follow the instructions on the screen and update accordingly
Then Turn off
Remove that PG76IMG from sdcard
After that download this and put in your memorycard and update same way, it will flash the CMR5.0.2.8 (after flashing dont forget to remove this PG76IMG from sdcard as well).
Now download this put it in your mmc and flash this from recovery.
Done.. U have successfully rooted Ur S-OFF device Now In CWM do factory reset install new custom rom according to the way devs say. I can assure U that this process will even remove Ur white screen
im stuck too on the recovery s-on btw and bootloader unlocked
ME TOO
but i m s-on
Same problem here, unlock by htc-dev worked. Recovery flashed but device stays stuck on the HTC logo. So my daughter's phone is unlocked but that's it.
Thanks, but now I am simply stuck with white htc logo on black background with purple line after entering recovery.
There might be another work around with fastboot, but also have a fastboot remote: not allowed.
Let me know
7axew3ku said:
Thanks, but now I am simply stuck with white htc logo on black background with purple line after entering recovery.
There might be another work around with fastboot, but also have a fastboot remote: not allowed.
Click to expand...
Click to collapse
I dont understand. If ur splash screen changed means u have installed cwm. Just select recovery and install a rom. Like this one
Download the rom. Put in ur sdcard.
remove battery
press vol down+power
press vol down
press power to select recovery
In recovery to move press vol up/down, to select press power
Wipe data/factory reset
Wipe cache partition
Advanced>> Wipe Dalvik cache then also wipe battery stats
Go back
Install zip from sdcard
Select the romname.zip put in sdcard
that should be it instructions are also found in that rom. thread so simple!!
7axew3ku said:
Thanks, but now I am simply stuck with white htc logo on black background with purple line after entering recovery.
There might be another work around with fastboot, but also have a fastboot remote: not allowed.
Click to expand...
Click to collapse
Here is a flash file you can try since you are S-Off. It should flash the default splash image, CWM 5.0.2.8, hboot 1.03 and re-calibrate the touch panel.
Hope it works for you.
Deleted
Problems persist
I have the same problem. My bootloader is unlocked via HTCDEV.com, though with S-ON. In any case...
My WFS is running 2.3.5, it's A510e.
installed recovery image 5.0.2.8 via console (had trouble installing it from the SD card).
each time I attempted to go HBOOT > RECOVERY, my phone would reboot, but would be stuck in black screen with the nav buttons at the bottom lit up (HOME, MENU, BACK, SEARCH).
installed recovery image 6.0.1.0 via SD card, going to HBOOT > RECOVERY will restart the phone, but it freezes on the white screen with the green HTC logo
downgraded to recovery image 6.0.0.3 via console, same problem - frozen on the white screen with the green HTC logo.
at this point, I'm out of ideas, but it seems that recovery image is at fault here?
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-7.57.39.10M
Feb 8 2012,18:29:31
Is there a way to execute the ROOT.ZIP script on the phone but via the console on PC?
Return back to Normal after BOOT-LOOP !
muckz said:
I have the same problem. My bootloader is unlocked via HTCDEV.com, though with S-ON. In any case...
My WFS is running 2.3.5, it's A510e.
installed recovery image 5.0.2.8 via console (had trouble installing it from the SD card).
each time I attempted to go HBOOT > RECOVERY, my phone would reboot, but would be stuck in black screen with the nav buttons at the bottom lit up (HOME, MENU, BACK, SEARCH).
installed recovery image 6.0.1.0 via SD card, going to HBOOT > RECOVERY will restart the phone, but it freezes on the white screen with the green HTC logo
downgraded to recovery image 6.0.0.3 via console, same problem - frozen on the white screen with the green HTC logo.
at this point, I'm out of ideas, but it seems that recovery image is at fault here?
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-7.57.39.10M
Feb 8 2012,18:29:31
Is there a way to execute the ROOT.ZIP script on the phone but via the console on PC?
Click to expand...
Click to collapse
Hi,
I read boot-looped for many in this thread...
I Hope this method would solve all your problems....
Follow and flash these system.img, boot.img and recovery.img file as in the link. (You must have installed .net framework on your PC).
http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1
Hope this may useful!! (If really just press 'Thanks")......
Senthamil said:
Hi,
I read boot-looped for many in this thread...
I Hope this method would solve all your problems....
Follow and flash these system.img, boot.img and recovery.img file as in the link. (You must have installed .net framework on your PC).
http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1
Hope this may useful!! (If really just press 'Thanks")......
Click to expand...
Click to collapse
Nope didn't work. I reflashed each of the boot.img, system.img, and recovery.img, manually though, since the utility didn't work for me. To do this, I booted into HBOOT, then FASTBOOT, and ran commands from my machine "fastboot flash <image type> <image.img>", where <image type> is either boot, recovery, or system, and <image.img> is the corresponding image (boot.img, recovery.img, system.img).
It seems my recovery cannot boot from HBOOT. It simply gets stuck.
With clockwork recovery 5.0.2.6, the phone appears to shut off completely.
With clockwork recovery 5.0.2.8, the phone will shut off except the Android buttons at the bottom are lit up.
I don't know if I can use later CW recovery images, but I tried 6.0.0.3 and I get stuck at the white background with green HTC logo when attempting to go into RECOVERY. Downgraded back to 5.0.2.8.
However, I gave the HTC SuperTool v3 another try, and this time it worked. Previously was giving me errors.
So... to those that are stuck, boot your phone normally. Make sure to go into Settings > Applications > Development and enable USB debugging. Also enable 3rd party installs, just in case.
Then proceed to STEP 3 on this page http://www.htcwildfiresblog.com/2012/03/guide-to-rooting-htc-wildfire-s-235-s.html
For those who want more info, here's another thread:
http://forum.xda-developers.com/showthread.php?t=1725398
It appears that the latest Wildfire S has a slightly different firmware, possibly for the video chip, which causes the CWM Recovery not to work. Perhaps there'll be a fix released eventually, but for now you can follow the thread above for some possible workarounds and more info.
Try mg all in one tool. Here: http://forum.xda-developers.com/showthread.php?t=1697985
It should sort out you guys problems.
muckz said:
Nope didn't work. I reflashed each of the boot.img, system.img, and recovery.img, manually though, since the utility didn't work for me. To do this, I booted into HBOOT, then FASTBOOT, and ran commands from my machine "fastboot flash <image type> <image.img>", where <image type> is either boot, recovery, or system, and <image.img> is the corresponding image (boot.img, recovery.img, system.img).
It seems my recovery cannot boot from HBOOT. It simply gets stuck.
With clockwork recovery 5.0.2.6, the phone appears to shut off completely.
With clockwork recovery 5.0.2.8, the phone will shut off except the Android buttons at the bottom are lit up.
I don't know if I can use later CW recovery images, but I tried 6.0.0.3 and I get stuck at the white background with green HTC logo when attempting to go into RECOVERY. Downgraded back to 5.0.2.8.
However, I gave the HTC SuperTool v3 another try, and this time it worked. Previously was giving me errors.
So... to those that are stuck, boot your phone normally. Make sure to go into Settings > Applications > Development and enable USB debugging. Also enable 3rd party installs, just in case.
Then proceed to STEP 3 on this page http://www.htcwildfiresblog.com/2012/03/guide-to-rooting-htc-wildfire-s-235-s.html
Click to expand...
Click to collapse
It finally worked. I am rooted. Thanks mate and everybody (who hasn't already received a thanks) that joined this posts receives virtual cookie from me and thanks.
I flashed stock http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1 and run SuperTool and it worked.
It took me a week, but it is finally done. Let the good times roll.:laugh:
7axew3ku said:
It finally worked. I am rooted. Thanks mate and everybody (who hasn't already received a thanks) that joined this posts receives virtual cookie from me and thanks.
I flashed stock http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1 and run SuperTool and it worked.
It took me a week, but it is finally done. Let the good times roll.:laugh:
Click to expand...
Click to collapse
It appears that CWM 5.0.2.8 actually works, but it doesn't provide any output to the screen. With ROM Manager, you can automate starting into CWM Recovery and installing a custom ROM, so it doesn't matter if the screen is blank.
Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!
BigEdgar said:
Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!
Click to expand...
Click to collapse
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.
cmlusco said:
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.
Click to expand...
Click to collapse
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?
BigEdgar said:
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?
Click to expand...
Click to collapse
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.
cmlusco said:
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.
Click to expand...
Click to collapse
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?
BigEdgar said:
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?
Click to expand...
Click to collapse
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?
BigEdgar said:
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?
Click to expand...
Click to collapse
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...
BigEdgar said:
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...
Click to expand...
Click to collapse
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Are you able to use adb now? If you can, i have another sugestion i came across in another thread. A guy said he could not access, format, or use his data partition. He claims he fixed it by adb pulling the file system from a working inc, and adb pushing the files to the borked inc, fixing it. If you can get adb to stay connected long enough to push the files it might be worth a try.
cmlusco said:
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Click to expand...
Click to collapse
Thanks again for the suggestions.
I tried that but it's pretty much the same results.
HBOOT--> Factory Reset --> Screen with green arrows --> Red triangle with Exclamation point --> - Power button + Up Volume to get to the System Recovery menu --> Reboot:
Phone hangs on the black/white "htc Incredible" splash screen
One other odd note - if I do this same factory reset process with the USB cable *unplugged*, the instead of hanging on the black/white splash screen, it just goes into an infinite loop (black/white splash screen --> HTC quietly brilliant screen --> droid eye --> back to the black/white splash screen). FWIW this isn't new behavior, I just forgot to mention it earlier. In fact this is what the phone started doing once Verizon pushed the OTA update that screwed up the phone in the first place (there are a number of threads on this over at HTC and VZW forums, but their solutions aren't working for me).
I think this thing is a brick. If anyone has any recommendations for tools that can be used to analyze the partitions on a phone that won't boot, let me know. Otherwise this thing is getting sold for parts : )
Ok, some more progress. Most importantly, I learned that adb has a shell! I obviously didn't RTFM well enough.
Anyways, with the shell I was able to verify that the partitions on the phone are accessible (at least from a Windows machine) and I can, in fact, write files to the device (using "adb push" to push files to /sdcard, for example). That's great as it proves that the storage on the device *is* accessible, but just not from CWM. I followed some instructions that I followed partially before (http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html) in an attempt to see if I could get S-OFF. This tutorial is nice because most of the actions are via adb and fastboot instead of using the UI on the phone, which I couldn't get to. I was able to do most of the work I needed to get S-OFF via adb instead of using CWM or some other recovery tool, which was key, since CWM always tells me that it can't read or write any partitions.
I was actually able to get Froyo installed and boot into it! That's the first time this POS has booted into anything in almost a month!!
Now to my current problem - the last few steps of the tutorial linked above require that I install superuser and unrevoked, and suggest that this be done via CWM. Unfortunately, CWM can't read any of my data partitions, so this doesn't work for me. Not many others seem to have this problem, so googling it doesn't turn up any help.
Is there any way I can use ADB to install superuser and unrevoked forever? I also have access to the UI via Froyo and could conceivably install apks as well.
Here are the instructions from the tutorial that don't work for me, as they rely on CWM:
******************
use the recovery menu on your phone to:
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-install zip from sd card(chose your forever file)
******************
Those last two steps - install zip from sd card - are the ones that completely fail for me. CWM just gives me a bunch of "E:can't mount /sdcard/" errors.
If anyone has any ideas on how to install superuser and unrevoked using ADB, I'm all ears : )
Thanks!
So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app
nschiwy said:
So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?
BigEdgar said:
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?
Click to expand...
Click to collapse
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.
cmlusco said:
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried this a few times and while Unrevoked is reporting success, I'm still S-ON and BusyBox and ROM Manager report that I'm not rooted. Back in CWM, CWM still reports errors mounting all drives and is basically crippled. In addition to the "can't mount SD card" errors, I'm also seeing "E:cant mount /dev/block/mmcblk0p2" and "E:Can't mount /cache/recovery/command". Weird. Can't tell if the mount errors are causing my inability to root or my inability to root is causing the mount errors.
(I also tried using AmonRa and got the same "can't mount" blah blah issues). Time for a drink : )
There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off
eljean said:
There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off
Click to expand...
Click to collapse
Eljean - that link's a 404...
I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app
eljean said:
I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.
BigEdgar said:
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.
Click to expand...
Click to collapse
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243
eljean said:
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243
Click to expand...
Click to collapse
I appreciate the thoughts, but I think we're talking about different issues here. One of your issues seemed to be that you couldn't access the device at all via USB. I don't have that problem. My USB connection has always been fine. My problem is that CWM can't mount the SD card (or any other drives, for that matter). Everything mounts fine in Froyo, so I'm guessing it has to do with the way the drives are mounted in Recovery vs. Froyo.
The thread you referenced stated that the fix for not being able to access the SDcard was the fastboot oem enableqxdm 0 fix. I tried that a few times but it didn't make any difference.
Thanks for the thoughts!
Hello,
I am no expert but i usually fix problems, however this one keeps puzzling me for a long time now.
I own a wildfire, not modded, not modified in any way. One day I open a qr code app, it decides to freeze, so i reboot. (i think i had to remove the battery) It takes about 15min to boot, doesn't respond to any input and then reboots and the cycle continues.
I have looked into several solutions for the problem, but all require me to turn S-off. But to do that I need to turn on usb-debug, but to do that I need a bootable image!!!!
At first i wanted to mod, tried revolutionary to turn off S, but doesn't work because i can't turn on usb-debug.
Then i wanted to turn off S the HTC way, where they send me the code needed to unlock it, but it said i had to first update the RUU and guess what:
"To install the RUU, simply follow these instructions: On your phone, enable USB debugging. (..)"
I do not understand what i should choose from the RUU download page, but if it helps i am from Italy. I tried the program and this is the output:
C:\Users\*user*>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
I did all possible options the bootloader gives me: deleted all user data (losing most of my stuff i guess), I tried recovery too but it doesn't like the image. (which i have not touched or modified in any way)
specs:
BUZZ PVT SHIP S-ON
HBOOT - 1 . 01 . 0001
MICROP - 0622
TOUCH PANEL - ATMELC03_16ac
RADIO - 3 . 35 . 20 . 10
Nov 17 2010 , 12:08:53
stormsight said:
Hello,
I am no expert but i usually fix problems, however this one keeps puzzling me for a long time now.
I own a wildfire, not modded, not modified in any way. One day I open a qr code app, it decides to freeze, so i reboot. (i think i had to remove the battery) It takes about 15min to boot, doesn't respond to any input and then reboots and the cycle continues.
I have looked into several solutions for the problem, but all require me to turn S-off. But to do that I need to turn on usb-debug, but to do that I need a bootable image!!!!
At first i wanted to mod, tried revolutionary to turn off S, but doesn't work because i can't turn on usb-debug.
Then i wanted to turn off S the HTC way, where they send me the code needed to unlock it, but it said i had to first update the RUU and guess what:
"To install the RUU, simply follow these instructions: On your phone, enable USB debugging. (..)"
I do not understand what i should choose from the RUU download page, but if it helps i am from Italy. I tried the program and this is the output:
C:\Users\*user*>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
I did all possible options the bootloader gives me: deleted all user data (losing most of my stuff i guess), I tried recovery too but it doesn't like the image. (which i have not touched or modified in any way)
specs:
BUZZ PVT SHIP S-ON
HBOOT - 1 . 01 . 0001
MICROP - 0622
TOUCH PANEL - ATMELC03_16ac
RADIO - 3 . 35 . 20 . 10
Nov 17 2010 , 12:08:53
Click to expand...
Click to collapse
Hmmm. First off, have you tried to factory reset from recovery? If you boot into the recovery and then hold both volume buttons and power a usable menu should appear. Factory reset from there and reboot. See if that helps.
If not we turn our attention to your hboot. The error is because it is not updated enough to have that command. So we have two choices here. You can either upgrade the hboot, unlock your bootloader via htcdev and flash a custom rom. Or you could create a Goldcard, flash a ruu that has the same hboot as the one you have. This should fix your rom and enable the phone to boot again.
In any event you will need to extract the rom.zip from whichever ruu you choose. To do that have a quick google search for a guide but its easy enough. After that rename the rom.zip to PC49img.zip and place it onto your sdcard, boot into hboot and allow it to flash it. The golcard process should be covered in one of my downgrade threads or one of the others from this forum.
Post back here if your having and trouble or need a hand
heavy_metal_man said:
Hmmm. First off, have you tried to factory reset from recovery? If you boot into the recovery and then hold both volume buttons and power a usable menu should appear. Factory reset from there and reboot. See if that helps.
Click to expand...
Click to collapse
Yes, i forgot to mention: i have tried all options in the recovery (red triangle thing) too (clear cache, factory reset) nothing worked, it says: E:Can't open /cache/recovery/command
heavy_metal_man said:
You can upgrade the hboot, unlock your bootloader via htcdev and flash a custom rom.
Click to expand...
Click to collapse
To do this, i would need usb-debug enabled, so I think i cannot, but if there is a way please tell me!
heavy_metal_man said:
Or you could create a Goldcard
Click to expand...
Click to collapse
To do this i will need a micro-sd adapter to put my card into my computer, i will find one and try it out.
I also read that i need the correct RUU for my carrier. I am not understanding very well what i'm doing, also no idea what a RUU is or where to get the appropriate one for my Hboot and carrier, any advice ?
stormsight said:
Yes, i forgot to mention: i have tried all options in the recovery (red triangle thing) too (clear cache, factory reset) nothing worked, it says: E:Can't open /cache/recovery/command
To do this, i would need usb-debug enabled, so I think i cannot, but if there is a way please tell me!
To do this i will need a micro-sd adapter to put my card into my computer, i will find one and try it out.
I also read that i need the correct RUU for my carrier. I am not understanding very well what i'm doing, also no idea what a RUU is or where to get the appropriate one for my Hboot and carrier, any advice ?
Click to expand...
Click to collapse
All usb debugging is for is so that adb can reboot the device to hboot. If you google for how to extract the rom.zip from the ruu and then put it on the sdcard (after renaming it to PC49IMG.zip) and boot to hboot it is the same thing. Just without usb debugging needed.
You will need a micro sdcard adapter pal.
alright, after using the HTC dev method, i unlocked the phone, it still says S-ON but *** UNLOCKED *** on top, the HBOOT is now 1.02.000
after that i obtained the ClockWorkMod recovery img (i used version 5.0.2.0) and did in the terminal:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
stormsight said:
alright, after using the HTC dev method, i unlocked the phone, it still says S-ON but *** UNLOCKED *** on top, the HBOOT is now 1.02.000
after that i obtained the ClockWorkMod recovery img (i used version 5.0.2.0) and did in the terminal:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
Click to expand...
Click to collapse
good stuff pal.
when you are in clockworkmod recovery the controls are different. use the trackball to scroll and select. power button is now the back button.
I would recommend this custom rom as it is stable and has a stock vibe to it. just follow its install instructions and you should be good to go
Thanks, after many trial and error i ended up asking my hacker friend and managed to install cyanide mod.
However the same problem which i originally had persists ( it is very slow to boot (when it boots) and it doesn't react to any input, at this point it must be a hardware problem. This makes me very sad, i thought i saved it..
stormsight said:
Thanks, after many trial and error i ended up asking my hacker friend and managed to install cyanide mod.
However the same problem which i originally had persists ( it is very slow to boot (when it boots) and it doesn't react to any input, at this point it must be a hardware problem. This makes me very sad, i thought i saved it..
Click to expand...
Click to collapse
That suck man.
Hmmm. Slow boot times are normal on this phone to a certain degree. Usually 20secs to 3 minutes at first boot aftet rom flash.
Once the phone has booted up does the trackball still work? Could just be a damaged digitizer. They are fairly cheap these days. Look here http://m.ebay.co.uk/itm/281644653982 and here http://m.ebay.co.uk/itm/281644653982 fairly straight forward to install, but you could buy a used version of the phone for £30 minimum so its up to you
Edit: although, on reflection 15 boot time and constant reboots are not a good sign. I was hoping it was a software issue. If the trackball is functional you could go into settings, enable usb debugging and then get a logcat. That would at least give us somewhere to work from :-/
the trackball is functional because i can use it in clockwork recovery! but the phone doesn't react to it after boot, it's like it's stuck, i don't think the issue is the touchscreen, it used to work fine, it must be something else.
boot time is about 5-6minutes now, but after that it's like frozen, and after a couple more minutes it reboots. A big improvement, now the bootloop period is at least 70% shorter! xD
stormsight said:
the trackball is functional because i can use it in clockwork recovery! but the phone doesn't react to it after boot, it's like it's stuck, i don't think the issue is the touchscreen, it used to work fine, it must be something else.
boot time is about 5-6minutes now, but after that it's like frozen, and after a couple more minutes it reboots. A big improvement, now the bootloop period is at least 70% shorter! xD
Click to expand...
Click to collapse
Lol! Well at least thats a plus :-/ theres not much else we can do here. We could try to enable usb debugging fron within clockworkmod by editing the build.prop and see if we can get a logcat but if the phones just locking up we might not even get one :-/