Database Info

Stock Recovery zip

Hi, am looking for the stock recovery file/zip p[ease.

The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.

_that said:
The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.
Click to expand...
Click to collapse
Thanks.

_that said:
The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.
Click to expand...
Click to collapse
I got the firmware and extracted the blob, but I only have fastboot, how do I flash it to get stock recovery back?
I tried this:
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 flash system blob
but nothing works, except I lost /system partition now (I was able to boot Android before). Any help appreciated.

3c said:
I got the firmware and extracted the blob, but I only have fastboot, how do I flash it to get stock recovery back?
I tried this:
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 flash system blob
but nothing works, except I lost /system partition now (I was able to boot Android before). Any help appreciated.
Click to expand...
Click to collapse
Sorry, if that doesn't work I have no more idea how to fix your locked tablet, if you don't have the blob for wheelie and nvflash.

_that said:
Sorry, if that doesn't work I have no more idea how to fix your locked tablet, if you don't have the blob for wheelie and nvflash.
Click to expand...
Click to collapse
Thanks anyway for helping. All I could figure out is that the blob doesn't actually get written to any partition. I've seen some users be successful doing that (what you suggested), so I'll keep trying, maybe reverting the driver. Wondering if using naked driver works well for such method.
In any case, thanks, and I'll post a reply if I can make it work.

3c said:
Thanks anyway for helping. All I could figure out is that the blob doesn't actually get written to any partition. I've seen some users be successful doing that (what you suggested), so I'll keep trying, maybe reverting the driver. Wondering if using naked driver works well for such method.
In any case, thanks, and I'll post a reply if I can make it work.
Click to expand...
Click to collapse
Try this, download stock recovery here http://www.mediafire.com/download.php?pdipp4h2qyqka63
then execute this:
fastboot -i 0x0B05 flash recovery recovery.blob
boot directly into recovery and see if you have recovery back.

buhohitr said:
Try this, download stock recovery here http://www.mediafire.com/download.php?pdipp4h2qyqka63
then execute this:
fastboot -i 0x0B05 flash recovery recovery.blob
boot directly into recovery and see if you have recovery back.
Click to expand...
Click to collapse
Big progress: blob flashed without a glitch. I was happy until I tried to reboot with fastboot: tablet frozen! Reboot, still no recovery
I guess this is it. Got a nice folding brick now! Will try RMA, but from Cambodia not sure it's worth it. Maybe next month when I'm in France.
Can't believe this happened while tablet is locked! Now I hate Asus for this.

3c said:
Big progress: blob flashed without a glitch. I was happy until I tried to reboot with fastboot: tablet frozen! Reboot, still no recovery
I guess this is it. Got a nice folding brick now! Will try RMA, but from Cambodia not sure it's worth it. Maybe next month when I'm in France.
Can't believe this happened while tablet is locked! Now I hate Asus for this.
Click to expand...
Click to collapse
I have asked you to flash the recovery zip, but once done you should boot directly into the recovery, don't boot up. Let me know if you still can fastboot the recovery to your device, but once done, hold the power until device turn off, then right away hold both power button and volume down button to boot into recovery. If you could do this we still have hope. Once in recovery let me know we can proceed to next step.

buhohitr said:
I have asked you to flash the recovery zip, but once done you should boot directly into the recovery, don't boot up. Let me know if you still can fastboot the recovery to your device, but once done, hold the power until device turn off, then right away hold both power button and volume down button to boot into recovery. If you could do this we still have hope. Once in recovery let me know we can proceed to next step.
Click to expand...
Click to collapse
I cannot actually do anything past flashing a blob. the tablet is "frozen" from the moment it enters fastboot, then after flashing any blobs, any further fastboot command are "non-responsive", here is the actual output. At the end the reboot command succeeds but nothing actually happened on the tablet. Still showing the 4 icons (RCK/Android/USB/WIPE) and the top white text. Tried with original Asus driver, with Google driver and now naked driver. no difference, can only be the tablet ;(
C:\Android\android-sdk\platform-tools>fastboot devices
015d2a5088641a08 fastboot
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery.blob
sending 'recovery' (6260 KB)...
OKAY [ 1.862s]
writing 'recovery'...
OKAY [ 2.432s]
finished. total time: 4.297s
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.642s
C:\Android\android-sdk\platform-tools>fastboot continue
resuming boot...
FAILED (command write failed (Unknown error))
finished. total time: 0.569s
C:\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
EDIT: Kinda lame I'm sure, but desperate as I am, I tried that too:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 boot recovery.blob
creating boot image...
creating boot image - 6414336 bytes
downloading 'boot.img'...
OKAY [ 1.857s]
booting...
FAILED (remote: ()
finished. total time: 1.861s
I suppose I need a kernel blob... But I couldn't find any stock to flash? Would you also happen to have that handy too?

3c said:
I cannot actually do anything past flashing a blob. the tablet is "frozen" from the moment it enters fastboot, then after flashing any blobs, any further fastboot command are "non-responsive", here is the actual output. At the end the reboot command succeeds but nothing actually happened on the tablet. Still showing the 4 icons (RCK/Android/USB/WIPE) and the top white text. Tried with original Asus driver, with Google driver and now naked driver. no difference, can only be the tablet ;(
C:\Android\android-sdk\platform-tools>fastboot devices
015d2a5088641a08 fastboot
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery.blob
sending 'recovery' (6260 KB)...
OKAY [ 1.862s]
writing 'recovery'...
OKAY [ 2.432s]
finished. total time: 4.297s
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.642s
C:\Android\android-sdk\platform-tools>fastboot continue
resuming boot...
FAILED (command write failed (Unknown error))
finished. total time: 0.569s
C:\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
EDIT: Kinda lame I'm sure, but desperate as I am, I tried that too:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 boot recovery.blob
creating boot image...
creating boot image - 6414336 bytes
downloading 'boot.img'...
OKAY [ 1.857s]
booting...
FAILED (remote: ()
finished. total time: 1.861s
I suppose I need a kernel blob... But I couldn't find any stock to flash? Would you also happen to have that handy too?
Click to expand...
Click to collapse
Seems like when you flashed the blob file it wipe out everything. But I tried to boot into recovery so it's a good sign that your tablet is not brick ....yet!!
Here is the stock kernel I created for you http://www.mediafire.com/download.php?16fji3z1nghr6th
fastboot -i 0x0B05 flash boot boot.blob
Possible we may need the bootloader too, but will see.

buhohitr said:
Seems like when you flashed the blob file it wipe out everything. But I tried to boot into recovery so it's a good sign that your tablet is not brick ....yet!!
Here is the stock kernel I created for you http://www.mediafire.com/download.php?16fji3z1nghr6th
fastboot -i 0x0B05 flash boot boot.blob
Possible we may need the bootloader too, but will see.
Click to expand...
Click to collapse
I guess I'm ready for bootloader flashing. Either it bricks it for good or it works or else
Nothing has changed. Just to give you more info, booting RCK, results in booting failed - unrecoverable bootloader error (0x000..).
Booting android: cold-booting linux - signature match. Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
So I tried flashing boot.blob and recovery.blob and the JB update blob to system again, but it hangs at the end, still have to reboot manually. It's like fastboot is not actually flashing anything, writing in below output is abnormally low or could it be that fast!?: It's the same time for boot, recovery of a 800Mb system file!?
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.329s]
sending 'system' (800199 KB)...
OKAY [141.653s]
writing 'system'...
OKAY [ 2.932s]
finished. total time: 146.920s
But the behavior of the bootloader seems quite strange, all this hanging at end of flashing, could this be a corrupted bootloader or worse a corrupted partition table?

3c said:
I guess I'm ready for bootloader flashing. Either it bricks it for good or it works or else
Nothing has changed. Just to give you more info, booting RCK, results in booting failed - unrecoverable bootloader error (0x000..).
Booting android: cold-booting linux - signature match. Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
So I tried flashing boot.blob and recovery.blob and the JB update blob to system again, but it hangs at the end, still have to reboot manually. It's like fastboot is not actually flashing anything, writing in below output is abnormally low or could it be that fast!?: It's the same time for boot, recovery of a 800Mb system file!?
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.329s]
sending 'system' (800199 KB)...
OKAY [141.653s]
writing 'system'...
OKAY [ 2.932s]
finished. total time: 146.920s
But the behavior of the bootloader seems quite strange, all this hanging at end of flashing, could this be a corrupted bootloader or worse a corrupted partition table?
Click to expand...
Click to collapse
Let try the bootloader http://www.mediafire.com/download.php?u6bwnaao6khcdaf

3c said:
Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
Click to expand...
Click to collapse
Define "Windows recognizes the tablet". If you have ADB access, you should be able to recover.

buhohitr said:
Let try the bootloader http://www.mediafire.com/download.php?u6bwnaao6khcdaf
Click to expand...
Click to collapse
Actually how do you flash bootloader? I did this: fastboot -i 0x0B05 flash bootloader loader.blob ?
But anyway, I just read fastboot doesn't flash anything when device is locked! So this piece of s**t doesn't flash but will erase any partition you wish! How's that for a crappy software! I wish I never tried to update to JB!
_that said:
Define "Windows recognizes the tablet". If you have ADB access, you should be able to recover.
Click to expand...
Click to collapse
No ADB, just the name of the tablet appears in Device Manager, sort of the SD card access, but no actual access. I updated the driver manually and was proposed some MTP device. No adb or fastboot when this is available.
Here is the input from another thread: I copy it because I believe the information is very important and identify another way to brick the TF700:
Pretoriano80 said:
ICS bootloader had the fastboot option disabled if the device's bootloader was still locked and the USB icon wasn't showing at all.
With the JB bootloader Asus made the USB icon available even if the device was locked so you can access fastboot mode but you can't flash anything (yes,it doesn't make sense, but this is Asus).
Anyway, if you are able to boot in recovery you should be able to restore you device easily,just follow my guide from the general forum.
Click to expand...
Click to collapse
That's exactly what's happening! I can go in fastboot, but it doesn't flash anything! Though it erase any partition you wish! How smart is that? So I have one thing to say to locked owner: never go in fastboot, ever, it's useless and can actually brick your tablet!!!
I bricked the tablet on my own sure enough, but without this ridiculous fastboot I wouldn't have been able to mess up the tablet in the first place! Sorry for those who love their tablet and Asus, but I find their strategy ridiculous. Except if it's main goal is to make money on RMA.
Thanks Asus for this nice brick!

3c said:
But anyway, I just read fastboot doesn't flash anything when device is locked! So this piece of s**t doesn't flash but will erase any partition you wish!
Click to expand...
Click to collapse
I'd still expect the locked bootloader to flash correctly signed blobs. But who knows what Asus were thinking...
One more idea you can try: Get the 10.4.4.23 dlpkgfile and extract the blob from there.
This blob contains the 10.4.4.23 bootloader, stock recovery and stock kernel, and an orignal Asus signature. My WW version is 13573093 bytes, so it is much smaller than the full firmware blob - try to flash that via fastboot, maybe you are lucky and it works.

_that said:
I'd still expect the locked bootloader to flash correctly signed blobs. But who knows what Asus were thinking...
One more idea you can try: Get the 10.4.4.23 dlpkgfile and extract the blob from there.
This blob contains the 10.4.4.23 bootloader, stock recovery and stock kernel, and an orignal Asus signature. My WW version is 13573093 bytes, so it is much smaller than the full firmware blob - try to flash that via fastboot, maybe you are lucky and it works.
Click to expand...
Click to collapse
Will do, thanks. How would you flash such blob? Onto "staging" or "system"? I've seen users flash the JB update blob to system and be successful. Also seen some posts mentioning staging?

3c said:
Will do, thanks. How would you flash such blob? Onto "staging" or "system"? I've seen users flash the JB update blob to system and be successful. Also seen some posts mentioning staging?
Click to expand...
Click to collapse
I don't really know - all I know is:
- TF700's fastboot implementation only supports blobs, no raw partition images
- blobs are usually always written to the staging partition first, then the contained partition images are flashed to the correct partition(s) by the bootloader
I've seen both variants of the fastboot command, so maybe the target partition doesn't matter when sending blobs. I'd try staging first.

stuck on a black HTC screen with 4 warning triangles in each corner

I flashed HPSGill's rom on Friday which is Sense 5 themed, It didn't boot up. So I went back to recovery, wiped everything down, and proceeded to flash the stock ROM. The RUU installation failed, giving me a 150 Error. I have used the same RUU for a year now. I then tried running some fastboot commands but most of them give me "REMOTE: NOT ALLOWED".
The phone goes into fastboot mode as when I execute "fastboot devices" i see my phone serial number on the command line. I can't however access adb. On removing the cable it takes me to the bootloader white screen, only now, the options for reboot, reset factory settings, recovery, etc, are not visible.
It just shows me my phone information, bootloader as relocked, and RUU highlighted. I have tried flashing the RUU multiple times, after each flash attempt, all partitions, except the userdata partition shows userdata FAIL-PU, which as I understand is the partition update failing, bootloader shows - BYPASSED. I have also tried downloading the same RUU just in case somehow the one I had was corrupted. But same result.
HTC service center says since I have rooted my phone, I will have to pay 6000 rs. for a 7000rs. phone to get it repaired. Is there any way back from this ? I have sent it to the service center and will get it back tomorrow, So I can only post screenshots if needed tomorrow. I have scoured the internet for the solution and I have read some odd success stories, but none of them for the explorer, mostly for desires. Any help appreciated.
I will be trying bortak's guide in the meanwhile which is again for htc desire.

Well from what I get so far you're stuck in the middle of a bad RUU flash, idea is you need to complete an RUU flash before you can do anything else, from this I get only try flashing several times this RUU or try with some another RUU else, if there is no fastboot this is hard to be fixed, try sending pm to @legen_dary , he experimented for a while to find some s-off way, so he should know a little bit more about this stuff. I'll continue the search, if find something will share, you also, do share what have you discovered, and if something works what is it.

shortyoko said:
Well from what I get so far you're stuck in the middle of a bad RUU flash, idea is you need to complete an RUU flash before you can do anything else, from this I get only try flashing several times this RUU or try with some another RUU else, if there is no fastboot this is hard to be fixed, try sending pm to @legen_dary , he experimented for a while to find some s-off way, so he should know a little bit more about this stuff. I'll continue the search, if find something will share, you also, do share what have you discovered, and if something works what is it.
Click to expand...
Click to collapse
Thanks for the reply. As I mentioned, the moment i connect the phone via the USB cable, it automatically goes into fastboot mode as when i run "fastboot devices", my device shows up. So I'm considering, not all hope is lost. I have to get to work, will be getting my phone back today, will experiment some and get back here at night.
forgot to mention a couple of things.
1. the bootloader shows relocked. On running the fastboot flash unlocktoken Unlock_code.bin, the command completes successfully but the bootloader still shows relocked. And because it constantly shows relocked, I'm not able to install a custom recovery as well.
2. tried putting the rom in the RUU on sdcard and renaming it as PBsomething.zip. but it wont read the sd card. So flashed it manually via fastboot flash zip zipname.zip runs upto a certain point then gives me something like this
RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" So I tried reflashing it, but keeps giving the same error.
So since the sd card is not being read at all, I guess bortak's method of creating a goldcard goes out the window.

Hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
If it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
ғг๏๓ ҭђє ғเรђ™
---------- Post added at 08:19 AM ---------- Previous post was at 08:15 AM ----------
legen_dary said:
hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
if it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
Edit : The correct filename is pj03img.zip(or something)..
When the phone first starts in the hboot, you should see a series of filenames, along with "not found" errors.. If you do, then it does scan the sdcard...
ғг๏๓ ҭђє ғเรђ™
Click to expand...
Click to collapse
ғг๏๓ ҭђє ғเรђ™

legen_dary said:
Hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
If it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
ғг๏๓ ҭђє ғเรђ™
---------- Post added at 08:19 AM ---------- Previous post was at 08:15 AM ----------
ғг๏๓ ҭђє ғเรђ™
Click to expand...
Click to collapse
Thanks. will try it out and get back to you but after about 12 hours, I am yet to get back my phone and gotta get to work.

burnt nand
your nand is burnt.you should use cute_prince's method.
Steps of solution
1.flash twrp via fastboot -------fastboot flash recovery twrp.img
2.boot recovery via fastboot------fastboot boot twrp.img
3.apply cute prince method -------http://forum.xda-developers.com/showpost.php?p=36868966&postcount=2367
4.re lock bootloader via fastboot ------fastboot oem lock
5.run compatible ruu
6[optional ] unlock bootloader and Flash favourite rom

juristokrat said:
your nand is burnt.you should use cute_prince's method.
Steps of solution
1.flash twrp via fastboot -------fastboot flash recovery twrp.img
2.boot recovery via fastboot------fastboot boot twrp.img
3.apply cute prince method -------http://forum.xda-developers.com/showpost.php?p=36868966&postcount=2367
4.re lock bootloader via fastboot ------fastboot oem lock
5.run compatible ruu
6[optional ] unlock bootloader and Flash favourite rom
Click to expand...
Click to collapse
He's unable to unlock the bootloader so it's impossible to flash a custom recovery
You can't use fastboot boot or fastboot flash with a locked bootloader. Can you get into HBOOT mode by holding volume down and power while switching on the device? Or does it go straight into FASTBOOT mode?

i tried
1) unlocking bootloader, and now its unlocked.
2) fastboot getvar all gives me
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.03.0000
(bootloader) version-baseband: 1.11.82.17
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.720.3
(bootloader) serialno: ********
(bootloader) imei: *******
(bootloader) product: pico
(bootloader) platform: HBOOT-7225A
(bootloader) modelid: PJ0310000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3673mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 30d3dcb5
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.032s
3) fastboot oem boot boots up the phone and is now stuck in a bootloop. gives me the htc jingle and restarts. tried pulling the battery and volume down + power combination to get to the hboot menu, but brings me back to the black htc screen with 4 triangles. At least there is some progress. Now I somehow just need to get that menu back that comes up after the volume down + power combination.
4) tried fastboot oem resetRUUflag and it gave me this -
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
5) tried fastboot boot hboot.img with the boot.img from the RUU
it gave me -
creating boot image...
creating boot image - 788480 bytes
downloading 'boot.img'...
OKAY [ 0.263s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 0.300s

Can you get into recovery?

The boot.img file is the kernel bro.. Not the hboot..
The file you're looking for is hboot -something-something.img
ғг๏๓ ҭђє ғเรђ™

@sachin thomas - No I can't get into recovery
@legen_dary - hboot_1.03.0000_30d3dcb5_1129_signed this one right ? i just renamed it to hboot.img to avoid typing or copying the whole name
EDIT : i find this flag out of place . (bootloader) boot-mode: RUU. should it be RUU ? i think this is the one causing all the problem, though of course i may be wrong.

salil_1337 said:
@sachin thomas - No I can't get into recovery
@legen_dary - hboot_1.03.0000_30d3dcb5_1129_signed this one right ? i just renamed it to hboot.img to avoid typing or copying the whole name
EDIT : i find this flag out of place . (bootloader) boot-mode: RUU. should it be RUU ? i think this is the one causing all the problem, though of course i may be wrong.
Click to expand...
Click to collapse
You can't boot from a signed HBOOT image because it's a plain binary file and not an android boot image. As you have unlocked the bootloader try fastboot boot with any recovery.img file (CWM or TWRP)

Sachin Thomas said:
You can't boot from a signed HBOOT image because it's a plain binary file and not an android boot image. As you have unlocked the bootloader try fastboot boot with any recovery.img file (CWM or TWRP)
Click to expand...
Click to collapse
EXCELLENT !
did this -
I:\Android Rooting\Flash>fastboot boot recovery-clockwork-5.0.2.8-pico.img
downloading 'boot.img'...
OKAY [ 0.810s]
booting...
OKAY [ 0.014s]
finished. total time: 0.834s
and now I am in CWM recovery screen.
EDIT 1: wiped all partitions.
EDIT 2 : rebooted the phone to check if it let me into the hboot menu, but it comes back to the black htc screen with 4 exclamation marks

salil_1337 said:
EXCELLENT !
did this -
I:\Android Rooting\Flash>fastboot boot recovery-clockwork-5.0.2.8-pico.img
downloading 'boot.img'...
OKAY [ 0.810s]
booting...
OKAY [ 0.014s]
finished. total time: 0.834s
and now I am in CWM recovery screen.
EDIT : wiped all partitions.
Click to expand...
Click to collapse
To be on the safer side do cute_prince's nand recovery procedure as juristokrat suggested

Sachin Thomas said:
To be on the safer side do cute_prince's nand recovery procedure as juristokrat suggested
Click to expand...
Click to collapse
i did that when i got my nand burned after installing cm10 beta 6. But AFAIK and as far as I understand, i need to place the flash_erase file into system/xbin. I am right now stuck in recovery. How am I supposed to do it from there ? is there a flashable zip for it which will run the commands via recovery ?
EDIT : this is FAR better than i expected. since I'm in recovery, adb devices spits this out -
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH1BJVN07184 recovery

salil_1337 said:
i did that when i got my nand burned after installing cm10 beta 6. But AFAIK and as far as I understand, i need to place the flash_erase file into system/xbin. I am right now stuck in recovery. How am I supposed to do it from there ? is there a flashable zip for it which will run the commands via recovery ?
Click to expand...
Click to collapse
Mount your SD card in recovery and place the file in the root of the SD card. Now, if you have TWRP you can use its file manager to move it into system/xbin and set permissions to 755
If you have CWM you can type the following in adb shell:
cd /
mv /sdcard/flash_erase /system/xbin
cd system/xbin
chmod 755 flash_erase
Click to expand...
Click to collapse
Then find a newer RUU and run it

Sachin Thomas said:
Mount your SD card in recovery and place the file in the root of the SD card. Now, if you have TWRP you can use its file manager to move it into system/xbin and set permissions to 755
If you have CWM you can type the following in adb shell:
Click to expand...
Click to collapse
OK. booted via twrp, copied file from sd card, but there seems to be no xbin folder in system
EDIT : ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen

salil_1337 said:
OK. booted via twrp, copied file from sd card, but there seems to be no xbin folder in system
Click to expand...
Click to collapse
Mount system

Sachin Thomas said:
Mount system
Click to expand...
Click to collapse
after mounting system, its still showing only one folder in system . lost+found. nothing else.
ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen

salil_1337 said:
after mounting system, its still showing only one folder in system . lost+found. nothing else.
ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen
Click to expand...
Click to collapse
Oh, the xbin folder should have got deleted when you formatted system. I don't think you can't get rid of the HTC screen without successfully flashing an RUU. Our aim is to get rid of bad blocks which prevents the RUU from getting flashed
Are you sure that it ran without errors? Move it into /system and change permission to 755 and re-run it before attempting to flash another RUU

Softbrick, can't unlock bootloader, that's why I cant unbrick it, pls help!

So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!

GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.

e1forall said:
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.
Click to expand...
Click to collapse
Thanks for the reply! I tried the steps but sadly it did not work.
I downloaded cm13, extracted it to my fastboot.exe folder and did enter the commands.
"c:\unlock>fastboot devices
9c50d771 fastboot"
So my device does show up which means drivers are properly installed aren't they?
"c:\unlock>fastboot flash recovery boot.img
target reported max download size of 1073741824 bytes
sending 'recovery' (7254 KB)...
OKAY [ 0.232s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.254s"
There is the error message again, I can't flash the stock recovery becaue the bootloader is not unlocked I think but I don't know what else to do.
then:
"c:\unlock>fastboot format cache
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.068s"
I did that too, I can't tell if it formatted cache or not, I dunnoooo
and then i entered the two commands to unlock and then check the bootloader:
"c:\unlock>fastboot reboot
rebooting...
finished. total time: 0.005s
c:\unlock>fastboot devices
9c50d771 fastboot
c:\unlock>fastboot oem unlock
...
OKAY [ 10.102s]
finished. total time: 10.106s
c:\unlock>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.013s]
finished. total time: 0.014s"
sooooo it sadly did not work

GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps

smarttmd said:
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps
Click to expand...
Click to collapse
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C

GriechischerYoghurt said:
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C
Click to expand...
Click to collapse
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?

smarttmd said:
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?
Click to expand...
Click to collapse
yes it's in the directory from where i start command prompt

Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)

meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too. Here i

GriechischerYoghurt said:
I tried that too. Here i
Click to expand...
Click to collapse
Rough spot to be in then. Hopefully someone has some other ideas for you to try. Good luck bud.

meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.

I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!

GriechischerYoghurt said:
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.
Click to expand...
Click to collapse
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.

ryanmat said:
I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!
Click to expand...
Click to collapse
Thanks for the reply and trying to help! but as I stated in the title my bootloader is LOCKED so i can't write anything to it. The guide of Heisenberg states clearly "Prerequisites: unlocked bootloader." so I knew it would not work but I tried it anyway.. sadly it did not work.. this is what it's giving me:
"C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.804s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.804s
C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>"
funny thing is, it's "only" a softbrick but behaves like a hardbrick. I can't do anything and I don't know what to do at this point.

meekrawb said:
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.
Click to expand...
Click to collapse
I will try the ColorOS hardbrick method on a virtual XP machine and report back.

I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.

GriechischerYoghurt said:
I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.
Click to expand...
Click to collapse
When you do a fastboot oem unlock does it reboot you back into recovery?

I used HighOnAndroid's guide to unlock bootloader, flash a custom recovery, and root.
Tutorial Video
https://www.youtube.com/watch?v=vPv2DYnH3S8&index=9&list=PLB86F041EAFE4F3E5
Step-By-Step and Downloads
http://highonandroid.com/android-smartphones/how-to-root-oneplus-one/

