yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] nkk71:
well with s-off, there's plenty of stuff that can be done, but very weird why it bypasses.... something must be wrong, do you have any idea what could have caused your phone to become "werid-ish"?? (anything??)

we can start by taking a look what's in that partition: reboot to TWRP, and do the following commands on your PC

adb shell dd if=/dev/block/mmcblk0p38 of=/tmp/mmcblk0p38_bak.img

adb pull /tmp/mmcblk0p38_bak.img

** warning "dd" is a very dangerous program with lot's of potential of bricking your phone **

then compress and upload that partition

also let's check the partition layout

adb shell cat /proc/emmc
[One (M8) Q&A, Help & Troubleshooting] Richylitschy:
Thank you already for your help!!

I pulled the partition and uploaded it, hopefully there is something to find.

However, applying the second code

adb shell cat /proc/emmc

just gives me this message:

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell cat /proc/emmc

dev: size erasesize name

C:\Program Files (x86)\Minimal ADB and Fastboot>

Did i something wrong or didnt the comment simply read anything on my device?

Greetings!

EDIT:

Got it now, went from system instead.

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell cat /proc/emmc

dev: size erasesize name

mmcblk0p1: 00100000 00000200 "sbl1"

mmcblk0p2: 076f7c00 00000200 "pg1fs"

mmcblk0p3: 00004000 00000200 "board_info"

mmcblk0p4: 00800000 00000200 "reserve_1"

mmcblk0p5: 00040000 00000200 "mfg"

mmcblk0p6: 017afc00 00000200 "pg2fs"

mmcblk0p7: 00040000 00000200 "sbl1_update"

mmcblk0p8: 00040000 00000200 "rpm"

mmcblk0p9: 00200000 00000200 "tz"

mmcblk0p10: 00008000 00000200 "sdi"

mmcblk0p11: 00400000 00000200 "hboot"

mmcblk0p12: 00500000 00000200 "sp1"

mmcblk0p13: 00100000 00000200 "wifi"

mmcblk0p14: 00008000 00000200 "ddr"

mmcblk0p15: 00100000 00000200 "dsps"

mmcblk0p16: 03c00400 00000200 "adsp"

mmcblk0p17: 00500000 00000200 "wcnss"

mmcblk0p18: 00800000 00000200 "radio_config"

mmcblk0p19: 00180000 00000200 "fsg"

mmcblk0p20: 04b00400 00000200 "radio"

mmcblk0p21: 00400000 00000200 "tool_diag"

mmcblk0p22: 03200000 00000200 "custdata"

mmcblk0p23: 00effc00 00000200 "reserve_2"

mmcblk0p24: 00100000 00000200 "misc"

mmcblk0p25: 00180000 00000200 "modem_st1"

mmcblk0p26: 00180000 00000200 "modem_st2"

mmcblk0p27: 01400000 00000200 "fataldevlog"

mmcblk0p28: 00001000 00000200 "debug_config"

mmcblk0p29: 00040000 00000200 "pdata"

mmcblk0p30: 00004000 00000200 "control"

mmcblk0p31: 00140400 00000200 "local"

mmcblk0p32: 00010000 00000200 "extra"

mmcblk0p33: 00100000 00000200 "cdma_record"

mmcblk0p34: 00000400 00000200 "fsc"

mmcblk0p35: 00002000 00000200 "ssd"

mmcblk0p36: 00040000 00000200 "skylink"

mmcblk0p37: 01900000 00000200 "carrier"

mmcblk0p38: 00040000 00000200 "sensor_hub"

mmcblk0p39: 01e00000 00000200 "devlog"

mmcblk0p40: 00002800 00000200 "cir_img"

mmcblk0p41: 02de6000 00000200 "reserve"

mmcblk0p42: 01000000 00000200 "boot"

mmcblk0p43: 01800000 00000200 "recovery"

mmcblk0p44: 05800000 00000200 "reserve_3"

mmcblk0p45: a8000000 00000200 "system"

