[Softbricked] HTC ONE MINI TAMPERED LOCKED SECURITY WARNING S-ON - HTC One Mini 2

Hi all, first time in this forum and i hope someone would save me!
I have an HTC One Mini 2
i'm **TAMPERED** **RELOCKED** **SECURITY WARNING** and S-ON
so from hboot and fastboot i can't do anything (also enter in recovery mode)
via usb in hboot i can use fastboot command but not adb command (for that i have to turn on my device which restart in 30 secs so it's very hard)
in that way no fastboot command works always say security warning failure or something like that
as far as i can understand
i have to get it back to stock state but for doing that i need a RUU (fastboot flash is useless and as i sayed i can't do anything with adb in fastboot mode) with the same version of my device (correct?)
in order to do that i have downloaded from htc the mem_ul source to compile with AOSP but on the phone there aren't the proc/
config.gz file and i'm stucked here.
these are the fastboot getvar all instruction.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.19.1017
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.18.401.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***********
(bootloader) imei: *********
(bootloader) imei2: *******
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__001
(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: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.121s
Please help me you would be my hero!
p.s. i'm now using other ruu.exe and changing the rom inside with one of correct version but if not signed it don't allow me to unbrick

ulisse2010 said:
Hi all, first time in this forum and i hope someone would save me!
I have an HTC One Mini 2
i'm **TAMPERED** **RELOCKED** **SECURITY WARNING** and S-ON
so from hboot and fastboot i can't do anything (also enter in recovery mode)
p.s. i'm now using other ruu.exe and changing the rom inside with one of correct version but if not signed it don't allow me to unbrick
Click to expand...
Click to collapse
unlock bootloader using HTC DEV
In fastboot mode install TWRP recovery
In recovery install Recovery Stock.
that should do the trick

it is security warning not allowing me to unlock via htc.dev
in the same way i can't do the other thing you suggested

ulisse2010 said:
it is security warning not allowing me to unlock via htc.dev
in the same way i can't do the other thing you suggested
Click to expand...
Click to collapse
What that means is that your bootloader is locked and you cannot load any software that isn't electronically signed by HTC and specific to your device. The security warning message means that the update you downloaded could have been corrupt (or the OS itself has become corrupt) and the bootloader doesn't recognise it as official HTC software, preventing it from loading.
You have 2 options, you can call HTC and explain what the situation is (if you've not done anything, you'll be covered under warranty), or try to find a matching RUU (Rom Upgrade Utility) and run that from your PC in an effort to restore working software to your phone.
I send my htc to reload stock software and they didnt charge me.

Related

[Q] [Help] Brick help needed [Solved!]

I was trying to flash a ROM earlier today and didn't realize that I was S-on... This threw me into a Boot loop, I thought no problem i'll just wipe and flash a rom that doesn't need s-off. found one and it booted but I got force close errors all over the place. Then I decided I should just bring it back to stock.. which I was somewhat able to using GURU RUU. I have the phone able to boot 100% into the OS but due to a Firmware difference (that he mentions in his video...) My touch screen isn't functioning. My current state is able to boot into stock rom with no error but no touch screen, I can Load bootloader, fastboot, and recover (I have TWRP but CWM works as well). I have fastboot operations but no adb functionality with the one exception that I can run sideload in twrp and cwm. Not sure if it is a pc issue or a phone issue, although I have tried reinstalling drivers both with and with out sync installed. What is my next move? Do i get a OTG USB cable and do an OTA using a mouse? Or do I do something else? wanted to check with you guys before I jump out of the frying pan and into the fire... seems like i have been making one mistake after another on my own accord. thanks for you time and help. Here is a copy of my fastboot getvar all (with my imei censored of course)
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3C5W902089
(bootloader) imei: XXXXXXXXXXXXXXXX
(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: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.109s
Use otg cable +USB mouse to control the phone
sent from my mobile device
update
I have my otg cable and im able to use the usb mouse with it but I am unable to check for the at&t software update... i click on it and it puls up for a second and then goes away... any ideas?
Idea
I read somewhere that I can flash firmware with s-on as long as i re-lock the bootloader and the mid and cid match on the firmware that i flash to it... this would be done in the ruu flash boot? does that sound right and would this allow me to either get the ota update or flash the correct ruu OR would it possible get my adb functionality back to my bootloader so i can s-off and flash a stock ruu?
medicsizzle said:
I was trying to flash a ROM earlier today and didn't realize that I was S-on... This threw me into a Boot loop, I thought no problem i'll just wipe and flash a rom that doesn't need s-off. found one and it booted but I got force close errors all over the place. Then I decided I should just bring it back to stock.. which I was somewhat able to using GURU RUU. I have the phone able to boot 100% into the OS but due to a Firmware difference (that he mentions in his video...) My touch screen isn't functioning. My current state is able to boot into stock rom with no error but no touch screen, I can Load bootloader, fastboot, and recover (I have TWRP but CWM works as well). I have fastboot operations but no adb functionality with the one exception that I can run sideload in twrp and cwm. Not sure if it is a pc issue or a phone issue, although I have tried reinstalling drivers both with and with out sync installed. What is my next move? Do i get a OTG USB cable and do an OTA using a mouse? Or do I do something else? wanted to check with you guys before I jump out of the frying pan and into the fire... seems like i have been making one mistake after another on my own accord. thanks for you time and help. Here is a copy of my fastboot getvar all (with my imei censored of course)
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3C5W902089
(bootloader) imei: XXXXXXXXXXXXXXXX
(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: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.109s
Click to expand...
Click to collapse
You need to flash your touch drivers.
You are in a bit of pickle, as you can't flash anything. Can you run this RUU? http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
SaHiLzZ said:
You are in a bit of pickle, as you can't flash anything. Can you run this RUU? http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Click to expand...
Click to collapse
I can try but I am stuck in S-on would this be an issue? and I can flash from cwm and twrp would a stock nandroid help?
What GURU Reset file did you use? If it is same as nandroid for ATT, then it wont help.
You will need to lock the bootloader and run the RUU file I linked. If RUU doesn't like something on your phone (CID/MID/MAIN-ver mismatch) it will fail before flashing. If it starts flashing you should have a working device at the end.
SaHiLzZ said:
What GURU Reset file did you use? If it is same as nandroid for ATT, then it wont help.
You will need to lock the bootloader and run the RUU file I linked. If RUU doesn't like something on your phone (CID/MID/MAIN-ver mismatch) it will fail before flashing. If it starts flashing you should have a working device at the end.
Click to expand...
Click to collapse
You are the BEST! Thank you so much.. I have been racking my head trying to get this fixed... I am up and running again! My process
1. I had my phone unlocked bootloader, s-on, and twrp recovery
2. booted into trwp, and adb pushed the Guru stock installer
3. installed the zip, selecting to wipe data, no super user, and then I put the stock recovery and radios on
4. rebooted into bootloader and locked my bootloader
5. rebooted phone
6. ran the RUU that you provided me. (Thanks again)
7. phone booted up 100% working!!!!
8. Gave credit where credit was due!

[Q] HTC One Bricked, Relocked, Tampered, S-ON, No operating system

Hello, I have a very big problem with my HTC One M7, it's bricked. It's with Hboot 1.57, tampered , relocked, No recovery, no rom and s-on.
I tried to flash a stock RUU.exe
For flashing it I had to lock the bootloader. So I run the ruu.exe and it deleted all from my phone and stuck on "Cheking header - 5%). When I rebooted the phone it was only with bootloader and everything else was wiped.
I tried to unlock it again but after unlocking i tries to get to recovery. But I don't have recovery. If I try to flash a recovery the phone should be unocked. I'm in a circle.
Please help me with this issue. I want to get back with working phone.
I have read all the threads in the forum about bicked htc one m7 but nothing helped me.
Here's my getvar all
C:\HTC>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **********
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4280mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
zHi5k0 said:
Hello, I have a very big problem with my HTC One M7, it's bricked. It's with Hboot 1.57, tampered , relocked, No recovery, no rom and s-on.
I tried to flash a stock RUU.exe
For flashing it I had to lock the bootloader. So I run the ruu.exe and it deleted all from my phone and stuck on "Cheking header - 5%). When I rebooted the phone it was only with bootloader and everything else was wiped.
I tried to unlock it again but after unlocking i tries to get to recovery. But I don't have recovery. If I try to flash a recovery the phone should be unocked. I'm in a circle.
Please help me with this issue. I want to get back with working phone.
I have read all the threads in the forum about bicked htc one m7 but nothing helped me.
Here's my getvar all
C:\HTC>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **********
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4280mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
unlock the bootloader
flash a custom recovery (twrp 2.6.3.3 preferred)
push a custom rom or a stock reset rom (that match your version) to your phone storage using adb sideload or adb push
install the rom using twrp.
zHi5k0 said:
Hello, I have a very big problem with my HTC One M7, it's bricked. It's with Hboot 1.57, tampered , relocked, No recovery, no rom and s-on.
I tried to flash a stock RUU.exe
For flashing it I had to lock the bootloader. So I run the ruu.exe and it deleted all from my phone and stuck on "Cheking header - 5%). When I rebooted the phone it was only with.....
C:\HTC>fastboot getvar all
(bootloader) version-main:
Click to expand...
Click to collapse
Cheking header - 5% problem is because of version main not found
if you remember exact version then flash same firmware then Run RUU
yatindroid said:
Cheking header - 5% problem is because of version main not found
if you remember exact version then flash same firmware then Run RUU
Click to expand...
Click to collapse
But anyway there is no RUU available that can be used on 1.57 Hboot, S-on and CID HTC__032. So at this point he can only flash a rom using a custom recovery
alray said:
But anyway there is no RUU available that can be used on 1.57 Hboot, S-on and CID HTC__032. So at this point he can only flash a rom using a custom recovery
Click to expand...
Click to collapse
Ohhh Sorry I not noticed that just focused on He was trying flash ruu
The problem is solved Thanks for your help
Help me please
zHi5k0 said:
The problem is solved Thanks for your help
Click to expand...
Click to collapse
Hello, fried. Could you explain or contact me how do you solved this problem? I have the same :crying:
eaeguu said:
Hello, fried. Could you explain or contact me how do you solved this problem? I have the same :crying:
Click to expand...
Click to collapse
Excuse me for the late reply. I'm posting the post that helped me:
Use this recovery
http://techerrata.com/file/twrp2/m7/...2.6.3.3-m7.img
Download and put the file in your fastboot folder rename it recovery.img and use these commands to flash the recovery.
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then select recovery from the bootloader menu to boot TWRP Recovery
Put the stock Rom zip in your fastboot folder and rename it rom.zip
While on the TWRP home screen connect your usb cable. In the command window type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push is complete (Several Minutes) When its done Install the Rom with TWRP recovery.
When its done Reboot system the device should boot as normal.

Semi Bricked Phone? Any Ideas

Good Morning Everyone,
first of all, thanks for everything I am a member since the HTC Touch HD times, where XDA enabled me to keep that device until 2015!!
Now I have a problem with the Desire 500 single sim of my wife... I just want to restore the phone to full stock to lend it to her mother so she can stay in contact with 21th-century technology (Whatsapp, ...).
Some time ago a messed a little with this device unlocking the bootloader and installing TWRP recovery, the idea was (as probably all the owners know) to install a light version ROM to have a little more space for applications, time wasn't on my side and therefore I had to leave the phone for a while, but as I can remember in working condition (still with the stock ROM).
I had some time to finish the work and a week ago a took out the phone again having a not very good surprise:
I can access now only the bootloader
Recovery send me in fastboot mode
Factory Reset send me in fastboot mode
Classic boot get me to the HTC green logo on white background without doing nothing
Fastboot commands are correctly taken
I am unable to flash whatsoever
I have to charge the phone with the batch file, but with manual booting in bootloader, otherwise, the script does not work
I am unable to relock the bootloader (the fastboot OEM lock throws a "too many links" error and fails)
The command fastboot OEM rebootRUU reboot the device, but not in RUU mode.
The bootloader is still unlocked 1.03.0001
The phone is S-ON
The OS line in the bootloader is empty
Flashing recovery throws "remote:image updated error"
Bootloader INFO
Code:
*** UNLOCKED ***
Z4U PVT SHIP S-ON RL
HBOOT-1.03.0001
RADIO-14.16.36Q4.22
OS-
eMMc-boot
Jul 8 2014, 19:15:10.0
fastboot getvar all
Code:
C:\Users\xxx>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.03.0001
(bootloader) version-baseband: 14.16.36Q4.22
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH449WE0XXXX
(bootloader) imei: XXX
(bootloader) meid:
(bootloader) product: z4u
(bootloader) platform: HBOOT-8x25Q
(bootloader) modelid: 0P3Z11200
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e9f20193
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
I think I almost checked all the internet, any suggestion simply does not work.
I tried to flash different recoveries, ROMs, RUUs... nothing works.
I need to consider the device bricked or do you guys have some other idea to try resolving the problem?
Thanks even if you spend some time for reading...
Bye
NP

M7 - boots to fastboot and recovery, can't boot custom ROMs, errors in RUUs

Hello everybody!
I am loosing my mind with this, would be grateful if someone could help me!
Received an HTC One M7 Nordic (HTC__Y13) version, HBOOT 1.61.0000, radio 4T.35.3218.16, ODSP 35.120.274.0718 OS.
Firstly, I unlocked the bootloader via HTCdev, then, as I did with other devices, installed CWM which I used to wipe just about everything and I installed LineageOS. (S-ON, Tampered, Unlocked bootloader). To my surprise, LOS didn't boot, booting back to fastboot. I gave it another try, reinstalling it, failed to boot again. Then I started trying the RUUs, and the farthest I could reach was the signature rejection at 4%. I am using a Mac with both Sierra and a windows XP SP3 VM in Parallels, which I also used to try with a myriad of toolkits made for this phone. In HTC Sync, although the phone is recognised, all info, like OS version, are blank.
Well, here I am with a device without OS which boots to fastboot and TWRP/CWM. Since the beginning of this adventure, I couldn't boot once to a ROM, and I lost 3 long nights on this already. I believe the only things I could have missed are: using the right RUU.exe or zip, or someway getting the phone S-OFF without using an OS, since I don't have one.
When trying to "fastboot flash -zip ruu.zip", I always have some kind of error like "remote 02 data length is too large" or a variant of this.
I am getting kinda afraid I may have bricked the phone. Could someone help me?
Thanks!
here is the "getvar" dump
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3BRWxxxxxx
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
wasserprojekt said:
When trying to "fastboot flash -zip ruu.zip", I always have some kind of error like "remote 02 data length is too large" or a variant of this.
Click to expand...
Click to collapse
You must use htc_fastboot.exe from a Windows pc, not the regular fastboot. Make sure you have the latest RUU for your cid/mid
Thanks for your answer. I was about to give up on this, but then I finally found the right RUU. There are so many variants it becomes a nightmare finding the adequate one, eve worse if version is not one of the best selling.
But, as someone may need this advice in the future, I'll leave a summary of the important steps in here:
Return to stock ROM (for S-ON & unlocked bootloader & tampered):
- relock your device;
fastboot oem lock
Click to expand...
Click to collapse
-find the adequate RUU;
(for HTC__Y13, it's the RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe)
-close all programs which may connect to phone (includes HTC sync, any fastboot or adb command window...), otherwise there will be no progress in the RUU;
-start the RUU with phone connected (VMs work - at leaset in Parallels with XP SP3).
Thanks to everyone.

HTC One (m7), S-ON, HTCDev UNLOCKED, TWRP installed, ROM/OS NOT detected/bootable

Hey,
long story short, a friend has an old HTC One m7. We revived it from beeing deeply discharged. It was in a bootloader loop.
OS version is NOT shown in the bootloader, no matter which ROM is installed. So we started repairing the system. First I unlocked the bootloader via HTCDev, then flashed TWRP(phone is without branding and S-ON).
This works quite fine. The first problem then was a corrupted storage, which showed a capacity of 2,2 exaByte. Wiping, formatting did not work. So I changed the filesystem and back and then i could wipe, format and the storage capacity was correct again.
No matter which ROM I will flash, if Android 4.4, Android 6.0 or 7.0 and so on, nothing works.
Lineage and some others get stuck at "starting apps", some other just have the boot animation forever.
Only Omni Rom boots into the system, but then i crashes always after a couple of seconds.
I tried also Nandroid backup restores or flash the rom with or without GApps and so on.
I have no idea what to do else. Can anyone help?
Summary:
HTC One (m7)
S-ON
Bootloader HTCDev unlocked
HBOOT-1.61.0000
TWRP 3.2.1-0
ADB Sideload Service inside TWRP not starting
normal ADB commands ARE working
fastboot mode is working
OS Version / OS not detected, not installable, not bootable (no matter which one)
nidico100 said:
Hey,
long story short, a friend has an old HTC One m7. We revived it from beeing deeply discharged. It was in a bootloader loop.
OS version is NOT shown in the bootloader, no matter which ROM is installed. So we started repairing the system. First I unlocked the bootloader via HTCDev, then flashed TWRP(phone is without branding and S-ON).
This works quite fine. The first problem then was a corrupted storage, which showed a capacity of 2,2 exaByte. Wiping, formatting did not work. So I changed the filesystem and back and then i could wipe, format and the storage capacity was correct again.
No matter which ROM I will flash, if Android 4.4, Android 6.0 or 7.0 and so on, nothing works.
Lineage and some others get stuck at "starting apps", some other just have the boot animation forever.
Only Omni Rom boots into the system, but then i crashes always after a couple of seconds.
I tried also Nandroid backup restores or flash the rom with or without GApps and so on.
I have no idea what to do else. Can anyone help?
Summary:
HTC One (m7)
S-ON
Bootloader HTCDev unlocked
HBOOT-1.61.0000
TWRP 3.2.1-0
ADB Sideload Service inside TWRP not starting
normal ADB commands ARE working
fastboot mode is working
OS Version / OS not deteced, not installable, not bootable (no matter which one)
Click to expand...
Click to collapse
Did you tried flashing a RUU?
Can you post the output of "fastboot getvar all" so we can know the exact state of the phone. Don't forget to remove the imei and serialno lines before posting
alray said:
Did you tried flashing a RUU?
Can you post the output of "fastboot getvar all" so we can know the exact state of the phone. Don't forget to remove the imei and serialno lines before posting
Click to expand...
Click to collapse
the problem with the RUU's is, that when I do
Code:
fastboot getvar version-main
no version is shown, so
I don't know which RUU to choose.
Code:
Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3940mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.081s
nidico100 said:
the problem with the RUU's is, that when I do
Code:
fastboot getvar version-main
no version is shown, so
I don't know which RUU to choose.
Code:
Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3940mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.081s
Click to expand...
Click to collapse
Use the 7.19.401.51 ruu
Don't forget to use htc_fastboot.exe instead of fastboot.exe (see the ruu thread in the general section)
alray said:
Use the 7.19.401.51 ruu
Don't forget to use htc_fastboot.exe instead of fastboot.exe (see the ruu thread in the general section)
Click to expand...
Click to collapse
Man you are my hero, thanks a lot it works again
nidico100 said:
Man you are my hero, thanks a lot it works again
Click to expand...
Click to collapse
You're welcome :good:
alray said:
You're welcome :good:
Click to expand...
Click to collapse
one last question, is S-OFF possible for me without paying 25$ for sunshine?
nidico100 said:
one last question, is S-OFF possible for me without paying 25$ for sunshine?
Click to expand...
Click to collapse
Sunshine is required for hboot 1.57 or higher, so the answer is no.

Categories

Resources