Database Info

fastboot bricked my device and it's not fixing it back

hello.
I tried to test a custom kernel today. So I followed the advice in cyanogenmod's wiki:
If you are developing a kernel, you may find it helpful to delete your boot.img and recovery.img to force booting into fastboot:
fastboot erase boot
fastboot erase recovery
You can then manually boot from your custom kernel and a ramdisk:
fastboot boot <kernel> <ramdisk>
Once you have a working kernel and ramdisk, you can automagically combine them within fastboot:
fastboot flash:raw boot <kernel> <ramdisk>
Click to expand...
Click to collapse
The erase steps worked happily! But when I reached the boot step:
Code:
% fastboot boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz
creating boot image...
creating boot image - 5416960 bytes
downloading boot.img...
OKAY [ 1.688s]
booting...
FAILED (remote: ()
finished. total time: 1.689s
And now, no matter what I try, I get:
Code:
Unrecoverable bootloader error <0x00000000>.
Flashing the previous (working) boot.img or recovery-jb-touch.img does not work. After finishing what appears to be a successful flash, the device gets unidentified for some reason. So I can't `fastboot reboot`.
Here is the full output:
Code:
% fastboot devices
015d262e983c120f fastboot
% fastboot flash recovery ../recovery-jb-touch.img
sending recovery (6942 KB)...
OKAY [ 1.961s]
writing recovery...
OKAY [ 3.136s]
finished. total time: 5.098s
% fastboot devices
???????????? fastboot
So every time I flash, I have to manually restart to the bootloader. And hence nothing gets fixed, I'm back to square one.
I understand that unlocking voids the warranty. But I expected the extra functionality to actually work if I follow the correct procedure. I didn't expect things to blow up in my face. The fact that I live overseas and there is probably no Asus tech support around here adds an insult to my injury.
I really hope there is a way to fix this.

y2012 said:
hello.
I tried to test a custom kernel today. So I followed the advice in cyanogenmod's wiki:
The erase steps worked happily! But when I reached the boot step:
Code:
% fastboot boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz
creating boot image...
creating boot image - 5416960 bytes
downloading boot.img...
OKAY [ 1.688s]
booting...
FAILED (remote: ()
finished. total time: 1.689s
And now, no matter what I try, I get:
Code:
Unrecoverable bootloader error <0x00000000>.
Flashing the previous (working) boot.img or recovery-jb-touch.img does not work. After finishing what appears to be a successful flash, the device gets unidentified for some reason. So I can't `fastboot reboot`.
Here is the full output:
Code:
% fastboot devices
015d262e983c120f fastboot
% fastboot flash recovery ../recovery-jb-touch.img
sending recovery (6942 KB)...
OKAY [ 1.961s]
writing recovery...
OKAY [ 3.136s]
finished. total time: 5.098s
% fastboot devices
???????????? fastboot
So every time I flash, I have to manually restart to the bootloader. And hence nothing gets fixed, I'm back to square one.
I understand that unlocking voids the warranty. But I expected the extra functionality to actually work if I follow the correct procedure. I didn't expect things to blow up in my face. The fact that I live overseas and there is probably no Asus tech support around here adds an insult to my injury.
I really hope there is a way to fix this.
Click to expand...
Click to collapse
You need to flash the correct kernel and such for the tf700, don't flash anything available out there, you are asking for bricking! I suggest to flash back to full stock firmware then start over.

buhohitr said:
You need to flash the correct kernel and such for the tf700, don't flash anything available out there, you are asking for bricking!
Click to expand...
Click to collapse
It was a CM10 kernel I compiled myself.
buhohitr said:
I suggest to flash back to full stock firmware then start over.
Click to expand...
Click to collapse
Explaining how this can be done from fastboot would be great. Especially when I can't even make recovery work.

Try flashing NVidia blobs instead of raw images ... AFAIK the TF700 bootloader's fastboot implementation only understands blobs.

You also forget the usb ID. Try this
Code:
fastboot -i 0x0B05 boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz

ostar2 said:
You also forget the usb ID. Try this
Code:
fastboot -i 0x0B05 boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz
Click to expand...
Click to collapse
I tried with and without the ID.
Is it really damaging if the ID is not included?

y2012 said:
I tried with and without the ID.
Is it really damaging if the ID is not included?
Click to expand...
Click to collapse
No. There were just some bootloader versions which never showed a serial number, just question marks, when issuing "fastboot devices", and then you needed to specify the ID to get anything to work.
The fastboot implementation in the TF700 is a bit strange. I also could not get "fastboot boot ..." to work, but I never erased my boot and recovery partitions. Just flashing blobs worked fine.

_that said:
The fastboot implementation in the TF700 is a bit strange. I also could not get "fastboot boot ..." to work, but I never erased my boot and recovery partitions. Just flashing blobs worked fine.
Click to expand...
Click to collapse
Can you elaborate on flashing blobs?
What blobs should I flash and where/how can I obtain them?

For reference:
Code:
% fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d262e983c120f
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.082s

y2012 said:
Can you elaborate on flashing blobs?
What blobs should I flash and where/how can I obtain them?
Click to expand...
Click to collapse
TF700 fastboot likes to flash blobs that start with a "-SIGNED-BY-SIGNBLOB-" header, followed by an "MSM-RADIO-UPDATE" header.
Try flashing the TWRP recovery from here (see "Fastboot method"): http://www.teamw.in/project/twrp2/105
y2012 said:
For reference:
Code:
% fastboot getvar all
...
Click to expand...
Click to collapse
I am getting the same output on mine, the only differences are the serial number (greetings from Captain Obvious) and the size of the userdata partition (I have a 64 GB tablet).

_that said:
TF700 fastboot likes to flash blobs that start with a "-SIGNED-BY-SIGNBLOB-" header, followed by an "MSM-RADIO-UPDATE" header.
Try flashing the TWRP recovery from here (see "Fastboot method"): http://www.teamw.in/project/twrp2/105
Click to expand...
Click to collapse
Flashing TWRP didn't work.
I think I'm giving up on this.

y2012 said:
Flashing TWRP didn't work.
Click to expand...
Click to collapse
Details?

Ive started the same thread erased the recovery it says it writed recovery image but i think the tablet freezes as any command after writing recovery will not work but before that it will an example:
try adb reboot the tablet will reboot
but after writing the recovery image try entering that command and see what happens
guess Im not the only one who has this problem now we need solutions
Edit: I just remembered I had plan to use Ubuntu to write recovery image see if you can flash ubuntu as the files are on SD rather then on tablet
also skythra had a similar problem he/she said that the fastboot unlocker for jellybean you cannot write you can only read and boot
I also want to ask you have a 64 GB as well?

_that said:
Details?
Click to expand...
Click to collapse
Same as the OP. Flashing looked like it succeeded. The device gets unidentified in fastboot after that. Manual restart. And choosing recovery shows the same error.
It looks like the only options left are:
1] fastboot flash -- I don't know where to get an update.zip that works with this.
2] fastboot flashall -- I don't know how this command works as it doesn't take any arguments.

