Database Develop

[Q] in desperate need of help: bricked my brand new HTC ONE

Hi!
Today I bought a brand new HTC One (not locked to any carrier) and I wanted to install ViperROM. I did probably something stupid, because I bricked the phone and I have no idea how to fix it (please note that this is my first Android, I was an iPhone user so far).
After following a guide how to root my device tried to install the latest viperROM and put it in the "download"-Folder on the device (I guess this was my mistake). When I tried to install the ROM in TWRP (version v2.6.0.1) the installation got stock with "Flashing Kernel". After waiting for 10 minutes or something I rebooted using "adb.exe" and tried it again (this time putting the ROM on an USB-stick and using an OTG-cable). This time the flashing ends up with:
Code:
Done!
Unable to mount '/cache'
Unable to mount '/system'
When I try to restart TWRP warns me that I have no OS installed. Normal booting gets stuck on the white HTC-screen.
I'm totally desperate. :crying:
Is there anything I can do to save my new device?
Greetings
MJFox

Your just soft bricked..there's so many threads on this I want to throw up

I know that I'm probably a pain in the ass, but I was not able to find a solution for my problem yet using the search
maybe you can point me to the right direction?
greetings
MJFox

MJFox78 said:
Hi!
Today I bought a brand new HTC One (not locked to any carrier) and I wanted to install ViperROM. I did probably something stupid, because I bricked the phone and I have no idea how to fix it (please note that this is my first Android, I was an iPhone user so far).
After following a guide how to root my device tried to install the latest viperROM and put it in the "download"-Folder on the device (I guess this was my mistake). When I tried to install the ROM in TWRP (version v2.6.0.1) the installation got stock with "Flashing Kernel". After waiting for 10 minutes or something I rebooted using "adb.exe" and tried it again (this time putting the ROM on an USB-stick and using an OTG-cable). This time the flashing ends up with:
Code:
Done!
Unable to mount '/cache'
Unable to mount '/system'
When I try to restart TWRP warns me that I have no OS installed. Normal booting gets stuck on the white HTC-screen.
I'm totally desperate. :crying:
Is there anything I can do to save my new device?
Greetings
MJFox
Click to expand...
Click to collapse
So you come charging in here using a new phone and OS (so basicaly fullly clueless) and start modifying stuff and now you`re surprised somethng went wrong.
Well, try installing a rom with adb sideload in TWRP.

gee2012 said:
So you come charging in here using a new phone and OS (so basicaly fullly clueless) and start modifying stuff and now you`re surprised somethng went wrong.
Well, try installing a rom with adb sideload in TWRP.
Click to expand...
Click to collapse
since I'm usually not an idiot with those things and I followed the guide I'm quite surprised that something went wrong
anyway, thank you for the sideload-hint, but it didn't help, the ROM got transfered to /data/media/sideload.zip and the flashing process starts after that but ends after several minutes with the same "Unable to mount"-error as before :crying:
in the mount-menu, which entries need to be checked before starting the flashing?
any further help would be greatly appreciated
greetings
MJFox

Can you go into bootloader if yes below might help
Have you tried downloading a ruu extract the bootloader flash the bootloader , put into fastbot and run the RUU

MJFox78 said:
since I'm usually not an idiot with those things and I followed the guide I'm quite surprised that something went wrong
anyway, thank you for the sideload-hint, but it didn't help, the ROM got transfered to /data/media/sideload.zip and the flashing process starts after that but ends after several minutes with the same "Unable to mount"-error as before :crying:
in the mount-menu, which entries need to be checked before starting the flashing?
any further help would be greatly appreciated
greetings
MJFox
Click to expand...
Click to collapse
Which guide were you following out of curiosity? And is your device detected in sideload mode while in twrp?
Sent from my HTC One using xda app-developers app

