Develop Bugs

Well, I think I killed it :(

Having a problem with my DHD after unlocking the bootloader through HTCDEV and then running the Advanced ACE Hack Kit.
It appears to be flashing roms but when rebooting it's just freezing at the HTC screen.
Now, I know it must be something I've done/I'm doing but I have no idea what so can someone please talk me through flashing the easiest rom in the easiest way?

Can you access to the bootloader(Turn off the device then press and hold vol down and power together until booted)?

ymcc said:
Can you access to the bootloader(Turn off the device then press and hold vol down and power together until booted)?
Click to expand...
Click to collapse
Yep. I can get into the bootloader so i've been going into recovery (which is now ClockworkMod 5.0.2.7) and trying to flash different roms from there but none are working so it must be something I'm doing

What it sais when you try and fail.Are there any errors ?

ymcc said:
What it sais when you try and fail.Are there any errors ?
Click to expand...
Click to collapse
Nope. I've tried 4 different roms and they all seem to work but when it reboots I just get the HTC at startup but it hangs there

You are not bricked if you can access bootloader.
You have to flash the Roms boot.img separate when you flash roms with unlocked bootloader, I would recommend to run the ruu from your computer when in fastboot mode, then relock the bootloader using HTCdev and rerun the advanced ace hack kit.
Sent from my HTC Desire HD using xda premium

Muikkuman said:
You are not bricked if you can access bootloader.
You have to flash the Roms boot.img separate when you flash roms with unlocked bootloader, I would recommend to run the ruu from your computer when in fastboot mode, then relock the bootloader using HTCdev and rerun the advanced ace hack kit.
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
I know I'm gonna look like a complete spaz here but can you tell me how to do it? I flashed my Magic and it was so easy compared to this :-S
Where do I put the rom? Do I need to unzip it first? Amd what commands do I use in fastboot?

Which of it? flash Rom or get real S-OFF?
Sent from my HTC Desire HD using xda premium

Dont unzip it copy to sdcard root.check android development stickies you got your answers and tools there you need to wipe everything then flash over and flash 4ext recovery wipe boot.imp then flash a rom
Sent from my Desire HD using xda app-developers app

Gixermouse said:
Having a problem with my DHD after unlocking the bootloader through HTCDEV and then running the Advanced ACE Hack Kit.
It appears to be flashing roms but when rebooting it's just freezing at the HTC screen.
Now, I know it must be something I've done/I'm doing but I have no idea what so can someone please talk me through flashing the easiest rom in the easiest way?
Click to expand...
Click to collapse
Gixermouse, you commited a mistake covered in the effen manual...you tried running the kit with an unlocked bootloader. You need to relock it first and then re run the Kit.
Do the following:
1) Boot in hboot and then choose fastboot.
2) Plug the phone (until you see fastboot usb)
3) Open a cmd as Admin in the PC or Terminal as root (in linux or mac)
4) Type: fastboot oem lock
then you should see OKAY. finished...then reboot the phone and from the htc screen run the Hack Kit again...
It will work unless you did a factory reset....if you need help just let me know...:good:

glevitan said:
Gixermouse, you commited a mistake covered in the effen manual...you tried running the kit with an unlocked bootloader. You need to relock it first and then re run the Kit.
Do the following:
1) Boot in hboot and then choose fastboot.
2) Plug the phone (until you see fastboot usb)
3) Open a cmd as Admin in the PC or Terminal as root (in linux or mac)
4) Type: fastboot oem lock
then you should see OKAY. finished...then reboot the phone and from the htc screen run the Hack Kit again...
It will work unless you did a factory reset....if you need help just let me know...:good:
Click to expand...
Click to collapse
OK! I've followed what you said to do and on the HBOOT scree it now says *** RELOCKED *** at the top but when I try to run the hack kit it's saying "Error: device not found". I've tried at the HTC screen, HBOOT screen ad FASTBOOT screen. Any ideas?