4SHR4F said:
Ive started the same thread erased the recovery it says it writed recovery image but i think the tablet freezes as any command after writing recovery will not work but before that it will an example:
try adb reboot the tablet will reboot
but after writing the recovery image try entering that command and see what happens
Click to expand...
Click to collapse
Assuming you meant fastboot not adb. This is true. The device gets unidentified (see `fastboot devices` output). Whether the freeze is caused by the unidentified device, or both symptoms are caused by something else, I don't know.
guess Im not the only one who has this problem now we need solutions
Click to expand...
Click to collapse
Well, Asus will not help. They provide half-assed unlocking feature, broken fastboot, and void your warranty in the process. Way to go winning developers and advanced users!
I also want to ask you have a 64 GB as well?
Click to expand...
Click to collapse
No. 32GB here.

y2012 said:
Assuming you meant fastboot not adb. This is true. The device gets unidentified (see `fastboot devices` output). Whether the freeze is caused by the unidentified device, or both symptoms are caused by something else, I don't know.
Well, Asus will not help. They provide half-assed unlocking feature, broken fastboot, and void your warranty in the process. Way to go winning developers and advanced users!
No. 32GB here.
Click to expand...
Click to collapse
Let me know what happens someone suggested downgrading to ICS then use debugfs and then use custom rom root and terminal to send the recovery that way either way my computers PCI card decided to stop working so I have to tether it and then download the tools which is a problemsince I formatted my whole computer to get this transformer workin best of luck but like I said please post ur method cause im in the same boat

4SHR4F said:
Let me know what happens someone suggested downgrading to ICS then use debugfs and then use custom rom root and terminal to send the recovery that way either way my computers PCI card decided to stop working so I have to tether it and then download the tools which is a problemsince I formatted my whole computer to get this transformer workin best of luck but like I said please post ur method cause im in the same boat
Click to expand...
Click to collapse
Bump any solutions cant use flash or boot so cant do anything could someone send us bootlocker tool or something i dont know please help

