Related
i know there is already a link [ multiupload,com/KT9WTYGBZE ] but its broken..anyone have a working link? also im trying to fix the problem of not being able to get past
C:\rootevo3dnew>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.161s
anyone have any ideas? i have been looking around the web and the best think i can find is to use the ruu..but it wont let me go from 2.17 to 2.8..effing sucks balls right now
Anyone? Anything? Anyone get past the unlock token check fail?
Noticed your unlock_code.bin says 0kb (mine is about 4kb on disk). You may need to get a new unlock code or redownload it from your email. If you still have problems & you're stuck at HTC's step 13, you'll have to rerun the RUU and try the unlock again. With S-On, there isn't a way to run the 2.08 RUU if you've already done the 2.17 update.
I have a guide/flashing notes in my signature that may clear some things up if you want to have a look.
thanks for the reply..i tried those and nothing...i emailed htc they "say" they are working on an update to fix the unlock problem..idk how long that it will take..hopefully a dev will come up with a better way then the htc way
I'm also having the same problem with my friends phone. I get like three different outputs when I try doing the last command to unlock. It goes from saying it's successful and writing to unlock failed to something else then loops over again (trying the same command over and over). Tried running the 2.08 RUU but it won't accept it. Does anyone have a link to the 2.17 RUU? Or is there any way to downgrade to 2.08? This is really bugging me, I hate how much HTC has complicated things compared to the one click root days
See the link in my signature to get the 2.17 Ruu
Sent from my PG86100 using Tapatalk
Did you copy Unlock_code.bin over to the rootevo3dnew folder?
MistakenUtopia said:
Did you copy Unlock_code.bin over to the rootevo3dnew folder?
Click to expand...
Click to collapse
Idk about the OP, but I did. I did everything exactly the same as when I rooted my phone except my friends has the 2.17 software and mine had 2.08. Does the HTC unlock not support 2.17 or what?
you need to downgrade the ruu software number to 2.08.651.2 otherwise you wont be able to do it
http://www.multiupload.com/09NOXKCUN0
Efrencalvario said:
you need to downgrade the ruu software number to 2.08.651.2 otherwise you wont be able to do it
http://www.multiupload.com/09NOXKCUN0
Click to expand...
Click to collapse
That link doesn't appear to work. And I tried using the 2.08 RUU and it failed to work. Something about version mismatch or authentication failed. And I heard a few other users say the HTC unlock worked for them with 2.17.
I was having the same problem and i did use tgus one try to find it typing the ruu mumber with elchupacabras you will find it
Sent from my PG86100 using XDA Premium App
U can't run a lower Ruu version than whats on ur phone already with HTC's unlock & S-On.
Sent from my PG86100 using Tapatalk
im going to try the 2.17 ruu and see what happens
well everything went smooth running the ruu EXCEPT!!! i still get remote : token check failed...WTF?
tried zedomx method and even htc method both failed like 5 times..so i guess htc said **** you to anyone having 2.17.651.5..THANK YOU HTC!! bastards!!
muffinman5323 said:
tried zedomx method and even htc method both failed like 5 times..so i guess htc said **** you to anyone having 2.17.651.5..THANK YOU HTC!! bastards!!
Click to expand...
Click to collapse
Read carefully. I unrooted since i have hboot 1.50 and rerooted after taking the update just fine.
Sent from my PG86100 using xda premium
muffinman5323 said:
tried zedomx method and even htc method both failed like 5 times..so i guess htc said **** you to anyone having 2.17.651.5..THANK YOU HTC!! bastards!!
Click to expand...
Click to collapse
Read carefully. I unrooted since i have hboot 1.50 and rerooted after taking the update just fine.
Sent from my PG86100 using xda premium
muffinman5323 said:
well everything went smooth running the ruu EXCEPT!!! i still get remote : token check failed...WTF?
Click to expand...
Click to collapse
you likely copied the token incorrectly. No Spaces along the left edge.
htv dev gives: said:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won\'t work.
Click to expand...
Click to collapse
HTC UNLOCK INSTRUCTIONS said:
When copying the token, start with this line:
<<<< Identifier Token Start >>>>
And end with this line:
<<<<< Identifier Token End >>>>>
(Note: Only copy the highlighted sections above.DO NOT COPY ANY SPACES/BLANKS! Do not copy the INFO or (bootloader) prefix)
Click to expand...
Click to collapse
This is quoted from my (extracted) official HTC Dev Unlocking instructions that have been stickied and are linked in my signature.
steve97ta said:
Read carefully. I unrooted since i have hboot 1.50 and rerooted after taking the update just fine.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
yea it still doesnt work..
muffinman5323 said:
yea it still doesnt work..
Click to expand...
Click to collapse
Downgrade the hboot. See the link in my signature.
First, thank you for reading and helping.
Second, sorry if this has been asked, but every thread I see is slightly different.
I'm on GB 1.36.531.6 (never did the OTA Wifi calling update), I'm rooted, with CWM, Unlocked, with S-On.
How do I revert everything back like it was from factory? If I've read correctly, I need to flash to stock bootloader then flash an RUU? Do I need to re-lock beforehand or will flashing handle this?
Thank you in advance.
relock your bootloader, then flash ph85img in hboot. back to stock!
So I don't need to worry about CWM at all?
No need to worry about anything else after you flash the ph85img because it writes everything back to stock. Just like factory. The only thing that you'll see different is you Bootloader will say relocked instead of locked or unlocked.
-------------------------------------
Check out my hairless guinea pig
And the last question I will have, how do I relock the bootloader? I remember a thread somewhere and I know it's a fastboot cmd.
Minker17 said:
And the last question I will have, how do I relock the bootloader? I remember a thread somewhere and I know it's a fastboot cmd.
Click to expand...
Click to collapse
Fastboot OEM lock... There are instructions throughout the threads
Sent from my HTC_Amaze_4G using Tapatalk 2
Gentlemen. Thank you.
Minker17 said:
Gentlemen. Thank you.
Click to expand...
Click to collapse
please show your thanks by hitting the thanks button on whatever posts helped you. it promotes morale and glacierguy gets really excited if you do
mrmako777 said:
glacierguy gets really excited if you do
Click to expand...
Click to collapse
That's gonna be my new Sig...lol
-------------------------------------
Check out my hairless guinea pig
Double0EK said:
That's gonna be my new Sig...lol
-------------------------------------
Check out my hairless guinea pig
Click to expand...
Click to collapse
Double0EK said:
That's gonna be my new Sig...lol
-------------------------------------
Check out my hairless guinea pig
Click to expand...
Click to collapse
Just think, if u 2 combine yours, you almost tally as much as me
Holla :beer:
mrmako777 said:
Click to expand...
Click to collapse
Sent from my HTC_Amaze_4G using Tapatalk 2
I'm in the same situation as the op. I want to go back to stock so I can get the official OTA ICS upgrade.
I was able to re-lock my bootloader.
How the heck do you flash the ph85img.zip in HBOOT? I downloaded the "PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed.zip" in the stock ROM collection thread, then renamed it to PH85IMG.zip.
But I did this after relocking the bootloader. So, I didn't place it on the SD card before relocking. Did it need to be done before? How do I access the SD card from HBOOT?
I tried typing fastboot update PH85IMG.zip in the cmd prompt, but that didn't do the trick.
Please help.
edmcrocker said:
I'm in the same situation as the op. I want to go back to stock so I can get the official OTA ICS upgrade.
I was able to re-lock my bootloader.
How the heck do you flash the ph85img.zip in HBOOT? I downloaded the "PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed.zip" in the stock ROM collection thread, then renamed it to PH85IMG.zip.
But I did this after relocking the bootloader. So, I didn't place it on the SD card before relocking. Did it need to be done before? How do I access the SD card from HBOOT?
I tried typing fastboot update PH85IMG.zip in the cmd prompt, but that didn't do the trick.
Please help.
Click to expand...
Click to collapse
Rename eng hboot "PH85IMG" and flash it like a RUU in hboot.
Then put ICS ROM on sd card and name it "PH85IMG" also. Replace hboot file. Then flash the Rom in hboot and boom... Done
Sent from my HTC_Amaze_4G using Tapatalk 2
Hey guys, I'm backing up everything and am going to go back to stock and then flash to the official ICS and root, etc.
Per these directions; http://forum.xda-developers.com/showthread.php?t=1619491
Do I really need to get s-off to get ICS? I was under the impression it wasn't necessary.
Minker17 said:
Hey guys, I'm backing up everything and am going to go back to stock and then flash to the official ICS and root, etc.
Per these directions; http://forum.xda-developers.com/showthread.php?t=1619491
Do I really need to get s-off to get ICS? I was under the impression it wasn't necessary.
Click to expand...
Click to collapse
you do not need s-off
Thanks! Lock bootloader, flash the GB Rom back to factory. Then follow directions to unlock, recovery, ICS, profit. Right?
glacierguy said:
Rename eng hboot "PH85IMG" and flash it like a RUU in hboot.
Then put ICS ROM on sd card and name it "PH85IMG" also. Replace hboot file. Then flash the Rom in hboot and boom... Done
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Phone is booted into hboot, fastboot usb.
Downloaded eng hboot, renamed it PH85IMG, attempted to flash but it failed.
here's what i typed:
C:\Android>fastboot flash zip PH85IMG.zip
sending 'zip' <401 KB> ... OKAY [ 0.244s ]
writing 'zip ... INFOsignature checking...
FAILED <remote: signature verify fail>
finished. total time: 0.299s
edmcrocker said:
Phone is booted into hboot, fastboot usb.
Downloaded eng hboot, renamed it PH85IMG, attempted to flash but it failed.
here's what i typed:
C:\Android>fastboot flash zip PH85IMG.zip
sending 'zip' <401 KB> ... OKAY [ 0.244s ]
writing 'zip ... INFOsignature checking...
FAILED <remote: signature verify fail>
finished. total time: 0.299s
Click to expand...
Click to collapse
Don't flash it from your pc. Put PH85IMG.zip on the root of your sd card then boot into hboot and it will do everything automatically.
Unplug your device from pc... You don't want to be in fastboot
Sent from my HTC_Amaze_4G using Tapatalk 2
thanks guys.
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
I purchased a EVO 4G LTE for my sister a little while back and recently she had her boyfriend attempt to root it for her, and since I'm here it obviously didn't go over all too well. All he said he did was follow a video (which he gave me) on how to root for the newer software version. "Something happened and it didn't work so I watched another video and tried that" The phone is currently unlocked with S-ON and he flashed a working version of TWRP and cm10 couldn't figure it out and here we are. help please. Rooted using Linux. i did some reading and found out i had to flash the boot.img through fastboot. it just hangs at <waiting for device> in the terminal. Apologies if this has been answered, if so please point me in the right direction.
http://forum.xda-developers.com/showthread.php?t=1917106
Scroll down to see how to replace the files with the files from the cm10 rom that he flashed to the phone.
I forgot to mention I too am running linux, i tried to open this in wine and it wont save the files to my system. i will try this at a friends house asap and report back, thanks
BusstopBill44 said:
I forgot to mention I too am running linux, i tried to open this in wine and it wont save the files to my system. i will try this at a friends house asap and report back, thanks
Click to expand...
Click to collapse
Is adb configured right?
I use Linux and when I was son I was able to flash boot.img without problems
Sent from my EVO using xda app-developers app
jesuscash said:
Is adb configured right?
I use Linux and when I was son I was able to flash boot.img without problems
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I'm not really sure what he did or why he even tried. How can I check adb to see if that was done correctly?
tilltheend714 said:
http://forum.xda-developers.com/showthread.php?t=1917106
Scroll down to see how to replace the files with the files from the cm10 rom that he flashed to the phone.
Click to expand...
Click to collapse
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
BusstopBill44 said:
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
Click to expand...
Click to collapse
I'm guessing it's on the latest firmware (3.16)? That update breaks the touch panel on all non-3.16 roms (which would include cm)...the only way to downgrade is to flash the tp.img from the previous firmware (3.15), which requires s-off. I would recommend going that route as it makes things a lot easier. For example, once you're s-off you won't have to fastboot flash kernels anymore. Check out the dirty racun thread in Original Development for more info. If you decide to s-off, you can flash the old tp.img zip from the 3.15 firmware to get the touch panel working for cm:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Otherwise, if you don't want to go s-off then you'll need to flash a sense Rom that's using the 3.16 base (which I think most if not all are now). I recommend Viper4g, runs great and has tons of tweaks like cm.
Sent from my EVO LTE
BusstopBill44 said:
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
Click to expand...
Click to collapse
Boot into bootloader and check the radio. If its 1.12.11.1210 then he took the 3.16 OTA and your only choices are what premo15 said.
premo15 said:
I'm guessing it's on the latest firmware (3.16)? That update breaks the touch panel on all non-3.16 roms (which would include cm)...the only way to downgrade is to flash the tp.img from the previous firmware (3.15), which requires s-off. I would recommend going that route as it makes things a lot easier. For example, once you're s-off you won't have to fastboot flash kernels anymore. Check out the dirty racun thread in Original Development for more info. If you decide to s-off, you can flash the old tp.img zip from the 3.15 firmware to get the touch panel working for cm: (Had to remove link)
Otherwise, if you don't want to go s-off then you'll need to flash a sense Rom that's using the 3.16 base (which I think most if not all are now). I recommend Viper4g, runs great and has tons of tweaks like cm.
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks, i decided to try and go S-OFF. I flashed the correct RUU for 3.16 and I get an error message after I flash the RUU,zip
/RabiesShot_LINUX$ sudo ./fastboot flash zip RUU.zip
< waiting for device >
sending 'zip' (659905 KB)...
OKAY [ 45.943s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 122.961s
BusstopBill44 said:
Thanks, i decided to try and go S-OFF. I flashed the correct RUU for 3.16 and I get an error message after I flash the RUU,zip
/RabiesShot_LINUX$ sudo ./fastboot flash zip RUU.zip
< waiting for device >
sending 'zip' (659905 KB)...
OKAY [ 45.943s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 122.961s
Click to expand...
Click to collapse
Did you run babyracun before relocking and running the ruu?
tilltheend714 said:
Did you run babyracun before relocking and running the ruu?
Click to expand...
Click to collapse
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
BusstopBill44 said:
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
Click to expand...
Click to collapse
re-flash twrp
bigdaddy619 said:
re-flash twrp
Click to expand...
Click to collapse
another error, $ sudo ./fastboot flash recovery openrecovery-twrp-2.4.2.0-jewel.img
sending 'recovery' (8032 KB)...
OKAY [ 1.277s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.107s
and tried it with 2.4.1.0, which i had before, as well.
BusstopBill44 said:
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
Click to expand...
Click to collapse
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again. You'll need the Unlock_code.bin for the Dirtyracun process anyway so you might as well get it again.
tilltheend714 said:
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again.
Click to expand...
Click to collapse
^^^^ true
I don't know if this will work since you've already tried dirtyracun; but I just used this method to achieve s off. It's ridiculously easy, and took me 5 minutes..
http://forum.xda-developers.com/showthread.php?t=2163013
tilltheend714 said:
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again. You'll need the Unlock_code.bin for the Dirtyracun process anyway so you might as well get it again.
Click to expand...
Click to collapse
alright, some progress, got my unlock from HTCDEV got the unlock token, restarted the whole S-OFF process over,got through the ruu.zip. it installed, It rebooted itself instead of allowing me to "sudo ./fastboot reboot bootloader." It booted to a stock rom (which is now 3.15), I was in shock that I had her phone working again. restarted to bootloader, noticed it was locked and s-on went back to the directions and had me unlock through the unlock_token and finall had me run "sudo ./RabiesShot...which is giving me errors.
Starting up...
Testing connection...
Test 1: Rebooting into bootloader
Waiting fastboot (18/60)
Waiting...
Test 2: Booting device...
Waiting ADB... (60/60)
Test 2: Booting FAILED
Reboot device manually
Connection test failed!
After this error I rebooted into bootloader and im S-ON with unlocked. can i jump right into s-off'ing it
BusstopBill44 said:
alright, some progress, got my unlock from HTCDEV got the unlock token, restarted the whole S-OFF process over,got through the ruu.zip. it installed, It rebooted itself instead of allowing me to "sudo ./fastboot reboot bootloader." It booted to a stock rom (which is now 3.15), I was in shock that I had her phone working again. restarted to bootloader, noticed it was locked and s-on went back to the directions and had me unlock through the unlock_token and finall had me run "sudo ./RabiesShot...which is giving me errors.
Starting up...
Testing connection...
Test 1: Rebooting into bootloader
Waiting fastboot (18/60)
Waiting...
Test 2: Booting device...
Waiting ADB... (60/60)
Test 2: Booting FAILED
Reboot device manually
Connection test failed!
After this error I rebooted into bootloader and im S-ON with unlocked. can i jump right into s-off'ing it
Click to expand...
Click to collapse
Yeah, you should be able to run rabies shot again. Did you enable USB Debugging befor trying to run rabies shot? And are you running linux 32-bit?
tilltheend714 said:
Yeah, you should be able to run rabies shot again. Did you enable USB Debugging befor trying to run rabies shot? And are you running linux 32-bit?
Click to expand...
Click to collapse
thanks, and after all that s-off/on nonsense I cant s-off with a 32 gb microsd....grrrr
BusstopBill44 said:
thanks, and after all that s-off/on nonsense I cant s-off with a 32 gb microsd....grrrr
Click to expand...
Click to collapse
You can try this
http://forum.xda-developers.com/showthread.php?t=2163013
But that requires root. You don't have a 2gb card laying around anywhere?
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