Develop Bugs

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:

htc one m8 twrp won't boot

Hello,
i have a problem with my htc one m8 any help will be appreciate.
i wan't to install the new rom viperone m8 but when i try to flash twrp latest version the recovery don't load it's reboot the bootloader only and don't get access to twrp to install rom
i'm able to flash philz_touch_6.26.6-m8.img and install skydragon latest rom
i'm also able to flash twrp-2.7.0.2-m8.img
here is my getvar all
c:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: <----------- i have doubt on this why it's empty
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__247
(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: eb00c9d0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
there is any solution for my problem?
can i install viperone 4.6.0 with wrp-2.7.0.2-m8.img
bootloader is unlocked and phone is s-off
Thank you in advance for your help.

First, remove Serial & Imei no from your post.
Can you remember whether your stock ROM is 4.21.1020.1 or 3.31.1020.9 ? Because both have hboot 3.19.0000
Don't use TWRP 2.7.0.2, use at least 2.8.4.0 or newer or latest.
Run these command
fastboot flash recovery NameofRecovery.img
fastboot erase cache
fastboot reboot-bootloader
now you should be able to enter recovery.
Advisable to reboot your device after doing fastboot erase cache and then boot to recovery

Hello,
thank you very much for your help.
i was on 4.21.1020.1
yes i have tried to use twrp-2.8.4.0-m8.img but not working
i also did what you said
fastboot flash recovery NameofRecovery.img
fastboot erase cache
fastboot reboot-bootloader
it's boot to bootloader it don't show twrp recovery.
very strange
thank you for your assistance
ckpv5 said:
First, remove Serial & Imei no from your post.
Can you remember whether your stock ROM is 4.21.1020.1 or 3.31.1020.9 ? Because both have hboot 3.19.0000
Don't use TWRP 2.7.0.2, use at least 2.8.4.0 or newer or latest.
Run these command
fastboot flash recovery NameofRecovery.img
fastboot erase cache
fastboot reboot-bootloader
now you should be able to enter recovery.
Advisable to reboot your device after doing fastboot erase cache and then boot to recovery
Click to expand...
Click to collapse

Yeah .. that's strange because your device on latest hboot.
Since your device is S-Off .. may I know why did you S-Off it ?
Seeing your device has stock CID/MID .. I'm scare that you jump from a lower 3.16.0000 hboot straight to 3.19.0000
Some people face problem too when they jump hboot.

i had to S-Off because in skydragon installation guides requirements
s-off is more easy
there is any solution to back and redo everything.
Thank you
ckpv5 said:
Yeah .. that's strange because your device on latest hboot.
Since your device is S-Off .. may I know why did you S-Off it ?
Seeing your device has stock CID/MID .. I'm scare that you jump from a lower 3.16.0000 hboot straight to 3.19.0000
Some people face problem too when they jump hboot.
Click to expand...
Click to collapse

Hello
Anyone got this type of problems?
There is any solution ?
Thank you

novalayer said:
yes i have tried to use twrp-2.8.4.0-m8.img but not working
i also did what you said
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
You understand "NameofRecovery.img" needs to be the actual file name (such as: twrp-2.8.4.0-m8.img)?

redpoint73 said:
You understand "NameofRecovery.img" needs to be the actual file name (such as: twrp-2.8.4.0-m8.img)?
Click to expand...
Click to collapse
@redpoint73, I think that is refering to an issue that occured with the new update from HTC. I have it too and another users the same. The recovery TWRP higher than twrp-2.8.1.0-m8.img does not boot and enter back to bootloader. We discused this in another thread and we don't have an resolution until now. Is not manifesting on all the phones and is not region and provider dependent. In this thread you can see more details. http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-stuck-boot-screen-t3186424

whiperhack said:
@redpoint73, I think that is refering to an issue that occured with the new update from HTC. I have it too and another users the same. The recovery TWRP higher than twrp-2.8.1.0-m8.img does not boot and enter back to bootloader. We discused this in another thread and we don't have an resolution until now. Is not manifesting on all the phones and is not region and provider dependent. In this thread you can see more details. http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-stuck-boot-screen-t3186424
Click to expand...
Click to collapse
Good info. Makes sense since he was able to flash TWRP 2.7.something.
But it would be useful for folks when they seek help to actually give the exact fastboot commands used, and not just cut and paste from somebody else's post (so we can't even be sure if he is using the right commands to install TWRP).

