Rogers said the new HTC EVO 3D bootloader would come unlocked, yet, on the bootloader screen, I get this:
Code:
*** LOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0008
eMMC-boot
Jul 15 2011,14:39:25
Does't look unlocked to me...
Has anyone been able to successfully unlock/root a GSM EVO 3D yet?
Don't take Social Media's "word" as any sort of truth, they just relay information.
HTC hasn't released the OTA yet to unlock the bootloader but they will.
This actually came from a Rogers rep on a Rogers website: http://mobilesyrup.com/2011/07/18/rogers-yes-our-htc-evo-3d-will-have-an-unlocked-bootloader/
Here's the actual Rogers site: http://redboard.rogers.com/2011/eve...oducing-the-htc-evo-3d-and-the-lg-optimus-3d/
Yeah I was hoping it would come unlocked too but it looks like we're going to have to wait.
Sent from my HTC EVO 3D using Tapatalk
Turge said:
This actually came from a Rogers rep on a Rogers website: http://mobilesyrup.com/2011/07/18/rogers-yes-our-htc-evo-3d-will-have-an-unlocked-bootloader/
Here's the actual Rogers site: http://redboard.rogers.com/2011/eve...oducing-the-htc-evo-3d-and-the-lg-optimus-3d/
Click to expand...
Click to collapse
I know where your information came from.
I told you, never take Social Media's information as any form of "truth". Anything they post is still bound by the legal disclaimer on all Rogers websites that their information is subject to change and may not be accurate. Do you really expect a journalist to know anything about a Bootloader? All they do is spew information they're told, and do a half assed job at best with that.
That being said, the bootloader will get unlocked, likely sooner by Revolutionary than by HTC themselves.
Don't feel bad, the European EVO3D users are in the same boat.
It actually shows "locked" in the bootloader? Just out of curiousity, can someone check to see what fastboot commands are available? You can find out by using fastboot oem ? (with the question mark) or fastboot oem h while it is in fastboot mode.
xHausx said:
It actually shows "locked" in the bootloader? Just out of curiousity, can someone check to see what fastboot commands are available? You can find out by using fastboot oem ? (with the question mark) or fastboot oem h while it is in fastboot mode.
Click to expand...
Click to collapse
Here ya go:
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) checkSbl1
(bootloader) checkHWSecurity
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readpid
(bootloader) writepid
(bootloader) readcid
(bootloader) writecid
(bootloader) readimei
(bootloader) writeimei
(bootloader) readsecureflag
(bootloader) writesecureflag
(bootloader) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) load_modem_emmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
They must have just added that get_identifier_token command, I don't remember seeing it in the 1.30 hboot and the it's not in the eng hboot either.
Can you give it a try to see what it does?
Code:
fastboot oem writesecureflag 0
fastboot oem get_identifier_token ?
xHausx said:
They must have just added that get_identifier_token command, I don't remember seeing it in the 1.30 hboot and the it's not in the eng hboot either.
Can you give it a try to see what it does?
Code:
fastboot oem writesecureflag 0
fastboot oem get_identifier_token ?
Click to expand...
Click to collapse
From the looks of it, a gold card might be needed?
Code:
fastboot oem writesecureflag 0
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) shooter_u_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
(bootloader) writesecureflag: Permission denied, value 1
OKAY [ 1.084s]
finished. total time: 1.086s
fastboot oem get_identifier_token ?
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 979CAC9BC47B6A2DA6164C92F581BE6C
(bootloader) D48C11BF91C56DF93EB96ABBFDC0B557
(bootloader) 5C3794863CB29EE44BF2BDA4B684ECDC
(bootloader) D091FAA3D9373B838B81138D5E930523
(bootloader) 41343BCE21D915B2926BD3E20F6F62CB
(bootloader) D22B9904764499498AE78DC6880CBD81
(bootloader) 6A337E89DDB34F9970F3CCB3E042FD87
(bootloader) A89849D1FDBE1DAA7E63D979E43B2849
(bootloader) F4D1E2207BEEEE481E4AEF3DF8A569D1
(bootloader) 75C66DAA8B41FA6812A462A0F12E469E
(bootloader) F505A0B8B986E40745A81633FC287B2A
(bootloader) 7C975C2B54AE7FF86002FA119B4ACD66
(bootloader) DC92B98D6C1636F71EC23FBC5FFD153B
(bootloader) 8EEFB5A7A9BF12448EA5234CD62B43B7
(bootloader) 1F97385D6A6D890BBDD3ED1673AB2EBD
(bootloader) FE90D203A4F1EAF01FAC3FC5A4A06627
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.073s]
finished. total time: 0.075s
The locked part it says must be for world unlocked. To use any sim.
They updated the RedBoard yesterday:
Rogers_Chris says: August 10, 2011 at 5:04 pm
Hi Andy,
When we announced the HTC EVO 3D coming to Rogers, we communicated that the device would launch with an unlocked bootloader (as Katie wrote above). Our apologies – we have since learned that the device will not be shipped unlocked. For more information on webtools, please visit the HTC website ww.HTCdev.com. If you decide to make a change, please note that some actions may void warranties.
Mnemoch said:
They updated the RedBoard yesterday:
Rogers_Chris says: August 10, 2011 at 5:04 pm
Hi Andy,
When we announced the HTC EVO 3D coming to Rogers, we communicated that the device would launch with an unlocked bootloader (as Katie wrote above). Our apologies – we have since learned that the device will not be shipped unlocked. For more information on webtools, please visit the HTC website ww.HTCdev.com. If you decide to make a change, please note that some actions may void warranties.
Click to expand...
Click to collapse
Looks like June 24th all over again.
My "DU4L C0R3 SH00T3R" shot you down in 3D! -Security Off-
Related
Hello all,
I'm hoping someone can tell me what I'm doing wrong.
I went to HTCdev and got the unlock code emailed but this is happening when i try to unlock,I put the code in the same folder as the fastboot...
C:\Joey\Unlock Tools>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 09676CC238975AE58745ED43A1A50C8A
(bootloader) ECF90A6E24B47051377B15F0178DF92C
(bootloader) A393503ADCC8606FC14ED1761E2456F6
(bootloader) F57F798477728947A8B7E1EBD8C343BA
(bootloader) 3966E2A81DF8844D9470FF08C7F75B60
(bootloader) AE0F848DE98EA5CE3D0C4341902723C5
(bootloader) F773CAAACE0D1F8E84BCB246BCC410E3
(bootloader) 02670551F637FB8AD6E4783FDDABD8D4
(bootloader) CAC4613F93ABB73203D1EB8552BA705F
(bootloader) 9417AC2E0E0DFD82F424EB0141A0E47F
(bootloader) B1CDF5791CD1F196A2B5282143FCFB1E
(bootloader) 57453E81BFC316B3D372F6DD74D65FA6
(bootloader) F6DB2C323BCB1BFE4040B59C10B4FC90
(bootloader) 77CFE117D6670229E2FF6C64C6125601
(bootloader) C7671A07B7034C492C85213FCCDC0DD3
(bootloader) A019ADDF0F220049A7404264BAE50571
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Joey\Unlock Tools>fastboot flash unlocktoken Unlock_code.bin
error: cannot load 'Unlock_code.bin'
Idea
I don't see the part where you got an email with the unlock code from HTC.
You have to submit that text to HTC, get an email with the file, put the file in the same folder as Fastboot, and then apply it.
Thanks for the reply,I got the code emailed and downloaded.I put it in the folder with the fastboot and got the error...I have no Idea what I did wrong.
Don't reboot your phone...also...male sure the phone is still in fastboot obviously.
Sent from my ADR6425LVW using XDA App
Thanks for your reply also.
I got it unlocked I had to change the folder name,I guess it wouldn't work cause unlock was in the folder name as soon as I changed it and entered the path it went though.. so I'm guessing that was the problem.
shooter_454 said:
Thanks for your reply also.
I got it unlocked I had to change the folder name,I guess it wouldn't work cause unlock was in the folder name as soon as I changed it and entered the path it went though.. so I'm guessing that was the problem.
Click to expand...
Click to collapse
Glad you got it figured out man!
Use fastboot for kernels, lol, I wish I had and almost bricked my phone.
I'm trying to RUU back to stock DNA on Verizon but it keeps telling me there is an error
it tells me "ERROR [158]: Image error"
am i missing something?
kreep22 said:
I'm trying to RUU back to stock DNA on Verizon but it keeps telling me there is an error
it tells me "ERROR [158]: Image error"
am i missing something?
Click to expand...
Click to collapse
Did you lock the phone again first, if you had previously unlocked/rooted?
GreginNH said:
Did you lock the phone again first, if you had previously unlocked/rooted?
Click to expand...
Click to collapse
yes, it's showing relocked status and it wont let me do anything just takes me to the bootloader no matter what i do
kreep22 said:
yes, it's showing relocked status and it wont let me do anything just takes me to the bootloader no matter what i do
Click to expand...
Click to collapse
Right Click and Run as Admin try that... make sure you are in fastboot usb mode as well or redownload the RUU maybe you got a bad DL
.torrented said:
Right Click and Run as Admin try that... make sure you are in fastboot usb mode as well or redownload the RUU maybe you got a bad DL
Click to expand...
Click to collapse
I tried to Run as Admin and no luck tells me the same error message, i've done it before with the same ruu that i am trying with now but idk what is going on, am i bricked?
kreep22 said:
I tried to Run as Admin and no luck tells me the same error message, i've done it before with the same ruu that i am trying with now but idk what is going on, am i bricked?
Click to expand...
Click to collapse
does your phone boot to android at all? or recovery
.torrented said:
does your phone boot to android at all? or recovery
Click to expand...
Click to collapse
I got it wprking, just re unlocked and rom came back on. Thank u
Sent from my HTC6435LVW using xda app-developers app
kreep22 said:
I got it wprking, just re unlocked and rom came back on. Thank u
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
How did you do it can you please explain?
Tried going back to stock settings
Relocked m errory phone s- off still the ruu wizard keeps giving me error 158? Flashed hboot with no luck. how do I unlock again like I said still s-off
wondering how u unlocked again
chris1569810 said:
How did you do it can you please explain?
Click to expand...
Click to collapse
I'm in the same situation
You flashed the stock hboot with no problems? Which hboot?
Help! I have a similar problem
GreginNH said:
Did you lock the phone again first, if you had previously unlocked/rooted?
Click to expand...
Click to collapse
I used moonshine S-OFF to root my DNA. I dont know how to get back to the stock locked hboot. and i keep getting that error 158.
any recommendations?
madc321 said:
I used moonshine S-OFF to root my DNA. I dont know how to get back to the stock locked hboot. and i keep getting that error 158.
any recommendations?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2293919
finanandroid said:
http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
Thanks but I tried that with no luck. I was able to flash viper venom though. no idea why the bamf rom did not work.
Solution?
So what ended up being the solution for the Error 158 and being stuck at Fastboot? I can't seem to find one that will work. Check my thread in Q & A: http://forum.xda-developers.com/showthread.php?t=2649525
Before running ruu u should boot into fastboot and make u see fastboot usb then start ruu, the error is because ur device can't boot into bootloader to finish with ruu
Sent from my HTC6435LVW using xda app-developers app
jaymazz13 said:
Before running ruu u should boot into fastboot and make u see fastboot usb then start ruu, the error is because ur device can't boot into bootloader to finish with ruu
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I just spent 20 minutes freaking out. I kept getting the 158 error over and over. I fastboot flashed the locked bootloader file and it said RELOCKED, but still errored out.
I was on the ENG hboot at the time and fastboot flashed the vanilla 3.06 hboot and this time the RUU went through.
Hopefully this will help somebody else out.
sasquatch1 said:
I just spent 20 minutes freaking out. I kept getting the 158 error over and over. I fastboot flashed the locked bootloader file and it said RELOCKED, but still errored out.
I was on the ENG hboot at the time and fastboot flashed the vanilla 3.06 hboot and this time the RUU went through.
Hopefully this will help somebody else out.
Click to expand...
Click to collapse
How can I do this if phone was fully stock before recieving an OTA via Verizon and now wont get past white HTC screen?
I am s-on...I cant flash anything...and RUU keeps failing.
---------- Post added at 04:56 PM ---------- Previous post was at 04:51 PM ----------
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
DuceTheTruth said:
How can I do this if phone was fully stock before recieving an OTA via Verizon and now wont get past white HTC screen?
I am s-on...I cant flash anything...and RUU keeps failing.
---------- Post added at 04:56 PM ---------- Previous post was at 04:51 PM ----------
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
By above post i could understand that your phone is S-On and LOCKED.
If that was the case, How your phone got updated to boot 1.57.0000?
Have you flashed anything (firmware) in fastboot mode?
If yes, You have very less chance to get the phone working unless its JTAGed.
First of all thank you for your reply...
This phone was all stock when I received it in this state...never been rooted ...unlocked or anything....
All I know is that after accepting an OTA update from vzw the phone never booted up fully again...
Now I did try the flashing instructions from .torrented but everything I do fails...
I get "remote 22 loading zip info fail"...
I also get " remote 12 signature verify fail"....
Sent from my SPH-L710 using XDA Free mobile app
---------- Post added at 06:34 PM ---------- Previous post was at 06:19 PM ----------
DuceTheTruth said:
First of all thank you for your reply...
This phone was all stock when I received it in this state...never been rooted ...unlocked or anything....
All I know is that after accepting an OTA update from vzw the phone never booted up fully again...
Now I did try the flashing instructions from .torrented but everything I do fails...
I get "remote 22 loading zip info fail"...
I also get " remote 12 signature verify fail"....
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.073s]
finished. total time: 0.073s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.038s]
finished. total time: 0.039s
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\adb>fastboot flash zip PL83IMG_3.06_Recovery.zip
target reported max download size of 1514139648 bytes
sending 'zip' (11248 KB)...
OKAY [ 1.343s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.451s
C:\adb>fastboot flash zip PL83IMG_1.15_hboot
error: cannot open 'PL83IMG_1.15_hboot'
C:\adb>fastboot flash zip PL83IMG_1.15_hboot.zip
target reported max download size of 1514139648 bytes
sending 'zip' (434 KB)...
OKAY [ 0.202s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.252s
C:\adb>fastboot flash recovery PL83IMG_3.06_Recovery.zip
target reported max download size of 1514139648 bytes
sending 'recovery' (11248 KB)...
OKAY [ 1.364s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.470s
[RUU] Google Edition Conversion. 4.4.2- 1.16.1700.16 -RUU Zip Non-Rooted & Pre-Rooted
This will NOT work on a CDMA HTC One GSM ONLY!
[PSA: People have been reporting not being able to flash back to sense. When investigating this further I found that the system partition on the GPE is about half the size of the sense system partition. (just over a gig compared to like 2.8) This was not the case on the M7
So as of now once you convert, YOU CAN NOT GO BACK TO A SENSE BASED ROM UNTIL A RUU is RELEASED! Rest assured nothing is wrong with the RUU. If you did convert and want to go back you just have to wait for a RUU to be released then you can go back but flashing a sense rom in recovery wont work.
This thread is NOT to support changing your MID, Changing your CID, Rooting or Flashing a custom recovery. If you need to learn how to do any of those do NOT use this thread to post in. Post in the respective dedicated threads to complete these processes. This thread is ONLY to support flashing the RUU. Nothing more, nothing less.
This is NOT a general 4.4.2 discussion thread.
Furthermore, if you need any more detailed instructions than what's stated in this post then you really shouldn't be doing this to your device. If you need a "video" or ask for "step by step" instructions you will NOT get anything more than what's in this post (at least from me). There is no easier way to do this process, there is no easier way to explain it. If you read the post and still don't understand what to do then I advise you to leave your phone alone... Read and then read some more until you understand everything.. WE WILL NOT SPOON FEED YOU IN THIS THREAD!
This procedure is not easy and is not really noob friendly, well flashing the RUU is not really difficult but it's the prerequisites that are more complex/risky. If the instructions aren't clear enough for you or you require further hand holding then I'm sure most of us would advise you stay away from the process.
Also, please do not PM me for support. PM's will not be answered. Post it in the thread. It helps other's having the same issue find a solution. If it's over PM it only benefits you and not everyone else
Prerequisites
S-Off,
ADB knowledge
Fastboot knowledge
Instructions:
First you are going to have to have s-off on your device. Thread for S-off (and support for S-off) http://forum.xda-developers.com/showthread.php?t=2708464
Full Conversion 4.4.2 RUU ZIP containing System, Boot and all Firmware 1.16.1700.16
This will wipe EVERYTHING INCLUDING YOUR INTERNAL SD CARD!!!! PLEASE REMOVE YOUR EXTERNAL CARD IF YOU HAVE ONE so make sure you back up the contents before running this, but you'll end up with a factory-fresh GE. Of course, there's still no support, warranty or responsibility implied or otherwise.
The 4.4.2 RUU Zip supports the following MIDs and CIDs if your MID or CID is not in this list you will have to modify the android-info.txt file in the zip to match your MID/CID
modelid: 0P6B12000
modelid: 0P6B17000
modelid: 0P6B*****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
(please note.. If your model id or cid is not supported you can open up the android-info.txt file that's in the zip and replace one of the model ids or cids listed to match yours.)
Code:
adb reboot bootloader
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip/CODE]
you will the following message:
[CODE]FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Just run the same command again:
Code:
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip
Code:
fastboot reboot
Stock Non-Rooted 4.4.2-1.16.1700.16 RUU Zip: http://www.androidfilehost.com/?fid=23329332407584639
Mirror:
MD5: eb56e73af883aa2d175032c7dc527dc8
Stock Rooted + busy box pre-installed 4.4.2-1.16.1700.16 RUU Zip: http://www.androidfilehost.com/?fid=23329332407584640
Mirror:
MD5: b380f51a4a2b0e2a83c4d7bd92075ce5
If you want to flash a custom recovery you will have to flash back to stock recovery to get the OTA's
You can get the GPE Stock recovery here
Special thanks to @pasker17 for allowing me to walk him through pulling all the partitions!!
@beaups and crew for S-off
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, or flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. This process is not for the faint of heart so I am not responsible.... It was the other guy... I swear....
reserved
this one too
Worked like a charm the first time thanks! One thing to note is my dot view case works fine with calls the voice gesture down is missing though I'm not missing it. I mention this as some reviews say the gpe edition can't answer calls with the case.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Pre-rooted + busybox RUU added to op
ill probably hold off on fully converting for now but what is the advantage of doing so VS just flashing a GPE rom?
fix-this! said:
ill probably hold off on fully converting for now but what is the advantage of doing so VS just flashing a GPE rom?
Click to expand...
Click to collapse
OTA updates.
Sent from my HTC One_M8 using Tapatalk
BONED
had to change name
Thank you. Confirmed works on Rogers M8. Thank you again. Would be nice if HTC can release the photo edit app on play store in the future.... and maybe the burst mode for the camera
Questions
First off I wanted to say thanks!
But I'm having a few issues getting the IR blaster to work. The app detects it but when I put a camera up to the button I'm not seeing any flashing.
Also how to we use the HTC photo edit?
Thanks again!
lordpelvis said:
First off I wanted to say thanks!
But I'm having a few issues getting the IR blaster to work. The app detects it but when I put a camera up to the button I'm not seeing any flashing.
Also how to we use the HTC photo edit?
Thanks again!
Click to expand...
Click to collapse
What IR app are you using? I'm using Smart Remote and it is working perfectly. As for the camera, sorry, but we lost pretty much all functionality with the GPe camera.
I've tried power IR and a few others. Have a link to the remote you're using?
Sent from my HTC One_M8 using xda app-developers app
---------- Post added at 11:01 AM ---------- Previous post was at 10:54 AM ----------
I actually bought the app and nothing happens.
Sent from my HTC One_M8 using xda app-developers app
You can download the HTC TV app from the playstore.. Again.. To remind you guys.. That type of discussion is off topic and does not belong in the thread.
Sent from my HTC One_M8 using Tapatalk
I did want to mention that when trying to flash the RUU, I did get a second "error" after the listed first one. I've attached the code from ADB below.
Code:
Daniels-iMac:~ Daniel$ fastboot flash zip /Users/Daniel/Downloads/RUU-HTC_One_M8_GE-1.16.1700.16.zip
target reported max download size of 1830715392 bytes
sending 'zip' (510598 KB)...
OKAY [ 20.133s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=9
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,76
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,6
(bootloader) [RUU]UZ,adsp,13
(bootloader) [RUU]UZ,adsp,21
(bootloader) [RUU]UZ,adsp,27
(bootloader) [RUU]UZ,adsp,34
(bootloader) [RUU]UZ,adsp,41
(bootloader) [RUU]UZ,adsp,48
(bootloader) [RUU]UZ,adsp,54
(bootloader) [RUU]UZ,adsp,61
(bootloader) [RUU]UZ,adsp,68
(bootloader) [RUU]UZ,adsp,74
(bootloader) [RUU]UZ,adsp,81
(bootloader) [RUU]UZ,adsp,88
(bootloader) [RUU]UZ,adsp,94
(bootloader) [RUU]UZ,adsp,99
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,26
(bootloader) [RUU]WP,adsp,53
(bootloader) [RUU]WP,adsp,79
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) current_image_number=1
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,6
(bootloader) [RUU]UZ,boot,12
(bootloader) [RUU]UZ,boot,18
(bootloader) [RUU]UZ,boot,25
(bootloader) [RUU]UZ,boot,33
(bootloader) [RUU]UZ,boot,43
(bootloader) [RUU]UZ,boot,55
(bootloader) [RUU]UZ,boot,62
(bootloader) [RUU]UZ,boot,68
(bootloader) [RUU]UZ,boot,74
(bootloader) [RUU]UZ,boot,80
(bootloader) [RUU]UZ,boot,87
(bootloader) [RUU]UZ,boot,93
(bootloader) [RUU]UZ,boot,99
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) current_image_number=2
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,8
(bootloader) [RUU]UZ,recovery,16
(bootloader) [RUU]UZ,recovery,22
(bootloader) [RUU]UZ,recovery,29
(bootloader) [RUU]UZ,recovery,37
(bootloader) [RUU]UZ,recovery,45
(bootloader) [RUU]UZ,recovery,51
(bootloader) [RUU]UZ,recovery,60
(bootloader) [RUU]UZ,recovery,68
(bootloader) [RUU]UZ,recovery,76
(bootloader) [RUU]UZ,recovery,85
(bootloader) [RUU]UZ,recovery,93
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,66
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=3
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) current_image_number=4
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,20
(bootloader) [RUU]UZ,sp1,41
(bootloader) [RUU]UZ,sp1,77
(bootloader) [RUU]UZ,sp1,97
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
(bootloader) ...... Successful
(bootloader) current_image_number=5
(bootloader) start image[system] unzipping & flushing...
(bootloader) [RUU]UZ,system,0
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 40.913s
For those who may think something is wrong, it may not be the case. Although I received the error above, my phone continued to go through the process of flashing the RUU. I was patient and let it finish. The last step running the "fastboot reboot" command will not work as I was at a black screen that looked like fastboot except I had none of the usual fastboot options (hboot, etc.), just the listing of the hardware info (model, CID, etc.). I held the power button for several seconds until the phone shut off completely. Turned it back on and it booted up fine. Ran through the setup process and everything seems to be working fine. I will update if my phone explodes or anything else I notice is wrong, but otherwise it's been great so far. Thanks graffixnyc!
Thanks for this. I did this and want to know what app do you recommend for visual voicemail? The original app was great. Anyway I can download the one that came with the phone? Thanks
xoulu said:
Thanks for this. I did this and want to know what app do you recommend for visual voicemail? The original app was great. Anyway I can download the one that came with the phone? Thanks
Click to expand...
Click to collapse
Use Google voice for vvm. It will even text you a transcription of the phone message.
Sent from my HTC One_M8 using Tapatalk
Hey guys, I'm going to close this thread and ask you guys that you use the main thread in the m8 section (the RUU is the same) It's just easier for me to maintain one thread instead of 3 so head on over to the main thread: http://forum.xda-developers.com/showthread.php?t=2708589
Hey guys,i hope someone can help me fix my fone..
I need to get RUU for my fone type.
I tried all RUU who are posted in htcdev.com - noone works.
***UNLOCKED***
BLISS PVT SHIP S-ON RL
HBOOT - 1.33.0000
RADIO - 3831.17.00.17_M
eMMC - boot
Apr 13 2012,10:10:20
Why don't you let us know what problems you are having, what region the Rhyme is from (Europe, Asia,...?), what RUUs you've tried exactly, and what part of the RUU is not working (error codes)?
The more info you give the better we can help.
es0tericcha0s said:
Why don't you let us know what problems you are having, what region the Rhyme is from (Europe, Asia,...?), what RUUs you've tried exactly, and what part of the RUU is not working (error codes)?
The more info you give the better we can help.
Click to expand...
Click to collapse
The problem is he stuck on switching on,
I have tryed the orginal RUU`s from htcdev.com ,but noone works.
I thing this rhyme is from Asia,becouse it have only 2 languages - Chaineese and English.
RUU ERROR - ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the corrent ROM Update Utility and try again.
Have you relocked the bootloader before running the RUU?
fastboot oem lock
I believe.
es0tericcha0s said:
Have you relocked the bootloader before running the RUU?
fastboot oem lock
I believe.
Click to expand...
Click to collapse
But to do this ,i need to enable USB Debugging ,but i cannt.
Is any automatic debugging for Rhyme?
That is not correct. You need to relock the bootloader while in the bootloader/fastboot mode so adb doesn't work there anyway.
es0tericcha0s said:
That is not correct. You need to relock the bootloader while in the bootloader/fastboot mode so adb doesn't work there anyway.
Click to expand...
Click to collapse
*** RELOCKED ***
BLISS PVT SHIP S-ON RL
HBOOT- 1.33.0000
RADIO- 3831.17.00.17_M
eMMC-boot
Apr 13 2012,10:10:20
I have RELOCKED it,but still cannt do anithing with RUU
Now is error 131
Error 131 should be because you are trying to use an HTC Rhyme RUU that is for a different region. If you don't have fastboot set up, you should (get it here: http://forum.xda-developers.com/showthread.php?t=2317790). Once you have that set up, open a CMD prompt and change directories to the folder where your fastboot files are then boot to the bootloader again and plug it in. Then do this:
fastboot devices
(this should pull up a string of letters+numbers, if it does not, you are either in the wrong folder or drivers are not correct)
if you get something with fastboot devices then do this:
fastboot getvar all
and post that here. This will give us ALL the details about what is on the phone and where it is from, etc.
Also, post up the version you are trying, for a reference point.
es0tericcha0s said:
Error 131 should be because you are trying to use an HTC Rhyme RUU that is for a different region. If you don't have fastboot set up, you should (get it here: http://forum.xda-developers.com/showthread.php?t=2317790). Once you have that set up, open a CMD prompt and change directories to the folder where your fastboot files are then boot to the bootloader again and plug it in. Then do this:
fastboot devices
(this should pull up a string of letters+numbers, if it does not, you are either in the wrong folder or drivers are not correct)
if you get something with fastboot devices then do this:
fastboot getvar all
and post that here. This will give us ALL the details about what is on the phone and where it is from, etc.
Also, post up the version you are trying, for a reference point.
Click to expand...
Click to collapse
This is what i got.
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.33.0000
(bootloader) version-baseband: 3831.17.00.17_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.708.3
(bootloader) serialno: SH34CVV00951
(bootloader) imei: 358071047342786
(bootloader) product: bliss
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PI4610000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 456a753a
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
How to know ,whatregion it is?
Mby u can now recommend some RUU?
Try this one:
http://dl4.htc.com/RomCode/Source_and_Binaries/bliss-ics-crc-3.0.16-5423ef1.zip
Hi
My fone htc one m8 es rooted and i want to go back my stock plz halp
I try rru img fil but error 130 bootloader also lock and (s-on )
Error 130 means you aren't using the right RUU. You have to use one that is specific to your carrier or region and must be the same version or newer. You can not downgrade while S-On.
htc on m8
I am use version4.28.502.1 dame error come
How i unroot my htc one m8 mey region asia
4.28.502.1 is the RUU you are trying to use? That appears to be one for ATT, which is an American cellular service provider. You should be able to find something here http://forum.xda-developers.com/showthread.php?t=2701376
htc on m8 how unroot and delete supersu
how unroot and delete supersu i am not able to find my htc one m8 arabic version
I want to restore orignal stock 4.4.4 kitkat
I can't guess which update you need. Since you don't know, the best way is to boot to the bootloader and use fastboot (if you don't have it, Google : Minimal ADB and Fastboot). Once in bootloader use the terminal or command prompt to enter : fastboot getvar all. Copy and paste results here and leave out your IMEI and serial number for security's sake.
es0tericcha0s said:
I can't guess which update you need. Since you don't know, the best way is to boot to the bootloader and use fastboot (if you don't have it, Google : Minimal ADB and Fastboot). Once in bootloader use the terminal or command prompt to enter : fastboot getvar all. Copy and paste results here and leave out your IMEI and serial number for security's sake.
Click to expand...
Click to collapse
my htc datail
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B67000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 56f9ae32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
Like I said in my last post, you should not post your IMEI / serial number.
I believe this RUU should work and is Lollipop 5.0.2 https://www.androidfilehost.com/?fid=95916177934518148
You must relock your bootloader since you are S-On. In bootloader, use fastboot command: fastboot oem lock
How to s-off and plz tel me how to install ruu zip file
Thanks
htc on m8
How to s-off and plz tel me how to install ruu zip file
Thanks
S-Off might not be the best idea for someone who isn't comfortable with how to search for information on XDA or Google. Double click the RUU exe and follow directions. S-Off can be achieved with Sunshine. It is a paid app. There are no free solutions anymore.
htc on m8
Dear
This on zip file not img
Did you try extracting it? It's probably compressed for easier uploading / downloading.
htc on m8
Yes i try to extrac
Ok can i use with adb fastboot comnd to install ?
I will try to flash but not load any ruu
I flash with fastboot error come
Target reported max download size 1826418688 byets
Error cannot load 0P6BIMG.zip no error
Thanks
htc one m8
i try but fastboot come like this
C:\Users\TOSHIBA\Desktop\adb fastboot-s.off\adb fastboot>fastboot flash zip 0P6B
IMG.zip
target reported max download size of 1826418688 bytes
error: cannot load '0P6BIMG.zip': No error
syedfawaf said:
i try but fastboot come like this
C:\Users\TOSHIBA\Desktop\adb fastboot-s.off\adb fastboot>fastboot flash zip 0P6B
IMG.zip
target reported max download size of 1826418688 bytes
error: cannot load '0P6BIMG.zip': No error
Click to expand...
Click to collapse
Sorry, didn't realize it was actually the zip as most RUUs are exes. To load the RUU zips you have to boot to the special fastboot screen by using the command:
fastboot oem rebootRUU
then flash the rom zip like you were trying. It might fail after the bootloader, which is common, you just need to immediately redo the command and it should go through.
no dear same error
Is the zip in the same folder where you are running the commands?
Yas zip is same folder