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
Related
Hello everyone!
I have run into problems with my hero since I flashed Drizzy's hero rom.
My sd card reader is no longer functioning and hence I am locked into drizzy's rom without any possibility of any kind of sd card use.
The sd card can't be read from cyanogens recovery even.
Is there any way to put a new rom on the phone without access to the sd card?
(I have root if that helps)
Thanks in advance,
Hampan
Can I use the fastboot update command without an sd-card available to the phone?
you can push (=upload) with adb (command is: adb push [local] [remote]) a file to the sdcard (just connect your phone via usb to computer)
example:
update.zip is here: C:\update.zip
then do:
adb push C:\update.zip /sdcard/update.zip
then it will upload the file (about 5-10 minutes).. ready to flash
Thank you for your reply , no I can't make adb connect to the phone.
Only fastboot works, and even if adb was working I couldn't possibly make it push the update to the sdcard since the phone can't see the sd card at all.
and you are even not able to access the sdcard via cyanogen recovery AND adb shell??
No exactly, the sd card can't be reached from ANYTHING , adb shell won't connect although fastboot does, and i can use fastboot commands.
I tried using the "fastboot update update.zip" with modacos rom but got the message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I'm thinking maybe one can flash the device without putting anything on sd via "fastboot update" .. can anyone confirm?
simply restore your nandroid backup that im sure you did.
./fastboot flash system system.img
./fastboot flash userdata data.img
./fastboot flash boot boot.img
./fastboot reboot
Thanks for your reply, yes I did make a nandroid backup and copied it to my pc
However, as it stands now I can only reach the phone from the computer with fastboot, usb is not recognized in windows and sd card is not functioning (even in cyanogen fastboot).
So, if I use my old stock nandroid backup and somehow the sd and usb is still not functioning, would there be a possibility that I would be stuck with the old slow rom forever?
Thanks for any help!
keatonreckard said:
simply restore your nandroid backup that im sure you did.
./fastboot flash system system.img
./fastboot flash userdata data.img
./fastboot flash boot boot.img
./fastboot reboot
Click to expand...
Click to collapse
Yup, now I tried .. doesn't work
C:\android-sdk-windows-1.5_r3\tools>fastboot flash boot boot.img
sending 'boot' (2560 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
I'm sh*t out of luck aren't I?
maybe the remaining option is to send it to htc... :-( but that will cost money cuz you lost the garanty
Yup, that, sadly -Is my conclusion as well.
Anyway, the phone works as usual , just no SD and no updates.
Since I have no warranty I might just wait until a new android version is released for Hero.
Thank you all for replying and trying to help me.
stupid question, but did you check to see if it is the micro sd that went bad, not the reader? you don't need to embarrass yourself by responding, I just hope it helps if that is what it was.
I have the same problems and follow these threads:
http://forum.xda-developers.com/showthread.php?t=556335
http://forum.xda-developers.com/showthread.php?t=559106
Can't you try to 'update' (restore) it with the htc RUU .exe
?
not totally sure since i dont have a hero myself, but i think this might work...
Hello,
i've just bricked my Desire i think
I think it got wrong in recovery mode. I chose usb mount from the recovery menu with a fat and ext3 partition (aps2sd).
Now my Desire hangs on the white screen with the green HTC letters. When i enter the recovery menu from holding volume down and the power button i can choose for the update zip to install, but then i get the error can't mount /dev/block/mmcblk0p1
Please help, this is so annoying.
Try the command in fastboot to reenable USB.
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.
Follow the USB un-bricking guide here:
http://forum.xda-developers.com/showthread.php?t=691639
Dont worry mate, i know it can be scary,
Its happened to us all, and if it hasnt, it will
Good luck with unbricking, every unbrick is a victory for XDA over HTC
JD
thnx for the replies.
I've just enabled the sdcard function so lets see how far i will come
Well it's working again This was really not cool
peewster said:
thnx for the replies.
I've just enabled the sdcard function so lets see how far i will come
Well it's working again This was really not cool
Click to expand...
Click to collapse
Great stuff, as you can see, it's not so much of a worry when there are fixes available
I haven't been bricked yet... but as JD said, there's still that chance... then i will be literally bricking it!
well the only thing i can't get to work is the actual fix.
my phone boots normally, but when i try to execute:
/data/flash_image misc /data/mtd0.img i get the following error:
mtd: rad all-zero block at 0x00000000; skipping
error reading mtd0.img
peewster said:
well the only thing i can't get to work is the actual fix.
my phone boots normally, but when i try to execute:
/data/flash_image misc /data/mtd0.img i get the following error:
mtd: rad all-zero block at 0x00000000; skipping
error reading mtd0.img
Click to expand...
Click to collapse
Are you sure you USB bricked and it's not just a bad flash that will be solved by a wipe/clear and reflash? That is, if you are able to get into recovery. As I understand it USB brickeds are still able to boot, while hanging on "quietly brilliant" is a typical bad flash/sd-card issue (had it a couple times meself). I might very, very, very well be wrong though
Mac
No this was a real usb brick. I could nog flash anything anymore, and mu usb wasn't working anymore.
I replaced the mtd0.img with a new one, and this time the script executed correctly.
I'm rebooting it now.
Just rebooted, and everything is working normal again
Great! Nothing is like the feeling of relief when things work again!
Mac
M4cr0s said:
Great! Nothing is like the feeling of relief when things work again!
Mac
Click to expand...
Click to collapse
You can say that again
No success after 1st step
MasDroid said:
Try the command in fastboot to reenable USB.
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.
Follow the USB un-bricking guide here:
http://forum.xda-developers.com/showthread.php?t=691639
Click to expand...
Click to collapse
I got this.
D:\Softwares\htc\android-sdk-windows\tools>fastboot oem enableqxdm 0
... OKAY [ 0.096s]
finished. total time: 0.096s
But, still now I'm getting
"Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
I'm trying to follow second step at the thread 691639. I have posted more info there. Please help.
Long story here. My desire has decided to become sd bricked
Hboot version is 0.93
Software is 2.29.405.5
Phone is not routed and is s-on.
I can use adb and fastboot but I cant do anything that requires the sd card. Can someone please help me in getting the sd card working again please.
John
did you already triy the "fastboot oem enableqxdm 0" command in fastboot mode?
Yes it comes back with
fastboot oem enableqxdm 0
...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
You need to have s off to use that command. Follow the root and s off guides in the development forum then try again.
Sent from my Motorola Startac running Atari 2600 software!
I've ran unrevoked and it says I am rooted and titanium backup runs.
I tried alpharev to get s off and it doesn't appear to work, it cant find my phone.
John
no you don't need s-off.
i think you are in the wrong directory. The fastboot.exe is in the folder tools,
so you have to change the directory in cmd and then "fastboot oem enableqxdm 0".
(also fastboot mode on your desire)
You tried reformatting the SD using "SD Formatter"?
Also, which ROM were you running? Some roms dont seem to boot (stuck on HTC logo screen) if theres probs with the SD card format - especially if your sd-ext is ext 4.
Can you boot into recovery? If so and you arent bothered about losing phone data, format your SD (using SDFormatter), stick something like LeeDroid 2.3d on and flash it (with full wipe).
Maybe this'll help:
http://forum.xda-developers.com/archive/index.php/t-1070863.html
Hello,
I posted this in the General section by mistake.
My HTC desire won't read the SD card. It is not a problem with the card since I tried it on Windows & other phones and it works + Tried cards that work in other phones and won't work on mine.
What do I have access to:
- The phone is S-OFF
- I have Clockworkmod Recovery
- I can't see the card from the recovery either ("Can't mount /sdcard")
- my phone is not rooted
- I have stock 2.2 android (2.29.405.5)
- I have the drivers installed on my PC and I can access the phone via abd or fastboot
I have tried:
"fastboot oem enableqxdm 0" from fastboot, it didn't fix it.
Unbrick from 4eXT Recovery:
Asked a coworker for his working SD Card
Used the "fastboot oem enableqxdm 0"
Installed "4eXT Recovery Touch v1.0.0.5 RC9"
Entered Recovery with msg "Error mounting your card .... "
Tools > Usb unbrick
"Your CID: HTC__032
Patching misc image..
Your misc partition size: 640kb
Writing mtd0..
Done.. please reboot!"
After reboot the same issue "Error mounting your card .... " in Recovery, loaded rom: No SD card
Returned the card to my coworker, card is still functional in his phone.
I am opened to suggestions. Worst case scenario: Hardware malfunction
Ty,
Danny
One additional question:
Assuming that I can't get my SDcard to work. Is there a way to install custom rom's?
I have s-OFF, Clockworkmod and adb + fastboot access. Can I flash a new rom from fastboot?
I tried like this with no success:
fastboot erase cache
erasing 'cache'...
OKAY [ 0.284s]
finished. total time: 0.284s
fastboot oem rebootRUU
...
OKAY [ 0.092s]
finished. total time: 0.092s
fastboot flash zip Official_Stock_Sense-Gingerbread_v1.2__GB-2.3.3_A2SD.zip
sending 'zip' (146730 KB)...
OKAY [ 21.102s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 29.371s
Danny
Im not an expert but it seems to be a hardware issue.
Also, if i would be in your situation i would try to change the hboot. Not sure if it has anything to do with it though. Like i said, not an expert.. but id try it anyway hehe..
Wait for someone with more knowledge on this matter to reply or take it to the service.
Please don't change hboot, it has nothing to do with your problem...
You only change hboot before you flash a rom to match the rom's /system size in order to maximize /data (internal memory)
To flash a rom you don't do it thru fastboot, you need to do it thru recovery like normal (full wipe then install zip from sdcard)
However it's strange why your phone can't detect your sdcard. suspect might be hardware after your current logical testing.
Last thing I would try is to delete all partitions and reformat to FAT32 partition using gparted, see if phone detects it after that
What is the capacity of your SDcard? (32Gb maximum for Desire if i'm right)
zinconnu said:
What is the capacity of your SDcard? (32Gb maximum for Desire if i'm right)
Click to expand...
Click to collapse
Just 2 GB and I also tried a 8 GB
If your sd-card is working in computer, so that is something wrong with the phone. Can you access your sd-card from recovery? If not, the system won't too.
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?