dami_cool said:
Can you go into bootloader if yes below might help
Click to expand...
Click to collapse
yes, I can go into the bootloader
dami_cool said:
Have you tried downloading a ruu extract the bootloader flash the bootloader , put into fastbot and run the RUU
Click to expand...
Click to collapse
I have absolutely no clue what that means, I will try to search the forums to find something that explains your suggestion
greetings
MJFox

dami_cool said:
Can you go into bootloader if yes below might help
Have you tried downloading a ruu extract the bootloader flash the bootloader , put into fastbot and run the RUU
Click to expand...
Click to collapse
He shouldn't have to ruu...that's last case scenario
---------- Post added at 09:18 PM ---------- Previous post was at 09:17 PM ----------
MJFox78 said:
I have absolutely no clue what that means, I will try to search the forums to find something that explains your suggestion
greetings
MJFox
Click to expand...
Click to collapse
Don't ruu

Ajxx16 said:
Which guide were you following out of curiosity? And is your device detected in sideload mode while in twrp?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
as a newbie I'm not allowed to post links, but it's an article with the title "Rooting The HTC One The Right Way" at cultofandroid.com
and yes, the device is deteced in sideload-mode, the rom gets transfered and the flashing starts, but it seems that no matter what, "system" can not be mounted after the flashing
greetings
MJFox

ok, I was able to restore the device with the stock firmware, woohooo!
I'm still not sure why flashing of viperROM went wrong the first time
any ideas? I would like to try it again, but since I have no idea what I did wrong the first time I don't want to mess up the system again
greetings
MJFox

THAT'S THE EASY WAY ONCE THE system boots you can start the whole process again but more carefully. Or you can flash the Rom.zip from the ruu
Sent from my HTC One using xda app-developers app

I tried to flash viperROM again
again I end up with:
Code:
Done!
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/system'
what's going on there?
greetings
MJFox

one abpote
Try again, make sure you have the correct device type ROM, there are several M7 devices around... may depend on your provider... I got mine yesterday, "m7ul" and succesfully flashed cyanogenmod 10.1, and even it´s still a nightly, I´m quite impressed...
Good Luck

lotte67890 said:
Try again, make sure you have the correct device type ROM, there are several M7 devices around... may depend on your provider... I got mine yesterday, "m7ul" and succesfully flashed cyanogenmod 10.1, and even it´s still a nightly, I´m quite impressed...
Good Luck
Click to expand...
Click to collapse
they don't seem to be various versions of the viperROM, all I could try is to install an older version
do you think this might help?
I found just one person that had the same problem in the viperROM-thread, but I couldn't find any solution for that
greetings
MJFox

MJFox78 said:
they don't seem to be various versions of the viperROM, all I could try is to install an older version
do you think this might help?
I found just one person that had the same problem in the viperROM-thread, but I couldn't find any solution for that
greetings
MJFox
Click to expand...
Click to collapse
And you have a Sprint HTC One? Cause that´s the only one the Viper ROM is build till now...

lotte67890 said:
And you have a Sprint HTC One? Cause that´s the only one the Viper ROM is build till now...
Click to expand...
Click to collapse
no, I don't have a Sprint HTC One, I have an open EU HTC One!
damn it, I didn't notice that it's just for sprint, stupid me!
that probably explains all my problems
thanks for the clarification!
is there any other ROM that is compareable to the viperROM? I would like to keep HTC Sense, but want to customize several things
greetings
MJFox

:good: Glad to help... I have no idea if there are other ROM´s with SENSE around... I use cyanogenmod 10.1, AOSP, very fast and nice to customize...
Regards

4.3 update messed up my phone

I have rooted HTC one google edition. I received a new official updated that I installed through twrp, after installation it told me that root access was lost and i could restore it by pressing restore root access option. Since then i cant get past the Google screen. My phone basically gets to Google screen then restarts, gets to Google screen and restarts. I tried factory reset, did not help. What should i do?

