Develop Bugs

[Q] help, bricked phone

Hi all, I followed the usb brick fix by the professor but it didnt work. the phone has a black screen with white htc. also i was s-off running cm7 r2. can't get into bootloader.this is my fastboot oem boot
c:\android-sdk-windows\tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x26A0D
(bootloader) TAG:hero panel = 0x3
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::HTC__Y13
(bootloader) serial number: SH09APL12956
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =421
(bootloader) active commandline: board_bravo.disable_uart3=1 board_bravo.
(bootloader) usb_h2w_sw=1 board_bravo.disable_sdcard=1 diag.enabled=1 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.11.05.27 androidboot.cid=H
(bootloader) TC__Y13 androidboot.carrier=HTC-Nor androidboot.mid=PB992000
(bootloader) 0 androidboot.keycaps=qwerty androidboot.mode=normal android
(bootloader) boot.serialno=SH09APL12956 androidboot.bootloader=6.93.1002
(bootloader) no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:526368 msec
FAILED (status read failed (Too many links))
finished. total time: 13.261s

And why don't you boot into fastboot with back + power button?
And remember one thing: If your phone still reacts, it's not bricked.
TouchPaled from Oxygen with Transparent XDA App

bricked is so over used.... you can access fastboot?? So what have you tried to fix the problem?

It all satrted when i backed up my rom with nandriod and then tried to flash a wifi n kernel, i then got boot loop, i then removed the battery and got to into recovery to flash backup only to realise that i could access my sd card. i then tried to flash back to my stock ruu without changing my hboot partitons (big mistake) thats when i could access any options on my bootloader, all it says is alpharev cm7 r2, radio and kernel, under all that where it should have fastboot recovery so on all it says is ruu. then when i plug usb cable in i get black screen with white htc and triangles in all 4 corners with exclamation marks in them.
i tried this usb brick by the professor guessing thats the problem, i have no idea what the correct terminology for what has happened is so i'm guessing after numerous google searches that its a usb brick. I generated my mtd0.img with the cid generator and move the mtd0.img and flash image to sdcard, but got stuck after that.
I hope this all makes sense to someone and you can help me through this.
Thanks very much guys

Was ROM manager involved in any way?

No rom manager involved.

The screen with the exclamation marks is fastboot-if you connect with your USB cable you should be able to enter fastboot commands with your PC.
You need to flash a ROM suitable for your hboot using fastboot commands.
You may also have overwritten your recovery partition which can be reflashed with fastboot.
I've only done the above a couple of times so may be wrong!

Ok.
Well going back to what BigMrB asked, can you boot into fast boot still? (Back + power from off)?
If you can, then check if when you plug in the USB cable, it changes to "Fastboot USB" please

Hey if you had taken backup of your rom then go to recovery by pressing volume down and power button then select recovery there go to back and restore and restore to the backup you had taken. Even i get my device not working while flashing new things there is nothing to worry you can always do the same.
Hope this helps you
Sent from my HTC Desire using XDA Premium App

iain2510 said:
The screen with the exclamation marks is fastboot-if you connect with your USB cable you should be able to enter fastboot commands with your PC.
You need to flash a ROM suitable for your hboot using fastboot commands.
You may also have overwritten your recovery partition which can be reflashed with fastboot.
I've only done the above a couple of times so may be wrong!
Click to expand...
Click to collapse
Sorry I didnt see your post. Fastboot should be white screen, but if he uses back and Power and gets the exclamations, it can still be used as fastboot.
What I am concerned about is the screen says "RUU" on it which sounds like a RUU was used and failed at some point (edit, yes OP said that)
A RUU would fail if he has CM7 Hboot.
I would personally recommend flashing the downgrader hboot via fastboot and then completing whatever RUU process was started.
I would also recommend people askign questions before jumping in and trying anythign they can to fix their issues, or guessing what issue they have

rootSU said:
Sorry I didnt see your post. Fastboot should be white screen, but if he uses back and Power and gets the exclamations, it can still be used as fastboot.
What I am concerned about is the screen says "RUU" on it which sounds like a RUU was used and failed at some point (edit, yes OP said that)
A RUU would fail if he has CM7 Hboot.
I would personally recommend flashing the downgrader hboot via fastboot and then completing whatever RUU process was started.
I would also recommend people askign questions before jumping in and trying anythign they can to fix their issues, or guessing what issue they have
Click to expand...
Click to collapse
Does he have to run the downgrader? Thought he could just flash a different hboot but i might be wrong...
Can you not just flash recovery again and just restore the nandroid? If not i would THEN use the RUU and start from fresh