For some reason I only can use twrp-2.7.0.2. All the others get back to bootloader immediately. Is there a solution? It happens after going back to sense from GPE. I followed this thread: http://forum.xda-developers.com/showthread.php?t=2733523
Edit: Maybe is has somrthing to do with hboot? I have 3 .19.0.000

Petert87 said:
For some reason I only can use twrp-2.7.0.2. All the others get back to bootloader immediately. Is there a solution? It happens after going back to sense from GPE. I followed this thread: http://forum.xda-developers.com/showthread.php?t=2733523
Edit: Maybe is has somrthing to do with hboot? I have 3 .19.0.000
Click to expand...
Click to collapse
Something isn't right here. If you actually followed the thread you linked, you would not be on hboot 3.19.
The thread is also incredibly obsolete, as in 3 software/firmware generations old (the current is 4.16.xxx).
You most likely can't use the current TWRP due to outdated firmware. But you haven't provided enough info to tell for sure. Do fastboot getvar all and post the output (be sure to delete IMEI and serial numbers before posting the getvar data, as these are personal info).

redpoint73 said:
Something isn't right here. If you actually followed the thread you linked, you would not be on hboot 3.19.
The thread is also incredibly obsolete, as in 3 software/firmware generations old (the current is 4.16.xxx).
You most likely can't use the current TWRP due to outdated firmware. But you haven't provided enough info to tell for sure. Do fastboot getvar all and post the output (be sure to delete IMEI and serial numbers before posting the getvar data, as these are personal info).
Click to expand...
Click to collapse
I'm at work so atm cant provide a getvar all. What I did:
write cid 11111111, flashed 1.54.401.5-W_Splash.zip, reboot stock recovery, factory reset, installed TWRP. Again factory reset in TWRP. Then installed MaximusHD. Then I installed the first Nandroid I had from my software x.xx.161.x. Then did all OTA's. I think my hboot never updated during OTA.s

Petert87 said:
Then did all OTA's. I think my hboot never updated during OTA.s
Click to expand...
Click to collapse
And why do you think that? If that were the case, you would not be on hboot 3.19. Flashing 1.54 firmware would put you on hboot 3.16.

redpoint73 said:
And why do you think that? If that were the case, you would not be on hboot 3.19. Flashing 1.54 firmware would put you on hboot 3.16.
Click to expand...
Click to collapse
I thought that OTA updates the firmware automatically

Petert87 said:
I thought that OTA updates the firmware automatically
Click to expand...
Click to collapse
Yes, it does.
But why do you think it failed to do so?

redpoint73 said:
Yes, it does.
But why do you think it failed to do so?
Click to expand...
Click to collapse
Because I'm on old hboot and latest lollipop.

Petert87 said:
Because I'm on old hboot and latest lollipop.
Click to expand...
Click to collapse
You stated your were on hboot 3.19; which is the latest hboot there is.

redpoint73 said:
You stated your were on hboot 3.19; which is the latest hboot there is.
Click to expand...
Click to collapse
Sorry, there was a misunderstanding. I thought you said the latest was 4.16.xxx but that was the software not hboot. Software is 4.19.161.3

Petert87 said:
Sorry, there was a misunderstanding. I thought you said the latest was 4.16.xxx but that was the software not hboot. Software is 4.19.161.3
Click to expand...
Click to collapse
I see.
Well, it would seem that your firmware is up to date. So I see no reason why TWRP 2.8 would cause any trouble.
What versions of TWRP did you try exactly? I would focus on the current/latest which is 2.8.7.