If you have a Google Edition rooted phone, it shouldnt have installed the OTA with a custom recovery installed. You'll likely have to use the RUU in the original dev thread. you'll want to backup your sdcard via adb cause the RUU will wipe everything.

Donjuanal said:
If you have a Google Edition rooted phone, it shouldnt have installed the OTA with a custom recovery installed. You'll likely have to use the RUU in the original dev thread. you'll want to backup your sdcard via adb cause the RUU will wipe everything.
Click to expand...
Click to collapse
I found this http://forum.xda-developers.com/showthread.php?p=39588860, but there is so many freaking links. Which one should i download for HTC one google edition?

sageyo said:
I found this http://forum.xda-developers.com/showthread.php?p=39588860, but there is so many freaking links. Which one should i download for HTC one google edition?
Click to expand...
Click to collapse
Just use this, its either pre-rooted or unrooted, follow the instructions but being on a GE One you should already be all set to flash it.
http://forum.xda-developers.com/showthread.php?t=2358781

Donjuanal said:
Just use this, its either pre-rooted or unrooted, follow the instructions but being on a GE One you should already be all set to flash it.
http://forum.xda-developers.com/showthread.php?t=2358781
Click to expand...
Click to collapse
I just realized i cant even access my phone through my computer...What the hell is going on. So annoyed right now.

sageyo said:
I just realized i cant even access my phone through my computer...What the hell is going on. So annoyed right now.
Click to expand...
Click to collapse
You can't install an OTA through a custom recovery my friend. RUU is your best option right now.

dgtiii said:
You can't install an OTA through a custom recovery my friend. RUU is your best option right now.
Click to expand...
Click to collapse
How am i supposed to use RUU if my computer wont recognize my phone in fastboot?

The RUU won't help anyway. It's not signed therefore will only install on s-off phone.

gunnyman said:
The RUU won't help anyway. It's not signed therefore will only install on s-off phone.
Click to expand...
Click to collapse
So what am i supposed to do now, phone stuck on google screen when booted. When i plug it in the computer i hear the sound but dont see the phone in my computer....stupid 4.3 update ****ed up my phone that worked perfectly fine.

sageyo said:
I just realized i cant even access my phone through my computer...What the hell is going on. So annoyed right now.
Click to expand...
Click to collapse
sucks this happened
but is a prime example of the golden rule
READ READ AND READ AGAIN

CheesyNutz said:
sucks this happened
but is a prime example of the golden rule
READ READ AND READ AGAIN
Click to expand...
Click to collapse
Is there anything i can do right now though?

sageyo said:
Is there anything i can do right now though?
Click to expand...
Click to collapse
sadly i don't think so but im not 100% on this

sageyo said:
So what am i supposed to do now, phone stuck on google screen when booted. When i plug it in the computer i hear the sound but dont see the phone in my computer....stupid 4.3 update ****ed up my phone that worked perfectly fine.
Click to expand...
Click to collapse
what does device manager say?
if it says something like QHUSB_Download mode, you're screwed, get it swapped out
if you can get to the bootloader, you can probably install a recovery again and install a stock 4.2.2 or 4.3 rom and get back up and running.

gunnyman said:
what does device manager say?
if it says something like QHUSB_Download mode, you're screwed, get it swapped out
if you can get to the bootloader, you can probably install a recovery again and install a stock 4.2.2 or 4.3 rom and get back up and running.
Click to expand...
Click to collapse
I can get to bootloader and i can also get to twrp. But the thing is i cant download anything to my phone because i cant access it through my computer, i hear the sound when i plug it in but i dont see the device in "My Computer"

Learned the hard way.
Your phone is not recognized, because you haven't updated your ADB and Fastboot files on your computer. Once, you do that.. You will need to download hboot 1.44 that gunnyman has in the 4.3 thread via RUU. After that is done find yourself, the RUU from whatever provider your phone is running under.. Ex: Dev or Tmo or ATT etc etc.. That should fix you up. I did this to my device once messing around with it.. But my problem also was with a locked boot loader that had 4 exclamation triangles on each corner.. No boot screen for start up even came up.. Just back to the boot loader of doom.
Sent from my HTC One using Tapatalk 2