BigMrB said:
Does he have to run the downgrader? Thought he could just flash a different hboot but i might be wrong...
Can you not just flash recovery again and just restore the nandroid? If not i would THEN use the RUU and start from fresh
Click to expand...
Click to collapse
He doesn't have to, he can flash a stock hboot, then flash recovery and a rom, but Id rather he RUU, which would require the downgrader

I get the black screen with the exclamations which can be used as fastboot.
How do i go about downgrading my hboot? will it revert my phone back to stock with the stock partitions?
thanks guys

mizdel said:
I get the black screen with the exclamations which can be used as fastboot.
How do i go about downgrading my hboot? will it revert my phone back to stock with the stock partitions?
thanks guys
Click to expand...
Click to collapse
Either download the adnroid flasher from the desire dev forum here, or follow my fastboot faq in my signature to do it manually. Download the downgrader from alpharev.nl (Redeirects sometimes to revolutionary.io so may have to click the alpharev link once redirected to the revolutionary page) and flash it.
It willput your phone in a state where a RUU will work woth the stock partitions but shouldnt be used as a hboot in iots own right so if you decide not to RUU, you would be better just flashing the stock hboot.

I'd recommend learning some basic fastboot commands regardless of which option you take.... They come in handy for situations just like this one

BigMrB said:
I'd recommend learning some basic fastboot commands regardless of which option you take.... They come in handy for situations just like this one
Click to expand...
Click to collapse
+1, its always good to understand a bit of what you are doing. Some of my other faq's may be helpful too.

i flashed downgrader to my hboot and now it says rebooting and nothing is happening. how long do i wait or do i have to flash stock ruu now?

How did you flash it? It should just say:
writing....
done
If you used fastboot flash hboot blahblahblah.img

i used android flasher and attached downgrader to flasher at hit begin

Well if its still in the same state, there's not a lot you can do but pull power
Sent from my HTC Desire using XDA App

Stuck at HTC logo, can't recover

Hey guys, I'm having quite an issue here trying to help a friend with her DesireZ, it's stuck at the HTC logo and won't start up...
Here's a list of things I've tried:
- Volume Down + Power > RECOVERY > will vibrate 7 times and then it's stuck.
- FASTBOOT - Flash new RUU - says "Rebooting to bootloader" on the PC but nothing ever happens.
- renamed rom.zip from the RUU to PC10IMG.ZIP, placed it on SDCARD, Volume Down + Power - it will see the file but... when the update process starts it gets stuck at the very first step "Bootloader - updating" and it freezes there.
The owner said she never tried anything like rooting it or changing the ROM or anything like that... what could be wrong??
THanks!

so she actually got a stock phone.
two things you could try:
1. if the phone is stock you can´t enter recovery through bootloader (power & volume -) - you have to use power & volume + (here you could try to wipe cache or do a factory reset)
2. you can force the phone to boot using fastboot and typing: fastboot oem boot (at least you will get an output what goes wrong while booting)

Thanks for the reply. Volume+ and power doesn't do anything it seems... if I do Volume- and Power I get to the bootloader (FASTBOOT, RECOVERY, FACTORY RESET, SIMLOCK, etc...) ... I tried FACTORY RESET but it freezes there. How can I wipe the cache?
This is what I get when i do fastboot oem boot
C:\Android>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878FC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25202
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is HTC__032
(bootloader) setting->cid::HTC__032
(bootloader) serial number:
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =504
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.10.04.03_M androidboot
(bootloader) .cid=HTC__032 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=HTC-EastEurope androidboot.mid=PC1011000 android
(bootloader) boot.keycaps=qwerty androidboot.mode=normal androidboot.seri
(bootloader) alno=SH19ERT00226 androidboot.bootloader=0.85.0013 zygote_on
(bootloader) eshot=off kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:19715 msec
FAILED (status read failed (Too many links))
finished. total time: 8.296s
C:\Android>

Delete the serial number in your posting.
try to enter recovery, you should see something like a red triangle then push volume + & power and you should see a menu... here you should be able to wipe cache
there is also a fastboot way to do this ...fastboot erase cache is the command for wiping, but it only works with eng hboot.
Is the ruu you used the same as your stock rom? other people fixed it with using the right PC10IMG.zip
or you can hope for warranty
Sent from my HTC Vision using XDA App