y2012 said:
Same as the OP. Flashing looked like it succeeded. The device gets unidentified in fastboot after that. Manual restart. And choosing recovery shows the same error.
It looks like the only options left are:
1] fastboot flash -- I don't know where to get an update.zip that works with this.
2] fastboot flashall -- I don't know how this command works as it doesn't take any arguments.
Click to expand...
Click to collapse
fastboot -b flashall
-b (specify a custom kernel base address)
in the same boat

HTC One XL Evita - Boot loop - Can't flash/sd corrupt?

Hey all,
Have a htc one xl evita that has been running fine for quite a while on CM11 nightlies.
Can't remember which kernal is on there.
My phone went flat a few days ago and then went into a bootloop.
I didnt think much of it, figuired id just reflash a different rom and it would be fine.
Its a very strange scenario.
I can flash different roms, they either fail or flash ok, but the flash doesn't actually work.
Eg. It might say it flashed ok, but on reboot, nothing is different.
I have tried flashing the latest TWRP, CWM, CWM touch recovery, it says it flashes ok, but it doesnt actually flash.
I have tried to run an RUU exe....
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe
Can't detect the phone.
I have seen you can manually try and flash a ruu by getting the files from the zip in the temp file but i cant extract anything from the zip, says it corrupt,
I have tried to follow a few guides that say to run the fastboot oem rebootRUU command, but that just reboots the phone and tried to load CM.
I also cant mount SD card from recovery.
I also cant actually wipe anything from the sd card. It says it wipes, but doesnt actually do anything.
I am maybe thinking the sd card is corrupt?
I get a few odd errors in recovery when trying to flash. Things like ...
e error in /cache/recovery/log read-only file system
Tried to flash a rom just now - error - E: could not extract 'meta-inf/com/google/android/update-binary.
3 different roms do that.
I seem to be able to ADB push files to the phone, they dont seem to stay there though.
The only thing i have been able to get the phone to do is run a temp recovery by using the Windroid HTC one xl toolkit.
It will reboot into whichever kernal i pick. But no changes i make in there actually do anything
Sorry for the wall of text, just wanted to put it all up there to answer as many questions as i can.
Any help would be great.
Fastboot details below.
------------------------------------------------
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: deleted
(bootloader) imei: deleted
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8312000
(bootloader) cidnum: 22222222
(bootloader) battery-status: low
(bootloader) battery-voltage: 3537mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s

What were you doing with the phone when it started acting up? Was an app installed...did you install a certain mod?
---------- Post added at 10:52 AM ---------- Previous post was at 10:49 AM ----------
I see a problem already. Maybe its cuz your cid is 2222222 and not 11111111. Look under timaaas signature. In his beginners thread it will help you

Absolutely nothing had been changed, Hadn't installed an app for a week or so. The phone just went flat one night.
Wouldn't boot the next morning.
Yeah the cid 22222222 thing, rooted it over a year ago and cant remember why i made it 22222222, i think i had problems with it going to 11111111 but 2222222 worked ok.
I have flashed many roms and kernals in the last 12 months. All with a cid of 22222222. So that shouldnt be a problem
-+------------------------
marknoll said:
What were you doing with the phone when it started acting up? Was an app installed...did you install a certain mod?
---------- Post added at 10:52 AM ---------- Previous post was at 10:49 AM ----------
I see a problem already. Maybe its cuz your cid is 2222222 and not 11111111. Look under timaaas signature. In his beginners thread it will help you
Click to expand...
Click to collapse

I don't think your device is properly rooted.

Over time the flashing affected your device. At times when one thinks the phone is properly rooted, it will run for a while. But after time it may corrupt the phone and or SD cards

Ok, so what do i do to FIX my root?
Also i worried that when i try and run the fastboot oem rebootruu command that it just reboots the phone.
Won't i need that command to fix things?

marknoll said:
I don't think your device is properly rooted.
Click to expand...
Click to collapse
What makes you say that?
marknoll said:
Over time the flashing affected your device. At times when one thinks the phone is properly rooted, it will run for a while. But after time it may corrupt the phone and or SD cards
Click to expand...
Click to collapse
What do you mean by properly rooted? Being rooted only means you have root privileges on the device. Do you mean something else?
neo__04 said:
Ok, so what do i do to FIX my root?
Also i worried that when i try and run the fastboot oem rebootruu command that it just reboots the phone.
Won't i need that command to fix things?
Click to expand...
Click to collapse
My guess is that your sd card has become corrupt at some point. Exactly which version of TWRP are you running? When you say you can't mount the sd card from TWRP do you mean to your pc?
Sent from a crappy Samsung because my Evita died

timmaaa said:
What makes you say that?
What do you mean by properly rooted? Being rooted only means you have root privileges on the device. Do you mean something else?
My guess is that your sd card has become corrupt at some point. Exactly which version of TWRP are you running? When you say you can't mount the sd card from TWRP do you mean to your pc?
Sent from a crappy Samsung because my Evita died
Click to expand...
Click to collapse
I meant properly configured. Why does he have 22222222?

I am running twrp 2.7.0.8
A further little update, i did manage to mount my sd card (in windows im talking about)
I ran the windroid all in one kit to do a temp recovery boot with cwm touch.
I managed to mount the internal storage and format it.
But i dont think it actually did it.
I then tried to flash a rom, and it gave me a symlink error in cwm.
I do think its problems somehow with the sd card or write permissions or something of the kind.

marknoll said:
I meant properly configured. Why does he have 22222222?
Click to expand...
Click to collapse
22222222 is just another form of SuperCID, it's just like having 11111111 as your CID.
Sent from a crappy Samsung because my Evita died
---------- Post added at 08:58 AM ---------- Previous post was at 08:56 AM ----------
neo__04 said:
I am running twrp 2.7.0.8
A further little update, i did manage to mount my sd card (in windows im talking about)
I ran the windroid all in one kit to do a temp recovery boot with cwm touch.
I managed to mount the internal storage and format it.
But i dont think it actually did it.
I then tried to flash a rom, and it gave me a symlink error in cwm.
I do think its problems somehow with the sd card or write permissions or something of the kind.
Click to expand...
Click to collapse
Flash TWRP 2.7.1.0 and use that to format your sd card. What ROM are you flashing?
Sent from a crappy Samsung because my Evita died

The problem is that nothing i flash actually sticks.
I can flash twrp 2.7.1.0, reboot to bootloader, then go into recovery, still 2.7.0.8.
Nothing i do actually sticks.
The only thing that works is a temporary recovery flash from the All in one toolkit, it will boot to any recovery then, but only the once.
i have a few roms on the sd card. I have tried flashing a stock telstra rom, Aokp, CM11, viper 3.2.7. Whatever was on my phone ive tried.
When i adb push files to it, it says it works, but doesnt actually come up on the sd card.
something very odd is happing.
Soooo annoying, nothing seems to work!

Exactly how are you flashing the recovery?
Sent from a crappy Samsung because my Evita died

the normal command
fastboot flash recovery xxxxxx.img

Are you giving the "fastboot erase cache" command after?
Sent from a crappy Samsung because my Evita died

have tried that yes, normally i hadn't needed to do that in the past.
But have tried that in the last few days while trying to fix the problem

Could he(neo) try and download min adb and fastboot so he could successfully run Ru u?

Ok, so im home for a lunch break so i'll try and rerun a recovery flash. Twrp 2.7.1.0
- So i put the phone in fastboot.
------
C:\android>fastboot flash recovery twrp2710.img
sending 'recovery' (8588 KB)...
OKAY [ 1.041s]
writing 'recovery'...
OKAY [ 3.461s]
finished. total time: 4.502s
--------
C:\android>fastboot erase cache
erasing 'cache'...
OKAY [ 0.841s]
finished. total time: 0.841s
---------------------------------
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.074s]
finished. total time: 0.074s
---------------------------------------------
Phone didnt actually reboot, just turned off, i powered it on while holding the vol down.
selected recovery from hboot menu.
Booted to recovery with twrp 2.7.0.8
Flash done nothing.....
Im lost