Why don't you flash firmware in unlocked bootloader, if possible ( please refer in the forum, as i think there's a way to flash firmware and then you can unlock bootloader )

Go to an independent repair shop. They have the equipment to flash on the motherboard.

Cannot run "fastboot boot img" successfully.

I've tried everything, Windows and Mac, standalone adb and fastboot as well as full SDK version, different USB ports, and I'm at a loss on what to do.
I got a Hong Kong version U11+ (CID: HTC_622, Asia-HK-CHT)
Whatever I do every time I try to boot via the fastboot boot command in bootloader mode it seems to work at first and then nothing, just a black screen.
The terminal output seems to indicate all went well and yet that's not the case:
fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
OKAY [ 10.112s]
finished. total time: 11.006s
Click to expand...
Click to collapse
Here is the output of fastboot getvar all:
boot-mode:FASTBOOT
unlocked:yes
off-mode-charge:0
charger-screen-enabled:0
battery-soc-ok:yes
battery-voltage:3911
version-baseband:
version-bootloader:
variant:MSM UFS
partition-type:cache:ext4
partition-size:cache: 0xE000000
partition-type:userdata:ext4
partition-size:userdata: 0x1C3C800000
partition-type:system:ext4
partition-size:system: 0x101000000
secure:yes
serialno: *removed*
product:HTC_Phone
max-download-size:536870912
kernel:uefi
Click to expand...
Click to collapse
Any clue on what is happening?