I have a similar problem, I think. I'll try to be as informative as possible, but I'm very new at troubleshooting my device.
As with the other phone, mine will continue to get stuck at the HTC logo, then reboot.
I was browsing market, when it froze. I just left it frozen, and waited for it to restart. Once it restarted, it came up with the phone with the triangle icon. Not knowing what it meant, I took out the battery and reinserted it.
On reboot, it began its boot cycle.
I get no response holding volume up + power, nor volume down + power.
I tried reinserting battery, removing memory card and removing sim card - restarting after each step, but still nothing.
Only way to break the boot cycle is to remove battery, but when rebooted, it starts over again.
Please help?

first of all you need to somehow enter bootloader (volume- & power) try it a few times after you pulled the battery...
is your phone rooted?

No, sorry, I forgot to say that. Not rooted. Too worried about viruses and stuff.
*EDIT*
Yay - got into the boot section. I hit recovery and I get the phone with the red warning triangle. Does that mean that it's not working, or that it's working on recovering?

Breagha said:
No, sorry, I forgot to say that. Not rooted. Too worried about viruses and stuff.
*EDIT*
Yay - got into the boot section. I hit recovery and I get the phone with the red warning triangle. Does that mean that it's not working, or that it's working on recovering?
Click to expand...
Click to collapse
no it´s normal if you are not rooted. now press power & volume + to enter menu and then first thing to try is wiping cache and see if you can boot into the rom afterwards

I cleared cache and it said it did so successfully.
However when I asked it to restart, it continues the reboot cycle
*Edit*
Yay! It works when I take out my memory card now! You're a life saver!
What do I do now?

Breagha said:
I cleared cache and it said it did so successfully.
However when I asked it to restart, it continues the reboot cycle
Click to expand...
Click to collapse
hm... next thing you could try is a factory reset (should be a option in recovery)
EDIT: if this doesn´t work you could try the PC10IMG.zip as described above - never done this, but i guess you have to use one that is the same as your stock rom...
EDIT 2: you can boot into the rom without sdcard? if so try to format your sdcard (don´t know if there is a option for it in stock recovery) or buy a new one

I got into my OS when I took out the memorycard..
I think it already did a factory reset, 'cause it's asking me to set it up again, only now it's frozen on my language selection screen. Is there a ctrl+alt+delete for androids? >.<

Breagha said:
I got into my OS when I took out the memorycard..
I think it already did a factory reset, 'cause it's asking me to set it up again, only now it's frozen on my language selection screen. Is there a ctrl+alt+delete for androids? >.<
Click to expand...
Click to collapse
no, press the power button for 5 sec maybe the phone shuts down... or pull the battery and to be sure do a factory reset again and then try to boot into the OS again
EDIT: skip the sign in part go to settings and enable usb debugging...

It's working, it's working!! You're my hero! I thought I'd have to send it back in and wait 14 work days to get it back >.<
*huggles* Merry happy awesome Christmas to you

help please
crzvm said:
Hey guys, I'm having quite an issue here trying to help a friend with her DesireZ, it's stuck at the HTC logo and won't start up...
Here's a list of things I've tried:
- Volume Down + Power > RECOVERY > will vibrate 7 times and then it's stuck.
- FASTBOOT - Flash new RUU - says "Rebooting to bootloader" on the PC but nothing ever happens.
- renamed rom.zip from the RUU to PC10IMG.ZIP, placed it on SDCARD, Volume Down + Power - it will see the file but... when the update process starts it gets stuck at the very first step "Bootloader - updating" and it freezes there.
The owner said she never tried anything like rooting it or changing the ROM or anything like that... what could be wrong??
THanks!
Click to expand...
Click to collapse
hey i have the exact same thing, my desire z froze when i received a htc update and got stuck once it restarted and now im stuck in the same boat as above.
its a non rooted UK htc desire z and i have tried:
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
Rom from shippedroms.com but it just freezes saying rebooting to bootloader.
Please help and tell me how to fix it as you have managed to do so.
thanks
---------- Post added at 06:21 PM ---------- Previous post was at 06:05 PM ----------
also the current image rom on my desire z is version 2.42.405.4 and the RUU says to flash it to 2.42.405.2 - would that be a problem???

