[HELP] Removing carrier branding, S-OFF and rooting - HTC One S

Hey guys.
I recently got a second-hand HTC One S (I think its the S3 model, since it says "Dual Core 1.5Ghz" in the settings or something like that) and it has the Vodafone carrier branding. I'm trying to remove it, root it and S-OFF it, but I'm new to HTC stuff (I'm used to mess with Motorola phones... way more easy) and it is not working.
I've already unlocked my bootloader and tried to root using superoot, but its stuck on "this build is for development purposes only" screen. Also, moonshine S-OFF is not compatible with my build (3.16.111.16), so I can't S-OFF it (whatever S-OFF means).
Can somebody help me? I've read a lot of threads, but none were useful enough
(Also, I can't get the fastboot of this phone to work on Windows 10, not even after following many tutorials).
Thanks in advance!
EDIT: here's the result of fastboot getvar all
Code:
>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.15.0000
INFOversion-baseband: 1.15.50.05.29
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.16.161.11
INFOversion-misc: PVT SHIP S-ON
INFOserialno: <<loremipsum>>
INFOimei: <<loremipsum>>
INFOproduct: vle
INFOplatform: HBOOT-8960
INFOmodelid: PJ4010000
INFOcidnum: VODAP102
INFObattery-status: good
INFObattery-voltage: 3849mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-64bedd38
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!

No one?

Ok, so if anyone ever needs this: I ended up finding that my model has the S4 processor when I tried to install TWRP. Then I installed CyanogenMod and managed to change the CID by hex-editing one partition (you can find it on the general section, I believe). After that, I had to revert back to stock (since camera doesn't worked for me on CM12), but since I had changed the CID, now I could flash any ville RUU!

Thanks mate for helping us
I have almost the same problem. Phone came to me with original Locked Bootloader and S-ON, and I hurried to install a custom ROM to upgrade the Android from original 4.1.2 to a Custom ROM 5.1 ( Candy one ), but I just unlocked bootloader and went immediately at the procedure of flashing Candy custom ZIP firmware and then GAPPS but after writing those 2 zips now my phone hangs at a black screen and is not booting.
Priot to writing those ZIPs I tried to S-OFF using Rumrunner, but it failed so I thought that it is not needed and I believed that just unlocking bootloader and writing Custom ROM like in HTC m7 and M8 that I have done some will work. But seems I am stuck now at S-ON and my phone doesn't boot, as I can not find a newer or same firmware version that the phone had:
fastboot
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.166.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH24CW400091
(bootloader) imei: 359901046616211
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 3970mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.145s
This is original firmware RUU for my phone CID :
RUU_Ville_U_Vodafone_CH-DE_1.78.166.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258383_signed
that I downloaded two times at Androidruu, but it is corrupted as a file, but I think also that I can not write that firmware as it is lower version than my phone had when it was working.
Also I think that I have S4 because when it was working I checked with an application that somebody said on this forum and it was adequate for S4
Any help would be much appreciated
Thanks
Renan Lazarotto said:
Ok, so if anyone ever needs this: I ended up finding that my model has the S4 processor when I tried to install TWRP. Then I installed CyanogenMod and managed to change the CID by hex-editing one partition (you can find it on the general section, I believe). After that, I had to revert back to stock (since camera doesn't worked for me on CM12), but since I had changed the CID, now I could flash any ville RUU!
Click to expand...
Click to collapse

Revived now the phone it is not said to be S-OFF for working phone.
I followed this Custom ROM thread and it is now on 5.1.1
http://forum.xda-developers.com/htc-one-s/development/rom-cyanogenmod-12-lollipop-htc-one-s-t2946468
BR

Related

[Q] Help! Something went wrong while installing an RUU!

Hi, I was trying to unroot my desire S, I have been following the desire fanatics guide on youtube (Can't post the link - sorry)
And I got up to the point where I was running the RUU utility. It started and then It got to about 50% in and then said Error, please use the correct RUU utility. (I'm guessing I've downloaded the incorrect RUU file.
So now, when I turn the phone on it goes right into the white menu with all the stuff on HBOOT etc.. fastboot I think it is, and it says security warning.
I'm guessing Its wiped the data but no longer has an OS to boot into. I honestly don't think it is bricked but I have no clue what to do from now!
I got my phone from mobiles.co.uk (A carphone warehouse subsidiary) and it is on contract with T-mobile. The phone had no branding on it from T-mobile so I guess its unlocked.
However I downloaded the T-mobile UK RUU and ran that..
Any advice on what to do from here? I'm currently in the process of downloading The Saga_HTC _Europe_1.28.401.1_Radio20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
I don't even know if this will work because I can't get into any OS. I also read a lifehacker article and it said I can put a file onto the SD card and it will automatically run fixing the phone, making it better.
Please help me!
So far, I've tryed:
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
and
RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed
But neither of these have worked, it gives me an error 140 saying I'm using the wrong version!
Can anybody tell me the correct version for an unlocked desire S bought in the UK from mobiles.co.uk?
Something that may of made this slightly more difficult for myself Is that While following the guide I followed, I used android flasher and flashed the bootloader included in the Revert to stock bundle kit thing, It was called engHBOOToverARX
I honestly have no Idea how I can fix this but Hopefully somebody else can!
can you tell me your current hboot version?
is your device detected by ADB?
if you have not set up ADB before read this below link
His device won't be detected by adb, only fastboot.
Run fastboot command "fastboot getvar all" and post the response.
Ok, this is what I get after fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) serialno: SH15NTJ00762
(bootloader) imei: 356708049175530
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.023s
And I have the ability to run adb commands but I don't know what command to use to check if its detecting my device, I type adb into cmd and loads of commands come up..
@imattacus
Okay you have a UK unbranded phone, I say this cause your CID is HTC__001 and your main version is 1.47.401.4.
So to fix you can either;
1) You can download this RUU (v1.47.401.4, hboot 0.98.0002) and run it from the PC.
Or
2) Change your main version (by getting shell root) then trying again with the 1.28.401.1 RUU. (but may be impossible since you can't get adb)
Option 1 is the easiest.
Same issue with Virgin Mobile RUU
Anyone got the correct RUU for me as I've got the same issue with a Virgin Mobile RUU. I followed the instructions for unrooting here. I was using the Virgin Mobile RUU listed on the link provided which was this list but I keep on getting error 140 when I run the RUU, telling me to use the correct one.
My bootloader is as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
I just need to find the right RUU version.
Any help would be greatly appreciated and as soon as possible.
Thanks
Just use Goldcard and try 1.47.401.4 again.
I also have a few problems with my Desire-S:
-my android email app keeps crashing when i try to open any email;
-official update aborts instalation (system 7) (even after hard reset).
So i decided to try fixing this via RUU. My phone is unbranded (bought in Slovenia's Vodafone), unrooted:
-android 2.3.3
-Sense 2.1
-Build 1.47.401.4
-Boot says: Saga PVT Ship S-on RL, Hbroot 0.98.0002, radio 3805.06.02.03_M
I tried to install:
-RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_234765_signed.exe
Every time i get an error 131- customer id error and message, that the ruu is wrong...
So i tried with the older one:
-RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed.exe
And i keep getting error 140.
And i'm stuck here. Any help? I'd like to put on 2.3.5 with sense 3 without that email bug.... and i'm considering taking it to the repair service...
Thank You
i had in a way similar problem with imattacus...
only i can't run adb commands (adb devices returns no value)
i tried folowing ruu-s:
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed
RUU's installed, but after boot phone was stuck in white screen with green htc.
after i installed this RUU my phone booted:
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
update>>
I checked for updates and there were some... After installing phone stuck on white screen...
I just whish to restore my phone to it's factory outofthebox state..
My getvar all result is::
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) serialno: HT13HTJ16283
(bootloader) imei: 355067040509788
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4020mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Any sugestions?
Goldcard
Sent from my HTC Desire S
I have installed ruu with the gold card, but I did removed it before update... Will try again and post back. Thank you very much for quick response!
>>>>>update...
Unfortunately, with gold card everything went same as before...
When i download and run update, phone reboots into update screen with progress bar, then reboots to update screen with same bar, then reboots to update screen without progress bar, then reboots and stays stuck on white screen...
i guess i have to find a way to unroot and s-on my device to the stock values before i try to update again...
my fastboot screen reads:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
One more curious thing..
When i install RUU ver 1.47.401.4 (only i'm able to boot so far) image version that i overwrite (visible from RUU install screen) is 13.10.401.8... A bit large number, isn't it?
>>> FINAL UPDATE
SUCCESS!!!
as i suspected earlier, when i folowed first post on this topic i locked the phone, and then update worked.
have a nice day, everyone!

[Q] Can't find a RUU that matches my hboot/radio

Hi everyone.
I'm trying to get back on stock (S4), but I can't find any RUU that matches my hboot and radio.
this is the result of fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4005mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I tried several S4 RUUs, european ones gave me error 131, Vodafone UK gave error 155 (the cellphone was bought in Italy).
What I did before executing the RUU exe(s) was just locking the bootloader. I think that probably installing ROMs in the time (the cellphone belongs to a friend of mine, so I don't know what was installed before) may have somewhat changed hboot (and/or radio) version, and now I can't find a RUU matching mine. Now i can only access the bootloader (I think the previous custom recovery is gone). I managed to access recovery by unlocking again the bootloader, but I can't mount any partition from the recovery (which is the main problem that lead me to decide to get back to stock.
What are my chances to return to HTC stock?
I have the same problem
Hi mate, I'm italian too. I suggest you to get S-Off (it's easy enough now with the brand new tools), change cid with fastboot command to HTC__001 and flash latest JB 4.1 european RUU. It's pretty easy
addsfsds said:
Hi mate, I'm italian too. I suggest you to get S-Off (it's easy enough now with the brand new tools), change cid with fastboot command to HTC__001 and flash latest JB 4.1 european RUU. It's pretty easy
Click to expand...
Click to collapse
I am very new to htc rooting and other stuff. kindly provide stepwise procedure with links to the tools and appropriate RUU
I have tried hit & trial but i am unable to get to stock
hasanalikhattak said:
I am very new to htc rooting and other stuff. kindly provide stepwise procedure with links to the tools and appropriate RUU
I have tried hit & trial but i am unable to get to stock
Click to expand...
Click to collapse
Dude give a quick look around, all the guides are here! or come to androidiani.com to get italian translated guides and support!

[Q] Unable to unlock again after "fastboot oem lock"

I'm trying to get my HTC Sensation to boot one of the 4.4 CyanogenMod unsupported ROM's, and after going through several walkthroughs I found here, I realized I had to upgrade my firmware before I could do that. So I used the "fastboot oem lock" command and reloaded a stock ROM using an RUU process. Now I'm ready to load one of the new CM ROM's, but I can't flash any boot image until I unlock the bootloader again. I tried using the HTCDev process again using my original Unlock_code.bin as well as a newly generated Unlock_code.bin, but no luck. I feel like this is the last speed bump to get over. Here are the results of my "getvar all":
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.106
(bootloader) serialno: HT162T527781
(bootloader) imei: 355066041626260
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4182mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I go into the bootloader it currently says:
Code:
*** RELOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
Any ideas of how I can unlock the bootloader long enough to flash a boot image? Any advice is much appreciated!
roswell1329 said:
I'm trying to get my HTC Sensation to boot one of the 4.4 CyanogenMod unsupported ROM's, and after going through several walkthroughs I found here, I realized I had to upgrade my firmware before I could do that. So I used the "fastboot oem lock" command and reloaded a stock ROM using an RUU process. Now I'm ready to load one of the new CM ROM's, but I can't flash any boot image until I unlock the bootloader again. I tried using the HTCDev process again using my original Unlock_code.bin as well as a newly generated Unlock_code.bin, but no luck. I feel like this is the last speed bump to get over. Here are the results of my "getvar all":
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.106
(bootloader) serialno: *************
(bootloader) imei: **********
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4182mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I go into the bootloader it currently says:
Code:
*** RELOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
Any ideas of how I can unlock the bootloader long enough to flash a boot image? Any advice is much appreciated!
Click to expand...
Click to collapse
since you are on S-OFF flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
after that install a custom recovery and flash a custom rom from it
you don't need to flash the custom rom's boot.img because you are on S-OFF
by the way you could just flash 3.33 universal in first place and avoiding the ruu process
note:remove you imei and s/n
don't show them in public
rzr86 said:
since you are on S-OFF flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
after that install a custom recovery and flash a custom rom from it
you don't need to flash the custom rom's boot.img because you are on S-OFF
by the way you could just flash 3.33 universal in first place and avoiding the ruu process
note:remove you imei and s/n
don't show them in public
Click to expand...
Click to collapse
That was it! Thank you very much. It's running like a champ now.

HTC ONE S - S4 - S-ON - RUU help

Hi, I need some help going back to stock rom on my htc one s (s4).
I've read some places that I need an Ruu same as my version, this is my info.
Version main: 3.16.110.4
Tampered
Unlocked
VLE PVT SHIP S-ON RL
HBOOT - 2.13.0000
RADIO - 1.11.50.05.28
OpenDSP -v31.1.0.45.0815
eMMC-boot
I tried the instructions on androidforums dot com, can't post the link here cus it's one of my first posts, but I typed in google "HTC one s ruu" and it was the first link.
But at the end it said something like "Can't flash this image, find the correct image" or something along those lines.
I used this ruu at the time because it was the only similar one (although not exact) to my phone.
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
and yes I did lock my bootloader before running the ruu, but I unlocked it again just for use until I can find a working solution to going back to stock rom. (Btw i'm S-ON!)
Any help would be MASSIVELY appreciated!
Do you know your CID? You can get this info in bootloader mode and use this command:
Code:
fastboot getvar all
Please post all data except your IMEI number.
The RUU you used should work for almost any European countries as long as it's an non-carrier specific phone.
kdd998 said:
Do you know your CID? You can get this info in bootloader mode and use this command:
Code:
fastboot getvar all
Please post all data except your IMEI number.
The RUU you used should work for almost any European countries as long as it's an non-carrier specific phone.
Click to expand...
Click to collapse
Thanks for your reply Yeh my CID is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.13.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.110.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT275W400818
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 3823mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-26dff973
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I guess you can't use this RUU for this phone. Try to find one for T-Mobile UK as it seems to be what your CID is telling.

Is it too late to S-OFF and SuperCID !?

Hi folks,
I've got my old Telstra HTC One XL (Evita) laying around that I need to re-commission back into service! Info is below.
I've been trying to S-OFF and SuperCID but all links seem to be dead and/or taking me round in circles from one site to another to another back to here, kind of thing.
The device currently has...
its bootloader unlocked
TWRP 3.0.2 custom recovery installed; and
root
Presently it is running CyanogenMod 12.1 (Android 5.1.1) which has,
Kernel version 3.4.105-ga346a29; and is
Build number cm_evita-userdebug 5.1.1 LMY48B 37126a8090
I was hoping to go to Marshmallow or even Nougat, but will look into that a bit further.
Main question I'm asking at the moment though is: do I need to spend any more time trying to get this device S-OFF and SuperCID? Is it even possible to get this device S-OFF and SuperCID? I did see one post that talked about downgrading, but again that was another thread with dead links and circling websites. Will going S-OFF and SuperCID now net me any further benefits over what I already have?
I know the device is old and I know most anyone and everyone has moved on now, but no harm in asking!
Thanking you.
Kind regards,
Dodgy Bob
..............................................
Code:
======================================================
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.38A.32.45.24
OpenDSP-V33.1.0.45.1128
eMMC-boot
Jul 9 2014,18:31:42:-1
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
POWER DOWN
SHOW BARCODE
IMEI:
SN:
MB:
======================================================
======================================================
C:\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.38a.32.45.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.841.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8312000
(bootloader) cidnum: TELST001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3911mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.097s
======================================================

Categories

Resources