EDIT: For all of you that are wondering what the "fused" flag in download mode means, it's something related to the file system. Just read that
https://www.xda-developers.com/divi...les-fuse-replacement-will-reduce-io-overhead/
Hi XDA community.
Just feel free to post any problems you have and we will try to resolve them.
Two methods for S-ON or S-OFF device, please do it under Nougat 7.0 firmware installed. This refers we have to downgrade to nougat first and the running those commands.
S-ON only
1. Reboot to TWRP recovery
2. Use the command below to erase persist partition
Code:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist
S-OFF only
1. Reboot to bootloader (not download)
2. Use the command below to erase persist partition
Code:
fastboot erase persist
Is that possible to downgrade without S-OFF??
Please watch the video, HTC 10 can downgrade in the same method!!!
PS. This video is for HTC One M9, please use Nougat RUU/firmware for HTC 10 to do downgrading.
Credits for @sappro
------------------ GO FROM US UNLOCKED TO EUROPEAN OREO-----------------
This is for all people who are in US Oreo and are having stability issues. Be noticed you need S-OFF on your phone.
Change your CID and MID to a WWE ones: HTC__034 (you can choose other WWE one) and 2PS620000.
Download Oreo RUU and flash it: https://androidfilehost.com/?fid=746010030569969175
No need to wipe the persist partition, as we aren't downloading.
(OUTDATED) GO FROM US UNLOCKED TO EUROPEAN OREO
EDIT: This method is now outdated, as now we have stable Oreo RUU for US unlocked, but if you want to convert to WWE from RUU, you can follow this steps.
This is for all people who are in US Oreo and are having stability issues. Be noticed you need S-OFF on your phone.
Change your CID and MID to a WWE ones: HTC__034 (you can choose other WWE one) and 2PS620000.
Flash nougat firmware zip (htc_fastboot): https://androidfilehost.com/?fid=961840155545593694
Flash nougat RUU (htc_fastboot): https://androidfilehost.com/?fid=817550096634797504
Flash oreo OTA within stock recovery:
https://androidfilehost.com/?fid=890129502657577071
DONE.
One other note is that all of us that have flashed Oreo firmware have a "fused" status flag in bootloader and download mode. So far as I know, no one knows what this means.
PR4X15 said:
One other note is that all of us that have flashed Oreo firmware have a "fused" status flag in bootloader and download mode. So far as I know, no one knows what this means.
Click to expand...
Click to collapse
I have added your note into the OP:good:
I'm uploading a "different" 2.41.401.41 RUU for you to try.
Will post a link when it's complete.
Fused
PR4X15 said:
One other note is that all of us that have flashed Oreo firmware have a "fused" status flag in bootloader and download mode. So far as I know, no one knows what this means.
Click to expand...
Click to collapse
When you downgrade that flag disappears. So I will downgrade and flash the official RUU once released... Hopefully that will correct everything.
Also, thanks to everyone for trying to work through this problem, I know I have spent hours downgrading, then flashing radio images, downgrading further ( zips ), if I ever get it working I will let you know... Gonna try again after work...
Typically fused status is just a way for a manufacturer to know if you've modified the firmware on a device. Kind of like the old "Tampered" hboot status. I'm guessing it's the same kind of idea, a way for HTC to know that the system or firmware has been modified different than it shipped in the event they need it for diagnostics or evaluating a warranty claim. i need someone more knowledgable to confirm, but I'm throwing this out for conversation.
santod040 said:
I'm uploading a "different" 2.41.401.41 RUU for you to try.
Will post a link when it's complete.
Click to expand...
Click to collapse
What do you mean with "different"?? Sorry the stupid answer but I have spend so many hours on this
slysurfer said:
When you downgrade that flag disappears. So I will downgrade and flash the official RUU once released... Hopefully that will correct everything.
Also, thanks to everyone for trying to work through this problem, I know I have spent hours downgrading, then flashing radio images, downgrading further ( zips ), if I ever get it working I will let you know... Gonna try again after work...
Click to expand...
Click to collapse
I hope so, that official update fixes that. And also thanks to all people who are trying to find out that from my side too.:fingers-crossed:
fdgd1998 said:
What do you mean with "different"?? Sorry the stupid answer but I have spend so many hours on this
Click to expand...
Click to collapse
This is a combined/signed RUU zip.
They typically include whatever bootloader was needed to prepare the device for the one in the main RUU.
Sometimes these are contained in a smaller pre-update or small update shortly before the one with major changes, as well as any other files needed to process the RUU.
Similar to what this RUU was missing, a pre-update hboot to allow the RUU to flash properly.
They made a similar goof on the Sprint (I forget if m7, m8, or m9) but it was pulled for the same/similar reason.
Anyhow, feel free to try it, or not.
The choice is of course yours.
Although I'd be at least a little curious if it worked for you or not, or anyone else in the same boat.
(Yes it is a FULL WIPE RUU)
2PS6IMG_PERFUME[email protected]61226_79.07_F_release_509716_combined_signed_2_4.zip
---
santod040 said:
This is a combined/signed RUU zip.
They typically include whatever bootloader was needed to prepare the device for the one in the main RUU.
Sometimes these are contained in a smaller pre-update or small update shortly before the one with major changes, as well as any other files needed to process the RUU.
Similar to what this RUU was missing, a pre-update hboot to allow the RUU to flash properly.
They made a similar goof on the Sprint (I forget if m7, m8, or m9) but it was pulled for the same/similar reason.
Anyhow, feel free to try it, or not.
The choice is of course yours.
Although I'd be at least a little curious if it worked for you or not, or anyone else in the same boat.
(Yes it is a FULL WIPE RUU)
2PS6IMG_PERFUME[email protected]61226_79.07_F_release_509716_combined_signed_2_4.zip
---
Click to expand...
Click to collapse
I'm gonna try this as soon as I get home! Thanks for your time!
santod040 said:
This is a combined/signed RUU zip.
They typically include whatever bootloader was needed to prepare the device for the one in the main RUU.
Sometimes these are contained in a smaller pre-update or small update shortly before the one with major changes, as well as any other files needed to process the RUU.
Similar to what this RUU was missing, a pre-update hboot to allow the RUU to flash properly.
They made a similar goof on the Sprint (I forget if m7, m8, or m9) but it was pulled for the same/similar reason.
Anyhow, feel free to try it, or not.
The choice is of course yours.
Although I'd be at least a little curious if it worked for you or not, or anyone else in the same boat.
(Yes it is a FULL WIPE RUU)
2PS6IMG_PERFUME[email protected]61226_79.07_F_release_509716_combined_signed_2_4.zip
---
Click to expand...
Click to collapse
Well, I just flashed the RUU. Unfortunately I'm still without any cell connectivity I'm totally thrown for a loop on this thing. I've got no idea what's keeping it from working.
If someone can get ahold of an RUU for the official Oreo rollout in Taiwan, I wonder if using that RUU and then using an old RUU will fix the issue. @fdgd1998 @PR4X15
jackebuehner said:
If someone can get ahold of an RUU for the official Oreo rollout in Taiwan, I wonder if using that RUU and then using an old RUU will fix the issue. @[email protected]
Click to expand...
Click to collapse
It't very difficult it could work. Because I have actually tried the same with the US unlocked and doesn't work.
I am at the miment on Taiwanese Oreo, and my phone is working phone. We know the problem is with the radio, but we aren't able to find out what is....
Anyway, if I find the Oreo RUU I'll post it.
If I had to make a guess at this point, I'd say something to do with new lockbooter.img in firmware. (not boot"loader" but lockbooter).
Assuming it remains even after using an older RUU, as there was no lockbooter.img in previous versions.
I realize this isn't very helpful, only for informational purposes.
Here are some strings of bytes taken from the image:
\00Illegal byte sequence\00Domain error\00Result not representable\00Not a tty\00Permission denied\00Operation not permitted\00No such file or directory\00No such process\00File exists\00Value too large for data type\00No space left on device\00Out of memory\00Resource busy\00Interrupted system call\00Resource temporarily unavailable\00Invalid seek\00Cross-device link\00Read-only file system\00Directory not empty\00Connection reset by peer\00Operation timed out\00Connection refused\00Host is down\00Host is unreachable\00Address in use\00Broken pipe\00I/O error\00No such device or address\00Block device required\00No such device\00Not a directory\00Is a directory\00Text file busy\00Exec format error\00Invalid argument\00Argument list too long\00Symbolic link loop\00Filename too long\00Too many open files in system\00No file descriptors available\00Bad file descriptor\00No child process\00Bad address\00File too large\00Too many links\00No locks available\00Resource deadlock would occur\00State not recoverable\00Previous owner died\00Operation canceled\00Function not implemented\00No message of desired type\00Identifier removed\00Device not a stream\00No data available\00Device timeout\00Out of streams resources\00Link has been severed\00Protocol error\00Bad message\00File descriptor in bad state\00Not a socket\00Destination address required\00Message too large\00Protocol wrong type for socket\00Protocol not available\00Protocol not supported\00Socket type not supported\00Not supported\00Protocol family not supported\00Address family not supported by protocol\00Address not available\00Network is down\00Network unreachable\00Connection reset by network\00Connection aborted\00No buffer space available\00Socket is connected\00Socket not connected\00Cannot send after socket shutdown\00Operation already in progress\00Operation in progress\00Stale file handle\00Remote I/O error\00Quota exceeded\00No medium found\00Wrong medium type\00No error information\00\00"entering %s"\00lockbooter_read_rpmb\00"ERR: qsee_stor_device_init: [%d]"\00"qsee_stor_device_init: ok"\00"ERR: qsee_stor_open_partition: [%d]"\00"qsee_stor_open_partition: ok"\00"ERR: qsee_stor_read_sectors: [%d]"\00"qsee_stor_read_sectors: ok"\00"exiting %s, ret = [%d]"\00"RPMB didn't provisioned. No fuse?"\00lockbooter_write_rpmb\00"ERR: qsee_stor_device_get_info: [%d]"\00"deviceInfo: bytes_per_sector: [%u], total_sectors: [%u], available_sectors: [%u]"\00"ERR: qsee_stor_add_partition: [%d]"\00"qsee_stor_add_partition: ok"\00"ERR: qsee_stor_open_partition again: [%d]"\00"ERR: qsee_stor_client_get_info: [%d]"\00"clientInfo: bytes_per_sector: [%u], total_sectors: [%u]"\00"ERR: qsee_stor_write_sectors: [%d]"\00"qsee_stor_write_sectors: ok"\00"LOCKBOOTER init. Version: %x.%x"\00"ERROR: Response buffer len insufficient, ERROR OUT"\00"ERROR: Command pointer equals NULL!"\00"ERROR: Command buffer len insufficient for reading cmd_id, ERROR OUT"\00"TZ App cmd handler, cmd_id = %d"\00"Cmd/rsp buffer lens insufficient - %x, %x, ERROR OUT"\00"CMD: app version"\00"CMD: random generation"\00"CMD: smart card verification"\00"CMD: ks random generation"\00"CMD: ks verification"\00"CMD: set ks verification key"\00"CMD: get ks verification: [%u]"\00"CMD: clear ks verification"\00"CMD: decrease ks verification"\00"FIXME: CMD_SET_UNLOCK_FLAG"\00"Unsupported command: %d"\00"LockBooter App shutdown"\00sc_random_generation\00"ERR: size"\00"%s: return value is not long enough"\00"%s: it's good to go"\00"exiting %s"\00"ERR: size is not right (%d)"\00sc_card_verification\00"sl = %d"\00"ERR: random number is wrong"\00"random number is correct"\00"ERR: qsee_malloc (key)"\00"ERR: qsee_hash (%d)"\00"ERR: qsee_rsa_verify_signature (%d, %x)"\00"qsee_rsa_verify_signature is good"\00sc_main\00"len is %d"\00"ERR: qsee_register_shared_buffer"\00"ERR: qsee_prepare_shared_buf_for_secure_read"\00"ERR: qsee_prepare_shared_buf_for_nosecure_read"\00"ERR: qsee_deregister_shared_buffer"\00ks_random_generation\00"ERR: size is not right [%d]"\00"return value is not long enough: [%d]"\00"ERR: qsee_hash [%d]"\00"key malloc failed"\00"public enc failed: [%d] [%d]"\00"ks_request_type: [%u], ks_reboot_count: [%u] [%#x] [%zu]"\00"init public key failed"\00ks_verification\00"ERR: Exceeded retry count [%d]"\00"qsee_rsa_verify_signature is good, nResult: [%d], request_type: [%d], ks_reboot_count: [%u]"\00"ERR: RSA_verify_ext [%d, %#x]"\00set_verification_key\00"ERR: size is not right [%d] [%zu]"\00ks_main\00pgfs_data_update\00"ERR: Bad Parameters"\00"ERR: qsee_cipher_init"\00"ERR: qsee_cipher_set_parm (key)"\00"ERR: qsee_cipher_set_parm (mode)"\00"ERR: qsee_cipher_set_parm (IV)"\00"ERR: qsee_set_bandwidth"\00"ERR: qsee_cipher_decrypt"\00"It's WRONG pgfs data!!!"\00"sec_info.security_level = 0x%x"\00"sec_info.unlock = 0x%x"\00"sec_info.keycard_s_off_times = 0x%x"\00"sec_info.keycard_s_on_timestamp = 0x%x"\00"sec_info.keycard_s_off_timestamp = 0x%x"\00"sec_info.version_check = 0x%x"\00"ERR: qsee_cipher_encrypt"\00"everything looks good!"\00\C8\E0\E4X<;\F0\CC睤\DAA\00[stub]\00" In qsee_shared_buffer.c: ISharedBuffer_registerSharedBuffer returned =%d"\00" In qsee_shared_buffer.c: qsee_register_shared_buffer: Object is NULL!!!"\00" In qsee_shared_buffer.c: qsee_deregister_shared_buffer: Object is NULL !!!"\00-+ 0X0x\00(null)\00-0X+0X 0X-0x+0x 0x\00inf\00INF\00nan\00NAN\00.\000123456789ABCDEFT!"
K'hnopqb ($
%#\83\82}&*+<=>?CGJMXYZ[\]^_`acdefgijklrstyz{|\00lockbooter\00m=x;n=lockbooter;p=b:9b8208ff2d701\00p+s}-#Pxh7Z!<+`
Click to expand...
Click to collapse
santod040 said:
If I had to make a guess at this point, I'd say something to do with new bootlocker.img in firmware. (not boot"loader" but boot"locker").
Assuming it remains even after using an older RUU, as there was no bootlocker.img in previous versions.
I realize this isn't very helpful, only for informational purposes.
Here are some strings of bytes taken from the image:
Click to expand...
Click to collapse
That' a very interesting info.
Edit: I think that this might be the cause of the messages I got on fastboot saying "mismatched partition size" and also the one which are keeping as from downgrading.
Just a new partition in Oreo.
Anyone else having battery issues?
fdgd1998 said:
That' a very interesting info.
Edit: I think that this might be the cause of the messages I got on fastboot saying "mismatched partition size" and also the one which are keeping as from downgrading.
Just a new partition in Oreo.
Click to expand...
Click to collapse
So they are messing with the partition table anyway, so they may just as well had given us Treble. Oh well...
errikosd said:
So they are messing with the partition table anyway, so they may just as well had given us Treble. Oh well...
Click to expand...
Click to collapse
Messing with partition table is a posibility. And Google said thar Treble will only support to devices that comes with Oreo preinstalled.
Maybe because of this? Differs from this?
Sent from my HTC 10 using Tapatalk
cyrusct82 said:
Maybe because of this? Differs from this?
Click to expand...
Click to collapse
I don't understand your post. Is a bit confusing. What should be able to see in that screnshots?
Related
Hello everyone, I I just got an M9 at my local Telus store and I would like to be able to do everything with it like I am able to do with my M7, so I know I will need to use sunshine to get S-OFF and I would also like to be able to change everything from the rom to the kernel to the OS, everything, so I was just wondering if someone could let me know the best order to go about doing things, meaning should I do sunshine first then worry about flashing a recovery and all that, or should I do the recovery first so that I can backup the phones current state? The phone currently says this in the hboot screen:
*** LOCKED ***
LK-1.0.0.0000
OS-1.32.661.6
and this is what it says on the phones Setting-About-Software screen:
Android version
5.0.2
HTC Sense version
7.0
Like I mentioned before, it would probably be best if I can make a backup of the phones current state just in case there are any issues, so to do that I know I need a recovery, but do I need to do the HTC Dev unlocker before I can do so? or do I have to flash a recovery first before everything else?
Now, before anyone gets upset with me for asking these questions because they have most likely been asked 1000 times before, I am not asking to be spoon feed all the details step by step, I am just asking to be pointed in the right direction and asking for you guy's opinions on the best way to go about doing things so that I do them right the first time... So if anyone could please take a minute to help me out and get me pointed in the right direction then it would be greatly appreciated... thank you very much...
apaquette420 said:
So if anyone could please take a minute to help me out and get me pointed in the right direction then it would be greatly appreciated... thank you very much...
Click to expand...
Click to collapse
First thing you should do is unlock your bootloader. After that you can install twrp and flash supersu (most can be found here) Once you are rooted run sunshine. After that the sky is the limit. You will be free to flash anything and everything. I know because I've done it. If you want to convert to a developers edition there is a post here. Personally I do not use my stock recovery or system image backups to download ota's. I prefer to run an RUU and do fresh installs. Reason why is because I am constantly changing firmware and roms. A lot of roms are based on the WWE firmware.
let me know if you have any more questions
bigp951 said:
First thing you should do is unlock your bootloader. After that you can install twrp and flash supersu (most can be found here) Once you are rooted run sunshine. After that the sky is the limit. You will be free to flash anything and everything. I know because I've done it. If you want to convert to a developers edition there is a post here. Personally I do not use my stock recovery or system image backups to download ota's. I prefer to run an RUU and do fresh installs. Reason why is because I am constantly changing firmware and roms. A lot of roms are based on the WWE firmware.
let me know if you have any more questions
Click to expand...
Click to collapse
Thank you very much for the tips.. Do I use the HTC Dev website to unlock the bootloader? I seen a link in the dev thread that said Unlock bootloader without HTCDev(root required), but I bet that the HTCDev way is probably the best best. which did you use? I'm not at home right now so I will begin when I get home later on tonight and if I need anything else I will post back, plus I post back to say how everything goes.. Thanks again for help, it is very much appreciated...
apaquette420 said:
Thank you very much for the tips.. Do I use the HTC Dev website to unlock the bootloader? I seen a link in the dev thread that said Unlock bootloader without HTCDev(root required), but I bet that the HTCDev way is probably the best best. which did you use? I'm not at home right now so I will begin when I get home later on tonight and if I need anything else I will post back, plus I post back to say how everything goes.. Thanks again for help, it is very much appreciated...
Click to expand...
Click to collapse
I've used htcdev for all 2 out o 3 of my m9's. third one is a developer edition so it wasn't needed.
just note download mode is fastboot mode on the m9. htcdev says to boot to fastboot mode and if you do not know than you can waste hours trying to figure it out.
bigp951 said:
I've used htcdev for all 2 out o 3 of my m9's. third one is a developer edition so it wasn't needed.
just note download mode is fastboot mode on the m9. htcdev says to boot to fastboot mode and if you do not know than you can waste hours trying to figure it out.
Click to expand...
Click to collapse
lol I so would have gotten caught up on that lol thanks again man!!! will post back later on...
cool..let me know if you get stuck anywhere
Ok so I got the bootloader unlocked and TWRP installed, right now I am taking a backup of the phones current state just in case. Now I just need to flash the SuperSU beta from the link you provided and then run sunshine, after that I would like to flash the latest OS for my phone, but I am not sure which version to use, I think this one is correct http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678 but I am not 100% sure, do you know if this is the correct latest version for my phone?
Also should I supercid my phone before updating the firmware by entering "fastboot oem writecid 11111111" while in download mode? because my cid is TELUS001 and I do not see that cid listed in the androidinfo.txt file that is in the firmware zip...
Thanks again for all your help...
**UPDATE** I now have S-OFF, I can't believe how smooth the whole process is now with sunshine compared to almost all of my other HTC phones, hats off to those guys for sure... Thank you very much for getting me this far!!! I appreciate it very much...
apaquette420 said:
Ok so I got the bootloader unlocked and TWRP installed, right now I am taking a backup of the phones current state just in case. Now I just need to flash the SuperSU beta from the link you provided and then run sunshine, after that I would like to flash the latest OS for my phone, but I am not sure which version to use, I think this one is correct http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678 but I am not 100% sure, do you know if this is the correct latest version for my phone?
Also should I supercid my phone before updating the firmware by entering "fastboot oem writecid 11111111" while in download mode? because my cid is TELUS001 and I do not see that cid listed in the androidinfo.txt file that is in the firmware zip...
Thanks again for all your help...
**UPDATE** I now have S-OFF, I can't believe how smooth the whole process is now with sunshine compared to almost all of my other HTC phones, hats off to those guys for sure... Thank you very much for getting me this far!!! I appreciate it very much...
Click to expand...
Click to collapse
I was actually just going to tell you to type
Code:
fastboot getvar all
while in download mode and to copy and paste that into a file a text file somewhere so you always have it. then you can supercid. I actually have never seen any firmware for your carrier. what is your mid? this is where I get all of my firmware from. I learned how to remove the red text using hex editor and I also throw in a custom splash screen before I flash.
Here is a link for your stock firmware. not sure what the most up to date is but most custom roms are using the WWE firmware anyways.
p.s. either quote me or tag me if you need a faster response. I'm not getting notifications otherwise.
bigp951 said:
I was actually just going to tell you to type
Code:
fastboot getvar all
while in download mode and to copy and paste that into a file a text file somewhere so you always have it. then you can supercid. I actually have never seen any firmware for your carrier. what is your mid? this is where I get all of my firmware from. I learned how to remove the red text using hex editor and I also throw in a custom splash screen before I flash.
Click to expand...
Click to collapse
My mid is 0PJA11000 but the one that is listed in the androidinfo.txt file of the firmware that I linked earlier is 0PJA10000, does this mean I cant use it? in all I plan to flash ViperOneM9 3.5.0 for the rom and it says it requires 2.10 but my phone is currently at 1.32
apaquette420 said:
My mid is 0PJA11000 but the one that is listed in the androidinfo.txt file of the firmware that I linked earlier is 0PJA10000, does this mean I cant use it?
Click to expand...
Click to collapse
I honestly don't know if the hardware is any different but it looks like your mid is the same as the dev ed. check this one out. @clsA is very knowledgeable on the m9. I learned a lot of what I know from his posts.
Personally I have gotten so relaxed that I just change my mid and cid to whatever it is I want to flash and just go for it. But I also understand that I'm risking a brick by doing so..lol
bigp951 said:
I honestly don't know if the hardware is any different but it looks like your mid is the same as the dev ed. check this one out. @clsA is very knowledgeable on the m9. I learned a lot of what I know from his posts.
Personally I have gotten so relaxed that I just change my mid and cid to whatever it is I want to flash and just go for it. But I also understand that I'm risking a brick by doing so..lol
Click to expand...
Click to collapse
took a look at the thread and it looks like all I need to do to flash 2.10 which is the international version is type fastboot oem writemid 0PJA10000 while in downloader mode because like you said and which I also confirmed in the other thread that my phone is the same as the dev ed and I should be able to switch back and forth with the same command
apaquette420 said:
took a look at the thread and it looks like all I need to do to flash 2.10 which is the international version is type fastboot oem writemid 0PJA10000 while in downloader mode because like you said and which I also confirmed in the other thread that my phone is the same as the dev ed and I should be able to switch back and forth with the same command
Click to expand...
Click to collapse
If going to dev ed I have had better luck running an RUU and accepting ota's as far as the radio goes. my reception went from 2 bars to full bars doing it that way verses just flashing the newest firmware. But it is a very long and tedious process and since you just got your m9 I'm sure you want to use it already..
What rom are you thinking about flashing?
bigp951 said:
If going to dev ed I have had better luck running an RUU and accepting ota's as far as the radio goes. my reception went from 2 bars to full bars doing it that way verses just flashing the newest firmware. But it is a very long and tedious process and since you just got your m9 I'm sure you want to use it already..
What rom are you thinking about flashing?
Click to expand...
Click to collapse
I am hoping to flash ViperOneM9 3.5.0, it was the only rom I ran on my M7 and I loved it, so I'm really hoping to have it on this phone too... I just asked in the roms thread to see if anyone else there is on my same network to see how they got it working... and to be honest I don't mind waiting in order to get things done the right way the first time, know what I mean...
apaquette420 said:
I am hoping to flash ViperOneM9 3.5.0, it was the only rom I ran on my M7 and I loved it, so I'm really hoping to have it on this phone too... I just asked in the roms thread to see if anyone else there is on my same network to see how they got it working... and to be honest I don't mind waiting in order to get things done the right way the first time, know what I mean...
Click to expand...
Click to collapse
Viper is one of my favorites. Was using it for months. They are good about replying too... A little too good because you get spoiled. Then when you post on other roms and nobody ever replies you realize how good those guys are..haha
check out the second line on this thread to reclaim 3 gb of data after using sunshine. I've been s-off for months and just saw this today.
bigp951 said:
Viper is one of my favorites. Was using it for months. They are good about replying too... A little too good because you get spoiled. Then when you post on other roms and nobody ever replies you realize how good those guys are..haha
check out the second line on this thread to reclaim 3 gb of data after using sunshine. I've been s-off for months and just saw this today.
Click to expand...
Click to collapse
do you know where I can find the latest international RUU? what rom are you running now?
@bigp951
Ok so I got the firmware updated to the latest international version 2.10 and was able to flash the ViperOne Rom and I love it just like I did for my M7... Everything is working great, except I have the problem that you mentioned would happen, I only show 1 bar for my signal strength, could you please let me know exactly what you had to do to fix it? Also, I would just like to say thank you once more, you helped me out a great deal and you made my upgrade to the M9 an absolute cake walk, so thank you very much for everything and for explaining the proper steps to take, I appreciate it very much...
I have a Dev edition M8 that i zip RUU'ed back to lollipop. i took a security update successfully, then the 3 preinstall updates in prep for marshmallow. however, I now get an error when taking the actual OTA for marshmallow. I am s-off and bootloader unlocked. I then downloaded the RUU from HTC to run the exe, but i always get error 155. I read @Sneakyghost post about firmware and it said it was either region ID's not matching, or the bootloader being unlocked. I don't see why the unlocked bootloader would be a problem when im s-off and its a dev edition, which is bootloader unlocked out of the box. Anyone know what is causing this?
fyarf said:
I have a Dev edition M8 that i zip RUU'ed back to lollipop. i took a security update successfully, then the 3 preinstall updates in prep for marshmallow. however, I now get an error when taking the actual OTA for marshmallow. I am s-off and bootloader unlocked. I then downloaded the RUU from HTC to run the exe, but i always get error 155. I read @Sneakyghost post about firmware and it said it was either region ID's not matching, or the bootloader being unlocked. I don't see why the unlocked bootloader would be a problem when im s-off and its a dev edition, which is bootloader unlocked out of the box. Anyone know what is causing this?
Click to expand...
Click to collapse
Haha nice man I just finished downloading that exact RUU and I have that exact phone in the exact same state. I got it from someone in the US.
I'll let you know how it goes on mine...
Sneakyghost said:
Haha nice man I just finished downloading that exact RUU and I have that exact phone in the exact same state. I got it from someone in the US.
I'll let you know how it goes on mine...
Click to expand...
Click to collapse
heres my recovery message, just to maybe help troubleshoot it. it mentions userdata being busy (i got an error in the zip ruu flash for userdata, had to flash the ruu zip twice to get an okay), then kidmode missing. not sure what to do besides flash the firmware from http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Modified system apps, sir. That's what it is. Did you root your system?
Edit:
Maybe not. Maybe just can't find those apps cuz it can't mount data.
Something wrong there.
No idea.
I'll see where I end up.
Sneakyghost said:
Modified system apps, sir. That's what it is. Did you root your system?
Edit:
Maybe not. Maybe just can't find those apps cuz it can't mount data.
Something wrong there.
No idea.
I'll see where I end up.
Click to expand...
Click to collapse
i did a factory reset from stock recovery, and kid mode is present now, maybe im onto something...
Edit: not rooted directly from a factory ruu zip (well, hopefully the zip creator did a factory dump and was unmodified) but kid mode wasnt an option before the factory reset
fyarf said:
i did a factory reset from stock recovery, and kid mode is present now, maybe im onto something...
Edit: not rooted directly from a factory ruu zip (well, hopefully the zip creator did a factory dump and was unmodified) but kid mode wasnt an option before the factory reset
Click to expand...
Click to collapse
Unfortunately, I'm with family tonight and won't be able to assist until much later. But note this: the factory reset could well help. I can explain later.
Sneakyghost said:
Unfortunately, I'm with family tonight and won't be able to assist until much later. But note this: the factory reset could well help. I can explain later.
Click to expand...
Click to collapse
ok so i got mine to work.. apparently the zip RUU isnt good. i ran the exe 4.16.1540.8 from here http://forum.xda-developers.com/showthread.php?t=2701376 and then updated ota from there without issue. so my guess is the RUU zip wasnt perfect system-wise,while the exe is straight from htc.
fyarf said:
ok so i got mine to work.. apparently the zip RUU isnt good. i ran the exe 4.16.1540.8 from here http://forum.xda-developers.com/showthread.php?t=2701376 and then updated ota from there without issue. so my guess is the RUU zip wasnt perfect system-wise,while the exe is straight from htc.
Click to expand...
Click to collapse
ok. Where you got that zip from? Cuz I downloaded the 6.xx RUU.exe straight from HTC USA...
Sneakyghost said:
ok. Where you got that zip from? Cuz I downloaded the 6.xx RUU.exe straight from HTC USA...
Click to expand...
Click to collapse
zip was from the same thread, i tried the exe instead because it was an HTC file instead of a contributor. now on MM sense. The 6.xx RUU refused to work no matter what i did, so i OTA'd to the latest version.
fyarf said:
zip was from the same thread, i tried the exe instead because it was an HTC file instead of a contributor. now on MM sense. The 6.xx RUU refused to work no matter what i did, so i OTA'd to the latest version.
Click to expand...
Click to collapse
I seem to be having an entirely different problem. After swapping cables, phones and laptop ports as well as updating drivers, it appears that the usb port of my M8 is broken. I'll have to see at someone else's computer, maybe tomorrow. Pretty frustrating right now as I'm liking the M8 better than my M9 and M7.
[EDIT]
I could stabilize the connection enough to run another, international RUU. The RUU worked fine while the 6.12.1540.4 kept getting stuck at either "checking header" or "sending" - both times with a successfully established connection. I already tweeted HTC asking to have that RUU checked. I assume your findings were correctly indicating a bad RUU, since a.) It also didn't work here and b.) people from my team have confirmed seeing several fail scenarios with that RUU spread over XDA.
Guess that's that then. Thanks for raising the issue. I would have messed around with it much longer otherwise since the error messages are not clearly pointing towards a broken RUU.
[EDIT]
More updates: searching the M8 forum for 6.12.1540.4 turned up this: http://forum.xda-developers.com/showthread.php?p=64320571
That'd mean the RUU fails at the hboot pre-update reboot. All that's needed apparently is to flash only the hboot manually first, so it can proceed. Hence also error 155 which usually indicates issues with the system image. You experienced that most likely because the older hboot couldn't extract the system.img from the rom.zip.
Usually, the procedure is:
RUU updates hboot
RUU reboots to boatloader
RUU updates rest of firmware
RUU sends over the system image in parts
Hboot now decrypts and flashes the part.zips
It just looks like mandatory hboot-first-flash didn't happen right, either not rebooting after it or not flashing it at all.
However, this seems to be fixable by running the hboot/firmware package first and then the complete RUU.
Sneakyghost said:
I seem to be having an entirely different problem. After swapping cables, phones and laptop ports as well as updating drivers, it appears that the usb port of my M8 is broken. I'll have to see at someone else's computer, maybe tomorrow. Pretty frustrating right now as I'm liking the M8 better than my M9 and M7.
[EDIT]
I could stabilize the connection enough to run another, international RUU. The RUU worked fine while the 6.12.1540.4 kept getting stuck at either "checking header" or "sending" - both times with a successfully established connection. I already tweeted HTC asking to have that RUU checked. I assume your findings were correctly indicating a bad RUU, since a.) It also didn't work here and b.) people from my team have confirmed seeing several fail scenarios with that RUU spread over XDA.
Guess that's that then. Thanks for raising the issue. I would have messed around with it much longer otherwise since the error messages are not clearly pointing towards a broken RUU.
[EDIT]
More updates: searching the M8 forum for 6.12.1540.4 turned up this: http://forum.xda-developers.com/showthread.php?p=64320571
That'd mean the RUU fails at the hboot pre-update reboot. All that's needed apparently is to flash only the hboot manually first, so it can proceed. Hence also error 155 which usually indicates issues with the system image. You experienced that most likely because the older hboot couldn't extract the system.img from the rom.zip.
Usually, the procedure is:
RUU updates hboot
RUU reboots to boatloader
RUU updates rest of firmware
RUU sends over the system image in parts
Hboot now decrypts and flashes the part.zips
It just looks like mandatory hboot-first-flash didn't happen right, either not rebooting after it or not flashing it at all.
However, this seems to be fixable by running the hboot/firmware package first and then the complete RUU.
Click to expand...
Click to collapse
I'm not sure about OP, but that worked perfectly for me. I wonder how HTC let a broken RUU.exe past testing?
Double_a2013 said:
I'm not sure about OP, but that worked perfectly for me. I wonder how HTC let a broken RUU.exe past testing?
Click to expand...
Click to collapse
They frequently do. Nothing exciting. That's why I notified HTC. They take their time with fixing them. The earlier the better.
Sneakyghost said:
They frequently do. Nothing exciting. That's why I notified HTC. They take their time with fixing them. The earlier the better.
Click to expand...
Click to collapse
Wow, I didn't realize that. Now if only they'd fix the ATT LTE issues on the dev rom :silly:
Double_a2013 said:
Wow, I didn't realize that. Now if only they'd fix the ATT LTE issues on the dev rom :silly:
Click to expand...
Click to collapse
My ota to the latest dev version got lte on at&t no problem, sure your apn settings are correct?
fyarf said:
My ota to the latest dev version got lte on at&t no problem, sure your apn settings are correct?
Click to expand...
Click to collapse
I've never had to reconfigure them before, regardless of if I'm using GPE or Sense RUUs. I'll give it another shot, and get back in a more timely manner
Edit: Apn settings seem fine. It's using the Nextgenphone one from ATT
Edit #2:
http://forum.xda-developers.com/att...ming-calls-lte-mode-m8-att-arhd-34-0-t3026710
Found this thread about a similar issue. I guess I'll disable HD Voice (Honestly, its borderline useless anyway) and see if that solves anything
I've gone through the (extremely confusing) readme thread several times but would appreciate a concrete answer on dev edition conversion.
My phone is hima_ulatt / firmware v3.38.502.12 / OPJA11000 / CWS_001.
So my question is, once i:
unlock bootloader > s-off > write cid BS_US001,
can i install ruu 4.30.617.12 or would i have to stay within 3.xx.617.xx versions?
jbonetwo said:
I've gone through the (extremely confusing) readme thread several times but would appreciate a concrete answer on dev edition conversion.
My phone is hima_ulatt / firmware v3.38.502.12 / OPJA11000 / CWS_001.
So my question is, once i:
unlock bootloader > s-off > write cid BS_US001,
can i install ruu 4.30.617.12 or would i have to stay within 3.xx.617.xx versions?
Click to expand...
Click to collapse
As far as I know you can't install a 4.x Ruu on 3.x firmware.
The encryption is different.
bubba1601 said:
As far as I know you can't install a 4.x Ruu on 3.x firmware.
The encryption is different.
Click to expand...
Click to collapse
Is there no way to update to the 4.xx versions then? The AT&T software update won't let me upgrade at all (says no updates found).
jbonetwo said:
Is there no way to update to the 4.xx versions then? The AT&T software update won't let me upgrade at all (says no updates found).
Click to expand...
Click to collapse
Download a 4.x based rom, there are several in the rom thread including the latest development rom.
They are stock ROMs that you can flash through twrp.
This one I've used and had no issues with.
https://forum.xda-developers.com/on...m9-4-14-617-6-stock-root-twrp-backup-t3518149
But if you are locked to ATT (unlike me because I'm in Europe and the European M9 is a GSM version.
You might want to try this version (ATT)
https://forum.xda-developers.com/one-m9/development/rom-stock-nougat-4-23-617-1-unlocked-t3553470
bubba1601 said:
Download a 4.x based rom, there are several in the rom thread including the latest development rom.
They are stock ROMs that you can flash through twrp.
This one I've used and had no issues with.
https://forum.xda-developers.com/on...m9-4-14-617-6-stock-root-twrp-backup-t3518149
But if you are locked to ATT (unlike me because I'm in Europe and the European M9 is a GSM version.
You might want to try this version (ATT)
https://forum.xda-developers.com/one-m9/development/rom-stock-nougat-4-23-617-1-unlocked-t3553470
Click to expand...
Click to collapse
Thank you!!
Please elaborate a bit further which part of the ReadMe thread confuses you. It's meant to be a helpful resource and if it's confusing at some point then it might need to get overhauled.
Flashing a rom won't update the firmware. Therefore, the linked roms won't help you much. (C.f. the article that is linked as "the difference between rom and firmware" in the further reading section of the ReadMe thread.)
You need to update the phone with an unencrypted firmware pack (that means an OTA or one of Sneakyghost's firmware packs). As already explained in this thread, RUUs with firmware 4.x use new encryption keys and therefore can't be used for updating from firmware 3.x. In addition, AT&T won't let you install OTAs on their branded phones if you aren't using one of their sim cards.
Either you convert to the 3.x version of the dev firmware and install the available OTAs afterwards or you need to flash a 4.x AT&T firmware pack from Sneakyghost's thread before you convert if you want to directly use the latest dev edition RUU.
Sent from my HTC One M9 using XDA Labs
I got confused too. It's confusing because the paragraphs digress and don't just follow the basic procedures. Probably because the information is necessary but not formatted into idiot speak.. idiot speak is what i needed.
So i thought "fk it my phone is dying anyway so how bad can it get"?.
If you're changing the cid and mid via fastboot do it first and get the firmware.zip of the region you want, at the phones CURRENT firmware level.
Flash the zip version of the firmware from external sdcard. To do that you need to
S-OFF: DONT NEED TO CHANGE ANYTHING.
S-ON: LOCK BOOTLOADER?? (CLARIFY)/CHANGE NOTHING?
rename the firmware.zip* file to whatever the filename asks for at the bottom of download mode (voldown+power), eg 0PJA***.ZIP.
copy it to the external Sdcard (not in a folder, just on its own), reboot phone to download mode, follow prompts.
THE PHONE WILL REBOOT MANY TIMES AND SHOULD TAKE AROUND 30 MINS TO 1 HOUR TO COMPLETE. DO NOT TOUCH THE PHONE. DO NOT TURN IT OFF. DO NOT UNPLUG IT FROM THE CHARGER. Leave it alone!!.
Once that completes you can take the ota.
Well, not everyone owns an SD card and there are other methods for flashing RUUs. That's why the RUU section describes all methods and the conversion guide only has a link to the RUU section. (The steps you describe are all mentioned in the guide for the SD card method.) This way users can choose which method they want to use. And describing all methods in both posts doesn't seem to make sense in my eyes, either.
The infos above the instructions of each post are actually needed for understanding why things are how they are if you've never owned an HTC device before. I can add a title "general info" for making clearer that the posts don't start with instructions, though.
The fact that you don't need to re-lock or lock the bootloader (neither for RUUs nor for OTAs) is e.g. explained in these additional infos. It's not mentioned in the instructions since that info itself is not an instruction.
Btw, a RUU reboots the phone only once and the flash shouldn't take longer than a couple of minutes. OTAs on the other hand can take up to am hour and reboot the phone several times.
Sent from my HTC One M9 using XDA Labs
Yes you are correct as always flippy. The reflash back to stock takes minutes while ota takes an age. Forgot that bit.
You also redefined what i said.. the posts digress to cover all eventualities but it is overwhelming to eejits like myself.
If it was laid out basic THEN cover the eventualities it'd be easier to follow. The english can be a tad broken too, which confuses the fk out of native English speakers like myself.
My post is just the basic. Nothing more, nothing less. If you bork your phone with my instruction it will be a hardware or user fault.
The only thing I'm not sure of, because my phone is s-off, is whether or not the bootloader must be locked or relocked with s-on. Otherwise with s-off they dont matter.
Don't get me wrong, I'm not saying you're feeding false info, I'm just saying that non native english speakers seem to have better results following your instructions better than native speakers, for some reason..
Flippy498 said:
Please elaborate a bit further which part of the ReadMe thread confuses you. It's meant to be a helpful resource and if it's confusing at some point then it might need to get overhauled.
Click to expand...
Click to collapse
Thanks for the info @Flippy498. I'll be re-reading everything thoroughly before attempting anything as i don't want to end up with a brick.
The readme is indeed confusing. It captures the evolution of the m9 since fw 1.xx and the corresponding changes to modding procedures. While this makes for a great catalogue of all info, even a seasoned flash-o-phile would find it difficult to navigate the veritable minefield of do's and don't's.
I'd love to redo the logic of the thread myself but don't know enough about this device yet. but perhaps something that determines one's fw/mid/cid through fastboot first, followed by targeted instructions for achieving different goals based on those differences would be much more legible. (e.g. if fw v 3.xx, do this to unlock but warning about flashing 4.xx). As it stands, coming from v 3.xx, one has to read several disjointed notes peppered around the thread only some of which are relevant and this only adds to the confusion via information overload.
If you have s-off youre good to go in any circumstances. Just check the os that it is on and return it to stock of that version os OR
If you change the cid and mid just flash to stock of THAT version AND the region you change to. Like changing from 401 to 617 you flash the 617 because it matches the cid and mid you changed to. It must still match the os version the phone is on ie marshmallow 3.35.xxx.xx, making it the 3.35.617.xx firmware you'd be looking to flash to get stock marshmallow..
Then you just take the ota updates as far as you like.
I flashed 2 s-off phones back to stock in the last week in one sitting and it was easy, just as I explained.
It's just bootloader in s-on conditions that I personally don't know and that throws me a bit. I don't know if it's a requirement or not. I'd highly recommend buying s-off via sunshine in all cases but otherwise flippy would have to answer a simple yes or no to "bootloader locked for s-on flashing?" or you'd have to dredge it up on a search site. The other option is bite the bullet and flash anyway hoping it boots you out with an error.
shivadow said:
flippy would have to answer a simple yes or no to "bootloader locked for s-on flashing?"
Click to expand...
Click to collapse
It doesn't matter whether the bootloader is locked, re-locked or unlocked.
Sent from my HTC One M9 using XDA Labs
shivadow said:
If you have s-off youre good to go in any circumstances. Just check the os that it is on and return it to stock of that version os OR
Click to expand...
Click to collapse
Your method worked great! changed cid & mid to dev edition, flashed dev edition and then used 'software update' to catch up to latest version. couldn't be easier, thanks!
Now for that obnoxious red text...
I take no credit for anything. All I did was make the process clearer. Glad you're sorted!.
Hi guys,
I hope you can help me solve my issue. I spend the entire evening try to do it, reading through the post on this forum but I couldn't figure out a solution.
So basically I bought an HTC 10 unlocked in Ireland, and I currently have Android 7 , no mods or anything on it.
I know there was an OTA update available, but every time I check for software updates I get the error Can't update software. There was an unexpected error and the file system may be corrupted.
I tried then to do a manual update. I download the file (ruu I think) from HTC website and I rebooted the device in download mode and tryed to install. I got error 130
to perform a manual update via PC but it didn't work, I received a model ID error (Model ID error)
I did a factory reset and tried OTA again with no luck.
I am looking for some pratical advice, Any help would be much appreciated!
Thanks,
Vincent
VincentHTC10 said:
Hi guys,
I hope you can help me solve my issue. I spend the entire evening try to do it, reading through the post on this forum but I couldn't figure out a solution.
So basically I bought an HTC 10 unlocked in Ireland, and I currently have Android 7 , no mods or anything on it.
I know there was an OTA update available, but every time I check for software updates I get the error Can't update software. There was an unexpected error and the file system may be corrupted.
I tried then to do a manual update. I download the file (ruu I think) from HTC website and I rebooted the device in download mode and tryed to install. I got error 130
to perform a manual update via PC but it didn't work, I received a model ID error (Model ID error)
I did a factory reset and tried OTA again with no luck.
I am looking for some pratical advice, Any help would be much appreciated!
Thanks,
Vincent
Click to expand...
Click to collapse
Boot to download mode, read the OS line and look for the matching ruu.zip.
Mr Hofs said:
Boot to download mode, read the OS line and look for the matching ruu.zip.
Click to expand...
Click to collapse
Hi Mr Hofs ,
OS-2.41.771.3
I should find an RUU with the same line and try the procedure again?
Yes one with the same line or a higher one, or a matching stock backup.
When you succeed to upgrade and tinker again with the device it's wise to create a pure stock backup for the future.
VincentHTC10 said:
Hi Mr Hofs ,
OS-2.41.771.3
I should find an RUU with the same line and try the procedure again?
Click to expand...
Click to collapse
Mr Hofs said:
Yes one with the same line or a higher one, or a matching stock backup.
When you succeed to upgrade and tinker again with the device it's wise to create a pure stock backup for the future.
Click to expand...
Click to collapse
Mr Hofs,
thanks for your help.
I have found this 2PS6IMG PERFUME UHL N70 SENSE80GP MR Telstra WWE 2.48.841.3 Radio [email protected] 80.07 F release 505754 partial
and it's only 105MB
Do you think this one could work?
Thanks for your help, I am not very familiar with this kind of things.
Vincent
VincentHTC10 said:
Mr Hofs,
thanks for your help.
I have found this 2PS6IMG PERFUME UHL N70 SENSE80GP MR Telstra WWE 2.48.841.3 Radio [email protected] 80.07 F release 505754 partial
and it's only 105MB
Do you think this one could work?
Thanks for your help, I am not very familiar with this kind of things.
Vincent
Click to expand...
Click to collapse
As been explained you need one with your OS number. Not some random firmware. 2.48.841 doesn't come near 2.41.771 .......
also a full ruu is at least 1.8 gig
Edit :
Especially the. 771 part has to match. The first 2.41 should match or be higher.
Mr Hofs said:
As been explained you need one with your OS number. Not some random firmware. 2.148.841 doesn't come near 2.41.771 .......
also a full ruu is at least 1.8 gig
Edit :
Especially the. 771 part has to match. The first 2.41 should match or be higher.
Click to expand...
Click to collapse
I thought it was 2.48 hence higher, didn't see the 1
The closer I could find online is 2.41.041.4 which is lower than the one that I have so I guess is not good.
Is there other way to do it ? a work around?
My phone is running at the moment I don't know why some files got corrupted.
VincentHTC10 said:
I thought it was 2.48 hence higher, didn't see the 1
The closer I could find online is 2.41.041.4 which is lower than the one that I have so I guess is not good.
Is there other way to do it ? a work around?
My phone is running at the moment I don't know why some files got corrupted.
SN:
IMEI
Click to expand...
Click to collapse
DELETE your imei and SN ASAP. that's never ment to be on an online platform!
Second option is to pay for S-OFF via sunshine and convert the device to wwe which has all RUU files available.
And as i explained allready and will do that again, your 771 part has to MATCH so it can't be 041 or 401 or 841 it MUST be. 771. So either 2.41.771 or 3.16.771 or 3.18.771 (as examples)
Mr Hofs said:
DELETE your imei and SN ASAP. that's never ment to be on an online platform!
Second option is to pay for S-OFF via sunshine and convert the device to wwe which has all RUU files available.
And as i explained allready and will do that again, your 771 part has to MATCH so it can't be 041 or 401 or 841 it MUST be. 771. So either 2.41.771 or 3.16.771 or 3.18.771 (as examples)
Click to expand...
Click to collapse
Thanks for your clarifications, Mr Hofs.
Yesterday evening I was able to find and buy this firmware 2PS6IMG_PERFUME_UHL_O80_SENSE90GP_MR_H3G_UK_3.18.771.1[email protected]_84.09_F_release_519646_signed.zip
that according to your explanation should be a good fit.
I downloaded the file on my pc and then I followed a guide to try and install it using "adb and fastboot" but when I gave the comand to run it and I received an error that the file was too big and the adb crashed as well, so I wasn't able to try to install it on the phone. I saw there are many different guides online. Do you know if there s a good one that works ?
Thanks for your help!
Vincent
VincentHTC10 said:
Thanks for your clarifications, Mr Hofs.
Yesterday evening I was able to find and buy this firmware 2PS6IMG_PERFUME_UHL_O80_SENSE90GP_MR_H3G_UK_3.18.[email protected]_84.09_F_release_519646_signed.zip
that according to your explanation should be a good fit.
I downloaded the file on my pc and then I followed a guide to try and install it using "adb and fastboot" but when I gave the comand to run it and I received an error that the file was too big and the adb crashed as well, so I wasn't able to try to install it on the phone. I saw there are many different guides online. Do you know if there s a good one that works ?
Thanks for your help!
Vincent
Click to expand...
Click to collapse
Yep should be great. You have to rename the ruu.zip to 2PS6IMG.zip only and copy it to your SDcard. Boot to download mode and follow the flash instructions. The file will be auto detected. Be aware that this will wipe the ENTIRE phone.
Edit :
You said "buy" ? Now i am wondering where you bought it and how much you payed for it ?
Mr Hofs said:
Yep should be great. You have to rename the ruu.zip to 2PS6IMG.zip only and copy it to your SDcard. Boot to download mode and follow the flash instructions. The file will be auto detected. Be aware that this will wipe the ENTIRE phone.
Edit :
You said "buy" ? Now i am wondering where you bought it and how much you payed for it ?
Click to expand...
Click to collapse
yes, I bought it for 3$ on firmware.gem-flash.com They have plenty of firmware there was also the 2.41.771.3 version.
I thought better pay 3$ than 25$ to buy the license for sunshine.
..Let`s see if it works now, finger crossed
VincentHTC10 said:
yes, I bought it for 3$ on firmware.gem-flash.com They have plenty of firmware there was also the 2.41.771.3 version.
I thought better pay 3$ than 25$ to buy the license for sunshine.
..Let`s see if it works now, finger crossed
Click to expand...
Click to collapse
I get few errors as well here
End ui_updating, press power key to continue
it says
12 RU_ZIP_ERROR
12 RU_ZIP_ERROR
FAIL12 RU_ZIP_ERROR
press power to continue (it shuts the phone )
when I restart everything as usual.
Do you think I should try with the original firmware? ( I can have it with another 3$ )
VincentHTC10 said:
I get few errors as well here
End ui_updating, press power key to continue
it says
12 RU_ZIP_ERROR
12 RU_ZIP_ERROR
FAIL12 RU_ZIP_ERROR
press power to continue (it shuts the phone )
when I restart everything as usual.
Do you think I should try with the original firmware? ( I can have it with another 3$ )
Click to expand...
Click to collapse
Dude - stop wasting your money on that website. All the files are available here @ XDA (nearly all!) for free via links already posted or by asking.
The RU_FAILED is because the file you got doesnt match the CID of your phone. The CID is basically the Network Lock on the phone - dont get confused with Sim Lock.
Go on Google Playstore and install; Simple CID Getter. Let us know here what it says. e.g; HTC_001 (Mines H3G_001 which is 3 UK Network)
Then we can get you further along.....
alchemist83 said:
Dude - stop wasting your money on that website. All the files are available here @ XDA (nearly all!) for free via links already posted or by asking.
The RU_FAILED is because the file you got doesnt match the CID of your phone. The CID is basically the Network Lock on the phone - dont get confused with Sim Lock.
Go on Google Playstore and install; Simple CID Getter. Let us know here what it says. e.g; HTC_001 (Mines H3G_001 which is EE Network)
Then we can get you further along.....
Click to expand...
Click to collapse
alchemist83 thanks for your suggestions. Here is my CID: H3G__003 ( 3 network)
Waiting for instruction :angel:
VincentHTC10 said:
alchemist83 thanks for your suggestions. Here is my CID: H3G__003 ( 3 network)
Waiting for instruction :angel:
Click to expand...
Click to collapse
So thats your pain in the arse (3 network! Me too - UK!)
Currently there does NOT seem to be any RUU for our networks.
Only way forward for both of us it would seem is to S-Off via Sunshine.
If you have already - then sweet, you can change your CID to 11111111 which will mean you can flash that zip you got and it will work.
Search or ask here on XDA about changiing CID to 11111111. Plenty have done before, so shouldnt be too hard for you.
I havent done it since HTC M7 so I cant remember, need to look it up myself.
Hope that helps!
alchemist83 said:
So thats your pain in the arse (3 network! Me too - UK!)
Currently there does NOT seem to be any RUU for our networks.
Only way forward for both of us it would seem is to S-Off via Sunshine.
If you have already - then sweet, you can change your CID to 11111111 which will mean you can flash that zip you got and it will work.
Search or ask here on XDA about changiing CID to 11111111. Plenty have done before, so shouldnt be too hard for you.
I havent done it since HTC M7 so I cant remember, need to look it up myself.
Hope that helps!
Click to expand...
Click to collapse
ahahah good to know!
So I understand what you say.. but what if I pay 3$ and download the exact firmware that I have at the moment 2PS6IMG_PERFUME_UHL_N70_SENSE80GP_MR_H3G_UK_2.41.771.31_[email protected]_79.07_F_release_509479_combined_signed.zip
After that (once the file system is no longer corrupted) I could try to do an OTA update
It would be too easy so maybe the problem is that I can`t be sure that firmware is for 3 network right?
VincentHTC10 said:
ahahah good to know!
So I understand what you say.. but what if I pay 3$ and download the exact firmware that I have at the moment 2PS6IMG_PERFUME_UHL_N70_SENSE80GP_MR_H3G_UK_2.41.771.31_[email protected]_79.07_F_release_509479_combined_signed.zip
After that (once the file system is no longer corrupted) I could try to do an OTA update
It would be too easy so maybe the problem is that I can`t be sure that firmware is for 3 network right?
Click to expand...
Click to collapse
Thats actually prob the 1 I need (if you have the file name BTW - search it in Google, for sure you might get lucky on a Download and NOT have to pay, might even find it on here XDA, theres a very good chance of that.)
For you however the need the file thats says H3G_ROI cos your CID is that. H3G__003 = H3G_ROI (Republic Of Ireland).
Mine is H3G__001 = H3G_UK. Soz bud dont think will work. You try, it will only fail or do it. It wont bust it if it does do it. S-OFF is calling you doh.... $25 about 18 pound UK.
---------- Post added at 11:39 PM ---------- Previous post was at 11:18 PM ----------
So if you do S-OFF and wanna go full OREO and have go Super CID 1111111.. whatever it is, then heres a link for WWE (Europe) RUU OREO zip for you HERE.
Rename it as you did before to 2PS6IMG etc - you've done it before lols. Best of luck
If the version number matches it's great to use. There is no RUU with 3.18.771 created for 2 different CID sets specifically. So that's not the problem. Either take the 2.41.771 (full ruu). Not only the firmware because if your OS is screwed you will be in the same boat again I remember they pulled the US ruu and they had to update the standalone firmware prior to using to the full ruu. You could check out to take the firmware from the ruu and flash it prior to the ruu.
That's done via download mode, htc ruu mode and Fastboot commands
VincentHTC10 said:
I get few errors as well here
End ui_updating, press power key to continue
it says
12 RU_ZIP_ERROR
12 RU_ZIP_ERROR
FAIL12 RU_ZIP_ERROR
press power to continue (it shuts the phone )
when I restart everything as usual.
Do you think I should try with the original firmware? ( I can have it with another 3$ )
Click to expand...
Click to collapse
---------- Post added at 04:04 AM ---------- Previous post was at 03:54 AM ----------
alchemist83 said:
Thats actually prob the 1 I need (if you have the file name BTW - search it in Google, for sure you might get lucky on a Download and NOT have to pay, might even find it on here XDA, theres a very good chance of that.)
For you however the need the file thats says H3G_ROI cos your CID is that. H3G__003 = H3G_ROI (Republic Of Ireland).
Mine is H3G__001 = H3G_UK. Soz bud dont think will work. You try, it will only fail or do it. It wont bust it if it does do it. S-OFF is calling you doh.... $25 about 18 pound UK.
---------- Post added at 11:39 PM ---------- Previous post was at 11:18 PM ----------
So if you do S-OFF and wanna go full OREO and have go Super CID 1111111.. whatever it is, then heres a link for WWE (Europe) RUU OREO zip for you HERE.
Rename it as you did before to 2PS6IMG etc - you've done it before lols. Best of luck
Click to expand...
Click to collapse
If you look at your and his original OS/firmware number the RUU should work. It's definitely not CID related at this point. They don't create 2 ruu files with the same firmware number for 2 or even more CID numbers, if you check a ruu and open the host file you will see more than 1 CID in there.
He has a matching ruu but i think it has the same issue as the US version has.
He took his OS line from the download mode, that number can't change without s-off so that's the thing you'd have to look at. It's not suddenly changing because of the CID.
Also if he had to look at h3g ROI his version number would have been different, in that case it should be 2.41.773 and not 771....... there is no H3G ROI for the HTC 10, it's integrated in the UK version range.
And also i googled some on this ruu, not easy to track or dead links or spam. So i can understand his call to buy it for 3.
If he wants to pay another 3 for the 2.41.771 than its his call. It's a big difference to 25. I can't look inside his wallet. However i share your feeling that sunshine would a more valuable investment.
Fair point Mr Hofs, I dont know enough really to be able to help fully. I need the same help to update my phone. I looked at the same place these RUU are available for $3 and they have alot more than has been listed (example; OREO update for 3 UK). I am considering downloading myself (and sharing for all!). I want to make sure I get the correct version - but I'm having trouble finding my version numbers so I get the right one. I've perhaps made it harder but using the Venom custom Rom. I've looked in about but cant find anything that makes sense. Can you advise where I can find the version numbers? Cheers
alchemist83 said:
Fair point Mr Hofs, I dont know enough really to be able to help fully. I need the same help to update my phone. I looked at the same place these RUU are available for $3 and they have alot more than has been listed (example; OREO update for 3 UK). I am considering downloading myself (and sharing for all!). I want to make sure I get the correct version - but I'm having trouble finding my version numbers so I get the right one. I've perhaps made it harder but using the Venom custom Rom. I've looked in about but cant find anything that makes sense. Can you advise where I can find the version numbers? Cheers
Click to expand...
Click to collapse
Man if your OS number is the same as mine I can share with you the file I downloaded and see if it can be useful for you at least.
I think I am gonna try to download the same version that I have at the moment as It seems an easier way than use sunshine to S-OFF and go down that way.
I ll keep you posted. Cheers
Hey guys,
After getting overwhelming reading on forums only to get my self confused at the end. Most threads I came across is last edited in 2016. Therefore I am little skeptical about moving forward.
Bottomline problem, Phone is fully working with PixelExperience ROM installed ( Clean flash) at the moment. BUT IT DOES NOT DETECT SIM CARD.
Model : HTC 10
Android Version : 9
Kernel Version : 3.18.120-IceMan-CAF-LA.UM.7.5
The phone was bought unlocked from HTC.
I have bootloader unlocked, but S-on.
TWRP version 3.3.1 (as of July 22-2019)
Upon reading many thread, It boils down to that I need to RUU in order to get my radio back working. (SIM card detection)
now RUU will not work unless I have S-off, in order to get S-off in need to pay sunshine fee.
Now sunshine needs device to be rooted.
My device is never rooted before, now rooting device has choices, something called SuperSu or Magisk etc.
this is where I am super confused.
I need help before I move on.
My understanding is
step 1: root the device as I already have bootloader unlocked. and TWRP installed and working.
Step 2 : get the S-off by paying sunshine fee
Step 3 : RUU the zip to go back to stock!! ( here also one more question , my kernel is already latest what does RUU do? will it downgrade? )
Step 4 : insert sim and use the Phone as intended !!!(lol)
Please help, I am having nightmare.
theteju said:
Hey guys,
After getting overwhelming reading on forums only to get my self confused at the end. Most threads I came across is last edited in 2016. Therefore I am little skeptical about moving forward.
Bottomline problem, Phone is fully working with PixelExperience ROM installed ( Clean flash) at the moment. BUT IT DOES NOT DETECT SIM CARD.
Model : HTC 10
Android Version : 9
Kernel Version : 3.18.120-IceMan-CAF-LA.UM.7.5
The phone was bought unlocked from HTC.
I have bootloader unlocked, but S-on.
TWRP version 3.3.1 (as of July 22-2019)
Upon reading many thread, It boils down to that I need to RUU in order to get my radio back working. (SIM card detection)
now RUU will not work unless I have S-off, in order to get S-off in need to pay sunshine fee.
Now sunshine needs device to be rooted.
My device is never rooted before, now rooting device has choices, something called SuperSu or Magisk etc.
this is where I am super confused.
I need help before I move on.
My understanding is
step 1: root the device as I already have bootloader unlocked. and TWRP installed and working.
Step 2 : get the S-off by paying sunshine fee
Step 3 : RUU the zip to go back to stock!! ( here also one more question , my kernel is already latest what does RUU do? will it downgrade? )
Step 4 : insert sim and use the Phone as intended !!!(lol)
Please help, I am having nightmare.
Click to expand...
Click to collapse
Where are you reading soff is needed for ruu.
That's not true.
You need an ruu for your specific device model.
Which model is your 10?
andybones said:
Where are you reading soff is needed for ruu.
That's not true.
You need an ruu for your specific device model.
Which model is your 10?
Click to expand...
Click to collapse
kindly see the screenshot attached. very first line says S-on people not here.
my model is HTC 10
SN# HT69XBN00387
it is GSM unlocked.
andybones said:
Where are you reading soff is needed for ruu.
That's not true.
You need an ruu for your specific device model.
Which model is your 10?
Click to expand...
Click to collapse
Now I know what you asking. may be this is proper answer.
fastboot getvar all
kernel: lk
product: htc_pmewl
version: 1.0
max-download-size: 1578400000
serialno: HT69XBN00387
slot-count: 0
current-slot:
imei: 354259077770388
version-main: 3.16.617.2
boot-mode: download
version-baseband: [email protected]
version-bootloader: 1.0.0.0000
mid: 2PS650000
cid: BS_US001
Click to expand...
Click to collapse
theteju said:
kindly see the screenshot attached. very first line says S-on people not here.
my model is HTC 10
SN# YOU CAN HIDE THIS.. NOT NEEDED AND SPECIFIC TO YOUR DEVICE.
it is GSM unlocked.
Click to expand...
Click to collapse
Do you see it say FIRMWARE.. that's not an ruu.
Firmware is a way of updating from say N to P without needing to flash entire ruu.
Firmware is in the ruu along with system, boot, recovery..
theteju said:
Now I know what you asking. may be this is proper answer.
Click to expand...
Click to collapse
3.16.617.2 = us unlocked
Simply find the 3.16.617.2 RUU and flash it.
Here.. https://androidfilehost.com/?fid=818070582850487062
This will wipe internal storage..
How to install:
Option 1 - PERSONALLY SUGGESTED
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
andybones said:
Do you see it say FIRMWARE.. that's not an ruu.
Firmware is a way of updating from say N to P without needing to flash entire ruu.
Firmware is in the ruu along with system, boot, recovery..
3.16.617.2 = us unlocked
Simply find the 3.16.617.2 RUU and flash it.
Here.. https://androidfilehost.com/?fid=818070582850487062
This will wipe internal storage..
How to install:
Option 1 - PERSONALLY SUGGESTED
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Click to expand...
Click to collapse
Respected Andybones,
I cannot thank you enough sir. After struggling for almost 48 hours. reading a lot threads. Sleepless nights. Finally my Phone is Back to Stock!!
(I am certainly hoping that it would now see the SIM card. I have to go to At&t store tomorrow to get my IMEI into their system.)
I just want to borrow your brain for few more questions.
I noticed that I am on Android 8 now.
Does this mean, My bootloader is locked again? TWRP is gone?
Can I install custom ROM?
Finally, what caused such issue? I do not understand what happened?
If you own HTC 10, what rom do you recommend? I used LinageOS.
Let me know,
Sincerely,
theteju said:
Respected Andybones,
I cannot thank you enough sir. After struggling for almost 48 hours. reading a lot threads. Sleepless nights. Finally my Phone is Back to Stock!!
(I am certainly hoping that it would now see the SIM card. I have to go to At&t store tomorrow to get my IMEI into their system.)
I just want to borrow your brain for few more questions.
I noticed that I am on Android 8 now.
Does this mean, My bootloader is locked again? TWRP is gone?
Can I install custom ROM?
Finally, what caused such issue? I do not understand what happened?
If you own HTC 10, what rom do you recommend? I used LinageOS.
Let me know,
Sincerely,
Click to expand...
Click to collapse
You're so very welcome.
Trust me, I know how tough it can be to fully understand an htc device and it's workings. Once you start to get into it like you have now, I'm sure you came out with some knowledge, so I'm more than happy to help.
I didn't realize you were still on Android 7. You're on 8 now because the RUU I gave you was android 8.(don't try and downgrade. You can but it's not as easy as flashing the android 7 ruu)
The ruu contains everything to make your device stock again, including stock system, stock kernel, stock recovery.
Flashing ruu doesn't touch an soff flag nor bootloader lock.(boot on into download mode and check it out). But even if it did lock it, which won't ever happen, you can always re-unlock bootloader.
It's only us Verizon users who suffer by blocking us from unlocking. NOT COOL VERIZON!!!
You just need to flash twrp again (get latest version), then flash roms as you desire.
I suggest any recent Pie rom. Thanks to dev Fagyi he has really made this phone great again. He maintains Stock lineage 16 is awesome, and theirs a few roms out based on his lineage, including my crdroidandroid rom. Also Fagyi has I think 2 roms based on AOSP rather lineage.
If you want Sense then LeeDroid is the ROM you want.
I'm actually not too sure what caused the sim issue unfortunately. I do have faith that att can get it going for you tmw. Fingers are crossed my friend.
Please keep me posted. :good:
andybones said:
I'm actually not too sure what caused the sim issue unfortunately. I do have faith that att can get it going for you tmw. Fingers are crossed my friend.
Please keep me posted. :good:
Click to expand...
Click to collapse
andybones said:
I'm actually not too sure what caused the sim issue unfortunately. I do have faith that att can get it going for you tmw. Fingers are crossed my friend.
Please keep me posted. :good:
Click to expand...
Click to collapse
Respected Andybones,
This is just an update. Please give me your input whenever u get a chance. Here is what happened.
My phone got back to stock succefully. I noticed it did not touch the bootloader. it was still unlocked. S-on. I successfully flashed TWRP again. All went well. Next day morning I was supposed to go to ATT store and get phone working. but I could not wait till morning. That night I flashed the phone with Pixel Experience again, as I thought my radio should be working now. ( I think I should have waited. Not sure why?)
So once again, I have perfectly working phone with Pixel Experience rom on it. but yet again it does not detect SIM card. The difference between stock and this rom is, STock was showing bars on top. at least detecting no cellular network. This is my uneducated guess!! lol
I am one-more time going to RUU with your zip. restore back to stock and shall see what happens. ( I know I should have waited before I flashed with PE)
Just to confirm and make sure.. I believe am currently on Oreo Firmware as the OS - 3.16.617.2 ( displays on download mode)
I think I should still be fine with the RUU zip you gave me.
theteju said:
Respected Andybones,
This is just an update. Please give me your input whenever u get a chance. Here is what happened.
My phone got back to stock succefully. I noticed it did not touch the bootloader. it was still unlocked. S-on. I successfully flashed TWRP again. All went well. Next day morning I was supposed to go to ATT store and get phone working. but I could not wait till morning. That night I flashed the phone with Pixel Experience again, as I thought my radio should be working now. ( I think I should have waited. Not sure why?)
So once again, I have perfectly working phone with Pixel Experience rom on it. but yet again it does not detect SIM card. The difference between stock and this rom is, STock was showing bars on top. at least detecting no cellular network. This is my uneducated guess!! lol
I am one-more time going to RUU with your zip. restore back to stock and shall see what happens. ( I know I should have waited before I flashed with PE)
Just to confirm and make sure.. I believe am currently on Oreo Firmware as the OS - 3.16.617.2 ( displays on download mode)
I think I should still be fine with the RUU zip you gave me.
Click to expand...
Click to collapse
Hey man, I don't think it's any issue you flashed pixel experience. You can always just reflash the ruu and get back to stock. Unfortunately, it could be a physical issue with the sim not getting detected but since stock showed bars, I think you need a new att sim card possibly.
But yes you may flash that same ruu and any that are x.xx.617.x and up. But I think the one I gave is the newest.
.617 refers to your device.
Mine for example (Verizon) is .605
Hope I've been of help. :good:
andybones said:
Hey man, I don't think it's any issue you flashed pixel experience. You can always just reflash the ruu and get back to stock. Unfortunately, it could be a physical issue with the sim not getting detected but since stock showed bars, I think you need a new att sim card possibly.
But yes you may flash that same ruu and any that are x.xx.617.x and up. But I think the one I gave is the newest.
.617 refers to your device.
Mine for example (Verizon) is .605
Hope I've been of help. :good:
Click to expand...
Click to collapse
Your guess was right. Does not seem like ROM issue. It now seems like hardware issue. I may have missed to connect an antenna properly. Or Something got damaged. I cannot say for sure.
I am now on market to for new phone at an odd time of the year !!!
I must thanks again for all your replies and answers with patience.
theteju said:
Your guess was right. Does not seem like ROM issue. It now seems like hardware issue. I may have missed to connect an antenna properly. Or Something got damaged. I cannot say for sure.
I am now on market to for new phone at an odd time of the year !!!
I must thanks again for all your replies and answers with patience.
Click to expand...
Click to collapse
Dang, I'm sorry my friend. And you're so very welcome.
You didn't mention what happened when you brought to att
I wish it could hold for the pixel4, i think im gunna grab one.That or maybe something else, who knows, lol.
but best wishes!
andybones said:
Dang, I'm sorry my friend. And you're so very welcome.
You didn't mention what happened when you brought to att
I wish it could hold for the pixel4, i think im gunna grab one.That or maybe something else, who knows, lol.
but best wishes!
Click to expand...
Click to collapse
I am temperory using iphone 4s. Life is in slowMotion mode using that phone since two weeks. LOL
I am eyeing Nokia 7.1. What are your thoughts?
any comment on Mi9?