Database Develop

[SOLVED] my incredible S stuck at HTC Logo After OTA Update

Hello, i Have HTC Incredible S.
my phone was S-Off with EhabFG RUU, after 2.3.5, 3.0 Sence officially released i decided to get back to original RUU.
i installed 2.1 RUU and then i performed steps here:
http://forum.xda-developers.com/showthread.php?t=1359555
to get back my S-ON to get update, after that i request OTA and installed 2.3.5 RUU successfully, after rebooting my phone now is stuck on HTC Logo and i can't do anything.
can anyone help me what can i do to get my phone back?
my bootloader still alive, but when i tried to install any official Rom but i'm receiving error said this RUU is older than i have.
Please Help.
Regards

hamza_aj said:
Hello, i Have HTC Incredible S.
my phone was S-Off with EhabFG RUU, after 2.3.5, 3.0 Sence officially released i decided to get back to original RUU.
i installed 2.1 RUU and then i performed steps here:
http://forum.xda-developers.com/showthread.php?t=1359555
to get back my S-ON to get update, after that i request OTA and installed 2.3.5 RUU successfully, after rebooting my phone now is stuck on HTC Logo and i can't do anything.
can anyone help me what can i do to get my phone back?
my bootloader still alive, but when i tried to install any official Rom but i'm receiving error said this RUU is older than i have.
Please Help.
Regards
Click to expand...
Click to collapse
You need to go into Fastboot mode and enter the command:
Fastboot getvar main_version and post your results. Also a shot of what your current HBOOT screen looks like.

tpbklake said:
You need to go into Fastboot mode and enter the command:
Fastboot getvar main_version and post your results. Also a shot of what your current HBOOT screen looks like.
Click to expand...
Click to collapse
thank you for fast respons.
my HBOOT Screen:
===
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3822.10.08.28_M
eMMC-boot
Apr 1 2011,18:34:39
===
and i don't know why i get error for the command you give, i get this result:
===
C:\Android>Fastboot getvar main_version
getvar:main_version FAILED (remote: unknown command)
finished. total time: 0.001s
===
Thank again

hamza_aj said:
thank you for fast respons.
my HBOOT Screen:
===
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3822.10.08.28_M
eMMC-boot
Apr 1 2011,18:34:39
===
and i don't know why i get error for the command you give, i get this result:
===
C:\Android>Fastboot getvar main_version
getvar:main_version FAILED (remote: unknown command)
finished. total time: 0.001s
===
Thank again
Click to expand...
Click to collapse
Ok try Fastboot getvar all and post the results.

tpbklake said:
Ok try Fastboot getvar all and post the results.
Click to expand...
Click to collapse
this is the result:
===
C:\Android>Fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.13.0000
INFOversion-baseband: 3822.10.08.28_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.09.415.2
INFOserialno: HT16ATD00221
INFOimei: 355301049745212
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213000
INFOcidnum: HTC__J15
INFObattery-status: good
INFObattery-voltage: 3876mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8a731c6e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.021s
===
Sincerely

hamza_aj said:
this is the result:
===
C:\Android>Fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.13.0000
INFOversion-baseband: 3822.10.08.28_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.09.415.2
INFOserialno: HT16ATD00221
INFOimei: 355301049745212
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213000
INFOcidnum: HTC__J15
INFObattery-status: good
INFObattery-voltage: 3876mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8a731c6e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.021s
===
Sincerely
Click to expand...
Click to collapse
Ok the line version-main shows that you have 3.09.415.2 which is what the OTA Attempted to install. In order to flash an older RUU, you need to change this value using the main_version program to something like 1.00.0000. Search this forum for downgrading hboot and you should find instructions on how to do that.

tpbklake said:
Ok the line version-main shows that you have 3.09.415.2 which is what the OTA Attempted to install. In order to flash an older RUU, you need to change this value using the main_version program to something like 1.00.0000. Search this forum for downgrading hboot and you should find instructions on how to do that.
Click to expand...
Click to collapse
OK, thank you i'll search for it, and if you found the link please posted here.
Thanks

hamza_aj said:
OK, thank you i'll search for it, and if you found the link please posted here.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20024110&postcount=10
This link shows you exactly what you need to do. The original post of this thread should have the file to download that contains the main_ version app.