mmcblk0p46: 18000000 00000200 "cache"

mmcblk0p47: b8000000 00000200 "userdata"

C:\Program Files (x86)\Minimal ADB and Fastboot>

EDIT 2:

Installed Whatsapp and tested the camera in there.

After opening the integrated camera app from whatsapp: Surprise!

It took 7 secs for the device to load up the camera, but it worked! The whole device was kinda laggy while the camera screen was active, but it worked!

This leads me to the conclusion that there must be some software error, and not a faulty hardware.

Is there no way to wipe/erase mmcblk0p38 to force the system to flash the sensor_hub.img with the next firmware and not just bypass it?

Greetings!
[One (M8) Q&A, Help & Troubleshooting] Richylitschy:
Update =

flashed firewaters eng hboot to get more fastboot commands.

Trying to use fastboot erase senor_hub in normal fastboot or fastboot RUU mode just ended in following error message:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase sensor_hub

erasing 'sensor_hub'...

FAILED (remote: partition is not allowed to be erased!)

finished. total time: 0.007s

is there rly no way to erase/overwrite the senor_hub parition?
[One (M8) Q&A, Help & Troubleshooting] nkk71:
are you trying to brick it?

RAW partitions get overwritten, not wiped, and the "bypassed" failure is usually caused by that img not being compatible with your phone (it's a safety feature)

anyway, you have HTCSHUB001.006.017.081 in there, which is the same version found in 1.54 firmware

2.12 fw has HTCSHUB001.065.023.009

2.22 fw has HTCSHUB001.065.023.012

3.28 fw has HTCSHUB001.065.030.018

you could "dd" the partition, but i don't recommend that cause you're bypassing the security/signature checks

can you post a "fastboot getvar all" (excluding IMEI), and a link to the thread of the firmware's you are trying to flash
[One (M8) Q&A, Help & Troubleshooting] Richylitschy:
Maybe that wasnt the smartest move i suppose haha

Anyway, i found out that on fw 2.22 my camera is working with all apps, even the HTC app. Sensors are still dead on 2.22, but camera is working. Maybe the NAND Chip is faulty?

Here is my getvar :

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.21331147A1.09G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.22.206.6

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

(bootloader) serialno: +++++++++

(bootloader) imei: +++++++++

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B10000

(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: 5e4b24e4

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.016s

I'm using different firmwares, but they all come from this thread:

http://xdaforums.com/showthread.php?t=2701376

Tried the o2___102 (since my phone is originally carrier branded) and the HTC___102, since i set supercid.

The firmwares I use are mostly from a german website, which hosts all firmwares for different rom versions and carriers:

http://www.handy-faq.de/forum/htc_o...resammlung_ruus_otas_backups.html#post2832635

I always use the signed ones.

Thanks for your help!
[One (M8) Q&A, Help & Troubleshooting] Richylitschy:
As i can See, your Sensor_hub is counting all the way up to 100while flashing. Mine never did that. I will try as soon as possible!

Thankd already very much and merry christmas indeed!
[One (M8) Q&A, Help & Troubleshooting] nkk71:
That is very weird indeed, dont know why this is happening (I do remember the sensor_hub partition taking quite some time when i flashed too, but it flashed fine)

You could dd the partition (thereby bypassing any security checks), though I can't really say what will happen, it's really not the recommended method of updating partitions

Maybe someone else has any ideas why this is happening??
[One (M8) Q&A, Help & Troubleshooting] Richylitschy:
As Long as it Works i'm happy with it. So just Disk dump the sensor_hub.img to the Partition?

Greetings!
[One (M8) Q&A, Help & Troubleshooting] nkk71:
well if you insist: (I really don't know why this is happening, and don't particularly like the below approach... i hope this doesn't break anything)

extract the sensor_hub.img from the firmware.zip and place it in your adb/fastboot folder

then while booted into TWRP

adb push sensor_hub.img /tmp/sensor_hub.img

adb shell dd if=/tmp/sensor_hub.img of=/dev/block/mmcblk0p38

then while still in TWRP, you can pull it again:

adb shell dd if=/dev/block/mmcblk0p38 of=/tmp/mmcblk0p38_new.img

adb pull /tmp/mmcblk0p38_new.img

and check if it was written properly, the version number is towards the end of the partition (last text before the trailing nulls)
[One (M8) Q&A, Help & Troubleshooting] Richylitschy:
HEy, thanks for your reply.

I diskdumped the partition, made no difference.

Im wondering, how do you extract the .img file?

Its not a system.img, so the tools wont work.

Thanks!
[One (M8) Q&A, Help & Troubleshooting] nkk71:
what to you mean "extract the .img file"?
[One (M8) Q&A, Help & Troubleshooting] Richylitschy:
Like, to open it.

See whats inside, get the version number etc.

How did you find out about the HTCSUB Version?

Greetings!
[One (M8) Q&A, Help & Troubleshooting] nkk71:
it's a RAW partition, it doesnt have a filesystem if that's what you mean (like /data, /system and /cache which are EXT4 filesystems)

i just used a hex editor, to look at the contents.... if you compare the backup you uploaded and the sensor_hub.img from 1.54 firmware.zip (using a hexeditor), you'll see they are 100% match

(well the backup you uploaded obviously has trailing nulls)
[One (M8) Q&A, Help & Troubleshooting] Richylitschy:
HEX Editor... Could have thought of that hahah

Thanks i will take a look!
[One (M8) Q&A, Help & Troubleshooting] Richylitschy:
[MENTION=2605798]nkk71[/MENTION]

Alright, CMD said it was successful:

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell dd if=/tmp/sensor_hub.

img of=/dev/block/mmcblk0p38

424+1 records in

424+1 records out

217466 bytes (212.4KB) copied, 0.094905 seconds, 2.2MB/s

However, the Version numbers doesnt match. I repulled the partition,

hex editor displayed

HTCSHUB001.065.023.012

Then i looked into the sensor_hub.img i flashed, it displayed

HTCSHUB001.065.030.018

Gonna try again, but i think that is all that can be done :/ faulty nand chip i suppose
[One (M8) Q&A, Help & Troubleshooting] nkk71:
well something has changed, cause the partition you uploaded earlier has HTCSHUB001.006.017.081

maybe you should do a full RUU restore (I think I saw a 1.54.401.10 or .5 RUU on xda), then a factory reset, then try again, maybe that could fix it
[One (M8) Q&A, Help & Troubleshooting] Richylitschy:
I'm gonna sent it to HTC now :/ Thankfully i noticed that IMEI is enough for their support to accept the device, no need for a receipt!

Thanks anway for your help [MENTION=2605798]nkk71[/MENTION] !

Have a good weekend!
[One (M8) Q&A, Help & Troubleshooting] nkk71:
you too

good luck with repair, hope it comes back soon
[One (M8) Q&A, Help & Troubleshooting] BloodyMoon95:
I got the same issue ... Any solution ?
[One (M8) Q&A, Help & Troubleshooting] krepsz:
did you found the way to fix the sensor hub problem?I have a HTC 10 now and by firmware flashing i have error to flash sensor hub img.
[Nexus 7 (2013) Q&A] mmm286:
Hi,

Lately I've noticed sensibility loss in my Nexus. I've installed Android 5, 4.4 and 4.3 and in all of them I see that I have problems sometimes when I press in the screen sometimes don't do anything.

Could you help me please?

Many thanks and sorry for my English!
[Nexus 4 Q&A, Help & Troubleshooting] DylonSaaied:
Hi everyone,

Today I tried to update my Nexus 4 with adb sideload, everything worked fine until it said that my build.prop has been modified.

Which at some point I remember I did change something but im not sure what it was.

Can any of you guys maybe provide me with the original build.prop file or atleast its contents so I can verify that I have the same things.

Exact error message: ( couldnt take a screenshot in recovery mode,)

Verifying current system. . .

''/system/build.prop'' has unexpected contents.

E:Error in /tmp/update.zip

(Status 7)

Installation aborted.

Thanks in advance :)
[Nexus 4 Q&A, Help & Troubleshooting] masterxxxxxl:
When you tell me, which android Version do you have currently installed, I can maybe give you.
[Nexus 4 Q&A, Help & Troubleshooting] DylonSaaied:
I am using 4.4.4 :)
[Nexus 4 Q&A, Help & Troubleshooting] jd1639:
Just flash the system.img from 4.4.4 with fastboot
[Nexus 4 Q&A, Help & Troubleshooting] DylonSaaied:
I should note also, that my bootloader is locked, so no flashing for me...
[Galaxy Note 4 Q&A, Help & Troubleshooting] jejunum:
Ok google was working beautifully when I got my phone, screen off etc.

Now it only works consistently when I am in the google now screen. I have turned s-voice on and off without any change.

I cant find any conflicts and was hoping someone would tell me the solution. I love google now and its always on capability.

Thanks!
[Nexus 5 Q&A, Help & Troubleshooting] dec1153:
Hi I was going to use chainfires method but the best the web page it only sates 5.0 with the build number LRX210- which is different to 5.0.1?

Is there any way to root then?
[Nexus 5 Q&A, Help & Troubleshooting] jss2:
of course there is a way to root 5.0.1.

use fastboot to either flash a custom recovery (TWRP is probably your best bet), or use fastboot to just boot into the custom recovery without flashing. Either way, once your in recovery, flash SuperSU (download here http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip)

done and done.
[Nexus 5 Q&A, Help & Troubleshooting] dec1153:
You sir are very wrong, you cannot flash that zip in recovery because it no longer works with lollipop... (Sigh)

PS. I have a custom recovery and unlocked boot loader so your suggestion are invalid
[Nexus 5 Q&A, Help & Troubleshooting] jss2:
actually, it does work. with 5.0.1, I'm rooted. Except when I flashed 5.0.1, SuperSU v2.40 hadn't yet been released, so I rooted with SuperSU v2.37, and then updated via the playstore when 2.40 came out. but it definitely works with Lollipop.

p.s. you need to have an unlocked bootloader to install a custom recovery (which is what I suggested doing). So in fact, my suggestion is completely valid and 100% relevant. In fact, I had assumed that you already had an unlocked bootloader when I posted.
[Nexus 5 Q&A, Help & Troubleshooting] dec1153:
Your point is again invalid and 100% incorrect- I have just tried and it has not given Me root. I have to manually re-root not flash the zip. See attachment
[Nexus 5 Q&A, Help & Troubleshooting] jss2:
yes, and the way to "manually re-root" is to flash the ZIP in a custom recovery. You the app installed, but not the SU binary. So flash it in TWRP.
[Nexus 5 Q&A, Help & Troubleshooting] gee2012:
CF Auto Root and flashing the superSU2.40.zip in recovery both root android 5(0.1/0.2). Did it myself and confirming root access.
[Nexus 5 Q&A, Help & Troubleshooting] Matrix_19:
You can root with the same chainfires files for 5.0, and then you can update supersu and twrp
[Nexus 5 Q&A, Help & Troubleshooting] JayR_L:
It astounds me how you have the guts to ask for help - then someone gives you an answer that is completely right and you do a hard six and blatantly flame them for trying to help you.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Crazy. Done it to me a few times. I even decided not to help him ever again some time ago, then took pity on him yesterday or the day before and the he did it AGAIN!

He's just a school kid, but you'd hope he would learn from his attitude, but apparently not.

What's worse, is he isn't even picking up the knowledge that people give him or reading the stickies. He's been Here pretty much a year in the n5 forum and cannot even be bothered to.understand the basics. Asks the most basic questions every time.
[X 2014 Q&A, Help & Troubleshooting] floepie:
It seems Moto is offering 50 off 350+ or 100 off from 500+ purchases. Is this discount also applied in countries outside of the US?
[8525, TyTN, MDA Vario II, JasJam ROM Development] Jygar:
Hi Guys

I have copied all the T-Mob customisations out, but have not uploaded them to the FTP, if you need them pls IM and I will send them to you.

This is not just the ExtROM, this includes the customisation cab that they have planted in the Windows folder too, inc XML files.

Hope you find them useful.
[8525, TyTN, MDA Vario II, JasJam ROM Development] StuBFrost:
I would find these very useful.

Any chance you could put on rapidshare or the like.

Stu
[8525, TyTN, MDA Vario II, JasJam ROM Development] darrellr:
Oh god yes! I upped to WM6 without thinking this through, just days before selling on my Vario2. I don't think I'll have to much problem putting my 'Phone on ebay with WM6 on it but I'm sure it will be be less 'saleable' without the T-Mobile look'n'feel.

Please PM/email me!
[8525, TyTN, MDA Vario II, JasJam ROM Development] jamiepyrite:
Hi, I'd also love a copy of this please if you could PM me!

Thanks very much :D
[8525, TyTN, MDA Vario II, JasJam ROM Development] chamelion:
me three! :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] sparkz:
Hi dude, any chance of the link as well. Cheers
[8525, TyTN, MDA Vario II, JasJam ROM Development] Jygar:
Lots of messages, added to MegaUpload:

