Develop Bugs

[Q] Unable to flash a custom rom (s on, recovery booted via fastboot, htcdev unlock)

Hey you pros
I am currently a little confused. I just got my HTC ONE m8 (dual boot) a week ago and tried since then to flash a custom rom. I unlocked my phone via htcdev and unlocked is shown. I do not have s off, because I read flashing should also work this way. I tried with twrp 2.8.1.0 on the old firmware (1.45.401.12). I did a full wipe and tried every different way, like booting into recovery via fastboot, flashing the kernel seperately. The newer version of twrp didn't work, and neither did cwm. Then I tried to update the firmware over the normal OTA way and have now version 3.33.401.6. The new twrp is working now, but i again tried all ways known to me and no one worked. Do you guys know what is wrong? I searched over google read different threads, but can't find an answer.
I would really appreciate if you could help me!
Here is the fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.30306251.27G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---
(bootloader) imei: ---
(bootloader) imei2: ---
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B64000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 4c3fbd70
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Oh and by the way I tried to flash the Official Nightlys of CM 11 and "[ROM][5.0.2][OFFICIAL] LiquidSmooth v4.0 | Lollipop | [12-25-14]".
Thanks for your help!
xhdev

So you're saying you fastboot flashed the kernel separately from the ROM itself?

Magnum_Enforcer said:
So you're saying you fastboot flashed the kernel separately from the ROM itself?
Click to expand...
Click to collapse
Yes, I ALSO tried this, because I read somewhere that with s on the recovery can't access /boot. I did this with the command "fastboot flash boot boot.img" if that helps. In this case I used of course the kernel within the rom archive. I tried as well to (again after full wipe) just flash the *.zip archive, which had again the outcome of the bootloader appearing directly on turn on before any logo or animation.

Info for everyone having the same problem: The problem is due to the dual sim model, which is incompatible to the standard custom roms. At the moment there is only maximus hd 2.0 for our model. Im not sure if one can change cid and get other roms to work or if there are other custom roms. If somebody knows more, I'd really appreciate a hint about that.
Sent from my HTC One_M8 dual sim using XDA Free mobile app

devxh said:
Hey you pros
I am currently a little confused. I just got my HTC ONE m8 (dual boot)..
Click to expand...
Click to collapse
I think you are confused
You have a dual sim (although dual boot would be nice). You need to be really careful what you do with it.
Unless stated, any other custom rom on xda (as of today) will not work on your dual sim.
As @devxh says, there are no custom roms apart from MaximusHD (we live in hope though)
Do not try any other roms.
Having said that, I have TWRP 2.8.1 and thats working fine and can recommend MaximusHD as a good replacement for stock rom.
It certainly 'feels' quicker than stock.
If you try it, make sure you update your firmware otherwise you will lose wifi

[Q] HTC M8 (Three UK) - Return to stock help please

Hello,
Apologies in advance for what is probably a dumb (and often repeated) question, but I'm hoping someone can sanity-check this before I attempt it as I am a bit confused around the version numbers mainly.
I have previously had Samsung Galaxy devices (S2, S3 and S4), all of which I regularly flashed with custom ROMs, but while I am delighted to be a HTC owner, the flashing process is very different.
I have a HTC One M8 from Three (UK) and am S-On; I followed the sticky guides originally to unlock the bootloader (using the code from HTC) and then installed the Venom ViperOneM8 (currently 3.2.1).
I am trying to return to stock so that I can update to the latest VenomRom based on Lollipop; I know there are inevitably a lot of questions about this so I appreciate anyone's assistance.
The output from my FastBoot getvar all is as follows:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.771.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: a3d0cb0d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I understand that I need to return to stock, and with S-On the way this is achieved is via a restore of a Nandroid backup and recovery, followed by multiple OTA updates to bring me up to the latest version.
My issue is that there are only 2 available links for firmwares with the "H3G" CID (one for PhilzTouch and another for TWRP; I have TWRP), in ExocetDJ and Soldier9312's thread (http://forum.xda-developers.com/showthread.php?t=2701376) and these are completely different that my currently installed version (i.e. I have 3.32.771.3 installed, and the TWRP version is 1.12.771.17).
Is this the correct firmware backup I need (albeit a much older version - 4.4.2 rather than my current 4.4.4)? I have also picked up the corresponding recovery file (stock+recovery+1.12.771+recovery.img) from the same thread, so assuming the firmware is correct then is this the right one too?
If these are correct, I then need to follow the guide to restore the Nandroid backup (copy the extracted files to the correct location on the ext-SD card, flash the boot.img from that backup, full wipe from recovery, restore Nandroid backup), and that should leave me with a stock ROM.
Can someone please confirm the above?
Many thanks in advance