marknoll said:
Could he(neo) try and download min adb and fastboot so he could successfully run Ru u?
Click to expand...
Click to collapse
He already has fastboot installed.
Sent from a crappy Samsung because my Evita died
---------- Post added at 01:35 PM ---------- Previous post was at 01:32 PM ----------
neo__04 said:
Ok, so im home for a lunch break so i'll try and rerun a recovery flash. Twrp 2.7.1.0
- So i put the phone in fastboot.
------
C:\android>fastboot flash recovery twrp2710.img
sending 'recovery' (8588 KB)...
OKAY [ 1.041s]
writing 'recovery'...
OKAY [ 3.461s]
finished. total time: 4.502s
--------
C:\android>fastboot erase cache
erasing 'cache'...
OKAY [ 0.841s]
finished. total time: 0.841s
---------------------------------
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.074s]
finished. total time: 0.074s
---------------------------------------------
Phone didnt actually reboot, just turned off, i powered it on while holding the vol down.
selected recovery from hboot menu.
Booted to recovery with twrp 2.7.0.8
Flash done nothing.....
Im lost
Click to expand...
Click to collapse
It looks like you have corrupt partitions, which I don't think you're gonna be able to repair yourself. A jtag repair is probably a good option for you at this strange. But, the corruption could have been caused by an emmc that's going bad, so the problem could reappear.
Sent from a crappy Samsung because my Evita died

Any suggestions on someone in Australia/Melbourne to get a jtag repair done?
Happy to pay if its going to fix it

I don't know of any personally, a Google search should uncover them though. If you do find one, let me know, I'm in Melbourne too all I'd be interested to know what turns up.
Sent from a crappy Samsung because my Evita died

RUU M8_VZW 4.4.3 (s-off only)

S-off ONLY!!
As many of you are aware, flashing roms to our phone comes with risk. That risk is dimished by the availability of an RUU for our phone.
I have created as much of an RUU as we can put together at this point. This is for s-off users only. I repeat...s-off only.
This zip is an RUUmode/hboot flashable stock RUUish compilation of the current boot/hboot/system/recovery/radio/firmware images. Just like an RUU... this WILL wipe your phone (internal memory). IF you are able...backup data prior to using this. This works EXACTLY like an RUU for s-off users. Two options exist for using this zip. This will land you on STOCK kitkat 4.4.3 pre-rooted with stock recovery. I have tested this on my kid's wife's M8 (she has no choice... ).
NOTE...HTC started preloading some files to /data on the latest Rom. There's not a clean way to add them to an ruu so please flash the following file in recovery after getting your phone back to stock. If you don't, the only problem would be that gallery is missing the sticker files under edit.
If coming from 4.4.4 firmware you will need to flash 4.4.3. in RUU mode prior to flashing this..
- https://www.androidfilehost.com/?fid=23622183712470028
Option 1
Copy 0P6BIMG.zip to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to bootloader and follow prompts once RUU is detected by phone.
Option 2 (Might not be working!)
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now either do one of two things 1)##reboot or 2)flash a custom recovery. IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
Optional If you wish to flash a custom recovery before leaving RUU mode you can. This is helpful if you have relocked for any reason as you CAN flash a recovery using this method while locked (since s-off). Download the ruuM8TWRP_2_7_1.zip below and place it in your working fastboot/adb directory. Once in place, issue the following command.
fastboot flash zip ruuM8_TWRP_2_7_1.zip
##example output
C:\Users\dottat\Downloads\mini-sdk-1.0.31-windows>fastboot flash zip ruuM8_TWRP_2_7_1.zip
target reported max download size of 1830711296 bytes
sending 'zip' (11756 KB)...
OKAY [ 1.404s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=1
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,7
(bootloader) [RUU]UZ,recovery,13
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,27
(bootloader) [RUU]UZ,recovery,36
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,57
(bootloader) [RUU]UZ,recovery,62
(bootloader) [RUU]UZ,recovery,69
(bootloader) [RUU]UZ,recovery,76
(bootloader) [RUU]UZ,recovery,84
(bootloader) [RUU]UZ,recovery,90
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 3.713s]
finished. total time: 5.117s
Once completed you can issue the command "fastboot reboot-bootloader" to return to hboot so you can enter recovery.
Downloads Do NOT mirror these elsewhere.
RUU link
- https://www.androidfilehost.com/?fid=23622183712470087
md5 f223e75d24266c379849e9e4a606f3d1
RUU Mode TWRP 2.8
- https://www.androidfilehost.com/?fid=23622183712470114
md5 2c654e1eadc0c3f3d1477591fb4e84b7
Stickers Fix
- http://www.androidfilehost.com/?fid=23329332407590188
md5 dda3713d8d0c4b50a1c80814c8bd07c5
HTC backup app (highly recommend this gem)
- http://www.androidfilehost.com/?fid=23329332407589902
md5 b7ec08c021b5fb8b1b86a0ab3535c1dd

mine................

You had me all excited for a minute!!! Great to see your getting ready tho. Thanks for all of your hard work.

Sweet!

Nice!.... Your last ruu saved my a$$!