Gixermouse said:
OK! I've followed what you said to do and on the HBOOT scree it now says *** RELOCKED *** at the top but when I try to run the hack kit it's saying "Error: device not found". I've tried at the HTC screen, HBOOT screen ad FASTBOOT screen. Any ideas?
Click to expand...
Click to collapse
umm...it seems that u have done a factory reset. I guess the best u can do is to flash a ruu, go back to stock and then when working re run the Hack Kit to gain S-OFF and root.
Do you know, what your cid is? boot in fastboot, plug the phone until you see fastboot usb and then from a cmd session as admin type
fastboot getvar all....paste here the INFOcidnum

Gixermouse said:
OK! I've followed what you said to do and on the HBOOT scree it now says *** RELOCKED *** at the top but when I try to run the hack kit it's saying "Error: device not found". I've tried at the HTC screen, HBOOT screen ad FASTBOOT screen. Any ideas?
Click to expand...
Click to collapse
since ur are saying that it says no device found then u have no other option but to flash the p98img.zip through fastboot but make sure not to flash a dhd shipped with gingerbread with a froyo ruu.Peace

What country and carrier is your phone from? The AAHK has am option to download RUUs. Try to use that. If that doesn't workout, I'll try to find an RUU for you (depending on your country and carrier).
Sent from my Desire HD using xda premium

Right. Here's all the info from the Getvar command minus the IMEI number:
version: 0.5
version-bootloader: 0.85.0024
version-baseband: 26.09.04.11_M2
version-cpld: None
version-microp: 0438
version-main: 1.80.502.3
serialno: HT0BHRX15082
product: ace
platform: HBOOT-7230
modelid: PD9810000
cidnum: HTC__001
battery-status: good
battery-voltage: 4165mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: a3d4fa0f
hbootpreupdate: 11
gencheckpt: 0
region-id: 0
The phone is a replacement board fitted by HTC under waranty after mine died (through no fault of my own that time!)
It wasn't network locked and was running 2.3.5 when I recieved it.
By booting in recovery and mounting the system data and cache I was able to make it appear to flash a rom and when I did a backup the files were on there but it still wouldn't boot.
If there's anything else you need let me know because the LG-A100 I've borrowed is now driving me crazy and I'm getting a bit desperate

Gixermouse said:
Right. Here's all the info from the Getvar command minus the IMEI number:
version: 0.5
version-bootloader: 0.85.0024
version-baseband: 26.09.04.11_M2
version-cpld: None
version-microp: 0438
version-main: 1.80.502.3
serialno: HT0BHRX15082
product: ace
platform: HBOOT-7230
modelid: PD9810000
cidnum: HTC__001
battery-status: good
battery-voltage: 4165mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: a3d4fa0f
hbootpreupdate: 11
gencheckpt: 0
region-id: 0
The phone is a replacement board fitted by HTC under waranty after mine died (through no fault of my own that time!)
It wasn't network locked and was running 2.3.5 when I recieved it.
By booting in recovery and mounting the system data and cache I was able to make it appear to flash a rom and when I did a backup the files were on there but it still wouldn't boot.
If there's anything else you need let me know because the LG-A100 I've borrowed is now driving me crazy and I'm getting a bit desperate
Click to expand...
Click to collapse
OK...STOP TRYING THINGS!! you might mess the device. I will send u a RUU in a PM that you will have to flash over fastboot....if you need help just let me know that way and we will work the way out.

help with get back stock rom from custom rom

hi, i have this htc one x.
this is fastboot info (fastboot getvar all)
Code:
(bootloader) version: 0.5a
(bootloader) [COLOR="Red"]version-bootloader: 1.39.000[/COLOR]0
(bootloader) version-baseband: 5.1204.164.30H
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) [COLOR="Red"]version-main: 3.14.771.34[/COLOR]
(bootloader) serialno: HT23TW126661
(bootloader) imei: 359188042590570
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) [COLOR="Red"]cidnum: H3G__G04[/COLOR]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4179mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.826s
actually it has running cyanogen rom, but i wanna get back to stock rom.
as info, i haven't nandroid backup or anything else.
i have downloaded latest ruu from Hutchison, but i don't find exactly rom. H3G__G04 (H3G_SWE)
i have downloaded rom from H3G from UK. and i tried flash this rom, but i get bootloader error.
i almost forget it. i was locked bootloader to run RUU, and i have read many threads from forum.
anybody can help me to get back to stock rom please?

