Database Develop

[GUIDE] How to S-OFF/Flash/Fix Your HTC One When Something Has Gone Wrong

From Buggy to Stable
This guide requires S-OFF
Less than 1.54 (revone) | 1.54-55
Disclaimer​
If there are files you need to keep, you can always use adb pull to get them out before hand (let's say a nandroid backup or something important)
This guide assumes you have knowledge about how adb and fastboot command work and that your HTC drivers are up to date. (Latest HTC drivers)
I am in NO WAY responsible for any possible damage that may happen to your phone, I am only trying to help
I am not a developer/hacker/programmer or anything similar; I am simply a patient geek that likes reading and writing. If you have to thank anyone, thank the developers who made this possible.
Special thanks to mike1986 for Android Revolution HD, the Revolutionary team for revone, beaups and fuses for Rumrunner and the CWM team for their awesome, continued work.
Goals of the Guide​
Help provide the detailed steps to resolve a catastrophe
Help beginners with a detailed step by step and the relevant links to resources that will help them improve their knowledge and understanding
What You Need​
An HTC One in distress
S-OFF
Custom ROM (or stock, we don't judge)
Unlocked bootloader
A custom recovery (I recommend ClockworkMod Recovery)
Compatible firmware package
*Optional but recommended for stability
*UL Variant : Regular / No Red Warning [3.62.401.1]
ADB and Fastboot in working condition
Quick verification​
Start your phone in bootloader by holding the Power button and Volume-Down button (make sure there is plenty of light pointed at the sensor) or by typing
Code:
adb reboot bootloader
Select "Fastboot" so that it appears in red instead of HBOOT
On your computer, make sure fastboot sees your device, then type
Code:
fastboot getvar all
Do a quick copy/paste to compare later.
It should look like this :
Code:
(bootloader) version: 0.5
[U](bootloader) version-bootloader: [B][COLOR="Green"]1.xx.0000[/COLOR][/B][/U]
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
[U](bootloader) version-main:[B] [COLOR="green"]3.57.401.500[/COLOR][/U]
[U][COLOR="Green"](bootloader) version-misc: PVT SHIP [SIZE="6"][B]S-OFF[/B][/COLOR][/SIZE][/U]
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: 11111111111119
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3810mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6cad6811
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Make sure the device is indeed S-OFF. If not, check your "version-bootloader" value and follow the appropriate instructions (which are linked at the top of thread depending on which version you are at)
If You Are Stuck in a Bootloop​
Hold the Volume-Down button
Hold the Power button for around 10 seconds
Release the Power button (but keep Volume-Down pressed)
You should see something similar to this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Plug the phone into the computer
Using the Volume buttons and the Power button, select Fastboot and make sure FASTBOOT USB shows up (like on the picture)
To make sure fastboot is properly connected, use
Code:
fastboot erase cache
Destroying to Better Rebuild​
****Steps 1 to 4 are, although optional, recommended. They will completely erase what you have on your phone, but will reduce conflict; especially in cases where difficulties are encountered.
If you are still on stock recovery and ROM, select the FACTORY RESET option (If it is not there, select BOOTLOADER and then the FACTORY RESET option should appear.) Then skip to Step #4
If you are on a custom recovery, select the RECOVERY option in FASTBOOT If it is not there, select BOOTLOADER and then the RECOVERY option should appear.)
In recovery, select
Code:
Wipe data/factory reset
Code:
Wipe cache
Code:
Advanced - > Wipe dalvik cache
Type
Code:
adb reboot-bootloader
Flashing Firmware​
Prepare your firmware.zip file for imminent flashing.
Type
Code:
fastboot erase cache
Type
Code:
fastboot oem rebootRUU
Once it's rebooted on a silver HTC logo, type :
Code:
fastboot flash zip [pathonyourcomputer/firmware.zip]
You should the following message :
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: [I]X.xxx[/I] s
Re-type :
Code:
fastboot flash zip [pathonyourcomputer/firmware.zip]
Wait until it is done on your computer. The green progress bar shown on the phone will never reach the end.
Type
Code:
fastboot reboot-bootloader
Type
Code:
fastboot getvar all
Allows you, by comparing with your "old" results that the flash indeed worked.
Reinstalling recovery​
Rename the recovery you downloaded to recovery.img and place it in your adb/fastboot folder
Reflash your recovery
Code:
fastboot flash recovery recovery.img
Reboot into recovery by selecting the option in fastboot by selecting BOOTLOADER and then RECOVERY (use the Volume-buttons to navigate and the Power-button to select )
***If it starts a boot loop, just force the phone to enter fastboot by holding the Volume-down button and use "fastboot erase cache"
***If you get an error similar to"mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument", follow this excellent guide by mike1986 on how to fix the issue.
Select the option "Wipe data/factory reset" (You will loose everything not previously backed up outside the phone.)
Select "Wipe Cache partition"
Select "Advanced -> Wipe Dalvik Cache"
Installing Custom ROM​
Now you have 2 options :
Push (Preferred)
While in recovery, type
Code:
adb push [path/rom.zip] /sdcard/rom.zip
Select "Install zip"
Select "Choose zip from sdcard"
Voila ! You should be good to go !
Sideload (If you can't push for some reason)
Select "Install zip"
Select "Install zip from sideload"
Type
Code:
adb sideload [path/rom.zip]
Voila ! You should be good to go !
If anything needs to be changed or if you have any questions, I am subscribed to this thread and will check a minimum of once a day.

Not sure all this is necessary (IMHO), but anyway thanks for the guide.
One thing step 15: "fastboot flash zip [pathonyourcomputer/firmware.zip]"
has to be done twice in succession. first time will come back with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
and the second "fastboot flash zip [pathonyourcomputer/firmware.zip]" will succeed.

nkk71 said:
Not sure all this is necessary (IMHO), but anyway thanks for the guide.
One thing step 15: "fastboot flash zip [pathonyourcomputer/firmware.zip]"
has to be done twice in succession. first time will come back with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
and the second "fastboot flash zip [pathonyourcomputer/firmware.zip]" will succeed.
Click to expand...
Click to collapse
Thank you nkk71 for your advice, I have fixed the guide.

Device not found?
I plug my phone in while in fastboot usb mode and when i enter getvar all the result was "device not found". Any suggestions? I'm caught in a bootloop at the moment, so it's a serious pain

everytime i get "error: device not found" how can i fix it?
---------- Post added at 04:28 PM ---------- Previous post was at 04:17 PM ----------
Thanks for your article, but i've try too many time, not work for me.

soundeluxe said:
everytime i get "error: device not found" how can i fix it?
---------- Post added at 04:28 PM ---------- Previous post was at 04:17 PM ----------
Thanks for your article, but i've try too many time, not work for me.
Click to expand...
Click to collapse
easy on double-posting please
http://forum.xda-developers.com/showthread.php?t=2689229

htc one m7 loop boot
hi sombody can help me my htc one stil reboot
with gevar cmd
i get this
E:\mini-sdk>
E:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.709.14
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA435W904039
(bootloader) imei: 356376052066523
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 3904mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f6d46
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
please can have stock rom or custom link
thanks d'advance

[Q] Can't unlock bootloader after relock

So I've converted my HTC One M7 from Sense to GPE and wanted to revert my changes. I flashed a Stock Nandroid backup (which worked fine), relocked my bootloader and made it from S-OFF to S-ON (why did I do this?).
I can receive the 4.3 OTA update directly with my phone, but after the download finishes, it says it finds that I've made some changes to my phone and it won't install the update.
My guess is that my kernel or my HBOOT aren't as stock as they should be.
I'm on 4.2.2
HBOOT-1.44.0000
RADIO-4A.14.3250.13
Firmware 2.24.401.8
Screenshot of my Firmware and so on:
s1.directupload.net/images/131108/yl3xutnf.png
s1.directupload.net/images/131108/a7mshuvo.png
Since I've updated to 4.2.2 I should have HBOOT 1.54, or not? After doing S-ON I can't upgrade my bootloader or flash anything anymore.
Even HTC Dev Unlock fails after getting a new unlock token. (It says success, but my phone won't do anything)
Any ideas?

Flibber said:
HBOOT-1.44.0000
Click to expand...
Click to collapse
If it's truly 1.44 (check in bootloader screen and make sure the date is before June 2013), then use revone to unlock.
EDIT: it may or may not work since you're already on 2.24, but give it a try anyway

nkk71 said:
If it's truly 1.44 (check in bootloader screen and make sure the date is before June 2013), then use revone to unlock.
Click to expand...
Click to collapse
I restarted in bootloader and checked it, it's 1.44 no doubt. I tried revone already many times but get "Segmentation fault (core dumped)".
Edit: I also checked the date. It's May 3rd 2013.

Flibber said:
I restarted in bootloader and checked it, it's 1.44 no doubt. I tried revone already many times but get "Segmentation fault (core dumped)".
Edit: I also checked the date. It's May 3rd 2013.
Click to expand...
Click to collapse
hboot is good, but the ROM is not really good for revone, best to have a 4.1.2 ROM. unless you can get your bootloader unlocked again, you might be stuck.
What's your current setup? post a "fastboot getvar all" (remove IMEI and s/n) and details of your ROM (you said you flashed a nandroid, which one)

nkk71 said:
hboot is good, but the ROM is not really good for revone, best to have a 4.1.2 ROM. unless you can get your bootloader unlocked again, you might be stuck.
What's your current setup? post a "fastboot getvar all" (remove IMEI and s/n) and details of your ROM (you said you flashed a nandroid, which one)
Click to expand...
Click to collapse
Thanks for your answer, here's my getvar:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA32xxxxxxx
(bootloader) imei: 3544xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.068s
If it's really because of 4.2.2, can I just install a 4.1.2 RUU over it with locked bootloader and S-ON?
I hope my getvar helps finding a solution.

Flibber said:
Thanks for your answer, here's my getvar:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA32xxxxxxx
(bootloader) imei: 3544xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.068s
If it's really because of 4.2.2, can I just install a 4.1.2 RUU over it with locked bootloader and S-ON?
I hope my getvar helps finding a solution.
Click to expand...
Click to collapse
RUU will work with a locked bootloader, but not with S-On (-> S-On won't allow you to downgrade which is only possible with S-Off)
And you firmware is 2.14.401.2 (posted in the getvar)? Haven't seen that one around. Let me think for a while
But in the meantime, can you try something in adb; after you push revone to the phone and open the adb shell, and change permission, your adb shell command prompt is supposed to start with "$", once you revone -P (gaining root access), does adb come back with "#" instead of "$"
can you do it and copy/paste the whole command prompt here.

nkk71 said:
RUU will work with a locked bootloader, but not with S-On (-> S-On won't allow you to downgrade which is only possible with S-Off)
And you firmware is 2.14.401.2 (posted in the getvar)? Haven't seen that one around. Let me think for a while
But in the meantime, can you try something in adb; after you push revone to the phone and open the adb shell, and change permission, your adb shell command prompt is supposed to start with "$", once you revone -P (gaining root access), does adb come back with "#" instead of "$"
can you do it and copy/paste the whole command prompt here.
Click to expand...
Click to collapse
Thanks a lot for helping me with my problem! That's what I get in my command prompt (I'm working with Windows):
Code:
C:\Users\Kevin\Desktop\One_All-In-One_Kit_v\Data>adb push revone /data/local/tmp
/
3324 KB/s (648208 bytes in 0.190s)
C:\Users\Kevin\Desktop\One_All-In-One_Kit_v\Data>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 revone
chmod 755 revone
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Segmentation fault (core dum
ped)
139|[email protected]:/data/local/tmp $

Flibber said:
Thanks a lot for helping me with my problem! That's what I get in my command prompt (I'm working with Windows):
Code:
C:\Users\Kevin\Desktop\One_All-In-One_Kit_v\Data>adb push revone /data/local/tmp
/
3324 KB/s (648208 bytes in 0.190s)
C:\Users\Kevin\Desktop\One_All-In-One_Kit_v\Data>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 revone
chmod 755 revone
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Segmentation fault (core dum
ped)
139|[email protected]:/data/local/tmp $
Click to expand...
Click to collapse
crap
somehow we need to get you into superuser mode, you wouldn't happen to have superuser installed, or be on custom recovery?
Options:
1- Have you tried typing "su" in the adb shell, we need to get the prompt to say # instead of $
2- exit the adb shell, and "adb reboot recovery" and see if adb shell gives you a # instead of $

nkk71 said:
crap
somehow we need to get you into superuser mode, you wouldn't happen to have superuser installed, or be on custom recovery?
Options:
1- Have you tried typing "su" in the adb shell, we need to get the prompt to say # instead of $
2- exit the adb shell, and "adb reboot recovery" and see if adb shell gives you a # instead of $
Click to expand...
Click to collapse
I don't have su anymore and I just tried it to be sure. I can get into recovery when pressing Volume UP + Power when the Symbol appears after typing "adb reboot recovery". It's Android System recovery 3e.
If I try "apply from ..." it says "invalid operation" and immediately reboots...
Btw: I just noticed that the firmware version from getvar is different from my software version in the settings. (2.14.401.2 in getvar and 2.24.401.2 in software information in settings). I guess that's what he doesn't like about my build when trying to do the OTA...

Flibber said:
I don't have su anymore and I just tried it to be sure. I can get into recovery when pressing Volume UP + Power when the Symbol appears after typing "adb reboot recovery". It's Android System recovery 3e.
If I try "apply from ..." it says "invalid operation" and immediately reboots...
Btw: I just noticed that the firmware version from getvar is different from my software version in the settings. (2.14.401.2 in getvar and 2.24.401.2 in software information in settings). I guess that's what he doesn't like about my build when trying to do the OTA...
Click to expand...
Click to collapse
Hey @Flibber, I've been looking around and
1- can't find anything on firmware 2.14.401.2 where did you get that from
2- your software version is 2.24.401.2, that's usually for M7_U models not M7_UL, also strange
How did you get your phone in that state??

nkk71 said:
Hey @Flibber, I've been looking around and
1- can't find anything on firmware 2.14.401.2 where did you get that from
2- your software version is 2.24.401.2, that's usually for M7_U models not M7_UL, also strange
How did you get your phone in that state??
Click to expand...
Click to collapse
First, I changed my MID and CID for going to GPE. To go back I used a nandroid backup of a DE O2 phone (since my phone is also a german O2 branded one). The problem is, i changed the CID to HTC__102 but forgot to change the MID back... No wonder that it won't accept any updates or OTA zips, since they don't match!
I have no idea since unlocking my bootloader, changing my MID/CID or going S-OFF won't work at all...
Edit: Is there any way to change a OTA firmware zip (to change the android-info.txt MID/CID) without losing the signature? Because when I try to flash a firmware zip from an OTA, it passes the signature verification, but fails after checking MID/CID (of course).
Edit2: I just looked into why I can't use revone and most users say that software and firmware version have to match. So the "only" thing I have to do is update my 2.14.401.2 firmware to 2.24.401.2. Again, an original firmware is needed where my CID/MID match the android-info.txt...

I'd really like to bump this. Is there really no way to rezip and sign firmware packages? Or any other solution available?

Sorry for bumping this again, but I'm really stuck with my lovely HTC One
No way to reset CID/MID? Maybe via support? Or something like a hard reset?

[Q] adb device offline

i m trying to get s-off but adb says "device offline" , i have already unlocked my bootloader and i m on OSX Mavericks

xproz said:
i m trying to get s-off but adb says "device offline" , i have already unlocked my bootloader and i m on OSX Mavericks
Click to expand...
Click to collapse
more info plz? Your device is in what mode? what is the output of ./adb devices? can you post a screenshot? and a ''fastboot getvar all'' won't hurt

alray said:
more info plz? Your device is in what mode? what is the output of ./adb devices? can you post a screenshot? and a ''fastboot getvar all'' won't hurt
Click to expand...
Click to collapse
Last login: Fri Feb 14 19:37:44 on console
iMac:~ iMAC$ cd Downloads/OneADB
iMacneADB iMAC$ ./adb-mac devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
iMacneADB iMAC$
Click to expand...
Click to collapse
iMacneADB iMAC$ ./fastboot-mac getvar all
ERROR: could not get pipe properties
< waiting for device >
Click to expand...
Click to collapse
i m in the normal mode, with the desktop screen , do i have to boot the device in boot loader?
edit, when booted on fast boot
Last login: Fri Feb 14 20:24:28 on ttys000
iMac:~ iMAC$ cd Downloads/OneADB
iMacneADB iMAC$ ./fastboot-mac getvar all
ERROR: could not get pipe properties
(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: x
(bootloader) imei: x
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__405
(bootloader) battery-status: good
(bootloader) battery-voltage: 3873mV
(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
all: Done!
finished. total time: 0.043s
iMacneADB iMAC$
Click to expand...
Click to collapse

xproz said:
i m in the normal mode, with the desktop screen , do i have to boot the device in bootloader?
Click to expand...
Click to collapse
As long ./adb-mac devices doesn't output your device s/n, don't attempt to s-off it will not work.no adb only works from OS of from custom recovery, not from bootloader. Looks like you having connectivity issues or drivers issues. Make sure you have latest android sdk installed on your computer and also make sure you have latest drivers for the phone. then run ./adb-mac devices again and make sure adb see the device

alray said:
As long ./adb-mac devices doesn't output your device s/n, don't attempt to s-off it will not work.no adb only works from OS of from custom recovery, not from bootloader. Looks like you having connectivity issues or drivers issues. Make sure you have latest android sdk installed on your computer and also make sure you have latest drivers for the phone. then run ./adb-mac devices again and make sure adb see the device
Click to expand...
Click to collapse
i never installed sdk on the mac , i m downloading it , thank you for the help!

xproz said:
i never installed sdk on the mac , i m downloading it , thank you for the help!
Click to expand...
Click to collapse
maybe your adb is outdated that is why I suggest you to download the latest android sdk for mac. You don't need to keep the entire sdk if you don't need it, just be sure to keep that ''platform-tools'' folder with adb and fastboot.

alray said:
maybe your adb is outdated that is why I suggest you to download the latest android sdk for mac. You don't need to keep the entire sdk if you don't need it, just be sure to keep that ''platform-tools'' folder with adb and fastboot.
Click to expand...
Click to collapse
nothing changed, no device found
iMaclatform-tools iMAC$ ./adb reboot
error: device not found
Click to expand...
Click to collapse
(i simply unzipped the sdk archive and launched eclipse)

xproz said:
nothing changed, no device found (i simply unzipped the sdk archive and launched eclipse)
Click to expand...
Click to collapse
Are you sure you are using a good usb data cable? not only a power cable? I never used eclipse from the sdk, did you tried adb directly from the platform-tools folder?

alray said:
Are you sure you are using a good usb data cable? not only a power cable? I never used eclipse from the sdk, did you tried adb directly from the platform-tools folder?
Click to expand...
Click to collapse
I m using the one provided by HTC
Yes i tried but it doesn t work
Inviato dal mio HTC One utilizzando Tapatalk

xproz said:
I m using the one provided by HTC
Yes i tried but it doesn t work
Inviato dal mio HTC One utilizzando Tapatalk
Click to expand...
Click to collapse
and usb debugging is enabled in developer menu?

alray said:
and usb debugging is enabled in developer menu?
Click to expand...
Click to collapse
I just rechecked it , i was shure it was enabled, i lo dry again
Inviato dal mio HTC One utilizzando Tapatalk

Last login: Fri Feb 14 21:37:45 on ttys000
iMac:~ iMAC$ cd Documents/Arex/Development/adt-bundle-mac-x86_64-20131030/sdk/platform-tools
iMaclatform-tools iMAC$ ./adb devices
List of devices attached
SH3AAW902104 device
iMaclatform-tools iMAC$
Click to expand...
Click to collapse
@alray thank you

xproz said:
@alray thank you
Click to expand...
Click to collapse
np just hit the thanks button if i helped

htc one stuck on logo S on how to s off? or make phone work again?

Hi guys i have htc one stuck on htc logo
i unlock the bootloader problem is this phone S on
can some one give me correct RUU so i can flash and make my phone working again?
here is detail
Code:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.23.3263.28
version-cpld: None
version-microp: None
version-main: 4.20.980.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: VODAP021
battery-status: good
battery-voltage: 4273mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-09ff2ded
hbootpreupdate: 11
can some explain me how to flash and make my phone working agian
thanks a lot

Hi guys can some plz help me out on this? can some one tell me how do solve my problem?

mps5566 said:
Hi guys i have htc one stuck on htc logo
i unlock the bootloader problem is this phone S on
can some one give me correct RUU so i can flash and make my phone working again?
here is detail
Code:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.23.3263.28
version-cpld: None
version-microp: None
version-main: 4.20.980.1
version-misc: PVT SHIP S-ON
serialno: HT379W903185
imei: 355859052317377
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: VODAP021
battery-status: good
battery-voltage: 4273mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-09ff2ded
hbootpreupdate: 11
can some explain me how to flash and make my phone working agian
thanks a lot
Click to expand...
Click to collapse
There is no RUU for available for your phone.
you could flash a custom rom to make your phone working again.

alray said:
There is no RUU for available for your phone.
you could flash a custom rom to make your phone working again.
Click to expand...
Click to collapse
Thanks for ur reply
can u tell me how do i flash customer rom on my phone
can u plz help me out
thanks

mps5566 said:
Thanks for ur reply
can u tell me how do i flash customer rom on my phone
can u plz help me out
thanks
Click to expand...
Click to collapse
So you already unlocked the bootloader, flash twrp recovery, adb push a custom rom, flash it using twrp.
Follow step by step and fell free to ask if you have any question/issue :
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer, either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\android-sdk-windows\tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery (2.6.3.3 or higher) on your device.
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
Here is a list of the HTC M7 roms
Connect your phone to computer using usb cable
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes and there is no progress bar. When the command prompt give you back the hand and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse

thanks for the reply i m stuck on step 5 adb push name_of_rom.zip /sdcard/
some how i can not put rom in to the phone and flash

thanks alray for fixing my phone i really appreciated ur help

mps5566 said:
thanks alray for fixing my phone i really appreciated ur help
Click to expand...
Click to collapse
btw, you might want to edit your post (OP) and remove the IMEI # and the SERIALNO (sensitive data, never post them when you post a ''getvar'' or phone could potentially be cloned)
and thank you for your donation to xda
Code:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.23.3263.28
version-cpld: None
version-microp: None
version-main: 4.20.980.1
version-misc: PVT SHIP S-ON
serialno: [B][COLOR="red"]remove serialno![/COLOR][/B]
imei: [B][COLOR="Red"]remove imei![/COLOR][/B]
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: VODAP021
battery-status: good
battery-voltage: 4273mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-09ff2ded
hbootpreupdate: 11
Click to expand...
Click to collapse

[Q] M7 full wipe no system 6.12.161.8 M7_UL Vodafone

hi my problem is with my htc I wipe it full and I have no software on it , it is vodafone has HBOOT 1.57.0000 and firmware 6.12.161.8 they can help me back up to play a firmware ?:crying:
C:\Users\-\Desktop\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(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
all: Done!

XFX-Gaming said:
hi my problem is with my htc I wipe it full and I have no software on it , it is vodafone has HBOOT 1.57.0000 and firmware 6.12.161.8 they can help me back up to play a firmware ?:crying:
C:\Users\-\Desktop\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(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
all: Done!
Click to expand...
Click to collapse
Remove your IMEI and SERIALNO from your getvar all.
I can't find any files useful to reset your phone back to stock 6.12.161.8 version. You should flash a custom recovery + a custom rom.

alray said:
Remove your IMEI and SERIALNO from your getvar all.
I can't find any files useful to reset your phone back to stock 6.12.161.8 version. You should flash a custom recovery + a custom rom.
Click to expand...
Click to collapse
how can I do that they can give me a manual or via teamviewer help me would be very grateful

XFX-Gaming said:
how can I do that they can give me a manual or via teamviewer help me would be very grateful
Click to expand...
Click to collapse
Follow this guide
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse

alray said:
Follow this guide
​
Click to expand...
Click to collapse
my htc is relocked

XFX-Gaming said:
my htc is relocked
Click to expand...
Click to collapse
same thing apply, follow the guide. (see 3rd prerequisite)

alray said:
same thing apply, follow the guide. (see 3rd prerequisite)
Click to expand...
Click to collapse
i have an error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
error: device not found

XFX-Gaming said:
i have an error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Might be because your driver isn't installed (should not be the case if you have followed the guide)
or maybe because you haven't enabled USB debugging
Hoewever, just do it manually by holding power and volume down until your phone reboot in bootloader then select "recovery"

alray said:
Might be because your driver isn't installed (should not be the case if you have followed the guide)
or maybe because you haven't enable USB debugging
Hoewever, just do it manually by holding power and volume down until your phone reboot in bootloader then select "recovery"
Click to expand...
Click to collapse
and i have this problem
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery openrec
very-twrp-2.6.3.3-m7.img
target reported max download size of 1509875712 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.152s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.056s

XFX-Gaming said:
and i have this problem
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery openrec
very-twrp-2.6.3.3-m7.img
target reported max download size of 1509875712 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.152s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.056s
Click to expand...
Click to collapse
You are not following the guide! Make sure you have all prerequisites before starting and then proceed step by step.
You are having this error because your bootloader is locked/relocked (see 3rd prerequisite, click "show content" and see step 1)

alray said:
You are not following the guide! Make sure you have all prerequisites before starting and then proceed step by step.
You are having this error because your bootloader is locked/relocked (see 3rd prerequisite, click "show content" and see step 1)
Click to expand...
Click to collapse
yes my bootloader is relocked

So I helped him ( @XFX-Gaming ) via team viewer. Bootloader is S-ON and Re-Locked. We got a fresh Unlock_code.bin from HTCDev.com. The unlock code flash fine and the bootloader unlock screen shows up. When selecting "yes" to unlock, phone attemps to boot in recovery and hangs at the "entering recovery" white screen. When force reboot to the bootloader, still re-locked.
Any idea @nkk71 @clsA @Danny201281 ?
I think we should reflash the firmware in RUU mode but can't find any useful files for his version (6.12.161.8)
So we need the 6.12.161.8 firmware or the 6.12.161.8 ota zip file

alray said:
So I helped him ( @XFX-Gaming ) via team viewer. Bootloader is S-ON and Re-Locked. We got a fresh Unlock_code.bin from HTCDev.com. The unlock code flash fine and the bootloader unlock screen shows up. When selecting "yes" to unlock, phone attemps to boot in recovery and hangs at the "entering recovery" white screen. When force reboot to the bootloader, still re-locked.
Any idea @nkk71 @clsA @Danny201281 ?
I think we should reflash the firmware in RUU mode but can't find any useful files for his version (6.12.161.8)
So we need the 6.12.161.8 firmware or the 6.12.161.8 ota zip file
Click to expand...
Click to collapse
Yeah your dead right. Fixed this same issue in the Unbrick Thread just the other day.
Flashing the firmware and getting a new Unlock_code.bin fixed it.

alray said:
So I helped him ( @XFX-Gaming ) via team viewer. Bootloader is S-ON and Re-Locked. We got a fresh Unlock_code.bin from HTCDev.com. The unlock code flash fine and the bootloader unlock screen shows up. When selecting "yes" to unlock, phone attemps to boot in recovery and hangs at the "entering recovery" white screen. When force reboot to the bootloader, still re-locked.
Any idea @nkk71 @clsA @Danny201281 ?
I think we should reflash the firmware in RUU mode but can't find any useful files for his version (6.12.161.8)
So we need the 6.12.161.8 firmware or the 6.12.161.8 ota zip file
Click to expand...
Click to collapse
My German is not so great but look here >> http://www.handy-faq.de/forum/htc_o...c_one_firmwaresammlung_ruus_otas_backups.html

Here you go
zHi5k0 said:
My stautus is relocked. This is the problem. When I'm trying to unlock it with HTCDev method it 's trying to get to recovery but there's no recovery.
Click to expand...
Click to collapse
Danny201281 said:
Ok that makes some sense, you probably have a minor firmware incompatiblity that's causing this problem.
Download this firmware zip and put it in your fastboot folder. Rename it "firmware.zip"
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.11.zip
Reboot the phone into the bootloader and connect fastbootusb.
In the fastboot command line type.
Code:
fastboot erase cache
fastboot oem rebootRUU
**---case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
When that's done go to htcdev.com and go through the entire unlock my bootloader to get a new Unlock_code.bin then use it to Unlock your bootloader. :good:
The firmware will also restore your Stock Recovery, so after the unlock you will need to flash a new custom recovery.
Click to expand...
Click to collapse
zHi5k0 said:
I have an unlocked phone now. Thank you very much. I have no words about the help you did to me. Please tell me what should I do for getting the phone back to stock without bricking it again.
Click to expand...
Click to collapse

Danny201281 said:
Yeah your dead right. Fixed this same issue in the Unbrick Thread just the other day.
Flashing the firmware and getting a new Unlock_code.bin fixed it.
Click to expand...
Click to collapse
Thanks for the info
clsA said:
My German is not so great but look here >> http://www.handy-faq.de/forum/htc_o...c_one_firmwaresammlung_ruus_otas_backups.html
Click to expand...
Click to collapse
Nice collection, everything about x.xx.161.x can be found there... except the 6.12.161.8 firmware or ota we need
Btw the OP also have a thread about his issue on that forum here
and it looks like even them don't have the 6.12.161.8 firmware
will ask in the update thread just in case someone have it.

Mike1986 has 6.12.161.5 in his repository but thats the closest i can find

@alray, i'm capturing 6.12.161.9 OTA (didnt get the .8 one, got straight to .9).... i'll post firmware once i have it

@alray here is the signed firmware from 6.12.161.9
https://www.dropbox.com/s/ov1x96x8c5qhyb6/signed_ota_firmware_6.12.161.9.zip?dl=0
Code:
modelid: PN0710000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAPE17
cidnum: VODAP405
cidnum: VODAP304
cidnum: VODAPD18
cidnum: VODAP120
cidnum: VODAP110
mainver: 6.12.161.9
btype:1
aareport:1
hbootpreupdate:3
as this is only an OTA update it only contains:
Code:
android-info.txt
boot.img
hboot_signedbyaa.img
rcdata.img
recovery.img
splash1.nb0
I was able to capture (even while on SuperCID )
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.5-5.16.161.2_release_387413_VodaIT.zip (608 MB)
then
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.9-6.12.161.5_release_401650aawyk6dy4kqo5flm.zip (250 MB)
don't know why no 6.12.161.8.... i'll try again in a bit (using different CID), so if you wanna wait to see if i can get the .8 version i'll let you know shortly....
@alray EDIT: just changed cid to VODAP102 and got the 6.12.161.8 update info..... downloading... (i've removed the other one from my dropbox)

nkk71 said:
@alray here is the signed firmware from 6.12.161.9
https://www.dropbox.com/s/ov1x96x8c5qhyb6/signed_ota_firmware_6.12.161.9.zip?dl=0
Code:
modelid: PN0710000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAPE17
cidnum: VODAP405
cidnum: VODAP304
cidnum: VODAPD18
cidnum: VODAP120
cidnum: VODAP110
mainver: 6.12.161.9
btype:1
aareport:1
hbootpreupdate:3
as this is only an OTA update it only contains:
Code:
android-info.txt
boot.img
hboot_signedbyaa.img
rcdata.img
recovery.img
splash1.nb0
I was able to capture (even while on SuperCID )
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.5-5.16.161.2_release_387413_VodaIT.zip (608 MB)
then
OTA_M7_UL_K443_SENSE60_MR_Vodafone_UK_6.12.161.9-6.12.161.5_release_401650aawyk6dy4kqo5flm.zip (250 MB)
don't know why no 6.12.161.8.... i'll try again in a bit (using different CID), so if you wanna wait to see if i can get the .8 version i'll let you know shortly....
@alray EDIT: just changed cid to VODAP102 and got the 6.12.161.8 update info..... downloading... (i've removed the other one from my dropbox)
Click to expand...
Click to collapse
Thanks so much!
 @XFX-Gaming New hope :good: