I just ran fastboot getvar all and the mainver came up blank. All other info showed up but that one had nothing. I've done it before way back when, on my old phone running GB and it showed up.
Phone is s-on and has global leak running EclipticRez. Anyone know why this is?
Code:
c:\android-flasher>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.27.0000
(bootloader) version-baseband: 2.22.10.0801r/2.22.10.0803r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4103mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ad3368f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.502s
main version is really a thing to worry about unless you want to go backwards on ruu but if you want to write it back to 1 follow this link : http://forum.xda-developers.com/showthread.php?t=1526316
use this post http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4
Shouldn't it say something after the "(bootloader) version-main:" listing? I was just looking it up to try to help someone out and that's blank.
In my notes from the old days where I put how to look up mainver I have that mine was 2.01.605.11 (at the time) but now I have nothing there. That is the spot it's supposed to be, right?
Never dealt with main version before.
It's all on you synister.
main version is really there so that when you want to install and RUU the signature will allow it to only update and not go back. when you flash the RUU it will write to it to show you are on version X.X and not X.Y. mine on my inc 4g is blank and it doesnt hurt it one bit.
Related
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.
So flashing a rom went wrong somewhere, and I've probably dug myself a deeper hole trying to fix it of course. I can get to bootloader, and I can also get to CWM and/or twrp recovery, however sideloading always fails. Here's a snapshot of where I am now after mucking around too much.
Looking for some help on what steps I need to take to get my baby working again.
boot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4202mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
simplydroid said:
Looking for some help on what steps I need to take to get my baby working again.
Click to expand...
Click to collapse
Not sure if this will work for you or not, with the S-ON thing, but try this:
http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
This is the RUU for the latest (current) T-Mobile update. It should wipe and return your device to 100% stock.
Normally RUU's will not work with S-ON, but I believe that's only for "downgrading"and not for flashing the current version. Should work. Can't hurt to try.
Download it, reboot into fastboot, and run the RUU. It'll take a while, but should work.
PhoenixPath said:
Download it, reboot into fastboot, and run the RUU. It'll take a while, but should work.
Click to expand...
Click to collapse
That got me going, thanked.
Hi, as title states, i purchased a HOX+ 64gb which did not boot, tried factory settings etc etc and always got stuck, tried finding an RUU and could not find for my version....
Anyway, been reading for 2 weeks on here and tried a few various things to get it to boot.
All failed until Android Revolution.
I put a custom recovery on, think its Team Venom Mod of TWRP
Unlocked The bootloader following instructions on here HTC Dev.
flashed boot.img extracted from AndroidRev8.0 zip (did not flash in fastboot so used a script that allows to flash from recovery on this forum)
Flashed the rom from recovery, and brilliant, the phone loads up, wifi bluetooth all work, just IMEI is unknown.
I've tried a few other roms from here, and they all do the same, only thing i have not tried is nandroid backup, but ive not read about them enough yet to trust myself in what im looking for.
I will post fastboot getvar all shortly, but at present im trying a locked bootloader with an RUU i just found while writing this....
Any suggestions for me to try??
(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: FA2B6W102293
(bootloader) imei: IMEI does show correctly here.....
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3840mV
(bootloader) devpower: 58
(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
all: Done!
finished. total time: 0.532s
anyone can help me with this? or a link to an RUU that would restore to stock??
HTC Proto / DESIRE X
Playing with custom ROM and everything connected to it I've managed to erase Serial No and model Id No.
here is the getvar all:
D:\'ndroid\onxr>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.25.0002
(bootloader) version-baseband: 1.15.40.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: u¥næg"öa6ü↨¡õ¥↨
(bootloader) imei: 355803051093548
(bootloader) meid:
(bootloader) product: proto
(bootloader) platform: HBOOT-8225
(bootloader) modelid: ┤ò£e㸪ñ(Éè¨─Q¤~*¼╩Q§¼=Ò±/ `oj\±
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: HTC
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2b02a5bf
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s
Even worse, my bootloader is Relocked and I can not use adb since even with correct drivers. So I'm left with Fastboot only.
It will not apply RUU since it can not pass serial and model check...and now I have a bricked phone.
Is there anyone here who might have idea on how to pull out of this?
HTC Desire X
Nobody? really?
ivar_sa said:
HTC Proto / DESIRE X
Playing with custom ROM and everything connected to it I've managed to erase Serial No and model Id No.
here is the getvar all:
D:\'ndroid\onxr>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.25.0002
(bootloader) version-baseband: 1.15.40.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: u¥næg"öa6ü↨¡õ¥↨
(bootloader) imei: 355803051093548
(bootloader) meid:
(bootloader) product: proto
(bootloader) platform: HBOOT-8225
(bootloader) modelid: ┤ò£e㸪ñ(Éè¨─Q¤~*¼╩Q§¼=Ò±/ `oj\±
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: HTC
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2b02a5bf
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s
Even worse, my bootloader is Relocked and I can not use adb since even with correct drivers. So I'm left with Fastboot only.
It will not apply RUU since it can not pass serial and model check...and now I have a bricked phone.
Is there anyone here who might have idea on how to pull out of this?
Click to expand...
Click to collapse
ivar_sa said:
Nobody? really?
Click to expand...
Click to collapse
Your phone is S-OFF. You probably deleted/formated/flashed certain partitions on your phone that are only accesable when you are S-OFF.
This means, most probably and unfortunatelly, that you have to replace the phone's mainboard.
So, no chance to use some RUU to patch this up?
dodialfaed said:
Your phone is S-OFF. You probably deleted/formated/flashed certain partitions on your phone that are only accesable when you are S-OFF.
This means, most probably and unfortunatelly, that you have to replace the phone's mainboard.
Click to expand...
Click to collapse
ivar_sa said:
So, no chance to use some RUU to patch this up?
Click to expand...
Click to collapse
As far as I know there are no jb hboot RUU's. Only for ICS hboot.
And I am sure you can't downgrade your hboot to ICS because of the corrupted data regarding serial number.
I have a bone stock M8 on Marshmallow. It suddenly started having com.htc.contacts errors and the phone becomes unavailable. I've done multiple recoveries, resets and cache clearing. Sometimes it comes back for awhile but soon eras out. I chatted with HTC support and they suggested reloading the rom so I downloaded the AT&T version and did all the steps per the instructions and started the update. It gets stuck on the "sending" stage and never completes. Reading the forum I saw Sync Manager can be a blocker so I didn't do it through that but no go. Am I missing something? Thanks I searched but didn't find this.
I assume you actually have the AT&T version M8?
If so, RUU stuck "sending" is common. You may need to find a Win7 PC with USB 2.0, which has the best chance of compatibility.
Back to Stock
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?