redpoint73 said:
I see.
Well, it would seem that your firmware is up to date. So I see no reason why TWRP 2.8 would cause any trouble.
What versions of TWRP did you try exactly? I would focus on the current/latest which is 2.8.7.
Click to expand...
Click to collapse
I tried every version until one works and stopped at that one.

HTC ONE M8 stuck in bootloop

Hey guys
I know there are similar posts out there but none who describe my exact problem^^
It's like this: Earlier today, I wanted to go back to stock, fully. Which means I downloaded the stock backup and put it on my phone with TWRP. Then, I changed to stock recovery by using the HTC ONE M8 toolkit from hasoon2000.
As far, as good, everything worked just fine. And to have it completely back to stock (except for the still unlocked bootloader) I came up with the glorious idea of restoring to factory settings using the options in the phone's settings... aaaand now I'm stuck in the bootloop.
I meanwhile figured out how to enter the bootloader (volume up + power til screen turns fully black, then volume down) and I'm also able to access stock recovery through that... I of course tried factory resetting it through the bootloader and the recovery, I also took the sim card out as somewhere was suggested... but ultimately, it always goes back to the bootloop.
When connecting to the PC I hear the connecting sound... but that's it. It doesn't show up and thus I also can't access it through fastboot/adb
I ran out of ideas myself, do you have any?^^
Thanks!

