So I received an update for the phone and figured it should be ok given that it's a security update, first one in ages for HTC One m8 and my phone got stuck in boot screen. As I understand it this is what happens as a result of Lollipop and a rooted device, binary and all that rubbish. This I knew AFTER doing the update. Honestly didn't think it would be a problem with an official update but ok...
So this is how it went thus far.
Tried installing back older firmware - nothing.
Tried to RUU but can't, doesn't detect my phone.
Can't even install HTC MTP driver on windows, error code 10...
Device has been fully wiped.
Tried to put the ruu in .zip form on SD card 0p6bimg etc, SDCard it claimed was damaged and needed to be formatted. SDCard is wiped completely.
Stuck in boot screen, no way to flash custom recovery, custom rom etc as my device cannot be detected.
I've been trying to do the usual for close to 10 hours now that I've been busy with this phone and I'm about 1 minute away from thrashing this P.O.S to pieces against a wall. Before that happens I figured I might as well come on here and ask for anymore suggestions.
Thank you.
Additional details about phone: S-OFF, Originally used to be HTC_203 EU device, converted it to Developer Edition. MID/CID are still correct, never changed that after the initial conversion.
Don't know if it's of any relevance or not but in recovery screen(stock recovery of course) it shows following message at the bottom:
E : missing bitmap oem_unlock_bg
(Code -1)
E : missing bitmap oem_unlock_bg_yes
(Code -1)
E : missing bitmap oem_unlock_bg_no
(Code -1)
Hey old mate !
That's normal in stock recovery but what is written after those line is important for the error reading.
Have you tried to use a card reader to read your microSD ? Or you use that mount with TWRP ?
Which RUU.zip ? Is it the ROM.zip that you got from TEMP folder on PC ?
ckpv5 said:
Hey old mate !
That's normal in stock recovery but what is written after those line is important for the error reading.
Have you tried to use a card reader to read your microSD ? Or you use that mount with TWRP ?
Which RUU.zip ? Is it the ROM.zip that you got from TEMP folder on PC ?
Click to expand...
Click to collapse
It was ROM.zip from temp folder yes. I sorted the issue out though, for one or other reason it read the rom.zip after a huge struggle. I tried it at least 7 times and for some reason it took on the 8th, not that anything changed at all. It was the same .zip renamed to 0p6bimg.zip, don't know what changed to have it work after so many tries. The only real thing that "changed" was my frustration in it and I ended up hitting the phone against the desk Yes...it picked up physical damage on the side too, right by the volume buttons it "bent" out a bit :crying:
So the phone is working again but not very happy lol I lost all my data I had on my phone, lost all the data I had on my sdcard... Physical damage of course.
First OTA in ages and this is the nonsense a person has to deal with. Honestly I didn't expect it to give this problem as I haven't been to the forums in ages I didn't read up on this issue. Thought it would be fine lol. Quite disappointed but what can you do.
Hi, maybe your SD card has reached the end of its life? How old is it? Phone said it was damaged and then took a really long time to read.
Could be time for the 128gb upgrade...
Related
Hi - im stuck at the first hurdle....ive done the gold card - thats inside the desire. but when i try to run "step1-windows" from the r5-desire-root folder i get a strange error erasing 'cache' ... FAILED (status malformed (1 bytes))
but - this could be down to how the device manager sees the phone - do you configure usb to see the phone as "Android ADB interface", "Android bootloader interface" or "Android Composite Interface"
the first 2 i tried and got the same error so im not sure if its that....
Any help would be greatly appreciated...
Tar
Comfy
Just got a little further....got to the part where it sends the 13meg zip file to the phone gets to the last point where it says FAILED (remote: 42 custom id check fail) but then carries on and says ok....is it??
Right - found my problem and have moved on to the next. The error was down to the gold card a. not being created properly and b. the gold card info from the img not being written to the actual sd card. I had to save it twice (dont ask me why - its what i had to do). so, ive got through the first part i think and i want to format my now gold card....how do i do that then as when i format it and then use the hex editor to check it i still see the info in the first 170 blocks...? so, im half way there.
Don't format it as you'll need it for future updates...just use it as it is
ok - check.
Right so, im a little further again ( and now needing help) went through the step 2 part....after a bit of messing around i got to the recovery menu and did a wipe and then did a flash (rootedupdate.zip) now, it gets to the htc splash screen and keeps rebooting at that point like it cant find an os to boot into....anyone?
do i have to apply the rootedupdate first or can i go straight to a cooked build??
oh - the other thing is that if i start the phone and go to recovery i just get the phone with the red triangle i can only invoke the recovery menu when i run "step2-windows"
+ should i be doing all of this on the gold card memory card or on a stock memory card + i also need to know how to format a gold card properly as i used another card as a gold card and want to return that back to how it was so i can use it normally again.
ok - im there (dont use the gold card to actually install the rootedupdate.zip file) - thats what caused the phone to keep rebooting at the splash screen.
If anyone can id still like to know how to return a gold card back to stock card...
Oh - another thing - why do i still need the gold card anyway? - its rooted.
It's rooted but the CID (think that's the right term!!) of the phone is still vendor locked...easier way is to have used unrEVOked. I used to use the MoDaCo way at first but last time I had to root I used unrEVOked and it was all done in about 5 minutes! Seriously easy!!
Ah - so i can i reflash t'other way over the top of this??
Another question....ive flashed the radio (the one posted today and also flashed the cyanogen build) but - its sitting at the cyanogen splash screen at the moment (been there for 10 mins)
should i just try another image? or another radio??
at last im there - RTFM....had to install the right radio first, then wipe and then install CyanoGen. All working now. Just in case anyone thinks i like the sound of my own voice/posts its more of a "this is how i got it working for me" type thing - hopefully others who get the same problems will happen to stumble upon this while googling with a dead phone!
I was copying my SD Card to my computer. At some point I forgot I was transferring files and disconnected the usb cable. I reconnected the cable and all seemed right. So I continued on and rebooted my phone.
After a few minutes I noticed the green notification light blinking and assumed I had a text or mail. When I hit the power button on top to wake the phone the screen never came on. I pulled the battery and tried to reboot the phone. It would just vibrate 5 times and the screen would stay blank. So i tried recovery and it would work only with the USB cord plugged in. But it wouldn't do a nandroid backup or even see the sdcard.
when in recovery I get the error E:Can't mount /dev/block/mmcblk1p1 (or /dev/block/mmcblk1)
I tried getting a adb shell but it says no device connected
I tried using fastboot flash boot boot.img and fastboot flash system system.img
they would error with FAILED (remote: signature verify fail)
anyone have any suggestions?
oh in windows device manager it say ADB bootloader only when I am in HBOOT when in fastboot it says nothing but since it did push the system image I assume it does work.
if i go into recovery though (Windows7 Enterprise 32bit) it asks for a Qualcomm CDMA driver real quick(2 seconds) then goes to Unknown Device
fader01 said:
oh in windows device manager it say ADB bootloader only when I am in HBOOT when in fastboot it says nothing but since it did push the system image I assume it does work.
if i go into recovery though (Windows7 Enterprise 32bit) it asks for a Qualcomm CDMA driver real quick(2 seconds) then goes to Unknown Device
Click to expand...
Click to collapse
Sounds like you corrupted a partition or two. Just get an RUU PB31IMG.zip, copy it your card (you may have to take it out and fix it in windows first), and let bootloader see it. There are ways to manually NANDroid your phone in ADB/Recovery, but it doesn't sound like you want to go that deep nor do I know how to tell you to do it from the command line.
Good luck!
Thanks for the reply. The phone will not mount or see the SD Card. I put the sd card in my storm and it formatted it I put it into the Incredible but it still will not mount the SD Card.
I did go to the verizon store and my hopes where they had some way to format the partitions and force the OS on it. The guy looked at the phone and said we dont have a recovery console for the Incredible so I will have a new one sent to you probably will be Tuesday.
I thought the Dallas Cowboys boot screen and fastboot screen would tell him something wasnt right but he didnt know or he didnt care. I also thought it was odd he gave me the phone back. Shouldnt he have kept it to send back in?
I have ran into the same issue. Basically my phone was bootlooping after a bad rom install(my guess). Then when I tried my nandroid recovery backup, I got to this black screen and the phone would vibrate 5 times! I have never had this issue before.
I have tried various RUU PB31IMG.zip's to flash back to a stable system and nothing works. I have noticed after flashing different RUU images(stock 2.2, stock 2.1), the phone will either vibrate 3, 4 or 5 times. I believe these could be error code messages of some kind.
Has anyone else gotten this black screen, and the 5 vibrations????? This seems like it should be called the black screen of death because it honestly makes me want pull my hair out in frustration! Any knowledge would be greatly appreciated. thanks.
google this error: E:Can't mount /dev/block/mmcblk1p1 and there should be a link to a cyanogen forums thread and a link to an xda thread. those two will contain the information necessary to repartition your internal storage so you can boot into the OS again
illalliance said:
I have ran into the same issue. Basically my phone was bootlooping after a bad rom install(my guess). Then when I tried my nandroid recovery backup, I got to this black screen and the phone would vibrate 5 times! I have never had this issue before.
I have tried various RUU PB31IMG.zip's to flash back to a stable system and nothing works. I have noticed after flashing different RUU images(stock 2.2, stock 2.1), the phone will either vibrate 3, 4 or 5 times. I believe these could be error code messages of some kind.
Has anyone else gotten this black screen, and the 5 vibrations????? This seems like it should be called the black screen of death because it honestly makes me want pull my hair out in frustration! Any knowledge would be greatly appreciated. thanks.
Click to expand...
Click to collapse
I got the 5 vibration deal when I was trying to boot into recovery.....but was pressing volume up/power, instead of vol down/power......the 5 vibrations are a Qualcomm diagnostic test.
SLOflatlander said:
google this error: E:Can't mount /dev/block/mmcblk1p1 and there should be a link to a cyanogen forums thread and a link to an xda thread. those two will contain the information necessary to repartition your internal storage so you can boot into the OS again
Click to expand...
Click to collapse
I had googled that before making this post, nothing I found had helped me. I cannot say, for sure, that I found the post you are referring to though. I did finally manage to get the system to see the sdcard and PB31IMG.zip. I took the rom.zip from the Froyo RUU and I renamed it pb31img.zip. It went through and flashed everything but still nothing. When I later tried to do the same thing with the rom.zip from the 2.1 RUU the system said that it was an older version and would not flash it. So this seems to me that the flash went OK. Its like the main OS partition isn't bootable or something the system knows the OS is there it just cannot boot to it.
You said it. The main partition is corrupt, I will try and find the link to the thread about how to restore it just give me a second.
Here is the link Talk to Ciwrl; he is a very smart person when it comes to these problems.
tdavis42 said:
You said it. The main partition is corrupt, I will try and find the link to the thread about how to restore it just give me a second.
Here is the link Talk to Ciwrl; he is a very smart person when it comes to these problems.
Click to expand...
Click to collapse
I trashed my internal partitions yesterday and used this method to fix it.....had to end up un-rooting and starting over after I got the partitions back in order....but it did fix the problem.
tdavis42 said:
You said it. The main partition is corrupt, I will try and find the link to the thread about how to restore it just give me a second.
Here is the link Talk to Ciwrl; he is a very smart person when it comes to these problems.
Click to expand...
Click to collapse
Thanks a lot. I will work on it after work tonight.
As the title says. I tried to go back to stock and got stuck. I was new, and still am to this whole thing to a degree. I had a friend who helped me unlock, root, and slap on a custom rom. I learned about it in the process, but here is my problem. I tried to go back to stock, and locked my bootloader before I slapped on the stock rom. And I wiped the phone, cache, and dalvik etc.. well the OS is gone too. I would like to be able to use my SD card to load the stock rom but it wont read the Ext sd card. Brand new, 3rd diff card. I tried to use adb, but it wont see the device in the command prompt. I have the sdk dev installed and universal adb drivers as well as htc sync. I've rebooted multiple times to make sure drivers are useful. The apk installer can see my phone, adb commands do NOT. So for the moment my m9 is a paper weight, I've tried to read and follow the searches I've run across on here but I seem to be stuck. Phone boots, and stops at the white boot screen. I am S-ON and relocked.
This is the info it shows me
Radio-1.11
OS 1.32.651.30
When I reboot it goes into a white screen. gives options to reboot into bootloader, reboot to recovery etc... If I reboot to recovery it shows it is missing items
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code-1)
E:missing bitmap oem_unlock_bg_no
(Code-1)
handle_cota_install: install cwpkg to /data/cwtemp/cwpg.zip
handle_cota_install: install cwprop to /data/data/cwtemp/cwprop
E: fail to open file: /sys/devices/platform/android_usb/hostmode
Write host_mode error
handle_cota_install: No CW files. Skip installation
I can't access my drive on the phone to store files, the only thing I can use is my sd card since adb wont see devices. And my phone wont read from the SD card ( Tried 3 diff ones ). And if I goto apply from sd card I get
E: Find no match PARTITION: for package path /sdcard/ptt.zip
E: Unknown volume for path []
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package....
Opening update package....
E: Failed to map file
-----------
But if I goto download mode, the pc will see the phone though APK Installer through taskbar notification. But not adb.:silly:
Sorry if I caused some of you do go "Seriously dude??!!" This is a headache, this I do know. I just want to either get this phone working again through stock ) Right now it's just a bunch of load up to bootloader screen and stop. No OS. And once again, wont read rom from sd card, wont even see sd. Says it can't access it.
And if I goto recovery mode it tells me that same junk about No CW files. skip installation. Am I as screwed as it sounds?
aimjewels said:
As the title says. I tried to go back to stock and got stuck. I was new, and still am to this whole thing to a degree. I had a friend who helped me unlock, root, and slap on a custom rom. I learned about it in the process, but here is my problem. I tried to go back to stock, and locked my bootloader before I slapped on the stock rom. And I wiped the phone, cache, and dalvik etc.. well the OS is gone too. I would like to be able to use my SD card to load the stock rom but it wont read the Ext sd card. Brand new, 3rd diff card. I tried to use adb, but it wont see the device in the command prompt. I have the sdk dev installed and universal adb drivers as well as htc sync. I've rebooted multiple times to make sure drivers are useful. The apk installer can see my phone, adb commands do NOT. So for the moment my m9 is a paper weight, I've tried to read and follow the searches I've run across on here but I seem to be stuck. Phone boots, and stops at the white boot screen. I am S-ON and relocked.
This is the info it shows me
Radio-1.11
OS 1.32.651.30
When I reboot it goes into a white screen. gives options to reboot into bootloader, reboot to recovery etc... If I reboot to recovery it shows it is missing items
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code-1)
E:missing bitmap oem_unlock_bg_no
(Code-1)
handle_cota_install: install cwpkg to /data/cwtemp/cwpg.zip
handle_cota_install: install cwprop to /data/data/cwtemp/cwprop
E: fail to open file: /sys/devices/platform/android_usb/hostmode
Write host_mode error
handle_cota_install: No CW files. Skip installation
I can't access my drive on the phone to store files, the only thing I can use is my sd card since adb wont see devices. And my phone wont read from the SD card ( Tried 3 diff ones ). And if I goto apply from sd card I get
E: Find no match PARTITION: for package path /sdcard/ptt.zip
E: Unknown volume for path []
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package....
Opening update package....
E: Failed to map file
-----------
But if I goto download mode, the pc will see the phone though APK Installer through taskbar notification. But not adb.:silly:
Sorry if I caused some of you do go "Seriously dude??!!" This is a headache, this I do know. I just want to either get this phone working again through stock ) Right now it's just a bunch of load up to bootloader screen and stop. No OS. And once again, wont read rom from sd card, wont even see sd. Says it can't access it.
And if I goto recovery mode it tells me that same junk about No CW files. skip installation. Am I as screwed as it sounds?
Click to expand...
Click to collapse
Use the full 1.32.651.30 RUU here
(originally from this thread)
I highly recommend you use the 1.32.651.30 one and NOT the newer 2.xx ones, because in the 2.x.xxx.x ones, (Android 5.1), a new setting has been implemented "Settings -> Developer Options -> OEM unlocking", if that is not checked, and it's not by default (and this can only be done during the booted ROM), you will not be able to unlock your bootloader again!! (so be careful!!)
EDIT: oh, and as far as I know, the M9 (unlike it's predecessors) doesnt need a relocked bootloader for RUU, even with S-ON
nkk71 said:
Use the full 1.32.651.30 RUU here
(originally from this thread)
I highly recommend you use the 1.32.651.30 one and NOT the newer 2.xx ones, because in the 2.x.xxx.x ones, (Android 5.1), a new setting has been implemented "Settings -> Developer Options -> OEM unlocking", if that is not checked, and it's not by default (and this can only be done during the booted ROM), you will not be able to unlock your bootloader again!! (so be careful!!)
EDIT: oh, and as far as I know, the M9 (unlike it's predecessors) doesnt need a relocked bootloader for RUU, even with S-ON
Click to expand...
Click to collapse
Well now the problem is that everything goes fine up until it comes time to update the rom. I get an error code of 155 an unknown error. It tells me to use the correct ROM Utility and try again. But This is the correct one I'm using. I am a bit confused now. I have tried even reinstalling some drivers and such all over again just to make sure. And rebooted. It gives an error on the same part every time. It doesn't even get to Step 2/4
But on the plus side it does still respond to the reboot to bootloader command. The screen the phone gets stuck on otherwise...is the install screen. The arrows are not spinning and the progress bar has no progress. That is usually when I get a fastboot.exe error
Hi,
i just got an HTC One M8s and i think its propably bricked. I don't know whats owner of that phone done here. Its Software status : Modified, Bootloader: Locked, and S-ON.
I can't turn on the phone, i just can go to bootloader option and cant access recovery bc its popably didn't exist anymore.
I was trying to flash RUU for my CID T-MOB009 but htc_fastboot says "data length is too large" and sometimes "remote:signature verify fail", and i was trying to unlock this bootloader with HTCDev, but when i clicked yes it looks like that(means 1st photo) and just reboot to fastboot in bootloader and it's still locked
Is there's a way to unbrick this phone ? I just spend like 4 hours of trying some tips but it doesn't work for it.
Some screens (remove spaces cause i can't post link before 10posts):
s14.postimg .org/b35qjqt6p/DSC_0001_1.jpg
s22.postimg .org/iiihlx2tt/DSC_0002_1.jpg
image.prntscr .com/image/85f19f6602fe4776b993affe62e959c1.png
Please understand my bad english, it's not my primary language
Mikkal said:
Hi,
i just got an HTC One M8s and i think its propably bricked. I don't know whats owner of that phone done here. Its Software status : Modified, Bootloader: Locked, and S-ON.
I can't turn on the phone, i just can go to bootloader option and cant access recovery bc its popably didn't exist anymore.
I was trying to flash RUU for my CID T-MOB009 but htc_fastboot says "data length is too large" and sometimes "remote:signature verify fail", and i was trying to unlock this bootloader with HTCDev, but when i clicked yes it looks like that(means 1st photo) and just reboot to fastboot in bootloader and it's still locked
Is there's a way to unbrick this phone ? I just spend like 4 hours of trying some tips but it doesn't work for it.
Some screens (remove spaces cause i can't post link before 10posts):
s14.postimg .org/b35qjqt6p/DSC_0001_1.jpg
s22.postimg .org/iiihlx2tt/DSC_0002_1.jpg
image.prntscr .com/image/85f19f6602fe4776b993affe62e959c1.png
Please understand my bad english, it's not my primary language
Click to expand...
Click to collapse
Yeah maybe there's a problem with the "Security warning" it shouldn't be there. What you can do is to reflash the RUU. But not with fastboot but from your sdcard.
Probably this is the firmware that you should use. I'm not sure though you can go one directory back and search for another one if that doesn't suit to you.
Now to flash it follow the steps
1) Download it and if you can check the md5sum so as to ensure it has downloaded correctly.
2) Rename it to 0PKVIMG.zip (note the first character is a zero and not a O
3) Take out the sdcard of your phone.
4) Insert it on your pc and format it to Fat32 or exfat.
5) Copy the above file into your sdcard.
6) Power off your phone and insert the sdcard
7) Go into the bootloader mode. It should automatically detect the firmware
8) When it asks you if you want to install choose "Yes"
9) Wait until it is done. It will flash multiple times the system partion. WAIT patiently
10) Hope that fixed it!
PS: When you enter fastboot you probably see some green letters. This means the hboot is searching for the software file i said above. If it finds it's ok. I had problems copying the file with windows though.
root-expert said:
Yeah maybe there's a problem with the "Security warning" it shouldn't be there. What you can do is to reflash the RUU. But not with fastboot but from your sdcard.
Probably is the firmware that you should use. I'm not sure though you can go one directory back and search for another one if that doesn't suit to you.
Now to flash it follow the steps
1) Download it and if you can check the md5sum so as to ensure it has downloaded correctly.
2) Rename it to 0PKVIMG.zip (note the first character is a zero and not a O
3) Take out the sdcard of your phone.
4) Insert it on your pc and format it to Fat32 or exfat.
5) Copy the above file into your sdcard.
6) Power off your phone and insert the sdcard
7) Go into the bootloader mode. It should automatically detect the firmware
8) When it asks you if you want to install choose "Yes"
9) Wait until it is done. It will flash multiple times the system partion. WAIT patiently
10) Hope that fixed it!
PS: When you enter fastboot you probably see some green letters. This means the hboot is searching for the software file i said above. If it finds it's ok. I had problems copying the file with windows though.
Click to expand...
Click to collapse
Yeah thanks for that great advice man! Unfortunately i was trying to copy this on Windows and when i try to Hboot that it just skip process (but stops for sec on a 0PKVIMG.zip) and going back to bootloader. Any advice how to do that properly on windows ? I checked md5 on sd card and its the same as on my computer disk and same as on this site what youre sent to me . Thanks for replies
Mikkal said:
Yeah thanks for that great advice man! Unfortunately i was trying to copy this on Windows and when i try to Hboot that it just skip process (but stops for sec on a 0PKVIMG.zip) and going back to bootloader. Any advice how to do that properly on windows ? I checked md5 on sd card and its the same as on my computer disk and same as on this site what youre sent to me . Thanks for replies
Click to expand...
Click to collapse
I couldn't get it that done on windows. Dunno what's going wrong. Hopefully i had a linux distro installed and i copied the file from there. Maybe you can do that.
If you haven't installed any linux then create a live cd and boot it up.
root-expert said:
I couldn't get it that done on windows. Dunno what's going wrong. Hopefully i had a linux distro installed and i copied the file from there. Maybe you can do that.
If you haven't installed any linux then create a live cd and boot it up.
Click to expand...
Click to collapse
Okay so now its the trick. I have done copied that properly, bc it start to loading when i put sd card. I click yes for update, and its start to flashing. Some of first steps failed so it wasn't look good. It called ROM failed to flashed click POWER to restart, and when i clicked it phone goes off and now its propably close to hardbricked cause i cant turn on bootloader. When i take it to charger there is no battery on screen informating its already charging. Only LED is working when charging and sound on windows when plug it on and off. Any suggestions guys? I'am scared now
Similar situation
Hi,
I appear to be in a similar situation with my M8 that I tried to convert to GPE. Something went wrong and although the ROM booted, I kept getting told my data was corrupt or encrypted... Tried a few reboots, and refreshed but still got the same...
A thread on here suggested formatting one of the partitions from TWRP which just returned an error, since then the phone appears to be 'hard bricked'.
No display, no charging indication, not recognised in ADB, and I can't force boot into recovery or fast boot.
However, I do still get the notification sound when I plug it into my PC...
It appears in the Device Manager as Qualcomm Mass Storage Device, and Windows shows ~20 drives most of which are unformatted, a few of which seem to contain system info...
I was wondering, would it be possible to re-image the Device? Given that the PC recognises the partitions, would anyway know what -should- be on them?
Alternatively, can anyone provide an image of a stock drive, partitions etc which I could apply?
Apologies if this is nonsense, but I'd imagine the reason it can't boot is the Bootloader partition is 'missing' or corrupted.
The same may be true for your device Mikkal.
Thanks in advance,
Mikkal said:
Okay so now its the trick. I have done copied that properly, bc it start to loading when i put sd card. I click yes for update, and its start to flashing. Some of first steps failed so it wasn't look good. It called ROM failed to flashed click POWER to restart, and when i clicked it phone goes off and now its propably close to hardbricked cause i cant turn on bootloader. When i take it to charger there is no battery on screen informating its already charging. Only LED is working when charging and sound on windows when plug it on and off. Any suggestions guys? I'am scared now
Click to expand...
Click to collapse
Exactly the same problem here, I followed the same steps as you, and had same errors as you.. Is there any help for this?
funjai said:
Exactly the same problem here, I followed the same steps as you, and had same errors as you.. Is there any help for this?
Click to expand...
Click to collapse
What is your CID , software version
No idea mate.. I can't turn on the phone so I can't check that..
For those who can't flash a RUU, unlock the bootloader install TWRP recovery, and install a custom ROM. Voila!
LoneWolfO2Se said:
For those who can't flash a RUU, unlock the bootloader install TWRP recovery, and install a custom ROM. Voila!
Click to expand...
Click to collapse
Oh really? You never noticed that there are no custom roms for M8S ?
funjai said:
Oh really? You never noticed that there are no custom roms for M8S ?
Click to expand...
Click to collapse
You sure about that ?
Hi can you paste info from your phone use this command in fasboot
fastboot getvar all
also tell me what software did you try to flash
Regards
(My Download Mode screen while stuck in boot-loop)
*** UNLOCKED ***
htc_pmewh1 PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.42.651.6
Jan 18 2017, 11:10:08(857212)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security checking failed GT_CONNECT_FAIL
Security Warning
Bla bla bla
SD MOUNTED
OTG NOT MOUNTED
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
So, I had Viper10 5.9 with TWRP, Magisk, and SuperSu but somehow messed with one of my color settings and just couldn't figure out how to fix it, this went on for weeks... so I decided to restore it and reflash the ROM. Somewhere in that process S-OFF went to S-ON, I believe, not sure if it makes a difference but from all the searching I've done trying to figure this out it seems like a big deal. Anyway, I can tell you this...
1) When I tried to format data through TWRP before it said something like "failed to mount bla bla bla device is busy or in use" (maybe something to do with encryption? or root? maybe not having root anymore since I had uninstalled SuperSu?
2) Now when I try to format data through TWRP it acts as if everything is fine and then I reboot and I'm stuck in a never-ending boot loop again
3) When I try to flash my firmware zip (which I got from here) in Download Mode I get
"22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
4) When I try to ADB sideload through TWRP it says the zip file is corrupt
5) When I try the HTC RUU (while in Download Mode) it never gets past the first screen where InstallShield or whatever is setting up
6) I just flashed Viper10 5.9 through TWRP and it worked all of a sudden (wasn't working before, while stuck in the loop)... I went with Magisk and MagiskSu this time to avoid a future conflict (not that I now what I'm doing or anything)
So I'm wondering if I'm okay... I'm still S-ON (I thought it went S-OFF when rooted?) and everything seems to be working fine... My Download Mode screen is exactly the same, including the "Security checking failed GT_CONNECT_FAIL"
Although I have this tiny itch to format my data through TWRP at some point and do a "fresh" install/ROM flash to be sure there isn't a hidden issue. Am I good? Seems like it's not quite perfect yet.
Thanks for your help.
WutUpCuuuz said:
(My Download Mode screen while stuck in boot-loop)
*** UNLOCKED ***
htc_pmewh1 PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.42.651.6
Jan 18 2017, 11:10:08(857212)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security checking failed GT_CONNECT_FAIL
Security Warning
Bla bla bla
SD MOUNTED
OTG NOT MOUNTED
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
So, I had Viper10 5.9 with TWRP, Magisk, and SuperSu but somehow messed with one of my color settings and just couldn't figure out how to fix it, this went on for weeks... so I decided to restore it and reflash the ROM. Somewhere in that process S-OFF went to S-ON, I believe, not sure if it makes a difference but from all the searching I've done trying to figure this out it seems like a big deal. Anyway, I can tell you this...
1) When I tried to format data through TWRP before it said something like "failed to mount bla bla bla device is busy or in use" (maybe something to do with encryption? or root? maybe not having root anymore since I had uninstalled SuperSu?
2) Now when I try to format data through TWRP it acts as if everything is fine and then I reboot and I'm stuck in a never-ending boot loop again
3) When I try to flash my firmware zip (which I got from here) in Download Mode I get
"22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
4) When I try to ADB sideload through TWRP it says the zip file is corrupt
5) When I try the HTC RUU (while in Download Mode) it never gets past the first screen where InstallShield or whatever is setting up
6) I just flashed Viper10 5.9 through TWRP and it worked all of a sudden (wasn't working before, while stuck in the loop)... I went with Magisk and MagiskSu this time to avoid a future conflict (not that I now what I'm doing or anything)
So I'm wondering if I'm okay... I'm still S-ON (I thought it went S-OFF when rooted?) and everything seems to be working fine... My Download Mode screen is exactly the same, including the "Security checking failed GT_CONNECT_FAIL"
Although I have this tiny itch to format my data through TWRP at some point and do a "fresh" install/ROM flash to be sure there isn't a hidden issue. Am I good? Seems like it's not quite perfect yet.
Thanks for your help.
Click to expand...
Click to collapse
Update: Since re-flashing Viper I haven't had any issues, although I haven't tried anything in depth. I still wonder about it not wanting to format data in TWRP before (remembering that it said it couldn't do something with /data).
Is there a way I can still format my device and get it back to stock, S-OFF and locked so I can start from scratch? The /data thing and the GT_CONNECT_FAIL are bothering me. Or, if there's a better route I should go I'm definitely open to suggestions.
Sent from my 2PS64 using Tapatalk
WutUpCuuuz said:
Update: Since re-flashing Viper I haven't had any issues, although I haven't tried anything in depth. I still wonder about it not wanting to format data in TWRP before (remembering that it said it couldn't do something with /data).
Is there a way I can still format my device and get it back to stock, S-OFF and locked so I can start from scratch? The /data thing and the GT_CONNECT_FAIL are bothering me. Or, if there's a better route I should go I'm definitely open to suggestions.
Click to expand...
Click to collapse
Put an ruu on an SD card and run that. Will take you back to complete stock and remove everything from the phone.
Also, regarding s-off, it's not clear if you ever had s-off to begin with. You had previously paid for it via sunshine??
Tarima said:
Put an ruu on an SD card and run that. Will take you back to complete stock and remove everything from the phone.
Also, regarding s-off, it's not clear if you ever had s-off to begin with. You had previously paid for it via sunshine??
Click to expand...
Click to collapse
I'm not exactly sure either... maybe I'm just imagining it. Looked into Sunshine but have yet to pump the trigger on it.
At one point I had found an RUU zip, put it on the SD, and renamed it to 2PS6IMG.zip, but it wouldn't run. I'll try again. Think I could use one of HTC's RUU executables? (that might be a dumb question [emoji6])
Thanks for your help
Sent from my 2PS64 using Tapatalk
WutUpCuuuz said:
I'm not exactly sure either... maybe I'm just imagining it. Looked into Sunshine but have yet to pump the trigger on it.
At one point I had found an RUU zip, put it on the SD, and renamed it to 2PS6IMG.zip, but it wouldn't run. I'll try again. Think I could use one of HTC's RUU executables? (that might be a dumb question [emoji6])
Thanks for your help
Click to expand...
Click to collapse
If you're not sure you ever had s-off, then you didn't have it. S-off is a separate procedure, not be confused with bootloader unlocking or rooting.
If the ruu didn't run, most likely you tried one made for another mid/cid, or the software version was older than what you had already on your phone. Make sure both of these are corrected and report back if it works. And yes the ruu.exe would work, but the two points I just mentioned need to be taken into account.
Double checked that it was the correct RUU... still correct as far as I can tell. Rebooted to download mode, didn't see it on the SD. Renamed the RUU to 2PS6IMG.exe, still didn't see it. ??? I'm stuck, my PC isn't here with me so I can't try it that way.