so on my Verizon htc one I wanted to unlock my bootloader and get s-off. I used rumrunner which gave me s-off. after not being able to flash a recovery I was on a forum that suggested I type a certain adb command to see if I was actually unlocked. (I was able to finally get a custom recovery after trial and error) but after using that command It somehow managed to get my device s-on... is there any way to fix this? I don't want to run rumrunner again because it says you have to run that program with the device completely stock.
blake1886 said:
so on my Verizon htc one I wanted to unlock my bootloader and get s-off. I used rumrunner which gave me s-off. after not being able to flash a recovery I was on a forum that suggested I type a certain adb command to see if I was actually unlocked. (I was able to finally get a custom recovery after trial and error) but after using that command It somehow managed to get my device s-on... is there any way to fix this? I don't want to run rumrunner again because it says you have to run that program with the device completely stock.
Click to expand...
Click to collapse
ADB would not have put you S-ON. Can you plug the phone into your computer and reboot to bootloader and run the following command?
fastboot getvar all
And post the results?
blake1886 said:
so on my Verizon htc one I wanted to unlock my bootloader and get s-off. I used rumrunner which gave me s-off. after not being able to flash a recovery I was on a forum that suggested I type a certain adb command to see if I was actually unlocked. (I was able to finally get a custom recovery after trial and error) but after using that command It somehow managed to get my device s-on... is there any way to fix this? I don't want to run rumrunner again because it says you have to run that program with the device completely stock.
Click to expand...
Click to collapse
do you have a custom recovery installed already? if so then:
1. back up current set up in recovery
2. return to stock
3. run rumrunner
4. restore back up from step 1
5. ???????????
6. profit
isdnmatt said:
ADB would not have put you S-ON. Can you plug the phone into your computer and reboot to bootloader and run the following command?
fastboot getvar all
And post the results?
Click to expand...
Click to collapse
here are my results
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.0906
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA37HS910604
(bootloader) imei: 990004280399845
(bootloader) meid: 99000428039984
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4115mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-57eb7f637d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
wiredout46 said:
do you have a custom recovery installed already? if so then:
1. back up current set up in recovery
2. return to stock
3. run rumrunner
4. restore back up from step 1
5. ???????????
6. profit
Click to expand...
Click to collapse
how to i return to stock without s-off
blake1886 said:
how to i return to stock without s-off
Click to expand...
Click to collapse
is your bootloader still unlocked? you can check it via the bootloader screen.
wiredout46 said:
is your bootloader still unlocked? you can check it via the bootloader screen.
Click to expand...
Click to collapse
my bootloader is unlocked
blake1886 said:
my bootloader is unlocked
Click to expand...
Click to collapse
Follow these instructions, then S-OFF from scratch:
http://forum.xda-developers.com/showthread.php?t=2475216
isdnmatt said:
Follow these instructions, then S-OFF from scratch:
http://forum.xda-developers.com/showthread.php?t=2475216
Click to expand...
Click to collapse
but my phone is s-on... doesnt that say i need s-off to use the ruu?
isdnmatt said:
Follow these instructions, then S-OFF from scratch:
http://forum.xda-developers.com/showthread.php?t=2475216
Click to expand...
Click to collapse
this is the command that was suggested i typed and gave me s-on
fastboot oem writesecureflag 3
blake1886 said:
this is the command that was suggested i typed and gave me s-on
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
Somebody fooled you then. That command is used to change back to S-On.
GrayTheWolf said:
Somebody fooled you then. That command is used to change back to S-On.
Click to expand...
Click to collapse
is there any way to fix this?
blake1886 said:
is there any way to fix this?
Click to expand...
Click to collapse
At this point try running the rumrunner again will probably work. No other way available
blake1886 said:
my bootloader is unlocked
Click to expand...
Click to collapse
if your bootloader is unlocked you can flash a rom.
i had my bootloader unlocked at day one. you need a stock rom, and stock recovery and rumrunner should work.
I ran rumrunner with cwm installed and it worked fine.
Sent from my Nexus 7 using Tapatalk
The recovery does not need to be stock, I ran Rumrunner with the TWRP recovery had it worked just fine. What is important for Rumrunner is the stock rom and stock kernel, without those you will get errors.
When I was trying to get Rumrunner to work I was having a lot of trouble since I htcdev unlocked my phone on day one and had been flashing roms since then. I tried flashing every stock rom I could find and none of them worked for me, I even tried flashing partitions individually but nothing I tried could get Rumrunner to start the pourings sequence. The only thing that saved me was that I found a nandroid that I had saved on my hard drive that I completely forgot about. After I flashed the nandroid and enabled/diabled what needed to be, I ran Rumrunner and finally it completed after only 3 pourings.
SoCmodder said:
I ran rumrunner with cwm installed and it worked fine.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Wozzie said:
The recovery does not need to be stock, I ran Rumrunner with the TWRP recovery had it worked just fine. What is important for Rumrunner is the stock rom and stock kernel, without those you will get errors.
When I was trying to get Rumrunner to work I was having a lot of trouble since I htcdev unlocked my phone on day one and had been flashing roms since then. I tried flashing every stock rom I could find and none of them worked for me, I even tried flashing partitions individually but nothing I tried could get Rumrunner to start the pourings sequence. The only thing that saved me was that I found a nandroid that I had saved on my hard drive that I completely forgot about. After I flashed the nandroid and enabled/diabled what needed to be, I ran Rumrunner and finally it completed after only 3 pourings.
Click to expand...
Click to collapse
i was running into issues with rumrunner until i flashed a stock recovery and stock boot.img, after that everything worked.
wiredout46 said:
i was running into issues with rumrunner until i flashed a stock recovery and stock boot.img, after that everything worked.
Click to expand...
Click to collapse
Stock boot.img is what you need. You don't need the stock recovery. I also did it with TWRP as my recovery.
karn101 said:
Stock boot.img is what you need. You don't need the stock recovery. I also did it with TWRP as my recovery.
Click to expand...
Click to collapse
so if I have an unlocked bootloader and I am rooted, as long as I have a stock boot.img and stock rom I can run rumrunner again and nothing will be harmed? if so, where can I get this stock boot.img?
blake1886 said:
so if I have an unlocked bootloader and I am rooted, as long as I have a stock boot.img and stock rom I can run rumrunner again and nothing will be harmed? if so, where can I get this stock boot.img?
Click to expand...
Click to collapse
Should be able to just flash the stock .10 Full Odexed rom that I posted.
It contains the stock rom files and Boot.img.
Then run Rumrunner.
Related
Hey all
Just bought a M8 and I wanted to root if for a few apps I use, however I didn't know that by putting a custom recovery mod I would not be able to update my phone. So I am trying my best to get it back to stock however I can not find a RUU that matches my CID. Could someone please help me find a way to get my phone back to stock so I can get updates with no problems.
-Cheers
P.S: Lesson learnt, always back up your phone before attempting this bull**** -.-, miss my s4. Could find anything I needed on that thing.
(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: *CENSORED*
(bootloader) imei: *CENSORED*
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(bootloader) cidnum: HTC__622
(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
I have a posted a link to a backup on mega. Search me.
You don't need to unroot to get updates. If you're s-off just flash a stock recovery. If your s-on flash a stock recovery and relock the boot loader. Takes about 2 mins to do either.
ihave prblem
ashyx said:
You don't need to unroot to get updates. If you're s-off just flash a stock recovery. If your s-on flash a stock recovery and relock the boot loader. Takes about 2 mins to do either.
Click to expand...
Click to collapse
hi any help please iwant to go back stock room on htc on m8 and ihave on it caynogenmod and icant make fastboot of on mobile cant found it and my phone
unloked and when i install room stoc with recovery my phone crashed
what can ido to goo back to stook room
and thanksssssssssssss
ashyx said:
You don't need to unroot to get updates. If you're s-off just flash a stock recovery. If your s-on flash a stock recovery and relock the boot loader. Takes about 2 mins to do either.
Click to expand...
Click to collapse
When I mean unroot, i mean my recovery mode wont allow me to do uodates due to sense.
Also do I need to use a RUU that matches my cid or can i flash any generic os onto my htc? sorry i am a real rookie.
arkwolf said:
When I mean unroot, i mean my recovery mode wont allow me to do uodates due to sense.
Also do I need to use a RUU that matches my cid or can i flash any generic os onto my htc? sorry i am a real rookie.
Click to expand...
Click to collapse
Like I already said all you need do is flash one of the stock recoveries from this thread, use whichever you had originally for your CID.
http://forum.xda-developers.com/showthread.php?t=2701376
You can't ota with a custom recovery.
I love ViperROM and would never want to go back. They are very good about getting updates out pretty quick. So not long after an official OTA comes I think Viper is quick on it. I believe we already had one for the M8. My friend has tried a few roms and thinks Viper is the best.
ashyx said:
Like I already said all you need do is flash one of the stock recoveries from this thread, use whichever you had originally for your CID.
http://forum.xda-developers.com/showthread.php?t=2701376
You can't ota with a custom recovery.
Click to expand...
Click to collapse
Hey man, I wouldn't of asked this question if I could simply find one to match. On that thread I can not find a single one that matches my phone.
arkwolf said:
Hey man, I wouldn't of asked this question if I could simply find one to match. On that thread I can not find a single one that matches my phone.
Click to expand...
Click to collapse
What was your original recovery version?
ashyx said:
What was your original recovery version?
Click to expand...
Click to collapse
no idea, anyway to find out?
I just looked at the software version of my phone under About and downloaded the matching recovery. Then I flashed the recovery, installed the OTA update, and reflashed TWRP after.
someone31988 said:
I just looked at the software version of my phone under About and downloaded the matching recovery. Then I flashed the recovery, installed the OTA update, and reflashed TWRP after.
Click to expand...
Click to collapse
My software version is 1.54.708.5, cant seem to find any version on the web that matches.
arkwolf said:
My software version is 1.54.708.5, cant seem to find any version on the web that matches.
Click to expand...
Click to collapse
I'll have a look tomorrow or the weekend, I might be able to hook you up. I have a couple of OTAs kicking around.
arkwolf said:
My software version is 1.54.708.5, cant seem to find any version on the web that matches.
Click to expand...
Click to collapse
Did you read anything on the stock backup page?
As long as the base number is the same then you should be able to flash a recovery that matches. You have software version 1.54.708.5 so just flash one that begins with 1.54.
The nearest is:
STOCK RECOVERY 1.54.707.5
Nothing will happen so just go ahead and try it.
Here's the OTA, but it won't install unless you already have the stock OS installed.
http://yun.baidu.com/s/1bnlFoDp
ashyx said:
Did you read anything on the stock backup page?
As long as the base number is the same then you should be able to flash a recovery that matches. You have software version 1.54.708.5 so just flash one that begins with 1.54.
The nearest is:
STOCK RECOVERY 1.54.707.5
Nothing will happen so just go ahead and try it.
Here's the OTA, but it won't install unless you already have the stock OS installed.
http://yun.baidu.com/s/1bnlFoDp
Click to expand...
Click to collapse
Ill do a backup and charge my phone tonight then I will give this a shot.
arkwolf said:
Ill do a backup and charge my phone tonight then I will give this a shot.
Click to expand...
Click to collapse
I've extracted and uploaded the stock recovery for your version, extract and flash via fastboot:
http://www.mediafire.com/download/h3iaxx95b2i8rmf/recovery_1.54.708.5.zip
ashyx said:
I've extracted and uploaded the stock recovery for your version, extract and flash via fastboot:
http://www.mediafire.com/download/h3iaxx95b2i8rmf/recovery_1.54.708.5.zip
Click to expand...
Click to collapse
If this works you will have my eternal gratitude.
I tried to flash offical rom and get this 32 header error.
Could anyone tell me how to solve it?
Many thanks!
How about telling us what you have done to your m8 first as what recovery u have did you unlock the bootloader
Sheesh
JohnM109R said:
How about telling us what you have done to your m8 first as what recovery u have did you unlock the bootloader
Sheesh
Click to expand...
Click to collapse
Ok, thanks for your heads up.
I have unlock and s-off my m8. And flash a GPE rom, which make my phone fails to recognise my SIM card. And then I flash Revolution HD 8.0, still no signal at all. Thus I tried to flash offical rom but failed.
I guess somehow you have killed your radio and you are running a custom recovery?
Post the output of - fastboot getvar all .
ashyx said:
I guess somehow you have killed your radio and you are running a custom recovery?
Post the output of - fastboot getvar all .
Click to expand...
Click to collapse
OK thanks. Sorry for my late reply.
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.14.21331931.LA02_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: HC44DWM01778
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B62000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
When you say you flashed the GPe ROM, did you use the RUU conversion or just a custom ROM?
EddyOS said:
When you say you flashed the GPe ROM, did you use the RUU conversion or just a custom ROM?
Click to expand...
Click to collapse
Thanks.
I use the RUU. And now since I managed to flash a custom rom on my M8, everytime it boot with a "Google" sign and the phone take a long time to boot up and it keeps rebooting all the time. Could you please help me out here?
OK, you HAVE to follow the guide in Post #2 of the GPe RUU thread to go back to a Sense-based ROM cause the partitions are changed with the GPe conversion. Until you do that it will fail to update any ROMs
EddyOS said:
OK, you HAVE to follow the guide in Post #2 of the GPe RUU thread to go back to a Sense-based ROM cause the partitions are changed with the GPe conversion. until you do that it will fail to update any ROMs
Click to expand...
Click to collapse
Thanks. And sorry for my stupid question: which is Post #2.
It's the second post in the thread...
deleted: not relevant to the issue at hand.
EddyOS said:
It's the second post in the thread...
Click to expand...
Click to collapse
Sorry. Do you mean this thread: [REF][GPE] HTC One M8 Google Play Edition Stock OTA URLs ? But I didn't see any guides on it. If I'm wrong, could you please kindly give me the link. I've been stuck on this issue like a week...
BerndM14 said:
Download the ROM again and try again, if it fails copy the .zip file to your computer, use a program like 7zip to extract the files and then use 7zip to zip it again.
It's strange but I did find that some of the .zip files that gets downloaded, firmware, ROMs etc can't be opened and read, throws errors even in windows but you can unzip it with 7zip and then re-zip it and it works fine.
I read somewhere(Can't recall where) that remote 32 header error occurs because the zip can't be properly read or unzipped, so perhaps the above might be a solution... I'm hoping so at least :fingers-crossed:
Click to expand...
Click to collapse
haha that'll teach me to eat while I have a post reply open, I didn't catch any of what you guys talked about with the conversion... :crying:
No, it's the RUU thread in Development that you originally used for the conversion in the first place
BerndM14 said:
deleted: not relevant to the issue at hand.
Click to expand...
Click to collapse
Thanks. I will try.
harvery said:
Thanks. I will try.
Click to expand...
Click to collapse
As I'm feeling nice, this is the thread I was on about...
http://forum.xda-developers.com/showthread.php?t=2733523
EddyOS said:
No, it's the RUU thread in Development that you originally used for the conversion in the first place
Click to expand...
Click to collapse
OK I found it. Since my phone is runing Revolutional HD Rom. Do i need to flash back to GPE to do this again? because my phone keep rebooting when i try "Boot into stock recovery"
harvery said:
OK I found it. Since my phone is runing Revolutional HD Rom. Do i need to flash back to GPE to do this again? because my phone keep rebooting when i try "Boot into stock recovery"
Click to expand...
Click to collapse
Plus everytime it boot up with a "Google“ sign even my phone is running Revolutioal HD or VIper...
Sorry for take up your precious time...
harvery said:
Plus everytime it boot up with a "Google“ sign even my phone is running Revolutioal HD or VIper...
Sorry for take up your precious time...
Click to expand...
Click to collapse
Since my phone reboot everytime. there's not enough time for me to set it up and enable USE debug, So I can change mid thus I failed whtn flash to GPE again.it said mid error when i flash gpe again
You don't need USB Debugging on at all, you just need to flash the firmware ZIP in RUU mode and then do the rest...5 minute job if you have any idea what you're doing
Hello,
I was s-on running a custom rom but wanted to go to stock update fw.So i relocked the bootloader, and that blocked me out of recovery and also a working rom. I can't use the unlocktoken as it asks for the unlock flag to be reset, which i cant do as it wont boot into a rom.
I also cannot find an RUU for my current main-version.
Edit:I think a 2.9.710.2 RUU would work, as i'm s-on
Any ideas?
Cheers
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.9.710.2
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: VODAP021
Click to expand...
Click to collapse
First off, can you boot into download mode and try this? http://forum.xda-developers.com/one-m9/general/hima-stock-rom-collection-htc-one-m9-t3095746
Otherwise, your phone is effectively bricked & there isn't a known workaround so far :/ . In this case it's best that you contact your isp or htc for servicing.
As I can see you need a Vodafone Australian RUU equal or higher than your version-main number.
Unfortunately I could not find one for you.
racerboy3801 said:
Hello,
I was s-on running a custom rom but wanted to go to stock update fw.So i relocked the bootloader, and that blocked me out of recovery and also a working rom. I can't use the unlocktoken as it asks for the unlock flag to be reset, which i cant do as it wont boot into a rom.
I also cannot find an RUU for my current main-version.
Edit:I think a 2.9.710.2 RUU would work, as i'm s-on
Any ideas?
Cheers
Click to expand...
Click to collapse
try this: http://llabtoofer.com/htc-ruu-flashing-service/
Thanks for the advice guys, i've since sent it back to the shop to see what they can do. Cheers
racerboy3801 said:
Hello,
I was s-on running a custom rom but wanted to go to stock update fw.So i relocked the bootloader, and that blocked me out of recovery and also a working rom. I can't use the unlocktoken as it asks for the unlock flag to be reset, which i cant do as it wont boot into a rom.
I also cannot find an RUU for my current main-version.
Edit:I think a 2.9.710.2 RUU would work, as i'm s-on
Any ideas?
Cheers
Click to expand...
Click to collapse
you can try this thread http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
i ran across it the other day looking for my sprint ruu
racerboy3801 said:
Hello,
I was s-on running a custom rom but wanted to go to stock update fw.So i relocked the bootloader, and that blocked me out of recovery and also a working rom. I can't use the unlocktoken as it asks for the unlock flag to be reset, which i cant do as it wont boot into a rom.
I also cannot find an RUU for my current main-version.
Edit:I think a 2.9.710.2 RUU would work, as i'm s-on
Any ideas?
Cheers
Click to expand...
Click to collapse
An RUU will do the job, might not even have to be from the same region, just to get you back up and running.
You should be able to force the device into recovery if you can get to the bootloader.
From the bootloader, i'm sure you could flash a recovery and perhaps even root the device (could be wrong there)
either way there would have been a way out of it.
Yeah so i couldn't get into a recovery as i had twrp running, and i couldnt flash a new one as it was relocked. I couldn't unlock it as i had no rom to boot into to turn the unlock flag. So yeah stuck in the bootloader. It's supposed to be back tomorrow so i'll keep you guys posted.
Hy guys, i hope someone can help me with this one.
I try the other days to root my phone, and all got smoth, then i update my firmware because WiFi will not work and i read somewhere that will be problem. And i update my firmware too, all was good, everything instaled sucefull but when i try to open it stay blocked on main screen. How to make more clear than that? The phone freeze where the HTC logo appear, i can't do anything more than that.
Some info i can get from fastboot:
*** Software status: Modified ***
*** RELOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.21.213311491.A04G
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-3.11.1700.5
eMMC- boot 2048MB
I think when i installed the firmware the proces delete everything on my phone, i dont have recovery or anything else. Can someone help please to restore to stock? Or at least to a soft that my phone to work?
Thanks! (And sorry for my bad english, not my first language)
pant3ras said:
Hy guys, i hope someone can help me with this one.
I try the other days to root my phone, and all got smoth, then i update my firmware because WiFi will not work and i read somewhere that will be problem. And i update my firmware too, all was good, everything instaled sucefull but when i try to open it stay blocked on main screen. How to make more clear than that? The phone freeze where the HTC logo appear, i can't do anything more than that.
Some info i can get from fastboot:
*** Software status: Modified ***
*** RELOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.21.213311491.A04G
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-3.11.1700.5
eMMC- boot 2048MB
I think when i installed the firmware the proces delete everything on my phone, i dont have recovery or anything else. Can someone help please to restore to stock? Or at least to a soft that my phone to work?
Thanks! (And sorry for my bad english, not my first language)
Click to expand...
Click to collapse
You still have KitKat firmware, as shown by your OS version. You CANNOT flash a modified firmware package while S-On. You need to either run a signed RUU, or go back to stock and use HTC's/your carrier's OTA updates.
Do you have a stock ruu? or maybe how to s-off? because i cant find anywhere firewater.
Maybe this will help with something:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(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: RUU
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.057s
So can anybody can help me? Please i am stuck on this. And when i want to flash the RUU from AT&T i still get the error 155: Unknow Error. Can someone help me? Please.
What firmware did you try to flash? It looks like it was GPE firmware.
Is your bootloader screen black or white now?
My bootloader screen it's black, it's that important?...
And the firmware was download from HDRevolution website.
pant3ras said:
My bootloader screen it's black, it's that important?...
Click to expand...
Click to collapse
Yup, that's very important. Black hboot screen is the GPE version (and white is Sense version hboot). You at least partially flashed a GPE firmware. This isn't supposed to happen with s-on (firmware for other versions should be blocked). But I do remember a while back, a few folks having the same issue; where a GPE firmware or RUU partially flashed (with s-on) and caused some problems.
pant3ras said:
And the firmware was download from HDRevolution website.
Click to expand...
Click to collapse
That doesn't help. Quite a few firmwares are posted there. What specific number firmware did you flash? Did you flash the firmware number (3.11.1700.5) shown OS number on your hboot screen?
---------- Post added at 12:03 PM ---------- Previous post was at 12:03 PM ----------
pant3ras said:
And when i want to flash the RUU from AT&T i still get the error 155: Unknow Error.
Click to expand...
Click to collapse
What RUU (file name) are you trying to flash?
redpoint73 said:
That doesn't help. Quite a few firmwares are posted there. What specific number firmware did you flash? Did you flash the firmware number (3.11.1700.5) shown OS number on your hboot screen?
Click to expand...
Click to collapse
The firmware i flash was 3.11.1700.5 yes.
redpoint73 said:
What RUU (file name) are you trying to flash?
Click to expand...
Click to collapse
That from the official page, this one:
"RUU_M8_UL_L50_SENSE60_ATT[email protected]_40.45.C33065.00_F_release_446225_signed_2"
And also i was trying with this one:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 I dont know where exactly i find this one, but this one like the one above give me the same error, now and before trying rooting my htc.
pant3ras said:
The firmware i flash was 3.11.1700.5 yes.
Click to expand...
Click to collapse
I don't know why you flashed this. Not only is it not current firmware (Kitkat, as another noted before), but its not even for your version (its GPE version firmware, as I mentioned).
pant3ras said:
That from the official page, this one:
"RUU_M8_UL_L50_SENSE60_ATT[email protected]_40.45.C33065.00_F_release_446225_signed_2"
Click to expand...
Click to collapse
That is the proper RUU for the AT&T version; and your bootloader is relocked, as it should be for RUU.
So I think the problem is the GPE firmware you flashed before.
Try flashing the proper firmware first, then RUU again, and hopefully that will work.
I can't find the 4.28.502.2 firmware. But 4.28.502.1 firmware is posted on the following. Use the Full stock firmware. Hopefully, this is close enough to 4.28.502.2 to work.
EDIT: Forgot to post the firmware link: https://docs.google.com/spreadsheets/d/1aNd_nm4Em1wamRLFT7qHM2c3O9_sg_H3ztBrGq1u9Ws/pubhtml
pant3ras said:
And also i was trying with this one:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 I dont know where exactly i find this one, but this one like the one above give me the same error, now and before trying rooting my htc.
Click to expand...
Click to collapse
That RUU will not work, anyway. Its for the Developer Edition, so the only way to run it would be to change your CID (s-off required, and working OS is needed to s-off).
---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------
pant3ras said:
or maybe how to s-off? because i cant find anywhere firewater.
Click to expand...
Click to collapse
Firewater was discontinued by its devs in December 2014. Since it has an online component (needed to connect to servers), it won't work even if you find the firewater binary.
Sunshine is the only current working s-off method, and as I mentioned, it requires a working OS to work.
redpoint73 said:
I don't know why you flashed this. Not only is it not current firmware (Kitkat, as another noted before), but its not even for your version (its GPE version firmware, as I mentioned).
Click to expand...
Click to collapse
I flash that firmware because have my cidnum and modelid, and i read that the firmware need to have the same cidnum and modelid.
redpoint73 said:
I can't find the 4.28.502.2 firmware. But 4.28.502.1 firmware is posted on the following. Use the Full stock firmware. Hopefully, this is close enough to 4.28.502.2 to work
Click to expand...
Click to collapse
Where can i find this firmware?
And i didn't know that firewater doesnt work anymore, and sunshine i think you have to pay 25$ per month, right?
pant3ras said:
I flash that firmware because have my cidnum and modelid, and i read that the firmware need to have the same cidnum and modelid.
Click to expand...
Click to collapse
Yes, firmware needs to have the same CID and MID. But the 3.11.1700.5 firmware doesn't go with your CID and MID (CWS__001 and 0P6B12000)
"1700" firmwares (such as 3.11.1700.5) are for the Google Play Edition (GPE) with CID of GOOGL001 and MID of 0P6B17000.
Proper firmwares for your AT&T CID and MID will have the number "502" in the position x.xx.502.x
pant3ras said:
Where can i find this firmware?
Click to expand...
Click to collapse
Sorry, forgot to post the link. I had the page open, and everything: https://docs.google.com/spreadsheets/d/1aNd_nm4Em1wamRLFT7qHM2c3O9_sg_H3ztBrGq1u9Ws/pubhtml
pant3ras said:
And i didn't know that firewater doesnt work anymore, and sunshine i think you have to pay 25$ per month, right?
Click to expand...
Click to collapse
That's right. And as I already stated, sunshine requires a working OS, which you don't have. And since getting the OS working again seems to be the main reason you want to get s-off, you see its quite pointless.
redpoint73 said:
Sorry, forgot to post the link. I had the page open, and everything: https://docs.google.com/spreadsheets/d/1aNd_nm4Em1wamRLFT7qHM2c3O9_sg_H3ztBrGq1u9Ws/pubhtml.
Click to expand...
Click to collapse
No problem And to flash this firmware i can do it like this:
f you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
Click to expand...
Click to collapse
pant3ras said:
No problem And to flash this firmware i can do it like this:
Click to expand...
Click to collapse
Yes, exactly.
redpoint73 said:
Yes, exactly.
Click to expand...
Click to collapse
I get this error when i try to flash the firmware:
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1826418688 bytes
sending 'zip' (57484 KB)...
OKAY [ 2.570s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.611s
Click to expand...
Click to collapse
pant3ras said:
I get this error when i try to flash the firmware:
Click to expand...
Click to collapse
You used the "full stock" firmware 4.28.502.1, correct? Not the "Combined, No wipe" one?
You can also try the 3.42.502.1 firmware.
redpoint73 said:
You used the "full stock" firmware 4.28.502.1, correct? Not the "Combined, No wipe" one?
You can also try the 3.42.502.1 firmware.
Click to expand...
Click to collapse
Yes, i use the full stock firmware. Now i will try with 3.42.502.1
Later edit: I get the same error when i try with the 3.42.502.1 stock
pant3ras said:
Yes, i use the full stock firmware. Now i will try with 3.42.502.1
Later edit: I get the same error when i try with the 3.42.502.1 stock
Click to expand...
Click to collapse
Those might be unsigned firmwares, but I thought they were signed.
I think your options at this point:
1) Find signed firmwares of the versions I recommended.
2) Unlock the bootloader again, flash TWRP again, then flash a 3.xx based custom or stock ROM (which will have working WiFi). Then s-off by sunshine so you can fix the firmware (will allow an unsigned firmware to be flashed).
Another thing to note, when you flashed the GPE firmware, it reverted the recovery back to stock recovery. Which is why you no longer have custom recovery.
redpoint73 said:
Those might be unsigned firmwares, but I thought they were signed.
I think your options at this point:
1) Find signed firmwares of the versions I recommended.
2) Unlock the bootloader again, flash TWRP again, then flash a 3.xx based custom or stock ROM (which will have working WiFi). Then s-off by sunshine so you can fix the firmware (will allow an unsigned firmware to be flashed).
Another thing to note, when you flashed the GPE firmware, it reverted the recovery back to stock recovery. Which is why you no longer have custom recovery.
Click to expand...
Click to collapse
And how i can unlock the bootloader again? and flash the TWRP?
pant3ras said:
And how i can unlock the bootloader again? and flash the TWRP?
Click to expand...
Click to collapse
Unlock the bootloader by HTCDev.com. Then flash TWRP with fastboot.
redpoint73 said:
Unlock the bootloader by HTCDev.com. Then flash TWRP with fastboot.
Click to expand...
Click to collapse
Ok, i succed to instal the TWRP and i unlock the phone, but i have no ideea what rom to instal. Can you help me with that please? I'm scare i will broke my phone again if i install something on my own again )
Hello,
I got an OTA update for my HTC one but i wasnt able to install it normally. so i went into TWRP recovery and FULLY-wiped my phone(system,data,cache,dalvik). When i proceeded to install the zip, i got an error saying:
file_getprop: failed to stat "/system/build.prop": No such file or directory.
E:Error executing updater binary in zip '...'
I got the same error when i tried flashing another ROM, dirty unicorns. I tried restarting my phone and installing again WITHOUT wiping anything and still nothing. When i connect the phone to my laptop, it shows the phone as a CD DRIVE. Can someone PLEASE help me?
TWRP:2.7.0.2
**TAMPERED**
**UNLOCKED**
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.16.2133156.UA10G
eMMC-boot 2048mb
OTA updates usually cannot be updated via Custom recoveries like CWM or TWRP. I suggest you do roll back to a stock rom using TWRP backups found in the forums, flash a recent version of TWRP and then try flashing custom roms.
Suggesting that you start with updating your current TWRP to 3.0.2
what's the OTA file name and size ?
can you post the result of getvar all after removing serialno and imei
Sent from my HTC One M8 using XDA Labs
ahmed.ismael said:
what's the OTA file name and size ?
can you post the result of getvar all after removing serialno and imei
Sent from my HTC One M8 using XDA Labs
Click to expand...
Click to collapse
Htc on(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA10G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__059
(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
And the name of the file is:
OTA_M8_UL_K44_SENSE60_MR_hTC_Asia_WWE_2.22.707.4-1.54.707.7_release_387917.zip
@Younuszain
from that i see you can access fastboot
well there is no RUU for your device but there is stock firmware,stock backup and stock recovery
you need to flash the firmware then flash twrp recovery then restore the backup and flash the stock recovery
by doing that you will be completely stock
ahmed.ismael said:
@Younuszain
from that i see you can access fastboot
well there is no RUU for your device but there is stock firmware,stock backup and stock recovery
you need to flash the firmware then flash twrp recovery then restore the backup and flash the stock recovery
by doing that you will be completely stock
Click to expand...
Click to collapse
Woah! Could you please elaborate in a step by step way please? doing This, for the first time.
Younuszain said:
Woah! Could you please elaborate in a step by step way please? doing This, for the first time.
Click to expand...
Click to collapse
I distinctly remember that I tried flashing the Unlocked/Developer firmware from this website: http://www.htc.com/us/support/rom-downloads.html
But, i got the same error as I've stated above while flashing.
Younuszain said:
I distinctly remember that I tried flashing the Unlocked/Developer firmware from this website: http://www.htc.com/us/support/rom-downloads.html
But, i got the same error as I've stated above while flashing.
Click to expand...
Click to collapse
You can't flash that RUU. Its not for your version, its for the US Unlocked or Developer's Edition, and that specific carrier ID (CID) and Model ID (MID) only. You don't have the right CID and MID to flash that RUU.
There seems to be a notion that the particular RUU is for any unlocked M8; and that notion is completely incorrect.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
Younuszain said:
I got the same error when i tried flashing another ROM, dirty unicorns.
TWRP:2.7.0.2
Click to expand...
Click to collapse
Your hboot and TWRP versions are far too old to install or run any current ROMs.
redpoint73 said:
You can't flash that RUU. Its not for your version, its for the US Unlocked or Developer's Edition, and that specific carrier ID (CID) and Model ID (MID) only. You don't have the right CID and MID to flash that RUU.
There seems to be a notion that the particular RUU is for any unlocked M8; and that notion is completely incorrect.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
Your hboot and TWRP versions are far too old to install or run any current ROMs.
Click to expand...
Click to collapse
So You're saying if i update my TWRP version, I should be able to install any other ROM?
Younuszain said:
Woah! Could you please elaborate in a step by step way please? doing This, for the first time.
Click to expand...
Click to collapse
You'll find the files and instructions here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Either flash updated firmware, the corresponding TWRP backup, as previously indicated. Or alternately, restore the TWRP backup that corresponds to your current firmware, restore corresponding stock recovery, then do multiple OTA updates to get to current firmware & software.
redpoint73 said:
You'll find the files and instructions here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Either flash updated firmware, the corresponding TWRP backup, as previously indicated. Or alternately, restore the TWRP backup that corresponds to your current firmware, restore corresponding stock recovery, then do multiple OTA updates to get to current firmware & software.
Click to expand...
Click to collapse
What if i just want to install a custom ROM, dirty unicorns?
Younuszain said:
What if i just want to install a custom ROM, dirty unicorns?
Click to expand...
Click to collapse
Update the firmware then flash the latest TWRP and flash your rom
Download the stock backup just in case you need it
Sent from my HTC One M8 using XDA Labs
ahmed.ismael said:
Update the firmware then flash the latest TWRP and flash your rom
Download the stock backup just in case you need it
Sent from my HTC One M8 using XDA Labs
Click to expand...
Click to collapse
Yeah but where do i find the latest firmware?! Apparently the one on the htc website corresponds only to the U.S variants. :/
Younuszain said:
Yeah but where do i find the latest firmware?! Apparently the one on the htc website corresponds only to the U.S variants. :/
Click to expand...
Click to collapse
It's the thread which redpoint link it
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
all you meed is there read to learn
Firmware section is post #5
Sent from my HTC One M8 using XDA Labs
ahmed.ismael said:
It's the thread which redpoint link it
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
all you meed is there read to learn
Firmware section is post #5
Sent from my HTC One M8 using XDA Labs
Click to expand...
Click to collapse
Ok So i follewed the instructions to flash the firmware and twas successful. Now my screen looks like thisThe bootloader had to be locked to flash the firmware):
**Software status: Modified**
**RELOCKED**
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
But now when i go to recovery, My screen blanks out and I get a Triangle with a red exclamation mark! So i went to FASTBOOT USB and ran:
fastboot flash recovery twrp.img
Which was given on the TWRP website. I got an error saying:
FAILED <remote: signature verify fail>
I even tried running:
fastboot oem rebootRUU
fastboot flash zip ".." for BOTH the twrp img file and the TWRP backup given in the link.
I get an error FAILED <remote: 12 signature verify fail>
I read somewhere that to flash TWRP I need to unlock the bootloader again and i have give the token on the HTCdev wesbite. But i tried registering there but i received no email from them.
What do i do now? :/
Younuszain said:
Ok So i follewed the instructions to flash the firmware and twas successful.
But now when i go to recovery, My screen blanks out and I get a Triangle with a red exclamation mark!
Click to expand...
Click to collapse
As would be expected, that is the stock recovery, which is a part of the stock/signed firmware; and therefore was installed when you flashed the stock firmware. You need to unlock the bootloader, and put TWRP back on the phone, if TWRP is what you want.
Younuszain said:
So i went to FASTBOOT USB and ran:
fastboot flash recovery twrp.img
I got an error saying:
FAILED <remote: signature verify fail>
Click to expand...
Click to collapse
This is normal, and expected. Unlock the bootloader again, either with the existing bin code, or go through the HTCDev.com process again, to get a new bin code.
You can't flash a custom recovery such as TWRP (or any other unsigned file) to recovery partition, with a locked bootloader. That is what it means to have a locked bootloader; and specifically what an unlocked bootloader allows you to do.
Younuszain said:
I even tried running:
fastboot oem rebootRUU
fastboot flash zip ".." for BOTH the twrp img file and the TWRP backup given in the link.
I get an error FAILED <remote: 12 signature verify fail>
Click to expand...
Click to collapse
Do not make up fastboot commands.Its simply a horrible idea. Unless you know exactly what you are doing you should only type in fastboot commands exactly as directed. You probably can't do any permanent damage with s-on, but you certainly can mess things up pretty well with the wrong fastboot commands.
For instance, what partition would TWRP be installing to, if you don't specify? Yeah, I don't know either. And that isn't a good thing.
Additionally, you don't seem to know what the TWRP backup file is. Its not a flashable zip. You shouldn't be flashing things, without bothering to read the instructions, and understand what they even are.
redpoint73 said:
As would be expected, that is the stock recovery, which is a part of the stock/signed firmware; and therefore was installed when you flashed the stock firmware. You need to unlock the bootloader, and put TWRP back on the phone, if TWRP is what you want.
This is normal, and expected. Unlock the bootloader again, either with the existing bin code, or go through the HTCDev.com process again, to get a new bin code.
You can't flash a custom recovery such as TWRP (or any other unsigned file) to recovery partition, with a locked bootloader. That is what it means to have a locked bootloader; and specifically what an unlocked bootloader allows you to do.
Do not make up fastboot commands.Its simply a horrible idea. Unless you know exactly what you are doing you should only type in fastboot commands exactly as directed. You probably can't do any permanent damage with s-on, but you certainly can mess things up pretty well with the wrong fastboot commands.
For instance, what partition would TWRP be installing to, if you don't specify? Yeah, I don't know either. And that isn't a good thing.
Additionally, you don't seem to know what the TWRP backup file is. Its not a flashable zip. You shouldn't be flashing things, without bothering to read the instructions, and understand what they even are.
Click to expand...
Click to collapse
Well, Thanks a lot for that info . As far as me not knowing, guess theres a first time for everything.
Could you direct me as to how to get the existing bin code to unlock the bootloader? Because i guess thats what I have to do next inorder to get my phone up and running again.
Younuszain said:
As far as me not knowing, guess theres a first time for everything.
Click to expand...
Click to collapse
My advice, is to learn by reading and understanding the guides and threads on this forum.
Do not learn by trial and error, unless you want to end up making your phone into an expensive paperweight. Don't experiment, don't make things up.
I recommend anyone wanting to mod these phones, to spend a minimum few hours reading and understanding the basic concepts, guides, etc. before doing anything. And if there is anything you don't fully understand, just come and ask, as there are plenty of folks here willing and able to help.
Younuszain said:
Could you direct me as to how to get the existing bin code to unlock the bootloader?
Click to expand...
Click to collapse
If you don't have it on your computer (and know where it is) then it can't be "retrieved".
Just go to HTCDev.com, and follow the instructions there to unlock the bootloader.
redpoint73 said:
My advice, is to learn by reading and understanding the guides and threads on this forum.
Do not learn by trial and error, unless you want to end up making your phone into an expensive paperweight. Don't experiment, don't make things up.
I recommend anyone wanting to mod these phones, to spend a minimum few hours reading and understanding the basic concepts, guides, etc. before doing anything. And if there is anything you don't fully understand, just come and ask, as there are plenty of folks here willing and able to help.
If you don't have it on your computer (and know where it is) then it can't be "retrieved".
Just go to HTCDev.com, and follow the instructions there to unlock the bootloader.
Click to expand...
Click to collapse
Thanks for the guidance. Will definitely be more careful from next time.
The Dev website isn't sending the confirmation mail though.
Younuszain said:
The Dev website isn't sending the confirmation mail though.
Click to expand...
Click to collapse
The website can be buggy. I think when I unlocked the bootloader on this or a previous HTC device, I had to use 3 different emails, before I got the confirmation email.