hyber_99 said:
hi, i have this htc one x.
actually it has running cyanogen rom, but i wanna get back to stock rom.
as info, i haven't nandroid backup or anything else.
i have downloaded latest ruu from Hutchison, but i don't find exactly rom. H3G__G04 (H3G_SWE)
i have downloaded rom from H3G from UK. and i tried flash this rom, but i get bootloader error.
i almost forget it. i was locked bootloader to run RUU, and i have read many threads from forum.
anybody can help me to get back to stock rom please?
Click to expand...
Click to collapse
What sense version do you want in result: 4+ or 5?
Did you update your phone via OTA earlier?
Post bootloader error here, please. Looks like your bootloader is updated and do not match requirements to flash RUU from Hutchison.

1.- i dont know what is better, if 4+ or 5.
2.- in fact the phone was updated by other person, i don't know what he did :/
3.- let me flash ruu again and post bootloader error.
if it's usefull, it has Team Win Recovery Project v2.4.1.0 installed.
thanks for reply

genocide_ru said:
What sense version do you want in result: 4+ or 5?
Did you update your phone via OTA earlier?
Post bootloader error here, please. Looks like your bootloader is updated and do not match requirements to flash RUU from Hutchison.
Click to expand...
Click to collapse
Error 140, error with bootloader version.
and if i try with Europe RUU i got Error with Carrier ID.

hyber_99 said:
Error 140, error with bootloader version.
and if i try with Europe RUU i got Error with Carrier ID.
Click to expand...
Click to collapse
Well, looks like firmware\hboot was updated and latest RUU for your CID requires older firmware\hboot.
So, you can't use old RUU to go back to stock.
You need to flash stock ROM for 1.39 hboot from recovery
Try to find ROM like this one, but older: http://forum.xda-developers.com/showthread.php?t=1546970&highlight=*stock*
I guess you need to search 3.18 or 3.20 version, don't remember wwich one will work with 1.39

ok, i'll search it.
thank you sir, i'll let you know the results.

one more question, can i use this method posted here? http://forum.xda-developers.com/showthread.php?t=1927048
exactly this:
Nand for H3G__106 - thanks to Jackster88
Part 1
Part 2
Quote:
Instructions:
***For this nand to work you need HBOOT 1.39 and cwm***
1) go into fastboot and enter "fastboot oem lock" - the device will reboot
2) go into fastboot again and enter "fastboot oem rebootRUU" - there will be a black screen with a silverish HTC logo
3) enter "fastboot flash zip firmware.zip" (you need the firmware.zip from page 1 for this)
3a) enter the same again, the green bar under the logo should go to 100% (either after the first or second time)
4) enter "fastboot reboot-bootloader" to go back to your fastboot
5) unlock your device again with the unlock code ("fastboot flash unlocktoken Unlock_code.bin")
6) Restore your old boot.img (fastboot flash boot name_of_boot_file.img) and recovery (fastboot flash recovery name_of_recovery_file.img), make sure you copied them from the nandroid backup folder we created earlier into the folder that contains the fastboot.exe you're using.
7) Reboot and you should now have Hboot 1.39 with your old boot and recovery.
(8) If it won't work we still have the backup ready to restore the old system, Hboot isn't changeable right now on S-ON devices outside of the RUU routine - so even if you restore your nandroid you should still have Hboot 1.39 now)
Confirmed working with H3G__001, H3G__003, H3g__G04
Click to expand...
Click to collapse

hyber_99 said:
one more question, can i use this method posted here? http://forum.xda-developers.com/showthread.php?t=1927048
exactly this:
Click to expand...
Click to collapse
yes, you can try this method
except, I guess you need not flash firmware, because you are already on 1.39

genocide_ru said:
yes, you can try this method
except, I guess you need not flash firmware, because you are already on 1.39
Click to expand...
Click to collapse
thank you very much.
after all i solve my problem installing RENOVATE Final 4 Rom ------ http://forum.xda-developers.com/showthread.php?t=1705334&highlight=3+20
after installing rom, we need flash kernel manually i flashed stock kernel.
my problem was that with cyanogen 10.1 this phone cann't accept unlocking code,
but now with renovate rom, code was accepted and phone now is sim unlocked
thank you very much for your time