sageyo said:
I can get to bootloader and i can also get to twrp. But the thing is i cant download anything to my phone because i cant access it through my computer, i hear the sound when i plug it in but i dont see the device in "My Computer"
Click to expand...
Click to collapse
do a factory reset in twrp. then reboot system. and DO NOT FIX ROOT when you reboot

sageyo said:
I can get to bootloader and i can also get to twrp. But the thing is i cant download anything to my phone because i cant access it through my computer, i hear the sound when i plug it in but i dont see the device in "My Computer"
Click to expand...
Click to collapse
then all is not lost. you're having either a driver issue or trying to use a usb 3 port or something like that.
boot to recovery
type adb devices
if it gives a number you can sideload a ROM.
download this rom http://forum.xda-developers.com/showthread.php?t=2390346
it's stock rooted 4.3
sideload it in twrp
start the sideload mode in twrp
type adb sideload then the name of the rom. the rom will push to the phone and then install.
---------- Post added at 09:56 PM ---------- Previous post was at 09:55 PM ----------
luckylui said:
Learned the hard way.
Your phone is not recognized, because you haven't updated your ADB and Fastboot files on your computer. Once, you do that.. You will need to download hboot 1.44 that gunnyman has in the 4.3 thread via RUU. After that is done find yourself, the RUU from whatever provider your phone is running under.. Ex: Dev or Tmo or ATT etc etc.. That should fix you up. I did this to my device once messing around with it.. But my problem also was with a locked boot loader that had 4 exclamation triangles on each corner.. No boot screen for start up even came up.. Just back to the boot loader of doom.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
The guy has a STOCK Google EDITION phone no S-off or anything please don't confuse things

gunnyman said:
then all is not lost. you're having either a driver issue or trying to use a usb 3 port or something like that.
boot to recovery
type adb devices
if it gives a number you can sideload a ROM.
download this rom http://forum.xda-developers.com/showthread.php?t=2390346
it's stock rooted 4.3
sideload it in twrp
start the sideload mode in twrp
type adb sideload then the name of the rom. the rom will push to the phone and then install.
Click to expand...
Click to collapse
i was just gonna link him to that thread. i think a factory reset *might* get it to boot tho. worth a try.

gunnyman said:
then all is not lost. you're having either a driver issue or trying to use a usb 3 port or something like that.
boot to recovery
type adb devices
if it gives a number you can sideload a ROM.
download this rom http://forum.xda-developers.com/showthread.php?t=2390346
it's stock rooted 4.3
sideload it in twrp
start the sideload mode in twrp
type adb sideload then the name of the rom. the rom will push to the phone and then install.
---------- Post added at 09:56 PM ---------- Previous post was at 09:55 PM ----------
The guy has a STOCK Google EDITION phone no S-off or anything please don't confuse things
Click to expand...
Click to collapse
He obviously has some sort of thing going. It clearly states in his OP, FYI. That he "was" rooted "before" the update. Umm & if he can get into boot loader & TWRP Recovery... He still has a chance.
Sent from my HTC One using Tapatalk 2

He also said that he had a GE phone. Totally rootable

[Q] M7 Set_metadata_recursive

Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I try to flash any custom rom (the one I want is viperone 5.8.0) the entire process goes smoothly until the last step of the installation where i get the error "set_metadata_recursive:some changes failed" I have searched around a lot but am unable to find anything
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Thanks in advance for any response!!!!!!
*EDIT*
FIXED problem turned out to be the wrong TWRP for the phone, was using TWRP 2.7.0.0 and 2.7.0.4 the correct version for the verizon phone is here http://crackflasher.com/openrecovery-twrp-2-7-0-1-m7wlv-img-htc-one-verizon-openrecovery/ rom flashes working now!!!!!

