Related
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-
Revert to 2.47
Hi
I have hboot 2.49 want to revert back to 2.47 and plus want to convert it to International version i want to use 407 roms
Details
CID-1111111
HBOOT-2.49.0000
Radio-4T.24.3218.09
OS-2.61.708.1
or can someone provide me latest 2.49 with OS 401
Thanks
Hi
I successfully flashed rom RUU.exe BrightstarUS WWE 1.23.1540.1 (flyhalf's)
and when i got the OTA for 4.4.2 it says my mobile software been modified and cannot update
I used manually to update through fastboot oem rebootRUU
OTA_T6_UL_K44_SENSE55_MR_BrightstarUS_WWE_2.61.1540.1-1.23.1540.1_release
please help me if I did something wrong
Try Change back go stock cid
Sent from my HTC One max using xda premium
I don't really know what is my original CID
HTC___116
something like this not sure
i have seen a list somewhere maybe i will recognize it
EDIT: Actually original software was HK region changed it to WWE US brightstar
I found the CID is HTC__622
i tried to flash it with Brightstar US CID BS_US001
is not working
with original CID HTC__622
is not working
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
I dont know whats wrong,
please help
The Don Jay said:
I found the CID is HTC__622
i tried to flash it with Brightstar US CID BS_US001
is not working
with original CID HTC__622
is not working
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
I dont know whats wrong,
please help
Click to expand...
Click to collapse
Can you check what is your MID ? is it 0P3P50000?
Also can you post the exact error message or a photo?
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.46.0000
(bootloader) version-baseband: 4T.21.3218.01
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.19.708.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA3ASWG05176
(bootloader) imei: 357311050403377
(bootloader) meid: 00000000000000
(bootloader) product: t6ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: 0P3P52000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 4153mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6cad6811
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.121s
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 20.643s
i have succeeded to flash
0P3PIMG_T6_UL_JB43_SENSE55_hTC_Asia_HK_1.19.708.2_Radio_4T.21.3218.01_10.15.1718.01_release_337043_signed_Hboot_2_4
my boot showing 1.19.708.2 but software version is 1.23.1540.1
what is missing what is the right thing to do ?
please help
Hi
I have HTC One max HK Asia Version HTC__622 i tried to flash this rom in CMW, TWP and stock recovery but not taking
with locked and unlocked bootloader
0P3PIMG_T6_UL_JB43_SENSE55_hTC_Asia_HK_1.19.708.2_ Radio_4T.21.3218.01_10.15.1718.01_release_337043_s igned_2_4.zip
tried wiping data, system and dalvik wipe but still giving me an error file is too large
is there anything i did wrong ?
please help im stuck
looking at the picture of you phone diplaying hboot, you cid is 111111111.
try changing back to a good 1
Hi
Problem solved thanks to Chinese website
changed the CID to the original which is HTC__622
Downloaded and copied and renamed the file
0P3PIMG_T6_UL_JB43_SENSE55_hTC_Asia_HK_1.19.708.2_ Radio_4T.21.3218.01_10.15.1718.01_release_337043_s igned_2_4.zip
to
0P3PIMG.zip and located to external SD card
Locked or Relocked the Bootloader .. better locked to get the fingerprint working (this can be done with scotty's method)
got to bootloader mode and press power button to enter bootloader mode then the file will update automatically without any command
Done
source chinese website which i cant post yet
your help
The Don Jay said:
Hi
Problem solved thanks to Chinese website
changed the CID to the original which is HTC__622
Downloaded and copied and renamed the file
0P3PIMG_T6_UL_JB43_SENSE55_hTC_Asia_HK_1.19.708.2_ Radio_4T.21.3218.01_10.15.1718.01_release_337043_s igned_2_4.zip
to
0P3PIMG.zip and located to external SD card
Locked or Relocked the Bootloader .. better locked to get the fingerprint working (this can be done with scotty's method)
got to bootloader mode and press power button to enter bootloader mode then the file will update automatically without any command
Done
source chinese website which i cant post yet
Click to expand...
Click to collapse
I need to revert back my hboot 2.49 to 2.47 . I would appreciate your help on how did your do it
solved too on me
The Don Jay said:
Hi
Problem solved...
Click to expand...
Click to collapse
Thanks!
BadrSaleh said:
I need to revert back my hboot 2.49 to 2.47 . I would appreciate your help on how did your do it
Click to expand...
Click to collapse
you need soff using firewater.
then you can flash any hboot. but be careful to use the correct one!
[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
S-Off
Unlocked bootloader
Had HD Rev 62 on it, but wiped EVERYTHING (data, cache, etc etc) in TWRP
Updated TWRP to 2.8.
Fastboot working, adb is not.
Fastboot sees and communicated with device just fine.
ADB does not list any devices, or errors. Just returns blank beneath List of connected Devices.
Cannot boot into anything since no OS is present. HD Rev latest version gets errors about "android-info.txt" and android-product.txt.
"error: update package has no android info.txt or android product.txt"
I don't care what OS is loaded on it because I am sending it to my mother. What is the fastest way to get it up and running again? I'm hoping to ignore fixing the ADB drivers on my Windows 8.1 machine (64-bit).
Can I just do a fastboot quick fix? If so, which RUU/Rom/Firmware/whatever. Anything that fastboot update update.zip will fix.
Thanks guys!
nik.the said:
S-Off
Unlocked bootloader
Had HD Rev 62 on it, but wiped EVERYTHING (data, cache, etc etc) in TWRP
Updated TWRP to 2.8.
Fastboot working, adb is not.
Fastboot sees and communicated with device just fine.
ADB does not list any devices, or errors. Just returns blank beneath List of connected Devices.
Cannot boot into anything since no OS is present. HD Rev latest version gets errors about "android-info.txt" and android-product.txt.
"error: update package has no android info.txt or android product.txt"
I don't care what OS is loaded on it because I am sending it to my mother. What is the fastest way to get it up and running again? I'm hoping to ignore fixing the ADB drivers on my Windows 8.1 machine (64-bit).
Can I just do a fastboot quick fix? If so, which RUU/Rom/Firmware/whatever. Anything that fastboot update update.zip will fix.
Thanks guys!
Click to expand...
Click to collapse
Post a fastboot getvar all (except for imei and serialno). If you are in bootloader/FASTBOOT USB and run the command adb devices it will not work. ADB works in OS if USB Debugging is enabled or in recovery.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34CW907053
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXX
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks @majmoz!
nik.the said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: removed
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXX
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: 11111111 change to T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks @majmoz!
Click to expand...
Click to collapse
This is the latest RUU 6.10.531.9 it will put you back at stock. Prior to running this, I would change the CID back to T-MOB010, I have had issues running TMO RUUs with SuperCID.
majmoz said:
This is the latest RUU 6.10.531.9 it will put you back at stock. Prior to running this, I would change the CID back to T-MOB010, I have had issues running TMO RUUs with SuperCID.
Click to expand...
Click to collapse
Which commands would I use to get this running? From bootloader/fastboot usb? Thanks again for the help @majmoz
nik.the said:
Which commands would I use to get this running? From bootloader/fastboot usb? Thanks again for the help @majmoz
Click to expand...
Click to collapse
Just follow the instructions in the Post. RUU.exe are run from Windows. Place the downloaded file in your fastboot/adb folder and double click it. Follow the on-screen instructions.
majmoz said:
Just follow the instructions in the Post. RUU.exe are run from Windows. Place the downloaded file in your fastboot/adb folder and double click it. Follow the on-screen instructions.
Click to expand...
Click to collapse
Nothing happens when I run the ruu. I get through to the agreement, accept, and then it disappears. Also, in the Sync manager, it's not showing my phone. I'm guessing this is a windows 8.1 problem?
nik.the said:
Nothing happens when I run the ruu. I get through to the agreement, accept, and then it disappears. Also, in the Sync manager, it's not showing my phone. I'm guessing this is a windows 8.1 problem?
Click to expand...
Click to collapse
Give this procedure a try!
Change USB ports (USB 2 is preferred) and cables if available
Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
Make sure you leave the adb and fastboot that you downloaded.
Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
A pop-up asking to install HTC Sync will appear, just ignore it or cancel it.
Make sure you set Fast Boot OFF in the Settings < Power on your phone, and USB Debugging enabled
Leave your phone ON and run the RUU set up.
I'm trying these things, but will it work on a phone that can't get to desktop? My phone isn't able to boot into android. It only can get into bootloader, recovery, and fastboot.
nik.the said:
I'm trying these things, but will it work on a phone that can't get to desktop? My phone isn't able to boot into android. It only can get into bootloader, recovery, and fastboot.
Click to expand...
Click to collapse
Put the phone in bootloader/FASTBOOT USB, then run the RUU.
majmoz said:
Give this procedure a try!
Change USB ports (USB 2 is preferred) and cables if available
Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
Make sure you leave the adb and fastboot that you downloaded.
Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
A pop-up asking to install HTC Sync will appear, just ignore it or cancel it.
Make sure you set Fast Boot OFF in the Settings < Power on your phone, and USB Debugging enabled
Leave your phone ON and run the RUU set up.
Click to expand...
Click to collapse
Hmm, frozen at 5% Checking header. RUU problem?
nik.the said:
Hmm, frozen at 5% Checking header. RUU problem?
Click to expand...
Click to collapse
Let's attack this differently. Let's flash the firmware 5.14.531.1 in fastboot. After it is finished, then run the RUU.
Download firmware, rename to fimware.zip and place in your fastboot folder.
Then put phone in bootloader/FASTBOOT USB then, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
majmoz said:
Let's attack this differently. Let's flash the firmware 5.14.531.1 in fastboot. After it is finished, then run the RUU.
Click to expand...
Click to collapse
It worked, then it restarted into QHSUSB_DLOAD. Hard bricked.
Any suggestions?
EDIT: Apparently Dexter's method can fix this, but I need the "appropriate" packages whatever those are :\.
nik.the said:
It worked, then it restarted into QHSUSB_DLOAD. Hard bricked.
Any suggestions?
EDIT: Apparently Dexter's method can fix this, but I need the "appropriate" packages whatever those are :\.
Click to expand...
Click to collapse
Here is his post and if you scroll down to Post #3 you will find the download.
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