Same problem
sal2103 said:
hey i have the exact same thing, my desire z froze when i received a htc update and got stuck once it restarted and now im stuck in the same boat as above.
its a non rooted UK htc desire z and i have tried:
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
Rom from shippedroms.com but it just freezes saying rebooting to bootloader.
Please help and tell me how to fix it as you have managed to do so.
thanks
---------- Post added at 06:21 PM ---------- Previous post was at 06:05 PM ----------
also the current image rom on my desire z is version 2.42.405.4 and the RUU says to flash it to 2.42.405.2 - would that be a problem???
Click to expand...
Click to collapse
I have a same problem, but nothing helped me what U wroted in the post... It can not came into recovery just vibrate several times and power off, or when I try to factory reset from bootloader screan it just frozen and only help is pulling the battery off.
So, no recovery, no factory reset, no adb communication... Please help, Thanks!

Sam Problem
So around 2 weeks ago I was using my G2 at a McDonald's and all of a sudden it turned off . . . Long Story short, it's stuck on the HTC screen. I can access Bootloader but doing recovery or factory reset does not do anything. I cannot access adb but I can use fastboot
Vision PVT SHIP S-ON
HBOOT-0.82.0008
MICROP-0425
RADIO-26.13.04.19_M
eMMC-boot
Apr 13 2011, 14:51:54
I also tried flashing several PC10IMG.zip files to no avail as each would end up with a "MAIN VERSION IS OLDER" error. I also made a GoldCard but have no idea how to properly apply it to the situation. Please I have spent 3 days working on this, I need help

SOLVED___help needed with a friends HTC desire

hi,
I spent last 5 hours reading on XDA, on another forums, testing stuff, searching more on the web but I cant figure out what to do. Also this is not my device so I am little worried to do something wrong.
I am using HD2 so this approach to android and flashing is little new to me so please forgive my desire noobiness.
First here are some info on the device.
It is a Desire GSM (I guess since it does have SIM card).
Baseband 32.56.00.32U_5.17.05.23
Info from hboot:
BRAVO PVT3 SHIP S-ON
HBOOT 0.83.0001
MICROP-051d
TOUCH PANEL-SYNt0101
RADIO-5.17.05.23
While doing some stuff for usb brick I got this info from running "fastboot oem boot". Posting it in case it might be relevant.
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07E8CC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x26A0D
(bootloader) TAG:hero panel = 0x3
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
(bootloader) serial number: HT09RPL01076
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =417
(bootloader) active commandline: board_bravo.disable_uart3=1 board_bravo.
(bootloader) usb_h2w_sw=1 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.17.05.23 androidboot.cid=1
(bootloader) 1111111 androidboot.carrier=ALL androidboot.mid=PB992**** an
(bootloader) droidboot.keycaps=qwerty androidboot.mode=normal androidboot
(bootloader) .serialno=HT09RPL01076 androidboot.bootloader=0.83.0001 no_c
(bootloader) onsole_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) mpu_nand_acpu_rw A1E 1000
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:33155 msec
FAILED (status read failed (Too many links))
finished. total time: 4.823s
Click to expand...
Click to collapse
I got this device from a friend. Symptoms were stuck at boot. It had 2.3 gingerbread installed. At that time adb worked and soon by looking at logcat I realized that something is wrong with sdext and then with sdcard and both werent usable in recovery.
After finding the threads about usb brick I did
fastboot oem enableqxdm 0(unblock your sd-card)
fastboot oem eraseconfig(fix misc partition)
Click to expand...
Click to collapse
and installed some zip through recovery that was on that page and after that
sdcard worked and I succesfully booted into android.
Then I installed latest clockworkmod recovery through rom manager and flashed this rom, a2sd+ version.
After that following problems occured:
I cant get adb to work, and usb mount is not working neither in recovery nor in rom. In recovery when desire is connected windows recognize "unknown device" and when I click on USB mount it stays on "unmount" option but computer doesn't see anything different.
When I connect the device while in android windows recognize 3 devices without drivers named "Qualcomm CDMA Technologies MSM".
I installed htc sync 2.0.33, and uninstalled it so that htc driver remains.
SD card woks fine in external card reader.
And there is also problem with charging. If I disconnect the cable while charging and plug it again phone wont charge. But there is a usb connection since windows still sees 3 devices named above. Then I need to turn off the phone, remove and put back the battery and then when I boot into android and plug the cable again it charges fine. If I disconnect the cable again problem is there again.
Jut so point out that while I am in fastboot or in hboot windows sees the phone, fastboot works fine, no metter if I unplug the phone and plug the cable back.
This somehow looks to me like possible hardware problem, but then again it could be something I did wrong or didnt know what to do.
After that I wanted to put phone to stock 2.2 rom, downloaded RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe but when running it while in fastboot phone hangs after some time. Also I tried renaming this file to PB99IMG.zip and copy it to a freshly formated sdcard (fat32) but when i enter the bootloader it wont do anything.
Any hint or suggestion is most welcome. I am all out of options what to try next.