T-Mobile Customisation Cabs
[8525, TyTN, MDA Vario II, JasJam ROM Development] londonmandan:
Hi, I'm new at this so I was wondering how do I do this as I have putthe files on my storage card clicked the autorun and nothing has changed.
[8525, TyTN, MDA Vario II, JasJam ROM Development] londonmandan:
Anyone know how to do this yet?
[8525, TyTN, MDA Vario II, JasJam ROM Development] papakeithjenkins:
Just click the files

If you are of a mind to, the easy way is to use WinRar to inpack the bundle into a folder on your comptuer with the phone synced using ActiveSync. Then run the autorun's. The second option is to put only the cabs that you want to use on the storage card and, one at a time, click on them and they will individually install on your device.

Either way should work. I hope this is helpful.

;)
[G2 Q&A, Help & Troubleshooting] playboypaul:
I was rooting and installing recovery and the threads I found said I need autorec.. So I followed instructions and bricked my phone, when on it stays in some kind of fastboot mode started, computer doesn't recognize either?? Im sure i installed wrong version, Ugggh pulling my hair out for 2 weeks now. Is my phone recoverable? My phone is the D803 version from rogers .. Please help will add a screenshot asap also.

Uggh pic won't upload but top left corner looks like this:

[820] Fastboot mode started [870]udc_start() And when plugged in it says: [820] Fastboot mode started [870]udc_start() [336150] -reset- [336150] -portchange- [336170] -reset- [336150] -portchange-*

