Develop Bugs

[Q] Why can't I flash my NAND - HBOOT 0.76.2000

What is up with fastboot and 0.76.2000??? In theory, I should be able to use fastboot to flash the pieces of a nandroid backup or the stock rom, but I've run into some odd issues.
I tried flashing system, boot, userdata, and cache on my G2 and it seems to hang- for over 10 mins. The little status bar sometimes starts to fill up, but not always. If it does actually finish sending the file, then the write fails. Is there some fastboot oem unlock command to use to enable flashing?
I've used fastboot to flash recoveries, radios, and SPLs on my G1, so I think it is working properly otherwise. I can flash the nandroid *.img files on my G1 and there are no problems using 1.33.2005 (AKA Death SPL) and an unmodified recovery. (I didn't have much luck with 1.33.2003 (Safe SPL) and an MTD patched recovery.)
Why doesn't this work on the my G2?
Code:
INFOversion: 0.5
INFOversion-bootloader: 0.76.2000
INFOversion-baseband: 26.03.02.26_M
INFOversion-cpld: None
INFOversion-microp: 0425
INFOversion-main: 1.22.531.8
INFOserialno: XXXX
INFOimei: XXXX
INFOproduct: vision
INFOplatform: HBOOT-7230
INFOmodelid: PC1010000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3872mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: ENG
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 977d3036
INFOhbootpreupdate: 11
INFOgencheckpt: 0
I'm using a Mac with fastboot via the developer site, but I also tried the fastboot that gets built with the aosp roms.
And yes, I can restore these parts via CMW recovery, but it seems like the eng hboot is missing some functionality.

I don't know why it's not working for you, so I'm clutching at straws here. But are you using the original HTC USB cable ? I had some odd issues myself when using a third-party cable.

I've use the original HTC cable with my G2 and it doesn't work.
On my G1, I've been using a non-HTC cable and it works fine. I've noticed some charging issues with a specific non-HTC cable and charging my G1, but I think it's just one bad cable.

Just to clarify, the fastboot binary that you've got is from the Android SDK (for Mac) from the AOSP site ?

I have one from the HTC site for ADP1 and the other gets compiled with the aosp source code when the rom is cooked. I don't recall the path but it's something like out/.../tools/
I didn't know that the new SDK comes with fastboot.
Sent from my CyanogenMod Vision

gee one said:
I have one from the HTC site for ADP1 and the other gets compiled with the aosp source code when the rom is cooked. I don't recall the path but it's something like out/.../tools/
I didn't know that the new SDK comes with fastboot.
Click to expand...
Click to collapse
I know that mine works fine using the fastboot from the SDK, and the eng hboot (I have a DZ). Worth a try to see if it's something about your fastboot binary ?

steviewevie said:
I know that mine works fine using the fastboot from the SDK, and the eng hboot (I have a DZ). Worth a try to see if it's something about your fastboot binary ?
Click to expand...
Click to collapse
You can flash the nandroid images to restore a rom? Mine seems to work fine otherwise and will even flash some of the smaller nandroid parts, but certainly not system.img and data.img on my G2. It works fine on the G1.
I'll dig around the SDK when I get home to make sure I'm using the lastest version of fastboot.
Sent from my CyanogenMod Vision

gee one said:
You can flash the nandroid images to restore a rom? Mine seems to work fine otherwise and will even flash some of the smaller nandroid parts, but certainly not system.img and data.img on my G2. It works fine on the G1.
Click to expand...
Click to collapse
I haven't tried it myself, but I'm 99% sure that you can't just flash a nandroid image for system via fastboot etc, you have to restore via nandroid.

