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

[Q] RUU fails (remote: 51 partition update fail)

After flashing RUU fails with
Hi,
I'm just trying to get my Desire back to stock so I can sell it but the RUU that I have used in the past has failed. I've run the downgrader and flashed the stock ROM from Alpharev but now when I try to re-apply the RUU I get the black HTC screen with 4 warning triangles in the corners of the screen. If remove the USB an dreconnect then I get this....
---Alpharev----
BRAVO PVT3 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNW101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
RUU
1 Bootloader - Bypassed
2 Radio V2 - FAIL-PU
3 RADIO CUST - OK
4 BOOT - OK
5 RECOVERY - OK
6 SYSTEM - OK
7 USERDATA - OK
8 SPLASH1 - OK
9 SPLASH2 - OK
Partition update fail!
Update fail!
If I run fastboot oem boot then I get this...
C:\AndroidSDK\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 ORANG001
(bootloader) setting->cid::ORANG001
(bootloader) serial number: SH09DPL01345
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =423
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=0 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.11.05.27 androidboot.cid=O
(bootloader) RANG001 androidboot.carrier=ORANGE-UK androidboot.mid=PB9920
(bootloader) 000 androidboot.keycaps=qwerty androidboot.mode=normal andro
(bootloader) idboot.serialno=SH09DPL01345 androidboot.bootloader=6.93.100
(bootloader) 2 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:423443 msec
FAILED (status read failed (Too many links))
finished. total time: 99.905s
I've got a gold card in. I'm not sure if I'm missing a partition or if my goldcard needs recreating. Oh, and I have tried various RUU's but no luck with any of them.
Does anyone have any ideas? Let me know if you need any more info.
Many thanks,
Baz

Did you flashed Stock Hboot partition table before downgrader?

I did bravo_downgrade.img followed by bravo_alphaspl.img and then the RUU.
Is there another one I have to do?

have you tried to run the RUU again while on the four-triangle-screen? that solved it for me.
Sent from my HTC Desire using xda premium

Don't open two threads about the same problem.
SwiftKeyed from CyanogenMod with Transparent XDA App

@Tillus - I had tried re-running the RUU but with no luck. I've also tried various other RUU's but can't get anything.
@MatDrOiD - Sorry, I think that's a forum screw-up because I was safely tucked up in bed at 12:48am. In response to your post on the other thread, I have flashed bravo_downgrade.img As far s I know that's the hboot downgrader, no?

Looks like a radio brick to me. You can try a,few things but you may end up contacting HTC
Sent from my HTC Desire using XDA App

I did bravo_downgrade.img followed by bravo_alphaspl.img and then the RUU.
Is there another one I have to do?
Click to expand...
Click to collapse
Why did you flash the stock after the downgrader?
First Flash the stock, then the downgrader.
That's why the bootloader is bypassed and radio can not be updated.

Exactly.
First you have to flash the partition table image, and then run the downgrader... if you do it backwards results might be unpredictable.

You do not have to flash stock, downgrader is enough. After downgrader run RUU and it will succeed.

Thanks Dave, I'll give that a go as soon as I've had a cup of tea. I did things that way round because I had an issue once before and someone said that was the way to fix it and it worked so this time I just did the same again. I'll get back to you and let you know how things went.

Please use the Q&A Forum for questions Thanks
Moving to Q&A

OK, I flashed stock followed by the downgrader and then ran the RUU. My fault has changed to something that strikes me as being rather more serious. I have a feeling I was lead to the wrong RUU (RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704) as after I ran this my screen went off and hasn't come back on at all so I'm thinking this might be a RUU for the led version of the Desire. Also I no longer have Super CID which seems to be preventing me from doing any further flashing. I'm just looking into reflashing misc to see if that might help.
Current problems: No Super CID, No display, only boots into fastboot.
...oh bugger :-/