ughhhh, i almost wet my pants

Sweet

Oh yes, the new 4.4.3 firmware we've all been waiting for....
nope! Just dottat (in my Chuck Testa voice)

JWhetstone02 said:
Oh yes, the new 4.4.3 firmware we've all been waiting for....
nope! Just dottat (in my Chuck Testa voice)
Click to expand...
Click to collapse
You guys crack me up. Enjoying the wait eh?

dottat said:
You guys crack me up. Enjoying the wait eh?
Click to expand...
Click to collapse
Patience is a virtue... Unfortunately, not one of mine.

Well played, almost had me ready to leave work early and head home hahaha

JediMindTrixx said:
Patience is a virtue... Unfortunately, not one of mine.
Click to expand...
Click to collapse
Hah... you don't have to explain... I DID get my moto 360 this weekend.. so i understand completely

dottat said:
Hah... you don't have to explain... I DID get my moto 360 this weekend.. so i understand completely
Click to expand...
Click to collapse
I know its off topic but since we are waiting, what are your thoughts on the moto 360 so far?

JediMindTrixx said:
Patience is a virtue... Unfortunately, not one of mine.
Click to expand...
Click to collapse
Bwuahahaha I hear that @JediMindTrixx I've been patient for far to long. Hope soon it's released. No more 4min wait boot up*yaay*.
Sent from my Insanely powered M8 using Tapatalk

Code:
[QUOTE="dottat, post: 55361775, member: 3472611"][B][SIZE="5"]S-off ONLY!![/SIZE][/B]
As many of you are aware, flashing roms to our phone comes with risk. That risk is dimished by the availability of an RUU for our phone.
I have created as much of an RUU as we can put together at this point. This is for s-off users only. I repeat...s-off only.
This zip is an RUUmode/hboot flashable stock RUUish compilation of the current boot/hboot/system/recovery/radio/firmware images. Just like an RUU... this WILL wipe your phone (internal memory). IF you are able...backup data prior to using this. This works EXACTLY like an RUU for s-off users. Two options exist for using this zip. This will land you on STOCK kitkat 4.4.3 pre-rooted with stock recovery. I have tested this on my [STRIKE]kid's[/STRIKE] wife's M8 (she has no choice... :)).
NOTE...HTC started preloading some files to /data on the latest Rom. There's not a clean way to add them to an ruu so please flash the following file in recovery after getting your phone back to stock. If you don't, the only problem would be that gallery is missing the sticker files under edit.
[B][SIZE="5"]Option 1[/SIZE][/B]
Fastboot RUU mode (preferred). This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
[HIDE][/HIDE]
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now either do one of two things 1)##reboot or 2)flash a custom recovery. IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
[B]Optional[/B] If you wish to flash a custom recovery before leaving RUU mode you can. This is helpful if you have relocked for any reason as you CAN flash a recovery using this method while locked (since s-off). Download the ruuM8TWRP_2_7_1.zip below and place it in your working fastboot/adb directory. Once in place, issue the following command.
fastboot flash zip ruuM8_TWRP_2_7_1.zip
##example output
[HIDE]C:\Users\dottat\Downloads\mini-sdk-1.0.31-windows>fastboot flash zip ruuM8_TWRP_2_7_1.zip
target reported max download size of 1830711296 bytes
sending 'zip' (11756 KB)...
OKAY [ 1.404s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=1
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,7
(bootloader) [RUU]UZ,recovery,13
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,27
(bootloader) [RUU]UZ,recovery,36
(bootloader) [RUU]UZ,recovery,41
(bootloader) [RUU]UZ,recovery,57
(bootloader) [RUU]UZ,recovery,62
(bootloader) [RUU]UZ,recovery,69
(bootloader) [RUU]UZ,recovery,76
(bootloader) [RUU]UZ,recovery,84
(bootloader) [RUU]UZ,recovery,90
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 3.713s]
finished. total time: 5.117s[/HIDE]
Once completed you can issue the command "fastboot reboot-bootloader" to return to hboot so you can enter recovery.
[B][SIZE="5"]Option 2[/SIZE][/B]
Copy 0P6BIMG.zip to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to bootloader and follow prompts once RUU is detected by phone.
[B]Downloads[/B]
[B]RUU link [/B]
[url]pending[/url]
md5
[B]RUU Mode TWRP 2.7.1[/B]
[url]https://www.androidfilehost.com/?fid=23622183712469358[/url]
md5 db77a00008eed750b4900f4c1ebb59a8
[B]Stickers Fix[/B]
[url]http://www.androidfilehost.com/?fid=23329332407590188[/url]
md5 dda3713d8d0c4b50a1c80814c8bd07c5
[B]HTC backup app (highly recommend this gem)[/B]
[url]http://www.androidfilehost.com/?fid=23329332407589902[/url]
md5 b7ec08c021b5fb8b1b86a0ab3535c1dd[/QUOTE]
So, what improvements are made with this, what will it change, how dangerous is it, and will it affect me on AOSP roms?