steviewevie said:
I know that mine works fine using the fastboot from the SDK, and the eng hboot (I have a DZ). Worth a try to see if it's something about your fastboot binary ?
Click to expand...
Click to collapse
I reinstalled the latest SDK and there is no fastboot included. (I updated first, but reinstalled for the sake of completeness.) The only sources of fastboot that I know of are from the HTC developer site and from AOSP. The AOSP version has a few more features, such as being able to set the kernel base address and the NAND page size.
steviewevie said:
I haven't tried it myself, but I'm 99% sure that you can't just flash a nandroid image for system via fastboot etc, you have to restore via nandroid.
Click to expand...
Click to collapse
I did try this on my G1 (one) and was successful. I was able to restore my backup as if I had restored it via recovery. On my G1, however, I am using Amon-Ra 1.7.0, not ClockworkMod. The *.img file seem to be similar, so this seems to be an issue with fastboot not being fully functional with the G2/0.76.2000.
Anyone want to try flashing the *.img files via fastboot? "fastboot flash userdata data.img" should be enough to tell if it's working. I'm using a Mac with CM6.1.1/CMW2.5.1.3, in case that matters.
BTW, the reason that I think this is important is because if this works, people can flash parts of the stock rom or RUU or PC101.img or whatever, without flashing the locked bootloader, which leads to brick-o-rama.

gee one said:
I reinstalled the latest SDK and there is no fastboot included. (I updated first, but reinstalled for the sake of completeness.) The only sources of fastboot that I know of are from the HTC developer site and from AOSP. The AOSP version has a few more features, such as being able to set the kernel base address and the NAND page size.
Click to expand...
Click to collapse
Sorry but I beg to differ, at least for the Windows version of the SDK. Version 8 (latest) of the Windows SDK starter package comes with fastboot.exe in the "tools" folder. adb has been removed from the starter package and comes in the platform tools module. I see that you use a Mac, so that might be different.

gee one said:
I did try this on my G1 (one) and was successful. I was able to restore my backup as if I had restored it via recovery. On my G1, however, I am using Amon-Ra 1.7.0, not ClockworkMod. The *.img file seem to be similar, so this seems to be an issue with fastboot not being fully functional with the G2/0.76.2000.
Anyone want to try flashing the *.img files via fastboot? "fastboot flash userdata data.img" should be enough to tell if it's working. I'm using a Mac with CM6.1.1/CMW2.5.1.3, in case that matters.
BTW, the reason that I think this is important is because if this works, people can flash parts of the stock rom or RUU or PC101.img or whatever, without flashing the locked bootloader, which leads to brick-o-rama.
Click to expand...
Click to collapse
You're asking someone to experiment ? I wouldn't try it, because as far as I know, Clockwork mod uses YAFFS format for its backup images. They're not just an image dump of the partition, which is why I'm pretty sure you can't just flash them back on with fastboot.

I've tried it on my G1 and G2. I'm asking someone to confirm if it's an HBOOT issue or if it's isolated to me.
The Nandroid files from Amon Ra on the G1 are YAFFS format as well. Both data.img and system.img unyaffs the same whether they are the G1 or G2.
I think there is extremely low risk. If it's an HBOOT issue, it probably will hang during the send and never get to actually flashing the NAND. If it's just my issue and it works on other phones, then it should flash fine, similar to what I did on my G1.
Sent from my CyanogenMod Vision