PblicEnemy said:
Whenever I try to flash any custom rom (the one I want is viperone 5.8.0) the entire process goes smoothly until the last step of the installation where i get the error "set_metadata_recursive:some changes failed" I have searched around a lot but am unable to find anything
Click to expand...
Click to collapse
First, I would try formatting (not wiping) your /system partition right before the install. If that fails, try following the advice in this thread, which sounds like a dead ringer for your problem:
http://forum.xda-developers.com/showthread.php?t=2532300
Note: Please post whether formatting /system is successful, so others can see the fact in their search results.

fenstre said:
First, I would try formatting (not wiping) your /system partition right before the install. If that fails, try following the advice in this thread, which sounds like a dead ringer for your problem:
http://forum.xda-developers.com/showthread.php?t=2532300
Note: Please post whether formatting /system is successful, so others can see the fact in their search results.
Click to expand...
Click to collapse
Hello, and thanks for the response, do you know of any guides to formatting my /system partition, and will this mean risking the backup i have saved through TWRP? Also I saw that thread that you posted earlier while researching but I don't understand if it is for my phone or compatible with the rom I'm trying to flash.

PblicEnemy said:
Hello, and thanks for the response, do you know of any guides to formatting my /system partition, and will this mean risking the backup i have saved through TWRP? Also I saw that thread that you posted earlier while researching but I don't understand if it is for my phone or compatible with the rom I'm trying to flash.
Click to expand...
Click to collapse
I believe it's an option under the advanced section of "wipe" in TWRP. And this won't risk your backups, because they're stored on another partition. Don't wipe or format anything except /system. And the file recommended in that article isn't likely to cause harm--I believe it's just a helper for how to perform the commands that are needed to install a ROM (for example, delete the files "system/*"). It's more likely to not work than to harm your phone, and there's no way it could install a ROM correctly, then prevent that ROM from running.

fenstre said:
I believe it's an option under the advanced section of "wipe" in TWRP. And this won't risk your backups, because they're stored on another partition. Don't wipe or format anything except /system. And the file recommended in that article isn't likely to cause harm--I believe it's just a helper for how to perform the commands that are needed to install a ROM (for example, delete the files "system/*"). It's more likely to not work than to harm your phone, and there's no way it could install a ROM correctly, then prevent that ROM from running.
Click to expand...
Click to collapse
Okay I believe I am doing something wrong because I downloaded the .zip file for that binary update that was mentioned in that thread. I extracted the file and also extracted the Rom file, I put the new binary into the extracted rom and removed the old one, then i re-zipped the new rom file, however the phone will no longer install, it doesn't even make it to the install screen. Is this because it needs to be recompiled after I change the binary update? If so how do I go about compiling?

PblicEnemy said:
Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I try to flash any custom rom (the one I want is viperone 5.8.0) the entire process goes smoothly until the last step of the installation where i get the error "set_metadata_recursive:some changes failed" I have searched around a lot but am unable to find anything
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Thanks in advance for any response!!!!!!
Click to expand...
Click to collapse
PblicEnemy said:
Okay I believe I am doing something wrong because I downloaded the .zip file for that binary update that was mentioned in that thread. I extracted the file and also extracted the Rom file, I put the new binary into the extracted rom and removed the old one, then i re-zipped the new rom file, however the phone will no longer install, it doesn't even make it to the install screen. Is this because it needs to be recompiled after I change the binary update? If so how do I go about compiling?
Click to expand...
Click to collapse
BRICK ALERT: A word of CAUTION!! are you using m7_u/ul recoveries, from the version numbers sound like m7_u/ul versions... you have m7_wlv so you need to flash a recovery compatible with that phone!

nkk71 said:
BRICK ALERT: A word of CAUTION!! are you using m7_u/ul recoveries, from the version numbers sound like m7_u/ul versions... you have m7_wlv so you need to flash a recovery compatible with that phone!
Click to expand...
Click to collapse
Someone sent me M7vzw-twrp_2.7.0.4b-santod_recovery, and that is the one I am using at the moment, is that wrong?