RockyGothyBaz said:
OK, I flashed stock followed by the downgrader and then ran the RUU. My fault has changed to something that strikes me as being rather more serious. I have a feeling I was lead to the wrong RUU (RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704) as after I ran this my screen went off and hasn't come back on at all so I'm thinking this might be a RUU for the led version of the Desire. Also I no longer have Super CID which seems to be preventing me from doing any further flashing. I'm just looking into reflashing misc to see if that might help.
Current problems: No Super CID, No display, only boots into fastboot.
...oh bugger :-/
Click to expand...
Click to collapse
why if you have dozen of ruu available, newbie always choice the damn old one??? U have to choice the damn last one! What wrong with the latest? How you can flash a such old ruu?
The next time, ask a confirmation before flash an ruu.

RockyGothyBaz said:
Current problems: No Super CID, No display, only boots into fastboot.
...oh bugger :-/
Click to expand...
Click to collapse
IF it boots into fastboot, you can flash a newer RUU, try the latest one, not one of the oldest

Hey guys,
I've also got a device from a mate who completely screwed it up. I also tried to flash the latest RUU but it failed.
My understanding is that with the device blocked at the HTC with 4 triangles boot, my only option is to use a Goldcard because of S-ON.
However my understanding is that to create a Goldcard you need to do this from your device whilst its working. Is it possible to create a goldcard without the device?
Thanks.

makcrellon said:
Hey guys,
I've also got a device from a mate who completely screwed it up. I also tried to flash the latest RUU but it failed.
My understanding is that with the device blocked at the HTC with 4 triangles boot, my only option is to use a Goldcard because of S-ON.
However my understanding is that to create a Goldcard you need to do this from your device whilst its working. Is it possible to create a goldcard without the device?
Thanks.
Click to expand...
Click to collapse
Read my thread.

[Q] Desire Z stuck at boot. Solved for a while. Stuck again!