This problem is ALL about the backup image that you are trying to restore.
There are two ways to create a backup.... direct binary copy of the partition (i.e. "dd"), or copying the contents of the filesystem (i.e. "cp -pr"). CWM/Vision uses the latter. Older nand devices typically use the FORMER.
If you want to fastboot flash a backup, your backups need to be direct binary dumps, which you can create using the "dd" command.
I.e. "dd if=/path/to/system/partition of=/sdcard/backups/system.img"
The backups made by CWM are a weird proprietary kind of backup (didn't look too far into it, since it is utterly uninteresting, or it may be yaffs, but WHY? It serves no purpose to use yaffs....). There IS a benefit to this kind of backup though (not to the use of yaffs though): it doesn't duplicate free space. The tradeoff is that you can't just flash it back. Remember that you have a total of 2.1 GB of internal storage on the device. A dd-type backup will take the exact same amount of space on your sdcard.
A much better way to do a backup is to create a SPARSE FILE backup.
Something along the lines of "dd if=/path/to/system/partition | cp --sparse=always /dev/stdin /sd-ext/backups/system.img" would cut out all the large spaces that are filled with nothing but zeros. Typically, on a magnetic disk, you would need to preceed this with a "dd if=/dev/zero of=/path/to/filesystem/to/be/backed/up/zerofile; sync; rm /path/to/filesystem/to/be/backed/up/zerofile; sync; umount/path/to/filesystem/to/be/backed/up" in order to clear all the random garbage from files that have already been deleted. MMC is a bit of an oddball though, with wear levelling, unused blocks get tagged and sometimes cleared, and sometimes the mmc device will "always return zero" for "unused" blocks, so it may not require you to zero everything out.
Note about sparse files: You need to store the sparse files on a filesystem that supports sparse files.... that means EXT, you can NOT create sparse files on a vfat filesystem.
When you READ a sparse file, offsets are automatically corrected and zeros automatically injected where applicable.
Now IF it is creating a yaffs backup, the same thing holds true.... yaffs is NOT COMPATIBLE WITH eMMC!!!! You can't flash a yaffs image onto the eMMC and expect it to work!

Thanks - I didn't realize that there was a change with backups, which explains the "issues" that I was having.

[Q] flashing gingerbread leaked testversion with su

all,
I have been reading several threads, wiki's, forums etc etc. Some seem somewhat helpful, others are showing details I don't see using my phone.
What is the thing I'd like to accomplish here:
I have a std HTC desire Z 1.82.405.1. It's not rooted, It doesn't have eng-boot etc. Neither I'd want to downgrade it, to get S-off at this moment. The only thing I want to do is to be able to load the gingerbread leaked version pc10img.zip.
I have been searching high and low as said -- haven't found a single article that exactly explains what to do.
I have linux, adb and fastboot available. I also have psneuter and the like. I even have the required downgrade f/w available. I only want to go that route if I see enough reason (for me) to be able to become root. (And emp root works fine btw thru psneuter/adb shell)
Now, when I try to load the leaked version:
1) I installed the pc10img.zip file /sdcard
2) started the phone in the boot menu, the zip fie gets loaded
3) the zipfile gets verified
and then, all stops. E.g. I haven't found at this point a piece of documentation what to do to flash this image in the phone. Recovery talks about update.zip and obviously the filename is different.
So what's next. What should I do to have this actually flashed?
And again, I have been reading several threads of over 30 pages, more wiki pages than fingers, been googling etc etc. You sometimes get quite far and then read after 16 pages that a special rom is needed, or eng-boot or.. etc.
Somewhat frustrating. :-(
Anyone who can tell how to proceed after step 3...?
Roeland

Hmm it's silent ..
all,
I have asked a few people off list and some of them were helpfl. Others were hinting that if someone asks a question, he or she must be stupid or something.
Anyways. I have been tedousy reading several threads that most of the time end up in being not the original thread anymore.. SOmeone said that my CID may be not the one in the android-info.txt file etc etc.
modelid: PC1011000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
mainver: 2.30.405.1
hbootpreupdate:12
is what it states.
if I exec from linux (output slightly edited):
[email protected]:~/temproot> adb shell /data/local/tmp/psneuter
property service neutered.
killing adbd. (should restart in a second or two)
[email protected]:~/temproot> adb shell /data/local/tmp/gfree_verify
gfree verify_cid returned:
@CID: HTC__E11
@secu_flag: 1
@SIMLOCK= 00
so the model is one of the android-info.txt file. Still it only loads the zip file,
verifies and that's it.
So I'm basically stuck.
I can downgrade the system to 1.34.70.73 make it a permanent root and s-off but then the question is -- how can I upgrade back to the current or future version? I know that there is a website that contains several roms and I even have found out partly what rom is for what audience.
http://shipped-roms.com/index.php?category=android
But then. if 1.34.x is installed does HTC notice this and direct push OTA the version I have now?
Really I tried my best in searching for answers bit it's adaunting task, especialliy if many times people drift away in a thread. So halfway reading may be interesting but then you might not have noticed that you needed clockworks recovery or (insert anything here).
The wiki:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
gives the most information here including linkts to other hepful resoures. STill the OTA question -- where..?

and why not going root anyways
well, there are several con's and pro's for being root on the device.
yes, I'd like to have busybox and su installed. But do I want s-off? I'd say -- handy. On the other hand, it makes the system more vulnerable.
I see several applications tht require root access. So yes may be worthwhile. but no I don't want to install an overclocked kerne, or specific thins or rmk* stuff etc.
I am happy withthe stock but sometimes may beed elevated privilegs.
I understand that the leaked version here of gingerbread contains su and may be hand to test a few things.
Other trouble why I hesitate is, that several sites report that for instance contacts are synced against google and yet, I have 400+ entries with half of it including additional details, links, mail addresses and on. If there are 20 on google.... I followed the guidelines to sync all but it appears to do a very small subset.
So I could use phone-nanny to have a backup and backupeverything (titatium only works of you have root..) but then how sure can I be that all is in place after I flashed, rooted and the like?
Most of the 'backup your stuff' messages think that you *are* already having root, which obviusly isn't the case.
If I would not have this phone filled with loads of information I just could flash and go for it. However, at this moment it may cause a lot of pain if I cannot recover. So I hope that the two recovery ways are enough.....

[Q] Bought M8, many problems/questions

Hi guys,
I've rooted my phone before and installed custom roms so not a complete noob but not far off. Anyway, down to my problems.
I bought phone off a guy, cheap. M8 running stock 5.0.1. Didn't get to look over phone properly, all looked ok. Then I noticed the problems.
Camera working but wont take pictures, says insert an sd card before using camera.
Cannot take screenshot as says no storage available (phone and sd card empty almost)
Can sign into my Google account, use gmail, photos, music but not hangouts or playstore. They will not load.
Cannot download apk's or zip files through chrome browser, so cannot get a file manager
Baseband, imei and kernel look ok but Seial number is some weird mix of characters and pictures, like <]#~q?/
Recovery is installed and phone is S-off. Computer recognizes phone but cannot see adb devices. This means I cannot change modelid from this weird serial number.
Some details
CID: GOOGL001
HBoot: 3.19.0.0000
Radio: 1.21.213311491.A04G
What would you guys recommend? Backup and install a sense rom through recovery? I have a feeling that will not work because of the serial no/modelid issues.
Any help would be greatly appreciated, I am broke now with a semi useless phone!! Please!!
Cheers guys
EDIT: ISSUE SOLVED
Was able to install a working backup through twrp (obtained elsewhere) This backup contained my serial no, modelid and imei details.

