Related
hi.
I bricked my desire with Hboot 0.93 when I flashed cusom rom Cyanogenom. I flashed via rom manager. Everything goes well, but after reboot not working SD card, USB and WCDMA. I thought of unroot PB99IMG to help, but to no avail. Unroot goes well, but problem persists. whereas USB does not work, we can not root. I tried to root http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/ but not working:
google translator helped me
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
Since you seem to have successfully unrooted, start from step 1.
-edit- Oops, didn't read properly. Looks like unrooting screwed you a little... what exactly isn't working when you try the root method linked in step one?
log from terminal, when I using Paul Obrien root method r6 :
About to start flash...
< waiting for device >
sending 'zip' (138708 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
sending 'zip' (138708 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 43 custom id check fail)
If you mean the r6 rooting method that's for HBOOT 0.65/0.80 ONLY - you definitely brick your phone using that!
Are you sure you're unrooted? Did you try
fastboot oem enableqxdm 0
in Fastboot and then flashing the update.zip from Modaco USB unbrick step 3?
How to do?
2. Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
Edit:
Power off the phone, hold 'back key' then power... go into your adb\tools and enter from a cmd window:
fastboot oem enableqxdm 0
You need to read up a lot more if you don't know basic fastboot/adb commands...
Depends on your OS... on Windows it's the same as ADB: Open a command prompt, cd to directory of fastboot.exe (in the SDK) and then enter the command.
EddyOS said:
You need to read up a lot more if you don't know basic fastboot/adb commands...
Click to expand...
Click to collapse
Yep, nobody should be rooting without knowledge of ADB and Fastboot... seems like Unrevoked makes it too easy.
True, I learnt the hard way (kinda) but now know more after reading up. Even Paul back in the day with the first rooting methods made it easy!!
I am using ubuntu and I have instaled Android SDK. I do not know how to run fastboot. How?
http://android-dls.com/wiki/index.php?title=Fastboot
http://forum.xda-developers.com/showthread.php?t=619153
Everything you need to know is in there (took me 2 seconds on Google to find them)
tma24 said:
I am using ubuntu and I have instaled Android SDK. I do not know how to run fastboot. How?
Click to expand...
Click to collapse
Find fastboot and run it from the terminal, I suppose... same as ADB. Or, if you've added the SDK tools directory to your path variable, just enter the command in the terminal, no need to CD to fastboot.
I added it to my path variable as soon as it was installed - SO much easier!
usb bricking isnt a problem. it can be realtivly easy fixed.
the only "real" brick can be done with destroying hboot - which today is nearly impossible with the rock solid alpharev solution.
i had a similar problem - 24 hours without my phone - i learned a lot in that time - and finally was much further than i was before.
so look at the bright side of it - in the end, you gathered knowledge.
the fastboot command will restore sdcard - then you can go to recovery and flash a new rom or restore a backup.
mad-murdock said:
the fastboot command will restore sdcard - then you can go to recovery and flash a new rom or restore a backup.
Click to expand...
Click to collapse
Can he really, if he already unrooted in a fit of panic?
I do not know it
my desire is in fastboot mode and connected to PC
path android-sdk is:
/home/username/android-sdk
path adb is:
/home/username/android-sdk/platform-tools
fastboot??? not find
I have the exact "fastboot" from r6.desire-root to platform-tools
and
open teminal:
cd /home/username/android-sdk/platform-tools enter
sudo fastboot oem enableqxdm 0
not working
cd /home/username/android-sdk/platform-tools enter
sudo fastboot
not working
where I make mistakes
You can't take the fastboot program from one folder into another...seriously, go read up on it and research properly. Go here for a start:
http://developer.android.com/sdk/index.html
My card is already fully working. problem is now in version HBOOT (0.93). anyone know how I could get hboot 0.80 from the card or through fastboot? All guides requires root or cable connection.
tma24 said:
How to do?
2. Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
Edit:
Power off the phone, hold 'back key' then power... go into your adb\tools and enter from a cmd window:
fastboot oem enableqxdm 0
Click to expand...
Click to collapse
Thanks! My SD card is back.
It all started when i tried to flash Insertcoin's Sense 2.1+ GB ROM. That involve messing about with partitions. I have re-formatted several times and erased all partitions, but still no help. the phone doesn't boot up, When SD card is in the phone, only the most basic android splash screen comes up and stays there. If my SD card is not on the phone. it is able to boot to the ROM, but nothing can be accessed, there is no keyboard, i can't answer calls, because the screen is just blank (apart from background image). also in Recovery mode i can't "choose zip from sdcard" because of the "E: can't mount /dev/block/mmcblk0
(or /dev/block/mmcblk0)" error.
edit: I tried un-rooting from http://forum.xda-developers.com/showthread.php?t=696189 thread. and in the beginning of the un-rooting it gave me the ERROR [140] BOOTLOADER VERSION ERROR. Now when SDcard is in, the boot process stops at HTC's own splash screen and when it's out of the phone, i can still access the obviously misinstalled ROM. At this point i'm very confused about what to do next. Can anyone help me?
Can you access and use fastboot??? If you can -
fastboot oem enableqxdm 0
and then
fastboot oem eraseconfig
That should fix your sd card mounting again....
i'm not really familiar with that command. In fastboot menu i can see Bootloader, Reboot, Reboot Bootloader and Power Down menu items
edit: okay, i understand you mean using that with cmd. Well, adb devices command shows no devices attached,
Amphor said:
i'm not really familiar with that command. In fastboot menu i can see Bootloader, Reboot, Reboot Bootloader and Power Down menu items
edit: okay, i understand you mean using that with cmd. Well, adb devices command shows no devices attached,
Click to expand...
Click to collapse
Not adb -
Boot to bootloader (vol down + power )
plug in usb - bootloader will change to say usb is plugged in
Boot fastboot - scroll down to and press power - bootloader will again change to show fastboot mode
open CMD then type -
fastboot devices
- if nothing happens make sure you have changed your directory to where fastboot.exe is stored
e.g. (is how my hard drive is set up but yours will prob be different
cd C:/android/tools
When fastboot devices command shows your phone -
fastboot oem enableqxdm 0
fastboot oem eraseconfig
That will re-eastblish your usb again
What set up do you have?? S-off?? Sd card partitioned etc... Hboot (all info from bootloader)
Oh and do you actually want to unroot or are you just trying to fix it?
i am just trying to fix it, any means necessary, whether it's unrooting or not
s-on, in the recovery menu there is format sdcard and format sd-ext. so, i would think that there is a partition, but not sure.
oh, and
C:\Users\Amphor>fastboot oem enableqxdm0
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.019s]
finished. total time: 0.020s
C:\Users\Amphor>
normal behaviour? Still can't choose zip from sdcard
http://forum.xda-developers.com/showthread.php?t=691639
Should get you going unless someone else has an easier way?
Not really sure what it did, but definitely not did it fix my problem. The solution was for some kind of USB connectivity issue which i have luckily. Wasn't it?
Amphor said:
Not really sure what it did, but definitely not did it fix my problem. The solution was for some kind of USB connectivity issue which i have luckily. Wasn't it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/archive/index.php/t-1077985.html Read that one .... I believe it is pretty much the problem you have?
C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem enableqxdm 0
...
OKAY [ 0.024s]
finished. total time: 0.024s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem eraseconfig
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
was my error, as was his. Strrangely, this time the first command didn't give me an error. But yeah, this is the problem pretty much yes. And there were no other solutions given, apart from the two lines in fastboot. Also, the last post stated that i have to be S-OFF to use fastboot (properly), but i am S-ON. Also, i couldn't find a way to format the card to fat, not fat32
Amphor said:
C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem enableqxdm 0
...
OKAY [ 0.024s]
finished. total time: 0.024s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem eraseconfig
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
was my error, as was his. Strrangely, this time the first command didn't give me an error. But yeah, this is the problem pretty much yes. And there were no other solutions given, apart from the two lines in fastboot. Also, the last post stated that i have to be S-OFF to use fastboot (properly), but i am S-ON. Also, i couldn't find a way to format the card to fat, not fat32
Click to expand...
Click to collapse
Is your sd card partitioned correctly??? How is is set up exactly??? Make sure that your partitions are EXT 3 /4 NOT LOGICAL
You still can't access SD card in recovery?
would you define "correctly"?
Finally got a chance to test with another card and i can access sd card from recovery. And i think the dog is buried under the issue that the testcard is FAT, but mine is FAT32. though my 8GB card couldn't be FAT. So what was it?
And again, what is correctly. If i look with Gparted, then my card has 7.40 gb and 512 mb partitions (dev/sda and sdb) and i can't delete that 512 mb one
Amphor said:
would you define "correctly"?
Finally got a chance to test with another card and i can access sd card from recovery. And i think the dog is buried under the issue that the testcard is FAT, but mine is FAT32. though my 8GB card couldn't be FAT. So what was it?
And again, what is correctly. If i look with Gparted, then my card has 7.40 gb and 512 mb partitions (dev/sda and sdb) and i can't delete that 512 mb one
Click to expand...
Click to collapse
Ah.... Insert coin states requirements - A2SD+ STOCK HBOOT - stock hboot - the one with 250 mB for /system
- 1 gB ext2/3/4 partition
So your correct sd card setup is FAT 32 7GB and 1GB EXT 3/4
If I were you I would backup ALL files from Sd card to computer...
Format your sd card with gparted..
New partition - Fat 32 - 7gb
New partition - Ext 3 or 4 - 1 gb
Apply
Transfer all files back to your sd card
Put in phone and see if it's fixed?
Make sure you are using the Stock HBOOT version of insert coin... I'm surprised nothing has got you up and running so far ?!
My problem is the mounting, not the "not booting" issue, still
but yes, thats why i started mazking partitions in the first place
Amphor said:
My problem is the mounting, not the "not booting" issue, still
but yes, thats why i started mazking partitions in the first place
Click to expand...
Click to collapse
I know I didn't mention not booting....
either way, it didnt solve my problem
Well if none of the 3 suggested fixes work... I'm out though
Good luck
Hello everyone, I made a mistake (I am a big noob) and I don't know how to fix it.
I wanted to have fresh phone (real factory reset) to back-up and start over, so in recovery mode (interim one from paul) I wiped data, cache partition and I also formated cache,data, sdcard and system.
Now, I am stuck on htc quietly brilliant screen, I have access to hboot, recovery etc. I have been looking for a solution for 2 days without succes, I am sad.
Can someone help please ? thanks guys.
You wiped the system so there is no android on there!
Eirher download a new Rom and flash or relock bootloader and use ruu
Sent from my HTC One X using xda premium
Thanks sir, I'll try.
sotirios said:
Thanks sir, what can I do ? Which part I did wrong ? thanks again
Click to expand...
Click to collapse
The part you did wrong: It's true that you wipe (dalvik) cache and data before flashing a custom rom. That will perform a factory reset. Wiping system means deleting android itself, as stated before. That's what you did wrong.
Now, we can't know why you wanted to start all over again, but assuming you already flashed a custom recovery, you wanted to install a custom rom. Just go ahaed and do so, your problem will be fixed.
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
sotirios said:
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
Click to expand...
Click to collapse
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push path/to/custom/rom /sdcard
or for linux/mac:
sudo ./adb push path/to/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
dobbi10k said:
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard
or for linux/mac:
sudo ./adb push pfad/zu/einer/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
Click to expand...
Click to collapse
That wont work as ADB does not work on any of the custom recoveries at the moment. Im stuck in the same situtation at the mo and as phone is branded cant get the RUU to reflash so just playing the waiting game until either ADB/USB mount available in recovery or S-Off available.
See my thread in development thread
http://forum.xda-developers.com/showthread.php?t=1599748
Sent from my HTC One X using XDA
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
"Eirher download a new Rom and flash"
I can't flash, my ssd is wiped too and i can't mount usb with this custom recovery
"That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard"
It doesn't work, it doesn't find my device, even with the adb devices command
sotirios said:
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
Click to expand...
Click to collapse
Go to development thread then shipped ruu ans download specific to ur phone. Follow and Job done
Sent from my HTC One X using XDA
Same problem here! I unfortunatly erase everything from my one x and i can't restore anything!! How can i solve it?? My device is unlocked but stay in s-on mode! Why? From fastboot i can't flash anything! Help!!
Hello folks, problem solved by following leejames instructions :
flash stock recovery
relock bootloader
use ruu
I'm so happy. Thanks.
Mee too!! Thanks a lot!! I'm very very very very very very very very very very very very very very happy!!
1 flash stock recovery
2 relock bootloader
3 use ruu
It works fine!!
I do exactly the same thing , but half way through the RUU process it gives me an error saying i need the correct RUU. anyone can help ?
All you have to do is grab an RUU, run it. now on your pc search for %temp%in there locate ROM.zip. Extract the boot.img and system.img. and push them thru fastboot
Code:
fastboot flash boot boot_signed.img
Code:
fastboot flash system system.img
Code:
adb reboot
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
mahdibassam said:
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
Click to expand...
Click to collapse
Is your bootloader unlocked?
When I do it with an unlocked bootloader the error changes to this:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
Nobody can help me?!! ((
Hi,
I have a serious problem. My phone for some reason was working fine, but all the sudden is now stuck in HBOOT.
i have tried recovery but the phone would just shut itself down. i couldn't not use adb even though before the phone went into this state, i turned the USB debugging mode on
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
please help , many thanks
Bump, I'm having the same problem on my tmobile m8
mmmgosu said:
Hi,
I have a serious problem. My phone for some reason was working fine, but all the sudden is now stuck in HBOOT.
i have tried recovery but the phone would just shut itself down. i couldn't not use adb even though before the phone went into this state, i turned the USB debugging mode on
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
please help , many thanks
Click to expand...
Click to collapse
raphi809 said:
Bump, I'm having the same problem on my tmobile m8
Click to expand...
Click to collapse
What versions of the M8 do you have?
EddyOS said:
What versions of the M8 do you have?
Click to expand...
Click to collapse
I have a t-mobile m8, I actually started a thread over there http://forum.xda-developers.com/tmobile-htc-one-m8/help/m8-bricked-soloution-t2818678 but so far no answers either
raphi809 said:
I have a t-mobile m8, I actually started a thread over there http://forum.xda-developers.com/tmobile-htc-one-m8/help/m8-bricked-soloution-t2818678 but so far no answers either
Click to expand...
Click to collapse
In which case stick to your thread as opposed to jumping on to others, makes it easier to follow
EddyOS said:
In which case stick to your thread as opposed to jumping on to others, makes it easier to follow
Click to expand...
Click to collapse
Yes, if you have already started a thread asking for help, don't jump around.
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
mmmgosu said:
this is the error message i got for trying to do fastboot flash recovery
target reported max download size of 1830727680 bytes
sending 'recovery' (14826 KB)...
OKAY [ 1.475s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.544s
Click to expand...
Click to collapse
What response do you get for:
fastboot devices
If it returns the device ID, than try:
fastboot erase cache
Then try to flash recovery again.
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
when i tried fastboot devices it returns an ID
but when i tried
fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
i have at&t
Maybe try to flash one of the modded hboots?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hawkysoft said:
Maybe try to flash one of the modded hboots?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how do i do that?
fastboot oem rebootRUU
fastboot flash zip name_of.zip
fastboot reboot-bootloader
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hard to help you if you do not even bother to answer all the questions posed to you. As I asked earlier:
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
redpoint73 said:
Hard to help you if you do not even bother to answer all the questions posed to you. As I asked earlier:
Did you by chance try to factory reset in bootloader (corrupts the internal memory on modded devices)?
Click to expand...
Click to collapse
I tried factory reset but it doesn't seem to be doing anything, just a white screen with android picture.
what do you mean by " corrupts the internal memory on modded devices?"
i tried
fastboot oem rebootRUU
but it says ...
(bootloader) [DEBUG] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(560): error 2
(bootloader) Start Verify: 3
(bootloader) [DEBUG] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [DEBUG] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.018s]
finished. total time: 0.018s
question, can i flash TWRP with 0p6bimg.zip?
If yes, can anyone provide the file?
Thanks
mmmgosu said:
I tried factory reset but it doesn't seem to be doing anything, just a white screen with android picture.
what do you mean by " corrupts the internal memory on modded devices?"
Click to expand...
Click to collapse
It means you should never ever do that (factory reset in bootloader) if bootloader unlocked, rooted, etc.. Only within the OS Settings or in recovery.
What this means, is that on a stock device, factory reset in bootloader works normally; but on a modded (rooted, etc.) device this corrupts the internal memory and renders it unable to be read or written to. This is probably why can't wipe cacher, install custom recovery, reboot RUU, etc (all are giving you errors reading data; and I think this is the reason why).
Connect the phone to a Windows PC (sorry if that is not what you use, its all I know) and use Device Manager to format the phone's internal memory. Once its formatted try again to wipe cache and flash custom recovery again.
This is great info to tuck away for future reference. How should the memory be formatted? FAT32 or exFAT?
Sent from my Nexus 10
bruce7373 said:
How should the memory be formatted? FAT32 or exFAT?
Click to expand...
Click to collapse
FAT32.
redpoint73 said:
It means you should never ever do that (factory reset in bootloader) if bootloader unlocked, rooted, etc.. Only within the OS Settings or in recovery.
What this means, is that on a stock device, factory reset in bootloader works normally; but on a modded (rooted, etc.) device this corrupts the internal memory and renders it unable to be read or written to. This is probably why can't wipe cacher, install custom recovery, reboot RUU, etc (all are giving you errors reading data; and I think this is the reason why).
Connect the phone to a Windows PC (sorry if that is not what you use, its all I know) and use Device Manager to format the phone's internal memory. Once its formatted try again to wipe cache and flash custom recovery again.
Click to expand...
Click to collapse
How exactly does one format the phone's internal memory via Device Manager?
adriankeith said:
How exactly does one format the phone's internal memory via Device Manager?
Click to expand...
Click to collapse
Couldn't actually tell you "exactly" myself as I haven't personally had to do it. But I know its been given as advice many times, and reported to work (at least for some instances of corrupted internal memory or can't mount memory).
In brief, open Device Manager, browse to the device/internal memory, and try to find the option to format FAT32.
Ok, I'm in the same pickle as person above. Let me just post the state the phone was in before everything happened. Unlocked bootloader, s-on, Android revolution HD installed (4.4.3). Friend tried to get back to stock and now the phone is stuck in hboot. Things done to phone: bootloader relocked, tried to change tampered flag without success, flashed stock recovery and boot image. Fastboot devices returns Id, storage is not recognized, adb commands do not work. I think he also tried to do factory reset while in hboot. Just stumbled upon this format memory thing, will do it once I get home. What are the steps after, can I just flash the correct ROM.zip or some moded hboot? If you can just point me in right direction I would very much appreciate it, thanks. Also if you need any additional info just ask for it
Similar problem here also,
I could really use some help guys! The new GPE 6.0 images are out on XDA. http://forum.xda-developers.com/htc...uu-m8-google-play-edition-5-1-lmy470-t3226765
I did a full wipe then I put on the rom using the zip file first through TWRP and it did install but the radio drivers failed.
So I then downloaded the system img file ruu and renamed it to 0P6BIMG.zip and now it is just stuck in a loop and will not boot into the Operating system. It will just freeze at the White HTC logo.
I press the power button and the volume up button to reset the device then push the power button and volume down button to get into the bootloader the bootloader instantly selects Hboot and starts loading up the 0P6BIMG.zip. The phone then procedes to give me the highlighted HBoot option and the message "Press <POWER> to reboot." Which then reboots right into the White HTC loading screen.
The phone is unlocked and has s-on. I have tried using ADB commands but cannot get an ID with ADB devices command.
Can someone help a brotha out?
Posted in the general thread, but no replies.
I seem to have softbricked my phone by rooting then applying the OTA update. I've tried re-rooting, wiping cache, factory resetting, etc., and nothing seems to work. Following the steps in http://forum.xda-developers.com/zenf...d-zf2-t3127835 I can get to step 7, but when I submit any of the commands I get this:
Code:
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14822 KB)...
OKAY [ 0.666s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.839s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.545s]
writing 'recovery'...
FAILED (remote: Permission denied
)
finished. total time: 0.716s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11868 KB)...
OKAY [ 0.522s]
writing 'boot'...
FAILED (remote: Permission denied
)
finished. total time: 0.694s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Permission denied)
finished. total time: 125.564s
It wasn't clear if it was a windows permission error or an android permission error, so I tried an admin command prompt but that didn't change anything.
Any suggestions? Thanks in advance
Bump in hopes of a solution
And another bump, any help would be greatly appreciated
I'm wondering if it has to do with having a bootloader installed being over a certain version. I had 2 Asus Zenfone 2s and I get the same error messages. I can't remember what my first ZF2 had for firmware to start, but I was a dummy and updated it all the way to 2.20.40.90 stock. Everytime I tried to write via fastboot, Permission Denied. My new ZF2 on 2.20.40.59 also has the same problem. I feel like Asus patched the ability to fastboot these files or something. Running CMD as Administrator doesn't help the situation.
bumping because I'm having the same issue, coming back to stock after having CM12.1
As easy as it sounds, the solution was just flashing the newest software from the ASUS website, using adb sideload UL-Z00A-WW-2.20.40.97-user.zip
I can't imagine why I wouldn't have done that sooner, but it fixed it. Whether that worked due to something else I did, i have no idea, but my phone is now working
I had that before but fortunately I was able to fix it.
Get a microsd, but a firmware from Asus website, make sure that it is the correct one if you have WW then download WW, download it from Asus website or it will not work.
Then put the micro sd on the phone., rename the file MOFD_UPDATE don't put zip cause it will be doubled.
Boot to bootloader then boot to recovery. Automatically the phone will restore itself.
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
I was also unable to mount the SD card, might have something to do with MOFD not being mapped.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
KylarBStern said:
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
ebanreb37 said:
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
I already tried it, I wrote in my post that I tried it. And it didn't work.
KylarBStern said:
I already tried it, I wrote in my post that I tried it. And it didn't work.
Click to expand...
Click to collapse
SD card MUST be FAT32 or 32gb or less. If you are using anything else it won't detect the sd card.
Cheers...
Ok it's been a while since I've tried anything with this phone and just now I did what you said, copied the firmware file which I downloaded from ASUS to a 2GB sd card formatted in fat32, rebooted to recovery phone applied the update sucessfully and restarted but I am still stuck in bootloop ? I tried every method so I asume the phone is ****ed and I should send it back for RMA ?