tpbklake said:
http://forum.xda-developers.com/showpost.php?p=20024110&postcount=10
This link shows you exactly what you need to do. The original post of this thread should have the file to download that contains the main_ version app.
Click to expand...
Click to collapse
thank you very much i will apply this steps now.
Best Regards

hamza_aj said:
thank you very much i will apply this steps now.
Best Regards
Click to expand...
Click to collapse
Hello, back again with no luck.
i see this steps for a device starting normally but my device freezing on HTC Logo so i can't do many steps here.
also, i tried to open downgrade toolkit, and the result still as the same.
can anyone help?
Regards

hamza_aj said:
Hello, back again with no luck.
i see this steps for a device starting normally but my device freezing on HTC Logo so i can't do many steps here.
also, i tried to open downgrade toolkit, and the result still as the same.
can anyone help?
Regards
Click to expand...
Click to collapse
OK, so inside the downgrade toolkit zip file you should find both zergRush and misc_version images, right?
Here are the steps you need to try using adb after you copy the zergRush and misc_version images to the same directory where you have adb.exe and fastboot.exe:
adb shell rm -r /data/local/tmp/*
adb push zergRush /data/local/tmp/zergRush
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/zergRush
adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 1.00.000.0'
Once you have done that then you can try flashing the RUU for your region.

Possible to s-off again and reflash boot.img from official RUU?
Not familiar with these issues as I find it hard to fathom why one would want to go official after trying so hard to go custom.
Edit: @tpbklake I don't want to step in on your support, but are you sure your code is correct? It's pushing zergrush and misc_version into their own folders within tmp but executing from tmp? Misc_version needs superuser permissions.

Nonverbose said:
Possible to s-off again and reflash boot.img from official RUU?
Not familiar with these issues as I find it hard to fathom why one would want to go official after trying so hard to go custom.
Click to expand...
Click to collapse
I completely agree, but the fact is some of these noobs see an OTA pop up and immediately think they need to flash it and end up in these situations without even reading and researching. Then they come help looking for help...

tpbklake said:
I completely agree, but the fact is some of these noobs see an OTA pop up and immediately think they need to flash it and end up in these situations without even reading and researching. Then they come help looking for help...
Click to expand...
Click to collapse
Lol yeah I noticed, but I also noticed that you're almost always the first and usually only one helping them out.
While I think your hard work and tireless efforts are commendable, spoon feeding noobs will just make them that much more dependant on you next time, and the time after that,etc..
From what I have seen of your activity on this forum, your thanks meter should be well in excess of your posts. /2c
Happy new year

Nonverbose said:
Lol yeah I noticed, but I also noticed that you're almost always the first and usually only one helping them out.
While I think your hard work and tireless efforts are commendable, spoon feeding noobs will just make them that much more dependant on you next time, and the time after that,etc..
From what I have seen of your activity on this forum, your thanks meter should be well in excess of your posts. /2c
Happy new year
Click to expand...
Click to collapse
I try to help, but I like to take the approach together them to search and find things on their own. I try to not post step by step, especially when someone else has done it.
It is like baking a cake. You can give them a recipe, but if they don't know how to turn on an oven, run a mixer or know the measurement abbrev. then that recipe is not of much value now is it?

tpbklake said:
OK, so inside the downgrade toolkit zip file you should find both zergRush and misc_version images, right?
Here are the steps you need to try using adb after you copy the zergRush and misc_version images to the same directory where you have adb.exe and fastboot.exe:
adb shell rm -r /data/local/tmp/*
adb push zergRush /data/local/tmp/zergRush
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/zergRush
adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 1.00.000.0'
Once you have done that then you can try flashing the RUU for your region.
Click to expand...
Click to collapse
thank you very much for your kind replay.
i tried to do this steps but i'm receiving this:
===
C:\Android>adb shell rm -r /data/local/tmp/*
adb server is out of date. killing...
* daemon started successfully *
error: device not found
===
i don't know if should i attache my device to fastboot or HBOOT USB but i tried both.
i attached my device and accessed to: HBOOT USB and i see: HBOOT USB PLUG
and i take fast boot and i can see: FASTBOOT USB.
why i'm receiving device not found?
sorry for a lot questions and thanks again for help.
Regards

hamza_aj said:
thank you very much for your kind replay.
i tried to do this steps but i'm receiving this:
===
C:\Android>adb shell rm -r /data/local/tmp/*
adb server is out of date. killing...
* daemon started successfully *
error: device not found
===
i don't know if should i attache my device to fastboot or HBOOT USB but i tried both.
i attached my device and accessed to: HBOOT USB and i see: HBOOT USB PLUG
and i take fast boot and i can see: FASTBOOT USB.
why i'm receiving device not found?
sorry for a lot questions and thanks again for help.
Regards
Click to expand...
Click to collapse
You need to have the phone booted normally when you are typing the adb commands.

tpbklake said:
You need to have the phone booted normally when you are typing the adb commands.
Click to expand...
Click to collapse
thank you, but as i told you from the biganning my phone is not starting normally. it just start and stuck on HTC Logo.
can i do something in my case?
thanks

Try flashing a custom rom

hamza_aj said:
thank you, but as i told you from the biganning my phone is not starting normally. it just start and stuck on HTC Logo.
can i do something in my case?
thanks
Click to expand...
Click to collapse
OK, do you still have the OTA file that you attempted to flash? It is probably still on your microSD card in one of the directories somewhere.
If you open that OTA.zip file, there should be a file inside called firmware.zip (or firmware.img can't remember which one it is). If you extract that file and then copy it to your microSD car and rename it PG32IMG.zip (or PG32IMG.img if it is firmware.img) and then reboot into HBOOT mode, it will attempt to install this and if it is successful you should be good to go.

AT&T HTC One s-off help

I have the 64gb HTC One unlocked, rooted and running TWRP recovery. I have been trying to get s-off but have only succeeded in messing up my WiFi and camera.
I have tried using moonshine (both windows and Linux ver) and revone from both the computer and direct on the phone. Is there anything else I can try?
I would like to either get s-off so I can do the Google edition conversion or go back to stock so I can get my WiFi and camera working and get the OTA updates.
Phone specs as follows
M7_UL pvt ship s-on RH
hboot - 1.44.0000
radio - 4A.17.3250.20_10.40.1150.04L
OpenDSP - V31.120.274.0617
eMMC - boot
Jul 5 2013,16:04:18:-1
Android 4.1.2
HTC Sense: 5.0
Build no: 1.26.502.15 CL213167 Release-keys
kernel ver: 3.4.16-g0a0f902
[email protected] #1
smp preempt
image crc:
rpm: 0x5c2b29fe
sbl1: 0x3eabf110
sbl2: 0xa35fe42a
sbl3: 0xe8ef6c99
tz: 0x5b8ab6c5
radio: 0x13bcf252
hboot: 0xb7620927
boot: 0xf0cadd9b
recovery: 0xcb9d7d41
system: 0xba29c7c6
Sent from my HTC One using xda app-developers app

Try rumrunner.

Try flashing a different kernel I messed up the camera but I flashed elemental x and worked again
Sent from inside the T.A.R.D.I.S

gvarnadoe said:
I have the 64gb HTC One unlocked, rooted and running TWRP recovery. I have been trying to get s-off but have only succeeded in messing up my WiFi and camera.
I have tried using moonshine (both windows and Linux ver) and revone from both the computer and direct on the phone. Is there anything else I can try?
I would like to either get s-off so I can do the Google edition conversion or go back to stock so I can get my WiFi and camera working and get the OTA updates.
Phone specs as follows
M7_UL pvt ship s-on RH
hboot - 1.44.0000
radio - 4A.17.3250.20_10.40.1150.04L
OpenDSP - V31.120.274.0617
eMMC - boot
Jul 5 2013,16:04:18:-1
Android 4.1.2
HTC Sense: 5.0
Build no: 1.26.502.15 CL213167 Release-keys
kernel ver: 3.4.16-g0a0f902
[email protected] #1
smp preempt
image crc:
rpm: 0x5c2b29fe
sbl1: 0x3eabf110
sbl2: 0xa35fe42a
sbl3: 0xe8ef6c99
tz: 0x5b8ab6c5
radio: 0x13bcf252
hboot: 0xb7620927
boot: 0xf0cadd9b
recovery: 0xcb9d7d41
system: 0xba29c7c6
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
First things first, you are lucky to be on 1.44; let's get you S-OFF using revone. Redownload the revone file and make sure to follow the instructions. If it doesn't work, quote my post with details about what didn't work and copy/paste of your terminal windows, and I'll try to help.

attanasi0 said:
First things first, you are lucky to be on 1.44; let's get you S-OFF using revone. Redownload the revone file and make sure to follow the instructions. If it doesn't work, quote my post with details about what didn't work and copy/paste of your terminal windows, and I'll try to help.
Click to expand...
Click to collapse
OK, tried revone again. Keep getting error 2.
Code:
Script started on Thu 31 Oct 2013 05:06:36 AM EDT
@TOSHIBA-NB305 ~/Downloads $ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT34LW904090 device
@TOSHIBA-NB305 ~/Downloads $ adb push revone /data/local/tmp
2179 KB/s (648208 bytes in 0.290s)
@TOSHIBA-NB305 ~/Downloads $ adb shell
[email protected]:/ # su
[email protected]:/ # cd /data/local/tmp
[email protected]:/data/local/tmp # ls
boot_backup.img
revone
[email protected]:/data/local/tmp # chmod 755 revone
[email protected]:/data/local/tmp # ./revone -P
revone v0.2.1
revone failed (error code = 2)
2|[email protected]:/data/local/tmp # exit
2|[email protected]:/ # exit
@TOSHIBA-NB305 ~/Downloads $ exit
Script done on Thu 31 Oct 2013 05:08:27 AM EDT

gvarnadoe said:
OK, tried revone again. Keep getting error 2.
Code:
Script started on Thu 31 Oct 2013 05:06:36 AM EDT
@TOSHIBA-NB305 ~/Downloads $ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT34LW904090 device
@TOSHIBA-NB305 ~/Downloads $ adb push revone /data/local/tmp
2179 KB/s (648208 bytes in 0.290s)
@TOSHIBA-NB305 ~/Downloads $ adb shell
[email protected]:/ # su
[email protected]:/ # cd /data/local/tmp
[email protected]:/data/local/tmp # ls
boot_backup.img
revone
[email protected]:/data/local/tmp # chmod 755 revone
[email protected]:/data/local/tmp # ./revone -P
revone v0.2.1
revone failed (error code = 2)
2|[email protected]:/data/local/tmp # exit
2|[email protected]:/ # exit
@TOSHIBA-NB305 ~/Downloads $ exit
Script done on Thu 31 Oct 2013 05:08:27 AM EDT
Click to expand...
Click to collapse
Are you with T-Mobile by any chance ?

attanasi0 said:
Are you with T-Mobile by any chance ?
Click to expand...
Click to collapse
No, I am on AT&T
Sent from my HTC One using xda app-developers app

I suspect that when I tried Moonshine it corrupted something and that is causing the problems.
Sent from my HTC One using xda app-developers app

gvarnadoe said:
No, I am on AT&T
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Your hboot is dated "Jul 5 2013,", so that's the patched version (so neither moonshine nor revone will work), you need to downgrade, check this thread for the ATT downgrade link: http://forum.xda-developers.com/showthread.php?t=2431515

Since you want the OTAs, I suggest you flash the stock nandroid from here, take the OTAs, then S-off with rumrunner.
I'm not sure if you have the Dev Edition or the AT&T 64 GB, but attempting to downgrade on my Dev Edition resulted in a soft brick and a phone out of commission for 4 days. So beware.

mojitochica said:
Since you want the OTAs, I suggest you flash the stock nandroid from here, take the OTAs, then S-off with rumrunner.
I'm not sure if you have the Dev Edition or the AT&T 64 GB, but attempting to downgrade on my Dev Edition resulted in a soft brick and a phone out of commission for 4 days. So beware.
Click to expand...
Click to collapse
I have the AT&T 64GB. I managed to get it straightened out by using Rumrunner then flashing the Google Play edition RUU. That gave me what I wanted to reach originally. Now I just need to see if there is a way to fix the tint in the camera.
Thanks for all the help from everyone who posted!

[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?

revone help needed (avoiding htcdev)

fastboot getvar all
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 1.00.20.0626
version-cpld: None
version-microp: None
version-main: 1.31.651.2
version-misc: PVT SHIP S-ON
serialno: FA389S907331
imei: ###############
meid: ###############
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4239mV
partition-layout: Generic
security: on
build-mode: SHIP
Adb log
[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)
I bought Two phones Friday both m7wls one black one blue. my black one unlocked/s-off fine through revone and was able to put recovery and custom rom with little issues. However when i tried same process with the blue one i get segmentation fault error every time and i have uninstalled/re-installed drivers for phone, never installed htc sync on my pc(windows 7 32 bit), disabled htc sync on phone, tried on clean install of windows(windows 8) after installing all drivers, factory reset phone several times(once from bootloader). I know i could be done in less than 10 if i went through htcdev but for me that's an option i refuse to take, so please help if you can!, within the one parameter (no htcdev)

reserved for logs and solution
reserved for logs and solution if one is found

Look HERE
Nevermind it requires TWRP which means you have to unlock

Prerequisites: unlocked, custom recovery
bigdaddy619 said:
Look HERE
Click to expand...
Click to collapse
"Make sure you have dev unlocked and you flashed a custom recovery"- Second line in post

nazs said:
"Make sure you have dev unlocked and you flashed a custom recovery"- Second line in post
Click to expand...
Click to collapse
Maybe an issue with your ADB shell? I have 'Revoned' twice now, the last time was this morning on my new blue ONE and both times I used terminal on the phone itself. Followed the steps and done. Even went back and did './revone -t' to remove the 'tampered' flag in fastboot. No issues. Try it that way and see what you get.....when you first pull up your term(I use Terminal Emulator), type 'su' (no quotes).......

You must unlock your boot loader. However after running this or even rum runners you can lock it again with a fastboot command and it WILL NOT read "relocked"

Updating my Firmware before Flashing Viper ROM 7.0

Hey guys,
Super excited about the new 7.0 release of Viper and ready to get my phone tearing it up again.
I'd like some advice on which firmware to update fully to get things running best as possible before flashing Viper 7.0.
I'm coming from basically stock 6.20, and TWRP 6.2.3.3 atm.
I'll go ahead and drop my fastboot getvar all below.
Should just be a few minutes because I'm backing up atm and then good to go.
Can't wait...
Thanks in advance for the help it's much appreciated - brothers!
You guys are seriously fantastic.
I'd thumbs up each and every one of you fine folks.
-SD

C:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34YW905216
(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: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-152f57d927912d0704cf7272206b5fa2f
getvar:all FAILED (unknown status code)
finished. total time: 0.066s

*PS*
^^^^^

SyntheticDynamics said:
Hey guys,
Super excited about the new 7.0 release of Viper and ready to get my phone tearing it up again.
I'd like some advice on which firmware to update fully to get things running best as possible before flashing Viper 7.0.
I'm coming from basically stock 6.20, and TWRP 6.2.3.3 atm.
-SD
Click to expand...
Click to collapse
IMO, get S-OFF then flash the firmware that the ROM is based on. Based on your low hboot you could probably start with revone S-OFF. This would give you much more flexibility in the future. Don't forget to make a nandroid of your present system and save it off of your phone. Stuff happens!!!

majmoz said:
IMO, get S-OFF then flash the firmware that the ROM is based on. Based on your low hboot you could probably start with revone S-OFF. This would give you much more flexibility in the future. Don't forget to make a nandroid of your present system and save it off of your phone. Stuff happens!!!
Click to expand...
Click to collapse
Alright that's a good place to start...
I was thinking about going S-OFF actually, so this may be right down my alley.
I've already got the nandroid backups saved and I'm copying it off my phone.

Why don't you S-OFF your phone before?

majmoz said:
IMO, get S-OFF then flash the firmware that the ROM is based on. Based on your low hboot you could probably start with revone S-OFF. This would give you much more flexibility in the future. Don't forget to make a nandroid of your present system and save it off of your phone. Stuff happens!!!
Click to expand...
Click to collapse
danielr18 said:
Why don't you S-OFF your phone before?
Click to expand...
Click to collapse
I'm in the process of trying to get it S-OFF'd.
ADB isn't recognizing the device for doing the revone method.
Firewater might be another option.

Also use this thread:
http://forum.xda-developers.com/showthread.php?t=2419699

danielr18 said:
Also use this thread:
http://forum.xda-developers.com/showthread.php?t=2419699
Click to expand...
Click to collapse
Alright, thanks and I'm ready to get this thing up and running soon!
:good:
-SD

SyntheticDynamics said:
I'm in the process of trying to get it S-OFF'd.
ADB isn't recognizing the device for doing the revone method.
Firewater might be another option.
Click to expand...
Click to collapse
Here is the method I used many moons ago. If it works great!
Written instructions:
 Download the Revone file and transfer it to your phone (or download on your phone)
 Use a root file explorer and paste the file inside the /data/local/tmp folder
 Open a terminal emulator and type of the following:
su (enter)
cd /data/local/tmp (enter)
chmod 755 revone (enter) (IF revone doesn’t work, type revone.bin)
./revone -P (enter)
 Reboot
 Open terminal again and type:
su (enter)
cd /data/local/tmp (enter)
./revone -s 0 -u (That would be a ZERO) (enter)
 Reboot
 That’s it! To get rid of the tampered, or relock, follow instructions below
To remove “tampered”
open terminal
cd /data/local/tmp
su
./revone.bin -t
These are other commands that you can fill in above to
-u – Unlock the device
-l – Lock the device (as if it was never unlocked)
-r – Relock the device (mark the device as relocked)
-t – Reset the device’s tamper flag.

SyntheticDynamics said:
I'm in the process of trying to get it S-OFF'd.
ADB isn't recognizing the device for doing the revone method.
Firewater might be another option.
Click to expand...
Click to collapse
Maybe you are using old adb. Here you have the adb & fastboot from last sdk.
Try to check if you have installed the drivers

majmoz said:
Here is the method I used many moons ago. If it works great!
Written instructions:
 Download the Revone file and transfer it to your phone (or download on your phone)
 Use a root file explorer and paste the file inside the /data/local/tmp folder
 Open a terminal emulator and type of the following:
su (enter)
cd /data/local/tmp (enter)
chmod 755 revone (enter) (IF revone doesn’t work, type revone.bin)
./revone -P (enter)
 Reboot
 Open terminal again and type:
su (enter)
cd /data/local/tmp (enter)
./revone -s 0 -u (That would be a ZERO) (enter)
 Reboot
 That’s it! To get rid of the tampered, or relock, follow instructions below
To remove “tampered”
open terminal
cd /data/local/tmp
su
./revone.bin -t
These are other commands that you can fill in above to
-u – Unlock the device
-l – Lock the device (as if it was never unlocked)
-r – Relock the device (mark the device as relocked)
-t – Reset the device’s tamper flag.
Click to expand...
Click to collapse
I have the steps done thus far -
 Download the Revone file and transfer it to your phone (or download on your phone)
 Use a root file explorer and paste the file inside the /data/local/tmp folder
How do I open the Terminal Emulator?
Is that similar to ADB?

SyntheticDynamics said:
I have the steps done thus far -
 Download the Revone file and transfer it to your phone (or download on your phone)
 Use a root file explorer and paste the file inside the /data/local/tmp folder
How do I open the Terminal Emulator?
Is that similar to ADB?
Click to expand...
Click to collapse
The terminal method all takes place on the phone it's self
you download Terminal Emulator from the play store

clsA said:
The terminal method all takes place on the phone it's self
you download Terminal Emulator from the play store
Click to expand...
Click to collapse
Thank you sir!
Just downloaded it.

SyntheticDynamics said:
I have the steps done thus far -
 Download the Revone file and transfer it to your phone (or download on your phone)
 Use a root file explorer and paste the file inside the /data/local/tmp folder
How do I open the Terminal Emulator?
Is that similar to ADB?
Click to expand...
Click to collapse
You can download one from the Play Store. This is the one I used.

I'm in the Terminal Emulator now.
Here is the progress.
Works all the way until I hit....
.revone -P
revone v0.2.1
revone failed (error code = 1)

majmoz said:
You can download one from the Play Store. This is the one I used.
Click to expand...
Click to collapse
It's not letting me push revone.
Getting device not found/recognized...
-SD

SyntheticDynamics said:
I'm in the Terminal Emulator now.
Here is the progress.
Works all the way until I hit....
.revone -P
revone v0.2.1
revone failed (error code = 1)
Click to expand...
Click to collapse
Are you entering .revone -P or ./revone -P? If you cannot get this to work you may have to go to rumrunner or firewater.

majmoz said:
Are you entering .revone -P or ./revone -P? If you cannot get this to work you may have to go to rumrunner or firewater.
Click to expand...
Click to collapse
Yeah I'm entering ./revone -P and getting the following.
revone failed (error code =1)
Can you walk me through rumrunner or firewater?
Thank you,
SD

SyntheticDynamics said:
Yeah I'm entering ./revone -P and getting the following.
revone failed (error code =1)
Can you walk me through rumrunner or firewater?
Thank you,
SD
Click to expand...
Click to collapse
Here are the steps to rumrunner S-OFF.
Here are the steps to firewater S-OFF.