I would try to return the phone for a refund, if you can. As it seems like the phone is all manners of messed up.
If you purchased with no method of return or refund . . . well I'd never buy a phone that way. But if that is the case, we'll try to get her working again.
---------- Post added at 10:25 AM ---------- Previous post was at 10:23 AM ----------
beardo81 said:
What would you guys recommend? Backup and install a sense rom through recovery? I have a feeling that will not work because of the serial no/modelid issues.
Click to expand...
Click to collapse
It looks like the phone has been fully converted to GPE, or was GPE in the first place. So you can't flash a Sense ROM until you fix the partitions by RUU. So you are right that you can't do that unless you change the CID and MID.
To be clear, what color is the hboot screen?
---------- Post added at 10:27 AM ---------- Previous post was at 10:25 AM ----------
beardo81 said:
Baseband, imei and kernel look ok but Seial number is some weird mix of characters and pictures, like <]#~q?/
Recovery is installed and phone is S-off. Computer recognizes phone but cannot see adb devices. This means I cannot change modelid from this weird serial number.
Click to expand...
Click to collapse
Serial number and model ID (MID) are 2 completely separate and different things. Which one is messed up, or are they both screwed up?
---------- Post added at 10:50 AM ---------- Previous post was at 10:27 AM ----------
beardo81 said:
Computer recognizes phone but cannot see adb devices.
Click to expand...
Click to collapse
You're trying adb with the OS booted, right (not in bootloader, which won't work)? And debugging is enabled in Settings?
Does fastboot work (needs to be in bootloader-fastboot mode)?

