Ok so I recently just ruu my Rezound (though an exe file not zip) and Now I'm trying to install Amon Ra so I can re-root my phone anyways here is what I type in and this is what I get
Fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
and this is what I get
Sending 'recovery' <7078kb>... OKAY [1.480s]
writing 'recovery' ... failed <remote: not allowed>
what Am I doing wrong?
Sounds like you aren't bootloader unlocked.
I think RUUs relock, but I am not sure.
GrayTheWolf said:
Sounds like you aren't bootloader unlocked.
I think RUUs relock, but I am not sure.
Click to expand...
Click to collapse
you're right my man above Vigor PVT it says locked (on hboot) but I am S-off still do I need to reunlock the bootloader or will S-off just work it's magic?
You have to be bootloader unlocked to write recovery. But once you do that, doesn't matter after that.
croonux said:
you're right my man above Vigor PVT it says locked (on hboot) but I am S-off still do I need to reunlock the bootloader or will S-off just work it's magic?
Click to expand...
Click to collapse
if you have jphboot then put the recovery in a ph98zip and load in bootloader, if you have stock hboot then you would have to unlock to get amon ra to flash. i used jphboot but somehow messed up memory during the process and redid the ruu. then i had stock hboot and unlocked.
croonux said:
Ok so I recently just ruu my Rezound (though an exe file not zip) and Now I'm trying to install Amon Ra so I can re-root my phone anyways here is what I type in and this is what I get
Fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
and this is what I get
Sending 'recovery' <7078kb>... OKAY [1.480s]
writing 'recovery' ... failed <remote: not allowed>
what Am I doing wrong?
Click to expand...
Click to collapse
ive read about a few people still having to unlock if your s-off but on any other hboot than the jpbear.. if you chose not to install the jpbear hboot when you s-offed then your stock bootloader you kept relolocks itself by default..
Related
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
I'm as new to the forums as you, but I did a little messing and reading around. In order to return your phone to the same way you bought it, you need to downgrade hboot to version 1.4 and then run the RUU.exe of your firmware version (I'm not sure which version it is for your phone, it was 2.17.651.5 for me but I got my phone with hboot 1.5). The downgrade thread is here [it's very tricky to brick it, make sure the light is a solid faint red (NOT BLINKING) in order to do it successfully]. Hopefully someone else can tell you which RUU version to use (to run before the downgrade if you get the *Security Warning* in hboot, as well as the one to use after in order to return to the way you were when you got the phone). I just downloaded all the RUU's and ran them all until one worked.
LesbianSeagull said:
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
Click to expand...
Click to collapse
Hi, did you unlock and root your phone using the HTC method?
If so I think I may be able to help.
koty2012 said:
Hi, did you unlock and root your phone using the HTC method?
If so I think I may be able to help.
Click to expand...
Click to collapse
I think it was the Revolutionary method. Can't remember for sure since I did it quite a long time ago.
LesbianSeagull said:
I think it was the Revolutionary method. Can't remember for sure since I did it quite a long time ago.
Click to expand...
Click to collapse
Pm me your email, and if you'd like I could email you the RUU I have and you could see if it'll work. I'll walk you through it. You have gmail right?
Bizarre1 said:
I'm as new to the forums as you, but I did a little messing and reading around. In order to return your phone to the same way you bought it, you need to downgrade hboot to version 1.4 and then run the RUU.exe of your firmware version (I'm not sure which version it is for your phone, it was 2.17.651.5 for me but I got my phone with hboot 1.5). The downgrade thread is here [it's very tricky to brick it, make sure the light is a solid faint red (NOT BLINKING) in order to do it successfully]. Hopefully someone else can tell you which RUU version to use (to run before the downgrade if you get the *Security Warning* in hboot, as well as the one to use after in order to return to the way you were when you got the phone). I just downloaded all the RUU's and ran them all until one worked.
Click to expand...
Click to collapse
Just tried that, but I got the same HBOOT error message and I couldn't start the update in order to brick.
LesbianSeagull said:
Just tried that, but I got the same HBOOT error message and I couldn't start the update in order to brick.
Click to expand...
Click to collapse
Since you got that error, you need to flash the 2.08 or 2.17 RUU.exe to get rid of it. Try running the RUU while in the fastboot menu, and make sure you have the HTC drivers installed on your computer.
Have you tried both RUUs to no avail?
*Edit: I believe the drivers will install if you install HTC sync. Unfortunately I cant post the link to it, but just do a Google for HTC Evo 3D drivers. It's on HTC's website
koty2012 said:
Pm me your email, and if you'd like I could email you the RUU I have and you could see if it'll work. I'll walk you through it. You have gmail right?
Click to expand...
Click to collapse
PM'd and thanked
Bizarre1 said:
Since you got that error, you need to flash the 2.08 or 2.17 RUU.exe to get rid of it. Try running the RUU while in the fastboot menu, and make sure you have the HTC drivers installed on your computer.
Have you tried both RUUs to no avail?
Click to expand...
Click to collapse
Tried both
Code:
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Both of which gave me the same error. the RUU connects over fastbootusb but halts at a specific point in the install, so I assume I have the right HTC drivers. I can find the install point in question if that would help.
Tried both
Code:
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Both of which gave me the same error. the RUU connects over fastbootusb but halts at a specific point in the install, so I assume I have the right HTC drivers. I can find the install point in question if that would help.
Click to expand...
Click to collapse
That's really strange. Just to make sure you have the right drivers, go to Control Panel and then to Device Manager and see if your phone is there. It should be under "Android USB devices" or the like. Also, is USB debugging on before the going into hboot?
*Edit: Some more little things, HTC Sync should be uninstalled from your computer, and your phone should be locked.
LesbianSeagull said:
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
Click to expand...
Click to collapse
Did you flash the vm firmware ??
#Root-Hack_Mod*Always\
laie1472 said:
Did you flash the vm firmware ??
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I used the instructions and download links from androidadvices(dot)com/update-htc-evo-3d-cdma-leaked-ics-403-firmware/. Reading the instructions now I see that I didn't put the phone into USB recovery mode. I can't get back into the ROM to do so and I can't get into my recovery either.
Your currently on hboot 1.57 and thats your your getting an update fail since 2.17 RUU has hboot1.50 Im not sure their is a way to downgrade this firmware unless you try the downgrade method for hboot 1.50 but that could maybe cause in a permanent brick.
iTzLOLtrain said:
Your currently on hboot 1.57 and thats your your getting an update fail since 2.17 RUU has hboot1.50 Im not sure their is a way to downgrade this firmware unless you try the downgrade method for hboot 1.50 but that could maybe cause in a permanent brick.
Click to expand...
Click to collapse
I'm trying that now. Hopefully it works!
So I tried bricking the phone using Unknownforce's method but everytime I would try and flash the 2.17 PG86IMG file in fastboot I get the same Hboot Version error. I also tried the Shooter_ICS_35_S_Sprint zip by renaming it to PG86IMG and and flashing in fastboot (since it has the matching hboot version), but I get a CID incorrect error. I'm trying to unlock my bootloader by using the HTC method in order to change the CID, but when I do so it gives me this in terminal.
Code:
C:\rootevo3dnew>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.159s
C:\rootevo3dnew>fastboot oem writecid htc__001
...
(bootloader) shooter_init_sd, SD card already power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.198s]
finished. total time: 0.198s
My bootloader still says it's locked but the unlock_code.bin in ADB looks like it's working. Can anyone tell me what is happening? This is the only thing holding me back from downgrading and it's frustrating
LesbianSeagull said:
So I tried bricking the phone using Unknownforce's method but everytime I would try and flash the 2.17 PG86IMG file in fastboot I get the same Hboot Version error. I also tried the Shooter_ICS_35_S_Sprint zip by renaming it to PG86IMG and and flashing in fastboot (since it has the matching hboot version), but I get a CID incorrect error. I'm trying to unlock my bootloader by using the HTC method in order to change the CID, but when I do so it gives me this in terminal.
Code:
C:\rootevo3dnew>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.159s
C:\rootevo3dnew>fastboot oem writecid htc__001
...
(bootloader) shooter_init_sd, SD card already power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.198s]
finished. total time: 0.198s
My bootloader still says it's locked but the unlock_code.bin in ADB looks like it's working. Can anyone tell me what is happening? This is the only thing holding me back from downgrading and it's frustrating
Click to expand...
Click to collapse
Hey sorry I so abrubtly had to go earlier, did you try again to flash the cwm.img? If you can get into backup and restore I feel as if you might be able to just go back to the previous hboot and ROM you had , not making any promises though.
koty2012 said:
Hey sorry I so abrubtly had to go earlier, did you try again to flash the cwm.img? If you can get into backup and restore I feel as if you might be able to just go back to the previous hboot and ROM you had , not making any promises though.
Click to expand...
Click to collapse
Just gave it another shot, but I got the same error:
Code:
C:\rootevo3dnew>fastboot flash boot cwm.img
sending 'boot' (4832 KB)...
OKAY [ 1.130s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.928s
EDIT: Also tried running the 2.17 RUU again and it fails after attempting a signature check as well.
LesbianSeagull said:
Just gave it another shot, but I got the same error:
Code:
C:\rootevo3dnew>fastboot flash boot cwm.img
sending 'boot' (4832 KB)...
OKAY [ 1.130s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.928s
EDIT: Also tried running the 2.17 RUU again and it fails after attempting a signature check as well.
Click to expand...
Click to collapse
I believe you don't flash that as boot. You flash cwm.img (clock work mod) as a recovery. Try
C:\rootevo3dnew>fastboot flash recovery cwm.img
*Edit: make sure your cwm.img is in your C:\rootevo3dnew folder.
Then after that, boot into the bootloader and go to recovery to access clockwork mod. See if you have any backups (which will save you a TON of pain by putting you back on hboot 1.4 with whatever former ROM you backed it up with)
Sent from my Evo 3D using XDA
Bizarre1 said:
I believe you don't flash that as boot. You flash cwm.img (clock work mod) as a recovery. Try
C:\rootevo3dnew>fastboot flash recovery cwm.img
*Edit: make sure your cwm.img is in your C:\rootevo3dnew folder.
Then after that, boot into the bootloader and go to recovery to access clockwork mod. See if you have any backups (which will save you a TON of pain by putting you back on hboot 1.4 with whatever former ROM you backed it up with)
Sent from my Evo 3D using XDA
Click to expand...
Click to collapse
Tried it, still gave me the signature verification error. I think it's because the bootloader is locked.
bump
Is there anything else I can try???
I know someone on XDA has to have a solution to this...
LesbianSeagull said:
Is there anything else I can try???
I know someone on XDA has to have a solution to this...
Click to expand...
Click to collapse
You have to be unlocked to flash the recovery image. Does it not say its unlocked at the top of HBOOT after using the HTC method?
Sent from the mobile paperweight itself!
hi guys, i have a big problem, i have an htc evo 3d gsm hboot 1.49.0007 S-OFF but i can't use fastboot, it gives me this error, for example i wanted to flash a boot.img:
c:\Android>fastboot flash boot boot.img
sending 'boot' (3720 KB)...
OKAY [ 0.861s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.179s
why? what can i do?
Peppero said:
hi guys, i have a big problem, i have an htc evo 3d gsm hboot 1.49.0007 S-OFF but i can't use fastboot, it gives me this error, for example i wanted to flash a boot.img:
c:\Android>fastboot flash boot boot.img
sending 'boot' (3720 KB)...
OKAY [ 0.861s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.179s
why? what can i do?
Click to expand...
Click to collapse
Read this post for an explanation.
You will need to either HTC unlock your bootloader, which is not recommended since it will leave a flag on your phone that it was modified, or flash a custom bootloader for your model. I don't have links to any for a GSM phone but I'm sure someone else can help.
ramjet73
ramjet73 said:
Read this post for an explanation.
You will need to either HTC unlock your bootloader, which is not recommended since it will leave a flag on your phone that it was modified, or flash a custom bootloader for your model. I don't have links to any for a GSM phone but I'm sure someone else can help.
ramjet73
Click to expand...
Click to collapse
ehm..but i have S-OFF RL, revolutionary, so i have already a custom bootloader....maybe method E of this post can help me? :/ http://forum.xda-developers.com/showthread.php?t=1743466
Peppero said:
ehm..but i have S-OFF RL, revolutionary, so i have already a custom bootloader....maybe method E of this post can help me? :/
Click to expand...
Click to collapse
I'm not familiar with the GSM hboots and didn't recognize 1.49.0007 as a Revolutionary version, but since you are S-OFF you could try flashing one of the JBear modified bootloaders from this page. I know they support the extended fastboot commands like "flash" and "erase". You might have to flash it from your current bootloader as PG86IMG.zip in the root of your SD card.
ramjet73
ramjet73 said:
Read this post for an explanation.
You will need to either HTC unlock your bootloader, which is not recommended since it will leave a flag on your phone that it was modified, or flash a custom bootloader for your model. I don't have links to any for a GSM phone but I'm sure someone else can help.
ramjet73
Click to expand...
Click to collapse
ramjet73 said:
I'm not familiar with the GSM hboots and didn't recognize 1.49.0007 as a Revolutionary version, but since you are S-OFF you could try flashing one of the JBear modified bootloaders from this page. I know they support the extended fastboot commands like "flash" and "erase". You might have to flash it from your current bootloader as PG86IMG.zip in the root of your SD card.
ramjet73
Click to expand...
Click to collapse
ok, i have solved, after the method E i have used the revolutionary method and now i have hboot 1.49.1107 revolutionary, hboot 1.49.0007 was not revolutionary xD
Same hboot as me, you may now back up your gb crap (nandroid) flash the updated your firmware and flash away, the bonus is you can flash any Rom with that hboot. As I have not had any bootloops, from miui, sense 3.6 or sense 4.1
Sent from my HTC EVO 3D X515m using Tapatalk 2
Hi guys,
Bought a Evo 3D second hand... GSM version.
Got it home, had a custom stock rom on it and had Revolutionary Recovery on it.
I flashed a MIUI rom to it and have been using that fine for a few months, now i have come to install a different rom and it installs fine but won't boot. It either stays on the bootscreen forever or just reboot cycles the phone.
Now the bootloader is unlocked but it doesn't have S-OFF.
I think i need to S-OFF to flash the roms correctly.
Here's whats on it:
Rom: MIUI v2.10.26
Baseband: 11.77.3504.00U_11.25.3504.06_M
HBOOT: 1.53.0007
Recovery: 4EXT recovery
HBOOT says:
*** UNLOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.007
eMMC-BOOT
May 22 2012, 01:06:07
Just want to provide as much info as possible...
It would be fantastic if you could help me
Thanks
bump!
I suggest you RUU back to stock and use this guide to get s-off
http://forum.xda-developers.com/showthread.php?t=1743466
EM|NEM said:
I suggest you RUU back to stock and use this guide to get s-off
http://forum.xda-developers.com/showthread.php?t=1743466
Click to expand...
Click to collapse
I have downloaded RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed
And i get Error 155 when flashing. I have also downloaded the .zip version and when i try and flash it from recovery it says it cant and the file is bad.
flyboyovyick said:
And i get Error 155 when flashing.
Click to expand...
Click to collapse
Lock your bootloader with the "fastboot oem lock" command and run the RUU again.
ramjet73
ramjet73 said:
Lock your bootloader with the "fastboot oem lock" command and run the RUU again.
ramjet73
Click to expand...
Click to collapse
This is what i get: http://puu.sh/2ndCW
EDIT: Now says relocked in HBOOT gonna flash RUU
Flashed the stock RUU, now i'm trying to unlock the bootloader again via HTCDev.com and when i copy the Identifier Token it says its too short. I am pretty sure i'm copying it correctly
solved... There were spaces in the box
So i am now S-OFF, i need to downgrade my HBOOT still...
How do i do that?
Right, managed to downgrade the HBOOT but still, when i flash AOKP it stays on the splashscreen forever....
http://forum.xda-developers.com/showthread.php?t=1906172
use this hboot. and wipe everything(data and cache) before flashing aokp
As the title specifics, I currently have no OS or recovery on my Droid DNA. I'm S-On and Locked. all i have access to is fastboot, no recovery. I'm trying to get back to stock so that i can bring it in to vzw. any idea how i can unlock and install my recover?
thanks
EDIT: some more details on my problem - i initially had it unlocked/s-off via moonshine. currently, its version 2.06 (doesn't boot), hboot version 1.33.0001. the only thing that correctly installs is dna2.06firmware.zip.
RUU doesn't complete (error 158). installing PL83IMG.zip and PL8320000-DNA.zip doesn't work either. not sure where to go now.
read in this section, this problem has been answered many times
hyphydragon said:
read in this section, this problem has been answered many times
Click to expand...
Click to collapse
I've read through many of the threads but unfortunately none of them help with my problem
snazztasticmatt said:
As the title specifics, I currently have no OS or recovery on my Droid DNA. I'm S-On and Locked. all i have access to is fastboot, no recovery. I'm trying to get back to stock so that i can bring it in to vzw. any idea how i can unlock and install my recover?
thanks
EDIT: some more details on my problem - i initially had it unlocked/s-off via moonshine. currently, its version 2.06 (doesn't boot), hboot version 1.33.0001. the only thing that correctly installs is dna2.06firmware.zip.
RUU doesn't complete (error 158). installing PL83IMG.zip and PL8320000-DNA.zip doesn't work either. not sure where to go now.
Click to expand...
Click to collapse
You need to flash Stock Hboot and then RUU
http://forum.xda-developers.com/showpost.php?p=42352912&postcount=4
piled onedati
finanandroid said:
You need to flash Stock Hboot and then RUU
http://forum.xda-developers.com/showpost.php?p=42352912&postcount=4
Click to expand...
Click to collapse
it doesn't flash. this is the message i get when i try to flash it:
Code:
sending 'zip' (434 KB)...
OKAY [ 0.202s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.254s
heres what fastboot says:
Code:
*** TAMPERED ***
*** LOCKED ***
MONARUDO PVT SHIP S-ON
HBOOT-1.33.0001
RADIO-1.01.04.0308
OpenDSP-v6.120.274.0114
eMMC-boot
Mar 9 2013,17:46:45:-1
Hello all, I've been trying to restore my droid dna back to stock for a warranty return. I have relocked my bootloader using http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19 method and restored with the stock 1.15 RUU. Now this is where the problems start. I had achieved "Relocked" with no tampered or security warnings in my bootloader. However, I wanted to see if I could achieve "Locked" to cover all tracks of tampering with the software. I tried the moonshine method of s-offing and it continuously failed. I would get to moonshining (10) before my phone would completely freeze with screen on and CMD showing "Waiting for device" never moving on to another step. OFC to moonshine I had to update to the 2.06 which I think has now caused all the problems. I cannot downgrade using the original 1.15 RUU because I get Error 158 (image error) after it tried to update signature. I have tried http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19 by flashing the hboot which gives the error:
C:\android-sdk\platform-tools>fastboot flash zip PL83IMG.zip
sending 'zip' (434 KB)...
OKAY [ 0.201s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.255s
lastly I tried HTC dev, the original method of rooting I used. Trying from the start as well as just simply trying to use the original unlock code file.
C:\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.126s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.134s
No luck and I'm running out of time because if I don't mail my phone tomorrow I will be charge for the replacement. Im begging for help. :[
Bootloader reads:
Tampered
Relocked
Monarudo pvt ship s-on
Hboot 1.33.0001
Radio-1.01.04.0308
OpenDSP-v4.120.240.0920
emmc-boot
Mar 9 2013,17:46:45:-1
Try rumrunner to s-off again.
Sent from my DNA using my mind.
Uzephi said:
Try rumrunner to s-off again.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Thanks for the reply!
I checked out the website and read all the prereqs,
"Your device must be HTCDEV unlocked or rooted unless using rumrunner with a device blocked by htcdev (e.g. m7wlv)"
My phone is no longer rooted, and the issue is I cannot figure out how to unlock it. My phone was never s-off if that matters. It was rooted through htcdev before anyone found out how to s-off.
Nevx said:
Thanks for the reply!
I checked out the website and read all the prereqs,
"Your device must be HTCDEV unlocked or rooted unless using rumrunner with a device blocked by htcdev (e.g. m7wlv)"
My phone is no longer rooted, and the issue is I cannot figure out how to unlock it. My phone was never s-off if that matters. It was rooted through htcdev before anyone found out how to s-off.
Click to expand...
Click to collapse
"Unless using a device blocked by htcdev". Our device is blocked. You are good to go. Keep on reading the instructions after that, and follow them exactly.
Edit: after s-off is achieved, follow the guide "how to return to stock s-on" thread.
http://forum.xda-developers.com/showthread.php?t=2293919
Sent from my DNA using my mind.
Uzephi said:
"Unless using a device blocked by htcdev". Our device is blocked. You are good to go. Keep on reading the instructions after that, and follow them exactly.
Edit: after s-off is achieved, follow the guide "how to return to stock s-on" thread.
http://forum.xda-developers.com/showthread.php?t=2293919
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Alright, I'm giving it a try. Everything is working smoothly so far. Now, after I have rebooted and s-off unlocked boot loader, I can restore to factory stock everything and boot loader will show "locked" instead of relocated and tampered etc?
EDIT: It worked, when I used the relock method and that worked fine, but now I have tampered above locked. The tampered remove method didn't work
.
RUU and keep everything stock. Should remove tampered tag
Sent from my DNA using my mind.
Uzephi said:
RUU and keep everything stock. Should remove tampered tag
Sent from my DNA using my mind.
Click to expand...
Click to collapse
RR worked beautifully, everything worked after following a few methods on the RUU, Hboot, recovery, and what not. Droid DNA is stock, S-ON Locked and ready for warranty return.
So much trouble for a non functioning audio jack...
Thank you for your help Uzephi!
EDIT: Thread good to be marked as resolved and locked if need be!