Develop Bugs

[solved]Help My phone is dropping calls when I put it to my ear

Hi
Ive been trying all day to get this phone working properly, recently I s-off-ed my phone using alpharev, I attempted to flash the sensation rom which gave me a sdcard error cant mount mmcblk1 sdcard no such file....(mmcqblk0) ect... I fixed this with the fastboot enable command although I still cannot mount my sd either in recovery or when booted. I do have access to fastboot.
I flashed the new reflex rom 2.0.1 which works fine but when I make a call it drops, if I call tmobile it will drop the call, if I call again immediately after it continues with the call as if I'd never disconnected, if I call my partner the call is still connected at her end but if I call her again it just starts a new call and the other line is kept on hold....Wierd, Stranger still is that if I put the phone on speaker it does not disconnect, however if I turned speaker off and put the phone to my ear it disconnects after 10 seconds max.
Ive also tried this without the speaker on and away from my ear and it seems to stay connected, so this happening when I put my phone to my ear?
I dont think this is a technical issue as when I restored my phone to miui rom I had some months ago I was able to make calls without a problem although the signal was bad and it cut out if I moved too much but stayed connected more or less
Any Idea
So I tried re-partitioning my sd changing ext from 4 to 3 and back again, changing radio though I have only tried one, changing ril I have tried 3 of these, I cant make an goldcard because the although I have fastboot I cannot get adb to work, none of the apps for making goldcards detect my phone so I cant flash a new hboot or go back to stock, I am completely lost with this situation, can anyone help?

A while back I have had the same issue with line dropping as soon I put the phone to my ear. Your problem may be different, but maybe my findings will help you too.
I had an app installed, I think it was "Superpower" installed. It manages various settings for power saving, under which a setting for disabling things as soon as the screen turns off.
In my case this was the problem. Because as soon as you put the phone to your ear, the proximity sensor shuts down the screen automatically.
So then the app closed all connections, see? I uninstalled Superpower and it was OK again.
Maybe something similar in your situation, but it could be totally different as well..
Hope it helps!

