Can't de-softbrick phone, HALP!!! - HTC EVO 3D

I'm trying to de-softbrick an Evo3D for an aquaintance, and I've run out of ideas, so any help this forum is willing to offer is muy apreciada.
Info about phone:
UNLOCKED
HBOOT 1.5
S-ON
Phone will not boot to OS. Phone will boot into hboot. Recovery menu does not function, it shows the fastboot menu instead. Selecting Fastboot takes you to the Fastboot menu, which seems to work fine. Factory Reset option takes you to Fastboot menu.
Initially phone seems to load PG86IMG.zip for flashing, but when the blue loading meter fills up, it says "parsing PG86IMG.zip" for a second and then boots me back to the hboot menu, without asking me to install the file. I've tried both the stock rooted and unrooted zips.
Tried plugging the phone into my computer and running the RUU exe. It will not detect the phone, which I'm guessing is because the phone won't boot into the OS. Also, phone does not appear to respond to any adb or fastboot commands (tried doing adb pull and fastboot reboot, neither worked).
EDIT: Now the phone is detected by the RUU, but I get a 155 error code, and the phone says "Security fail!" and "Update fail!"
Again, any help is appreciated.

What happens when you try to run any fastboot command?

xxjrkkrjxx said:
What happens when you try to run any fastboot command?
Click to expand...
Click to collapse
I get < waiting for device > and it just sits there forever.

try this
Enter FASTBOOT
Open command prompt in your computer
Relock your device by typing "fastboot oem lock" , device will reboot.
Enter FASTBOOT again (you will see *** RELOCKED ***)
Apply the RUU.
RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10. 0808_NV_SPCS_1.31_003_release_219445_signed
http://www.filefactory.com/file/cfd5...445_signed.exe
Your device will be back to stock rom unrooted

