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
Related
Dear experts,
i m needing your help since i think my evo 3d is bricked however i can explain the current situation that i m S off revolutionary method and my current hboot is 1.49.1107 with cid number htc_001 i m just stuck in the boat loader not able to flash ruu neither recovery if i flash recovery using fastboot commands i recieve the error "failed remote: partition doesnot exist.
any one please help me or tell me if i m completely brciked...plz plz
fastboot boot recovery.img
Although the 'partition does not exist' bit doesn't sound good.
wrong section bro..
anyway try this...
fastboot erase cache
fastboot erase recovery
then try
fastboot boot recovery.img
or
fastboot flash recovery recovery.img
thanks for the advice i m getting the following error
erasing 'recovery'... FAILED (remote: erasing error!)
erasing 'cache'... FAILED (remote: erasing error!)
mani00007 said:
thanks for the advice i m getting the following error
erasing 'recovery'... FAILED (remote: erasing error!)
erasing 'cache'... FAILED (remote: erasing error!)
Click to expand...
Click to collapse
is your bootloader locked or unlocked?
it doesnt show me ny thing in boatloader screen except that revolutionary
shooter_u pvt ship s-off rl
hboot 1.49.1107
emmc - boot
but i guess its locked
coolexe said:
wrong section bro..
anyway try this...
fastboot erase cache
fastboot erase recovery
then try
fastboot boot recovery.img
or
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
i think he has erased all system-partitions...
try to flash a OFFICIAL RUU
and if it doesnt work, try to flash the bootloader.
can u please explain how to flash boatloader... where can i get it.. please i m in deep trouble ...
mani00007 said:
can u please explain how to flash boatloader... where can i get it.. please i m in deep trouble ...
Click to expand...
Click to collapse
ill make a package for you. be patient. be sure your battery level is high enough...
thanks .. yup i m ready ...
mani00007 said:
thanks .. yup i m ready ...
Click to expand...
Click to collapse
1- Place the "PG86IMG.zip" in the root of your sd-card
Click to expand...
Click to collapse
Download:http://www.mediafire.com/?4d2cnz43cdp6l6z
2-boot into bootloader, not fastboot.
Click to expand...
Click to collapse
3- If asked, press Volume up. (if not asked, constantly press volume up)
4- Press Power
DO THIS STEP 2x, IT FLASHES BOOTLOADER, SO STEPS
2,3 and 4 are reqired to be done 2x
Click to expand...
Click to collapse
5-Pull out Battery
6- Remove sd-card
7-boot into bootloader
8-boot recovery
9-AFTER YOU HAVE PRESSED RECOVERY PUT SDCARD IN
10- Flash Gingerbread rom like leedroid(http://forum.xda-developers.com/showthread.php?t=1245424)
Click to expand...
Click to collapse
report to me if it worked.
ok thanks i will get back to you.. after i finish downloading the files
its showing update fail.
mani00007 said:
its showing update fail.
Click to expand...
Click to collapse
is bootloader still labeled as revolutionary?
---------- Post added at 02:33 PM ---------- Previous post was at 02:30 PM ----------
EMD:
try this: http://forum.xda-developers.com/showthread.php?t=1627897
if it does not work, you should send it to htc customer care...
e3d said:
is bootloader still labeled as revolutionary?
---------- Post added at 02:33 PM ---------- Previous post was at 02:30 PM ----------
EMD:
try this: http://forum.xda-developers.com/showthread.php?t=1627897
if it does not work, you should send it to htc customer care...
Click to expand...
Click to collapse
I thought dexter unbricking method is only for bricked s-on device.
Sent from my HTC EVO 3D X515m using XDA
oOps, yeah.
OP:
send it to htc sutomer care. They may give you a charge of €50 (it was so on my htc mozart) for Unlocking it and doing sh#t with it. It'll take about 3 weeks till you have a fully-functional phone agin. but take care, when u got it back
e3d said:
is bootloader still labeled as revolutionary?
Click to expand...
Click to collapse
@mani00007 ans. plz
Have you actually tried 'fastboot boot recovery.img'? You've mentioned the outcome of a few things, but not that
Mod needs to move this to q+a.
Sent from my HTC EVO 3D X515m using xda premium
dladz said:
Mod needs to move this to q+a.
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
you don't need to write that here, you have to pm the Mod to move it.
for some reason today i started getting random reboots here and there. when i got home i decided to wipe my phone and do a clean install. everything went well, successful wipe and complete flash of the rom, but when it restarted after the flash it was still the same as before. nothing changed, all my apps, wallpaper, settings everything had been untouched. i even did fastboot wipe userdata. it was like i didnt do anything at all. then i tried wiping my internal sd card, same thing successful wipe, but it all comes back again. i did it a couple of times from the phone settings and also from my computer. then i flashed the ruu from the bootloader, everthing flash normal but when it restarted nothing changed. also tried changing my recovery to cwm but that didnt work either. tried flashing the eng bootloader and it said fail-pu.
right now im running energy rom june 19th, 4 ext recovery, joupunutbear 1.93.2222
any help or advise would be great.
msndroid said:
for some reason today i started getting random reboots here and there. when i got home i decided to wipe my phone and do a clean install. everything went well, successful wipe and complete flash of the rom, but when it restarted after the flash it was still the same as before. nothing changed, all my apps, wallpaper, settings everything had been untouched. i even did fastboot wipe userdata. it was like i didnt do anything at all. then i tried wiping my internal sd card, same thing successful wipe, but it all comes back again. i did it a couple of times from the phone settings and also from my computer. then i flashed the ruu from the bootloader, everthing flash normal but when it restarted nothing changed. also tried changing my recovery to cwm but that didnt work either. tried flashing the eng bootloader and it said fail-pu.
right now im running energy rom june 19th, 4 ext recovery, joupunutbear 1.93.2222
any help or advise would be great.
Click to expand...
Click to collapse
The outlook isn't good, sorry to say that. Most likely, the internal memory chips have failed. Basically, it won't write anymore on it, meaning what you have on it right now may be stuck, permanently. This is because of the "Fail-PU" error. Before doing anything like the wire trick below, try to ensure that the RUU you're trying to flash is a correct one. It would be great if you could get a picture (or describe) what it says when the ruu flash is done. But since you have problems wiping, this may not be the issue. Try the wire trick, as described below with caution.
Unfortunately, there isn't much you can do. I've heard that sometimes if you do the wire trick, it can temporarily fix the error. Heed this. Do the wire trick on its own, meaning do not connect the phone to a computer, or run the Juopunutbear's S-OFF program, or anything of that nature. Just do the exact same wire trick (same timing too) you did to obtain s-off, but without using the s-off program, or plugging it in the computer.
Keep us updated if that trick works for you.
It would also be a good idea to flash a RUU after doing the wire trick (again, without the s-off program, or plugging it in the computer!!!)
Again, best of luck!
this is what came up.
i used this ruu
http://d-h.st/z70
msndroid said:
this is what came up.
i used this ruu
http://d-h.st/z70
Click to expand...
Click to collapse
Have you tried the trick i mentioned earlier and then flashing the RUU?
yes, i've tried it a couple of times. ill try again in the morning but i think its a lost cause though. thanks for your help.
msndroid said:
yes, i've tried it a couple of times. ill try again in the morning but i think its a lost cause though. thanks for your help.
Click to expand...
Click to collapse
theres another thing you could try too.
Boot into fastboot and then type in this command:
fastboot oem boot
Pull out your battery
Put back in.
Flash the RUU
Keylogger_0 said:
theres another thing you could try too.
Boot into fastboot and then type in this command:
fastboot oem boot
Pull out your battery
Put back in.
Flash the RUU
Click to expand...
Click to collapse
no good. i pulled the battery as soon as the htc screen came on and also when the boot animation started. still getting the same results with the ruu.
i noticed this though. isnt it supposed to be bootloader instead of misc?
INFOaARM_Partion[0].name=misc
I'm assuming you know how to use fastboot, flash your stock SHP or ENG hboot via fastboot via:
fastboot erase cache
fastboot rebootRUU
fastboot flash zip en_hboot.zip
Place the attached zip of choice be it sh or en in your adb folder and try those commands, let me know your results.
If he flashes eng hboot, redownloads ruu to ensure good download, and try flashing ruu in bootloader again... I bet it would work
Sent from my HTC VLE_U using Tapatalk 2
msndroid said:
no good. i pulled the battery as soon as the htc screen came on and also when the boot animation started. still getting the same results with the ruu.
i noticed this though. isnt it supposed to be bootloader instead of misc?
INFOaARM_Partion[0].name=misc
Click to expand...
Click to collapse
Actually, I checked it out for my phone with fastboot oem boot too. It lists the partition 0 being the misc partition too. So I think that's fine. My device is fully functional (wipe/flash capabilities included) *knocks on wood* so I think that partition is normal.
Dark Nightmare said:
I'm assuming you know how to use fastboot, flash your stock SHP or ENG hboot via fastboot via:
fastboot erase cache
fastboot rebootRUU
fastboot flash zip en_hboot.zip
Place the attached zip of choice be it sh or en in your adb folder and try those commands, let me know your results.
Click to expand...
Click to collapse
tried both and it gave me this....
C:\adb>fastboot flash zip sh_hboot.zip
sending 'zip' (396 KB)... OKAY [ 0.246s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 0.563s
To be honest I think the emmc chip although it's s-off it thinks its still s-on, my best guess would be to try s-off again, see what happens.
Sent from my SGH-T679 using xda app-developers app
msndroid said:
tried both and it gave me this....
C:\adb>fastboot flash zip sh_hboot.zip
sending 'zip' (396 KB)... OKAY [ 0.246s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 0.563s
Click to expand...
Click to collapse
Boot into fastboot, and then type in this command
fastboot oem readsecureflag
This command should return with a value of 0
If not, let us know.
Keylogger_0 said:
Boot into fastboot, and then type in this command
fastboot oem readsecureflag
This command should return with a value of 0
If not, let us know.
Click to expand...
Click to collapse
yup thats what i got.
C:\adb>fastboot oem readsecureflag
... INFOsecure_flag: 0
OKAY [ 0.007s]
finished. total time: 0.007s
I kinda gave up on the phone. Ill just buy a galaxy nexus by the end of the month. But if there's still any suggestions I can do to try to fix it, I'm willing to do so, just incase it happens to someone else. Thanks for helping.
Sent from my myTouch_4G_Slide using xda app-developers app
msndroid said:
I kinda gave up on the phone. Ill just buy a galaxy nexus by the end of the month. But if there's still any suggestions I can do to try to fix it, I'm willing to do so, just incase it happens to someone else. Thanks for helping.
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
You could try to claim warranty, but the thing is, it's already modified so most likely, they won't touch it. A fail-pu error usually means a hardware failure. Most likely, your chip failed and will not write any more.
Another thing you could try to do is brick it, and then claim warranty. You can always say that it turned off and never turned on again.
Keylogger_0 said:
You could try to claim warranty, but the thing is, it's already modified so most likely, they won't touch it. A fail-pu error usually means a hardware failure. Most likely, your chip failed and will not write any more.
Another thing you could try to do is brick it, and then claim warranty. You can always say that it turned off and never turned on again.
Click to expand...
Click to collapse
The warranty is not the same as the tmobile insurence is it? Because I took that off thinking I wouldn't need it. Also stupid question, how would I go about bricking it?lol
Sent from my myTouch_4G_Slide using xda app-developers app
msndroid said:
The warranty is not the same as the tmobile insurence is it? Because I took that off thinking I wouldn't need it. Also stupid question, how would I go about bricking it?lol
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
HTC usually has warranty too. The thing is, they will most likely refuse it if you have modified the phone.
Bricking can be easy. But, bricking with a Fail-PU error isn't always easy.
PM me later, and I will try to assist you. I'm a bit busy right now so just send me a PM to remind me.
Keylogger_0 said:
HTC usually has warranty too. The thing is, they will most likely refuse it if you have modified the phone.
Bricking can be easy. But, bricking with a Fail-PU error isn't always easy.
PM me later, and I will try to assist you. I'm a bit busy right now so just send me a PM to remind me.
Click to expand...
Click to collapse
Will do. Thanks I appreciate it
Sent from my myTouch_4G_Slide using xda app-developers app
Hi,
I'm having similar issue with my phone, tried a lot of things when I enter command
fastboot oem readsecureflag
I'm getting this:
(bootloader) secure_flag: 3
OKAY [ 0.010s]
finished. total time: 0.011s
If anybody is still checking that thread appreciate any help.
Thanks.
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
Hello,
I have tried to flash a custom ROM to my htc desire x but unfortunetly I am a almost complete noob. I have been using Desire_X_All-In-One_Kit_v2.0 in order to complete the action. The problem is that i have never rooted the fone nor i have put in the recovery into it. So basically i unlocked the bootloader and thought it would all work.Well you know yourselfs it didn't.I have been looking all over the place for a way to get my phone fixed and i found one(ima Junior member can't post links yet ( Re-flash stock ROM (RUU) after bricking a rooted device)) .I have done all the steps but in step5 i get an error
C:\rec>fastboot flash recovery recovery_signed.img
sending 'recovery' (4266 KB)...
OKAY [ 0.795s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.323s
and in step 7 i get Error 140 bootloader error during RUU
Any help here would be greatly appreciated
Regards Kuba
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
nlooooo said:
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
Click to expand...
Click to collapse
How do you mean? do you mean whats written when i enter the bootloader or what have I written in in the terminal ( eg. fastboot flash recovery recovery_signed.img)
Thanks a lot for your quick reply
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
nlooooo said:
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
Click to expand...
Click to collapse
*****RELOCKED********
PROTO PVT SHIP S-ON RL
HBOOT-1.24.0000
RADIO-1.10.40.23
eMMC-boot
Oct 30 2012, 20:09:09
The most recent RUU i have downloaded is RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed
But i have read that FAILED <remote: signature verify fail> error that im getting is related to wrong ruu .I guess you know better
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
nlooooo said:
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
Click to expand...
Click to collapse
Great man!! thanks for help!! Could you just make it clear what i need in the folder with the ruu ?. its Adb.exe AdbWinAp.dll fastBoot.exe and the image file? is there anything else i would need? (as you see i know basically nothing about this)
It's not a folder its exe file, just run it from PC.
nlooooo said:
It's not a folder its exe file, just run it from PC.
Click to expand...
Click to collapse
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
hlick14 said:
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
Click to expand...
Click to collapse
That's why I'm here and that's what the thanks button stands for...
like how it looks when i first got it is there a way? and i wanna unroot it relocking the bootloader doesnt matter it would take hours for me to relock it it seems its alot harder to unroot it then it is to root it i tried researching but i cannot by nomeans find what i need how do i do this?
did you even bother to search? there are multiple guides in the general section
stop creating unnecessary threads and learn to search
ive searched for hours all i find is stuff on how to root or perform a factory reset
i even tried downloading the ph85img.zip file and rebooted into bootloader that didnt even work that just does soething else i hvent quite figured out yet i there not a way to unroot?
Lots of ways to unroot..
Run the ruu for your carrier. In bootloader... Not recovery
You may need soff for a complete return to factory
Damn your attitude sucks!
Sig:
What do you mean I can't say that??!!.. It's the fkin Internet!
---------- Post added at 12:59 AM ---------- Previous post was at 12:58 AM ----------
avenged_sevenfold27 said:
i even tried downloading the ph85img.zip file and rebooted into bootloader that didnt even work that just does soething else i hvent quite figured out yet i there not a way to unroot?
Click to expand...
Click to collapse
You mean PH85IMG.zip.... It's CAse SENSitiVE
Sig:
What do you mean I can't say that??!!.. It's the fkin Internet!
Idk how to soff and sorry bout my attitude but I tried the PH85IMG like 10 times no luck after it says its parsing then I reboot it once its done my phone has no changes I managed to actually unroot it it was an option in supersu settings to unroot is there a telus ota that I can flash using 4ext?
Sent from my HTC_Amaze_4G using xda app-developers app
avenged_sevenfold27 said:
Idk how to soff and sorry bout my attitude but I tried the PH85IMG like 10 times no luck after it says its parsing then I reboot it once its done my phone has no changes I managed to actually unroot it it was an option in supersu settings to unroot is there a telus ota that I can flash using 4ext?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
The RUU is probably not doing anything because you are s-on and your bootloader is unlocked. To flash an ruu with s-on, you have to relock the bootloader first.
sent from.. wait, where am I?
Upgrade your T-Mobile Amaze to ICS? CLICK ME!
************************************
International/Asian Amaze? CLICK ME. Upgrade 2 ICS so you can flash custom roms
:good:If someone helped you, hit their thanks button!:good:
i think i made a big mistake i dpwnloaded the all in one toolkit and relocked the bootloader when i chose the option to flash factory ruu zip i thought that the toolkit came with it but it didnt now i can only go inbto the bootloader what do i do? how can i put the PH85IMG.zip onto my phone now?
this is what happens when i try to flash the PH85IMG.zip manually sending 'zip' (331555 KB)...
OKAY [ 31.770s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 76.186s why does it say that? i relocked my bootloader maybe im not telus? i mean i am with tmobile and my phone was unlocked when i got it so that app cid getter could be lying
avenged_sevenfold27 said:
this is what happens when i try to flash the PH85IMG.zip manually sending 'zip' (331555 KB)...
OKAY [ 31.770s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 76.186s why does it say that? i relocked my bootloader maybe im not telus? i mean i am with tmobile and my phone was unlocked when i got it so that app cid getter could be lying
Click to expand...
Click to collapse
Check cid with adb
Sig:
What do you mean I can't say that??!!.. It's the fkin Internet!
kazzxtrismus said:
Check cid with adb
Sig:
What do you mean I can't say that??!!.. It's the fkin Internet!
Click to expand...
Click to collapse
Lets make it even easier. Just use hasoon's toolkit to check the CID. Then post it here.
(Not that using adb isnt easy, but just less chance of there being a user error)