ried uninstalling some likley coulprits to no avail i'm afraid, I am having trouble sorting out the usb brick I thought if I could get that working I might be able to resolve whatever is wrong, when I enter fastboot oem boot all it is giving me is
>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 0x21F04
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is T-MOB005
(bootloader) setting->cid::T-MOB005
(bootloader) serial number: HT******18
(bootloader) commandline from head: no_console_suspend=1 msmsdcc_sdioirq=
(bootloader) 1 wire.search_count=5
(bootloader) command line length =456
(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.08 androidboot.cid=T
(bootloader) -MOB005 androidboot.carrier=TMUK androidboot.mid=PB9920000 a
(bootloader) ndroidboot.keycaps=qwerty androidboot.mode=normal androidboo
(bootloader) t.serialno=3118 androidboot.bootloader=0.93.0001 no_
(bootloader) console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5
(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:20437 msec
FAILED (status read failed (Too many links))
finished. total time: 4.786s
there is no infotag, googled this and there is no info on this?

try to enable bluetooth if it doesnt then i know what the problem is

reaper7881 said:
try to enable bluetooth if it doesnt then i know what the problem is
Click to expand...
Click to collapse
I can't enable Bluetooth never have I been so happy to see that.
Sent from my HTC Desire using XDA App

i think you have a corrupt misc partition so u need to flash a new 1
let me compile the files for your CID:T-MOB005
THEN ILL UPLOAD AND TELL U HOW TO FLASH

does your usb connectivity work properly

I can fastboot but can't mount SD I can flash from SD if I use a SD reader just can't mount from recovery or pc
If u give my something to flash I can flash it from SD recovery
Sent from my HTC Desire using XDA App

first do fastboot oem enablqxdm 0
then extract and copy the two files in this archive to ur sdcard http://www.mediafire.com/?5h5593mcoblaykq
then install terminal emulator
THIS FIX IS ONLY FOR PHONES THAT ARE TMOBILE BRANDED
CID:T-MOB005
DONT TRY ON OTHER BRANDED PHONES

Ok done what now
Sent from my HTC Desire using XDA App

delete the post will all the fastboot oem boot since ur serial is still in ther
(bootloader) t.serialno=HT here 8 androidboot.bootloader=0.93.0001 no_
(bootloader) console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5

omg come to this page bro. but when u do then
move both files to /data
then open terminal then type
su
chmod 755 /data/flash_image

Im afraid that has not worked, I'm totally stumped

you havent flashed it yet lol
if you have applied the permissions then
in terminal emulator
/data/flash_image misc /data/mtd0.img
re check ur typing to make sure

then reboot and try to enable bluetooth if it enables then were done

delete the post will all the fastboot oem boot since ur serial is still in ther
(bootloader) t.serialno=HT HERE 8 androidboot.bootloader=0.93.0001 no_
(bootloader) console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5
serial number needs deleting in red on ur other post

Ok thanks Bluetooth enables yet to check usb but thank u so much hope this solves my call drop problem
Sent from my HTC Desire using XDA App

no problem bro

reaper7881 said:
no problem bro
Click to expand...
Click to collapse
Cheers reaper much respect all problems gone just by fixing the usb brick apparently it affects radio

i think i have soved the dropping calls
http://www.mediafire.com/download.php?7453qbvf78f5l50 and do the same as before

[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

Soft bricked with S-On

I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.

R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.

xunholyx said:
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.
Click to expand...
Click to collapse
I tried that, but it doesn't flash the ROM. Instead it starts flashing and then restarts back into TWRP midway. I tried flashing superuser the same way but to no avail.

You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.

R3dact said:
I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On
Click to expand...
Click to collapse
Are you sure it was ever s-off? S-off isn't need to flash ROMs, root, or a great many other things.
The only way you could have gotten s-off is with the sunshine app ($25); unless you did s-off with firewater before that method was disabled in Dec 2014.
R3dact said:
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Click to expand...
Click to collapse
There is rarely ever a reason to go into the Advanced section. But if you do, its called "Advanced" for a reason. You shouldn't be wiping any partitions on this device without understanding what it means, and what the results will be.
R3dact said:
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part)
Click to expand...
Click to collapse
If you haven't installed a new TWRP version in a year, there is no way its the "latest".
There is also no reason to guess at this. It says the TWRP version number right on the main screen of TWRP. You're always better of giving the specific number, instead of just saying latest. Folks on here often post they have the "latest" TWRP. But once prompted for the actual version number, I often find its something very old, often 2 years old!

R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Can you plz post fastboot getvar all here without the imei or serial#. We may be able to find you an RUU that may be able to recover your device.
Sent from my Nook HD using XDA Labs

ckpv5 said:
You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.
Click to expand...
Click to collapse
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================

smub said:
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================
Click to expand...
Click to collapse
Jesus. 1.54.651.8 OS? That phone has never been updated since forever.
Go to this thread for instructions and links to update your device.
You want the ones that aren't "Harman"
EDIT: You are S-Off, so keep that in mind (security: off from your getvar)
Feel free to send me a PM if you need further instructions.

M9 s-on/bootloader unlocked bricked

Hello, today i saw a good deal for a HTC M9. In advertisement photos were showing that it's stuck on bootloader, i thought nothing hard to rewrite stock rom and use it again, but now im facing some problems:
***Software status: Modified ***
***Unlocked ***
***S-ON ***
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
POWER DOWN
That is all I can see in this phone, previous owner said that it started rebooting while installing official update via usb cable, i cant tell if its true, but now i cant get in fastboot mode, if i choose BOOT TO RECOVERY or DOWNLOAD MODE phone only starts rebooting with black screen and HTC silver letters in that screen and some red words in the bottom of the screen.
Cant tell what CID or MID it is, but i found a blackfire research sticker on the original its box, so i guess it was sold in USA, and thats all.
fasboot getvar all shows only this:
C:\Users\Vartotojas\Desktop\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(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:FA568YJ00385
all:
finished. total time: 0.158s
Can you guys tell me what to do to get this perfect aluminium bar working?

Send it to HTC and let them repair it. That's the dead nand issue (c.f. the FAQ of the ReadMe thread) - a hardware issue.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Send it to HTC and let them repair it. That's the dead nand issue (c.f. the FAQ of the ReadMe thread) - a hardware issue.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Dont know if Lithuania has HTC repair center.. So you telling me that there is no DIY repair? Only way to do it myself is to find a cracked screen working m9 motherboard and to replace it?

There haven't been any reports about successful repairs of such dead nand phones, yet, aside from those cases in which the owners sent their phone to HTC.
However, that doesn't mean that a DIY repair is impossible. Therefore, if you successfully repair your phone it would be nice if you contribute a little guide to the community.
Sent from my HTC One M9 using XDA Labs

HTC M8 stuck on HTC One logo boot

Hi, I'll keep this short and simple. The phone is locked, with S-ON and everything is stock, it's running Lollipop 5.0 with stock sense. I've had my M8 since Oct 2014, served me well until Dec 2017 when I switched to the HTC 10. At any rate, I've migrated the majority of my content to the new phone except for a few like telegram secret chat etc. Since I made the switch, I usually keep the M8 switched off and I used it like 4-5 times only since December. My last usage was around early March.
Anyway, come last week. I turned it on and it got stuck on the HTC logo (first time ever). So I booted into recovery which is when I noticed that the software status is now modified vs Official despite never tampering with it. I cleared the cache and attempted a reboot and it got stuck on the "HTC One" logo but that' about it. The only way out of this state is power button + vol up which reboots it again and on and on this goes. It just refuses to go past that stage. Occassionally "android is optimising apps" appears for like 2 sec before the htc One logo shows up again and remains there indefinitely.
Any idea on what I could do to make it startup? Preferably without factory resetting. Thank you
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

So just an update, it seems that right now, my device goes straight into fastboot regardless if I choose power down (powering it on again boots it back into fastboot) or restart it (again goes into fastboot).

hemingway60 said:
Any idea on what I could do to make it startup? Preferably without factory resetting. Thank you
Click to expand...
Click to collapse
Probably unlikely to get the phone working and keep your data.
It appears your OS has become corrupted or damaged in some way (it happens). This would explain why it goes straight to bootloader instead of booting to OS. It may also explain why it says software "modified" when you haven't done any mods. Although I haven't seen that happen specifically (showing "modified" due to OS damage on an otherwise stock device); but it does seem logical it would say this (it is possibly reading the damage as some unknown "modification").
Your best bet is to restore factory image using RUU, following the instructions on the following post: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
RUU will wipe all data on the phone. But in the current condition (as mentioned), I don't think you have much choice anyway.
The RUU should restore the OS, in addition to updating it to Marshmallow (the last version HTC released for this device).

Hey, appreciate the reply. That's disappointing, considering the phone was literally just sitting inside a desk. Anyway, I recalled seeing this post : https://forum.xda-developers.com/showpost.php?p=64883695&postcount=6772 and noticed the OTA release code was 464427 vs 464360 on the RUU file. Is there any significance to this? Ironed bugs perhaps? If it's a better build, can I upgrade to that instead?
Thanks.

hemingway60 said:
I recalled seeing this post : https://forum.xda-developers.com/showpost.php?p=64883695&postcount=6772 and noticed the OTA release code was 464427 vs 464360 on the RUU file. Is there any significance to this? Ironed bugs perhaps? If it's a better build, can I upgrade to that instead?
Click to expand...
Click to collapse
Both are build number 6.12.401.4.
So I doubt there is any actual difference. If there was any change, it would have a different build number (6.12.401.5 or whatever).