hyber_99 said:
thank you very much.
my problem was that with cyanogen 10.1 this phone cann't accept unlocking code,
but now with renovate rom, code was accepted and phone now is sim unlocked
thank you very much for your time
Click to expand...
Click to collapse
No problem, man!
Glad I helped you with this :good:

Screwed Up Need Help URGENT

Hi. My phone has had issues with not being able to be mount backups on TWRP and have tried everything to fix the problem with no luck. I read somewhere on a post that the only way I can fix my problem is to relock my bootloader and flash a RUU which I'm in the process of doing now. This all started when I accidentally deleted my system files (which was stupid) in TWRP. Have I screwed up and will I be able to flash the RUU onto my phone.

NEVER do anything until you got the correct files. Who says there is a RUU ? we need info.....
Post the outcome of :
Fastboot getvar all (and del the IMEI & SERIAL)
Can you enter the bootloader and the recovery ?

Mr Hofs said:
NEVER do anything until you got the correct files. Who says there is a RUU ? we need info.....
Post the outcome of :
Fastboot getvar all (and del the IMEI & SERIAL)
Can you enter the bootloader and the recovery ?
Click to expand...
Click to collapse
Thanks for the quick response, it's really late right now but hopefully I can post those details tomorrow morn. I can enter bootloader/hboot which my computer recognizes. Though I have relocked the bootloader which I can easily unlock, it's status is relocked. My recovery (TWRP) was killing me though as every time I pushed a file through adb which was received the bloody program spat out an error every time about being unmountable to the system and cache. I know I shouldn't have rooted my device if I didn't know what I was doing and what did you mean about not having the correct files? I did have a cm11 stable backup but that wouldn't "mount to disk" either. From what I have heard I think this is a soft brick which would mean it is repairable? Or is it just a lost cause?

Also if this helps, I am s-on and wiped my dalvik, cache, data and accidents the system. I also have a 32 gb sd card installed on the device.

Cool. The easiest way is to unlock the bootloader, load a rom.zip (preferably) a sense 6 (close to stock rom like arhd or maximus) and perform a full wipe in the recovery and install the rom.zip via the recovery (external sd)
See if there are any errors in this process

Mr Hofs said:
Cool. The easiest way is to unlock the bootloader, load a rom.zip (preferably) a sense 6 (close to stock rom like arhd or maximus) and perform a full wipe in the recovery and install the rom.zip via the recovery (external sd)
See if there are any errors in this process
Click to expand...
Click to collapse
Tried this, if I try to load a rom onto my m8 it will automatically fail. The rom is not able to be mounted to anything. I also tried flashing a boot.img to try to get it to startup but it also failed from the same reasons as flashing a sense base rom and cm11. Also before I cleared the system partition I had a gpe rom installed if that helps.

Was it a complete gpe or just a Rom? Also if Roms are failing to install get the sdcard from the phone and use a card reader...then put the zip on it and flash it..normally a boot.img fastboot should be flashed without problems

Read this thread carefully, it has info about not mounting issues !
http://forum.xda-developers.com/showthread.php?t=2850470
Maybe this applies to you too

