Hello.
Can anyone help me? I can't get in my HTC10.
On the boot, it asked for a password to encrypt, but every password is wrong.
Maybe because the system isn't enabled with usb debugging.
Anyone who has an answer?
The phone is
*** RELOCKED ***
*** FUSED ***
htc_pmeuhl PVT S_ON
LK-1.0.0.0000
[email protected]
OpenDSP-v23.0.8996.00007_1028
OS-3.16.401.2
i faced the same issue. I searched a lot including erase data in twrp but nothing helped. so i reverted back to my stock oreo rom.
if you wana atleast do the same and be able to use the phone i suggest you flash your stock rom again. in order to do that can you please go into fastboot mode again (vol down while holding power) and then execute the command fastboot getvar all and get back here with the output (please delete IMEI/Serial number from the output)
Related
When running the RUU I encounter an error 155.
After unplugging the data cable:
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.08.0099
MICROP-0451
RADIO-7.53.39.03M
Nov 28 2011, 19:09:21
RUU
Security fail!
Update fail!
The bootloader is unlocked via HTCDEV
The phone is rooted. CWM installed and reinstalled via rommanager
I assume that:
fastboot oem lock
might work to fix the security fail.
Can anyone give me an advice on howto proceed?
After removing battery and reinserting battery, the phone boots normally.
Regards,
Ruud
PS: I managed to collect rom.zip from temporary directory
rkloost said:
When running the RUU I encounter an error 155.
After unplugging the data cable:
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.08.0099
MICROP-0451
RADIO-7.53.39.03M
Nov 28 2011, 19:09:21
RUU
Security fail!
Update fail!
The bootloader is unlocked via HTCDEV
The phone is rooted. CWM installed and reinstalled via rommanager
I assume that:
fastboot oem lock
might work to fix the security fail.
Can anyone give me an advice on howto proceed?
After removing battery and reinserting battery, the phone boots normally.
Regards,
Ruud
PS: I managed to collect rom.zip from temporary directory
Click to expand...
Click to collapse
Try to relock your boot loader, with command fastboot oem lock.
Then try to run RUU again.
The error 155 seems fixed.
Now I get an error 131
Suppose it is time to rename the rom.zip I recovered to PG76IMG.zip and try to flash it?
so create gold card and reflash the phone?
Regards,
Ruud
Gold card succesfully created, but still no succesfull flash
Main Version is older!
Tried several (4) stock zip's but each time:
*** RELOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.08.0099
MICROP-0451
RADIO-7.53.39.03M
Nov 28 2011, 19:09:21
HBOOT
Main version is older!
Update fail!
The phone is still rooted. CWM installed and reinstalled via rommanager
Can anyone give me an advice on howto proceed?
Is there a way to circumvent Main version is older?
Is it possible to make a dumpfile from misc or so, which can be hex-edited, if so which raw-device I have to cat into an img-file?
Regards,
Ruud
Hope this link will help you http://forum.xda-developers.com/showthread.php?p=21891784
Sent from MARVEL
I had the same problem, with BL unlocked, you do not need gold card.
extract the rom.zip
Copy:
boot.img
system.img
to your computer Android directory (where you have fastboot and adb, you need to download them)
boot WFS into hboot, mark fastboot, hit power button and attach usb cable
now open a command shell in the computer:
fastboot flash boot boot.img <-- will flash kernel and boot
fastboot flash system system.img <-- will flash stock rom
now go to hboot, factory reset and restart
http://forum.xda-developers.com/showthread.php?t=1530864 this will help you just click the last option and you will be able to try again and it will work
Sent from my HTC_A510c using Tapatalk
hi there first here's all you need to know i think?
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.39.0000
CPLD-None
MICROP-None
RADIO-5.1204.163R.30
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW secure boot: enabled
MODEM PATH : OFF
and........ version T-MOB005, main 3.16.110.4
++ i havent been able to find an RUU for this setup anywhere
i managed to flash cm10 and clockworkmod recovery touch but now i cant make it do anything
this i what i have done to try to resolve the problem without success
fastboot lock oem
[okay]
fastboot flash firmware
[okay]
fastboot flash unlocktoken Unlock_code.bin
[okay][/I]
i then go on to flash clockwork recovery and flash cyanogenmod+ su update to it but then it sticks in boot loop
i had a look at the files after mounting usb in clockwork but there is nothing there at all
unfortunately i didnt do a backup at all as i have modded a few phones in the past with success
i have no idea what is going on here as im no dev or writer
please help i dont have another phone at the moment and desperately need it as im a community first responder and rely on being able to call ambulance service
does anyone have any idea how to solve this problem????? [/I]
To be able to run CM10 on the JB hboots you need a modified boot.img
http://db.tt/uDdWaAtH
Flash this one and reboot
Need Help!
First of all sorry for my English.
I have a Desire Z not working, stops at the boot with white logo and htc green.
One mainboard has been changed when in warranty, now... after one year same problem.
I tried many ways but no solutions.
Situation:
Phone is original:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
Radio_26.10.04.03_M
eMMC-boot
apr 11 2011.23:36:27
Gingerbread 2.42.405.3
I can go in fastboot and find the device
I can go ion adb but no device is found (drivers in resources pc are ok, phone recognized)
If I run an RUU.exe phone stops in "avvio su bootloader.........." (starting on bootloader) phone freeze...
Flash some files from fastboot not working....someone tell that I have to be S-off..(true?)
Factory reset: the phone freeze, stops working.
Recovery: the phone reboot and go in black logo with an image phone with reciclyng icon then 7 vobrations and phone turn off.
I try to change to S-OFF by unlocking bootloader vith htcdev procedure but when I try to get the token on fastboot I get the error: (bootloader) [ERR] Command error !!!
Put the phone in the refrigerator for some time....not working
Someone tell that the eMMC can be dead/corrupted....
First to buy a new phone, anyone has other solutions to try to recover the phone to the
Did I do something wrong?
Thanks in advance for your help!!!
Fish_htc said:
Need Help!
First of all sorry for my English.
I have a Desire Z not working, stops at the boot with white logo and htc green.
One mainboard has been changed when in warranty, now... after one year same problem.
I tried many ways but no solutions.
Situation:
Phone is original:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
Radio_26.10.04.03_M
eMMC-boot
apr 11 2011.23:36:27
Gingerbread 2.42.405.3
I can go in fastboot and find the device
I can go ion adb but no device is found (drivers in resources pc are ok, phone recognized)
If I run an RUU.exe phone stops in "avvio su bootloader.........." (starting on bootloader) phone freeze...
Flash some files from fastboot not working....someone tell that I have to be S-off..(true?)
Factory reset: the phone freeze, stops working.
Recovery: the phone reboot and go in black logo with an image phone with reciclyng icon then 7 vobrations and phone turn off.
I try to change to S-OFF by unlocking bootloader vith htcdev procedure but when I try to get the token on fastboot I get the error: (bootloader) [ERR] Command error !!!
Put the phone in the refrigerator for some time....not working
Someone tell that the eMMC can be dead/corrupted....
First to buy a new phone, anyone has other solutions to try to recover the phone to the
Did I do something wrong?
Thanks in advance for your help!!!
Click to expand...
Click to collapse
Im not 100% sure if this will work for you, but this is how i unbricked my DZ.
I can see you already have fastboot running in your pc, good.
Boot into bootloader and go into fastboot there.
Then in cmd use fastboot oem rebootRUU
when your phone is in RUU, type:
fastboot -w
fastboot flash zip PC10IMG.zip it will propably give some error message and says to flush image immediately, so type fastboot flash zip PC10IMG.zip again.
fastboot reboot-bootloader
Now you should have engineering hboot running.
PC10IMG.zip file mentioned can be downloaded here : http://files.virtuousrom.com/vision/misc/PC10IMG.zip
Hi I have m8 16gb and I don't know its variant and I also don't know anything about this android phone.
Can anyone please help me. I don't have any recovery and don't know how to install its firmware again. I tried some of the firmware but my mobile don't pick up the signals.
It Happens when I tried to reset the phone and I accidently wipe the phone because I didn't know this could be possible at all :crying:
In its bootloader it shows
***TAMPERED ***
***UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.19.21331147A1.09G
OPENDSP-v38.2.2-005420M8974.0311
OS-
eMMC-BOOT 2048MB
AUG 4 2014,22:59:39.0
IbrahimSulaiman said:
Hi I have m8 16gb and I don't know its variant and I also don't know anything about this android phone.
Can anyone please help me. I don't have any recovery and don't know how to install its firmware again. I tried some of the firmware but my mobile don't pick up the signals.
It Happens when I tried to reset the phone and I accidently wipe the phone because I didn't know this could be possible at all :crying:
In its bootloader it shows
***TAMPERED ***
***UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.19.21331147A1.09G
OPENDSP-v38.2.2-005420M8974.0311
OS-
eMMC-BOOT 2048MB
AUG 4 2014,22:59:39.0
Click to expand...
Click to collapse
STEP BY STEP INSTRUCTIONS
1. Grab the latest TWRP recovery here and rename the file to 'recovery.img'
2. Boot your phone into bootloader and the first highlighted option is fastboot, use power button to enter fastboot mode.
3. Use google to search for fastboot files and place them into a folder named "Fastboot" .
4. Placed the downloaded TWRP recovery into the fastboot folder.
5. Press right shift key + left mouse and click on open command window.
6. In command window, type this command in: "fastboot flash recovery recovery.img" (without the quotes)
7. Now, download a ROM that your firmware supports and flash it through with your newly installed recovery
8. Enjoy your ROM
5. Press shift & RIGHT mouse button (not left)
Couple basic fumbles that seem all too common on these forums:
1) Why do folks neglect to make a nandroid backup of their stock (or current "known good") seteup before flashing ROMs or doing other mods?
2) Why do some folks insist on wiping partitions when the don't understand the basics of what that partition is, and what the effect will be? If you don't know what it is, don't mess with it, and certainly don't wipe it!
Locked bootloader
S-on
-----
kernel: lk
product: htc_himauhl
version: 1.0
imei: XXXXXXXXXXXXXX
version-main: 3.35.61.14
boot-mode: download
version-baseband: 01.01_U11440792_95.00.51130G_F
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: ORANG001
--
I can only enter bootloader mode or download mode
Cannot enter OS
Cannot enter recovery
cannot enter fastboot oem rebootRUU = bootloops
Cannot obtain fastboot oem get_identifier_token due to not able to access OS to turn appropriate setting on
As i understand the only way to recover is
1)with RUU matching 0PJA10000/ORANG001 [/B] EE/ORANGE 3.35.61.14 or above RUU file as I could then fastboot flash zip RUU.zip
PROBLEM: Cannot find 0PJAIMG_HIMA_UHL_M60_SENSE70_MR_Orange_UK_3.35.61.14_Radio_01.01_U11440792_95.00.51130G_F_release.zip
found on something called gem-firmware but no idea about this site safety
2)S-OFF / unlock bootloader (at local phone shop)
PROBLEM is this even possible with phone state by local phone shops (xtc2clip etc) as I am pretty sure I cannot do it from PC in current phone state
3)Moan to EE/ORANGE UK to say sort this out after all it was caused by an EE upgrade to 6.0.1
Can any one please help me with 1) or 2)
1. Check HTC RUU Flashing Service. They might have the proper RUU.
2. xtc2clip s-offed and BL unlock device in download mode so it's possible.
If you can boot into download mode, I'm sure that you can still unlock the bootloader with the proper key/unlock_code.bin, and then see if you can flash TWRP. Then restore a stock backup which you'll find in Flippy's ReadMe thread.
Thank you for your responses.
I can enter download mode but it's weird, sometimes I have to reboot bootloader then I can enter download mode otherwise I can't.
I do not have the unlock.bin
And I can not get token due to OS setting of unlocking bootloader not allowing.
This leads me to believe that unfortunately I can not solve it alone though i want to try getting
0pjaimg_hima_uhl_m60_sense70_mr_orange_uk_3.35.61.14_radio_01.01_u11440792_95.00.51130g_f_release_470526_signed_hboot.zip
166.5MB
0pjaimg_hima_uhl_m60_sense70_mr_orange_uk_3.35.61.14_radio_01.01_u11440792_95.00.51130g_f_release_472007_combined_signed.zip
2329.8MB
or find 4.19.61.1 hboot as i have RUU but need hboot for it.... 0PJAIMG_HIMA_UHL_N70_SENSE80_MR_Orange_UK_4.19.61.1_Radio_01.01_U114401031_122.01.61213G_F_release_492070_signed_Hboot_2_4.zip
I have
0PJAIMG_HIMA_UHL_N70_SENSE80_MR_Orange_UK_4.19.61.1_Radio_01.01_U114401031_122.01.61213G_F_release_492070_signed_2_4
obviously if i can do it my self i will try...but it looks like I may need to xtc2clip at local phoneshop as my only option IF they can s-off in my curent state
Thank you all again, it is so much appreciated
bothered said:
I do not have the unlock.bin
And I can not get token due to OS setting of unlocking bootloader not allowing.
Click to expand...
Click to collapse
Does this mean that you have no OS installed? (somehow managed to wipe /system with a locked bootloader)
lazyguyMC said:
Does this mean that you have no OS installed? (somehow managed to wipe /system with a locked bootloader)
Click to expand...
Click to collapse
I've never unlocked bootloader on this phone
It happened after upgrading phone I tried to wipe phone to default setting..to be honest all probably my fault..I'm not denying.
It just never boots system, and boots to bootloader instead and can get into download fastboot..I guess
It's some incomplete upgrade that means mismatch so can't even use ruu.. fastboot oem rebootRUU
Just loops then back to bootloader
all guess I know