Hello all,
So after reading through a metric-buttton of posts about getting s-off after the most recent OTA I have been unable to Re-unlock my Droid DNA. So just after the latest OTA I was running CM11, then I got the urge to switch ROMs again. Eventually I ended up on Cyanogen 10.2.1 just to play around. For some reason my radio got corrupted and I ran the 4.2.2 or 3.06 RUU. But a while ago I had heard that I had to relock the bootloader with:
Code:
fastboot oem lock
So I did. Then flashed the RUU and took the 4.4.2 OTA. Because I figured if it was the latest Android I may as well settle. But what can I say, Cyanogen is my distro of choice. So Now my bootloader reads RELOCKED and S-OFF. I've tried flashing TWRP but that failed. I've also tried firewater but it just said I already have S-OFF so it did nothing. Does anybody have any ideas what to try next?
Thank you for your help everybody.
I am having the same problem.
S-OFF before the latest OTA, had to relock to take OTA
now it shows S-OFF RELOCKED
cant flash recovery, it errors out.
target reported max download size of 1514139648 bytes
sending 'recovery' (8758 KB)...
OKAY [ 1.057s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.099s
any help would be appreciated. thanks
Droidel said:
I am having the same problem.
S-OFF before the latest OTA, had to relock to take OTA
now it shows S-OFF RELOCKED
cant flash recovery, it errors out.
target reported max download size of 1514139648 bytes
sending 'recovery' (8758 KB)...
OKAY [ 1.057s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.099s
any help would be appreciated. thanks
Click to expand...
Click to collapse
So what I ended up doing was re-flashing the old 3.06 bootloader, hboot, and radio. Then just going back to rumrunner to get s-off. But you have to turn s-on and get the bootloader back to locked before rumrunner actually worked, then from there just flash twrp and install whatever rom you like.
Willielikesmonkeys said:
So what I ended up doing was re-flashing the old 3.06 bootloader, hboot, and radio. Then just going back to rumrunner to get s-off. But you have to turn s-on and get the bootloader back to locked before rumrunner actually worked, then from there just flash twrp and install whatever rom you like.
Click to expand...
Click to collapse
How did you do that? I tried it but it doesn't let me and gives me this error FAILED (remote: not allowed)
Droidel said:
How did you do that? I tried it but it doesn't let me and gives me this error FAILED (remote: not allowed)
Click to expand...
Click to collapse
I SOLVED IT! This worked for me!!
http://forum.xda-developers.com/droid-dna/help/solved-flash-recovery-relocked-s-off-t2804435
Related
I have recently went through the following procedure.
re-locking my bootloader
(in fastboot, fastboot oem lock)
Running the 3.11.605.22 RUU (because I've had it before, and it's already downloaded, and I'm just trying to restore my phone how it was) with PH98IMG.zip
Unlocking my bootloader
I went through the HTCDev.com steps again, including getting a new Unlock_token (even though my old one was still there from the same RUU a month ago).
I get
C:\Android\sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.150s
I'm pretty technical (I work in IT) and I've done this procedure several times (including to a lot of other phones). Am I missing something? I've re-downloaded my Unlock_code several times, and tried using my old one, as well. I get this same error.
Does anyone else know of any trouble using HTCDev to unlock the 3.11.605.22 leak? I'm lost as to what to do. I have my nandroid backup of my old ROM on my SDCard, and my ultimate goal here is to flash my recovery (amon-ra 3.15) and restore my nandroid backup (and flash the corresponding kernel).
I seem to be stuck in the *** RELOCKED *** state.
---------------------------------------------------------------------------------------------\
After attempt number (20+), and constantly rebooting in between, it worked. Same command, same code. No moving files around.
So the lesson here? beware not trying it enough times?
Awkward! Thank you anyone who read this.
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!
Phone: HTC Evo 3D
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
I'm a newbie. Last week, I bought this phone from a lady. She told me it had already been flashed to Cricket (my current carrier). Using various threads on the forums here, I spent several hours trying to figure out how to get it to root with no luck.
I got the unlock_code.bin from HTCDev fine and placed it in my android-sdk folder.
I put my phone in FASTBOOT USB, entered "fastboot flash unlocktoken unlock_code.bin" and got back:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.161sOn my phone, I didn't receive the expected "Unlock Bootloader?" screen. It just remained in FASTBOOT USB mode.
I tried to do it all over again and had the same outcome.
I'm frustrated. I need help. How can I unlock my phone and get it to root?
pezastic said:
How can I unlock my phone and get it to root?
Click to expand...
Click to collapse
As far as i remember i has a similar problem and i had to run Ful RUU in order to unlock Bottloader.
pezastic said:
Phone: HTC Evo 3D
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
I'm a newbie. Last week, I bought this phone from a lady. She told me it had already been flashed to Cricket (my current carrier). Using various threads on the forums here, I spent several hours trying to figure out how to get it to root with no luck.
I got the unlock_code.bin from HTCDev fine and placed it in my android-sdk folder.
I put my phone in FASTBOOT USB, entered "fastboot flash unlocktoken unlock_code.bin" and got back:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.161sOn my phone, I didn't receive the expected "Unlock Bootloader?" screen. It just remained in FASTBOOT USB mode.
I tried to do it all over again and had the same outcome.
I'm frustrated. I need help. How can I unlock my phone and get it to root?
Click to expand...
Click to collapse
it may have something with where you put it. in my "root" folder is adb and fastboot ONLY. i put what i want in there just to flash it.
in other words
c:\documents and settings\user\desktop\root
fastboot flash unlock_token.bin
try to find fastboot and adb and copy them to their own folder. for me i named it "root"
No cigar
jaredl45600 said:
try to find fastboot and adb and copy them to their own folder. for me i named it "root"
Click to expand...
Click to collapse
I did that, creating the new "root" folder on my desktop, just like you did. I didn't know where to put unlock_code.bin, though, so I put it on the SD root. When I tried to flash it, I got back:
error: cannot load 'unlock_code.bin'So, I put unlock_code.bin in the newly created folder on my desktop. Then, reflashed and got:
sending 'unlocktoken' (0 KB)... OKAY [ 0.151s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.159sThat's a bit different from my previous response, but with the same outcome. There is no option to proceed forward, and the top of the screen says the same thing. :crying:
Am I doing something wrong?
Flash RUU then unlock bootloader.
Still... after all these years
luis4ever said:
Flash RUU then unlock bootloader.
Click to expand...
Click to collapse
Which ruu should I flash? It currently has v2.95.651.5, and I can't find a ruu for that version (or higher?). Attempting to flash previous versions produces an error 155.
Hi,
please use this guide: http://forum.xda-developers.com/showthread.php?t=1889438
it should answer all of your questions.:good:
Hi,
please use this guide: http://forum.xda-developers.com/show....php?t=1889438
it should answer all of your questions.
COLOR="Silver"]
---------- Post added at 11:20 PM ---------- Previous post was at 11:18 PM ----------
[/COLOR]
No, that simply tells you to go to htcdev.com and run the unlock process, which is the hangup in the first palce and what isn't working. I'm having the same problem.
Pezastic, have you gotten anywhere with this yet? If so, how? I've jacked with this phone for two weeks and I'm about ready to ditch it and get a Galaxy. They're soooo much easier to work with.
does the Juopunutbear S-OFF woks with hboot 1.58 o virgin phone?
Okay guys. I unlocked with Moonshine, was on a Carbon ROM 10.1, updated last night to a 10.2 based Carbon ROM and lost my data. I found out to get it back, I needed to RUU back to stock. Downloaded the RUU and tried to run but it tells me that fastboot.exe and adb.exe have stopped working (I am on Windows 8). In the meantime, I missed a step and re-locked the bootloader early.
Trying to re-unlock with Moonshine and it continually reboots my phone at the "Launching Temproot" stage. Tried to unlock with Facepalm and it worked fine except it didn't fail (as it's designed too) Try to run the next step from Facepalm (The boot stage) and it fails.
Now when I hard reboot get out of the HTC screen from Facepalm, it hangs on the splash screen which is custom. Also after I performed Facepalm, it overwrote my custom recovery so that's gone and it won't let me write another one because the bootloader is locked.
I'm am at a complete loss here and am very afraid that my DNA it toast but I know there is a glimmer of hope because I can access fastboot. Any help from the masters here at XDA would be great.
Snowman1771 said:
Okay guys. I unlocked with Moonshine, was on a Carbon ROM 10.1, updated last night to a 10.2 based Carbon ROM and lost my data. I found out to get it back, I needed to RUU back to stock. Downloaded the RUU and tried to run but it tells me that fastboot.exe and adb.exe have stopped working (I am on Windows 8). In the meantime, I missed a step and re-locked the bootloader early.
Trying to re-unlock with Moonshine and it continually reboots my phone at the "Launching Temproot" stage. Tried to unlock with Facepalm and it worked fine except it didn't fail (as it's designed too) Try to run the next step from Facepalm (The boot stage) and it fails.
Now when I hard reboot get out of the HTC screen from Facepalm, it hangs on the splash screen which is custom. Also after I performed Facepalm, it overwrote my custom recovery so that's gone and it won't let me write another one because the bootloader is locked.
I'm am at a complete loss here and am very afraid that my DNA it toast but I know there is a glimmer of hope because I can access fastboot. Any help from the masters here at XDA would be great.
Click to expand...
Click to collapse
Wow! 1)..RUU does totally format, erase and finally restore the original system that came with the phone as new. so you loose everything
2) Try it from Windows 7 PC
3) Return to stock on Moonshine S-Off > http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Okay, Tried RUU from a Windows 7 pc and no dice, I get error 170 (USB connection) but no fastboot or adb failures. I was able to flash the stock 1.15 HBOOT but when I go to fastboot it tells me my HBOOT is version 1.33.
Tried Facepalm to no avail, It still won't fail after the first command as its supposed to. Tried Moonshine as well but wouldn't work because debugging isn't enabled.
Found a guide that said to find the RUU rom in the temp files and put that on the sd-card which I can't do because it won't boot, but thought I would try to flash it and this is what it did - P.S. The Rom is the PB99IMG file
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot oem
rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.045s]
finished. total time: 0.045s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot fla
sh zip PB99IMG.zip
sending 'zip' (913111 KB)...
OKAY [ 40.273s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 46.433s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>
Snowman1771 said:
Okay, Tried RUU from a Windows 7 pc and no dice, I get error 170 (USB connection) but no fastboot or adb failures. I was able to flash the stock 1.15 HBOOT but when I go to fastboot it tells me my HBOOT is version 1.33.
Tried Facepalm to no avail, It still won't fail after the first command as its supposed to. Tried Moonshine as well but wouldn't work because debugging isn't enabled.
Found a guide that said to find the RUU rom in the temp files and put that on the sd-card which I can't do because it won't boot, but thought I would try to flash it and this is what it did - P.S. The Rom is the PB99IMG file
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot oem
rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.045s]
finished. total time: 0.045s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot fla
sh zip PB99IMG.zip
sending 'zip' (913111 KB)...
OKAY [ 40.273s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 46.433s
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>
Click to expand...
Click to collapse
where did you get the instructions found with this PB99IMG.zip file?
Your Bootloader is locked or unlocked?
letschky said:
where did you get the instructions found with this PB99IMG.zip file?
Your Bootloader is locked or unlocked?
Click to expand...
Click to collapse
IDK it may work, worked in a different phone, but have to be pushed to the sd card
http://forum.xda-developers.com/showthread.php?p=32574569
letschky said:
where did you get the instructions found with this PB99IMG.zip file?
Your Bootloader is locked or unlocked?
Click to expand...
Click to collapse
Here is the link to what I used to get the PB99IMG.zip - It is the same one finanandroid posted
http://forum.xda-developers.com/showthread.php?p=32574569
And my Bootloader is locked because I was following this guide (http://forum.xda-developers.com/showthread.php?t=2293919) and spaced out and locked the bootloader without realizing I needed to flash the stock HBOOT and Splash screen, That's what I get for trying to do it at 11:30 at night.
Snowman1771 said:
Here is the link to what I used to get the PB99IMG.zip - It is the same one finanandroid posted
http://forum.xda-developers.com/showthread.php?p=32574569
And my Bootloader is locked because I was following this guide (http://forum.xda-developers.com/showthread.php?t=2293919) and spaced out and locked the bootloader without realizing I needed to flash the stock HBOOT and Splash screen, That's what I get for trying to do it at 11:30 at night.
Click to expand...
Click to collapse
Where are you currently?
s-off?
locked?
whats your CID read as in fastboot?
Also are you on windows 8 or 8.1 and do you have working drivers to begin with.
I have S-ON and Bootloader is locked,Problem,i have Software 1.15 but i flash the HBoot,Boot.img ... To make Moonshine S-OFF.This is the 2.06 Kernel with Software 1.15 and i have Problem with Wifi and the Screen flackered white.And the next Problem,i can't unlock the Bootloader witn Hboot 1.33,i hope you understand me.
jake.corey.jacobs said:
Where are you currently?
s-off?
locked?
whats your CID read as in fastboot?
Also are you on windows 8 or 8.1 and do you have working drivers to begin with.
Click to expand...
Click to collapse
My bootloader screen reads,
"Tampered
Locked
Monarudo pvt ship s-off
CID-VZW_001
HBOOT-1.33.0001
RADIO-1.01.01.0110"
I am on Windows 8 (and have access to a Windows 7 desktop) and yes, I have working drivers.
Moonshine and face palm are failing because you're already s-off
Try a different usb port and flash the stock splash screen, then run RUU
Phaded said:
Moonshine and face palm are failing because you're already s-off
Try a different usb port and flash the stock splash screen, then run RUU
Click to expand...
Click to collapse
Okay I tried both of my 2.0 USB slots and neither worked, Here is what I get -
C:\Users\Matt\Desktop\adt-bundle-windows-x86_64-20130522\sdk\tools>fastboot flas
h splash1 splash.img
sending 'splash1' (4050 KB)...
OKAY [ 0.616s]
writing 'splash1'...
FAILED (remote: not allowed)
finished. total time: 0.653s
You need to unlock... Um try htcdev and go for an unlock token. Since you're s-off it may work.
Fastboot oem unlock might work as well. Try that first, then if no go try htcdev
Phaded said:
You need to unlock... Um try htcdev and go for an unlock token. Since you're s-off it may work.
Fastboot oem unlock might work as well. Try that first, then if no go try htcdev
Click to expand...
Click to collapse
Just tried to OEM unlock and nothing, it gives me this.
C:\Users\Owner\Desktop\adt-bundle-windows-x86_64-20130729\sdk\tools>fastboot oem
unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.010s]
finished. total time: 0.010s
The command is "fastboot oem unlock" isn't?
Just looked into HTC Dev and the DNA is not listed as being supported.
Snowman1771 said:
Just looked into HTC Dev and the DNA is not listed as being supported.
Click to expand...
Click to collapse
you have to select other devices.
Like Jake said, scroll to the other devices part, then try
jake.corey.jacobs said:
you have to select other devices.
Click to expand...
Click to collapse
Just tried and it failed, here is what it said.
Error Code: 160.
Error Reason: MID Not Allowed.
Snowman1771 said:
Just tried and it failed, here is what it said.
Error Code: 160.
Error Reason: MID Not Allowed.
Click to expand...
Click to collapse
does your CID say vzw_001 or 111111 or 222222
You may be able to write the cid since you're s-off. Don't hold me to that tho.
jake.corey.jacobs said:
does your CID say vzw_001 or 111111 or 222222
Click to expand...
Click to collapse
The CID says VZW_001.
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