Mr Hofs said:
Read this thread carefully, it has info about not mounting issues !
http://forum.xda-developers.com/showthread.php?t=2850470
Maybe this applies to you too
Click to expand...
Click to collapse
Ok now I am able to do the fastboot getvar all cmd, here it is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---
(bootloader) imei: ---
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: VODAP021
(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
all: Done!
finished. total time: 0.204s
Hope this helps
Also I have tried to fix using the solution mentioned though I don't know where to download the "mkfs.ext4 binary".

Mr Hofs said:
Who says there is a RUU ? we need info.....
Click to expand...
Click to collapse
There is an RUU for the AT&T Variant online. I used it to restore my M8 back to stock. There is a link here, you just got to look for it.

Oditius said:
There is an RUU for the AT&T Variant online. I used it to restore my M8 back to stock. There is a link here, you just got to look for it.
Click to expand...
Click to collapse
Hi, would I be able to flash an RUU onto my m8 International version with s-on?

jarrodli2 said:
Hi, would I be able to flash an RUU onto my m8 International version with s-on?
Click to expand...
Click to collapse
Yes,you can....find the ruu. And as for that file you could have taken the initiative to PM the user that has it !
Oditius said:
There is an RUU for the AT&T Variant online. I used it to restore my M8 back to stock. There is a link here, you just got to look for it.
Click to expand...
Click to collapse
LOL People rely on having a ruu to much. Good luck in finding one for him. Since he is s-on it has to match his official main too because downgrading is not an option (with a ruu)
1 ruu for the AT&T....does it work on a Sprint device ? Does it work on a international carrier branded device ?

Mr Hofs said:
Yes,you can....find the ruu first
---------- Post added at 04:46 AM ---------- Previous post was at 04:44 AM ----------
People rely on having a ruu to much. Good luck in finding one for him. Since he is s-on it has to match his official main too because downgrading is not an option (with a ruu)
Click to expand...
Click to collapse
GOD YES!, i've somehow managed to get the bloody device to boot up but now its stuck in a bootloop. I think i opened up a custom rom extracted the boot.img file and flashed it to something (not sure what). Does this mean i have to manually replace each partition (data, cache, system ect.) with a part of a rom?

I would install a fresh rom via the sdcard.
And you "think" you opened a rom.zip and flashed a boot.img ? Seriously .....

Mr Hofs said:
I would install a fresh rom via the sdcard.
And you "think" you opened a rom.zip and flashed a boot.img ? Seriously .....
Click to expand...
Click to collapse
Unfortunaly the problem still persists (log) ;
E: Can't mount /sdcard
E: Can't mount /data
E: Can't mount /cache
E: Can't mount /system
Installation aborted.
I really don't know how i've gotten to this point, should I just take my phone back to the manufacturer for repair?

Oditius said:
There is an RUU for the AT&T Variant online. I used it to restore my M8 back to stock. There is a link here, you just got to look for it.
Click to expand...
Click to collapse
Does it matter what m8 you have...like I have a international one m8 so can I use the at&t RUU
Sent from my HTC One_M8 using XDA Free mobile app

No you need to PM the guy with the mkfs file and fix that first.

ok just pm'ed him, hope he can respond soon. As for the state of my phone, is it soft or hard bricked? I just can't tell the difference because other people in the same situation as me have given up.

Its soft......as long as you can reach the bootloader it could be fixed.
ILIVE4HEAD said:
Does it matter what m8 you have...like I have a international one m8 so can I use the at&t RUU
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
If you want a phone that doesn't work.....then yes !

Mr Hofs said:
Its soft......as long as you can reach the bootloader it could be fixed.
If you want a phone that doesn't work.....then yes !
Click to expand...
Click to collapse
Lol thanks
Sent from my HTC One_M8 using XDA Free mobile app

Brick?

Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo

mtt_73 said:
Hi,
I have a big problem with my HTC one M8.
I was tring to back sense from GPE conversion, and now I do not know how to proceed. Maybe bricked my phone.
My situation is as follows:
Relocked. Adb can't find my device so I can not unlock again.
No recovery, no ROM installed. So, I can not flag USB debug. Can't proceed since relocked. Any suggestion?
Matteo
Click to expand...
Click to collapse
im going to assume your phones is s-off?

Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Thank you.
Sent from my Nexus 4 using XDA Free mobile app

mtt_73 said:
Yes s-off. Not sure how, but I am in recovery. Something looks like stock, I think. What can I do from here? Should I install twrp recovery? Or what else?
Click to expand...
Click to collapse
You can't install custom recovery with a (re)locked bootloader.
With s-off, you shouldn't ever relock the bootloader, as its no longer a requirement to RUU once s-off. But that's neither here nor there at this point, just info for future reference.
Any response to: fastboot devices
Make sure the phone is in fastboot mode.
Try to run the GPE RUU with phone in fastboot mode, to get the phone back up and running at least. Assuming you are still on the GPE CID and MID.

How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Sent from my Nexus 4 using XDA Free mobile app

mtt_73 said:
How can I flash ruu gpe with boot loader relocked? Is it possible? It gives me error.
Click to expand...
Click to collapse
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.

Hi guys,
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
1)flashing twrp via fastboot:
C:\adb>fastboot flash recovery C:\adb\openrecovery-twrp-2.8.5.0-m8.img
target reported max download size of 1830727680 bytes
sending 'recovery' (16086 KB)...
OKAY [ 1.438s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.500s
2) flashing stock recovery via fastboot( i dont know if i had the right one):
C:\adb>fastboot flash recovery C:\adb\recovery.img
target reported max download size of 1830727680 bytes
sending 'recovery' (14109 KB)...
OKAY [ 1.262s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.277s
3) 'booting' same stock recovery- what changed now are 3 android skaters for cca 0.2 sec when i try to enter recovery or start factory reset from bootloader, before it just went to fastboot usb mode.
C:\adb>fastboot boot recovery.img
creating boot image...
creating boot image - 14450688 bytes
downloading 'boot.img'...
OKAY [ 1.273s]
booting...
OKAY [ -0.000s]
finished. total time: 1.273s
Can please anyone help me? Thanks in advance
Here is data about the phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT.............8
(bootloader) imei: 35...........30
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