[URL=http://s452.photobucket.com/us...aul1/Mobile Uploads/20141221_103021.jpg[/IMG][/URL]
[G2 Q&A, Help & Troubleshooting] Pepoto99:
Did you fixed it?I had the same problem and fixed that.
[G2 Q&A, Help & Troubleshooting] playboypaul:
No its not fixed, guy had it at the fix it store for 2 weeks and he couldn't do it either. Please help.
[G2 Q&A, Help & Troubleshooting] lynxrz:
If fastboot mode works wisely you can rescue your phone with flashing partitions via cmd

cmd

There is hope for you!
[G2 Q&A, Help & Troubleshooting] playboypaul:
When I get to a computer to check fastboot mode I'll see but everything I've tried to date gives me the same screen
[G2 Q&A, Help & Troubleshooting] Rotondo:
in your pc appears many partitions to format??
[G2 Q&A, Help & Troubleshooting] nivren:
fastboot flash img

Try this video, fastboot flash all partition img by youself. then, in download mode, flash TOT file.

https://www.youtube.com/watch?v=YEqEE9Qb8Sk
[G2 Q&A, Help & Troubleshooting] playboypaul:
I'm working in a remote area so I'll try it once I get to a laptop and let u know if it worked, thanks alot
[G2 Q&A, Help & Troubleshooting] playboypaul:
Trying now and command window is saying waiting for device, which has the same black screen with:

Fastboot mode started

Udc start

??

The guide says that I should be able to use but until I can get my device recognized I'm still stuck
[G2 Q&A, Help & Troubleshooting] playboypaul:
Awesome, I fixed my download and fastboot modes after Months of trying by following this simple tutorial.

http://xdaforums.com/showthread.php?t=2681089
[HTC One S] derkleinebroicher:
As there are again and again discussions concerning the minfree settings in CM12 roms, I decided to open this thread. If a moderator thinks, this is the wrong place for this thread, just move it, to where it belongs.

Obviously, since the last builds of CM12, the settings for minfrees cause some trouble. After a clean install of any rom, the minfree settings in trickstermod and in fauxclock are completely empty. In fauxclock the settings for OOM (out of memory) Score as well. Some people entered them manually, but I'm afraid, this won't help.

To really solve this, you have to do the following steps: open your file explorer, go to sys/module/lowmemorykiller/parameters. There you will find 5 files. Two of them do not have correct permissions. The first one, called adj, is for the OOM Scores. The other one, called minfree, is, you won't guess it, for the minfrees. :fingers-crossed:

As you see, both of them have only write permissions, but no read permissions. So I guess, the system will ignore these settings completely. I checked this, using cool tool from play store, very nice tool to show for example the actual free ram in your status bar. And in deed, the ram went down to 25MB, after I had opened a handful apps, and then my phone stopped working. I only could do a reboot.

Now the solution, which is quite easy: change the permissions into rw-rw-rw (666), and maybe change the group under owners into root (I'm not sure, if this is necessary, but it does make no problems, so why not).

Et voilà - if you now open trickstermod or fauxclock again, you will see the preset parameters. As you can see also, the minfrees there are really high. In another thread, there have been suggested the following settings, which are a good standard:

trickstermod 48/60/72/84/96/120

fauxclock 12288/15360/18432/21504/24576/30720

Important: In fauxclock, the minfree settings are not made in MB. You have to enter the so called "pages" for minfrees, which I can't explain exactly, what this is. In general, if you want to change minfrees in fauxclock, just take the settings in MB, you want to, and multiply by 256. This will give you the correct values.

BTW I don't think, it's a good idea, to change the OOM Scores, as long as you do not know exactly, what you're doing.

So, hopefully I could help a bit and clear some things up. But the final question to the CM devs remains:

is this a bug or is this a feature? :confused:
[HTC One S] Loreane Van Daal:
With me, those files were already chmod 666, owner root. I use latest liquidsmooth rom. What i did, prior reading your post, was that i set minfree in trickster, from my presets, than immedatly switched to faux, parameters were there, pressed apply, switched set on boot and rebooted. After that minfree r sticking in faux and trickster. Guess that my actions leaded to what you have described. Anyway, your way is much more convinient - at least one app less to use ;)
[HTC One S] mariachi62:
I don't get it... The directory you mentioned is empty on my one s as well as on my nexus 10 both with cm12.

However my settings stick since I use fauxclock.

One more thing I don't get is in fauxclock. It says "kilobyte" explicitly in the minfree settings although you said (and it stems to be) this strange pages value....
[HTC One S] derkleinebroicher:
You have to use your file manager with root permissions. Depending on which file manager you use, this can be done differently. The inbuilt CM12 file manager can be given root permissions in settings, in Root explorer for example you have to mount the directory as r/w.

An yes, you are right, fauxclock says, the settings are in kilobyte, but this is not correct. If you succeed to open the minfree file with your file manager, you will find there exactly the values, you have entered in fauxclock.
[HTC One S] mariachi62:
Damnit, you're right. Solid explorer doesn't show the content of the directory.... I use it a long time and always had the feeling solid explorer shows me all files...

Cm file manager works, thanks!