M4C00kie said:
Then, I changed to stock recovery by using the HTC ONE M8 toolkit from hasoon2000.
Click to expand...
Click to collapse
Why you would you the toolkit for that? The toolkit is woefully obsolete (hasn't been updated in over a year, going on 2 years) and therefore causes more problems than it solves. Flashing stock recovery is really easy, its a single fastboot command. Don't over-complicate it.
M4C00kie said:
I also can't access it through fastboot/adb
Click to expand...
Click to collapse
Are you sure you are in bootloader-fastboot mode when you try fastboot commands (this is required)?
adb requires being in OS or recovery (and I'm not sure if stock recovery supports adb). And for the most part, fastboot is what you need to recover.
Need more info to help further. What CID version of the phone? If OS version number is shown on hboot screen, post it here. What are the version numbers or the stock nandroid, and the stock recovery you installed? If you can get fastboot work, do fastboot getvar all, and post the output.

redpoint73 said:
Why you would you the toolkit for that? The toolkit is woefully obsolete (hasn't been updated in over a year, going on 2 years) and therefore causes more problems than it solves. Flashing stock recovery is really easy, its a single fastboot command. Don't over-complicate it.
Click to expand...
Click to collapse
That's because I was using an older guide... good to know^^
redpoint73 said:
Are you sure you are in bootloader-fastboot mode when you try fastboot commands (this is required)?
Click to expand...
Click to collapse
That's what's strange... on the phone, it's showing FASTBOOT USB and it even makes this sound when connecting... fastboot commands still don't work though: "error: device not found"
the CID number is HTC__102, he version number of the stock nandroid and recovery was 4.16.401.10
regarding the OS number: on the hboot screen there's just written OS- <- is this the place where it's supposed to be?
thanks a lot for helping!

OK. fastboot commands ARE working (adb aren't, as predicted by you^^)
C:\Users\aaron_000\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.000
(bootloader) version-baseband: 1.25.2145000
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Update: as it was suggested to me on another thread, I downloaded an RUU (https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
my version & radio number are matching the ones in this RUU
so...
what now?^^ before I flash the RUU, I have to relock my bootloader, have I? and is this possible with S-ON?
oh, and would doing this even help in my current situation?
Thanks for helping

M4C00kie said:
OK. fastboot commands ARE working (adb aren't, as predicted by you^^)
Click to expand...
Click to collapse
Did you do anything different to get it working?
M4C00kie said:
Update: as it was suggested to me on another thread, I downloaded an RUU (https://www.androidfilehost.com/?w=f...4a4f68918d8199)
Click to expand...
Click to collapse
Does this mean you are hopping around in other threads? Or you just read it elsewhere?
The above is not linking me to any specific file. Might be the same link as the on the following thread:
http://forum.xda-developers.com/showthread.php?t=2701376
M4C00kie said:
before I flash the RUU, I have to relock my bootloader, have I? and is this possible with S-ON?
Click to expand...
Click to collapse
Relocking the bootloader is not just possible with s-on, its an absolute requirement to RUU.
Simple fastboot command: fastboot oem lock
M4C00kie said:
oh, and would doing this even help in my current situation?
Click to expand...
Click to collapse
Most likely, yet. I'd say almost certainly.
Also, you should delete your IMEI and serial number from your getvar info, as these are personal data. I should have mentioned that, but I didn't know you'd get fastboot working so quickly!

redpoint73 said:
Did you do anything different to get it working?
Click to expand...
Click to collapse
I might have confused adb and fastboot... pretty sure it was working all along
redpoint73 said:
Does this mean you are hopping around in other threads? Or you just read it elsewhere?
Click to expand...
Click to collapse
I initially posted this on another forum... realised too late that this one here was more appropriate and posted it here xD
redpoint73 said:
The above is not linking me to any specific file. Might be the same link as the on the following thread:
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
fixed, should link to the correct one now... have a look again
(this is it: https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
redpoint73 said:
Relocking the bootloader is not just possible with s-on, its an absolute requirement to RUU.
Simple fastboot command: fastboot oem lock
Click to expand...
Click to collapse
done.
redpoint73 said:
Most likely, yet. I'd say almost certainly.
Also, you should delete your IMEI and serial number from your getvar info, as these are personal data. I should have mentioned that, but I didn't know you'd get fastboot working so quickly!
Click to expand...
Click to collapse
deleted it. thanks for all your help so far!

M4C00kie said:
fixed, should link to the correct one now... have a look again
(this is it: https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
Click to expand...
Click to collapse
File name looks right. But can't personally vouch for the particular link or source. but it has plenty of downloads, so you should be fine.

redpoint73 said:
File name looks right. But can't personally vouch for the particular link or source. but it has plenty of downloads, so you should be fine.
Click to expand...
Click to collapse
question: the exe file tells me to turn on my phone... is bootloader considered turning on?^^ or should I rather download a zip version of it?

M4C00kie said:
question: the exe file tells me to turn on my phone... is bootloader considered turning on?^^ ?
Click to expand...
Click to collapse
As long as "fastboot" is selected in bootloader it will work.

redpoint73 said:
As long as "fastboot" is selected in bootloader it will work.
Click to expand...
Click to collapse
it worked!!
never heard a sweeter sound before than the HTC boot sound^^
thank you so much for all your help!

Completely erased Android using TWRP "advanced wipe". HOWTO install the OS again?

Completely erased Android using TWRP "advanced wipe". HOWTO install the OS again?
Hi
As the title says I completely erased my phone. The file structure seems to be there still from a fairly old ARHD 4.4.4 install. I did a Nandroid before doing this and it is backed up on my computer. Because it is an older (KK) ROM I'm on TWRP 2.8.1.0. I've tried to do
1 ADB pushed a version of that over to the device and tried to install with TWRP but it wouldn't install.
2 an ADB sideload of the latest GPE ("blues") by lyapota, but it didn't install. Does this take a super long time, as I'm trying it a second time. First time I cancelled after about 10 mins of no activity.
So, I'm in a bit deep here. At this point I'm even afraid to unplug the phone from the computer as I fear I'll never get it to boot again. Can I still access the phone by turning it on via booting into download mode/recovery?
If generous, can you walk me through step by step? Otherwise, is there a good guide that will step by step me through the process? A 2014 version of this thread referred the poor guy to the FAQ, but it doesn't cover this case.

If you can get/boot to recovery, just enable mtp in mount menu then you can browse your storage on PC.
Transfer your backup to restore or transfer a custom rom zip and install. But most custom rom work on lollipop and marshmallow firmware. As you said yours is a kitkat, there will be problem.
Or while on fastboot/bootloader see what is the hboot no. and the OS no or better to run command fastboot getvar all and post here the result without serial & imei no.

ckpv5 said:
If you can get/boot to recovery, just enable mtp in mount menu then you can browse your storage on PC.
Transfer your backup to restore or transfer a custom rom zip and install. But most custom rom work on lollipop and marshmallow firmware. As you said yours is a kitkat, there will be problem.
Or while on fastboot/bootloader see what is the hboot no. and the OS no or better to run command fastboot getvar all and post here the result without serial & imei no.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA14G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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
all: Done!
finished. total time: 0.050s
Should I start looking for a stock kitkat ROM or RUU?
Is there a thread you know of, or a good google search term I can start my learning on?
And most importantly, will anything I do ever eliminate my s-off?

That's a very old firmware that you have there.
It is 1.54.709.12 where the current one is 6.20.709.2; means you already missed 5 or 6 updates.
You can read post #1 on how-to, get the 1.54.709.12 backup on post #2 and the 1.54.709.12 stock recovery.img on post #4 then do multiple OTAs to the latest 6.20.709.2
See my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Noted that you have a S-Off device ... do you have a good reason why the device is S-Off ? Let say the reason was you wanted to make it EU WWE Intl GSM ... then there is another approach to this :
1. You need to change the MID from 0P6B11000 to 0P6B10000
http://forum.xda-developers.com/showthread.php?t=2708581
2. You install EU WWE Intl GSM RUU zip 6.12.401.4
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

ckpv5 said:
That's a very old firmware that you have there.
It is 1.54.709.12 where the current one is 6.20.709.2; means you already missed 5 or 6 updates.
You can read post #1 on how-to, get the 1.54.709.12 backup on post #2 and the 1.54.709.12 stock recovery.img on post #4 then do multiple OTAs to the latest 6.20.709.2
See my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Noted that you have a S-Off device ... do you have a good reason why the device is S-Off ? Let say the reason was you wanted to make it EU WWE Intl GSM ... then there is another approach to this :
1. You need to change the MID from 0P6B11000 to 0P6B10000
http://forum.xda-developers.com/showthread.php?t=2708581
2. You install EU WWE Intl GSM RUU zip 6.12.401.4
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Sounds OK, will that install a less effective radio, or are radios not affected? I have S-off for exactly this kind of this instance, but i guess it could be construed as the cause too.... The main reason is getting bloat off the ROM though.

Should be fine. As far as I can remember, both TWN and EU have same radio.
The different is slightly on rcdata... but that another story, won't affect anything at where you are now.
Being a S-Off device you can change the OS version at any time that like.

Weird, I downloaded minimal adb fastboot, and I can fastboot devices and get my serial, but adb devices returns device null. Am I missing something? The phone is in bootloader mode. Should I be in TWRP?

I got adb devices by going into TWRP, but now I do adb shell and it returns ~ # <[6n I'm guessing that means I need to be a super user...how? Every time I reboot TWRP it asks me if I want SU, but the process hangs.

Can the HTC utility restore a phone in this state, and not lose s-off? I put the external SD in the phone, with the nandroid I did today, and am trying to transfer it into the bare file system, where should I put it. Why can't TWRP just see the nandroid on the external? WIll the nandroid be of any value to me at this point?
When I try to do this:
6(b). For those with no OS, connect device to PC. In TWRP recovery go to mount, make sure MTP is enabled.
Then you can open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
7. Transfer the extracted x.xx.xxx.x folder (not x.xx.xxx.x_ckpv5 folder) and its content to the backup path on your device, so it looks like this :
TWRP/BACKUPS/SerialNo./x.xx.xxx.x
it tells me "cannot copy system.ext4.win000" "it's file size is larger than the device limit"
So do I need to re partition somehow? How would I do that? How can I find, and post, what the filesystem layout is now if more info is needed?
I have the TWRP backup on the external SD, but restore won't see it either.
Or what about the Hasson2000 toolkit to push an RUU to it?

Sorry guys, I still need help. I try to do adb shell, but can't seem to get root (su) . Because of this I am afraid of moving forward. I have changed my CID to GOOGL001 using HASOON2000's toolkit as I've decided I might as well go full goog since I'm at this point. I think my MID 0P6B11000 is OK, as it's mentioned in graffixnyc/Enewman17's GPE thread, correct? I've downloaded the MM H11 and it's waiting, but I'm afraid to move forward with the root problem better explained in the post above. Am I overly worried?

downwiththebanksters said:
I got adb devices by going into TWRP, but now I do adb shell and it returns ~ # <[6n I'm guessing that means I need to be a super user...how?
Click to expand...
Click to collapse
No .. while in TWRP you just run adb shell, no need SU because while in TWRP it's already rooted ..
so
adb shell
~ # <[6n
then paste in the code to change MID then type exit, exit
If you want to run the EU WWE RUU that I linked above, you also need to change the CID .. I suggest a SuperCID 11111111 then later you can run anything that you like as long has you have the correct MID for the RUU that you're going to install.
Now .. since you changed the CID to Google CID and intended to install a GPE RUU .. read through the thread that you linked .. can't help much .. maybe someone else will help you for the GPE conversion.
Still I suggest, instead of running a Google CID ... change it to SuperCID so you don't have to every time change the CID when you decide to run other RUU.
EDIT :
I just remember something .. there is a RUU zip for Taiwan HTC__621 that you can use (but you need to put back the CID to HTC__621 (the original CID) or make it SuperCID 11111111
The steps are the same as I posted before. You need to use htc_fastboot.exe and follow those fastboot commands to install a RUU zip.
Or if you have a microSD card, you can rename the RUU zip to 0P6BIMG.zip and put it on your microsd. On fastboot, select hboot .. it will scan the 0P6BIMG.zip and ask whether you want to update, volume up to update. Once completed, remove this 0P6BIMG.zip from your microsd.
Later you can do all the OTA to the latest.
Download 0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip here : http://androidruu.com/?developer=M8

Well as I said above I decided to try the full GPE RUU, so I followed these instructions. I used hasoon2000's toolkit to change the CID, my MID was compatible with the GPE. I then fastboot bootloader and:
Method 1
*ADB / Fastboot*
First, make sure you have the path to adb and fastboot setup in your system environment variables
When you open a command prompt, open it in the folder the zip is in. Hold shift, Left Mouse click, open command prompt here.
1. Rename the RUU.zip to something short and easy like RUU.zip
2. adb reboot bootloader "press enter" Wait till phone reboots into fastboot
3. fastboot oem rebootRUU "press enter" Wait till the phone is in RUU mode (black screen with HTC logo)
4. fastboot flash zip RUU.zip "press enter"
*You will get the following message: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
*RUU mode will reboot,
*Now run the same command again,
5. fastboot flash zip RUU.zip "press enter"
6. fastboot reboot-bootloader "press enter"
7. Select hboot, Do a factory reset in recovery. To enter the recovery menu when greeted by the Android with an exclamation, Hold Power button and click Volume UP.
8. Done, reboot system.
It took a long time for the ROM to install, but I was happy to see the Google splash screen rolling along.
Overall a bit scary as I worried about potential partition issues, but I could see the naked filesystem poking around in TWRP, and knew it wasn't a brick because I got the HTC splash screen and TWRP. I'm not totally in love with the GPE right now, as I miss the Nova launcher layout (fixable, installing now), and I can't toggle data with a homescreen widget (unfixable, now 3 clicks with dropdown...first world problems!!). Bottom line, be careful with what you wipe in TWRP! Thanks to you ckpv too!

bricked??

Hello, i am having a big trouble here
I was trying to format my phone but the bootloader's screen does not appear, it's been a while, when I enter the bootloader screen is just black, but the options work , I entered on recovery screen and went wipe, ticked all the options and I wipe , now my phone does not show anything, only black screen.
When i press power+up for 15 seconds, the cell shakes, i can flash recovery using fastboot by cmd, i can use anything with fastboot, but if i try something with adb, it says that i dont have adb devices. Can i solve my problem using fastboot option? i already flash a recovery by fastboot, but i cant enter on recovery, i can enter on fastboot reboot-bootloader for example.
Someone can help me plz?
Thx for attention. And sorry for bad english hehehe

Tirania_br said:
but if i try something with adb, it says that i dont have adb devices.
Click to expand...
Click to collapse
This is normal, and as it should be. adb command only work within OS and recovery, adb command do NOT work in bootloader.
I've seen a few reports of this issue (black screen in bootloader, although the options work if you select them "blindly"). If an RUU exists for your version, I would try to run that RUU, and see if that helps.

redpoint73 said:
This is normal, and as it should be. adb command only work within OS and recovery, adb command do NOT work in bootloader.
I've seen a few reports of this issue (black screen in bootloader, although the options work if you select them "blindly"). If an RUU exists for your version, I would try to run that RUU, and see if that helps.
Click to expand...
Click to collapse
thx, i found a RUU for my phone but very old, and found another current version here, but not for my version.
i have s-off on phone, these the information
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) cidnum: HTC__621
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I dont have any acess on cellphone screen, all i can do is fastboot code on my pc.
I have 2 questions.
How can i flash this RUU in my situation?
Is better use the old RUU of my version or the new of another version? i can use because i am s-off, or am i wrong?
thx for help

Tirania_br said:
I dont have any acess on cellphone screen, all i can do is fastboot code on my pc.
I have 2 questions.
How can i flash this RUU in my situation?
Click to expand...
Click to collapse
RUU is ideal to flash in fastboot mode. So being in fastboot mode (even if you can't see the screen) is a good thing.
Tirania_br said:
Is better use the old RUU of my version or the new of another version? i can use because i am s-off, or am i wrong?
Click to expand...
Click to collapse
Either should work under the proper conditions below:
1) Older RUU for your version may fail with Error 155. Going back to pre-MM by RUU usually requires flashing the older fimrware.zip, then RUU in order to bypass Error 155.
2) S-off alone is not enough to flash another version's RUU. You need to change the CID, and possibly the MID (if its different from what the RUU requires). But those aren't difficult with s-off.
Now, whether either one of those will help your issue (blank screen on bootloader) is the big question. But I'd say RUU is your best bet at a fix.

redpoint73 said:
RUU is ideal to flash in fastboot mode. So being in fastboot mode (even if you can't see the screen) is a good thing.
Either should work under the proper conditions below:
1) Older RUU for your version may fail with Error 155. Going back to pre-MM by RUU usually requires flashing the older fimrware.zip, then RUU in order to bypass Error 155.
2) S-off alone is not enough to flash another version's RUU. You need to change the CID, and possibly the MID (if its different from what the RUU requires). But those aren't difficult with s-off.
Now, whether either one of those will help your issue (blank screen on bootloader) is the big question. But I'd say RUU is your best bet at a fix.
Click to expand...
Click to collapse
Hi, before i do all steps i want to know if i will do everyting ok
my cell's information again
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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
i didnt get RUU of my version. I got 4.17.1540.9 - HTC One U.S. Developer Edition.
The steps
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot oem lock - i really need to do this?
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip OR Double-click the file and run it as any other executable program.
Its alright?

Tirania_br said:
i didnt get RUU of my version. I got 4.17.1540.9 - HTC One U.S. Developer Edition.
The steps
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot oem lock - i really need to do this?
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip OR Double-click the file and run it as any other executable program.
Its alright?
Click to expand...
Click to collapse
Just changing the CID is not enough to run that RUU, you need to match the Dev Edition MID as well. Instructions here: http://forum.xda-developers.com/showthread.php?t=2708581
The 4.17.1540.9 RUU is Lollipop. So it will probably fail with Error 155 as I already point out (Item 1 in my last post) forcing you to flash the firmware seperately, then RUU again. You're adding more complexity than needed (for no good reason). Therefore, I'd suggest the Dev Edition MM RUU 6.12.1540.4, if you are going to convert to Dev Edition (CID, MID, etc.). RUU 6.12.1540.4 linked at the bottom of the following: http://www.htc.com/us/support/htc-one-m8/news/
No need to relock the bootloader. This isn't required to RUU since you are s-off (only required to RUU when s-on). And I also do not recommend to lock the bootloader. There is no benefit to doing so in your case (since its not required to RUU) and an unlocked bootloader gives you more options if you run into more issues (you can flash custom recovery, etc.). So locking the bootloader is a waste of steps and time, and limits your options.

redpoint73 said:
Just changing the CID is not enough to run that RUU, you need to match the Dev Edition MID as well. Instructions here: http://forum.xda-developers.com/showthread.php?t=2708581
The 4.17.1540.9 RUU is Lollipop. So it will probably fail with Error 155 as I already point out (Item 1 in my last post) forcing you to flash the firmware seperately, then RUU again. You're adding more complexity than needed (for no good reason). Therefore, I'd suggest the Dev Edition MM RUU 6.12.1540.4, if you are going to convert to Dev Edition (CID, MID, etc.). RUU 6.12.1540.4 linked at the bottom of the following: http://www.htc.com/us/support/htc-one-m8/news/
No need to relock the bootloader. This isn't required to RUU since you are s-off (only required to RUU when s-on). And I also do not recommend to lock the bootloader. There is no benefit to doing so in your case (since its not required to RUU) and an unlocked bootloader gives you more options if you run into more issues (you can flash custom recovery, etc.). So locking the bootloader is a waste of steps and time, and limits your options.
Click to expand...
Click to collapse
thank you! i am almost there!
now the steps i have to do:
adb shell
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
adb reboot bootloader
fastboot getvar all //see if change mid
fastboot fastboot reboot-bootloader
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot getvar all //see if change cid
fastboot oem rebootRUU //need do this? if my Ruu is .exe
Double-click the file and run it as any other executable program. Follow the instructions by the program.
I have only one big problem now, the first command, i cant use adb, i can only use with fastboot, don't know why. adb device cant find, i have the drivers, the pc does a sound when i connect the phone, if i press power button on black screen bootloader i enter in fastboot mode and this commands i can do.
there is a command to do this with fastboot?

Tirania_br said:
I have only one big problem now, the first command, i cant use adb, i can only use with fastboot, don't know why. adb device cant find, i have the drivers, the pc does a sound when i connect the phone, if i press power button on black screen bootloader i enter in fastboot mode and this commands i can do.
Click to expand...
Click to collapse
adb command don't work in bootloader, as I already stated.
Do you still have TWRP custom recovery (its not clear, based on your descriptions so far). If so, boot into recovery, and try adb commands.

redpoint73 said:
adb command don't work in bootloader, as I already stated.
Do you still have TWRP custom recovery (its not clear, based on your descriptions so far). If so, boot into recovery, and try adb commands.
Click to expand...
Click to collapse
I did not have more , when I tried to enter on recovery mode the cell came into loop , I downloaded a new version of the recovery , for my surprise it worked! got access to recovery , now everything was much easier! thank you for help and understanding. Now I have my phone back ! haha

Tirania_br said:
I did not have more , when I tried to enter on recovery mode the cell came into loop , I downloaded a new version of the recovery , for my surprise it worked! got access to recovery , now everything was much easier! thank you for help and understanding. Now I have my phone back ! haha
Click to expand...
Click to collapse
i thinked my problem was gone, but when i try to run the Ruu i get always error 155.
i think is because my cellphone is cdma, from taiwan...
I took back my old cid and mid, restored a nandroid and now is ok.
The bootloader still with black screen, but i can live with it.
Thank u for attention, u help me a lot

Tirania_br said:
i thinked my problem was gone, but when i try to run the Ruu i get always error 155.
i think is because my cellphone is cdma, from taiwan...
I took back my old cid and mid, restored a nandroid and now is ok.
The bootloader still with black screen, but i can live with it.
Thank u for attention, u help me a lot
Click to expand...
Click to collapse
First .. your device is not a CDMA device, it is a GSM.
What you can try to fix that bootloader with black screen ... flash full signed 6.20.709.2 firmware.zip.
You can get the full signed firmware in my thread (post #5) : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860