Database Develop

[Q] after Official 2.3.5 with sens 3.0 my incredible S transform into brick..

I bought my phone about a mount ago.. in store have told to me that phone is s-on and official and i believed in it(( After official update from htc it stoped working. Work only recovery and -revolutionary-.
this is info in it:
info frm revolutionary
"vivo pvt ship s-off rl
hboot-6.13.1002
radio-3805.06.03.03_M
eMMC-boot
apr 1 2011, 18:34:39"
phone info
imei: 358000045678255
s/n: HT1A2TD03837
old OS: android 2.3.3
could anyone help me with this.. sry for my bad eng..

Ertey said:
I bought my phone about a mount ago.. in store have told to me that phone is s-on and official and i believed in it(( After official update from htc it stoped working. Work only recovery and -revolutionary-.
this is info in it:
info frm revolutionary
"vivo pvt ship s-off rl
hboot-6.13.1002
radio-3805.06.03.03_M
eMMC-boot
apr 1 2011, 18:34:39"
phone info
imei: 358000045678255
s/n: HT1A2TD03837
old OS: android 2.3.3
could anyone help me with this.. sry for my bad eng..
Click to expand...
Click to collapse
The OTA update cannot be applied to a phone that was S-Off with Revolutionary. You should be able to pull the battery to reboot into Recovery mode and restore your backup to get going again.

official 2.3.5 with revolutionary S-OFF won't boot. Why don't give a try on ARHD 2.1 by mike?

keroro430 said:
official 2.3.5 with revolutionary S-OFF won't boot. Why don't give a try on ARHD 2.1 by mike?
Click to expand...
Click to collapse
i try it but it just don't want to setup.. in recovery then i want to install via sd card it says about signature and i can not turn it off in standart recovery(( in revolutionaty it don't setup too..

Same problem....
Can somebody tell WTF should I do to get the new frimware???? PLEASE HELP!

It is simple - restore S-ON and everything will be OK. Search this forum - there was nice manual to do that. Had this "fun" 2 days ago...

Which Recovery you are using? Give a try to 4EXTRecovery. And now, what is your Incs Bootloader version?

i tried to bring back s-on:
C:\ADB>fastboot flash hboot rom.zip
sending 'hboot' (257756 KB)...
OKAY [ 43.328s]
writing 'hboot'...
FAILED (remote: image error! (Platform check fail))
finished. total time: 43.328s
HBOOT now is 6.13.9999
and how could i setup new recovery when my phone is brick..

i want to write a recovery cwm, but..
C:\android-win-tools>fastboot flash recovery cwm.img
sending 'recovery' (3696 KB)... OKAY [ 1.328s]
writing 'recovery'...
about an hour i see this.. that a problem with it =\

You must go back to S-ON and everything is OK!!!

How to go back to S-ON..............

nikolaet said:
How to go back to S-ON..............
Click to expand...
Click to collapse
Please do not hijack a thread and then ask a question that isn't even relavent to the topic.
You need to search this forum and next time definitely give more information such as I used [fill in the blank] method to S-Off my IncS. What is the procedure I can use to get back to S-On?

Follow this beautiful guide go back to S-ON, tried myself AMD it works flawlessly..
http://forum.xda-developers.com/showthread.php?t=1359555
You should have the hboot version which you had previously..
Read carefully you will gain s-on..
After s-on run the RUU sense 3 exe file which you have downloaded but don't install from pc.. before doing this procedure you should make a goldcard.. search for that in google .. once you make a gold card, put the extracted file of that RUU from temp folder ( I guess you know how to do that ) , name it PG32IMG.zip and reboot your phone by pressing volume down+power phone will search for that file and follow on screen procedure.. it will install sense 3.0.. and your phone will start working again.. don't panic...
Info about making goldcard found here though it says for desire hd it works for incredible s too..
http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
PS : you have to make a gold card so your phone does not give you a signature error.. I was stuck with the same problem after updating the latest release but now my phone is working perfectly again..
Sent from my HTC Incredible S using Tapatalk

Nvr flash or ota update without fully reseaech.
Sent from my HTC Incredible S using XDA App

[Q] pls someone to help me HTC ONE M7

I am asking for help
HTC ONE M7
No OS, no any data no nothing
I try to use RUU to restore but its give me error 155
the phone is with unlocked bootloader and relocked again
what shall i do?
additionl info about the model
++++tampered++++
++++relocked++++
++Security Warning+++
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4A.17.3250.14
OpenDSP_v32.120.274.0909
OS-6.12.161.8
eMMC_boot 2048MB
sep 3 2014, 10:26:40​

Cirez said:
I am asking for help
HTC ONE M7
No OS, no any data no nothing
I try to use RUU to restore but its give me error 155
the phone is with unlocked bootloader and relocked again
what shall i do?
additionl info about the model
++++tampered++++
++++relocked++++
++Security Warning+++
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4A.17.3250.14
OpenDSP_v32.120.274.0909
OS-6.12.161.8
eMMC_boot 2048MB
sep 3 2014, 10:26:40​
Click to expand...
Click to collapse
There is no ruu you can use for that version with s-on.
If you have a nandroid backup of your phone, push it back and restore it.
You can also push a rom to your phone and install it from a custom recovery then optionally you can try to s-off using that rom and then restore back to stock using a ruu with s-off
and btw questions must be posted in the q&a section not in general (a moderator will probably move you thread there)

alray said:
There is no ruu you can use for that version with s-on.
If you have a nandroid backup of your phone, push it back and restore it.
You can also push a rom to your phone and install it from a custom recovery then optionally you can try to s-off using that rom and then restore back to stock using a ruu with s-off
and btw questions must be posted in the q&a section not in general (a moderator will probably move you thread there)
Click to expand...
Click to collapse
Thank you but i don´t have nandroid back up
Can you please be more spasific i am little new in the forum
i try to flash with fastboot but its give me a error
target reported max download size of 1514139648 bytes
sending 'zip' (1313670 KB)...
OKAY [ 57.437s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 203.298s
can you please send me a post
thank you in advance and sorry about the post here
i will know for next time

for reference, OP started a second thread here in the q&a: http://forum.xda-developers.com/htc-one/help/help-suggestion-to-t2929174
thanks

[Q] Need help desperately - Back to stock

I was using the latest Viper Rom and my Camera busted on my phone. So naturally I needed to get the M7 back to stock. I have never done it before so I did some searching and found the method right in this same forum.
So Walking through the instructions everything went well
I locked the bootloader
went through the process of flashing the stock rom with fastboot and it keeps erroring out. I am consistently getting "FAILED (status read failed (Too many links))" I tried the RUU and I keep getting unknown errors from those too. I have tried multiple PC and different usb cables and ports. I am completely stumped.
I was under the impression that it didn't matter which stock ROM you tried but I did try many different ones.
Would anyone have any suggestions?

I'm not sure what RUU guide you used, but I and a few others have had success with the guide I wrote. Try it and follow up here or in that thread if you have issues (or if it worked for you).
http://forum.xda-developers.com/spr...de-reset-phone-using-ruu-htcfastboot-t2876110

Thanks for the links and the response. I followed your step to a tee and got to step 6 and tried to flash the firmware. I am s-off and when I pushed the firmware o am now getting;
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830
Any suggestions?
Thanks again for your help.

Just another thing I noticed with your guide
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
s-off means the bootloader is unlocked and s-on means that it is locked. so your instructions are a little unclear. I am assuming that you meant that you need the bootloader locked.
On a whim I unlocked my bootloader again using fastboot and my BIN file and my phone did finally boot back to the Viper rom instead of being stuck on the Bootloader screen. I am curious why going s-on is making the phone fail and soft bricking the phone. Maybe my HBOOT is wrong? Could my Twerk recovery corrupted HBOOT?
Thanks again for your help!

raremind said:
Thanks for the links and the response. I followed your step to a tee and got to step 6 and tried to flash the firmware. I am s-off and when I pushed the firmware o am now getting;
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830
Any suggestions?
Thanks again for your help.
Click to expand...
Click to collapse
raremind said:
Just another thing I noticed with your guide
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
s-off means the bootloader is unlocked and s-on means that it is locked. so your instructions are a little unclear. I am assuming that you meant that you need the bootloader locked.
On a whim I unlocked my bootloader again using fastboot and my BIN file and my phone did finally boot back to the Viper rom instead of being stuck on the Bootloader screen. I am curious why going s-on is making the phone fail and soft bricking the phone. Maybe my HBOOT is wrong? Could my Twerk recovery corrupted HBOOT?
Thanks again for your help!
Click to expand...
Click to collapse
I think this is the issue: since you are s-off, you should have ignored step 4 and not have locked your bootloader. A locked bootloader will not allow you to flash the firmware (it fails the security check since it wasn't created by HTC). Unlock your bootloader and try to flash the firmware file again. The reason I'm not sure is because it was my impression that an s-off phone ignores the locked/unlocked flag. But, I never lock my bootloader so I'm not sure.
By the way, s-off =/= unlocked and s-on =/= locked. Phones start as locked and s-on. Unlocking the bootloader through HTC Dev allows you to install custom recoveries and ROMs. However, it is limited because you are still s-on (security on). For example, you can only upgrade hboots, but can never downgrade to an older one. Same with RUUs. Being s-off is very flexible but more dangerous as you can access normally protected partitions. Hope that clears things up some.

Thank you again for your help. I seem to be a little more confused now. Line 4 of your guide states;
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
Click to expand...
Click to collapse
Why would I lock the the bootloader using "fastboot oem lock" if I already have s-on. You said you can not flash firmware with s-on but line 4 says I should before I flash firmware. What I just got from you, am I understanding right that I should not "fastboot oem lock" before you flash the firmware? If you are s-on the bootloader is already locked and you would not be able to do step 5.
I am s-off right now. Would I flash the firmware now, then s-on when run the RUU?

Unlocked bootloader does not = s-off.
My guess is you are unlocked not s-off.
S-OFF explained - by a Developer

So if I need to update the firmware do I need to be s-on or s-off? I need to get the phone back to stock and am having a really hard time.

raremind said:
So if I need to update the firmware do I need to be s-on or s-off? I need to get the phone back to stock and am having a really hard time.
Click to expand...
Click to collapse
Easiest way to go back to stock is to RUU. If you are s-on you need to re-lock (it will tell you in bootloader if you are s-on or s-off)
Updating firmware can be done s-on (need to re-lock bootloader) or s-off (no locking required).

BD619 said:
Easiest way to go back to stock is to RUU. If you are s-on you need to re-lock (it will tell you in bootloader if you are s-on or s-off)
Updating firmware can be done s-on (need to re-lock bootloader) or s-off (no locking required).
Click to expand...
Click to collapse
That's just the thing. I am s-on and relocked and every RUU I have tried failed. I have tried it with fastboot the exe and everything else under the sun. Everything I have tried has failed. here is what I am seeing:
Code:
*** TAMPERED ***
*** RELOCKED ***
*** Security warning ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO- 1.01.20.0984_2
OpenDSP- v32.120.274.0909
OS-5.05.651.2
eMMC-boot 2048MB
Sep 24 2014, 16:58:42:0
I rooted and flashed TEAMWIN recovery and Viper 7.1 - My Camera started acting up and I couldn't talk on calls so I wanted to get it back to stock. The only thing I was able to do successfully trying to get it back to stock was lock the bootloader. Everything beyond that has failed.
This is what I get updating the firmware:
Code:
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking..
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830s
This is what I got when I locked the bootloader:
Code:
D:\Downloads\HTC\Try this\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.199s
Trying to flash RUU I get:
Code:
D:\Downloads\HTC\Try this\Minimal ADB and Fastboot>fastboot flash zip Sprint_HTC
_One_m7wls_1.29.651.7_encrypted_ROM.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1029700 KB)...
OKAY [ 37.166s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 133.077s
Running the RUU.exe I recieve an unknown error. Am I screwed?

Ok first off you are using the wrong RUU.
You need to use the 5.05.651.2 RUU

So, you are s-on and relocked (you said s-off before so that threw me off). Because you are s-on, you may not be successful flashing the firmware, hence the security warning in the first box (see the link explaining s-off that @BD619 left). I probably need to fix my guide to reflect that issue. In the second box, you get an error trying to relock which makes sense since you are already locked. In the third box, it looks like you get an error since you are trying to flash an older RUU (not allowed since you are s-on).
At this point, as BD said, you should be able to just go here and download the ruu exe (it's the first link). I run it as an administrator just to be safe. Follow the prompts and wait around ten minutes for it to do its thing.
Don't get too frustrated. The (forced) learning process from this is very valuable. BD and I are just members who have been on here long enough to have a good understanding of what's going on. Not speaking for BD, but I started on here knowing next to nothing about Android except it's based on Linux.

Not speaking for BD, but I started on here knowing next to nothing about Android except it's based on Linux.
Click to expand...
Click to collapse
You knew more then me lol.
My first couple posts were me begging for help because I bricked my sons Epic 4G Touch lol (posted in Development...reasoning I thought it would get more exposure and I would get helped faster lol)

BD619 said:
(posted in Development...reasoning I thought it would get more exposure and I would get helped faster lol)
Click to expand...
Click to collapse
Haha, noob! I would have replied with "Cool ROM, bro".

Well thank you both! I was able to successfully flash the 5.05.651.2 RUU. Such a simple thing that was causing me such problems. I was under the impression that the RUU version didn't make a difference. I wish they would add that to the guides! Well thanks to both of you!

i need help with unlock bootloader

look my htc one on that mode is
tampered <--- I THINk because i once used king root from pc i though it will do it all but no
***UNLOCKED***
M7_UL PVT SHIP S_ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
0S-7.19.401.51
eMMC-BOOT 2048MB
Nov 16 2015,20:23:35.0
and i did every thing good in the unlock bootloader at the end it was saying
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.155s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.166s
But nothing was happening on my phone but my phone is still
tampered
unlocked even when i reboot bootloader

Titanscream said:
look my htc one on that mode is
tampered <--- I THINk because i once used king root from pc i though it will do it all but no
***UNLOCKED***
M7_UL PVT SHIP S_ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
0S-7.19.401.51
eMMC-BOOT 2048MB
Nov 16 2015,20:23:35.0
and i did every thing good in the unlock bootloader at the end it was saying
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.155s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.166s
But nothing was happening on my phone but my phone is still
tampered
unlocked even when i reboot bootloader
Click to expand...
Click to collapse
So what exactly is your issue? Your bootloader is unlocked

donkeykong1 said:
So what exactly is your issue? Your bootloader is unlocked
Click to expand...
Click to collapse
no because when i am doing step 10 of unlocker there pop nothing up in my screen
and i want it unlocked not tampered

Titanscream said:
no because when i am doing step 10 of unlocker there pop nothing up in my screen
and i want it unlocked not tampered
Click to expand...
Click to collapse
Nothing is happening after step 10 because your bootload is already unlocked :
***UNLOCKED***
M7_UL PVT SHIP S_ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
0S-7.19.401.51
eMMC-BOOT 2048MB
Nov 16 2015,20:23:35.0
Click to expand...
Click to collapse
***TAMPERED*** is only a warning telling that someone tampered with the phone, exactly what you did. So what is the problem exactly?
And btw why did you started a new thread for the same issue?
http://forum.xda-developers.com/htc-one/help/help-t3301948

alray said:
Nothing is happening after step 10 because your bootload is already unlocked :
***TAMPERED*** is only a warning telling that someone tampered with the phone, exactly what you did. So what is the problem exactly?
And btw why did you started a new thread for the same issue?
http://forum.xda-developers.com/htc-one/help/help-t3301948
Click to expand...
Click to collapse
ooh thanks my phone is succesfully rooted and working good now can you help me my htc one m7 always is on 37-42 Celsius is there any app to reduce the overheating because when its overheating like that my camera is pink i want to fix it but i dont want to get my camera out of my phone i aint good at it if you know what i mean

Titanscream said:
ooh thanks my phone is succesfully rooted and working good now can you help me my htc one m7 always is on 37-42 Celsius is there any app to reduce the overheating because when its overheating like that my camera is pink i want to fix it but i dont want to get my camera out of my phone i aint good at it if you know what i mean
Click to expand...
Click to collapse
The pink tint in the camera is a well known issue and can only be repaired by replacing the camera sensor by a new model. 37-42 is pretty normal but you could try to undervolt and underclock the CPUs to decrease the performance and so the temperature but to be honest, I don't think it will change anything. So your 2 options are:
Send your phone to repair (camera change)
Don't send it and live with the fact that your pictures will often have a pink tint.

Trying to restore an old HTC One M7 to stock

Greetings,
Going through some boxes the other day I found my old HTC One M9, which I had previously unlocked and flashed with various different ROMs.. Basically, this was the first device I ever actually tried any custom ROMs. That said, it's been so long, I don't have any of my old files left and I don't remember exactly what I did.
At this moment in time, the device is booting and running Xiaomi MIUI 8 (Android 6), but I'm unable to get into TWRP (constant bootloop) and I can't flash a new recovery image.
After a "fastboot reboot bootloader", I see the following details:
Code:
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.54.000
RADIO-4T.36.3218.06
OpenDSP-v26.120.274.0202
OS-
eMMC-boot 2048MB
Apr 28 2015,09:16:24.0
When I try flash "twrp-3.3.1-1-hima.img", I get the following:
Bash:
> fastboot flash recovery twrp-3.3.1-1-hima.img
Sending 'recovery' (21852 KB) OKAY [ 2.072s]
Writing 'recovery' FAILED (remote: 'image update error')
fastboot: error: Command failed
I'm hoping to flash LineageOS from this thread, either 16.0 (as per the thread details) or the 17.1 or 18.1 available in the linked repository, but I can't do so until I get the recovery partition sorted out.
Please can someone help me fix whatever it was that I broke here..?
---
Please note: originally, I accidentally posted this in the M9 forum. I'm now creating this to replace that thread...
There was a suggestion to just try flashing the boot image first, and effectively worry about recovery later. So I will jump on that, as soon as I have this annoying "no permissions" issue with fastboot. But I do want to post this here in the meantime, just in case somebody has any other bright ideas.

..and I just realised I was trying to use the "hima" recovery, which is the codename for the One M9. I'm really out of the Android flashing game these days..
Suffice to say, this is somewhat embarrassing. Let me go try this again, using the proper files this time. I'll update things again soon..

So guess what, with the correct files, things actually flash.. Amazing how that works hey?
Anyways, after all that, I got it sorted. Flashing LineageOS now.

Nice to see some good old HTC One M7 posts these days haha