nkk71 said:
BRICK ALERT: A word of CAUTION!! are you using m7_u/ul recoveries, from the version numbers sound like m7_u/ul versions... you have m7_wlv so you need to flash a recovery compatible with that phone!
Click to expand...
Click to collapse
Sorry for double post, but you pointed out the solution and the phone is working correctly!

PblicEnemy said:
Sorry for double post, but you pointed out the solution and the phone is working correctly!
Click to expand...
Click to collapse
well hope all is well now, and also make sure to flash ROMs which are compatible!
most users (including myself are on m7_u/ul) and this could be easily overlooked...
Good luck and enjoy

[SOLVED] Epic frustration!!! Problems with ROM installation. Everything else seems OK

Tearing my hair out a little with this one.
Out of the box my phone was a UK GSM HTC One, which I gather is the 'm7' when I'm in this company
I've unlocked the handset with the HTC Developer unlock instructions
I've installed ClockworkMod recovery 6.0.4.8 (as per the note on CyanogenMod site, re new partition structure)
I've rooted with SuperSU.zip
I've not got S-OFF (I'm unclear as to the value of going that far; although I have done with previous phones)
I can get to the bootloader fine; I can switch to fastboot; I can issue fastboot commands; I can get to recovery and do all the recovery stuff; I can issue adb sideloads
What I DON'T seem to be able to do, is install any ROM other than cm-11-20140504-SNAPSHOT-M6-m7.zip . Any other ROM I try (later CM snapshots; Android Revolution HD; deodexed Stock ROM (from Android Rev site)), all give me installation errors....
I get the errors if I;
- Try a CM update from within CM in the Settings/Updates menus
- Reboot to recovery and do a zip install from recovery (zip previously downloaded to phone)
- ADB sideload from recovery
Can ANYONE think of anything I'm not doing; or that I'm doing incorrectly, that might be causing this?
It's driving me nuts!

OpusLefteye said:
Tearing my hair out a little with this one.
Out of the box my phone was a UK GSM HTC One, which I gather is the 'm7' when I'm in this company
I've unlocked the handset with the HTC Developer unlock instructions
I've installed ClockworkMod recovery 6.0.4.8 (as per the note on CyanogenMod site, re new partition structure)
I've rooted with SuperSU.zip
I've not got S-OFF (I'm unclear as to the value of going that far; although I have done with previous phones)
I can get to the bootloader fine; I can switch to fastboot; I can issue fastboot commands; I can get to recovery and do all the recovery stuff; I can issue adb sideloads
What I DON'T seem to be able to do, is install any ROM other than cm-11-20140504-SNAPSHOT-M6-m7.zip . Any other ROM I try (later CM snapshots; Android Revolution HD; deodexed Stock ROM (from Android Rev site)), all give me installation errors....
I get the errors if I;
- Try a CM update from within CM in the Settings/Updates menus
- Reboot to recovery and do a zip install from recovery (zip previously downloaded to phone)
- ADB sideload from recovery
Can ANYONE think of anything I'm not doing; or that I'm doing incorrectly, that might be causing this?
It's driving me nuts!
Click to expand...
Click to collapse
Flash TWRP recovery, version 2.6.3.3, not the latest via fastboot and enjoy
Can't think of a good sig

donkeykong1 said:
Flash TWRP recovery, version 2.6.3.3, not the latest via fastboot and enjoy
Can't think of a good sig
Click to expand...
Click to collapse
For my own satisfaction; why not the latest TWRP?
Thanks though. That sounds like a pretty decisive answer!
Also. For future reference, was the way I laid out my question clear and should I include any other details?

