HTC Rhyme s510b correct RUU - Android Q&A, Help & Troubleshooting

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

Related

Nothing unlocked about new Rogers HTC EVO 3D Bootloader

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 (Back to stock ROM)

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!

[Q] Soft Brick -- Help me fix this the easy way please!

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.

Boootloop and/or Stuck at Logo

Hi,
For no obvious reasons my phone went to bootloop yesterday night and I've been trying to fix it by different methods suggested in forums. But my phone does either of two things after changes/updates I make:
(1) Bootloop or (2) startup and stuck at HTC One beats audio screen
I have TWRP 2.8.0 installed. I can login to recovery.
Below is the phone getvar info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34SW906267
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
It's an ATT HTC One M7.
Problems, at this moment:
(1) Get get adb to connect to device
(2) I have twrp backups on my computer but don't know how to transfer them onto phone so that I can try restore command - backup files are not in zip format but a folder with files in it.
(3) when I was able to sideload a rom, I did flash ARHD 82.0 but that didn;t help.
PLEASE HELP !!:crying:
st167 said:
Hi,
For no obvious reasons my phone went to bootloop yesterday night and I've been trying to fix it by different methods suggested in forums. But my phone does either of two things after changes/updates I make:
(1) Bootloop or (2) startup and stuck at HTC One beats audio screen
I have TWRP 2.8.0 installed. I can login to recovery.
Below is the phone getvar info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
It's an ATT HTC One M7.
Problems, at this moment:
(1) Get get adb to connect to device
(2) I have twrp backups on my computer but don't know how to transfer them onto phone so that I can try restore command - backup files are not in zip format but a folder with files in it.
(3) when I was able to sideload a rom, I did flash ARHD 82.0 but that didn;t help.
PLEASE HELP !!:crying:
Click to expand...
Click to collapse
To install ARHD you should use TWRP 2.6.3.3 :good:
Or if you want to use your backup you can push it to the phone storage with adb, while in TWRP recovery.
Put the backup folder inside your fastboot folder on your pc and rename it something easy to type "nandroid" for example. Boot the device to TWRP recovery Home Screen. Connect usb cable. Then in the command window type
Code:
adb push nandroid /sdcard/TWRP/BACKUPS/DEVICESERIALNO./nandroid
Replace "DEVICESERIALNO." with your phone's Serial number in capitals
Wait for the push to complete, the command window may appear unresponsive at first just be patient when it's done restore the nandroid with TWRP
P.s you should edit your post and delete your Serial number. You don't want it displayed on the forums. FYI that's the serial number you need to use in the push command.
If you found my posts helpful, no need to say thanks. There's a button for that
Thank you again (already pressed thanks button )...I'll give it a try once I get home.
st167 said:
Thank you again (already pressed thanks button )...I'll give it a try once I get home.
Click to expand...
Click to collapse
Your welcome let me know how it goes, or if you need more help :good:
If you found my posts helpful, no need to say thanks. There's a button for that
So I was able to push backup to TWRP and restore. Yay!
But now the problem is I don't have any cell services....phone identity section shows no imei, no baseband, etc. I can see all these info from fastboot getvar. Any idea?
Oh and I keep getting error saying com.htc.dialer is not responding.
st167 said:
So I was able to push backup to TWRP and restore. Yay!
But now the problem is I don't have any cell services....phone identity section shows no imei, no baseband, etc. I can see all these info from fastboot getvar. Any idea?
Oh and I keep getting error saying com.htc.dialer is not responding.
Click to expand...
Click to collapse
Sorry to tell you that doesn't sound good. Unknown imei and Baseband is normally a hardware failure.
You can try to flash a firmware package or even better if possible an ruu but it rarely solves the issue. It's most likely the Antenna pin connector.
Do you have warranty on the device if so the best option is to return to Stock and send it for repair. :good:
If you found my posts helpful, no need to say thanks. There's a button for that
Danny201281 said:
Sorry to tell you that doesn't sound good. Unknown imei and Baseband is normally a hardware failure.
You can try to flash a firmware package or even better if possible an ruu but it rarely solves the issue. It's most likely the Antenna pin connector.
Do you have warranty on the device if so the best option is to return to Stock and send it for repair. :good:
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
I flashed the att firmware and then flashed rom again. Everything worked fine Phone started normally and I was able to make calls.
But my happiness ended soon...I tried to restart the phone after it finished downloading and updating apps and it died
Now phone doesn't power on, no led indicator or nothing when I plug the charger in. I tried diff combinations of power and vol button but no luck. So now I have an expensive paper-weight :crying:
Phone is out of warranty as it has been more than 365 days since purchase.
But thanks for your help.
WHen my phone did similar behavior I held down power + vol up (It will eventually vibrate and show the white HTC splash screen) THen continued to keep the buttons held down for almost 10 seconds, it rebooted itself again and finally allowed me into HBOOT and from there I was able to choose "Recovery" and boot into TWRP
If that doenst work, try the same with Power + Vol down. Or maybe it was Power + Home + Vol up, or Power + home + Vol down. Sorry, I dont exactly remember but one of those 4 combinations will get you into HBOOT or into recovery so that you can flash a new Rom
st167 said:
I flashed the att firmware and then flashed rom again. Everything worked fine Phone started normally and I was able to make calls.
But my happiness ended soon...I tried to restart the phone after it finished downloading and updating apps and it died
Now phone doesn't power on, no led indicator or nothing when I plug the charger in. I tried diff combinations of power and vol button but no luck. So now I have an expensive paper-weight :crying:
Phone is out of warranty as it has been more than 365 days since purchase.
But thanks for your help.
Click to expand...
Click to collapse
It's also worth checking on your warranty most come with 2years

HTC one m8

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

Categories

Resources