current state: unrooted, s-on, relocked
I successfully unlocked my phone, installed TWRP and attempted to flash a new ROM. Some how I messed up by wiping out system file without backup, and I failed to flash a new ROM either.
So I flashed my phone with RUU latest version (hboot 1.19, radio 1.12.) Now on the bootloader screen it says RELOCKED on top.
When I tried to unlock (normal HTC Dev method) the terminal gave "unlock token checked successfully OKAY", and the unlock confirmation screen showed up normally.
But after rebooting, it turns out my phone is still "RELOCKED." Is there any reason why it doesn't work? And how to reunlock it successfully?
Did you submit the unlock token to htc website so that you can be given the unlock_code.bin file to flash?
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Never mind I misread the post, try the relock command and unlocking again
Make sure the command is right
Fastboot flash unlocktoken Unlock_code.bin
om4 said:
Did you submit the unlock token to htc website so that you can be given the unlock_code.bin file to flash?
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Never mind I misread the post, try the relock command and unlocking again
Make sure the command is right
Fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Here is what happened in my terminal:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.011s]
finished. total time: 0.014s
C:\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.147s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.011s]
finished. total time: 0.164s
After that the green unlock confirmation screen showed up on the phone, I chose unlock, pressed power button, waited for it to reboot, then reboot again to see the bootloader. Still no avail (relocked).
Have you tried flashing twrp anyway?
Use the 2.2.2.0 release, the new 2.3 has some issues that need to be worked out. It may just flash over, and never know
om4 said:
Have you tried flashing twrp anyway?
Use the 2.2.2.0 release, the new 2.3 has some issues that need to be worked out. It may just flash over, and never know
Click to expand...
Click to collapse
Here's what I got:
C:\android-sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7356 KB)...
OKAY [ 1.170s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.810s
(I used the img file in 2.2.2.0 twrp zip file. The name is recovery.img)
Does the failure message have something to do with being relocked?
Have you tried the PJ75IMG.zip for twrp. If you are s-off you should be able to install that and not worry about being unlocked.
Sent from my icrap 2 using Tapatalk HD
That shouldn't happen unless phone is still locked or software doesn't match
cruise350 said:
Have you tried the PJ75IMG.zip for twrp. If you are s-off you should be able to install that and not worry about being unlocked.
Click to expand...
Click to collapse
Opps sorry, I'm currently S-On.
om4 said:
That shouldn't happen unless phone is still locked or software doesn't match
Click to expand...
Click to collapse
When I tried to lock the phone again, it says my phone is already locked. But the problem is normal unlock method doesn't work with some reason.
I'm stumped, maybe ruu again?
om4 said:
I'm stumped, maybe ruu again?
Click to expand...
Click to collapse
Done ruu again, but still can't get unlocked.
Maybe it's worth mentioning that after select 'Yes' on the unlock bootloader screen (the green page), the phone didn't reboot. It just turned itself off with red LED charging.
chtat12 said:
Done ruu again, but still can't get unlocked.
Maybe it's worth mentioning that after select 'Yes' on the unlock bootloader screen (the green page), the phone didn't reboot. It just turned itself off with red LED charging.
Click to expand...
Click to collapse
Is there another way around (manual method) for unlocking? To me it looked like some thing after the green confirmation page just didn't work right.
I can't think of any reason it wouldn't work again, maybe someone else will see this and have a fix. Sorry
chtat12 said:
Is there another way around (manual method) for unlocking? To me it looked like some thing after the green confirmation page just didn't work right.
Click to expand...
Click to collapse
You could try downgrading to hboot 1.12 to get s-off...then it won't matter if you're unlocked or not. The process is still pretty new and not for the faint of heart (yet), but seems to be verified working. Check the downgrade sticky thread in the original dev forum for more details.
Sent from my EVO LTE
I would have mentioned it if closeone had a release ready but it's still a bit off. Better to wait then to have someone following directions to purposely brick their phones
premo15 said:
You could try downgrading to hboot 1.12 to get s-off...then it won't matter if you're unlocked or not. The process is still pretty new and not for the faint of heart (yet), but seems to be verified working. Check the downgrade sticky thread in the original dev forum for more details.
Sent from my EVO LTE
Click to expand...
Click to collapse
I believe downgrading method requires an unlocked phone, since it needs twrp for adb commands?
Yes it does, I didn't even remember that lol. I just didn't mention it because right now the overall process is rough
I think the unlock process modified the boot section, and looks like mine is a bit messed up. If so, would 'fastboot flash boot <bootfile>' work? (I don't know where to find it yet, just an another thought.)
chtat12 said:
I believe downgrading method requires an unlocked phone, since it needs twrp for adb commands?
Click to expand...
Click to collapse
Good point...
Sent from my EVO LTE
any resolution to this? i find myself in the same situation
Related
[Solved!] Thanks.
So on step 12 of the website it says to type the below:
C:\>fastboot flash unlocktoken C:\Unlock_code.bin
I do so and I get the correct output that the site displays.
Which is:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' <0 KB>...
OKAY [0.151s]
writing 'unlocktoken' ...
<bootloader> unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.158s
Step 13 reads:
"On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty"
However, I see no disclaimer appear on my phone. It stays on the fastloader hboot screen.
What's going on? Do I have to be not in the recovery fastloader screen and do that command when the normal os is showing? Or what?
Thanks if you can help.
Locate and flash the latest stock Ruu (or current one installed) from football or Mr.esp's thread to clear the issue. You should id your current Rom/radio version in android settings (about phone ) first... Ie. 2.08.651.3 vs 2.17.651.5 and phone codename is "shooter" not shooteru .
http://forum.xda-developers.com/showthread.php?p=19089387
Then retry the unlock & it should work. Check development sticky thread.for link & instructions. If you look at jtniggles hboot unlock/flash thread it will mention this issue.
If your hboot 1.50 you may have issues with specific recoveries not loading. I'd recommend you grab Cwm touch 5.0.8.1 and a more current Su 3.0 file to flash. I have some examples of flashing these & other stuff after unlocking in my recovery issues thread (see signature). Htcevohacks.com has a good how to video also.
Sent from my "Up all night, sleep all day" Evo3D via Tapatalk.
i tried this method myself but when i run the ruu it just sits at sending.... and never gets past it. please help!
Saw you posted a separate RUU question, so hopefully you'll get a response there, but just to try and help a bit...
There is an RUU .exe Instructions Doc in the Sticky Thread that may help you.
Edit: its 1/2 way down my useful thread links post (in my signature).
- you should indicate in your questions what your phone setup is so people can better help you: Hboot version, Firmware/Radio version, HTC Unlocked/Locked/not rooted, S-ON vs S-Off, Custom Recovery you use, filenames/thread links you're using, etc if they apply to your situation.
did you enable "usb Debugging" under settings, applications?
Did you DL the RUU.exe or RUU PG86IMG.zip ?
What he said you need to run latest RUU I have walked a bunch of folks through that .... Worked everytime for them...
og92 said:
i tried this method myself but when i run the ruu it just sits at sending.... and never gets past it. please help!
Click to expand...
Click to collapse
Relock and then run RUU.
Sent in L*W*H
intrlude said:
Relock and then run RUU.
Sent in L*W*H
Click to expand...
Click to collapse
He sounds like he is tryin to root the first time and gets to the part were the phone splash screen is suppose to say do you wish to unlock bootloader....
Which he needs to just run the RUU and should be good to go..
Thanks a bunch guys! Flashing the latest RUU and redoing the process worked. However...how do you know the bootloader was unlocked afterall? I want to double check.
Edit: Sorry, just figured it out..just needed to do the reboot again and says unlocked on the top. Yay!
FYI, I added some RUU info to the other post:
Running stock RUU Reference info: http://forum.xda-developers.com/showpost.php?p=22190515&postcount=5
GamerC said:
So on step 12 of the website it says to type the below:
C:\>fastboot flash unlocktoken C:\Unlock_code.bin
I do so and I get the correct output that the site displays.
Which is:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' <0 KB>...
OKAY [0.151s]
writing 'unlocktoken' ...
<bootloader> unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.158s
Step 13 reads:
"On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty"
However, I see no disclaimer appear on my phone. It stays on the fastloader hboot screen.
What's going on? Do I have to be not in the recovery fastloader screen and do that command when the normal os is showing? Or what?
Thanks if you can help.
Click to expand...
Click to collapse
The first suspect thing to me here is that file says that its 0 kb, try to download again that file but maybe disable the AV to avoid getting it corrupted or stripped.
Sent from my PG86100 using Tapatalk
Hi, i recently bought a replacement EVO 3D and i am having trouble unlocking it. I was able to unlock my first 3D which had the exact same software versions with no problem.
I have HBOOT 1.58 and the latest Sprint OTA ICS update.
When i go through the CMD part and enter the following:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
nothing happens.
CMD shows the following:
C:\sdk-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.151s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.160s
Click to expand...
Click to collapse
but I don't receive an option to accept on my phone it just stays in the bootloader menu. Has anyone had this issue? Thanks
I know this doesn't help but I did have the problem with one EVO 3d I had with hboot 1.5 so I returned it and luckily got another with 1.4...spent 8 hours trying to unlock that one and never did get answers
Sent from my PG86100 using Tapatalk 2
Well first is the code.bin in it folder were it shud be?
EVO 3DIZZLE
S-OFF
HBOOT 1.58
Jmurphy8367 said:
Well first is the code.bin in it folder were it shud be?
EVO 3DIZZLE
S-OFF
HBOOT 1.58
Click to expand...
Click to collapse
Yes, it is sitting in the main folder with the other files. I followed the same steps i used before which worked on my old EVO 3D, but are not working on this one. Thanks.
All drivers and HTC sync good to go?
EVO 3DIZZLE
S-Off
hboot 1.58
Jmurphy8367 said:
All drivers and HTC sync good to go?
EVO 3DIZZLE
S-Off
hboot 1.58
Click to expand...
Click to collapse
Yes, I also tried uninstalling and reinstalling the drivers..and I tried a second computer. I have no idea what could be wrong, Is there an official RUU out yet from sprint for the new OTA ICS that I should install on it?
Here's my s-off folder put it on it hardisk its got fast boot adb and recovery put the code.bin in there and try it
EVO 3DIZZLE
S-Off
hboot 1.58
---------- Post added at 08:16 PM ---------- Previous post was at 08:08 PM ----------
http://db.tt/T6eecDpL
EVO 3DIZZLE
S-Off
hboot 1.58
The same thing happened. Command Prompt returns the following:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.159s
But nothing happens on my phone screen. Still stuck at the screen that says Fastboot USB in red. The window asking me if i want to unlock bootloader does not come up.
Robot818 said:
Hi, i recently bought a replacement EVO 3D and i am having trouble unlocking it. I was able to unlock my first 3D which had the exact same software versions with no problem.
I have HBOOT 1.58 and the latest Sprint OTA ICS update.
When i go through the CMD part and enter the following:
nothing happens.
CMD shows the following:
but I don't receive an option to accept on my phone it just stays in the bootloader menu. Has anyone had this issue? Thanks
Click to expand...
Click to collapse
Did you get a new token file for your replacement phone?
I would submit the file you capture from your phone and get a new token again just in case something went wrong the first time.
I "re unlocked" my phone after 1.58 using the same binary file I had from when I previously unlocked it.
sonza said:
Did you get a new token file for your replacement phone?
I would submit the file you capture from your phone and get a new token again just in case something went wrong the first time.
I "re unlocked" my phone after 1.58 using the same binary file I had from when I previously unlocked it.
Click to expand...
Click to collapse
Thanks for your reply, I just tried getting a new token again and still haven't been able to get the unlock bootloader option to pop. I've actually requested a new token three times now and and still nothing.
Just to let anyone else know that might have this same problem, i was able to fix this by running the RUU found here: http://forum.xda-developers.com/showthread.php?t=1827712
My phone is finally unlocked!
Robot818 said:
Thanks for your reply, I just tried getting a new token again and still haven't been able to get the unlock bootloader option to pop. I've actually requested a new token three times now and and still nothing.
Click to expand...
Click to collapse
Ok, the fact that is says sending with 0KB would seem to me that it is not actually reading the darn .bin file.
Now this might seem stupid, but we are shooting totally in the dark here.
First, I have my folder that has adb and all the other files in the root of the hard drive. It is called rootevo, just to keep the folder name short. While it usually should not matter, I knew we would be running adb from a command box, and that can sometimes cause issues with folder and file names longer than 8 characters.
If the phone is booted, plug it in and you should be able to type "adb reboot bootloader" and the phone should reboot to the bootloader screen. If this works, I would try and do the unlock process again. Make sure you are typing in the name exactly as it is named in the folder.
The other option would be to boot straight to bootloader after a battery pull. Again, not sure why it would matter, but you have a strange one here, so the fix could end up being equally strange.
Good luck! :laugh:
i guy's can you help us
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.172s
what is the solution of this error.???
Hello Evo 3D Fellow..
today i've got Evo 3D CDMA (Shooter) from my friend, he gave it to me because he said it was brick, i don't know what kinda break that's he meant, but i think it a soft brick, because i still can access a bootloader, flash a recovery from adb, it said it successfully flashed, but nothing happened when i select recovery...
i did nothing to fix this because i'm totally blind for CDMA devices..
here's the little information that i think can be a references for my problem:
*** UNLOCKED ***
SHOOTER XC SHIP S-OFF RL
HBOOT-1.50.0000
RADIO-1.06.00.1216
eMMC-boot
mine is Evo GSM and it work like a charm, and i have never encountered a problem like this before, and honestly i have never read any thread that related with Brick/Unbrick, also never read anything in the CDMA section.. so if i want to fix this, i don't know the point to start..
my question is, how can i fix this??
please ignore my signature since mine is GSM, so please keep in mind that my question is related for CDMA (Shooter)
Thanks
-b-
Flash a RUU.
MrJyrks said:
Flash a RUU.
Click to expand...
Click to collapse
my friend said he tried to flash an RUU but no luck, eh?
Here. http://forum.xda-developers.com/showthread.php?t=2136964
Follow the instructions and it should work.
Oh, right, the first step needs a working recovery...
MrJyrks said:
Here. http://forum.xda-developers.com/showthread.php?t=2136964
Follow the instructions and it should work.
Oh, right, the first step needs a working recovery...
Click to expand...
Click to collapse
i'm gonna try it, i'll be back for the progress..
Okay, better say, is it a sprint evo 3d?
MrJyrks said:
Okay, better say, is it a sprint evo 3d?
Click to expand...
Click to collapse
rite..
sorry, forgot to mention it was sprint..
http://forum.xda-developers.com/showthread.php?t=1578977
Then this is more appropriate.
---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------
Let me know how it went
MrJyrks said:
http://forum.xda-developers.com/showthread.php?t=1578977
Then this is more appropriate.
---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------
Let me know how it went
Click to expand...
Click to collapse
dude... sorry but i think that link is not related with my problem?
as i mentioned, the problem is i can access the bootloader but cannot access the recovery, i flash a recovery 5 times, and still can't access the recovery, IMHO as i indicate some block of partitions corrupt or something like that.. i didn't mean i wanna back to stock or even downgrade my hboot.. any advices please?
strykerider said:
dude... sorry but i think that link is not related with my problem?
as i mentioned, the problem is i can access the bootloader but cannot access the recovery, i flash a recovery 5 times, and still can't access the recovery, IMHO as i indicate some block of partitions corrupt or something like that.. i didn't mean i wanna back to stock or even downgrade my hboot.. any advices please?
Click to expand...
Click to collapse
Gosh, AFAIK all these kind of problems can be fixed by flashing a ruu, that means going back to stock. Anyway, If you don't want to, try to get recovery working. What recovery were you trying to flash.
Is it the right recovery you're flashing? (shooter, not shooteru)
Try flashin 4ext, it has never given me any problems.
Found someone who had a similar issue, read from there -> http://forum.xda-developers.com/showthread.php?t=1757826&page=3
---------- Post added at 03:52 PM ---------- Previous post was at 03:28 PM ----------
Anyway, if i were on your situation, I would flash ruu (return to stock), then s on with htcdev and s off with juopunutbear wire trick.
If flashing a ruu doesn't help it's most likely a hardware problem, maybe internal memory is broken or something like that.
MrJyrks said:
Gosh, AFAIK all these kind of problems can be fixed by flashing a ruu, that means going back to stock. Anyway, If you don't want to, try to get recovery working. What recovery were you trying to flash.
Is it the right recovery you're flashing? (shooter, not shooteru)
Try flashin 4ext, it has never given me any problems.
Found someone who had a similar issue, read from there -> http://forum.xda-developers.com/showthread.php?t=1757826&page=3
---------- Post added at 03:52 PM ---------- Previous post was at 03:28 PM ----------
Anyway, if i were on your situation, I would flash ruu (return to stock), then s on with htcdev and s off with juopunutbear wire trick.
If flashing a ruu doesn't help it's most likely a hardware problem, maybe internal memory is broken or something like that.
Click to expand...
Click to collapse
Yes, I'm flashing the right ruu and the right recovery, mate.. Ok I'm gonna try the last link you give tomorrow, since I'm so sleepy right now, wish me luck..
Sent From My ShooterU
strykerider said:
Yes, I'm flashing the right ruu and the right recovery, mate.. Ok I'm gonna try the last link you give tomorrow, since I'm so sleepy right now, wish me luck..
Sent From My ShooterU
Click to expand...
Click to collapse
Good luck!
MrJyrks said:
Good luck!
Click to expand...
Click to collapse
flashing RUU.. just get an error, see attach..
This.
Unknownforce said:
Not in fastboot no, if they are not giving you the option to flash, they are not signed/valid zip's.
Run the RUU exe, wait till it gets to the first "Next" prompt, Leave it open and running, open up windows explorer, type %temp% into the path, and press enter, look for a folder that has {683BEF986C0941 BLAHBLAHBLAH} (not exactly, of course) as it's name, check in each of those and inside one of the sub-folders of that folder is a rom.zip, (you can just search for "rom.zip" inside the %temp% location as well)
Copy this out, rename it to PG86IMG.zip (or without the .zip if you don't show file extensions in windows explorer)
Copy this to SD Card and it should allow it to flash now from hboot.
This is the most reliable method of getting a valid/signed zip file that hboot will accept.
Click to expand...
Click to collapse
Also, are you 100% sure it's the correct RUU? How is the ruu named?
MrJyrks said:
This.
Also, are you 100% sure it's the correct RUU? How is the ruu named?
Click to expand...
Click to collapse
my bad... the RUU is different downloading the other one... still in progress now..
thanks mate..
dude... it's become dead at all now after flashing pg86img.zip..
at the first time after flashing pg86img.zip it still boot up, then it's off and won't be able on at all.. any other way to fix this out?
edit: damn, the battery is running out.. tryin' to switch to my GSM Battery now..
same result, won't be able to boot up, only got a bootloop after did return to stock, flash RUU, S-On, etc.. LOL..
see attach for the pic show PG86IMG.zip flashed, and it fine since i've got no error at these process
this the recovery that i flashed;
Code:
c:\Android>fastboot flash recovery recovery-clockwork-touch-5.8.0.2-shooter.img
sending 'recovery' (4128 KB)...
OKAY [ 1.060s]
writing 'recovery'...
OKAY [ 4.477s]
finished. total time: 5.538s
c:\Android>fastboot flash recovery recovery.img
sending 'recovery' (6912 KB)...
OKAY [ 1.705s]
writing 'recovery'...
OKAY [ 8.554s]
finished. total time: 10.261s
any other way to fix this out? our i can say this is a hardware (internal memory) problem?
I can't confirm but most likely it is. Still, doesn't hurt to try this -> http://forum.xda-developers.com/showthread.php?t=2193675.
Recovery-clockwork-5.0.2.0-shooteru.img is gsm recovery so try finding recovery-clockwork-5.0.2.0-shooter.img or something like that. As mentioned it is a bit risky to install such an old recovery but since it helped the OP, it may work for you too. Give me feedback how it went.
Can you do a factory reset from bootloader?
MrJyrks said:
I can't confirm but most likely it is. Still, doesn't hurt to try this -> http://forum.xda-developers.com/showthread.php?t=2193675.
Recovery-clockwork-5.0.2.0-shooteru.img is gsm recovery so try finding recovery-clockwork-5.0.2.0-shooter.img or something like that. As mentioned it is a bit risky to install such an old recovery but since it helped the OP, it may work for you too. Give me feedback how it went.
Can you do a factory reset from bootloader?
Click to expand...
Click to collapse
Ummm.. I will give a try with an old recovery then..
Also trying to factory reset from bootloader give me a zero results, though.. LOL..
Sent From My ShooterU
zero result..
Code:
C:\Android>fastboot flash recovery recovery-clockwork-5.0.2.0-shooter.img
sending 'recovery' (4726 KB)...
OKAY [ 1.135s]
writing 'recovery'...
OKAY [ 4.551s]
finished. total time: 5.688s
still got a bootloop... LOL
strykerider said:
zero result..
Code:
C:\Android>fastboot flash recovery recovery-clockwork-5.0.2.0-shooter.img
sending 'recovery' (4726 KB)...
OKAY [ 1.135s]
writing 'recovery'...
OKAY [ 4.551s]
finished. total time: 5.688s
still got a bootloop... LOL
Click to expand...
Click to collapse
stupid question.... did you relock the bootloader and pull and flash the stock recovery from the rom before trying to ruu??
the device has to be relocked and have the stock recovery before it will take the ruu
I'm somewhat of a noob at this - this is my first HTC, so I had no idea what S-Off or unlocked bootloader meant. With my Samsung, rooting and installing a custom recovery involved a one-click method, so I never had to learn all the ins and outs of this stuff. With this DNA, I used the revone method (since the phone was purchased with 2.06 firmware already installed), so I still didn't need to learn much.
Anyway, I recently tried to go back to stock. I figured that would involve an RUU, going back to S-On, and locking the bootloader. So I first (yes, before performing the RUU like a dodo) used revone to go back to S-On, then found something saying I needed to execute "fastboot oem writesecureflag 3", so I did that, and now I am stuck at fastboot. I don't have access to CWM recovery, and if I try to boot beyond fastboot it hangs on the initial HTC screen.
Without being able to use ADB since it doesn't boot that far, I can't go back to S-Off via revone. I can't flash anything that I have been able to find so far via fastboot because it fails at signature verification. And I can't use the RUU that I found because it is firmware 1.15 and it won't allow me to install on top of 2.06.
Does anyone have any ideas on how to fix this? Is there a way to get to S-Off through fastboot? Is there an RUU for the 2.06 firmware? I have spent a few days searching and the answer to both seems to be no...
UPDATE: I grabbed the Rom.zip out of the 1.15 RUU and tried flashing that via fastboot (in RUU mode). I got the following message:
sending 'zip' (913111 KB)...
OKAY [ 35.667s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 118.073s
Click to expand...
Click to collapse
I assume this has something to do with the firmware version difference (1.15 vs. 2.06). But I was very excited to see a signature check be successful for once.
I should note that the ROM I was running when doing this was Newt's NOS m7 v 3.0.6
When selecting recovery from the fastboot menu, it does nothing?
If that's a yes... You need s-off again.
Phaded said:
When selecting recovery from the fastboot menu, it does nothing?
If that's a yes... You need s-off again.
Click to expand...
Click to collapse
It doesn't do nothing per se, it shows a screen that I'm not used to with a red triangle and exclamation point on top of a picture of a phone with a blue background. I assume this is the recovery screen from the factory, not the CWM recovery I had installed previously.
Is there a way to get s-off without ADB (only using fastboot)?
Flash firmware zip located on the moonshine thread, then use moonshine
Phaded said:
Flash firmware zip located on the moonshine thread, then use moonshine
Click to expand...
Click to collapse
I successfully flashed the firmware zip from the moonshine thread, but the phone still will not boot past fastboot. I assume since the instructions for moonshine require the phone to be booted to android, this option will not work for me.
jdpalmer2k13 said:
I successfully flashed the firmware zip from the moonshine thread, but the phone still will not boot past fastboot. I assume since the instructions for moonshine require the phone to be booted to android, this option will not work for me.
Click to expand...
Click to collapse
I've been thinking about this. Why did the firmware zip from Moonshine pass signature inspection? Was it signed? Could that same signature be placed on a rom or some other zip that installs a recovery or even somehow performs s-off? I know I am not very well experienced with android development, so I'm probably talking out of my ass.
I recently flashed the RUU from fastboot.
http://forum.xda-developers.com/showthread.php?t=2115987 post#4
I believe what you are looking for is in this thread.
To get back to stock on my phone I needed to flash the stock hboot first before I could use the stock RUU
bwhxeon said:
I believe what you are looking for is in this thread.
To get back to stock on my phone I needed to flash the stock hboot first before I could use the stock RUU
Click to expand...
Click to collapse
I can't flash the stock hboot because I'm s-on and the file fails signature verification.
jdpalmer2k13 said:
I can't flash the stock hboot because I'm s-on and the file fails signature verification.
Click to expand...
Click to collapse
Then your pretty much out of luck. Need to exchange it or possibly do a jtag. Does your phone say tampered/relocked? If so then I'd guess Jtag is the only solution.
Unfortunately the guide you used to go back to stock was pretty dumb in telling you make your phone s-on again. It isn't needed especially if it was just so you could do a clean install and flash other roms.
I was in your situation, but I was lucky enough to have unlocked my phone using htcdev when Jcase released his original unlock method. If the super cid method still works. I would unlock my bootloader the super cid method and not even bother with moonshine. That way you end up with a unlock token and wouldn't get stuck in this situation.
bwhxeon said:
Then your pretty much out of luck. Need to exchange it or possibly do a jtag. Does your phone say tampered/relocked? If so then I'd guess Jtag is the only solution.
Unfortunately the guide you used to go back to stock was pretty dumb in telling you make your phone s-on again. It isn't needed especially if it was just so you could do a clean install and flash other roms.
I was in your situation, but I was lucky enough to have unlocked my phone using htcdev when Jcase released his original unlock method. If the super cid method still works. I would unlock my bootloader the super cid method and not even bother with moonshine. That way you end up with a unlock token and wouldn't get stuck in this situation.
Click to expand...
Click to collapse
Nothing was wrong with the guide. He didn't follow it correctly as he did s-on using revone.
Flashing the firmware zip should allow you to boot up and run moonshine. Are you sure it flashed correctly.
Phaded said:
Nothing was wrong with the guide. He didn't follow it correctly as he did s-on using revone.
Flashing the firmware zip should allow you to boot up and run moonshine. Are you sure it flashed correctly.
Click to expand...
Click to collapse
Correct, the guide was not at fault here, I am just an idiot. Here are the results of flashing the dna2.06firmware.zip file from the moonshine thread: http://pastebin.com/GkgdGt19
Following what is shown at this link, I executed "fastboot reboot-bootloader", selected "Power Down", and then tried to turn the phone on again. I got the same result as always (stuck on the initial HTC quietly brilliant screen - not the bootanimation screen).
Spoke with beaups on IRC. I was running a 4.2 rom that will not run on the stock kernel. Since the only thing I can flash is the signed stock kernel because I am s-on, the only remaining option is to run a 2.06 RUU. However, the 2.06 RUU has not been leaked to anyone's knowledge. So I will have to send off for jtag in order to get s-off, then flash whatever - RUU, custom ROM, what-have-you.
Thanks all for trying to help. I will hang on to it for a while if anyone has any other thoughts or suggestions.
jdpalmer2k13 said:
Spoke with beaups on IRC. I was running a 4.2 rom that will not run on the stock kernel. Since the only thing I can flash is the signed stock kernel because I am s-on, the only remaining option is to run a 2.06 RUU. However, the 2.06 RUU has not been leaked to anyone's knowledge. So I will have to send off for jtag in order to get s-off, then flash whatever - RUU, custom ROM, what-have-you.
Thanks all for trying to help. I will hang on to it for a while if anyone has any other thoughts or suggestions.
Click to expand...
Click to collapse
I talked to beaups last night about the same thing... Hes a good guy. I'm in the exact same boat. I hope there is a break through on this but if not I guess JTAG is our only option. Let me know if you figure anything out jdpalmer, i'd really appreciate it.
Try this please
fastboot oem readcid
What's it say?
Phaded said:
Try this please
fastboot oem readcid
What's it say?
Click to expand...
Click to collapse
VZW_001 for me. Not trying to jack your thread jd, it just seems we have screwed up in the exact same manner.
PiperBen85 said:
VZW_001 for me. Not trying to jack your thread jd, it just seems we have screwed up in the exact same manner.
Click to expand...
Click to collapse
Yep same here
jdpalmer2k13 said:
Yep same here
Click to expand...
Click to collapse
You are s-on... Are you also locked?
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
It's possible you might have supercid, although I doubt it
You could try
Fastboot oem writecid 22222222
Reboot
Fastboot oem readcid
Did it change?
Phaded said:
You are s-on... Are you also locked?
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
It's possible you might have supercid, although I doubt it
You could try
Fastboot oem writecid 22222222
Reboot
Fastboot oem readcid
Did it change?
Click to expand...
Click to collapse
Yes, I am locked. Here is the result of trying to writecid:
Code:
C:\Android>fastboot oem writecid 22222222
...
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (Too many links))
finished. total time: 0.005s
My phone was acting buggy with the radios and had HUGE performance issues. To be frank, i think a SNAIL was faster than this phone at the time... I am S-OFF, unlocked and i cannot flash recovery.
I get this output and error:
Code:
sending 'recovery' (8516 KB)...
OKAY [ 1.087s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.129s
here is the current HBOOT Config and display:
Code:
FIREBALL PVT SHIP S-OFF RL
CID-VZW__001
HBOOT-1.15.0000
OpenDSP-29.1.0.45.622
eMMC-boot
Just for good measure i re-wrote the CID to 11111111 and locked and unlocked the bootloader again to no avail, thinking it was possibly that being unlocked during an RUU. The thing is, while unlocked, the RUU still processed... Oh and the phone boots up fully. i have ZERO issues with actually using the phone, but i cant believe i am stuck on a stock rom and not allowed to flash a custom recovery... >_>
Other thing... just to see if this would help, i used junkmail9's ENG HBOOT with the RegawMOD Customizer to flash the ENG hboot to try my luck. STILL no good. i can flash hboot directly, and whatever else, but is recovery just stuck??
i really want to be free again, so can someone please explain to me why after an RUU even WHILE S-OFF and unlocked, that i cannot flash recovery?
cyberkeeper1 said:
I get this output and error:
Code:
sending 'recovery' (8516 KB)...
OKAY [ 1.087s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.129s
Click to expand...
Click to collapse
You did not mention either the recovery image you tried to flash, nor the command you used to try and flash it. There's no point in messing with bootloader lock/unlock if you're s-off. Just leave it alone.
my apologies... well basically, i cannot flash any custom recovery for this phone. CWM 6.0.3.1 which i had before the restore, and i just tried the philZ Touch 5 recovery which is basically the same thing as CWM... for some reason, the recovery partition became locked after the restore despite being s-off. i remember this error before while s-on and locked when I used to have the Wildfire S.
cyberkeeper1 said:
my apologies... well basically, i cannot flash any custom recovery for this phone. CWM 6.0.3.1 which i had before the restore, and i just tried the philZ Touch 5 recovery which is basically the same thing as CWM... for some reason, the recovery partition became locked after the restore despite being s-off. i remember this error before while s-on and locked when I used to have the Wildfire S.
Click to expand...
Click to collapse
alright, i am a dodo-bird... apparently, i really need glasses because i JUST noticed that i was flashing a zip file.... dang it... for whatever reason, it can flash zip files, but i guess i didnt have the right one. anyhow, no help needed now. Mods, you can close the thread... my apologies for the wasted space. If its any consolation, i havent really slept so.... yea. lol. thanks for the help thus far.
i wasnt flashing the IMG file like i should have been.
similiar issue
hello users of the almighty xda!
I have obtained s-off using dirtyracun and flashed between team venoms viper rom and cyanogenmod10.1 multiple times
this last time I tried to flash back to viper2.2.0 from cyanogenmod because of the problems with the m2 snapshot I wiped everything as usual including cache,data, and even a factory reset and installed the viper rom and said everything was good to go and now the phone wont boot past the htc screen
so I figured i'd reflash the viper boot.img to see if that would help and doesn't
not only will it not boot but when I go to the bootloader and try to enter recovery it flashes and I see the clockwork mod symbol and then it boot loops back to the htc logo endlessly
wtf! ugg! any ideas oh great xda users?
p.s im also under the impression that because im s-off I cant RUU back to stock is this the case?
styxking said:
im also under the impression that because im s-off I cant RUU back to stock is this the case?
Click to expand...
Click to collapse
This is not true. You may at any time run the RUU to restore borked programming. Besides, the dirtyracun method of flashing s-off is risky to say the least. I used facepalm s-off and it was stupid easy. Anyhow, run the RUU and then immediately run a factory reset. The RUU formats and repairs all partitions on the device and the factory reset restores the radio and baseband as described by mdmower.
Sent from my ADR6410LVW using xda app-developers app
Do the following to prepare for RUU-
Run these commands in order:
fastboot oem resetRUUflag (wait for reload)
Fastboot oem rebootRUU
Fastboot erase cache
Fastboot flash zip name_of_file.zip
Alternatively, you can run the automated HTC RUU utility, but it often fails vs. A manual reflash.
Sent from my ADR6410LVW using xda app-developers app
ignore please, came late and didnt notice
gonna try it
thanks for the response. I agree the dirtyracun method is pretty risky, but at the time I think it was the only s-off method I could find
well I will ruu then
thanks for the detailed fastboot commands and such
I don't have to relock the bootloader do I?