Don't go with 1.x version, you'll get stuck with no wifi. You only can go one version lower 2.x or same version 3.x
Try mine : http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1897

ckpv5 said:
Don't go with 1.x version, you'll get stuck with no wifi. You only can go one version lower 2.x or same version 3.x
Try mine : http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1897
Click to expand...
Click to collapse
Thankyou very much; I will give that a go tonight.

Easy, squeezy...

ckpv5 said:
Don't go with 1.x version, you'll get stuck with no wifi. You only can go one version lower 2.x or same version 3.x
Try mine : http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1897
Click to expand...
Click to collapse
Just to clarify, I assume that the version 3.32.771.10 in your post newer than my current version 3.32.771.3?
Therefore I would be better off using the 2.22.771.5 one.

You should be fine using 3.32.771.10 if available (plus I think the Lollipop OTA requires this version to update)

EddyOS said:
You should be fine using 3.32.771.10 if available (plus I think the Lollipop OTA requires this version to update)
Click to expand...
Click to collapse
ok, thanks chap; i'll give it a shot.
I can always restore a Nandroid of my current firmware (taken before I start) if it goes tits-up

Thanks for the help guys.
I ran through the process last night with relatively little drama and I'm now running Lollipop and Venom 4.0.0.
Much appreciated as always.

[Q] No ADB. No recovery. No OS.

Alright, yesterday I posted a thread asking for help here. Since this is a different issue I created a new topic instead of posting it in that thread.
Since my Android was screwed up and I wanted to revert back to a Sense ROM for a while now, I thought I might as well do that now. I tried it with this guide. Changed my CID to Super CID, flashed the firmware, and did that factory reset in the bootloader. But, since the OS is screwed up and my recovery is gone, I can't use adb anymore. I also can't use it in the bootloader. So, no OS, no recovery, no adb as far as I can tell.
I'm clueless and having a little panic attack here. Any help would be awesome.

Connect your phone in fastboot and then run fastboot getvar all and post the results (minus your S/N and IMEI) and we'll see what you need to get working again

Alright, here it goes.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

This is easy, just flash the 4.16.401.10 RUU and jobs done...
http://forum.xda-developers.com/showthread.php?t=2735235
Step 3 applies to you as Step 1 and 2 you don't need to do but make sure you download the files required (you can do Step 2 if you want to change your CID back but that's up to you)

Alright, thanks. What exactly will this get me? And will I be able to flash a custom Sense based rom like InsertCoin then? If so, what steps do I take from here? I'm not really that experienced and kind of afraid I'll screw up again without someone holding my hand through the process.