You did the right steps, and think you fixed it, you just broke it again using ROM MANAGER!! Stay away from that piece of SH*T application!
Have you tried using the USB Brick Fix again? It should do it for you. Once you've done that, return it to stock, S-OFF the phone (much easier to fix), flash 4EXT Recovery (automatic USB un-brick, installed via app from market), backup, full wipe, and flash a rom.
Then never use ROM Manager in your life.

bortak said:
You did the right steps, and think you fixed it, you just broke it again using ROM MANAGER!! Stay away from that piece of SH*T application!
Have you tried using the USB Brick Fix again? It should do it for you. Once you've done that, return it to stock, S-OFF the phone (much easier to fix), flash 4EXT Recovery (automatic USB un-brick, installed via app from market), backup, full wipe, and flash a rom.
Then never use ROM Manager in your life.
Click to expand...
Click to collapse
I did the usb brick thing few more time, althought sdcard work without problems in that time.
But I cant do the s-off because of 0.83.0001 hboot version and dont know how to update the hboot without usb connection. All the ways I tried didnt do anything.
I just saw one thing. This is some errors in logcat that I get after plugging/unplugging the usb cable while in android.
E/BatteryService( 1019): /sys/devices/platform/msm_hsusb/usb_cable_connect (No such file or directory)
E/BatteryService( 1019): read property /sys/devices/platform/msm_hsusb/usb_cable_connect failed
E/BatteryService( 1019): /sys/devices/platform/msm_hsusb/usb_cable_connect (No such file or directory)
E/BatteryService( 1019): read property /sys/devices/platform/msm_hsusb/usb_cable_connect failed
D/BatteryService( 1019): isUsbConnected() = false
D/UsbConnectedReceiver( 1220): action = psclient.intent.action.usb_status
Click to expand...
Click to collapse
So there is a connection between computer and phone but something is not letting the phone start charging again. No metter if its connected to a computer or a wall charger. I need to remove the battery so it can start charging again.
From my point of view and limited experience with the device it can be caused by....anything....maybe faulty hardware...something done wrong by whoever rooted/flashed this device before me.
Thanx for conformation I did good steps.
I would like to install a stock 2.2 or maybe 2.3 rom without s-off, root or anything to see if that will fix this issue. Then I will know that is probably hardware error.
But dont know how to do it.
I tried starting wwe ruu from fastboot, and the phone freezes after I click on update and with renaming that file and try from sd card but nothing also happened. That card had single fat32 partition with only that zip file on it.

Check if you renamed it right. It must be pb99img.zip and not pb99img.zip.zip.
Gesendet von meinem HTC Desire

muellersmattes said:
Check if you renamed it right. It must be pb99img.zip and not pb99img.zip.zip.
Gesendet von meinem HTC Desire
Click to expand...
Click to collapse
At first I named it PB99IMG.zip (uppercase). Just now tried it in lowercase after doing the usb brick thing again and as again when it enters the hboot after about 5 sec it lists some green text and says no image. I tried with 3 different sd cards.

I got another SD card, extracted the rom.zip from ruu, renamed it to PB99IMG.zip and I succesfully flashed 2.2 stock rom, but the usb cable issue still exists.
After I once remove the usb cable, end plug it again, computer only sees three "Qualcomm CDMA Technologies MSM" devices, no driver for it..
Phone doesnt react at all, it is not charging, no usb connection detected other then the errors in logcat I typed before (I got those from aLogcat app).
Meanwhile in fastboot connection works fine, now I have 0.93.001 hboot.
Can I achieve root and s-off without USB connection?
Also now when I go into recovery now I get a black screen with phone picture and red trigle with exclamation sign..

After found this article I did USB brick fix on non-rooted stock 2.2 rom, and after that USB mount and charging works fine.
I just did root and s-off with unvevoked3 app and reflashed newest radio.
I will try now to flash newer 2.3 rom and hopefully it will work...
thanx to everyone
edit:
everything works perfectly.

clyder said:
After found this article I did USB brick fix on non-rooted stock 2.2 rom, and after that USB mount and charging works fine.
I just did root and s-off with unvevoked3 app and reflashed newest radio.
I will try now to flash newer 2.3 rom and hopefully it will work...
thanx to everyone
edit:
everything works perfectly.
Click to expand...
Click to collapse
Glad to hear it, there was no need to update to 2.3 though if your friend will be rooting and using custom ROMs anyway.
For future problems, keep S-OFF and flash 4EXT recovery which has USB brick auto detection and fix, so you won't have to go through this lengthy process again

