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.

[bug] Changing the radio version manually

While attempting to update my firmware manually from the bootloader I accidentally came across a glitch which allows me to change the Radiover appearing in the bootloader (not sure why)
There is no use of changing the radio version but i found it interesting enough to share it, while we are waiting for JB .
Warning: attempting this could lead to the combustion of your phone.
make a pj46img.zip, place an android-info.txt in it and write the following in the txt file:
modelid: PJ4610000
cidnum:enter_CID_here
Radiover: whateveryouwanttoappear
flash the zip in ruu mode without locking(fastboot flash zip pj46img.zip, not update)
it will give you errors but the value still changes
I tryed to change other variables/values but none changed except this one.

What errors do you get?
I would have thought that it would fail signature check and not change anything at all.
Is it possible to dump the pj46img.zip from a phone?
If so, has anyone tried dumping a pj46img.zip from a Super CID phone, then flahsing it to a different phone? Surely someone must have tried that a long time ago.

with the bootloader unlocked it gives error 99 unknown fail
with the bootloader locked i think it gave signature check fail

Sentinel196 said:
What errors do you get?
I would have thought that it would fail signature check and not change anything at all.
Is it possible to dump the pj46img.zip from a phone?
If so, has anyone tried dumping a pj46img.zip from a Super CID phone, then flahsing it to a different phone? Surely someone must have tried that a long time ago.
Click to expand...
Click to collapse
My first thought also.
But surely someone would have thought of that, like Xmoo or something?
Nice find though Vcek !

I don't think the zip is stored anywhere on the phone, once you install it, each of its components go to their place, then the zip is erased.
Add: the value changes for some reason during the signature checks whether it failed or not.
Sent from my HTC One X