OpusLefteye said:
For my own satisfaction; why not the latest TWRP?
Thanks though. That sounds like a pretty decisive answer!
Also. For future reference, was the way I laid out my question clear and should I include any other details?
Click to expand...
Click to collapse
Latest TWRP has some problems with flashing kitkat ROMs.Version 2.6.3.3 is proven to work with every ROM out there. The best thing to do if you have a problem with your phone is to explain your issue as short as possible and post fastboot getvar all. Your post was fine, but for future reference, and let's hope you won't need it, fastboot getvar all is a great help
Can't think of a good sig

donkeykong1 said:
Latest TWRP has some problems with flashing kitkat ROMs.Version 2.6.3.3 is proven to work with every ROM out there. The best thing to do if you have a problem with your phone is to explain your issue as short as possible and post fastboot getvar all. Your post was fine, but for future reference, and let's hope you won't need it, fastboot getvar all is a great help
Can't think of a good sig
Click to expand...
Click to collapse
UPDATE - Latest CM11 snapshot in and running nicely Thanks donkeykong1

OpusLefteye said:
UPDATE - Latest CM11 snapshot in and running nicely Thanks donkeykong1
Click to expand...
Click to collapse
You're welcome [emoji106]
Can't think of a good sig

HTC Desire 510 64 bit unable to boot after OTA update

Hello
After trying to do an OTA update which failed my phone won't boot normally. If I just turn it on it boots into stock recovery and if I reboot it from there it just boots back into recovery.
I have tried to do a factory reset but it won't work, it seems like the system partition has been messed up.
I keep reading that I just need to "run the RUU" but I have no idea where I can find a RUU for my phone, it's a EU 64Bit version with no carrier. The htcdev site just lists kernel sources for my device.
Any idea how I can fix this and get back to a stock system?

henning_ said:
Hello
After trying to do an OTA update which failed my phone won't boot normally. If I just turn it on it boots into stock recovery and if I reboot it from there it just boots back into recovery.
I have tried to do a factory reset but it won't work, it seems like the system partition has been messed up.
I keep reading that I just need to "run the RUU" but I have no idea where I can find a RUU for my phone, it's a EU 64Bit version with no carrier. The htcdev site just lists kernel sources for my device.
Any idea how I can fix this and get back to a stock system?
Click to expand...
Click to collapse
Download this...
http://dl4.htc.com/RomCode/Source_and_Binaries/a11ul-3.10.28-g930be6d.zip

Thanks for the reply but the link just takes me to the general download page, could you tell me what filter you used to find the correct download?

henning_ said:
Thanks for the reply but the link just takes me to the general download page, could you tell me what filter you used to find the correct download?
Click to expand...
Click to collapse
Just enter the desire 510 skip the carrier and version just EU in the region and download the first one.

MrMike2182 said:
Just enter the desire 510 skip the carrier and version just EU in the region and download the first one.
Click to expand...
Click to collapse
Ok, but those are all just kernel sources, that's the problem, I can't use any of those to restore my device.

henning_ said:
Ok, but those are all just kernel sources, that's the problem, I can't use any of those to restore my device.
Click to expand...
Click to collapse
Well the only way I think you're gonna be able to fix it now is to follow the thread that shows you how to root the phone and install a recovery called philz touch recovery for 64 bit and then you'll be able to install the back up recovery that other users have posted.

MrMike2182 said:
Well the only way I think you're gonna be able to fix it now is to follow the thread that shows you how to root the phone and install a recovery called philz touch recovery for 64 bit and then you'll be able to install the back up recovery that other users have posted.
Click to expand...
Click to collapse
Thanks, I just did this, but I installed an old backup I had made before rooting the phone earlier this year. Now I'm back!

henning_ said:
Thanks, I just did this, but I installed an old backup I had made before rooting the phone earlier this year. Now I'm back!
Click to expand...
Click to collapse
Glad you got it fixed because I couldn't find anything for you about the RUU for 64 bit... So I was pretty sure you could fix it by rooting it!