yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] ThOnDeR5:
It was ARHD 84.0 that is in this forum, and now i send you the outputs of the codes, and i did just what you tell me to do, i unchecked the boxes in order to put the codes and this is what appeas.

C:\Users\treme_000\Desktop\Nueva carpeta>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34DS900914
(bootloader) imei: 990001465737948
(bootloader) meid: 99000146573794
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN072****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d8b0f7651bb88c960f701ae91477674a
getvar:all FAILED (unknown status code)
finished. total time: 0.070s

C:\Users\treme_000\Desktop\Nueva carpeta>adb shell
~ # ←[6ne2fsck -fvy dev/block/mmcblk0p35
e2fsck -fvy dev/block/mmcblk0p35
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open dev/block/mmcblk0p3
5

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

~ # ←[6ne2fsck -fvy dev/block/mmcblk0p36
e2fsck -fvy dev/block/mmcblk0p36
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open dev/block/mmcblk0p3
6

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

~ # ←[6ne2fsck -fvy dev/block/mmcblk0p37
e2fsck -fvy dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

14 inodes used (0.01%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 6
15610 blocks used (3.29%)
0 bad blocks
0 large files

1 regular file
4 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
5 files
~ # ←[6nexit
exit

C:\Users\treme_000\Desktop\Nueva carpeta>
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Your device is Sprint, ARHD is not a compatible rom for your phone. Do e2fsck again with these block numbers :good:

adb shell

e2fsck -fvy dev/block/mmcblk0p37

e2fsck -fvy dev/block/mmcblk0p38

e2fsck -fvy dev/block/mmcblk0p39

exit

After that's done I think it's best to flash a Stock RUU
[One (M7) Q&A, Help & Troubleshooting] ThOnDeR5:
I still dont see much more storage than the 1759mb or so but he codes outputs where different.. here you go... im trying to push a sprint rom...

C:\Users\treme_000\Desktop\Nueva carpeta>adb devices
List of devices attached
FA34DS900914 recovery

C:\Users\treme_000\Desktop\Nueva carpeta>adb shell
~ # ←[6ne2fsck -fvy dev/block/mmcblk0p37
e2fsck -fvy dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

14 inodes used (0.01%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 6
15610 blocks used (3.29%)
0 bad blocks
0 large files

1 regular file
4 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
5 files
~ # ←[6ne2fsck -fvy dev/block/mmcblk0p38
e2fsck -fvy dev/block/mmcblk0p38
e2fsck 1.41.14 (22-Dec-2010)
dev/block/mmcblk0p38: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

15 inodes used (0.04%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 7
5267 blocks used (3.21%)
0 bad blocks
0 large files

3 regular files
3 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
6 files
~ # ←[6ne2fsck -fvy dev/block/mmcblk0p39
e2fsck -fvy dev/block/mmcblk0p39
e2fsck 1.41.14 (22-Dec-2010)
dev/block/mmcblk0p39: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

dev/block/mmcblk0p39: ***** FILE SYSTEM WAS MODIFIED *****

198 inodes used (0.01%)
15 non-contiguous files (7.6%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 187/1
568246 blocks used (8.34%)
0 bad blocks
1 large file

92 regular files
95 directories
0 character device files
0 block device files
0 fifos
0 links
1 symbolic link (1 fast symbolic link)
1 socket
--------
189 files
~ # ←[6nexit
exit

C:\Users\treme_000\Desktop\Nueva carpeta>

THe device still without system and cache partitions, i cant mount them via TWRP, and the sideload of a Sprint ROM failed for the same issue. Failed to mount system and cache partition.. Hoping you can help me
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
The stuff you've been trying to flash has probably messed up your partitions, I suspect you have a nonSprint compatible recovery also. This procedure will return everything to stock ;)

Download this RUU https://www.androidfilehost.com/?fid=22979706399752930

MAJOR EDIT:- Ok although this RUU is a zip file it appears it's not actually and RUU.zip, it's an RUU.exe. After you have downloaded the ruu extract it to your desktop. you should get an .exe file.

Connect fastboot usb in the bootloader and luanch the exe then follow the instructions to return your device to stock :good:

When it's finished the device will reboot :finger-crossed:
[One (M7) Q&A, Help & Troubleshooting] ThOnDeR5:
Sadly The RUU.exe program need the phone to be turned on to work, and wether the phone is on fastboot or bootloader mode, it doesnt rocgnize it... ANy tips ?
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
When you connect you usb cable in fastboot mode do you see fastboot usb on the bootloader screen. Check your drivers are installed correctly in device manager on your PC. Your phone should be listed as MY HTC in device manager.

The RUU should detect the device if the phone is showing fastboot usb, and your drivers are ok.
[One (M7) Q&A, Help & Troubleshooting] ThOnDeR5:
Now i can ell that my phone has come back completly fine except that i note that the phone doesnt get the call network any tips again.. thanks or all the help
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Your Welcome, As for the no service I'm not certain what to suggest, I assume as your device is Sprint you live in the US and use a CDMA network.

Your Firmware is very old you could try updating your phone to the latest software, Have you flashed a custom recovery or still with stock. If your still with stock connect your wifi. Go to Settings>About and check for software updates you should be able to update your device through OTA's
[One (M7) Q&A, Help & Troubleshooting] punkboyinsf:
that is a one in the command right?

at

ububtu@ubuntu:~$

I typed

1usb

1usb: command not found

am I doing something wrong?

I am booted into ununtu liveDVD latest version from their site..

do I need to run it from a usb stick?
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Check your command it should be

lsusb

first letter is l(L) not Number 1 ;) If it helps copy and paste it from this post.
[One (M7) Q&A, Help & Troubleshooting] punkboyinsf:
all that comes up (while fastboot is running) is a bunch of linux root hubs, the dell hubs, the system stuff and nothing that would be a htc device at all..

am I screwed?

---------- Post added at 06:03 PM ---------- Previous post was at 06:02 PM ----------

is there anything that can be done by opening the case?

since I am not the original owner and it's a weird dev edition running and it says tampered, there's no hope of htc helping I bet
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
If Linux doesn't see anything then the USB port is most likely borked. It can be replaced but your right I doubt HTC will repair it under warranty while its got Tampered flags.

Normally a functioning HTC one would show up as High Tech Computer corp device. Other possibilities are "QHSUSB_DLOAD" Normally a dead Motherboard or Firmware incomparability or "Possibly Qualcom USB Modem" or "Qualcom USB Storage device"

but if there is nothing then there's no data connection.

It's fair to say there's no fastboot usb in the bootloader either?

You could also try this command

dmesg

from this you will get a very long output. PM it to me if you want me to take a look see if there's anything in there.

Also the fact that you have the "This build is for development purposes" on the boot splash is very strange. Normally or to the best of my knowledge you would only see this on an s-off device but when you posted the bootloader information it shows s-on.

So it's possible the device was s-off at some point, Maybe this was a botched return to stock or something and they went back to s-on with some type of custom firmware but even then you would expect that message to go when you turn s-on.
[One (M7) Q&A, Help & Troubleshooting] punkboyinsf:
in luck.. after I told the guy there was no way to do anything since the USB connection ain't happening, he said he will refund me tomorrow.. So I'll have $50 back to try to get another phone.. my Amaze 4g is on it's last leg.. constantly slowing down, even on a fresh install of jelly bean rom.

Mostly, I have been disappointed with whatever hardware (namely the camera) that is incompatible with newer android versions that kept people from developing for this phone.. There are kitkat roms that work ok, but only using pmem and the camera exposure sensor goes haywire when running 4.3 and above.. I may have to settle for a One S which has working lollipop ROMs and I can afford since I have to buy a phone ourtight with no credit..

Thanks again for your shared knowledge, always happy to see a vibrant helpful thread on XDA, and you guys were fast and courteous. Cheers!
[One (M7) Q&A, Help & Troubleshooting] lukas22497:
Hello xda community,

i have a big Problem with my htc one.

It reboots all two minutes and it's s-on. Flashing a Firmware about ruu-mode Fails all time.. (Signature Error)

My getvar all:

C:\adb>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.57.0000

(bootloader) version-baseband: 4T.29.3218.08

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 6.09.401.11

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__102

(bootloader) battery-status: good

(bootloader) battery-voltage: 4069mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-6d8a0b9b

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

I cant give it in repair because i dont have s-off and can make the changes back.

IMEI and BASEBAND are shown as unknown in the Settings. i setted it up using the flightmode, otherwise after swiping the lock Screen away only the htc logo appears and it's going to reboot after the 2 minutes.

If i Flash cm via recovery, there is no reboot, but sunshine doesn't work there.

So i don't know what i could do now..

Please help me!!
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Unknown IMEI and baseband is rarely fixable with software depending on how it happened or what caused it, but post the output of

fastboot getvar all

Please remove your IMEI and Serial number before posting and we can see what your options are.
[One (M7) Q&A, Help & Troubleshooting] lukas22497:
have edited the old post..

Happend with locked Bootloader and all stock, no CHANGES!! After official ota..
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Well the fact that this happened while your device was stock and installing the OTA is promising but you shouldn't get your hope's up just yet. I have a procedure (experimental) that has repaired this issue on only 2 of the many devices I have seen with this problem. Unfortunately I don't have access to all the files you will need to carry out the procedure on your device. We may have to come back to this tomorrow. It's probably best if you refrain from flashing anything at this point.

You need the correct stock files to try and repair this issue but in some cases it's hardware related and can't be fixed with software. And just to give a little ray of hope both devices repaired with the proposed procedure were s-on and bricked by a failed OTA while the device was stock. You can read about one such case in this post http://xdaforums.com/showthread.php?p=57971938 the threads OP is still struggling with this issue but the linked post describes a different user problem in the same situation but is now fixed :good:
[One (M7) Q&A, Help & Troubleshooting] lukas22497:
Hey, i have the stock Firmware backup matching my device (nandroid).

But then, when i want to Flash the ruu, there is a signature error.

i dont know how to fix this. By the way i am not s-off. Can i Flash the Firmware.zip in the rebootRUU-Mode?

Which fail should be showed normally at the first Flash? i dont think that it should be the signature error..
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
I assume your trying to use the 4.19.401.x RUU? you will need to first downgrade your firmware as your s-off that should be possible.

http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/

Download the 3.62.401.1.zip from the above link. Flash the firmware in RUU mode. I assume you know the correct procedure to flash the firmware as you asked about the error on first flash. Let me know if you'd prefer some instruction on that.

After you flashed the firmware run the RUU.exe while the device is connected with fastboot usb and it should work.

Do you mind telling me how you got sunshine to work while you had this problem ?
[One (M7) Q&A, Help & Troubleshooting] lukas22497:
I think sunshine will not work because of the reboots. i come to pay with PayPal, then reboot.

What will happen if i Flash the 3.62... about ruu mode.

If i understood you right, i must be s-off to Flash the ruu and this is the big Problem...

Sry i forgot the not in the line with s-off.

I am not s-off.. sry i will edit this.
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Ok yeah that confused me a little. With s-on you have no hope of using the RUU :(

The stock nandroid I assume you made after the problem occurred so that probably is not going to help.

Give me 5 mins then check your private messages.
[One (M7) Q&A, Help & Troubleshooting] doggyollie:
Danny,

Unfortunately I am back. I got a replacement device for my screen issue through warranty. Now my phone won't take or make calls correctly. There is no audio. I looking to make the device stock again for another warranty return, which brings me here.

I have hboot 1.57 and I am unable to download firewater to attempt ot get s-off as it has been discontinued:( So I'm not sure I can get it back to 100% stock, can I? rumrunner wasn't succesful on 1.57.

Anyway, here is my getvar all

version: 0.5

(bootloader) version-bootloader: 1.57.0000

(bootloader) version-baseband: 4M.27.3218.14

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 5.12.502.2

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: X

(bootloader) imei: X

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0712000

(bootloader) cidnum: CWS__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 3891mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-1f512bb6

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

I am curently using this recovery:

TWRP v2.6.3.3

I am currently using this ROM:

Android revolution HD 81.0

Fastboot is showing:

Tampered and Unlocked

If I can't get it back to 100% stock then an ATT stock ROM might help. Unfortunately when I installed the custom ROM my Nandroid backup ROM got corrupted :(

Let me know what you think the best course of action would be.
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
No sound in calls is a know problem, Nothing to do with your device ;) It's something to do with google updates conflicting with system files. Update your rom to ARHD 84. The new rom includes a fix for this problem ;) But unless your speakers and mic are not working at all it's more than likely a software problem :good:
[One (M7) Q&A, Help & Troubleshooting] doggyollie:
Awesome, hopefully that'll do. I'll give it a whirl. Thanks as always.
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Your Welcome, as always :) If the problem persists after you update your rom let me know there's other things that can be done. Also make a nandroid of your current setup and start with a clean install of ARHD 84. A dirty flash may carry the problem to your new rom :good:
[One (M7) Q&A, Help & Troubleshooting] theclaytons:
Hi,

I sent a PM to the OP but writing this here in case that was wrong thing to do.

hi,

I've done something stupid and bricked my phone. It is a HTC one M7 Australian unbranded version that I converted to GPE version.

It was OTA to lollipop and I was trying to revert to stock. I installed a 5.11.980.x firmware file and was trying to flash a 5.11.401.x RUU zip file and after the first RUU zip install the phone went black and now I get no response or other feedback.

Windows detects this as a QHSUSB device but I cannot find a driver.

There are no LEDs on the phone and the screen stays dark.

Is this recoverable? Can you please help?

Chris.
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Well this could be one of two things. Either you borked your firmware most likely scenario if your device is s-off. In which case look here http://xdaforums.com/showthread.php?t=2770684

Or your mainboard has died in which case it's as good a dead. If you have warranty just send it for repair. If it is the mainboard they have no way of knowing if it was tampered or not and will replace the board or the phone :good:
[One (M7) Q&A, Help & Troubleshooting] doggyollie:
A clean install did the trick. Nandroid in progress.:D
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Glad to hear it :good:
[One (M7) Q&A, Help & Troubleshooting] theclaytons:
Hi [MENTION=1029271]danny210[/MENTION]1281,

Thanks for the quick response. I'm in the process of doing what is included in this post and as I understand it I need to do the following:

1. Install Linux (using Ubuntu) and run this on a USB drive attached to my computer

2. Extract the tool (on first page of this post) to the pen drive and put in folder that i can see from Linux

3. Run revive.sh as root and attach device to computer

4. flash new firmware provided in tool (5.11.401 version)

5. Fingers crossed this fixes it!

I tried this with DSL Linux (small download) but it did not detect my device. I am downloading Ubuntu now and will try this tonight. Could DSL version of Linux be reason my phone not detected by tool? Is it ok to run Linux from USB drive attached to computer and phone attached to same computer?

Is there anything else I'm missing.
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
I've never had the misfortune to need the Unbrick Project, But 32bit Ubuntu seems to be the best distro for the task. I have a guide here in this thread for setting it up with adb and fastboot maybe it can help http://xdaforums.com/showthread.php?p=54272479

If you get the same problem with ubuntu use the below 2 commands in the terminal while the device is connected and send me the output's. Probably best to PM them as the dmesg out put will be very long or copy them to a text file and attach it to a post here :good:

lsusb

dmesg

From these I will be able to tell you if this project should work for you or if the more unfortunate outcome is a dead mainboard. :good:
[One (M7) Q&A, Help & Troubleshooting] theclaytons:
Thanks for the quick reply. The guide has some stuff about downloading packages for fastboot/ADB etc. I presume this is not necessary?

If I do this part:

1. go here http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3

2. Then go here http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD

3. Then use these to create a bootable Linux usb drive with at least a 2gb persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from usb.

Then copy the tool (unlock bricked phone tool) to the USB stick in a folder called unbrick or similar then run revive.sh is that all i need to do? i.e. i do not need to download fastboot etc?

If that does not work I'll send output of the DMESG in a txt file - let's hope I do not need to!
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
You will need fastboot to complete the Unbrick procedure as you will be required to flash firmware if it works. Using windows to finish unbricking the phone may prove problematic because of the required drivers. Although once your back in the bootloader Windows may work for flashing the firmware, I'm not sure about that as I say I've never had to use it myself.

Linux doesn't need drivers for android phones because Android is built on the Linux Kernel ;) Hence the reason the unbrick script requires linux :good:
[One (M7) Q&A, Help & Troubleshooting] theclaytons:
Danny, thanks for all your help. I'm sitting here with Android 5.0.1 running on my One. No issues with the followed process. Might have even saved my marriage Lol.

I think I'll shy away from any new flashing for a while.

Chris.
[One (M7) Q&A, Help & Troubleshooting] banerjee_saikat:
Karbonn Titanium S5

I have a Karbonn Titanium S5 running on Jelly Beans. first I installed a kitkat ROM from the internet. Then I rooted it and removed all system apps. The system wont start and then it showed ENTRY FOR QPST DOWNLOAD on rebooting. I followed the post http://xdaforums.com/showthread.php?t=2459150 . I backed up my phone with Acronis true image. But unfortunately the boot sector 20 kb partition got overwritten. Now my phone wont even showing QPST download. It is not being recognized in Linax or windows. I messed up completely. what to do ?
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Happy day's :D Glad it worked out for you, I assume the wife wasn't to happy about you bricking the phone lol. Anyway glad you got it sorted. :good: