[Q] Trying go back to STOCK with RUU.exe Error 140 - HTC One X+

Hi there,
I came from CM 10.1.1 by Lloir and tried to get back to Stock.
I flashed the original boot.img the stock recovery, relocked the bootloader and used every RUU exe listed in the Device essential material section.
Everytime I get the Error 140 "Bootloader Version Error".
My version-main is 1.17.401.3. The latest available RUU exe has 1.17.401.1... is this maybe why it doesn't works?
Here is my data:
fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.40.0000
(bootloader) version-baseband: 3.1204.168A.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.17.401.3
(bootloader) serialno: FA2AVW102321
(bootloader) imei: 353567050732099
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3820mV
(bootloader) devpower: 56
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
... I have read other threads where people had the same error code, but all of their solutions didn't work for me and I was dumb enough to not do a nandroid backup having STOCK RUU.
As long it doesn't work I can use CM 10.1.1... I have only to flash the right boot.img for CM for that time, so I can use the phone.
Has anyone an idea how I can solve this problem and get back to stock?
Best regards.

Related

Cyanogenmod 11 Problems

Hello everyone! I recently bought a black 32GB HTC One through AT&T. I immediately set to unlocking/rooting/installing a custom recovery. I even used Rumrunner to gain S-OFF. Everything is running fine on my Google Play Edition 4.4.2 ROM. However, my problem is that flashing a CM11-based ROM yields a nonworking camera. It simply reads 'Cannot connect to the camera.' I've tried this on three different ROMs on both the latest TWRP and CWM. I even updated my firmware to the latest Kitkat-based version. Could anyone tell me what I should try now?
I take it that my situation must be rather unique.
Did you flash a 4.4 gapps as well?
cschmitt said:
Did you flash a 4.4 gapps as well?
Click to expand...
Click to collapse
Yes, I did with each ROM I tested.
If it helps in any way possible, this is what I get with "Fastboot getvar all"
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT3AKW904878
(bootloader) imei: 354439058587389
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4148mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s

[Q] HTC One problem, Stuck in cyanogen boot loop, s-on, no RUU available

*Sorry for bad English*
So i have my htc one (m7), and i was trying to get it back to stock htc sense, because is was on cyanogenmod and i didn't really like it. i have used the tutorial from htc-one.wonderhowto .com ... I followed all the steps (relocked bootloader and downloaded HTC program), but the RUU wasn't compatible, i didn't know that at the time. So I was searching for another RUU, but I coudn't find a one to fit my device.
This is what *fastboot getvar all* gives me:
(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-ON
(bootloader) serialno: SH35WW909931
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
As you can see, i currently have s-on, and i can't find a proper RUU. So i tryed if there was a way to set my s-on to s-off. but i can't do that with rumrunner, since i am not able to uncheck *fastboot* in android settings, because i can't boot. Note: i have Clockworkmod Recovery installed. I live in the Netherlands.
Can anyone help me with this? i'm new to all this info so i dont know if there is an other way to simply install the stock htc rom.

CanĀ“t unlock BL stuck

Hello,
I bought a broken One X+ (Digitizer is faulty) on eBay. The Phone bootet full up but there was a Pin lock, so i decided to go to BL and do a Factory Reset unfortunately this deleted the whole OS and I think also the Recovery. So i tried to install JB via RUU but it stucks at "waiting for Bootloader" and after a while the RUU stops working: Error 171. All drivers are correctly installed, so i tried to unlock the BL to install a custom recovery and an AOSP ROM. But every time i flash the unlock.bin and confirm it on the Phone it reboots and stays locked. Is there a way to get Android back running on the HOX+?
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 3.1204.171.33
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.18.401.2
(bootloader) serialno: FA2BRW104070
(bootloader) imei: 353567051433945
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: low
(bootloader) battery-voltage: 3303mV
(bootloader) devpower: 0
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
Regards Lukas

[Q] HTC One (m7)unrooting

I have recently decided to root my HTC one m7 to install stock android and failed, i installed kernels and roms but i didn't know i had to have s-off now my phone is in a boot loop.I have tried too install the ruu files but with no success so i am asking for someone to help me.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.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__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4074mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You don't have to S-Off to install custom roms and kernels, it just makes it easier to install. To install while S-On, you must extract the boot.img file from the rom zip and install via fastboot while in bootloader mode. If you are trying to restore to stock with an RUU, you must relock the bootloader or the RUU won't run properly and fail.
Repy
I have re-locked and tried to install my ruu file but it always fails saying that my phone got disconnected .Also my "version-main" is blank.
I managed to fix it thanks for your reply es0tericcha0s you have finished my 3 day ordeal.

[Q] Possible brick

Hi there,
I'm not sure what you consider as bricked phone, but I might have end up with this situation. I have tried updating my Amaze 4g to CyanogenMod 11 but I believe completely failed :/. Currently the device doesnt work at all I have tried to put a stock rom and a lot of other custom roms but unfortunately none of them worked. The phone is S-ON running HBOOT 1.93.002 and these are the variables that I managed to get from the fastboot:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.93.0002
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: SH1AGVP00507
(bootloader) imei: 358927045134428
(bootloader) product: ruby
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH8511000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4208mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6298f8f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Unfortunately I dont have a backup of anything I cant revert what I didt, so I m kind of at desperate at the moment. I do have a TWR 2.8.1.1 which I can access but still I m not sure how to proceed from now onward :/
Can anybody help me please?

Categories

Resources