redpoint73 said:
I think you've got it backwards. With s-on the bootloader actually needs to be relocked (or locked) in order to RUU.
With s-off, RUU will run whether the bootloader is unlocked, relocked, or locked.
In other words, the bootloader being relocked is not the problem.
What is the error message?
Did you change the CID/MID yet (what are they currently)? The CID and MID need to match the RUU.
Click to expand...
Click to collapse
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Sent from my Nexus 4 using XDA Free mobile app

mtt_73 said:
I will try again later. If I am not wrong the error is about partition problem. It does not recognize the zip.
Click to expand...
Click to collapse
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------
mato123 said:
I have a problem with my one m8 at&t, unlocked, and i can only navigate in hboot in hboot & fastboot modes. no htc logo screens or sth like this.
when i try to go to recovery or do factory reset i get three android skaters on the screen for cca 0.2 sec and it returns to fastboot usb mode.
Its friends phone so i dont know what he had done to it, but i just want to make it work again, wiping data is not the problem.. can you tell me what should i do to get recovery( TWRP/ CWM) working, thats all i need for now because im going to s-off later. i tried to do something but it didnt work.
some things i have tried in that order:
Click to expand...
Click to collapse
I would highly suggest not to post to another user's troubleshooting thread like this, as it doesn't look like the same problem at all (and in my experience rarely is, even when folks will post "I have the same issue"). You really should have just started your own thread, and would have been justified doing so IMO. Posting here just confuses matters for you, the OP and those trying to help.
But DON'T start another thread now (and add even more confusion). I'll ask the mods if they can move this post to its own thread.

ok, sorry

redpoint73 said:
When you get a chance, you should list exactly (in detail, and in order) what you have done to the phone to get to this point.
I can't tell how far you go in the conversion (GPE>Sense) but it seems you at least got partway (if you indeed got a partition size error).
Also need to know current CID and MID.
Click to expand...
Click to collapse
Thanks for reply.
I went now in fastoob mode and tried to flash the RUU GPE again.
The error is:
macbooks-MacBook-Proownloads macbook$ ./fastboot-mac flash RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip
unknown partition 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
error: cannot determine image filename for 'RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip'
Just to clarify. I successfully when in GPE (with conversation). The problem was when going back to Sense. I do not know exactly what I did wrong.
My CID is 11111111
My MID is 0P6B10000
Really do not know how to proceed.
M

I unfortunately don't know jack about how to use fastboot and other actions on a Mac. I'm also not that familiar with running the RUU as a zip (I always do it on a PC with the RUU .exe).
But it looks like you just have the command syntax wrong. I think it should be:
fastboot oem rebootRUU
fastboot flash zip filename.zip
But it also look to me like nothing is actually "wrong" (aside from adb not working?). The phone not booting after relocking the bootloader is normal and intentional. You should just be able to run the desired Sense RUU, provided you have the right MID.

I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M