redpoint73 said:
I would try to return the phone for a refund, if you can. As it seems like the phone is all manners of messed up.
If you purchased with no method of return or refund . . . well I'd never buy a phone that way. But if that is the case, we'll try to get her working again.
Unfortunately not an option, private sale and seller has 'disappeared'
---------- Post added at 10:25 AM ---------- Previous post was at 10:23 AM ----------
It looks like the phone has been fully converted to GPE, or was GPE in the first place. So you can't flash a Sense ROM until you fix the partitions by RUU. So you are right that you can't do that unless you change the CID and MID.
To be clear, what color is the hboot screen?
Hboot screen is black, looks normal, states I have S-OFF and CID-GOOGLE001
---------- Post added at 10:27 AM ---------- Previous post was at 10:25 AM ----------
Serial number and model ID (MID) are 2 completely separate and different things. Which one is messed up, or are they both screwed up?
They both are messed up, when I check through fastboot I see different weird characters. Very odd. Like a mixture of chinese numerals, small emoji and characters, maybe 8 of them.
Just to be clear though, I have box and checked imei online, it is a real M8
---------- Post added at 10:50 AM ---------- Previous post was at 10:27 AM ----------
You're trying adb with the OS booted, right (not in bootloader, which won't work)? And debugging is enabled in Settings?
Does fastboot work (needs to be in bootloader-fastboot mode)?
Click to expand...
Click to collapse
Debugging is enabled and fastboot seems to be fine too. Computer sees phone now (I installed drivers and HTC SYNC) but just now showing in adb devices.
Even if I could install a working GPE version on it I would take that, but at moment cant use camera, hangouts or Play store. So just browsing, texts and calls!!
Cheers for help, I appreciate any given.

Managed to copy the serial number from Settings> About Phone > Status. It is:
<眇?]q 戴
Nothing comes up when I google this, its very very strange and I have no idea how to change it!

beardo81 said:
Managed to copy the serial number from Settings> About Phone > Status. It is:
<眇?]q 戴
Nothing comes up when I google this, its very very strange and I have no idea how to change it!
Click to expand...
Click to collapse
since its s off i would try returning it to sense

toysoldierq said:
since its s off i would try returning it to sense
Click to expand...
Click to collapse
I tried reinstalling a gpe ROM last night and using the 5.1 update file also, but neither worked. Think I will try returning to sense today.
Would the serial number problem be when something corrupted during gpe conversion maybe?