Exactly the same is happening for me when I just try and boot it rather than flash it. I'm on the Chinese variant of the phone with Chinese firmware. I get exactly the same message on adb (successfully booted) but just a black screen on the phone.

Prot02018 said:
Exactly the same is happening for me when I just try and boot it rather than flash it. I'm on the Chinese variant of the phone with Chinese firmware. I get exactly the same message on adb (successfully booted) but just a black screen on the phone.
Click to expand...
Click to collapse
How did you do ? rebooting is not as simple as we think ,

afaik, fastboot boot does not work anymore on recent HTC devices , so you have to flash it in order to boot into twrp

DeeZZ_NuuZZ said:
afaik, fastboot boot does not work anymore on recent HTC devices , so you have to flash it in order to boot into twrp
Click to expand...
Click to collapse
Oh, well that makes sense! Thanks.
Does anybody know if RUU.zips contain the stock recovery too? As well as everything else needed to get the phone back to stock?

Prot02018 said:
Oh, well that makes sense! Thanks.
Does anybody know if RUU.zips contain the stock recovery too? As well as everything else needed to get the phone back to stock?
Click to expand...
Click to collapse
A ruu contains everything
Sent from my HTC 10 using XDA Labs

aurelienlux said:
I've tried everything, Windows and Mac, standalone adb and fastboot as well as full SDK version, different USB ports, and I'm at a loss on what to do.
I got a Hong Kong version U11+ (CID: HTC_622, Asia-HK-CHT)
Whatever I do every time I try to boot via the fastboot boot command in bootloader mode it seems to work at first and then nothing, just a black screen.
The terminal output seems to indicate all went well and yet that's not the case:
Here is the output of fastboot getvar all:
Any clue on what is happening?
Click to expand...
Click to collapse
Hi. I have the same phone but my max download size is 2399200000. Is there any reason why yours is lots higher than mine? I tried flashing a RUU and I keep getting messages saying file size larger than device limit. Is there a way we can change this max download limit? Thanks.