mtt_73 said:
I am back to GPE!
Stupid me! I missed a "zip" in the fastboot command...
Thank you for support!
I will try again to go back to Sense.
M
Click to expand...
Click to collapse
hehe try watch this movie: https://www.youtube.com/watch?v=CCGj0rOuiR4
Most important is the firmware flash... so partition layout etc is changed to sense like after that you can flash sense roms etc. (for example viper rom as in video)

0kk0 said:
Most important is the firmware flash... so partition layout etc is changed to sense
Click to expand...
Click to collapse
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.

redpoint73 said:
Some folks have had to do this, some haven't. But yes, if the RUU fails and gives a image size error, flashing the Sense firmware manually (then RUU) is the right thing to do.
This part has never made sense to me, since the RUU flashes firmware anyway, by definition. All I can guess, is that it has to do with the sequence in which the firmware is flashed (versus other partitions) in the RUU.
Click to expand...
Click to collapse
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Sent from my HTC One_M8 using xda Forum

mtt_73 said:
So, even if the sense RUU is available, to go back to sense I need to flash the firmware before to flash the RUU. Right?
Click to expand...
Click to collapse
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.

redpoint73 said:
I just said in the post you quoted: some folks are fine just running the RUU (to convert from GPE to Sense); but when the RUU alone doesn't work, run the firmware manually first, then the RUU.
Running the firmware manually first (then RUU) has a higher chance of working, I'd say.
Click to expand...
Click to collapse
I did it. I am back to Sense now.
Any advice to remove tell HTC problem? I mean it says that I have a testing device. Is it because I am s-off? Should I go for s-on again? And how?
TY!

Variant System Version OTA Update Error

After a long wait I finally got my ota update to Nougat.
But there is another problem, I cant finish the update because my phone showed that error.
I'm on stock M9 in bootloader it says software status official, locked, and s-on. No root, as I have checked it using root checker. Recovery is there.
I never modified my phone. And its fine back when I updated from lollipop to mm via ota, there is no problem.
And as far as I know, my phone is on correct mid and cid, SKU 708, mid 0PJA10000 exactly the same with mid engraved on my phone, and cid HTC__044
But when I update mm to nougat, this variant system version error shows up
I have tried to flash RUU of my current firmware, but still nothing.
Please help me, where did I do wrong? or how can I solve this problem?

Bumping this because I got the same thing too.
My device is not even rooted!

Did you guys flash a RUU for your current firmware and try to download the OTA, again?

Flippy498 said:
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Click to expand...
Click to collapse
I did, but the problem stays there.

Flippy498 said:
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Click to expand...
Click to collapse
I dont know how to flash the RUU.
But anyway, is there a way to check whether i can flash the OTA on my own?

vglaksana said:
I did, but the problem stays there.
Click to expand...
Click to collapse
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
-marco- said:
I dont know how to flash the RUU.
Click to expand...
Click to collapse
Well, there is a thread pinned above all the other threads in this section that is even called "ReadMe" and people still tend to completely ignore it...
-marco- said:
But anyway, is there a way to check whether i can flash the OTA on my own?
Click to expand...
Click to collapse
If you can't flash an OTA via the software update function then you can't flash it via fastboot, either. Your phone doesn't pass the security checks that google implemented with android 5 so the method you use for flashing the OTA doesn't matter.
Flash a RUU and re-try to install the OTA. If that still doesn't matter then please copy and paste your fastboot getvar all output here (without your IMEI!), as well.

Flippy498 said:
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
Click to expand...
Click to collapse
Here it is
C:\Users\Vito G. Laksana\Desktop\New folder>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U114,10801_97.64.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC 044
all: inished. total time: 0.016s
Above is getvar all from before I flashed my current RUU. I believe it wouldn't change anything, as I can't get fastboot getvar all working now.

vglaksana said:
(bootloader) cid: HTC 044
Click to expand...
Click to collapse
If that is an exact copy of the output then it's no miracle that you can't install the OTA. That CID doesn't exist. It needs to be HTC__044 (8 letters, numbers or symbols in total and no spaces). You need S-OFF for being able to correct your CID.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
If that is an exact copy of the output then it's no miracle that you can't install the OTA. That CID doesn't exist. It needs to be HTC__044 (8 letters, numbers or symbols in total and no spaces). You need S-OFF for being able to correct your CID.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ah my bad. The correct CID is HTC__044, as I mentioned in the thread first post.
I just using image to text converter because I have screencap of the output and didn't see that straight away.