Here is my getvar. Check out modelid and serial number. Bizarre.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: <þ£Ã└⌂*╩L]q▬÷H┤
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: ☻r♠
(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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.156s
PLEASE SOMEONE HELP!!!

Private message me or Google hangouts

Did you try to run an Official GPe RUU?It should return the phone to stock GPe and maybe fix your serial No to prior state.
P.S. you may want to hide your IMEI from your previous message.

nighthawk696969 said:
Did you try to run an Official GPe RUU?It should return the phone to stock GPe and maybe fix your serial No to prior state.
P.S. you may want to hide your IMEI from your previous message.
Click to expand...
Click to collapse
Ive tried this, will not run because of the modelid issue, error 41 I think.
Thanks, hidden imei, not thinking!!

toysoldierq said:
Private message me or Google hangouts
Click to expand...
Click to collapse
Sent you pm buddy. If it didn't get through let me know, it's not coming up as sent

toysoldierq said:
Private message me or Google hangouts
Click to expand...
Click to collapse
I've received your message and replied but it is not showing under my sent messages. Am I not allowed private message yet maybe?
Anyway, thanks for the message, so should I type 'fastboot oemwrite xxxxx'?
I'll give it a shot!!

toysoldierq, are you getting my pm's?
That didnt work btw

Thanks for help toysoldierq, appreciated.
Guys, this is still unsolved if anyone can help?
Cheers

toysoldierq said:
Private message me or Google hangouts
Click to expand...
Click to collapse
It's nice of you that i see you helping people constantly via teamviewer or PM but nobody else can benefit from that. This is an open forum and can also be used to learn by reading, we can't read your PM 's unfortunately !

I'm sorry but sometimes it's hard to explain to a person what to do, from now on I will keep it here

toysoldierq said:
I'm sorry but sometimes it's hard to explain to a person what to do, from now on I will keep it here
Click to expand...
Click to collapse
I did it for years on the hox, it's most off the time all same. I made a basic layout with steps and commands. Little copy and paste here and it was done
Cheers

It looks like the underlying issue here is the modelid and serial number got corrupted while whoever had the phone before me was changing it to GPE. The phone is useable for browsing and texts and calls but that's it.
I can sign in with my Google account and use YouTube, gmail, drive, photos, music etc but not hangouts or play store. No file explorer and can't download or open apk or zip files on phone. Camera launches but won't take pictures as SD card is not recognised.
Can't seem to contact phone via adb on computer although I can by fastboot. But this means I can't try change modelid this way.
All in one tool doesn't work. The flasahable zip for changing modelid on XDA didn't work.
I didn't do a full wipe yet through recovery as seeing as every time I have tried to flash anything I am getting met with error 41, modelid.
Pulling my hair out here guys!!

beardo81 said:
It looks like the underlying issue here is the modelid and serial number got corrupted while whoever had the phone before me was changing it to GPE. The phone is useable for browsing and texts and calls but that's it.
I can sign in with my Google account and use YouTube, gmail, drive, photos, music etc but not hangouts or play store. No file explorer and can't download or open apk or zip files on phone. Camera launches but won't take pictures as SD card is not recognised.
Can't seem to contact phone via adb on computer although I can by fastboot. But this means I can't try change modelid this way.
All in one tool doesn't work. The flasahable zip for changing modelid on XDA didn't work.
I didn't do a full wipe yet through recovery as seeing as every time I have tried to flash anything I am getting met with error 41, modelid.
Pulling my hair out here guys!!
Click to expand...
Click to collapse
Infact i wonder if you tried to re write the model id if that woud help or you could try to go back to sense
step 1 well i reflash the gpe rooted rom
step 2 i change his mid to dev edtion one
step 3 change his cid to super cid
step 4 i flash 1.54.401.5-W_Splash and let him wipe data and cache in stock recovery
step 5 change his cid to dev
step 6 ran dev ruu the lateset
everything you need is in these threads
http://forum.xda-developers.com/showthread.php?t=2708581
http://forum.xda-developers.com/showthread.php?t=2733523

toysoldierq said:
Infact i wonder if you tried to re write the model id if that woud help or you could try to go back to sense
step 1 well i reflash the gpe rooted rom
step 2 i change his mid to dev edtion one
step 3 change his cid to super cid
step 4 i flash 1.54.401.5-W_Splash and let him wipe data and cache in stock recovery
step 5 change his cid to dev
step 6 ran dev ruu the lateset
everything you need is in these threads
http://forum.xda-developers.com/showthread.php?t=2708581
http://forum.xda-developers.com/showthread.php?t=2733523
Click to expand...
Click to collapse
Hi soldier,
I've tried both of those and neither will work. I cant seem to communicate with my windows 8.1 pc through adb. When I try to change the serial number with fastboot another error comes up.
I wonder if I tried a windows 7 pc would that work? Means I'll have to turn my other laptop into an win7 laptop now too!!
Very frustrating as I cannot seemingly falsh anything, either through fastboot or recovery

[SOLVED] Can't write on Internal Storage (5.0.1)

Hi everyone..
You are my last chance..
Okay so I installed TWRP, and did a backup of my phone. After that, i rooted it.
Then, I installed a stock 5.0.1 (Sense 6) ROM. And the problem happened: I can't write on my internal SD card/internal Storage anymore (Where "ringtones, Pictures, Media etc are located. I think this is a permissions-related problem, but I'm not sure.
I installed a custom ROM (LeeDrOiD) to see if it fixes the problem, and yes. The permissions came back again, and I could write on my internal storage (move files, create folders etc). Finally, I decided to restore my backup, but the problem came again. I couldnt write on my internal storage anymore! I don't know what the heck is happening to my phone but I don't like that!
I already read the other threads but none of them gave a working answer..
What do you think ? Please help me, you guys are the only ones who can help me..!
Sorry for my bad english

LowPoly said:
Hi everyone..
You are my last chance..
Okay so I installed TWRP, and did a backup of my phone. After that, i rooted it.
Then, I installed a stock 5.0.1 (Sense 6) ROM. And the problem happened: I can't write on my internal SD card/internal Storage anymore (Where "ringtones, Pictures, Media etc are located. I think this is a permissions-related problem, but I'm not sure.
I installed a custom ROM (LeeDrOiD) to see if it fixes the problem, and yes. The permissions came back again, and I could write on my internal storage (move files, create folders etc). Finally, I decided to restore my backup, but the problem came again. I couldnt write on my internal storage anymore! I don't know what the heck is happening to my phone but I don't like that!
I already read the other threads but none of them gave a working answer..
What do you think ? Please help me, you guys are the only ones who can help me..!
Sorry for my bad english
Click to expand...
Click to collapse
enable USB debugging in your rom (needs to be rooted), then:
Code:
adb shell
su
restorecon -FR /data/media
exit
exit
reboot if needed
or from a terminal emulator on your phone directly:
Code:
su
restorecon -FR /data/media

nkk71 said:
enable usb debugging in your rom (needs to be rooted), then:
Code:
adb shell
su
restorecon -fr /data/media
exit
exit
reboot if needed
or from a terminal emulator on your phone directly:
Code:
su
restorecon -fr /data/media
Click to expand...
Click to collapse
Oh my. I can't believe it actually worked. Thank you. Thank you so much omfg I though my problem was hopeless!!
Thank you thank you thank you you're the best

LowPoly said:
Oh my. I can't believe it actually worked. Thank you. Thank you so much omfg I though my problem was hopeless!!
Thank you thank you thank you you're the best
Click to expand...
Click to collapse
No problem :good::good:
It's a well known issue with Android 5.x (not only on HTCs but others as well)
and if all is good now, can I ask you to also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title

nkk71 said:
It's a well known issue with Android 5.x (not only on HTCs but others as well)
Click to expand...
Click to collapse
Oh really? I searched like for weeks to fix this problem, but It seemed no one had the same issue as me
Anyway I set the thread as [SOLVED]

nkk71 said:
enable USB debugging in your rom (needs to be rooted), then:
Code:
adb shell
su
restorecon -FR /data/media
exit
exit
reboot if needed
or from a terminal emulator on your phone directly:
Code:
su
restorecon -FR /data/media
Click to expand...
Click to collapse
Couldnt get the play store to download properly but this works great on my HTC One m8. God bless U

nkk71 said:
No problem :good::good:
It's a well known issue with Android 5.x (not only on HTCs but others as well)
and if all is good now, can I ask you to also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title
Click to expand...
Click to collapse
Using this in 2019 haha
God bless you
Rest in peace my friend

Hello,
I am pretty much hopeless for my htc one m8.:crying:
The problem is that my phone is stuck in a uncommon situation. When I try to install any apps or download anything in the intenal storage or change anything of my device it just restarts and vanishes all my activities.
I've been googling for 4 months and not found any solution.
Also include that the factory reset not working. It is showing formated successfully but when I press reboot and again nothing changed. All of my apps and files were there.
The problem started when the charging port was damaged and I was charging my phone all day long. Suddenly it stuck at 1% of battery then after 3 hours it shutdown. Then I repair the damaged port and the charging issue fixed but the new issue raised.
Help
Thanks in advance.

Abu omayer said:
I am pretty much hopeless for my htc one m8.:crying:
The problem is that my phone is stuck in a uncommon situation. When I try to install any apps or download anything in the intenal storage or change anything of my device it just restarts and vanishes all my activities.
I've been googling for 4 months and not found any solution.
Also include that the factory reset not working. It is showing formated successfully but when I press reboot and again nothing changed. All of my apps and files were there.
The problem started when the charging port was damaged and I was charging my phone all day long. Suddenly it stuck at 1% of battery then after 3 hours it shutdown. Then I repair the damaged port and the charging issue fixed but the new issue raised.
Click to expand...
Click to collapse
Storage corrupt is not that uncommon an issue.
Is the phone modified at all (unlocked bootloader, TWRP, root, etc.)? Or still stock?
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number). If you don't know how to do that, reboot to bootloader, and tell us what it says for OS number on the bootloader screen.