bracketslash said:
Code:
So, what improvements are made with this, what will it change, how dangerous is it, and will it affect me on AOSP roms?
Click to expand...
Click to collapse
They added more bacon, the version number will change, dwarves may eat your cat but other than that you're safe, and finally no it shouldn't affect aosp unless your cat maintains the device in which case being eaten by a dwarf will hamper releases.

bracketslash said:
Code:
So, what improvements are made with this, what will it change, how dangerous is it, and will it affect me on AOSP roms?
Click to expand...
Click to collapse
This is the latest article I could find that explains most of the changes. Hope this helps.
http://www.android.gs/verizon-htc-one-m8-android-4-4-3-update-available-now-for-download/

mademan420 said:
I know its off topic but since we are waiting, what are your thoughts on the moto 360 so far?
Click to expand...
Click to collapse
My daily driver phone is a one max.. so far.. my moto 360 and my one max seem to be linked on battery life. At the end of the day, I have almost half of the battery on each device left. I have my moto 360 screen not set to that mode that keeps the screen on all the time. I like it. It does exactly what i was hoping it would and it's not killing the battery.

Nandroid Backup Beforehand
This may be stupid but would I be able to flash the RUU and then restore a nandroid i made right before to get all my data and apps etc back on the phone with the new firmware??

Seanzle said:
This may be stupid but would I be able to flash the RUU and then restore a nandroid i made right before to get all my data and apps etc back on the phone with the new firmware??
Click to expand...
Click to collapse
I do it that way when i'm on a stock rom that i've made changes to that i'm too lazy to undo... If it's very close to stock, usually restoring just /data works fine. Alternatively, you can use the HTC backup app in the OP to have your texts/email accounts/desktop/apps(no app data)/etc backed up.

Bootloader & download mode not working!

Hi everyone,
I hope someone can. Help. Unfortunately I flashed a bad firmware and therefore have the problem, that download mode doesn't work (power button + vol down --> gets to the dark screen with htc logo but then goes completely off) AND bootloader also doesn't work (power + vol up --> gets to white screen with green HTC logo but also goes completely off)! Any chance to get my A9 back to life? Any ideas? Thanks!
Original cid/mid
cid: HTC__034
mid: 2PQ910000
Now on super cid, s-off

SpeziesTR said:
Hi everyone,
I hope someone can. Help. Unfortunately I flashed a bad firmware and therefore have the problem, that download mode doesn't work (power button + vol down --> gets to the dark screen with htc logo but then goes completely off) AND bootloader also doesn't work (power + vol up --> gets to white screen with green HTC logo but also goes completely off)! Any chance to get my A9 back to life? Any ideas? Thanks!
Original cid/mid
cid: HTC__034
mid: 2PQ910000
Now on super cid, s-off
Click to expand...
Click to collapse
You flash which version of firmware? A9 original version of what? now you can into bootloader mode?

Hi thanks for answering. I flashed 1.57.617.20 firmware, but saw too late thats not for my model...
I cannot enter bootloader. When I press Power + Vol up, white screen and green HTC logo shows for 1-2 seconds and then the phone turns off completely...

SpeziesTR said:
Hi thanks for answering. I flashed 1.57.617.20 firmware, but saw too late thats not for my model...
I cannot enter bootloader. When I press Power + Vol up, white screen and green HTC logo shows for 1-2 seconds and then the phone turns off completely...
Click to expand...
Click to collapse
When you at the "dark screen with htc logo" . enter cmd command "fastboot reboot-bootloader" can you into bootloader mode?

Hi, the dark screen is also only there for 1-2 seconds, then device turns off again...

SpeziesTR said:
Hi, the dark screen is also only there for 1-2 seconds, then device turns off again...
Click to expand...
Click to collapse
You need to flash 1.56.401.70 of aboot_signed.img & hosd_signed.img.but this must be in bootloader mode .
A9_1.56.401.70.rar
HTC SYNC adb tools
Code:
fastboot flash aboot aboot_signed.img
fastboot flash hosd hosd_signed.img
fastboot reboot
Now unable into bootloader mode is the biggest problem.

