FORUMS

Bricked/Soft Bricked - Corrupted Internal Memory

1 posts
Thanks Meter: 0
 
By SamoDon, Junior Member on 29th September 2013, 08:38 PM
Post Reply Subscribe to Thread Email Thread
Hey guys so the problem is that it is bricked I think or its soft bricked so what did I do well I firstly unlocked the boot loader and then I rooted the phone and made a stock back up of my htc sense 5 and install htc one 4.3 Google edition on a sense 5 htc one so after a couple of hours of usage I didn't like it and I wanted to restore back to stock rom so I entered twrp recovery and restored the stock rom so it was working fine and then I went back into recovery mode and accidentally erased all my internal memory including the back up after rebooting the phone was stuck in the htc one boot logo so then I went onto my computer and not realizing I havenít turned on usb debugging and drivers not installed I have done a lot of things like flashing the zip in cmd and it wonít flash the zip so then I try it in adb and it wonít work in their tried ruu and for some reason not working in their trying side load and saying side load and then not side loading the data
So I tried to install the official stock rom and still wonít work

Please someone help me
 
 
29th September 2013, 08:44 PM |#2  
Guich's Avatar
Recognized Contributor / Themer
Flag Here
Thanks Meter: 3,352
 
Donate to Me
More
Wait, calm
So, boot in recovery, and use the command:
Code:
adb devices
and check if you can see the serial number of your phone.
If yes, you're done for flashing a rom from pc.
The Following User Says Thank You to Guich For This Useful Post: [ View ]
1st October 2013, 07:49 PM |#3  
I too have a simliar issue.. however when i check adb devices it doesn't show anything, when i enter sideloading mode i hear the computer signal it doesn't have the correct driver for it. is there anyway you could provide such a driver. i have tried the one that comes with htc sync manager and the one from the sdk
28th February 2014, 03:22 PM |#4  
Junior Member
Flag delhi
Thanks Meter: 0
 
More
Post same problem
i have same problem giving command adb devices it says
C:\Windows\fastboot>adb devices
List of devices attached


not able to run any rom
and mtp driver installation fail .in pc insted of sd card it shows i and h optical drive it just happen after flashing viper on 5 version before i had flash it in cwmr mode but accidently i run 5 version also in cwmr by viper it was instrcted to flash in twrp mode and it stuck off in recovery mod then i run rom in twrp but it shown error e:not avilabe and now not able to run to any thing

pls hel me
28th February 2014, 04:03 PM |#5  
Phoenix007's Avatar
Member
Thanks Meter: 13
 
More
First: You really need to have ALL drivers working for your phone, else you are stuck with an expensive paperweight ... this is crucial !!!
Second: Get S-OFF ! Used this guide, methode 1: http://forum.xda-developers.com/show....php?t=2632351
Third: Sideload a ROM. (Works best on USB2 connection!)

Me too had the problem, and after 2 hours of tinkering got my phone in working condition again.
I got it working again by SIDELOADING a ROM, it takes about 30 to 45 minutes, so be patient!
You wont see any action during the uploading to the phone, no fancy progress bar ...

I'm sorry I can't remember more, but I'm now a happy user for 10 days (bought the phone 11 days ago, rooted it and then got the No access to "SDEXT" ...)

Regards,
Phoenix

ps.:
I did it with the ROM in my signature, it's 1Gb big, so that's why it takes that amount of time to sideload!
Last edited by Phoenix007; 28th February 2014 at 05:15 PM.
The Following User Says Thank You to Phoenix007 For This Useful Post: [ View ]
28th February 2014, 05:26 PM |#6  
Junior Member
Flag delhi
Thanks Meter: 0
 
More
Post same problem2
sir i have all the drivers properly installed but then also it says mtp driver failed to install and when phone boots it stuck on htc logo and able to put in recovery mode but not able to go in cwmr and twrp mode
in my computer it shows to h and i optical drive and fails to run any recoveries and ROM.otherwise taking all adb commands.

and thanks for your instruction sir.
is their any way to get my phone in working mode pls help me
28th February 2014, 05:39 PM |#7  
Phoenix007's Avatar
Member
Thanks Meter: 13
 
More
So you don't have all drivers working ...