bortak said:
Glad to hear it, there was no need to update to 2.3 though if your friend will be rooting and using custom ROMs anyway.
For future problems, keep S-OFF and flash 4EXT recovery which has USB brick auto detection and fix, so you won't have to go through this lengthy process again
Click to expand...
Click to collapse
I installed Revolution 4.0 rom on it. This device is used by an older man so if he is used to sense android I dont want to confuse him for now.
Allthough I dont like sense Revolution works very fast and stable.
I did s-off and flashed 4ext allready. Thanx for the tip about that one.

[Q] Stuck in RUU [HELP PLEASE!]

Dear developers,
I got a problem, there were a lot of things I could help my self with but now i'm stuck.
My HTC Desire Z won't boot... I can't flash anything to my phone because the bootloader is locked and I can't find a official RUU that would help me out.
I tried to boot in fastboot and I get the HTC logo with in every corner an exclamation, when I disconnect the phone I get the following screen:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.51.26
eMMC-boot
Apr 11 2011,23:36:27
RUU
- no reboot possible
- screen says RUU (when plugged in, RUU USB)
- can't find device with adb devices
- can find device with fastboot devices
- not possible to make goldcard, because no adb connection
- running new RUU didn't work either (because I can't find a RUU for 2.42.405.5)
I have no solution, can someone please help me?
------- Update
I have a gold card using another phone
If I now just try to flash something on my phone I get a signature error

What happened around the time your phone stopped booting? Did you go to HTC website to get the latest ruu from them? Also boot back to fastboot and try
fastboot check_emmc_mid
Sent from my Nexus 7 using xda premium

On the HTCDev.com I can vind a RUU for software version: 2.42.405.2 but I have 2.42.405.5
Now I tried the command: fastboot oem check_emmc_mid and get the output:
...
(bootloader) Manufacturer ID, MID=45
(bootloader) eMMC should be Sandisk
OKAY [ 0.009s]
finished. total time: 0.010s
I don't understand anything about it, I hope you do
And I tried a the command: fastboot oem boot and than I get the output:
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878FC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is HTC__E11
(bootloader) setting->cid::HTC__E11
(bootloader) serial number: SH0BNRT08614
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =496
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.10.51.26 androidboot.c
(bootloader) id=HTC__E11 androidboot.batt_poweron=die_battery androidboot
(bootloader) .carrier=HTC-Dutch androidboot.mid=PC1011000 androidboot.key
(bootloader) caps=qwerty androidboot.mode=normal androidboot.serialno=SH0
(bootloader) BNRT08614 androidboot.bootloader=0.85.0013 zygote_oneshot=of
(bootloader) f kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:27964 msec
FAILED (status read failed (Too many links))
finished. total time: 7.423s
And mij device gives a normal boot logo (the white one instead of the black one with the "!" in every corner)

Just wanted to se which emmc you had as one is prone to failure, you do have a good one though!
Now its all about finding the right bit to flaash for you which may be a bit hard as unrooted and bootloader locked phones only allow new os versions to be flashed. I won't be near a computer for a while but when I get back ill try to dig up a file for you
Sent from my SGH-T839 using Tapatalk 2

if you would like to do I'd be very grateful!

yeah seems like you have the latest version right now other than the latest g2 ruu but you dont have super cid so you wont be able to flash that either
do you remember what happened when your phone stopped working? may help figure this out.
also just for fun what output do you get when you type this in fastboot
fastboot flash system system.img
dont worry that there is no image, im more concerned if your current bootloader will allow you to do this, i doubt it but why not
also check this
fastboot oem partition_test all

Like evry other flash I try:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
and the output of the partiton test:
(bootloader) [ERR] Command error !!!
I think the phone does not flash because the bootloader is locked? (S-ON)
I do not know how the device can not work anymore, I've bought via ebay ...'m a bit ripped off because it said that the phone worked

yeah a bit ****ty of whomever sold it to you, id try for a refund!
i take it you tried the basic stuff like booting to recovery and doing a factory reset?
this is real annoying too being without knowing the cause and having such limited access its hard to fix this thing, one of those deals where if i had it in front of me i think i could figure it out! but really you are going to need an updated ruu signed by htc to get this thing up and running if all the simple fixes havent worked... i guess you can see if debugging will work in recovery mode? if so then should still be fixable...