@ nenebear: Thanks for your help so far!
Has anyone else a clue how to start into bootloader?

i have almost the same problem. my screen is black all the way but all the buttons work and i can hear it boot but the screen does not turn on

I managed to get into bootloader and from there into recovery. I had to press vol up + vol down + power so the device would boot into bootloader. Very strange as this is not the normal combination. I restored my previous image, it will boot but is somehow slow and sluggish.
Nevertheless I did flash
fastboot flash aboot aboot_signed.img
fastboot flash hosd hosd_signed.img
fastboot reboot
but I'm still not able to go to download mode. Furthermore beeing in bootloader reading basic information is not possible. For example:
...\HTC One A9\mini-sdk>fastboot devices
HT******** fastboot
...\HTC One A9\mini-sdk>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x29b000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc6000000
(bootloader) serialno:HT********
all:
finished. total time: 0.080s
...\HTC One A9\mini-sdk>fastboot oem readcid
...
FAILED (remote: unknown command)
finished. total time: 0.004s
...\HTC One A9\mini-sdk>fastboot oem readmid
...
FAILED (remote: unknown command)
finished. total time: 0.011s
Anyone a clue how to fix my A9 completely?

Hi,
i just tried to flash system.img (which I decrypted from 1.56.401.70 ROM.zip) but unfortunately got the following error.
Code:
fastboot flash system system.img
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
htc_fastboot finished. total time: 134.464s
Flashing Boot.img, aboot.img etc. is working....
Has someone a clue?

I fixed the problem. I flashed firmware and rom from 1.27.401.5. After that download mode was working again and I could flash 1.56.401.70 without a problem.
Now I'm on Icanas ROM and my A9 is working better than ever...

I did the same flashed a bad firmware. I can access bootloader but not download mode. I have restored a backup I had in twrp so I am running a rooted stock rom but I still can't update my phone thru RUU or Download mode. I have tried flashing the 2p9qimg ( firmware img/ zip ) thru fastboot thru bootloader but no go. All I want to do is flash the correct file so I can access download mode
S-Off
At&T converted to Unlocked
CID & MID changed

nenebear said:
You need to flash 1.56.401.70 of aboot_signed.img & hosd_signed.img.but this must be in bootloader mode .
A9_1.56.401.70.rar
HTC SYNC adb tools
Code:
fastboot flash aboot aboot_signed.img
fastboot flash hosd hosd_signed.img
fastboot reboot
Click to expand...
Click to collapse
which img files do I need to flash if I'm on 1.12.617.6 S- off US Unlocked converted from S-On At&t. I can't get into download mode, it turns off after the HTC logo with black background. Bootloader, recovery and my phone work though.
Nevermind figured it out! =)

Good day guys,
This is my first post in xda, and i'm a little bit nervous. and please bear with my english and i am a noob to some terms too. anyway, my unit is htc one a9. it was sent to me by my brother here in philippines. it is a sprint htc and i think it is a cdma with a sim slot and memory on the side. after reading some of your topics in some forums, i manage to unlock the the network. i can make outgoing and incoming calls and sms. but GPRS is disconnected. i then found another topic by jianC on how to Convert Sprint/Boost HTC One A9 to Dev Unlock. for it says that it can solve No mobile data (but have voice/sms) on sprint firmware after sim unlock. i followed the instructions but unfortunately it brick my phone. i flashed the 2PQ9IMG_HIA_AERO_UL_M60_SENSE7GP_ATT_NA_Gen_Unlock_1.12.617.6_signed.zip, to my phone. My old firmware was 2PQ9IMG_HIA_AERO[email protected]51002_15.00_F_CNV_CNV_HIAE_SPCS_1.15_003_release_453002_signed.zip. Now my problem is that i can get in to bootloader mode by pressing power+vol up+vol down together which is awkward.......but i cannot get in to download mode and recovery mode. the phone can still display the htc logo but 15 seconds later it shutsdown. i tried your advice to type fastboot erase system but it says FAILED<remote:device is locked. cannot erase. But my phone is Bootloader Unlocked and S-Off from sunshine. CID/MID (SPCS_001/2PQ93000) before. I change it to (11111111/2PQ912000) after. Then i tried to flash. I really don't know where to start until i found this forum. I hope somebody could help me in this problem i have.
Thanks and sincerely yours,
kramned

[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