The MTP driver is the most crucial driver you have to get working or else every other task will fail ...

Drivers and tips can be found here: http://forum.xda-developers.com/show....php?t=2191279
Also give Windows Update a try to find the drivers needed ... I did ...

Also cleanup systemcache and Dalvikcache, available in the bootloader ...

Regards,
Phoenix007

Quote:
Originally Posted by vinodsharmaa77

sir i have all the drivers properly installed but then also it says mtp driver failed to install and when phone boots it stuck on htc logo and able to put in recovery mode but not able to go in cwmr and twrp mode
in my computer it shows to h and i optical drive and fails to run any recoveries and ROM.otherwise taking all adb commands.

and thanks for your instruction sir.
is their any way to get my phone in working mode pls help me

Last edited by Phoenix007; 28th February 2014 at 05:43 PM.
The Following User Says Thank You to Phoenix007 For This Useful Post: [ View ]
28th February 2014, 05:55 PM |#8  
Quote:
Originally Posted by vinodsharmaa77

sir i have all the drivers properly installed but then also it says mtp driver failed to install and when phone boots it stuck on htc logo and able to put in recovery mode but not able to go in cwmr and twrp mode
in my computer it shows to h and i optical drive and fails to run any recoveries and ROM.otherwise taking all adb commands.

and thanks for your instruction sir.
is their any way to get my phone in working mode pls help me

Quote:
Originally Posted by Phoenix007

So you don't have all drivers working ...

The MTP driver is the most crucial driver you have to get working or else every other task will fail ...

Drivers and tips can be found here: http://forum.xda-developers.com/show....php?t=2191279
Also give Windows Update a try to find the drivers needed ... I did ...

Also cleanup systemcache and Dalvikcache, available in the bootloader ...

Regards,
Phoenix007

This thread has been updated more recently: http://forum.xda-developers.com/show....php?t=2089508

and if you have this in device manager:


check my guide Post #1, FAQ #2.
1st March 2014, 03:24 AM |#9  
Junior Member
Flag delhi
Thanks Meter: 0
 
More
Post same problem2
sir as per your direction i followed it but not able to install mtp driver .but i am able to update frimware by ruu method and when flashing ROM it says zip is sending and stops with error.i think it is hard bricked in internal storage is died.
is their any way to come out from it should i go to technician .will he be able to solve my problem or not i will have Rs36000 paper weight.
Last edited by vinodsharmaa77; 1st March 2014 at 03:30 AM. Reason: full detail
1st March 2014, 10:09 AM |#10  
Phoenix007's Avatar
Member
Thanks Meter: 13
 
More
I almost can assure you, your memory did not die, there is only a link to that memory that is not correct, I'm sorry I can't remember more on how I did it in more detail, I already was happy when I got it working again ...

I did not make notes how I did it, stupid me ...
I'm doing this all from memory, but the most important thing still is, get all your drivers play nice with your phone, so no question marks in Device Manager.
That was also the hardest part for me to get that working.

And I work almost 20 years as a systems engineer on the Microsoft platform.
My knowledge about linux/unix is very slim.

Regards,
Phoenix007

Quote:
Originally Posted by vinodsharmaa77

sir as per your direction i followed it but not able to install mtp driver .but i am able to update frimware by ruu method and when flashing ROM it says zip is sending and stops with error.i think it is hard bricked in internal storage is died.
is their any way to come out from it should i go to technician .will he be able to solve my problem or not i will have Rs36000 paper weight.

The Following User Says Thank You to Phoenix007 For This Useful Post: [ View ]
1st March 2014, 12:29 PM |#11  
Junior Member
Flag delhi
Thanks Meter: 0
 
More
Post
sir today i went to gaffar market karolbagh new delhi and all shop technicians refused to check my phone now it all on xda devopes if any way to get out of the problem.