redpoint73 said:
Storage corrupt is not that uncommon an issue.
Is the phone modified at all (unlocked bootloader, TWRP, root, etc.)? Or still stock?
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number). If you don't know how to do that, reboot to bootloader, and tell us what it says for OS number on the bootloader screen.
Click to expand...
Click to collapse
No, boot loader is locked and its not rooted also. The information I got:
*** Locked ***
M8_WLV PVT SHIP S-OFF
CID-111111111
HBOOT-3.19.0.0000
RADIO-1.09.20.0926
OpenDSP-v46.2.2-00564-M8974_FO.0811
OS-3.28.605.4
eMMC-boot 2048MB
Sep 30 2014,01:16:07.3
I have 0 knowledge about the deep things you told pls help

Abu omayer said:
No, boot loader is locked and its not rooted also. The information I got:
*** Locked ***
M8_WLV PVT SHIP S-OFF
CID-111111111
HBOOT-3.19.0.0000
RADIO-1.09.20.0926
OpenDSP-v46.2.2-00564-M8974_FO.0811
OS-3.28.605.4
eMMC-boot 2048MB
Sep 30 2014,01:16:07.3
I have 0 knowledge about the deep things you told pls help
Click to expand...
Click to collapse
You can try to install the RUU (ROM update utility) which will re-write all partitions, and may help your issue.
You can flash 4.4.4 or 5.0.1 versions RUU from here (post includes instructions): https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Based on your knowledge level, exe format is easiest method.
4.4.4 is Kitkat (and your current Android version).
5.0.1 is Lollipop
You can also flash 6.0 (Marshmallow). However, you have a US variant (Verizon) M8, which has a peculiarity with the Marshmallow RUUs; where you need to flash firmware.zip before the Marshmallow RUU will work. This is probably over your head, so therefore I am suggesting that you flash one of the RUUs indicated above (4.4.4 or 5.0.1).