[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

No ROM or Backup - TWRP is installed.

I am turning my old phone into pretty much a mobile gaming/media device for my son. In my rushed laziness I misconstrued unlocking/s-off and rooting as the same thing. To make a long story short, I have TWRP 2.7.0.2 installed (I now know this is a very old version, I didn't realize the post I was following was from 4 years ago. -_-), I am unlocked, and s-off. I however do not know if I am rooted (I am guessing not since TWRP fails to install OS ROM's). I do not have a backup of the original OS (which I don't want anyway) and need some assistance with rooting or verifying I am rooted from within TWRP or adb. I figured since my phone is still booting up to TWRP and I have successfully sideboarded SuperSu and installed it from within TWRP I am not completely out of luck.
Thank you ahead of time for any assistance. It's greatly appreciated.
I am open to recommendations for ROMs. I was going to do CM13 w/gapps but if there is a sleeker, more efficient ROM (I've heard good things about Viper) feel free to advise. He'll just be taking pictures, playing Clash and Pokémon Go etc.
This is also a Verizon phone not sure if that matters anymore since I nuked it and unlocked it.
I figured I would be asked to do this so here is the info getvar info all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.14.20.0930
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

you need the most staple rom ?
I believe it will be the stock as you said for some gaming and taking pictures
also there is viper and s-rom ( both are ported from HTC 10 ) and pretty stable to be daily drive
and many more roms which support Verizon devices
Sent from my HTC M8 using XDA Labs

I don't mind if it isn't staple. I need it to be stable, bloat free, high performance, and basic features need to work like Gapps, camera, blue tooth, and gps. Thank you for taking time to respond.

Hatemedude said:
I am unlocked, and s-off. I however do not know if I am rooted (I am guessing not since TWRP fails to install OS ROM's).
Click to expand...
Click to collapse
You don't need root to install ROMs on this phone. You do need root (at least temp root) in order to s-off; but since you have successfully obtained s-off, its irrelevant now whether you are rooted or not.
The main reason ROMs won't install is probably due to the outdated TWRP version. Install the current TWRP 3.0.2.
Also make sure that the ROM(s) specifically supports the Verizon M8. If not, the ROM won't boot, due to kernel differences between the VZN version, and most other M8 versions.

redpoint73 said:
You don't need root to install ROMs on this phone. You do need root (at least temp root) in order to s-off; but since you have successfully obtained s-off, its irrelevant now whether you are rooted or not.
The main reason ROMs won't install is probably due to the outdated TWRP version. Install the current TWRP 3.0.2.
Also make sure that the ROM(s) specifically supports the Verizon M8. If not, the ROM won't boot, due to kernel differences between the VZN version, and most other M8 versions.
Click to expand...
Click to collapse
Thanks that about did it. I upgraded TWRP to current, wiped Davlick/Cache/System/Data etc, installed CM13, cleared Davlick/Cache again, rebooted and I was good to go. I updated to CM14 + gapps 7.1. Everything is working great. I backed up probably 4x as I went along so I don't lose the OS like I did last time.
I do have a few other questions that you may or may not be able to answer.
Where does TWRP save the back ups on the phone? I was unable to locate them via File Manager (even with Root Access on.)
I installed Pokémon Go and it fails to authenticate every time regardless if I use his gmail or PTC account. It seems like the game detects Root access but I have Root turned off at the moment. Do you have any suggestions? That would probably be his favorite game to play.

Hatemedude said:
Where does TWRP save the back ups on the phone? I was unable to locate them via File Manager (even with Root Access on.)
.
Click to expand...
Click to collapse
It depends on your choice ( internal or external )
Once you made a backup and choosed the location ( external or internal ) you will find a new folder called TWRP in your storage open it you will find another folder called BACKUPS open it you will see another folder called ( your device serial number ) open it you will see your backup folder called by date and time ( if you didn't change it )
it should be like this
TWRP--»BACKUPS--»YOURSERIALNUMBER--»BACKUPNAME
Hope that helps
Sent from my HTC M8 using XDA Labs

Hatemedude said:
Where does TWRP save the back ups on the phone? I was unable to locate them via File Manager (even with Root Access on.)
Click to expand...
Click to collapse
As ahmed stated, this depends on what you have selected in TWRP (internal storage vs. SD card). There is a button in TWRP to toggle between internal storage and SD. Either way, it will generate a folder named "TWRP" which will contain your backups.
Hatemedude said:
I installed Pokémon Go and it fails to authenticate every time regardless if I use his gmail or PTC account. It seems like the game detects Root access but I have Root turned off at the moment. Do you have any suggestions? That would probably be his favorite game to play.
Click to expand...
Click to collapse
Pokémon Go definitely checks for root. I'm not personally aware whether having root "deactivated" (or whatever the right term would be) on the CM settings is enough. But since you can't login to the game, I'd say its detecting root.
There is an Xposed module to hide root. But I'm not sure if that is enough, either.

Hatemedude said:
I installed Pokémon Go and it fails to authenticate every time regardless if I use his gmail or PTC account. It seems like the game detects Root access but I have Root turned off at the moment. Do you have any suggestions? That would probably be his favorite game to play.
Click to expand...
Click to collapse
redpoint73 said:
Pokémon Go definitely checks for root. I'm not personally aware whether having root "deactivated" (or whatever the right term would be) on the CM settings is enough. But since you can't login to the game, I'd say its detecting root.
There is an Xposed module to hide root. But I'm not sure if that is enough, either.
Click to expand...
Click to collapse
As far as I'm aware of - not playing it myself - PoGO checks for root as well as safetynet (as used by banking apps). Root triggers it in any case, but also an unlocked bootloader, because an unlocked bootloader triggers safetynet. There are possibilities to hide both, root as well as unlocked bl, from PoGO to get it up and running. But I'm not familiar with the needed steps as I don't use this game and thus don't need to know about those steps.
Sent from my htc_pmeuhl using XDA Labs

Alrighty thanks again. Honestly, the game is quite awful and this gives me a reason to not have him play it. 😂

redpoint73 said:
As ahmed stated, this depends on what you have selected in TWRP (internal storage vs. SD card). There is a button in TWRP to toggle between internal storage and SD. Either way, it will generate a folder named "TWRP" which will contain your backups.
Pokémon Go definitely checks for root. I'm not personally aware whether having root "deactivated" (or whatever the right term would be) on the CM settings is enough. But since you can't login to the game, I'd say its detecting root.
There is an Xposed module to hide root. But I'm not sure if that is enough, either.
Click to expand...
Click to collapse
Xposed haven been published on cm14 yet. just saying
Hatemedude said:
Thanks that about did it. I upgraded TWRP to current, wiped Davlick/Cache/System/Data etc, installed CM13, cleared Davlick/Cache again, rebooted and I was good to go. I updated to CM14 + gapps 7.1. Everything is working great. I backed up probably 4x as I went along so I don't lose the OS like I did last time.
I do have a few other questions that you may or may not be able to answer.
Where does TWRP save the back ups on the phone? I was unable to locate them via File Manager (even with Root Access on.)
I installed Pokémon Go and it fails to authenticate every time regardless if I use his gmail or PTC account. It seems like the game detects Root access but I have Root turned off at the moment. Do you have any suggestions? That would probably be his favorite game to play.
Click to expand...
Click to collapse
My suggesting into bypassing the pokemon go is to install a nonrooted rom, install and login to pokemon go, root it using supersu systemless root, use titanium backup to backup pokemon go and its user data, go back to cm 14 enable root from developers option, install titanium backup again and restore pokemon go. Ive heard it works and it totally works on snapchat as snapchat won't let you login if your rooted.

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