Hello,
This will be a long read. Thanks in advance for your patience. I'm not skilled in android or mobile phones in general, so I'll try to be the most descriptive possible on this.
I have a HTC Desire Z phone which suddenly has ceased to work. I've checked a bunch of threads that list some steps to follow, but I've noticed that all the steps are for rooted devices, so I'm unsure about them. The amount of information found is overwhelming.
This phone is not under warranty. I've had it like for two months so far. Apparently, bought as new (boxed, etc) from a store remnant. So I cannot send it to service, etc.
What happened is as follows. 2 days ago I was doing like 3 or 4 simultaneous updates (apps like firefox, skype, google maps...that I remember) via wifi. Some ended, some were about to end I think. I left the phone unattended for a while, and when I came back, it had a black screen with a red triangle / exclamation icon. I never had similar problems before. Maybe a few restarts because it was unresponsive (which I assume it's normal for a smartphone nowadays).
After this, I removed the battery, put it back, and turned the phone on. It started as usual, but as soon as it connected to the net, when the small synchronizing icon (circling arrow) appeared at the top of the screen, it froze. So I repeated the battery thing and as soon as it started, deactivated the synchronization, the wifi and the data connection.
I don't exactly remember if I was able to deactivate all the three, but the phone froze again. Only got a white screen with the HTC logo in the next boot. The usual "quietly brilliant"-or something message never appeared. Stuck forever. Repeated a few times and same thing.
So I entered the "Volume Down + Power Menu", and hit Factory Reset. It seemed to restart, showed a black screen with a circling green + phone icon and an animated progress bar below (not showing progress, just animating), and after a while the screen went totally black. Some seconds later, the phone vibrated 7 times. And it still does this if I repeat the factory reset operation.
BTW, I don't understand why at the right-end of the progress bar, there's a small micro-sd icon, like if the phone were trying to read or write anything from/to the sd card (a factory reset should not need anything external, IMO). Anyway, this process behaves exactly with or without an sd card in the slot.
The phone does not start after this vibration-thing. I have to remove the battery, wait some seconds and put it back. After this, it starts and immediately shows the previous animation and does the vibration thing, like if it was in a Factory Reset "loop" (quoted because I have to totally turn it off for it to happen again).
-I assume that the vibration is some sort of error code, but I've not found any source for this, which is kinda stupid.
To break that "loop", I have to start the phone again, with the Volume Down thing, to get the HBOOT menu:
Code:
VISION PVT SHIP [B]S-OFF[/B]
HBOOT-0.85.0013
MICROP-0424
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
After some searches, I noticed that the "S-OFF" part might be an indication that the phone is rooted. At this point, I'm not sure. However, I had (i.e., several days ago) tried to copy/create some file in the filesystem using either the ADB Shell, or a shell application. That was not possible. Isn't this a good indication that the phone was not booting as root?
BTW, phone is not visible through "adb devices". But "fastboot devices" lists it OK.
A command like "fastboot flash recovery ..." ends with
Code:
FAILED (remote: not allowed)
This gives me the idea that the firmware memory (or whatever is named) is read-only at this time (?), so what the "S-OFF" means then?
Anyway...
That happened on day 1 after the problem. Then I found this thread:
http://forum.xda-developers.com/showthread.php?t=2474781
And went through the RUU route, accordingly.
Downloaded the file RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.3_Radio_12.56.60.25_26.10.04.03_M_release_224299_signed.exe from shipped-roms.com, and ran it.
That worked. The OS was reinstalled and the phone was able to boot as factory default.
Side note: This RUU thing actually did a subtle downgrade. The previous installed version was 2.42.405.4, according to the program.
So I began to set up the phone, configured an APN, connected to the Internet, went to the Market and downloaded one required app. It installed successfully, but as soon as I tried to execute it, the phone froze and had to remove the battery to turn it on again. And it went back to the original problem, stuck at boot, white screen + HTC logo. Any subsequent RUU application execution gets hung in the "Reboot to bootloader..." part. Nothing starts to be copied. The phone (in the FASTBOOT USB menu) is also frozen after this. :crying:
I also tried a previous RUU: RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe from the same source. Same behavior.
I have no idea about what happened. The phone was running again, with working phone network, wifi, gps, sd filesystem, etc.
Oh, almost forgot it. Before finding the RUU solution, I tried putting an official Gingerbread firmware in the PC10IMG.zip file, in the root of the SD. The file was parsed OK by the phone, but when I proceeded with the update, it got stuck in the first item (updating "boot" or so - I don't remember). I think this is because the "not allowed" condition I previously got with the fastboot application.
OK. These are some details I got AFTER running some fastboot commands in the phone, now that it's boot stuck again.
First of all, this is my current HBOOT menu header:
Code:
VISION PVT SHIP S-OFF
HBOOT-0.85.0013
MICROP-042[B]5[/B]
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
>fastboot devices
Code:
SH115RT01882 fastboot
>fastboot oem boot
Code:
(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 super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::[B]11111111[/B]
(bootloader) serial number: SH115RT01882
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =493
(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=11111111 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=ALL androidboot.mid=PC10***** androidboot.keycap
(bootloader) s=qwerty androidboot.mode=normal androidboot.serialno=SH115R
(bootloader) T01882 androidboot.bootloader=0.85.0013 zygote_oneshot=off k
(bootloader) memleak=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:125342 msec
FAILED (status read failed (Too many links))
finished. total time: 7.101s
After this, the phone is hung in the white screen / HTC logo part.
>fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0013
(bootloader) version-baseband: 26.10.04.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 2.42.405.3
(bootloader) serialno: SH115RT01882
(bootloader) imei: 320864213579134
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: [B]PC10*****[/B]
(bootloader) cidnum: [B]11111111[/B]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4133mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 81c588a7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
See that kinda fake modelid and cidnum? I certainly have no idea about what do they mean, but isn't that a proof that the phone is rooted?
>fastboot oem list_partition_emmc
Code:
(bootloader) index, type, start, num
(bootloader) 0, 0x4D, 0x1, 0x3E8
(bootloader) 1, 0x45, 0x3E9, 0x80
(bootloader) 2, 0x46, 0x469, 0x2328
(bootloader) 3, 0x5, 0x2791, 0x43186E
OKAY [ 0.016s]
finished. total time: 0.016s
>fastboot oem check_emmc_mid
Code:
(bootloader) Manufacturer ID, MID=15
(bootloader) eMMC should be samsung
OKAY [ 0.008s]
finished. total time: 0.009s
>fastboot -w
Code:
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.001s
Short question. Any ideas? :fingers-crossed:
Thanks again for your help!

S-OFF means you can basically write to (almost) any part of the device and disables signature checks on firmware images....

riahc3 said:
S-OFF means you can basically write to (almost) any part of the device and disables signature checks on firmware images....
Click to expand...
Click to collapse
Makes sense.
But "fastboot erase userdata" should work then. It only gets "FAILED (remote: not allowed)".
ADB does not find the phone.
RUUs get stuck at the "Reboot to bootloader..." part. Phone also gets stuck here.
I'm stuck too...

S-off, like riahc3 said, means security flags are removed but this is for firmware so it doesn't mean rooted which would be for software. Which from what you've stated I doubt it was rooted.
The shipped bootloader though won't allow for many fastboot commands, that's why you get errors
The cid has been changed to allow for any firmware to be flashed, but the bad news is the Samsung chip which is prone to failure,
At this point I would attempt to flash an engineering bootloader and then custom recovery and os, hopefully you will be good after this
http://forum.xda-developers.com/showthread.php?t=2348266
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
S-off, like riahc3 said, means security flags are removed but this is for firmware so it doesn't mean rooted which would be for software. Which from what you've stated I doubt it was rooted.
The shipped bootloader though won't allow for many fastboot commands, that's why you get errors
The cid has been changed to allow for any firmware to be flashed, but the bad news is the Samsung chip which is prone to failure,
At this point I would attempt to flash an engineering bootloader and then custom recovery and os, hopefully you will be good after this
http://forum.xda-developers.com/showthread.php?t=2348266
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your reply.
I tried this with the engineering bootloader:
>fastboot flash hboot 0.84.2000_hboot-eng.img
Code:
sending 'hboot' (1024 KB)...
OKAY [ 0.187s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.189s
Is "hboot" a special name? According to the fastboot help, after "flash" comes a partition name, and I don't find that in the list returned by "fastboot oem boot".
Anyway, still "not allowed".

hboot, bootloader, SPL, these are all interchangeable terms, you will not see it listed in oem boot because that doesn't list partitions
Being you still have a shipped bootloader that command won't work, you need to flash it as a PC10IMG.zip, the link I attached has a thread on bricks and one on fastboot, read those and there is a link to a PC10IMG.zip that should hopefully work for you
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
hboot, bootloader, SPL, these are all interchangeable terms, you will not see it listed in oem boot because that doesn't list partitions
Being you still have a shipped bootloader that command won't work, you need to flash it as a PC10IMG.zip, the link I attached has a thread on bricks and one on fastboot, read those and there is a link to a PC10IMG.zip that should hopefully work for you
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You mean, copying that file in the SD and booting, right?
Will do.
In that link you attached, there's a section with "Important Brick Info!", with another link to "When all Else Fails Boot From SD".
They talk about booting CM7.1 from recovery. But I don't see (at least, it's not clear for me) any engineering hboot in the file they attach. Is this something completely different? And it seems it's for rooted phones...
When you say "Being you still have a shipped bootloader that command won't work, you need to flash it as a PC10IMG.zip", these two things are pretty clear for me:
I DO need the engineering hboot.
I would need to put this engineering hboot image inside a compressed file named PC10IMG.zip in the sd card, and boot the phone with that.
If this is the case, I have the image at hand, but I've noticed that all the PC10IMG files include a file named "android-info.txt" and I don't know how to create this one (maybe it's easy).
Is this the path to follow?
Thanks for the time you're investing on this.
PS. What is this then?
Code:
(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
Copied from what "fastboot oem boot" returns.

Its checking boot sequence not listing all partitions
See the 30th post
http://forum.xda-developers.com/showthread.php?t=
Hopefully you can flash the PC10IMG.zip and will then have an engineering bootloader and a custom recovery, with these you will have a much higher likelihood of fixing your phone, but being you have the chip prone to failure you may need to boot from sd
You'll need a custom recovery in order to boot from SD, this is a last resort though
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Its checking boot sequence not listing all partitions
See the 30th post
http://forum.xda-developers.com/showthread.php?t=
Hopefully you can flash the PC10IMG.zip and will then have an engineering bootloader and a custom recovery, with these you will have a much higher likelihood of fixing your phone, but being you have the chip prone to failure you may need to boot from sd
You'll need a custom recovery in order to boot from SD, this is a last resort though
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ugh, you didn't specify a thread id in that link.

Bump

What happened after the flash?
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
What happened after the flash?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, you sent me some link and addressed me to the 30th post, but the link was incomplete.

http://forum.xda-developers.com/showthread.php?t=1728208y
Sent from my SGH-T699 using XDA Premium 4 mobile app

demkantor said:
http://forum.xda-developers.com/showthread.php?t=1728208y
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi.
Code:
Parsing...[SD ZIP]
[ 1 ] RECOVERY
[ 2 ] SPLASH1
[ 3 ] TP
[ 4 ] TP
[ 5 ] BOOTLOADER
[ 6 ] RADIO_V2
[ 7 ] RADIO_CUST
Answered Yes to "Do you want to start update?".
Frozen as soon as it begins the update:
Code:
[I][ 5 ] BOOTLOADER Updating[/I]
.

Emmc is bad, need to replace motherboard, sorry
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Emmc is bad, need to replace motherboard, sorry
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, I've already contacted HTC for this. I have no idea about how much would it cost, but they can do it.
Anyway, taking advantage from your expertise here, do you think if in these cases they replace just the chip or the whole motherboard?
Also, -and I prefer to ask it here first before showing myself as a daring retard-.... This device is the euro version...do you think it makes sense if I request a change to the usa version? (I'm talking about the HSDPA/3G frequencies here). I'm pretty sure this can be done only at hardware level (probably a single chip replacement?), but if they replace the motherboard, I don't see how difficult would be just "putting this instead of this one", considering that we don't use the euro frequencies here either. Is this a valid request?
Thanks for your help.

It will cost more than its worth to have HTC do it, unless somehow you still have a warranty but that would be surprising. Yes the radio bands differ between the desire z and g2, what I would suggest is buying a broken one from eBay for cheap and swap logic boards, if you dig I bet you can find one for 40$ or less which will be much cheaper than sending it to htc
Sent from my Nexus 7 using XDA Premium 4 mobile app

Buy a new one bro..

Hello.
I sent my phone to HTC and they replaced the motherboard. The whole cost was still cheaper than buying a new phone, so I went that route.
Since they get the replacements from their available stock, I had not much control on what they were using. So guess what...Samsung eMMC chip again.
Three questions:
1-Is this chip really that bad and I'm condemned? :laugh:
2-Rooting my phone would give me any options if the same problems happens in a future?
3-Considering that:
a) I have the old motherboard
b) a Sandisk eMMC chip does cost about 10 bucks
c) I know someone with the right tools to replace this chip.
If the same problem happens in a future and I replace the chip myself, should this work immediately of should I have to "prepare" this chip with some special software?
Thanks for all the support given with my issue.

The Samsung emmc is prone to failure but that doesn't mean it will die in a week, a month or a year, some have had it work for years
Rooting and true radio s-off is amazing and will help with other problem, just not a fried emmc, not even JTAG can fix this
Soldering a new chip is tricky if you haven't done real fine soldering before, so be careful doing it yourself
Depends how and where you bought the chip, many vision specific ones come preloaded with firmware/software
If it doesn't you will need JTAG equipment to flash it
Hope all goes well for you!
Sent from my Nexus 4 using XDA Premium 4 mobile app

[Q] [RUU] Error: 152. Unable to Restore TMob One M8

Hi, thanks for reading.
I was running the latest version of CM on my One M8. Decided I wanted to revert to stock ROM to regain HTC camera and wifi calling functionality. Figured an RUU would be the easiest way.
Here's where I probably screwed up. Downloaded and ran the RUU for ver. 2.xxx from HTC. Forgot to relock bootloader, but it rebooted early back into CM no problem. Relocked bootloader. Ran again.
I should have known to pause when I saw that my version was 1.5xx but it seemed fine with updating versions as part of the process.
Then it failed again, error 152. Was able to reboot into CM again this time.
I did some googling and reading and saw one guy say that he was able to fix by simply running the RUU again once it was in the "four exclamation marks in triangles" screen, which is where I was after the next try, so I ran again. Another error 152.
So finally I realized maybe I needed the 1.5xx RUU. DL'd that, tried running, "error, wrong version." Because now it thinks my phone is on ver 2.xxx.
Now I can't get the phone to boot into recovery or into bootloader. No clue where to go from here. I'd really appreciate your help. Gosh I screwed up.
The last lines in the RUU log (1.5xx) are:
Code:
<T205408><DEBUG><OUT>Execution time is 6(s)</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAIL43 main version check fail</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
and the prior try, RUU log 2.xx:
Code:
<T202916><DEBUG><OUT>(bootloader) [RUU]WP,system,37</OUT>
</DEBUG></T202916>
<T202917><DEBUG><OUT>(bootloader) [RUU]WP,system,42</OUT>
</DEBUG></T202917>
<T202939><DEBUG><OUT>(bootloader) ...... Failed</OUT>
</DEBUG></T202939>
<T202941><DEBUG><OUT>(bootloader) current_image_number=0</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>Execution time is 216(s)</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAIL51 partition update fail</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAILED (remote: 51 partition update fail)</OUT>
</DEBUG></T202941>
<T203947><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T203947>
<T203948><DEBUG><OUT />
</DEBUG></T203948>
</LOG>
Thanks.
Update 1: can recognize device using "fastboot devices" but not "adb devices." haven't tried pushing/pulling anything yet. Saw someone in another thread tried installing via command line. Not sure which .zip I should use, as there are a ton of options on XDA, or if this is what I should try next.
Update 2: there are seemingly two versions of the "four exclamation points" screen: one is dim and has the orange led showing and the other is bright without led. Bright without LED is what I got after "flashboot reboot-bootloader". Worried that the bright one may deplete battery.
3: Since I can't otherwise boot into a recovery, should I try to flash a recovery?
4: Not sure if this is useful but:
Code:
getvar version-main is indeed listed as 2.22.531.5
phone CID T-MOB010
phone MID 0P6B13000
5: Phone was S-ON. Wasn't able to get S-OFF using the free method.
6: Was reading another thread with similar error (but One X), this seemed to be useful to the one guy:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ###
(bootloader) imei: ###
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s
7: Tried to flash a stock recovery:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery Tmo-M8-2
.22.531.5-recovery.img
target reported max download size of 1830612992 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.533s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.430s
8: Tried to create some RUU .zips per this method http://forum.xda-developers.com/showthread.php?t=2534428 but the zips say that archive is corrupted. EDIT: MD5's for the .exe's do check out.
9: Used a zip repair to repair those RUU .zip's. Noticed that their android-info files have "hbootpreupdate:12" but my phone has "hbootpreupdate:11" might that be an issue?
Sad Edit: I tried some stuff, nothing seemed to work. Freshly downloaded from an alternative mirror the 2.2xx RUU and booted into RUU via fastbooth before running it. Everything said it went perfectly "CONGRATULATIONS ROM UPDATED! Rebooting!" etc.
My phone is bricked. Never woke up from that reboot. My computer keeps trying to recognize the device via usb, but nothing.

I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?

grim489 said:
I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?
Click to expand...
Click to collapse
Yeah I tried unlocking the bootloader while fastboot was still recognizable, but it wouldn't work.
Not sure about the unsigned zips thing. Would that also go for the RUU? I thought those were signed/straight from HTC.
I'll try it once more, but it should have been fully charged last time I gave it a try. Computer shows an intermittent "QHSUSB_Bulk" but not sure where to go from there. Found threads for other HTC phones and tried their methods, but it got to the point where the one guy was supposed to go through Ubuntu to manually install individual .imgs to the phone, but I think he had somehow managed to get fastboot to work.

Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.

grim489 said:
Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.
Click to expand...
Click to collapse
Yeah it's especially weird because I thought with S-ON it was supposed to be hard/impossible to override ?boot.ini (not sure, don't quote me on that) anyway. But yep, won't boot at all.

HTC One M9 stuck on fastboot bootloader

Hi !
One of my friend ask me to try to save his One M9 phone, that seems to be bricked.
Here is the context :
- I absolutely don't know what he did, and it seems he don't either...
- The phone state is : Software status : Modifed, S-ON, and LOCKED
- I can't have another screen that Fastboot bootloader
The only options in the bootloader menu are :
REBOOT : it works
REBOOT TO BOOTLOADER : it works
BOOT TO DOWNLOAD MODE : does not work (Failed to boot to download mode)
BOOT TO RECOVERY MODE : does not work (Failed to boot to recovery mode)
POWER DOWN : it works
I tried a lt of things, and read a lot of threads before posting this one.
What i can say for the moment is :
- RUU flash using exe : does not work, i get an error saying the battery is too low
- RUU flash using SD card (extract rom.zip, renamed 0PJAIMG.zip, and put on the root of SD card) : zip is not detected at boot
- Getting bootloader unlocked : does not work, because fatboot oem get_token_identifier command seems unknown (probably because oem commands only work in download mode for this phone)
- Getting S-OFF : seems impossible without OS, as it needs Sunshine app installed...
- Few fastboot commands are OK (devices, getvar all, ...) but most of it are refused because of S-ON
- No adb commands are working
Here is the output of fastboot getvar all :
Code:
D:\ANDROID\RUU\RUU>htc_fastboot getvar all
(bootloader) version: 0.5
(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
(bootloader) serialno: FA56GYJ01267
all:
finished. total time: 0.094s
htc_fastboot finished. total time: 0.718s
So, from your experts point of view, is this phone definitely bricked, or is there a way to save it ?
Thanks for your precious help guys !

Hey! I have the exact same problem. Anyone knows how to fix that?
I unrooted, stocked and relocked the bootloader. Everything went fine first, was using the phone about two days. But after a restart I'm stuck in bootloader and can't boot to download nor recovery mode.
Phone is only working with fastboot commands.
I also tried these steps OP tried and everything is the same.
I tried to flash hosd file and this works, but still not able to boot to download mode.
The HTC One is an unbranded EU model with 3.35.401.12 (<- but I think there's nothing on the phone right now)

i am also facing same problem with 2 htc one m9 which i have, i also have XTC2CLIP box which is professional tool for all htc devices, i can S-off with this box of all htc phone even no os needed, but phone should accept bootloader mode & ftm mode, & in this case where we can only goto fastboot mode, S-off command not working in state... i spend lot of time but no luck... but i still believe its only software bug & can be solve with fastboot commands. because i aslo read about same problem on htc X model. & they use fastboot command for this problem. but these commands not working on m9 case.

no solution for this? I have one m9 here exatly with the same situation, already did all your debuging with the same results

Hi there! I'm new here, created an account specially for replying to this thread:
So I'm having the same problem, phone (EU M9) died on it's own. Everything is stock.
Tried all of the above, also no results...
Here is my log from "fastboot getvar all"
Code:
C:\Android>fastboot getvar all
(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
(bootloader) serialno:HT54NYJ04596
all:
finished. total time: 0.147s
If anyone has any ideas left, I'm happy to try them. For now, it's an ugly paperweight

If it died on its own and in a stock state then you can safely assume it's dead. Most likely nand failure.
Ps, dont all m9 serials start with an "F"?.
Beamed in by telepathy.

thank you

My guess is it tried to do an OTA update overnight, don't know exactly where it went wrong.
By the way, I do get some ADB communication:
First reboot to bootloader (so it doesn't say "Security Warning"), then select 'boot to Recovery Mode' and wait for the red triangle.
If it doesn't reach that point, reboot to bootloader once more. If it does reach the red triangle: hold the Power button and press the Volume Up button once. You can then release the Power button and Recovery Mode should become visible. Note that I tried several options in this menu including "Install from ADB" and "Install from SD Card", but both gave errors.
Hope someone can use this information.

I have exactly this same issue. Sounds like NAND failure? Nothing to be done about it?

KaiLoi said:
I have exactly this same issue. Sounds like NAND failure? Nothing to be done about it?
Click to expand...
Click to collapse
If it's spewing failed to mount errors then yes, dead phone. Only htc will be able to fix it.
Beamed in by telepathy.