This will get your phone running 100% stock Sense Lollipop as if you just took the phone out the box. You can then flash a custom ROM (if you'd like) using the guides on here

I haven't done anything yet, but with my goal being having installed InsertCoin, can I just flash TWRP now and flash the InsertCoin zip? I have already gotten to the point in the video I mentioned where I had to flash the firmware. I stopped at the point he went into Android again to enable USB debugging since I wasn't able to that. I didn't go any further because I was afraid of messing my phone up.

You're better off doing what I suggested to make sure everything is up-to-date firmware wise and then go custom

I did what you told me to and everything was okay after that. Right now I'm on InsertCoin. Thank you very much!

[Q] Flashing the latest SD 10.1 on an outdated M8

Hello
My friend's device has had the same ROM since she got the phone (Viperone M8 v1.8) which is really old! I was thinking of just flashing the latest TWRP recovery using fastboot and then installing SkyDragon v10.1, so would that be possible or do I have to flash the latest firmware as well? And if so, does the device HAVE to be S-OFF? When I was running a custom ROM and wanted to go S-OFF in the past, it was a huge hassle and it took me a lot of time to finally get it to work and I don't even remember the process or want to go through it again, unless there's an easier (non-paid) way nowadays.
Thanks guys!

I tried flashing the latest TWRP recovery but it didn't work:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA43JWM00903
(bootloader) imei: 358714050511611
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any ideas?

Return to stock rom + stock recovery, update the phone with official OTA and then flash custom roms. Written everywhere around and check the stickied threads in the general. Fairly easy.....you are around for a while to know how this forum works. And stop spamming the serial and imei around in your posts, delete them ! They don't belong on the www they are private !
And here are backups
http://forum.xda-developers.com/showthread.php?t=2701376
Took me 1 minute......
Edit :
Ow to be clear, restore the 1.54 orang001 cid backup and check for ota. Download it but apply it later. Then take out the recovery from the ota zip and flash it. Then you have the stock recovery and are able to apply the actual ota's (yes there will be multiple)

Thank you for your reply. I've never really had a branded device before so that was the struggle. The device is my colleague's, therefore I'm trying to be as cautious as possible. The thread you linked me to apparently contains a zip backup of stock firmware for the same cid so that's pretty awesome, however I cannot find the appropriate recovery img from the ones listed. Any ideas where I can find one? I'm having a difficult time finding things for ORANG001 on the forum.
Sent from my HTC One M8 using XDA Premium 4 mobile app

TarekElsakka said:
The thread you linked me to apparently contains a zip backup of stock firmware for the same cid so that's pretty awesome, however I cannot find the appropriate recovery img from the ones listed. Any ideas where I can find one? I'm having a difficult time finding things for ORANG001 on the forum.
Click to expand...
Click to collapse
Read Post #3 of the previously linked thread, under "Questions & Answer" and read the 2nd to last Q/A.
Any 1.54.xx stock recovery will work.

Thank you so much for your help, I truly appreciate it and I cannot wait to try this. Have a great day!!
Sent from my HTC One M8 using XDA Premium 4 mobile app

wiped my OS, flashed a poop ROM need help

Long story short, I forgot my screen lock and wiped as a last resort. Realizing too late that a factory reset wouldn't complete, I was left with a paperweight. I was able to get a rooted stock ROM from XDA, flashed it and it seems to be working. I want to get back to viper ROM, preferably marshmallow (I'm currently on lollipop) but I am having a lot of trouble. Attempts to get s-off have been thwarted, and flashing viper (5.0.2) has failed. Any help would be appreciated. I can answer any questions.

What stock ROM did you flash, exactly?
How exactly are you trying to s-off, and what step did you get stuck (error messages, or other results?)?
When the ROM failed, did it give you an error message (or list any other outputs or results)?
Your statements on these last 2 points if far too vague, for us to help properly.
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

Lmy470.h6 is the ROM I flashed. I've been trying to push firewater via adb to get s off. I can't/won't pay for a sunshine. When flashing other stock Roms, the error is no error. It just says install aborted. When trying to flash viper, it says there's a permission error. When trying to run firewater, it gives me the PIE error. Getvar coming later.

Firewater won't work, Period. It had an online component (had to connec to a server), which the devs stopped supporting in Dec 2014. Nothing you do will make it work, and is a complete waste of time.
That said, you don't need s-off to flash ROMs. And whatever is wrong with flashing ROM, s-off is probably not going to fix.
The fact that multiple ROMs work, indicates user error, and you're incorrectly trying to blame the ROMs ("poop ROM").
What TWRP version? Need that info, and getvar data. But I'm guessing you just have an old version of TWRP (or try another slightly different build TWRP).

I'm actually using philz touch recovery. I only call it a poop ROM because I don't like what it came with and how it looks. Also. The ROM I'm using is the only ROM that works thus far. Most other Roms simply abort. Viper ROM tells me it doesn't have to permissions necessary which indicates the need for s off. I attempted getvar, however the command window just sat idle and wouldn't let me type anything. Am I missing something there?

I should also mention I've been using recovery to flash Roms. Perhaps flashing via adb would work better? Or work at all?

One last thing. Flashing the ROM I'm currently using created new 0 directories. I now have 0/0/0. Any safe way to fix that?