I tried a lot, can't boot to recovery because there is no.
it automaticly boots into RUU mode and if i try to boot it in to bootloader, system or recovery it stuck at the HTC logo.
How can I debugg the device? I know how to debug C# applications with Dot Net but a simple android phone is a lot harder
I could send my phone to your house if u think that would help?

Problem solved! partially i used a RUU from asia with a higher Version

dont send me the phone i live far away, send it back to whoever sold it to you and get the refund. hell ill sell you one that does work!
by debugging i meant to see if it were turned on on the phone, this is what allows for adb to work where you do the debugging. adb wont work in bootloader/fastboot mode, only in os and recovery. but again the problem is you can flash a recovery or os being you have a locked/shipped bootloader, the only thing to do at this point is to work with the limited fastboot commands you have or install a PC10IMG.zip, again the problem with this is they have to be signed by htc and be of a new version then your phone thinks you have installed... kinda stuck without some nicer options

Oh, I had forgotten that "adb" for android debugging bridge stands.
I do not have adb access only fastboot access, and a PC10IMG.zip does not work,like you already said it needs to have a htc signature.
Sending my phone to you was a joke.
But it is now almost entirely successful. I have an official RUU software used with a higher number, I had 2.42.405.5 and I have set up a foreign RUU and it worked "HTC Asia WWE 2.42.707.3"
I now have at least access to the HBoot, now I'll have to see how I can get S-OFF. flashing and "get_identifier_token" are still not working

Awesome news! So as of right now you have a stock ROM/Hboot/recovery?
If that is the case go right over to the xda wiki for the vision and root your phone with gfree!
Do it now before anything else brakes! Once you root (only use gfree method laid out in wiki) then everything else will be easy! Let me know how things go or if you need a hand!
*can't believe I glossed over that ruu!
Sent from my Nexus 7 using xda premium

He does not work well, he gets stuck on the normal boot logo.
If I run fastboot reboot bootloader he walks onto the boot screen. Install another RUU does not work, it stuck on "wait for bootloader"
Now the option "Image CRC" is added to the HBOOT menu, and I ran a factory reset that fails, that is what crashed my phone

can you post everything on your new hboot screen here? also everything that image crc says or any other options that may have appeared. also does it let you boot to a recovery?

Code:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
crc output:
7 times vibrate
Code:
calculating... please wait
osbl: 0x7EE4ED8C
amss: 0x0
hboot: 0x887F7ABB
boot: 0x0
recovery: 0x0
system: 0x0
Press power key to go back.
I could get into recovery but after I did the factory reset (what went wrong) I can't. I can only get into the bootloader by "VOL-" and "POWER" but if I from fastboot reboot-bootloader command doing he stack onto the HTC logo.

well according to this you have no system, kernel or recovery installed right now just a locked bootloader with all security flags on.
can you try another ruu, or flash the same one again? also look in here nipqer made these and they may help you out... actually he or ghul would be very helpful on this unless you can wait longer, i have some things im working on right now and i can look this over again tonight when i have some more time.
see if you can find them or another helpful one at FREENODE make a name and join #g2root

Yeah, yesterday I was @ the chat on freenode, they told me to try the asian RUU (a) I'll try the DZ_PC10IMG.zip form your link and if that doesnt work I'll wait for the next option
Thanks a lot!

I can't flash any RUU because after the command "reboot bootloader" he keeps waiting for the bootloader but the device gets stuck on the htc logo and doesn't boot to the bootloader, even if I set it from "VOL UP" + "POWER" to the bootloader the RUU installer status remains: "Waiting for bootloader"
After entering the bootloader menu is scans the SDCARD and finds the PC10IMG.zip
telling me: loading...[PC10IMG.zip], after that it's saying: Checking..[PC10IMG.zip].
After checking it just goes back to the Menu without asking me to update etc.
And I tried to flash a stock recovery but than I got a Signatue failure.

Try taking the pc10img off SD card or removing SD altogether
Then of will boot into fastboot, the in fastboot mode type
fastboot OEM rebootRUU
Sent from my Nexus 7 using xda premium

bricked htc m9

hi i was given an m9 so im trying to resurrect it first a few stats
soft version modified
locked
s-on
security warning
i can get into recovery mode
android recovery
htc/htc_himauhl/htc_himauhl
6.0/mra58k/buildteam02041257user/release-keys
then menu
reboot sys
reboot to bootloader
apply update from adb
apply update from sd card
wipe data/factory reset
wipe cache partition
power off
them some messages support api3
handle_cota_install install cwpkg to /cache/cota/cwpkg.zip
please any ideas??????????