HELLO EVERYONE

I posted my question already in General Discussion - Introductions.
But i think/ hope this is where i need to be.
Hey and hello dear 'XDA-COMMUNITY'!!
I am complitely new, not only in this forum but in/to Android as well.
I were able to get an "old" htc one m9, in very good shape and thought if this
good looking device could be capeable of running up-to-date software and apps.
To my surprise - How i found out through your website -
This phone can possible be a very useful phone even in these days.
First and foremost beacause of your fascinatiing work!
"Shout out - to all of you" for keeping these possibilities alive.
Since i am a very beginner, there might be a lot of things i need to get to know...
But... here the things i already know (about the device)
--
*** UNLOCKED ***
*** S-ON ***
kernel: lk
product: htc_himauhl
version: 1.0
version-main: 1.32.161.7
boot-mode: download
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: VODAP102
--
It seems to be completely empty... No Android main operating system installed.
TWRP is installed but an old version... 2.8.7- i guess
I already setted up my pc with ADB/fastboot/ and drivers
I think (as far as i understood) to get a lineageOs e.g. 17.1 or newer (19) working
i need to update the #version-main: 1.32.161.7 to at least 4.xx ?right/wrong?
And here i am....
Would be very nice if someone can give an advice about
what to do and in which order to get it "proper" working, if possible...
Thank you for your angagement and your time-
best regards from Germany
Bruse
P.S.:
For example, are or would these files be a good "path" to go or at least near by??
Found in you forum -> link
HTC ONE (M9) RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
Original STOCK file to flash the HTC One M9 from the RUU BACK TO STOCK You can flash throu fastboot or change the name of the file to 0PJAIMG.ZIP and put it in SDCard and load Bootloader S-Off is Required with Eurpean CID Go into fastboot...
forum.xda-developers.com

See if you can get a rooted stock rom to flash with twrp , that way you wont have to flash the stock rom root and install twrp all over again .
if not , I would say that the link you attached is a nice starting point .
Good luck!

Dear @ThatLatinGuy thank you very much.... Your post gave me the confidence to go ahead with these steps....
Got it working - thank you
NIce greetings
Bru.Se