Hey guys before I started doing anything my phone had Cyanogen Mod on it. I have to return it back to Verizon within 5 days so I am trying to get it completely back to stock. I was following tutorials on how to LOCK the bootloader and turn S-ON. I ended up in the bootloader and there is no chance of starting the phone. I downloaded a couple of RUUs and tried flashing them from fastboot and the signature check fails because of S-ON most likely. Can someone please give me a short guide on how to get out of this whole mess and the proper order of how to do things. Unless someone knows where I can find a RUU that will pass signature check with S-ON.
Currently my bootloader screen looks like this:
*** TAMPERED ***
*** RELOACKED ***
*** Security Warning ***
S-ON
Thanks in Advance!!!
HunterT said:
Hey guys before I started doing anything my phone had Cyanogen Mod on it. I have to return it back to Verizon within 5 days so I am trying to get it completely back to stock. I was following tutorials on how to LOCK the bootloader and turn S-ON. I ended up in the bootloader and there is no chance of starting the phone. I downloaded a couple of RUUs and tried flashing them from fastboot and the signature check fails because of S-ON most likely. Can someone please give me a short guide on how to get out of this whole mess and the proper order of how to do things. Unless someone knows where I can find a RUU that will pass signature check with S-ON.
Currently my bootloader screen looks like this:
*** TAMPERED ***
*** RELOACKED ***
*** Security Warning ***
S-ON
Thanks in Advance!!!
Click to expand...
Click to collapse
your screwed unless you can get s-off back ... never go s-on with tampered / relocked bootloader
For real? I'm done for?
clsA said:
your screwed unless you can get s-off back ... never go s-on with tampered / relocked bootloader
Click to expand...
Click to collapse
Are you serious? I followed this video and in his video his phone goes to LOCKED, mine never went to LOCKED it went to RELOCKED so I just continued with the tutorial and turned S-ON which I guess was a big mistake because then when I restarted the TAMPERED MESSAGE came up.
I was following this thread to lock it.
http://forum.xda-developers.com/showthread.php?t=2314582&nocache=1
When I did ./revone -l and checked the bootloader it said RELOCKED not LOCKED
HunterT said:
Are you serious? I followed this video and in his video his phone goes to LOCKED, mine never went to LOCKED it went to RELOCKED so I just continued with the tutorial and turned S-ON which I guess was a big mistake because then when I restarted the TAMPERED MESSAGE came up.
I was following this thread to lock it.
http://forum.xda-developers.com/showthread.php?t=2314582&nocache=1
When I did ./revone -l and checked the bootloader it said RELOCKED not LOCKED
Click to expand...
Click to collapse
check @nkk71 SuperGuide here >>
http://forum.xda-developers.com/showthread.php?t=2541082
HunterT said:
Hey guys before I started doing anything my phone had Cyanogen Mod on it. I have to return it back to Verizon within 5 days so I am trying to get it completely back to stock. I was following tutorials on how to LOCK the bootloader and turn S-ON. I ended up in the bootloader and there is no chance of starting the phone. I downloaded a couple of RUUs and tried flashing them from fastboot and the signature check fails because of S-ON most likely. Can someone please give me a short guide on how to get out of this whole mess and the proper order of how to do things. Unless someone knows where I can find a RUU that will pass signature check with S-ON.
Currently my bootloader screen looks like this:
*** TAMPERED ***
*** RELOACKED ***
*** Security Warning ***
S-ON
Thanks in Advance!!!
Click to expand...
Click to collapse
Unlock bootloader again
install TWRP
install Custom Rom
install custom kernel
make it S Off
Remove Tempered use LINK
Run RUU according to your CID & MID and your Need
Edit: Never mind :/
Sent from my HTC One using XDA Free mobile app
yatindroid said:
Unlock bootloader again
install TWRP
install Custom Rom
install custom kernel
make it S Off
Remove Tempered use LINK
Run RUU according to your CID & MID and your Need
Click to expand...
Click to collapse
he's Verizon ... he has to be s-off to unlock the bootloader
So not chance I am getting out of this one?
clsA said:
he's Verizon ... he has to be s-off to unlock the bootloader
Click to expand...
Click to collapse
There are no RUU's out there that will work with S-ON?
HunterT said:
There are no RUU's out there that will work with S-ON?
Click to expand...
Click to collapse
RUU's
http://bit.ly/vzwone-15
S-off RUU (decrypted)
http://flyhalf205.com/?dir=RUU/m7vzw
http://forum.xda-developers.com/showthread.php?t=2765784
http://forum.xda-developers.com/showthread.php?t=2764109
That pretty much covers all your options at this point
I downloaded the for one on your list
clsA said:
RUU's
http://bit.ly/vzwone-15
Click to expand...
Click to collapse
I downloaded the first one on your list and used fastboot oem rebootRUU
Then I did fastboot flash zip rom.zip
It seems to have gotten passed the signature check but then when parsing I got a too many links error.
(bootloader) adopting the signature contained in this images...
(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
(bootloader) FAILED (status read failed (Too many links))
seems like the closest I got to getting it working actually.
any ideas?
HunterT said:
(bootloader) adopting the signature contained in this images...
(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
seems like the closest I got to getting it working actually.
any ideas?
Click to expand...
Click to collapse
Android_info fail check cid mid software no. match ?
from HTC One
HunterT said:
I downloaded the first one on your list and used fastboot oem rebootRUU
Then I did fastboot flash zip rom.zip
It seems to have gotten passed the signature check but then when parsing I got a too many links error.
(bootloader) adopting the signature contained in this images...
(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
(bootloader) FAILED (status read failed (Too many links))
seems like the closest I got to getting it working actually.
any ideas?
Click to expand...
Click to collapse
Android_info fail could also mean the RUU is older than your current software
you can't flash older RUU without s-off
Way out
clsA said:
Android_info fail could also mean the RUU is older than your current software
you can't flash older RUU without s-off
Click to expand...
Click to collapse
There has to be a way out of this. I am willing to do absolutely anything. Am I really trapped with S-ON,TAMPERED AND RELOCKED?
HunterT said:
There has to be a way out of this. I am willing to do absolutely anything. Am I really trapped with S-ON,TAMPERED AND RELOCKED?
Click to expand...
Click to collapse
hboot version ?
OS / software / version main ?
Or gatvar all without imei & serial number
from HTC One
I have the same problem as the threadstarter. Apologies, I mean no disrespect but I don't want to create another thread having the same problem.
(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: SH34JW902721
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4058mV
(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
HunterT said:
There has to be a way out of this. I am willing to do absolutely anything. Am I really trapped with S-ON,TAMPERED AND RELOCKED?
Click to expand...
Click to collapse
hboot is 1.55 so use rumrunner or firewater & get S Off you every problem will gone
sandykalugdan said:
I have the same problem as the threadstarter. Apologies, I mean no disrespect but I don't want to create another thread having the same problem.
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
Click to expand...
Click to collapse
you don't have the same problem as the OP, he's on Verizon, which means he can't use HTCdev to unlock, so he's in a seriously bad situation, what problem do you have?
Sorry for saying I have same problem.
I guess we are in the same situation, stuck in bootloader, tampered, relocked, s-on but I using a HTC One International version. It was running with cyanogenmod 11 and I decided to go back to stock and I have this problem.
sandykalugdan said:
Sorry for saying I have same problem.
I guess we are in the same situation, stuck in bootloader, tampered, relocked, s-on but I using a HTC One International version. It was running with cyanogenmod 11 and I decided to go back to stock and I have this problem.
Click to expand...
Click to collapse
No need to apologize, you may be in a similar situation, but the OP has a real problem because he can't unlock his bootloader; in your case:
* just go to HTCdev, get a new unlocktocken,
* unlock bootloader again
* flash back custom recovery
* install ROM
sandykalugdan said:
I have the same problem as the threadstarter. Apologies, I mean no disrespect but I don't want to create another thread having the same problem.
Click to expand...
Click to collapse
The OP has a Verizon phone with locked bootloader and s-on. How is you situation alike?
Whoops little late
Sent from my HTC One_M8 using Tapatalk 4
Related
So back story goes like this.
Broke screen, got replacement from insurance. Want to put phone back to stock.
Device is currently (relocked and s-off) hboot 1.44
Has no root though, as I used RUU to get back to stock 1.27 on T-Mobile.
I have complete functional adb and fastboot and I'm knowledgeable with them.
Just can't figure out how to get SU pushed to the phone so I can revert bootloaders messages showing (relocked & get s-on) to show a fully stock phone. I know it might not matter with insurance and phone being replaced already and that jazz... Just want to do this for peace of mind, as I'm not trying to pay 600$ to them just in case they flag my phone.
Here is my getvar all
C:\adb>fastboot getvar all
(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.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36HW911407
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4268mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.078s
mt3g said:
So back story goes like this.
Broke screen, got replacement from insurance. Want to put phone back to stock.
Device is currently (relocked and s-off) hboot 1.44
Has no root though, as I used RUU to get back to stock 1.27 on T-Mobile.
I have complete functional adb and fastboot and I'm knowledgeable with them.
Just can't figure out how to get SU pushed to the phone so I can revert bootloaders messages showing (relocked & get s-on) to show a fully stock phone. I know it might not matter with insurance and phone being replaced already and that jazz... Just want to do this for peace of mind, as I'm not trying to pay 600$ to them just in case they flag my phone.
Here is my getvar all
C:\adb>fastboot getvar all
(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.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36HW911407
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4268mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.078s
Click to expand...
Click to collapse
http://www.htc1guru.com/guides/guru-bootloader-reset/
flash this in CWM/TWRP.
Choose locked nd remove Tampered flag. Then, u can send it in
raghav kapur said:
http://www.htc1guru.com/guides/guru-bootloader-reset/
flash this in CWM/TWRP.
Choose locked nd remove Tampered flag. Then, u can send it in
Click to expand...
Click to collapse
Problem is I can't get a custom recovery to stick, flashing recovery in fastboot doesn't work.
mt3g said:
Problem is I can't get a custom recovery to stick, flashing recovery in fastboot doesn't work.
Click to expand...
Click to collapse
Thats because ur bootloader is relocked.
Unlock your bootloader via HTC dev
Then flash the custom recovery and then, the zip file i semt you
raghav kapur said:
Thats because ur bootloader is relocked.
Unlock your bootloader via HTC dev
Then flash the custom recovery and then, the zip file i semt you
Click to expand...
Click to collapse
Currently in that process, thanks.
mt3g said:
Currently in that process, thanks.
Click to expand...
Click to collapse
or with S-OFF you can zip a custom recovery.img in a firmware.zip and flash it via RUU mode even with a locked bootloader.
raghav kapur said:
Thats because ur bootloader is relocked.
Unlock your bootloader via HTC dev
Then flash the custom recovery and then, the zip file i semt you
Click to expand...
Click to collapse
alray said:
or with S-OFF you can zip a custom recovery.img in a firmware.zip and flash it via RUU mode even with a locked bootloader.
Click to expand...
Click to collapse
I'm just laughing at myself over here.
So I have root, I have TRWP installed. I have tried the file from HTC1GURU and it will simply not do anything to my bootloader no tampered removal or locking is being done, no errors are showing though...
I tried using revone its a no go as well, all is fine but get the error-1 after entering ./revone -l any ideas guys? I'm so close but things just are not going my way haha. Thanks for the help .
mt3g said:
I'm just laughing at myself over here.
So I have root, I have TRWP installed. I have tried the file from HTC1GURU and it will simply not do anything to my bootloader no tampered removal or locking is being done, no errors are showing though...
I tried using revone its a no go as well, all is fine but get the error-1 after entering ./revone -l any ideas guys? I'm so close but things just are not going my way haha. Thanks for the help .
Click to expand...
Click to collapse
which twrp version are you using? Crushalot specify to use twrp 2.6.3.3 with his tool. NVM he said at least twrp 2.6.3.3 so higher version should be fine.
alray said:
which twrp version are you using? Crushalot specify to use twrp 2.6.3.3 with his tool. NVM he said at least twrp 2.6.3.3 so higher version should be fine.
Click to expand...
Click to collapse
I'm gonna try 2.7
why wouldn't revone work though?
mt3g said:
I'm gonna try 2.7
why wouldn't revone work though?
Click to expand...
Click to collapse
its been a while since I used revone but I think you must have root for it to work correctly.
alray said:
its been a while since I used revone but I think you must have root for it to work correctly.
Click to expand...
Click to collapse
I hate being an idiot, 2.7 worked. I'm locked going to set s-on and run the RUU and put the phone in its box and take a nap or something lol. Thanks again for the help guys.
mt3g said:
I hate being an idiot, 2.7 worked. I'm locked going to set s-on and run the RUU and put the phone in its box and take a nap or something lol. Thanks again for the help guys.
Click to expand...
Click to collapse
don't forget to remove the tampered flag before! (you probably already did just in case)
alray said:
don't forget to remove the tampered flag before! (you probably already did just in case)
Click to expand...
Click to collapse
aaaaaand I Gotta start over lol.
mt3g said:
aaaaaand I Gotta start over lol.
Click to expand...
Click to collapse
really? :laugh:
alray said:
really? :laugh:
Click to expand...
Click to collapse
Ya no joke... I'm so drained lol. The phone is stuck in bootloader can't boot around it recovery or anything. Guess I'll be here helping people out in the future with my knowledge that I've gained.
now I can't even attain s-off lol... got it unlocked with the ugly tampered warning still up there.
Tried rumrunner, firewater all in one tool kit... should i run the ruu again then attempt to proceed?
Why'd I have to skip the stupid tampered part!!!????
mt3g said:
now I can't even attain s-off lol... got it unlocked with the ugly tampered warning still up there.
Tried rumrunner, firewater all in one tool kit... should i run the ruu again then attempt to proceed?
Why'd I have to skip the stupid tampered part!!!????
Click to expand...
Click to collapse
Bumpin for help puhleasee
Sent from my HTC One using XDA Premium 4 mobile app
mt3g said:
now I can't even attain s-off lol... got it unlocked with the ugly tampered warning still up there.
Tried rumrunner, firewater all in one tool kit... should i run the ruu again then attempt to proceed?
Why'd I have to skip the stupid tampered part!!!????
Click to expand...
Click to collapse
well, you need a working OS to use rumrunner or firewater. It cannot be done in fastboot mode. So, ideally, adb sideload ARHD to ur phone. Flash it. Then run the S-OFF tool of ur choice
raghav kapur said:
well, you need a working OS to use rumrunner or firewater. It cannot be done in fastboot mode. So, ideally, adb sideload ARHD to ur phone. Flash it. Then run the S-OFF tool of ur choice
Click to expand...
Click to collapse
Already have a booted OS with root.
Sent from my HTC One using XDA Premium 4 mobile app
mt3g said:
Already have a booted OS with root.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
use Revone if u have HBOOT 1.44
Hey guys need ur help with going back to stock.Essentially I flashed the stock ruu and locked the bootloader and toggled my device from S-OFF to S-ON but i forgot to flash the stock recovery after rooting my phone using TWRP. Now my device is S-ON with bootloader locked and with custom recovery.I tried to use revone-0.2.1 to S-OFF and then unlock my bootloader but after few tries it says successful but when i checked the bootloader it shows S-ON and tampered.I even used firewater thta was also unsuccessful so please i need urgent help.
P.S My phone is still rooted.
You don't need to soff to flash stock recovery. You need unlocked bootloader. Unlock it using aio kit and you can flash stock recovery after that. You cannot flash recovery with a locked bootloader.
Sent from my All Metal HTC One.
Android 4.4.2 - Sense 6.0
well i tried using revone's option of unlocking bootloader shows error code -1
Hboot is 1.44
and if ur talking about using the unlock bin code i need stock recovery for that.Can someone provide me a signed stock recovery as i tried to flash a recovery from ruu but it shows signature verification failure.
Bump need urgent help
Slim Shady said:
Bump need urgent help
Click to expand...
Click to collapse
what's your current "fastboot getvar all" (except IMEI and s/n)
nkk71 said:
what's your current "fastboot getvar all" (except IMEI and s/n)
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(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: 1.29.707.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4179mV
(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.044s
Slim Shady said:
C:\adb>fastboot getvar all
(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: 1.29.707.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_u
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
finished. total time: 0.044s
Click to expand...
Click to collapse
well I couldn't find signed ruu, OTA, or signed firmware for your version, so best to start over from the beginning (unlock, s-off, etc), and do it again.
but one thing:
Essentially I flashed the stock ruu and locked the bootloader and toggled my device from S-OFF to S-ON but i forgot to flash the stock recovery after rooting my phone using TWRP
Click to expand...
Click to collapse
the RUU already has stock recovery, so why would you have TWRP there?
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.
nkk71 said:
what's your current "fastboot getvar all" (except IMEI and s/n)
Click to expand...
Click to collapse
nkk71 said:
well I couldn't find signed ruu, OTA, or signed firmware for your version, so best to start over from the beginning (unlock, s-off, etc), and do it again.
but one thing:
the RUU already has stock recovery, so why would you have TWRP there?
Click to expand...
Click to collapse
actually after applying the ruu i rooted the phone using twrp then locked the bootloader and then S-on the device.
Slim Shady said:
actually after applying the ruu i rooted the phone using twrp then locked the bootloader and then S-on the device.
Click to expand...
Click to collapse
see my last edit:
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.
Thats what I thought... restoring via RUU restores the recovery also.
nkk71 said:
see my last edit:
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.
Click to expand...
Click to collapse
Not even able to access twrp now. Is there any way u can help me ???
Slim Shady said:
Not even able to access twrp now. Is there any way u can help me ???
Click to expand...
Click to collapse
why can't you access TWRP
anyway, start from the beginning, unlock, s-off, etc.
nkk71 said:
why can't you access TWRP
anyway, start from the beginning, unlock, s-off, etc.
Click to expand...
Click to collapse
tried firewater not working asking to start the process again saying nasty chaser , then tried revone it reports success but when i check the bootloader it says s-on i just don't know what to do.
What happens when you choose recovery from bootloader?
finally success took a leap of faith used unlock token from htc and it worked yay.
Thanks to all the people who advised me and helped me troubleshoot.
can i run the ruu after i lock bootloader and return to s-on ???
also wanted to ask this
first i should get rid of tampered and lock my bootloader
then i should flash the ruu and them i should go S-on
right ?
Slim Shady said:
can i run the ruu after i lock bootloader and return to s-on ???
also wanted to ask this
first i should get rid of tampered and lock my bootloader
then i should flash the ruu and them i should go S-on
right ?
Click to expand...
Click to collapse
can you check my guide on how to do it: http://forum.xda-developers.com/showthread.php?t=2541082
RUU.ZIP method using this http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
this is a decrypted ruu.zip, so it only works with S-OFF.
got a new problem tampered text is not going away
getting error code -2 with revone
Slim Shady said:
got a new problem tampered text is not going away
Click to expand...
Click to collapse
WHY?? (how about more details next time )
EDIT: read the guide!!
nkk71 said:
WHY?? (how about more details next time )
EDIT: read the guide!!
Click to expand...
Click to collapse
Actually issue was dd commands and revone wasn't working for tampered so tried the guru rest and voila it worked.Now atlast everything's back to stock now i can give htc my phone and tell them to change it or repair it cause of the imsi issue im facing with the phone which happened after i got jtag brick repair.
Hi guys, hope you can help me out...
I just rooted my HTC One (unlock bootloader and install TWRP recovery), WITHOUT installing any custom ROM (i just kept the factory OS, because i couldn't S-Off the phone in order to install the google play edition). The OS i had (and still have) is stock Android 4.4.3 with Sense 6.
The problem is that i need to lock the phone back (in order to benefit from the warranty - technical touchscreen problem).
I tried using Revone to lock the phone back, but i get an error: "Failed to open framebuffer device". I understand that revone doesn't work with hboot 1.57.
Could you please help me with the relocking/unrooting the phone (at least give me a link to a guide that is working for my phone configuration - hboot 1.57) ? And also could you tell me if i need a RUU, or i can just wipe/reinstall the current OS (which i never changed in the first place) ? And if i need a RUU, how can i find the one that was initially installed on the phone ?
Oh, and one more thing: at first, when my phone started, i had a Vodafone screen showing up, and some crappy apps preinstalled. After i rooted an installed twrp recovery, i don't get that vodafone screen anymore, an the crappy apps weren't preinstalled anymore.
Cheers and thanks in advance !
andreih8017 said:
Hi guys, hope you can help me out...
I just rooted my HTC One (unlock bootloader and install TWRP recovery), WITHOUT installing any custom ROM (i just kept the factory OS, because i couldn't S-Off the phone in order to install the google play edition). The OS i had (and still have) is stock Android 4.4.3 with Sense 6.
The problem is that i need to lock the phone back (in order to benefit from the warranty - technical touchscreen problem).
I tried using Revone to lock the phone back, but i get an error: "Failed to open framebuffer device". I understand that revone doesn't work with hboot 1.57.
Could you please help me with the relocking/unrooting the phone (at least give me a link to a guide that is working for my phone configuration - hboot 1.57) ? And also could you tell me if i need a RUU, or i can just wipe/reinstall the current OS (which i never changed in the first place) ? And if i need a RUU, how can i find the one that was initially installed on the phone ?
Oh, and one more thing: at first, when my phone started, i had a Vodafone screen showing up, and some crappy apps preinstalled. After i rooted an installed twrp recovery, i don't get that vodafone screen anymore, an the crappy apps weren't preinstalled anymore.
Cheers and thanks in advance !
Click to expand...
Click to collapse
Ok well first off you need s-off to set your bootloader to ***LOCKED*** and to get back to 100% stock. As your on Hboot 1.57 the only way to gain s-off is with Sunshine App. Which will cost $25 to use.
The stock Rom on your Device won't be a complete stock Rom either. When you unlock the bootloader the device is wiped along with some preload data (crappy apps) which is critical if you want the device back to stock. Or to be able to accept OTA updates. If the device is Vodafone I'm not sure there is an RUU but you should be able to get a full stock Rom from somewhere. Please post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting. And we can see what is available for you. But if you want to go 100% stock to reinstate your warranty you will need s-off first :good:
Danny201281 said:
Ok well first off you need s-off to set your bootloader to ***LOCKED*** and to get back to 100% stock. As your on Hboot 1.57 the only way to gain s-off is with Sunshine App. Which will cost $25 to use.
The stock Rom on your Device won't be a complete stock Rom either. When you unlock the bootloader the device is wiped along with some preload data (crappy apps) which is critical if you want the device back to stock. Or to be able to accept OTA updates. If the device is Vodafone I'm not sure there is an RUU but you should be able to get a full stock Rom from somewhere. Please post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting. And we can see what is available for you. But if you want to go 100% stock to reinstate your warranty you will need s-off first :good:
Click to expand...
Click to collapse
Hey, thanx for the quick answer !
This is the result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(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!
finished. total time: 0.054s
What do you mean by "Or to be able to accept OTA updates" ?? At his moment i won't be able to receive any updates anymore ? :crying:
Also, what about Firewater for S-OFF ?
andreih8017 said:
Hey, thanx for the quick answer !
This is the result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(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!
finished. total time: 0.054s
What do you mean by "Or to be able to accept OTA updates" ?? At his moment i won't be able to receive any updates anymore ? :crying:
Click to expand...
Click to collapse
Unlocking the bootloader wipes /data partition to prevent unauthorized access to your data. Problem is that HTC packed some of their stock apps in /data/preload which mean you don't have these apps anymore after unlocking the bootloader. When installing an ota update, there is a script verifying the integrity of each files to be patched, inluding apps normally present in /data/preload. After the script will find out that these apps are missing, the ota update installation will abort. So no your phone can't install ota update anymore unless you restore your phone back to stock (which can be done with s-off btw).
Also, what about Firewater for S-OFF ?
Click to expand...
Click to collapse
Its discontinued. Firewater was using online resources no more available to do its magic.
From what I see from your "getvar all" you have the pretty standard version of the M7. Follow nkk71's guide linked in my signature. You want to follow the procedure using the 1.28.401.7 ruu.zip
@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,
andreih8017 said:
@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,
Click to expand...
Click to collapse
To safely go back to s-on without risking tampered you should have done it before installing the OTA updates as explained in @nkk71 guide.
So now you should downgrade with the ruu again then set s-on then install OTA updates to avoid the tampered flag returning. :good:
andreih8017 said:
@alray
@Danny201281
I successfully did the following:
- S-OFF with Sunshine
- I got rid of "tampered" and "unlocked" in bootloader, by using nkk71's guide. Now it just says "locked".
- I flashed the 1.28.401.7 ruu zip
- I updated the software via OTA
Now the only thing left is to get back to S-ON, right ? How can i do this without risking the "tampered" sign (as explained in nkk71's guide) ? Any safer way ?
And btw, the result of getvar all is the same as before, except now is S-OFF instead of S-ON
Thanks,
Click to expand...
Click to collapse
how far did you go with the OTA's? as long as it's pre 7.xx (ie Lollipop), sunshine will still work, in case you the tampered sign back, you can use sunshine again to s-off, and redo it (the guide)
but as danny said, i (personally) only recommend it on 1.xx or 2.xx firmware.... i don't know the reason for tampered [sometimes/often] reappearing so i dont know what's involved or what triggers it
@Danny201281
@nkk71
i took a leap of faith and eneter the "fastboot oem writesecureflag 3" command. It worked like a charm. Afterwards i rebooted the bootloader 3 times and no "tampered" sign, but S-ON. I also rebooted the phone once and still no "tampered" sign, but S-ON. Guess it worked, right ?
As for the OTAs, i went until the last one available for HTC One - 6.09.401.11.
Thanks guys !
andreih8017 said:
@Danny201281
@nkk71
i took a leap of faith and eneter the "fastboot oem writesecureflag 3" command. It worked like a charm. Afterwards i rebooted the bootloader 3 times and no "tampered" sign, but S-ON. I also rebooted the phone once and still no "tampered" sign, but S-ON. Guess it worked, right ?
As for the OTAs, i went until the last one available for HTC One - 6.09.401.11.
Thanks guys !
Click to expand...
Click to collapse
You need to reboot the ROM three times at least, not the bootloader
Sent from my HTC One_M8 using Tapatalk
@nkk71
I did that also. Still working fine, "locked" and S-ON
Thanx,
andreih8017 said:
@nkk71
I did that also. Still working fine, "locked" and S-ON
Thanx,
Click to expand...
Click to collapse
cool, good to hear :good: :good:
[Fixed][Solution]
This should work for anyone who soft bricked there device but still has the 1.44 HBoot to allow them to still flash a recovery. I did not come up with any of this but was helped by nkk71 who showed me the way. I dealt with this problem for over 2 days now non-stop trying to fix it only missing 1 step that made all the difference.
This method is for a HTC One (M7) Sprint Variant:
-Be sure to use HTCDev to unlock your phone and flash a custom recovery. (I used TWRP)
-Be sure to have all the adb and fastboot exe files needed. If you bricked your phone you most likely already do but if not there are tons of links on the forums to help you get all the information you need from them.
-Check to make sure what RUU your phone is at by going into fastboot and using a cmd window type: fasboot getvar all. This will display your phones information. If you happen to be at 1.31 like my phone was you will need to do the next step, if not then find your recovery.
- Fix your version main to say 1.29.651.10 by editing the misc partition
Boot into recovery
In the recovery mount your device. I mounted all parts in TWRP.
Open a cmd window and doucle check that your device is connected by typing: adb devices
(If it shows a set up numbers and letters and then says recovery then that is your device.)
Now type: adb shell
type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
type: adb reboot bootloader
Once it loads back into the bootloader click on fastboot and check to see if your device is connected by typing: fastboot devices
If you see you device type: fastboot oem lock (This will relock your device)
- Now you are ready to run the RUU. (After it runs your phone is back to stock)
If any of this is confusing, there are links below that were used to get me through this. If you need to do this I wish you luck.
Original Post:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.
toxicfumes22 said:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.
Click to expand...
Click to collapse
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output
nkk71 said:
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output
Click to expand...
Click to collapse
1) C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4117mV
(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.059s
2) Yes on Sprint, but with no activation on this phone now.
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
BTW, Thank you for the response.
toxicfumes22 said:
BTW, Thank you for the response.
Click to expand...
Click to collapse
Sure, no problem.
toxicfumes22 said:
1) C:\adb\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
2) Yes on Sprint, but with no activation on this phone now.
Click to expand...
Click to collapse
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
toxicfumes22 said:
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
Click to expand...
Click to collapse
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
toxicfumes22 said:
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
Click to expand...
Click to collapse
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction
nkk71 said:
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
Click to expand...
Click to collapse
Nice trick, still learning a lot from you
alray said:
Nice trick, still learning a lot from you
Click to expand...
Click to collapse
it's an "old trick", i take no credit at all for it ... as long as hboot version is the same, fixing the version-main (using adb or even the "misctool" <- it's somewhere on xda, dont have a link handy atm) should work fine
extract:
Code:
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version... [I]<- this is where it would fail, without that fix[/I]
(bootloader) checking hboot version... [I]<- this is where it would fail if hboot is higher[/I]
(bootloader) start image[boot] unzipping & flushing...
nkk71 said:
Sure, no problem.
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction
Click to expand...
Click to collapse
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.
toxicfumes22 said:
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.
Click to expand...
Click to collapse
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.
New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(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.062s
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.
toxicfumes22 said:
New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(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.062s
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.
Click to expand...
Click to collapse
yes should work fine now, give it a try.
alray said:
yes should work fine now, give it a try.
Click to expand...
Click to collapse
nkk71 said:
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.
Click to expand...
Click to collapse
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.
toxicfumes22 said:
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.
Click to expand...
Click to collapse
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
All thanks for you
My only contribution here was to say "give it a try" :laugh:
alray said:
All thanks for you
My only contribution here was to say "give it a try" [emoji23]
Click to expand...
Click to collapse
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk
nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
I copied and pasted, its exactly what I used. If it's wrong let me know and I'll fix though.
Another update though is I am now Unlocked with S-Off w/o Tampered. Basically what I wanted.
Now should be my last questions, but it's a good idea to update to the newest firmware correct?
Firmware will never be able to stop me from achieve what I just did to fix the phone correct?
nkk71 said:
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
Yup, I was going to not do a thing until I had a response. I was just worried I'd somehow mess it up. Just one confirmation that it looked good was enough to give me confidence.
Close this thread mod.
I will move to my old thread: http://forum.xda-developers.com/htc-one/help/planning-to-buy-bricked-htc-one-m7-t3376521
MihailMojsoski said:
So, my HTC One M7 is bricked.
This is all the information:
I can get ONLY into fastboot and hboot.
The is is all the data from the phone when i go to hboot:
*** RELOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.18.161.51
eMMC-boot 2048MB
Nov 18 2015, 13:59:56.22095
Recovery is not working,
also when i start the phone it boots to HBOOT or FASTBOOT
Click to expand...
Click to collapse
And what was done to the phone before it got bricked?
alray said:
And what was done to the phone before it got bricked?
Click to expand...
Click to collapse
Don't know.
I got this phone from a friend.
Edit: Also when i try to flash recovery i get error:
FAILED (remote: signature verify fail)
MihailMojsoski said:
Don't know.
I got this phone from a friend.
Click to expand...
Click to collapse
So this is the broken phone you was planning to buy like you have explained in your other thread, why creating a new thread for this? You already have one with post #2 reserved by yourself for this purpose....
"your friend" probably relocked the bootloader with a custom recovery/rom installed. The phone can't boot custom software when the bootloader is locked. You'll have to unlock the bootloader or flash a ruu.
If a custom recovery was installed you'll probably not be able to unlock it since the unluck process requires the stock recovery installed on the phone.
This phone is s-on so you can only flash ruu same or newer version as the current version installed and unfortunately there is no ruu for this version. There's a way to bypass this but you'll need a custom working custom recovery......
Let's try to unlock your bootloader first using htcdev.com then report in your original thread and close this one.
Sent from my HTC One using XDA Labs
Edit: Also when i try to flash recovery i get error:
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
The bootloader is locked, you can't flash the recovery partition on a locked bootloader.
alray said:
So this is the broken phone you was planning to buy like you have explained in your other thread, why creating a new thread for this? You already have one with post #2 reserved by yourself for this purpose....
"your friend" probably relocked the bootloader with a custom recovery/rom installed. The phone can't boot custom software when the bootloader is locked. You'll have to unlock the bootloader or flash a ruu.
If a custom recovery was installed you'll probably not be able to unlock it since the unluck process requires the stock recovery installed on the phone.
This phone is s-on so you can only flash ruu same or newer version as the current version installed and unfortunately there is no ruu for this version. There's a way to bypass this but you'll need a custom working custom recovery......
Let's try to unlock your bootloader first using htcdev.com then report in your original thread and close this one.
Sent from my HTC One using XDA Labs
The bootloader is locked, you can't flash the recovery partition on a locked bootloader.
Click to expand...
Click to collapse
Hey, so i tried finding the right RUU but i failed.
Also this is my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.161.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT**********
(bootloader) imei: ***HIDE***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-7661b1d7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Edit: Also would this work: https://www.androidfilehost.com/?fid=24052804347763901
Edit2: I tried unlocking the bootloader, but when i selected "YES", it got stucked on a screen with 3 androids and when i pressed the power button it vibrated. I will try again but i will give it some time, and i will tell you if it will work.
Alray's right, the problem seems quite difficult to walk around. Maybe you can send the phone to http://www.fonefunshop.co.uk I'm almost certain they'll figure out a way to fix it.
You can try to unlock the bootloader.. That ruu is unlikely to get you out of this mess cause it seems you're on a newer firmware version. But again, it won't hurt to try.. especially at this stage.
monrokhoury said:
Alray's right, the problem seems quite difficult to walk around. Maybe you can send the phone to http://www.fonefunshop.co.uk I'm almost certain they'll figure out a way to fix it.
You can try to unlock the bootloader.. That ruu is unlikely to get you out of this mess cause it seems you're on a newer firmware version. But again, it won't hurt to try.. especially at this stage.
Click to expand...
Click to collapse
I unlocked the phone, but i fail to install a recovery.
Code:
C:\Users\User\Desktop>fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9594 KB)...
OKAY [ 1.227s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.338s
monrokhoury said:
Alray's right, the problem seems quite difficult to walk around. Maybe you can send the phone to http://www.fonefunshop.co.uk I'm almost certain they'll figure out a way to fix it.
You can try to unlock the bootloader.. That ruu is unlikely to get you out of this mess cause it seems you're on a newer firmware version. But again, it won't hurt to try.. especially at this stage.
Click to expand...
Click to collapse
Also i live in Macedonia, so i can't send them the phone.
I can only fix it manually.