Mr.Esp said:
try this
Enter FASTBOOT
Open command prompt in your computer
Relock your device by typing "fastboot oem lock" , device will reboot.
Enter FASTBOOT again (you will see *** RELOCKED ***)
Apply the RUU.
RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10. 0808_NV_SPCS_1.31_003_release_219445_signed
http://www.filefactory.com/file/cfd5...445_signed.exe
Your device will be back to stock rom unrooted
Click to expand...
Click to collapse
Here's the output of the fastboot oem lock (it's responding to fastboot commands now YAY!):
Code:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 66977136 (0x3FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
It does show the phone as relocked now, but right below the pink "***RELOCKED*** I also have ***SECURITY WARNING***. The security warning part seems to go away if I boot into hboot with the sd card removed.
EDIT: RUU worked on the second try after this. Thanks a ton!

I'm having the same issue but the link to the RUU does not work anymore, can anyone repost?

martymania85 said:
I'm having the same issue but the link to the RUU does not work anymore, can anyone repost?
Click to expand...
Click to collapse
http://tinyurl.com/6tauv3b

billdozer357 said:
Here's the output of the fastboot oem lock (it's responding to fastboot commands now YAY!):
Code:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 66977136 (0x3FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
It does show the phone as relocked now, but right below the pink "***RELOCKED*** I also have ***SECURITY WARNING***. The security warning part seems to go away if I boot into hboot with the sd card removed.
EDIT: RUU worked on the second try after this. Thanks a ton!
Click to expand...
Click to collapse
Does USB come up next to Fastboot? If so can you reflash CWM?

Related

No bootloader/fastboot/recovery Htc Desire 516 dual

This phone has never been even mentioned on xda so there is nothing to search for.
Anyways i have gone thru some threads of similar phones and tried some one click root methods. They didnt work.
So i thought i should unlock the bootloader.
Just for the sake of it i tried to boot into recovery and was successful.
Then i started following those htcdev.com instruction which required me to go into the bootloader mode.
But whenever i try doing that it either:
-Remains stuck at htc logo screen (the 1st one and not the bootanimation)
-Boots normally
then i saw that i had to press this button release this after so many seconds and......
so just to be sure that im not making those silly mistakes i tried to go into bootloader thru adb which always remains stuck at the htc splash screen (htc - powered by android).
then i tried to go to recovery but now even that isnt possible.
so in short: i cant get into the bootloader so i cant unlock or root. I cant get into the recovery either. The phone otherwise is working pretty normal. But on trying to get into any modes i remain stuck at the 1st htc screen (and not the bootanimation) and then i have to remove the battery to get it booting normally.
It is HTC Desire 516 Dual sim and is on JB 4.3 (if u needed this)
and finally i got this log from a unlock tool if it makes it easier for you
adb: reboot-bootloader
adb out:
Reboot success!
fastboot: devices
fastboot out: 0123456789ABCDEF fastboot
fastboot: oem lock
fastboot timeout
lock_failed
adb: reboot-bootloader
adb out:
Reboot success!
fastboot: devices
fastboot out: 0123456789ABCDEF fastboot
fastboot: getvar version
fastboot out: version: 0.5
finished. total time: 0.003s
fastboot: getvar version-bootloader
fastboot out: version-bootloader:
finished. total time: 0.003s
fastboot: getvar version-main
fastboot out: version-main:
finished. total time: 0.003s
fastboot: getvar serialno
fastboot out: serialno: 0123456789ABCDEF
finished. total time: 0.003s
fastboot: getvar product
fastboot out: product: MSM8610
finished. total time: 0.003s
fastboot: getvar modelid
fastboot out: modelid:
finished. total time: 0.003s
fastboot: getvar cidnum
fastboot out: cidnum:
finished. total time: 0.003s
fastboot: getvar build-mode
fastboot out: build-mode:
finished. total time: 0.003s
fastboot: getvar boot-mode
fastboot out: boot-mode:
finished. total time: 0.003s
fastboot: getvar security
fastboot out: security:
finished. total time: 0.003s
fastboot: getvar imei
fastboot out: imei:
finished. total time: 0.003s
fastboot: oem get_identifier_token
fastboot timeout
get_device_info_failed
Click to expand...
Click to collapse
pls do help if u can :highfive: :fingers-crossed:
noone? @psych.half suggest anything?
T3snake said:
noone? @psych.half suggest anything?
Click to expand...
Click to collapse
Remove your battery before trying to boot into fastboot.
If you can't remove your battery, go to Settings->Power options And disable fast boot
dummie999 said:
Remove your battery before trying to boot into fastboot.
If you can't remove your battery, go to Settings->Power options And disable fast boot
Click to expand...
Click to collapse
yea tried that..
same result
btw volume up brings up recovery and down brings bootloaderr
is fastboot a different mode or u call bootloader mode and fastboot the same..?
T3snake said:
yea tried that..
same result
btw volume up brings up recovery and down brings bootloaderr
is fastboot a different mode or u call bootloader mode and fastboot the same..?
Click to expand...
Click to collapse
Yes fastboot and bootloader are the same
Have you tried booting into bootloader with "adb reboot bootloader"
Info
You are not alone !
Now can have all the stock files here .
dummie999 said:
Yes fastboot and bootloader are the same
Have you tried booting into bootloader with "adb reboot bootloader"
Click to expand...
Click to collapse
yea both recovery and bootloader isnt accessible by adb
joldisadrian said:
You are not alone !
Now can have all the stock files here .
Click to expand...
Click to collapse
but there are only kernel sources
T3snake said:
yea both recovery and bootloader isnt accessible by adb
Click to expand...
Click to collapse
How do you mean isn't accesible? What do you see when you type those commands? What is the output?
I have this device, and i booted it in fastboot mode successfully. Open ADB and type "adb reboot-bootloader", the phone will reboot and remain stuck in the boot logo (the first). Now open fastboot and type "fastboot devices" and it will be recognized. I can't unlock bootloader, because when i type "fastboot oem get_identifier_token" it remains stuck, and it's so annoying because i want to root this device, can you help me? :crying:
I'm having the same problem. The bootloader is not accessible. I tried all possible root methods but none work. Kinda regretting now buying this phone
dummie999 said:
How do you mean isn't accesible? What do you see when you type those commands? What is the output?
Click to expand...
Click to collapse
As I said it reboots but remains stuck at HTC logo until removal of battery
Sent from my SM-T211 using Tapatalk
AceXer said:
I have this device, and i booted it in fastboot mode successfully. Open ADB and type "adb reboot-bootloader", the phone will reboot and remain stuck in the boot logo (the first). Now open fastboot and type "fastboot devices" and it will be recognized. I can't unlock bootloader, because when i type "fastboot oem get_identifier_token" it remains stuck, and it's so annoying because i want to root this device, can you help me? :crying:
Click to expand...
Click to collapse
So since its stuck and we can't do anything
BTW we had an 110 mb update just a few days ago but since my phone can't get into recovery the final steps don't take place where it goes to recovery and finishes up(in my case it remains stuck at HTC logo so device remains as it was when I boot it normally)
Sent from my SM-T211 using Tapatalk
rakeshz said:
I'm having the same problem. The bootloader is not accessible. I tried all possible root methods but none work. Kinda regretting now buying this phone
Click to expand...
Click to collapse
Well if they gave us an app2sd feature I ccud forgive em a bit.
I contacted the customer service and when I mentioned a stuck up screen they immediately asked if I WS rooting. So maybe htc did it intentionally or maybe some1 fishy intervened or something
Sent from my SM-T211 using Tapatalk
T3snake said:
Well if they gave us an app2sd feature I ccud forgive em a bit.
I contacted the customer service and when I mentioned a stuck up screen they immediately asked if I WS rooting. So maybe htc did it intentionally or maybe some1 fishy intervened or something
Sent from my SM-T211 using Tapatalk
Click to expand...
Click to collapse
Yes, seriously we need the move to sd card feature. The whole reason of having a feature phone without being able to install any apps or big games sucks
rakeshz said:
Yes, seriously we need the move to sd card feature. The whole reason of having a feature phone without being able to install any apps or big games sucks
Click to expand...
Click to collapse
I calculated and found that u can get Max 1.7 GB free (as indicated by the mobile) but if u use mtp or reach 1.5 GB u will not be able to put anything more since there shud always be 200mb free
So we get only 1.5 GB after disabling all the preinstalled apps
Sent from my SM-T211 using Tapatalk
So I'm able to boot into fastboot mode, I'm able to boot into recovery mode. But how can we unlock the bootloader?
AceXer said:
So I'm able to boot into fastboot mode, I'm able to boot into recovery mode. But how can we unlock the bootloader?
Click to expand...
Click to collapse
Go to htcdev.com
If u can get into fastboot mode u can run some commands to get a token paste the token at the place indicated and follow the steps
Sent from my GT-S5282 using Tapatalk
T3snake said:
Go to htcdev.com
If u can get into fastboot mode u can run some commands to get a token paste the token at the place indicated and follow the steps
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
Yes, but this device isn't in the list, and when I type (in fastboot mode) "fastboot oem get_identifier_token" it stuck and three dots appear.
All command work, but if i type "oem" after "fastboot" (ex. "fastboot oem command list) it stuck with three dots. Help meeeee pleease!
AceXer said:
Yes, but this device isn't in the list, and when I type (in fastboot mode) "fastboot oem get_identifier_token" it stuck and three dots appear.
All command work, but if i type "oem" after "fastboot" (ex. "fastboot oem command list) it stuck with three dots. Help meeeee pleease!
Click to expand...
Click to collapse
Hi,
I have same device and same problems. I think I tried all solutions I've seen so far. I had HTC wildfire, Motorola XT530, Huawei Ascend G300, HTC Desire X, and I have some expirience rooting, but this phone makes me sick. Just sent an rage mail to HTC, saying that they made great little piece of hardware with software making it almost unusable. So far I tried SuperOneClick, RootGenius and adb root, but nothing works.

[Q] AT&T One M9 identifier token error

I'm trying to unlock the bootloader of my One M9 so that I can use Sunshine and get S Off. In the end I'm trying to convert it to the dev version. I've unlocked the bootloaders of my M7 and M8 before this but for some reason it is giving me an error this time. It says "FAILED (remote: unknown command)" every time I try. I've tried with sync manager install and uninstalled. I really have no idea why this is happening. I tried to get the tokens on the M7 and M8 with the same drivers to test them and everything went as usual. Can anyone help me with this?
Thanks
Schmerg said:
I'm trying to unlock the bootloader of my One M9 so that I can use Sunshine and get S Off. In the end I'm trying to convert it to the dev version. I've unlocked the bootloaders of my M7 and M8 before this but for some reason it is giving me an error this time. It says "FAILED (remote: unknown command)" every time I try. I've tried with sync manager install and uninstalled. I really have no idea why this is happening. I tried to get the tokens on the M7 and M8 with the same drivers to test them and everything went as usual. Can anyone help me with this?
Thanks
Click to expand...
Click to collapse
I think you need to be in download mode for the fastboot commands to work.
dratsablive said:
I think you need to be in download mode for the fastboot commands to work.
Click to expand...
Click to collapse
Wow thank you so much. I didn't know I needed to be in download mode.
Much appreciated!
I found that in Download mode I couldn't get the identifier token for some reason. I had to boot into the bootloader then use "fastboot oem rebootRUU" to get into RUU mode. THEN I was able to get the identifier token, but I couldn't flash the Unlock file unless I was in Download mode. A little more convoluted then the M8
navalynt said:
I found that in Download mode I couldn't get the identifier token for some reason. I had to boot into the bootloader then use "fastboot oem rebootRUU" to get into RUU mode. THEN I was able to get the identifier token, but I couldn't flash the Unlock file unless I was in Download mode. A little more convoluted then the M8
Click to expand...
Click to collapse
How do I boot into boot loader? I'm only getting command not found in terminal every time I type in the fast boot command...
elusivepuma said:
How do I boot into boot loader? I'm only getting command not found in terminal every time I type in the fast boot command...
Click to expand...
Click to collapse
easy way is enable developer options on the phone
turn on usb debugging hook phone to PC
from command prompt on PC type adb reboot download
navalynt said:
I found that in Download mode I couldn't get the identifier token for some reason. I had to boot into the bootloader then use "fastboot oem rebootRUU" to get into RUU mode. THEN I was able to get the identifier token, but I couldn't flash the Unlock file unless I was in Download mode. A little more convoluted then the M8
Click to expand...
Click to collapse
Hello there. I am not able to get identifier token both in bootloader and download mode. I tried adb reboot bootloader first, successfully entered in bootloader. After typing fastboot oem_get_identifier_token
stuck in error FAILED (remote : unknown command)
and same as for adb reeboot download mode.
What should i do now?
I have HTC Desire 626s.
Thanks in advance
aashish981 said:
Hello there. I am not able to get identifier token both in bootloader and download mode. I tried adb reboot bootloader first, successfully entered in bootloader. After typing fastboot oem_get_identifier_token
stuck in error FAILED (remote : unknown command)
and same as for adb reeboot download mode.
What should i do now?
I have HTC Desire 626s.
Thanks in advance
Click to expand...
Click to collapse
Command is wrong. Try fastboot oem get_identifier_token
Hi guys,
im trying to unlock to the bootloader. I use the command "fastboot oem get_identifier_token" from the website "htcdev". But i get no token, there is showing following issue:
C:\Fastboot>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.100s]
finished. total time: 0.101s
my htc one m9 please help me
<<<< Identifier Token Start >>>>
1E273FDE078CCB771DFA5E6A826083BF
2D6F6C1A962A39E4A133A5B95214CA0C
F856D703BD183517577291FAB5F6A6B4
5307F3888E6CA0C866411B1072588567
F0D67ED66548E31EA4332612B2DA089C
8A96B3918CC122D63AC944BB7E790F47
490E35E4BF24C7956207A709BF6B33C0
7DD92A84CACAF4487F4DFE44D11A4C9B
1D6366A63326C6DBE442CE57A92CA767
F7F09206F75E6E2B606759953F259B23
2C9D86AFCE30EEAE3021231698C1A624
0DCD40A03C61A8CF4D809BC1DAAB589B
D16914018ADBA0029C8CB95A8C2D6513
F49A75ABE7A574BF288E16C50C98870B
8909B333B14FC6F60F977A301919DF6A
83192A7E07B091DA044374F432BB1B82
<<<<< Identifier Token End >>>>>
send me the Unlock_code.bin for my email.
[email protected]

Unable to unlock bootloader

Hi,
This morning i had the very bad idea of changing my recovery, and now I'm stuck!
I'm running CM13 and i wanted to update to the latest release, but I got errors, so I said "well, maybe they need their recovery and TWRP is not good anymore for some reasons.
I downloaded the new recovery from CM website (yes, it is the correct version of the phone) and installed it. Well, i don't know what happened, but now I'm stuck into the bootloader (fastboot mode detects my device in cmd)
I decided to flash TWRP again, but now my bootloader is locked (for some mysterious reason, as it was unlock by both the dev option toggle and by a previous OEM unlock command).
I've been trying to unlock it again, but nothing. I lunch
Code:
fastboot oem unlock
and all it does is coming up with this message:
Code:
OKAY [ 0.015s]
finished. total time: 0.016s
The phone reboots and it's stuck as I have access to neither recovery or OS. It just stays there and i have to go back into the bootloader.
the device info from fastboot is:
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.010s]
finished. total time: 0.010s
I also tried with
Code:
fastboot flashing unlock
but it stays stuck with the 3 dots without doing anything.
Is there anything i can do or i have to trough my device into the bin?
thanks
nickimola said:
Hi,
This morning i had the very bad idea of changing my recovery, and now I'm stuck!
I'm running CM13 and i wanted to update to the latest release, but I got errors, so I said "well, maybe they need their recovery and TWRP is not good anymore for some reasons.
I downloaded the new recovery from CM website (yes, it is the correct version of the phone) and installed it. Well, i don't know what happened, but now I'm stuck into the bootloader (fastboot mode detects my device in cmd)
I decided to flash TWRP again, but now my bootloader is locked (for some mysterious reason, as it was unlock by both the dev option toggle and by a previous OEM unlock command).
I've been trying to unlock it again, but nothing. I lunch and all it does is coming up with this message:
The phone reboots and it's stuck as I have access to neither recovery or OS. It just stays there and i have to go back into the bootloader.
the device info from fastboot is:
I also tried with but it stays stuck with the 3 dots without doing anything.
Is there anything i can do or i have to trough my device into the bin?
thanks
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page18
shravanv3 said:
Try this
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page18
Click to expand...
Click to collapse
Yes, this worked!
Thanks a lot.

Stuck in Fastboot

Hello there!
I was on Sultanxds Custom rom + kernel and decided to flash another Rom. Therefore i wanted to update my TWRP to Version 3.0.2.0.
So i went into fastboot, connected my phone to the pc as always an ran the comand: "fastboot flash recovery twrp-3.0.2-0-onyx-20161116-113742.img". I got the message: "FAILED (remote: Device not unlocked cannot flash or erase)"
So i checked for oem unlock and this was the message i got.
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false"
I just dont understand why the bootloader is locked... how is this even possible but anyways so i tried to just normaly reboot the device. But now i see the 1+ logo for 1 sec and it vibrates. And then it turns black again and I see the logo again and again...
But i'm still able to enter fastboot mode and i can send command from my PC. Can anyone tell what steps i have to do to make it bootable again? (is this a hardbrick?).
Thx in advice!
I just followed the hardbrick guide and i'm now on stock OS. For some reason the bootloader was locked again... problem solved and this thread can be closed...

Help unbricking ANE-LX1 9.1.0.360

fastboot oem get-build-number
(bootloader) :ANE-LX1 9.1.0.360(IRLC368E6R1P6)
fastboot getvar vendorcountry
vendorcountry: h3g/ie
fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :ANE-LX1-CUST 9.1.0.6(IRLC368)
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.134(IRLC368E4R1P6)
Click to expand...
Click to collapse
First, this phone has been hell, no other phone that I've ever tried to root behaved like this, anyways, yesterday I unlocked my bootloader using the PotatoNV Test pin method, All was smooth sailing until I tried installing TWRP with the help of this thread, but somewhere along the line, everything just broke, For some reason every time I flash 'recovery_ramdisk' it does nothing, I still get put into the stock eRecovery.
Some more info:
Phone: UNLOCKED
FRP: UNLOCKED
After flashing 'recovery_ramdisk', the phone boots up for a second, than turns back on, than it boots to the 'Your device cant be trusted screen'
I have 2 options, boot into recovery, or the system.
I cant seem to boot into TWRP as it always boots into eRecovery, the 'Update and recover system' Button doesn't work, it always fails to fetch info.
when I boot into the system I get promoted with.
ERROR MODE
Attention!
Please update system again
Error!
Func NO: 10 (Boot image)
Func NO: 2 (Load failed!)
Click to expand...
Click to collapse
Any help would be greatly appreciated, guides on reflashing everything to stock etc.
In fastboot flash EMUI 9.1 Stock recovery_ramdisk, download here
- fastboot reboot
- When the yellow warning appears, press and hold Vol Up. In eRecovery turn off your phone.
- Then press and hold Power & Vol Up, your phone should reboot into Recovery.
Thank you! Last step cleared everything up a lot

Categories

Resources