enviouss said:
I'm actually using philz touch recovery.
Click to expand...
Click to collapse
That's the problem right there. Philz hasn't been updated in a long time, maybe 2 years. Its almost certainly the cause for the ROM flashes failing.
Use TWRP, but exact version depends on your current firmware version, indicated in getvar. But probably TWRP 2.8.7 since you indicated you were using Lollipop ROMs okay.
enviouss said:
I only call it a poop ROM because I don't like what it came with and how it looks.
Click to expand...
Click to collapse
So its your personal opinion and preference, and I would recommend you not insulting the work of devs that work so hard (usually for no compensation) to post their work here.
---------- Post added at 10:09 AM ---------- Previous post was at 10:06 AM ----------
enviouss said:
I should also mention I've been using recovery to flash Roms. Perhaps flashing via adb would work better? Or work at all?
Click to expand...
Click to collapse
Sideload adb still needs the proper recovery, adb can't flash a ROM by itself. Sideload just adds move points of failure, not less. I don't recommend it, as I've seen it cause more problems than it solves (fails when simply flashing in recovery works).
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
enviouss said:
I attempted getvar, however the command window just sat idle and wouldn't let me type anything. Am I missing something there?
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when issuing the command?
If so, try another cable, another USB port, or re-install HTC drivers.

I haven't been I boot loader mode. Will try shortly. Also. Will change to twrp. And yes, I'm on lollipop 5.1. I will change recoveries and attempt getvar. Results will be posted.

Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s

Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s

enviouss said:
Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse
Also, flashed your recommended version of TRWP recovery. It is up and running. I am ready for the next phase.

enviouss said:
Also, flashed your recommended version of TRWP recovery. It is up and running. I am ready for the next phase.
Click to expand...
Click to collapse
I'm glad I asked for the getvar data. Your firmware (hboot, radio, etc.)is woefully outdated as its still on kitkat firmware, which I can tell from the radio number and version-main 3.28.1540.5. This alone will prevent LP and MM ROMs from working (no boot or broken WiFi).
There are various ways to update the firmware:
- Restore stock TWRP backup for 3.28.1540.5, and corresponding stock recovery, and perform OTA updates which will also update the firmware.
- Relock bootloader, and flash full stock 6.12.1540.4 firmware following the Method 2 here. After flashing firmware, you can then unlock bootloader again, flash TWRP and flash the desire ROM.

I would greatly prefer not to relock my boot loader,as it requires HTC correspondence to unlock. That could take a while. Can you walk me through your first method? Possibly with links to other threads and downloads?

I messed up. big time. So i found and downloaded your recommended recovery image. Downloaded flashify for root, and flashed the image. Now whenever I try to boot, or enter recovery mode, i get the red triangle of death. Please help! I tried reflashing twrp via adb, but adb doesnt recognize my device anymore! I dont know what to do...

update: performed a factory reset. Was able to get device up and running again. Impatiently awaiting further instruction.

enviouss said:
I messed up. big time. So i found and downloaded your recommended recovery image. Downloaded flashify for root, and flashed the image.
Click to expand...
Click to collapse
What did you download, and from where? Its not clear what you were trying to do here, exactly. You don't need root to flash ROMs or TWRP backups; and I personally dislike using apps like Flashify, for things that are easily accomplished with fastboot, TWRP, etc.

I found the stock nandroid backup suggested and flashed it using flashify. I have an idea what needs to be done here, but if an expert like yourself could leave me some detailed instructions as well ad download links it would really help.

enviouss said:
I found the stock nandroid backup suggested and flashed it using flashify. I have an idea what needs to be done here, but if an expert like yourself could leave me some detailed instructions as well ad download links it would really help.
Click to expand...
Click to collapse
He did give you expert advice, and you didn't follow it. Don't use Flashify. Any instructions you get from anyone here will tell you to use ADB/fastboot.
Also, you are going ahead without proper instructions and you can go ahead and do that, but go to where you got those other instructions from to ask for help.

Actually, in reference to the nandroid backup, he (we are assuming here) never said exactly how to use the files. Just what to do. I need precise instructions with links to fix this issue. This is one I've never dealt with before.