C:\Windows\fastboot>fastboot oem boot
... INFOBoot/Recovery signature checking...
INFOTZ_HTC_SVC_HASH ret = 0
INFOsetup_tag addr=0x80600100 cmdline add=0x00357914
INFOTAG:Ramdisk OK
INFOTAG:skuid 0x38D01
INFOTAG:hero panel = 0x940069
INFOTAG:engineerid = 0x0
INFOTAG: PS ID = 0x0
INFOTAG: Gyro ID = 0x2
INFOTAG: Compass ID = 0x0
INFODevice CID is not super CID
INFOCID is VZW__001
INFOsetting->cid::VZW__001
INFOserial number: FA37LS905781
INFOcommandline from boot/recovery image header: console=ttyHSL0
INFO,115200,n8 androidboot.hardware=m7wlv user_debug=31
INFOactive commandline length = 884
INFOactive commandline:
INFO poweron_status=1
INFO reset_status=0
INFO board_m7_wlv.disable_uart3=0
INFO diag.enabled=0
INFO board_m7_wlv.debug_uart=0
INFO userdata_sel=0
INFO androidboot.emmc=true
INFO androidboot.pagesize=2048
INFO skuid=0
INFO ddt=20
INFO ats=0
INFO androidboot.lb=1
INFO uif=T000
INFO td.sf=0
INFO td.td=0
INFO td.ofs=328
INFO td.prd=1
INFO td.dly=0
INFO td.tmo=300
INFO hlog.ofs=628
INFO un.ofs=696
INFO imc_online_log=0
INFO androidboot.efuse_info=4FSL
INFO androidboot.baseband=1.12.42.0906
INFO androidboot.cid=VZW__001
INFO androidboot.devicerev=0
INFO androidboot.batt_poweron=good_battery
INFO androidboot.carrier=Verizon
INFO androidboot.mid=PN0731000
INFO enable_zcharge=8
INFO androidboot.keycaps=qwerty
INFO androidboot.dq=PASS
INFO androidboot.mode=normal
INFO androidboot.serialno=FA37LS905781
INFO androidboot.bootloader=1.54.0000
INFO bpht=0x7D0
INFO lscd=0x1
INFO androidboot.nledhw=0
INFO androidboot.ddrmid=(0x3)
INFO acpu.footprint=FFFFFFFF
INFO abnrst=0
INFO zygote_oneshot=on
INFO kmemleak=off
INFO rpm_debug.enable=0
INFO console=ttyHSL0,115200,n8
INFO androidboot.hardware=m7wlv
INFO user_debug=31
INFOsetup_all_partition_atag:
INFO Partition[0].name=misc
INFO Partition[1].name=recovery
INFO Partition[2].name=boot
INFO Partition[3].name=system
INFO Partition[4].name=local
INFO Partition[5].name=cache
INFO Partition[6].name=userdata
INFO Partition[7].name=devlog
INFO Partition[8].name=pdata
INFO Partition[9].name=extra
INFO Partition[10].name=radio
INFO Partition[11].name=adsp
INFO Partition[12].name=dsps
INFO Partition[13].name=radio_config
INFO Partition[14].name=modem_st1
INFO Partition[15].name=modem_st2
INFO Partition[16].name=cdma_record
INFO Partition[17].name=reserve_1
INFO Partition[18].name=reserve_2
INFO Partition[19].name=reserve_3
INFO Partition[20].name=reserve
INFOValid partition num=21
INFOsetting_get_bootmode() = 9
INFOsmem 84505000 (phy 8F205000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
INFOTZ_HTC_SVC_ENC ret = 0
INFOTZ_HTC_SVC_ENC ret = 0
INFOTZ_HTC_SVC_DISABLE ret = 205643776 (0xC41E000)
INFOStart Verify: 0
INFO[RUMBA_S] firmware version: 3-46-43-33-0-0-0-0
INFO[RUMBA_S] ondevice version: 3-46-43-33-4-29-A1-0
INFO[RUMBA_S] firmware version already up-to-date
INFOpm8921_vreg_disable function, vreg_id = 8
INFOpm8921_vreg_disable function, vreg_id = 7
INFOpm8921_vreg_disable function, vreg_id = 37
INFOpm8921_vreg_disable function, vreg_id = 19
INFOpm8921_vreg_disable function, vreg_id = 34
INFOjump_to_kernel: machine_id(4358), tags_addr(0x80600100), ker
INFOnel_addr(0x80608000)
INFO-------------------hboot boot time:43694 msec
FAILED (status read failed (Too many links))
finished. total time: 3.122s

my all device status in oem boot mode is stated above.

pls help me

Read More
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes