Hi all, I am helping my friend to root his tablet. I faced some issues here. Please spend couple minutes to help me out.
Below are my device information,
------------------------------------------------------------------------------------------------------
X:\ROOT\android-sdk-windows\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0011
(bootloader) version-baseband: 3822.10.08.07_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0950
(bootloader) version-main: 3.60.707.4
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: flyer
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG4110000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4143mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f0e1145e
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
------------------------------------------------------------------------------------------------------
I tried globatron method, and everything runs well but I got [140] bootloader error from the RUU.
I tried the following RUU, and the output are the same.
RUU_Flyer_hTC_Asia_WWE_1.48.707.4_Radio_20.3501.30.089BU_3809.05.04.10_M_release_193927_signed.exe
RUU_Flyer_hTC_Asia_WWE_2.27.707.1_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204905_signed.exe
Flyer_hTC_Asia_WWE_1.14.707.1_Radio_20.33.30.088AU_3808.04.00.01_M_test_183285.zip
If anyone know how to solve it, kindly leave a reply here.
Thanks in advance,
From MelvinCHng
If u just want to root, I supposed u r already htcdev unlocked, just flash cwm with fastboot and install superuser 3.13 sign.zip with cwm and u r rooted. Don' t ve to b s off for custom.
Sent from my HTC Flyer P510e using xda premium
go to htcdev.com, unlock your bootloader.
Go to: http://forum.xda-developers.com/showthread.php?t=1870652
download Quick Root 1.1.13 follow the instructions.
Error 140 is bootloader version error. You can't just run any RUU. It has to be the proper RUU for your version (region), and it must be equal or newer than what is already installed on the device. You can't run an older RUU (previous hboot number) unless you are S-off. So the error you are getting is correct and expected.
Just unlock the bootloader as recommended by the previous replies. Or you can look at this (I can't personally vouch for it): http://forum.xda-developers.com/showthread.php?t=2070140
Related
Hey everyone, I'm having an issue unlocking my bootloader after updating the firmware.
When preparing to install the newest version of Android Revolution HD I thought it'd be a good time to update my firmware before switching to the KitKat based ROM. I used the firmware and instructions from here: http://forum.xda-developers.com/showthread.php?t=2182823
All went well until I tried to unlock the bootloader. I can complete all the steps through sending the Unlock_code.bin to the phone, which is successfully sent via fastboot, but I never get the notice on the phone to unlock. Nothing happens.
I believe my best course of action is to flash an RUU but I can't find any that are 4.06.1540.2 or higher at the moment and with S-ON and a locked bootloader, I can't load anything earlier.
If anyone has any insights I'd be most gracious, I'm currently without a phone and have to lug around a Galaxy Tab 3 for mobile connectivity.
Here's my getvar:
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(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: 4283mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
More info
I'll also note that I've tried two different computers, three different cables, and I've probably tried at least 20 different Unlock_code.bins.
I'm really at a loss here, I can flash both 4.06.1540.2 and 4.06.1540.3 to the device from Mike's firmware link; the device has no problems communicating via fastboot. It's just not asking me if I want to unlock after a successful code transfer.
Please contact me if anyone out there wants a challenge to fix my m7-ul. I have fastboot and stock recovery... relocked S-on. Been out of commission for over a month and no one has been able to give me any info that has been helpful yet. I am willing to pay well for some help.
bda714 said:
Please contact me if anyone out there wants a challenge to fix my m7-ul. I have fastboot and stock recovery... relocked S-on. Been out of commission for over a month and no one has been able to give me any info that has been helpful yet. I am willing to pay well for some help.
Click to expand...
Click to collapse
Have you tried the RUU? have you tried unlocking the boot loader and flashing a rom through clockwork mod. What version is the boot loader. what operating system are you on?
bda714 said:
Please contact me if anyone out there wants a challenge to fix my m7-ul. I have fastboot and stock recovery... relocked S-on. Been out of commission for over a month and no one has been able to give me any info that has been helpful yet. I am willing to pay well for some help.
Click to expand...
Click to collapse
fastboot getvar all please do it and remove imei and serial of the device
Sent from my HTC One using xda app-developers app
Tried all the above
TopoX84 said:
fastboot getvar all please do it and remove imei and serial of the device
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I have tried a few different ruu's, not sure if any were the correct one.... i have tried unlocking bootloader. I was previously running the ota of 4.4.2 ge. getvar all as follows: Thanks for your time to anyone that is taking the time to help!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3460mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
bda714 said:
I have tried a few different ruu's, not sure if any were the correct one.... i have tried unlocking bootloader. I was previously running the ota of 4.4.2 ge. getvar all as follows: Thanks for your time to anyone that is taking the time to help!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3460mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Click to expand...
Click to collapse
http://www.htc.com/us/support/htc-one-att/news/
Try that rom
Sent from my HTC One using xda app-developers app
bda714 said:
I have tried a few different ruu's, not sure if any were the correct one.... i have tried unlocking bootloader. I was previously running the ota of 4.4.2 ge. getvar all as follows: Thanks for your time to anyone that is taking the time to help!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3460mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Click to expand...
Click to collapse
You need to wait for ATT RUU higher than 4.06.1540.2. None that is available.
sent from my mobile device
TopoX84 said:
http://www.htc.com/us/support/htc-one-att/news/
Try that rom
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Tried RUU and got error 155.... I have been in denial that there is no answer besides wait for a newer RUU from AT&T.... are there really no hackers out there that can get past the signature verifications?
Have you tried contacting HTC? I'm in the same position as you, same firmware version and all. There's nothing that can get us past that short of that 4.06 or higher RUU - and as was mentioned, it is not available. I'm awaiting a response from the tech team at HTC now.
codejunkie83 said:
Have you tried contacting HTC? I'm in the same position as you, same firmware version and all. There's nothing that can get us past that short of that 4.06 or higher RUU - and as was mentioned, it is not available. I'm awaiting a response from the tech team at HTC now.
Click to expand...
Click to collapse
yes I am also waiting for a rresponse from HTC 3rd tier cust service.... joann or something like that but I really dont think they have a fix or if they are even going to be able to do anything. they informed me this was a security implemented by google during the 4.4.2 update which doesnt allow users to flash anything with a main ver. of equal or less than the current and also the htc dev unlock no longer works with hboot ver 1.55 or 1.56.... aIt is total bs that you can have an htc m7-UL which is supposed to be the developers edition but it is blocked from developing!!
*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.
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.
I relocked my bootloader. Turned S- ON and ran the correct RUU.exe file that I downloaded straight from HTC's website and I always get stuck during the update process(technically a downgrade I suppose) The RUU.exe always comes back with error 155 UNKNOWN ERROR. Not sure what I'm doing wrong. I ran ADB and checked before I ran the RUU that my PC does in fact recognize it( both while on my homescreen and FASTBOOT mode). Please I need help!
ok so I unlocked my bootloader again via HTCDev. But I can't for the life of me get S-OFF again. My HBOOT is 1.54. I am on the OFFICIAL GPE ROM. Help please.
vampsandbats said:
ok so I unlocked my bootloader again via HTCDev. But I can't for the life of me get S-OFF again. My HBOOT is 1.54. I am on the OFFICIAL GPE ROM. Help please.
Click to expand...
Click to collapse
Post a fastboot getvar all except remove your imei and serialno! If what I suspect is true, you changed your MID and CID to the Google MID & CID. If you did that, then the T-Mobile RUU will not run since it is the wrong MID & CID. When you went back to S-ON you made it impossible to change your MID & CID back to T-Mobile. As far as S-OFF is concern you might try Sunshine S-OFF.
majmoz said:
Post a fastboot getvar all except remove your imei and serialno! If what I suspect is true, you changed your MID and CID to the Google MID & CID. If you did that, then the T-Mobile RUU will not run since it is the wrong MID & CID. When you went back to S-ON you made it impossible to change your MID & CID back to T-Mobile. As far as S-OFF is concern you might try Sunshine S-OFF.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 3992mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I appreciate your help.
vampsandbats said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 3992mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I appreciate your help.
Click to expand...
Click to collapse
Let try an older RUU 5.14.531.11
Place phone in FASTBOOT USB
Lock your bootloader if it is not already locked
Run the RUU from your computer
If it fails post the error
If successful then
Try S-OFF with Sunshine
RUU 6.10.531.9
RUU 6.10.531.10
DUDE THANK YOU SO MUCH. I KNOW ITS LIKE 4 months ago but thank you so much. the old RUU did the trick and I got back to stock.