[HELP] Unlock Android bootloader without OEM Unlock (Phone doesn't start)

¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
Install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.

Hmmm ill help you with your answer if u can get help for me with mine

Zaq1xsw222 said:
Hmmm ill help you with your answer if u can get help for me with mine
Click to expand...
Click to collapse
So help me and give me your answer, let me see if i can help you

CheckS86 said:
So help me and give me your answer, let me see if i can help you
Click to expand...
Click to collapse
Ok so you was saying you need a command right to type into linux shell. But hold on did you put a custom rom onto the phone yourself
Also, if your phone randomly stopped working by its self, our issues may be related........

Zaq1xsw222 said:
Ok so you was saying you need a command right to type into linux shell. But hold on did you put a custom rom onto the phone yourself
Also, if your phone randomly stopped working by its self, our issues may be related........
Click to expand...
Click to collapse
No, i dont flash nothing in this phone, it just stopped working by itself.
I have a Windows 10 pc and i only can use some fastboot commands, so, i already tried various commands but my outdated recovery only letme run some of them!

CheckS86 said:
No, i dont flash nothing in this phone, it just stopped working by itself.
I have a Windows 10 pc and i only can use some fastboot commands, so, i already tried various commands but my outdated recovery only letme run some of them!
Click to expand...
Click to collapse
What was the last thing you done on your phone?
The last setting you changed?
Have you tried turning the phone on with the battery out?

Zaq1xsw222 said:
What was the last thing you done on your phone?
The last setting you changed?
Have you tried turning the phone on with the battery out?
Click to expand...
Click to collapse
I was playing or using whatsapp maybe, and yes, i tried that, but never start (because of the volt needed), only the LED is on

CheckS86 said:
I was playing or using whatsapp maybe, and yes, i tried that, but never start (because of the volt needed), only the LED is on
Click to expand...
Click to collapse
Here u go.
Hard Reset HTC Desire 10 Pro, how to - HardReset.info
www.hardreset.info

Ok now its your turn

Zaq1xsw222 said:
Here u go.
Hard Reset HTC Desire 10 Pro, how to - HardReset.info
www.hardreset.info
Click to expand...
Click to collapse
The phone make exatly the same, after set the HTC logo the screen and LED turn down (like an animation when lock your screen), i dont know why, but making this led mi to the begining :/
(tell me your question btw)

CheckS86 said:
The phone make exatly the same, after set the HTC logo the screen and LED turn down (like an animation when lock your screen), i dont know why, but making this led mi to the begining :/
(tell me your question btw)
Click to expand...
Click to collapse
Have you tried to restart your phone in safety mode?

Zaq1xsw222 said:
Have you tried to restart your phone in safety mode?
Click to expand...
Click to collapse
It doesn't work, this just led me to de begining too.
The phone can't start, so maybe re-install his firmware is the best option. I already search the firmware for this phone (to try flash it with SP Flashtool), even here in XDA there is an RUU Collection for this phone, but none of them is compatible with mine. This is the firmware compatible:
2PYAIMG_A56DJ_PRO_DTWL_M60_SENSE80GP_HTC_India_SEA_1.18.400.22_Radio_0.A56DJPV1P32.7900.0216.A56T_release_508642_combined_signed_2_4.zip
but is only available to buy... here for example:
2PYAIMG_A56DJ_PRO_DTWL_M60_SENSE80GP_HTC_India_SEA_1.18.400.22_Radio_0.A56DJPV1P32.7900.0216.A56T_release_508642_combined_signed_2_4.zip | Easy Firmware
easy-firmware.com
IDK why this firmware is not in other pages .

Reinstall stock firmware so you can boot into system. Then follow instructions to unlock with unlock code