First, we need to know more about your device.
You need adb and fastboot installed(I recommend Minimal ADB & Fastboot if you don't have already), HTC Drivers.
Put your phone in download mode and do "fastboot getvar all" remove imei/sn from output and post here.

lucyr03 said:
First, we need to know more about your device.
You need adb and fastboot installed(I recommend Minimal ADB & Fastboot if you don't have already), HTC Drivers.
Put your phone in download mode and do "fastboot getvar all" remove imei/sn from output and post here.
Click to expand...
Click to collapse
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
hi yes have adb just downloaded the original rru tyed to install via sd card but it failed

glinjik said:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
hi yes have adb just downloaded the original rru tyed to install via sd card but it failed
Click to expand...
Click to collapse
Do the command again from download mode not bootloader
Sent from my OnePlus 2 using XDA Labs

lucyr03 said:
Do the command again from download mode not bootloader
hi cant get into download mode it comes up in red
failed to boot to download mode press vol
up or down to back to menu
then htc log
then in red
this build is for development purposes only do not distribute outside of htc without htc's written permission failure to comply may lead to legal action
Click to expand...
Click to collapse

No download mode means no way to flash. Dead phone.

hi so i persisted and tryed holding power button vol up down etc and somehow got to this
HTC Download Mode
****locked*****
htc_himauhl pvt s-on
lk-1.0.0.0000
radio-01.01_u11440792_95.00.51130g_f
opendsp-15.6.1.00.522.8994_1026
os-3.35.61.14
feb 4 2016, 13:06:46(670363)
then the following
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
then in yellow
security warning
blah blah
sd card not mounted

glinjik said:
hi so i persisted and tryed holding power button vol up down etc and somehow got to this
HTC Download Mode
****locked*****
htc_himauhl pvt s-on
lk-1.0.0.0000
radio-01.01_u11440792_95.00.51130g_f
opendsp-15.6.1.00.522.8994_1026
os-3.35.61.14
feb 4 2016, 13:06:46(670363)
then the following
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
then in yellow
security warning
blah blah
sd card not mounted
Click to expand...
Click to collapse
I can't find a ruu for your phone.
Try to unlock bootloader, flash twrp and flash any marshmallow based sense custom rom.
Your only way to revert to full stock is s-off.
Sent from my OnePlus 2 using XDA Labs

hi is it possible to unlock bootloader from adb in download mode or twrp? is it possible to get soff in this mode?
i have the correct rru but i tryed to flash from sd
so i renamed the rru to opjaimg.zip
i get to flash menu press vol up to start flash
start ui_updating
it just goes back to bootloader

this is the rru i got
0PJAIMG_HIMA_UHL_M60_SENSE70_MR_Orange_UK_3.35.61.14_Radio_01.01_U11440792_95.00.51130G_F_release_472007_combined_signed.zip

after trying again managed to get to recovery mode
android recovery
htc/htc_himauhl/htc_himauhl
6.0/mra58k/buildteam02041257
user/release-keys
use volume up/down and power
then reboot system now
reeboot to bootloader
apply update from adb
apply update from sd card
wipe data/ factory reset
wipe cache partition
power off
tryed apply update from sd card
gives following
e:failed to set up expected mounts for install aborting
e: failed to mount / devlog (invalid argument) try emmc mount
e: cant find device node for mount point/devlog
the list goes on
the goes back to recovery mode

You need to rename it to 0PJAIMG.zip
The first character it's zero(0) not O
And boot in download mode and follow the on screen instructions
Sent from my OnePlus 2 using XDA Labs

that 0 might b the problem il try that and report back thank you so far

tried the official rom just goes back to bootloader gonna try a custom rom next fingers crossed

tried flashing from sd get
255
255
fail 255

glinjik said:
tried flashing from sd get
255
255
fail 255
Click to expand...
Click to collapse
Fail 255 indicated a broken SD card as far as i know.

il give it a go with a different sd card

Hello,
i have a big problem with my HTC one M9 OS 3.35.161.12( s-on, bootloader locked)
Recovery mode is broken , i'm able to enter into download mode, but when i want to flash a zip file i have problems to enter into RUU Mode because it is in a bootloop after i give the command "htc_fastboot oem rebootRUU" , it means the phone attempts to enter into RUU mode but it keeps just restarting in the black screen with htc Logo for 2 -3 sec.
can annybody pls tell me what can i do to repair the RUU mode?