Ah ok. And I already hoped that we found the cause of the problem... There have been some threads about devices that got bought in the US, S-OFFed and reflashed to non-US versions for selling them in other countries, in the past (around the time when firmware 2.x was the latest one). In most cases the sellers didn't convert the phones correctly and the buyers faced similar errors to your one when they tried to install an OTA.
Unfortunately there's nothing strange I can find in that output, then.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Ah ok. And I already hoped that we found the cause of the problem... There have been some threads about devices that got bought in the US, S-OFFed and reflashed to non-US versions for selling them in other countries, in the past (around the time when firmware 2.x was the latest one). In most cases the sellers didn't convert the phones correctly and the buyers faced similar errors to your one when they tried to install an OTA.
Unfortunately there's nothing strange I can find in that output, then.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks for helping me figuring out the problem.
If that is the problem, then why I have successfully update from lollipop to mm?
Yes i did buy it second hand, he said that the phone is from Singapore, and from the getvar output it is make sense that my phone came from Singapore.
Soo...I believe my only option is to S-OFF and convert to other version to get the update, is that correct?

I just re-read your opening post. Looks like I missed the part with the engraving. The US variant has a different engraving than the one you mentioned. So my assumption is probably wrong.
Since I have no clue what might cause your problem I actually don't see any other solution than getting S-OFF and converting the phone.
If there was a publicly available 4.x RUU for your SKU you could have asked Sneakyghost whether he creates a firmware package for you. By flashing that (S-OFF needed) you would have been able to use the 4.x RUU although you never installed the corresponding OTA. This way you could have kept your SKU. However, I haven't seen a public download link for such a RUU, yet. Therefore, you'll need to convert to a different SKU if you want the latest firmware.
Since you're still on firmware 3.x you need to flash one of Sneakyghost's 4.x packages before you can flash a 4.x RUU of the SKU that you want to convert to. Or you use a 3.x RUU for converting and try to install the OTA of the new SKU, afterwards. (The latter will probably take longer in total.)
Alternatively, you can wait some more days and see if some else has a better idea.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
Click to expand...
Click to collapse
I rebooted into bootloader to get the getvar but it doesnt work.
adb lists no devices.
Also, see the enclosed pic. that's as far as i managed to get.

Adb won't work if the device isn't booted to system or recovery mode.
And since the fastboot mode doesn't exist anymore on the M9 and all newer HTC phones you need to boot to download mode.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Adb won't work if the device isn't booted to system or recovery mode.
And since the fastboot mode doesn't exist anymore on the M9 and all newer HTC phones you need to boot to download mode.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
booted to system: adb sees device but says it's offline
booted to dl mode: adb can't see the device.
anyway, i took picture of what dl mode looks like. Attached.

Yeah, that's how it's supposed to be. ADB can only be used if the phone is booted to the system or the recovery mode. You can't use ADB commands while it's booted to the bootloader or the download mode. You need to use fastboot commands in these modes.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Yeah, that's how it's supposed to be. ADB can only be used if the phone is booted to the system or the recovery mode. You can't use ADB commands while it's booted to the bootloader or the download mode. You need to use fastboot commands in these modes.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
apparently i had a problem with drivers. i have fixed it now, that's why it gave empty devices.
Ok went back to bootloader mode. run fastboot getvar all:
Code:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT54GYJ05021
all:
finished. total time: 0.132s
this is instead the same taken from dl mode:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__044
all:
finished. total time: 0.006s
what now?

Mhm, there's nothing strange in that output, either.
Can you flash a RUU and re-try installing the OTA? If that doesn't fix the problem then the only other option is converting the phone as I already suggested to vglaksana.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Can you flash a RUU and re-try installing the OTA?
Click to expand...
Click to collapse
can you point me to a guide on how to do this?
and also where can i find my relevant RUU?
thanks.

I already did so in my first reply to you.
Sent from my HTC One M9 using XDA Labs