I have bricked my Desire 510. I need a ROM to flash through philz touch recovery, if some one in Australia has this device with philz touch can you please make a backup in the recovery and then post it to me! Its my last hope because no RUUs are working.
Either that or make me a ROM that is for the Australian telstra 64-bit model maybe some ome can teach me how to create and compile it my self.
Have you tried a backup first ?
Vmo x said:
I have bricked my Desire 510. I need a ROM to flash through philz touch recovery, if some one in Australia has this device with philz touch can you please make a backup in the recovery and then post it to me! Its my last hope because no RUUs are working.
Either that or make me a ROM that is for the Australian telstra 64-bit model maybe some ome can teach me how to create and compile it my self.
Click to expand...
Click to collapse
This seems like a Strange question I know, But have you tried doing a BACKUP FIRST ?
Now having had to rescue a couple of these phones (3 to be precise) , (all with the same nandroid backup I might add)
(With No help from HTC - where are the RUU links for our phone I have to ask?, that having been said, thanks HTC for letting me unlock bootloader, (still cool) I take it all back.....)
I have found however that if a flash completes but is no good , fails to boot for example, that if you FIRST, take a backup with philz of your corrupted system, - to allow the recovery to write a last log to (broken) system with mount points,phone specifics about baseband, serial no., etc,.. BEFORE trying to restore a Good copy of a nandroid backup
(hope you have one! )
That you should then be able to restore a nandroid backup to phone. sometimes even a nandroid that failed last time. (due to failing to find mount points)
A quick note on this point is that only backups made while booted into recovery have proven successful when trying to restore backups thus far, all methods of taking backups any other way are/will be corrupted and will not prove in any way useful to restore your device.
Most of the RUU updates are wrong bootloader by the way they are based on 3.4 kernel (32bit) and not 3.10 kernel which is what 64 bit is running.
I would offer you a copy of a nandroid myself but I am aware that radio firmware is tied to carrier and probably would not work for your baseband and carrier setup. If all else fails however you are of course welcome to try, (pm me if you need a copy) I dont think it will be too long before a successful port to our phone anyway.
Good-luck,
ki113r.
Please send me a nano backup when youre on EU models orange romania
jsjohnsheehan said:
This seems like a Strange question I know, But have you tried doing a BACKUP FIRST ?
Now having had to rescue a couple of these phones (3 to be precise) , (all with the same nandroid backup I might add)
(With No help from HTC - where are the RUU links for our phone I have to ask?, that having been said, thanks HTC for letting me unlock bootloader, (still cool) I take it all back.....)
I have found however that if a flash completes but is no good , fails to boot for example, that if you FIRST, take a backup with philz of your corrupted system, - to allow the recovery to write a last log to (broken) system with mount points,phone specifics about baseband, serial no., etc,.. BEFORE trying to restore a Good copy of a nandroid backup
(hope you have one! )
That you should then be able to restore a nandroid backup to phone. sometimes even a nandroid that failed last time. (due to failing to find mount points)
A quick note on this point is that only backups made while booted into recovery have proven successful when trying to restore backups thus far, all methods of taking backups any other way are/will be corrupted and will not prove in any way useful to restore your device.
Most of the RUU updates are wrong bootloader by the way they are based on 3.4 kernel (32bit) and not 3.10 kernel which is what 64 bit is running.
I would offer you a copy of a nandroid myself but I am aware that radio firmware is tied to carrier and probably would not work for your baseband and carrier setup. If all else fails however you are of course welcome to try, (pm me if you need a copy) I dont think it will be too long before a successful port to our phone anyway.
Good-luck,
ki113r.
Click to expand...
Click to collapse
i was brick my phone and i need help please send my a recovery img my root kep working
jsjohnsheehan said:
This seems like a Strange question I know, But have you tried doing a BACKUP FIRST ?
Now having had to rescue a couple of these phones (3 to be precise) , (all with the same nandroid backup I might add)
(With No help from HTC - where are the RUU links for our phone I have to ask?, that having been said, thanks HTC for letting me unlock bootloader, (still cool) I take it all back.....)
I have found however that if a flash completes but is no good , fails to boot for example, that if you FIRST, take a backup with philz of your corrupted system, - to allow the recovery to write a last log to (broken) system with mount points,phone specifics about baseband, serial no., etc,.. BEFORE trying to restore a Good copy of a nandroid backup
(hope you have one! )
That you should then be able to restore a nandroid backup to phone. sometimes even a nandroid that failed last time. (due to failing to find mount points)
A quick note on this point is that only backups made while booted into recovery have proven successful when trying to restore backups thus far, all methods of taking backups any other way are/will be corrupted and will not prove in any way useful to restore your device.
Most of the RUU updates are wrong bootloader by the way they are based on 3.4 kernel (32bit) and not 3.10 kernel which is what 64 bit is running.
I would offer you a copy of a nandroid myself but I am aware that radio firmware is tied to carrier and probably would not work for your baseband and carrier setup. If all else fails however you are of course welcome to try, (pm me if you need a copy) I dont think it will be too long before a successful port to our phone anyway.
Good-luck,
ki113r.
Click to expand...
Click to collapse
i have a similar case, i was able to get 64 bit RUU's from the internet (Asia WWE, and HTC Europe) but i can't flash them, the following is a description of the situation:
1. bootloader unlocked, custom recovery installed.
2. S-ON,
3. no userdata (system partition ?) i don't know the difference, i can flash boot (kernel) and recovery.
4. i can't flash the above mentioned roms since it is saying i have wrong CID, and i can't change the CID because S-ON
any tips ?
* i was able to download, compile & build kernel from source for telstra, i don't know how system (or userdata) image is built, any hint on that as well ?
mohsh86 said:
i have a similar case, i was able to get 64 bit RUU's from the internet (Asia WWE, and HTC Europe) but i can't flash them, the following is a description of the situation:
1. bootloader unlocked, custom recovery installed.
2. S-ON,
3. no userdata (system partition ?) i don't know the difference, i can flash boot (kernel) and recovery.
4. i can't flash the above mentioned roms since it is saying i have wrong CID, and i can't change the CID because S-ON
any tips ?
* i was able to download, compile & build kernel from source for telstra, i don't know how system (or userdata) image is built, any hint on that as well ?
Click to expand...
Click to collapse
"fastboot getvar cid" and post your CID.
lucyr03 said:
"fastboot getvar cid" and post your CID.
Click to expand...
Click to collapse
Hi Mate,
i've got the following:
Code:
cid: TELST001
i was thinking hex editing the zip file to replace the cid, but since its zipped i can't find the plain text to get it replaced.
thanks in advance.
Have u relocked the bootloader and then tried to install the RUU?
I had the same problem with restoring the orginal Rom.
I think the command for relocking the bootloader was "fastboot oem relock"
SpitFireXB360 said:
Have u relocked the bootloader and then tried to install the RUU?
I had the same problem with restoring the orginal Rom.
I think the command for relocking the bootloader was "fastboot oem relock"
Click to expand...
Click to collapse
I've already done that, having the bootloader unlocked will throw another error, this was incorrect CID related one.
my phone is on Telstra (Australia) ROM, sadly, the RUU exists on some Persian forums with paid service, if there is a way where i can compile/build the system image from source, please let me know..
mohsh86 said:
I've already done that, having the bootloader unlocked will throw another error, this was incorrect CID related one.
my phone is on Telstra (Australia) ROM, sadly, the RUU exists on some Persian forums with paid service, if there is a way where i can compile/build the system image from source, please let me know..
Click to expand...
Click to collapse
I will make backup of my system and boot wih phillz, but I'm from EU(64bits)
lucyr03 said:
I will make backup of my system and boot wih phillz, but I'm from EU(64bits)
Click to expand...
Click to collapse
thanks mate, but will it flash ? and shall i flash it using recovery or htc_fastboot ?
---------- Post added at 12:58 PM ---------- Previous post was at 12:25 PM ----------
mohsh86 said:
thanks mate, but will it flash ? and shall i flash it using recovery or htc_fastboot ?
Click to expand...
Click to collapse
and mine is 64 bit btw
mohsh86 said:
thanks mate, but will it flash ? and shall i flash it using recovery or htc_fastboot ?
and mine is 64 bit btw
Click to expand...
Click to collapse
First flash this recovery.
Status: Uploading, sorry for my slow upload speed
P.S: My ROM is not stock, missing few system apps and have modifications by me, SORRY
lucyr03 said:
First flash this recovery.
Status: Uploading, sorry for my slow upload speed
P.S: My ROM is not stock, missing few system apps and have modifications by me, SORRY
Click to expand...
Click to collapse
thanks mate,
please let us know the link for the upload
cheers
May I inquire as to how you got S-ON? I'm hoping mine isn't a door stop. It's stuck and out of commission. Not sure at all what to do at this point. Please help....
---------- Post added at 02:19 PM ---------- Previous post was at 02:12 PM ----------
I know RBHeromax made a kernel for our 64bit and was attempting a ROM. But I haven't checked in the progress today, I'm about to however. Can you please send me a copy of your 64 link? St this point I'll try just About anything. I'll keep you posted
Please helpme find RUU for A11_UL.
My device CID is: HTC__059.
Thank.
Htc desire 510 64 bit
lucyr03 said:
I will make backup of my system and boot wih phillz, but I'm from EU(64bits)
Click to expand...
Click to collapse
salut imi poti da te rog backup stock rom de la telefonul tau te roog mult.
htc desire 510 telstra backup files
you need to make a folder named back up then another folder named 2014-01-01.00.46_KTU84L_release-keys
sorry about the spaces but i couldn't post it any other way
https://drive.google.com/open?id=0B...lMZWRXcWJtNzdPWklUMHE0MVc0dE1ENGxDZkNaZ21seDA
download everything from here and put it in the folder and you should be ok
razza15 said:
you need to make a folder named back up then another folder named 2014-01-01.00.46_KTU84L_release-keys
sorry about the spaces but i couldn't post it any other way
https://drive.google.com/open?id=0ByGpSt5l7872fldKRE9mUkc0M1lMZWRXcWJtNzdPWklUMHE0MVc0dE1ENGxDZkNaZ21seDA
download everything from here and put it in the folder and you should be ok
Click to expand...
Click to collapse
please let me know if anyone has any issues
Hello guys,
i can't find a stock rom for my phone.. having a european 64bit Desire 510 CID: htc_031
i hope someone can help me out!
Grtz Marco
razza15 said:
please let me know if anyone has any issues
Click to expand...
Click to collapse
Silly question...but how do I flash these files to the device?
Thanks in advance!
ruu for htc desire 510 64 bit and 32 bit
bobbytables22 said:
Silly question...but how do I flash these files to the device?
Thanks in advance!
Click to expand...
Click to collapse
okay first off lock your bootloader here are the ruu's for 32 bit and 64bit htc desire 510 series
if you are Europe carrier use any of the 64 bit roms make sure boot loader is locked!!
it wont let me post the link for the ruu.exe so email me [email protected]
i will send the link for the ruu for all 64bit models will work no matter what carrier you have
no need to thank me
Device: HTC Desire 626x LTE
Android: 4.4
Ram: 1 GB
internal storage: 16GB
Carrier: Unlock
-----------------------------
After Rooting my device using this way in " tep-by-step root procedure for HTC Desire 626s " but the Custom Recovery not work so i use flash recovery from this video " Root HTC Desire 626X ", After root the device work fine.
later i tried to make factory rest for device so i go to the Advanced Wipe then make factory rest for it But Unfortunately the device down and when i power on, it stop booting in HTC splash screen for ever!!
why? How to fix it?
i think it need to flash Rom it again, when i can find Stock Rom?
Updates
I found the solution for this problem in other thread but this solutions for the 64bit device and android 5.1!!!
link:forum.xda-developers.com/showpost.php?p=63807219&postcount=2
my device HTC 626x A32_UL_K444 not HTC 626x A32_UL_L51 So i try to download the required file for Kitkat 444:
0PKXIMG_A32_UL_K444_DESIRE_SENSE60_h...artial_16G.zip
from the same site but i'can
link: ir-file.com/show.php?token=30321
can you help me plz?
possible fix
mohamed7afezz said:
Device: HTC Desire 626x LTE
Android: 4.4
Ram: 1 GB
internal storage: 16GB
Carrier: Unlock
-----------------------------
After Rooting my device using this way in " tep-by-step root procedure for HTC Desire 626s " but the Custom Recovery not work so i use flash recovery from this video " Root HTC Desire 626X ", After root the device work fine.
later i tried to make factory rest for device so i go to the Advanced Wipe then make factory rest for it But Unfortunately the device down and when i power on, it stop booting in HTC splash screen for ever!!
why? How to fix it?
i think it need to flash Rom it again, when i can find Stock Rom?
Click to expand...
Click to collapse
http://www.htc.com/us/support/htc-desire-626s-t-mobile/news/
So, I have several international HTC m7s (HTC 802w) at work and I'm trying to flash TWRP on these devices. All of them are at least S-off and some unlocked. This one particular device I'm trying to flash is both s-off and unlocked (but these weren't done by me). Interesting thing is, the twrp flashes normally in fastboot, but when I reboot into recovery, there is black screen only. If I attach usb in this state, computer detects MTP device and I can browse the phone contents and when I run adb devices, it says the device is in recovery. Does this mean twrp is flashed but can't correctly boot into it? What can I do to successfully boot into it?
My HBoot is 2.49 and CID is 11111111.
Edit: Another "interesting" bit. When I open back cover, it indeed says HTC 802w, but installed system is 802t.
asakurato said:
So, I have several international HTC m7s (HTC 802w) at work and I'm trying to flash TWRP on these devices. All of them are at least S-off and some unlocked. This one particular device I'm trying to flash is both s-off and unlocked (but these weren't done by me). Interesting thing is, the twrp flashes normally in fastboot, but when I reboot into recovery, there is black screen only. If I attach usb in this state, computer detects MTP device and I can browse the phone contents and when I run adb devices, it says the device is in recovery. Does this mean twrp is flashed but can't correctly boot into it? What can I do to successfully boot into it?
My HBoot is 2.49 and CID is 11111111.
Click to expand...
Click to collapse
Are you sure your twrp img is the one for the 802 model? Because the versions you'll find linked everywhere in this forum section is for the 801 model (the single sim variant).
The dual sim twrp versions are there:
https://twrp.me/htc/htconem7dualsim.html
Edit: Another "interesting" bit. When I open back cover, it indeed says HTC 802w, but installed system is 802t.
Click to expand...
Click to collapse
Someone probably converted this phone from w to t. You can dump the mfg partition to look at the original MID/CID if you really want to know what it was when it shipped from the factory.
alray said:
Are you sure your twrp img is the one for the 802 model? Because the versions you'll find linked everywhere in this forum section is for the 801 model (the single sim variant).
The dual sim twrp versions are there:
https://twrp.me/htc/htconem7dualsim.html
Someone probably converted this phone from w to t. You can dump the mfg partition to look at the original MID/CID if you really want to know what it was when it shipped from the factory.
Click to expand...
Click to collapse
Damn, so that's where I was messing up. I even read getvar multiple times, but somehow didn't pay attention that codename is cdtu. And no, I'm not interested what was shipped from factory, I just thought it had something to do with not being able to boot into twrp.
Another question then. What roms can I flash on cdtu? I have tried AICP from M7 forum, but it ended with error 7.
Edit: Can you tell me how to convert it back to 802w?
Hi all, I have a Desire 510 (D510n), I assume it's a 64bit version.
Long story short purchased a lot of devices on ebay cheap, The Desire 510 (D510n) had no rom that would boot, I assume someone else was tinkering with it, I was able to get the bootloader unlocked and was able to flash a version of twrp I had found in this forum, I may have messed up doing that as I can not do anything with it, It wont flash any roms, it will complete flash but will not boot, I tried many RRU and cannot get it to connect with them, sideloading twrp or cwm will not override the twrp currently on it, I can sd flash in the pre recovery mode but cannot flash as it says its to large.
I have almost run completely out of ideas, I was hoping to ask someone if they happen to have a RUU that is for aus so I can extract the rom.zip from temp folder or a twrp backup of Australia stock to test if twrp will at least flash that.
I am happy to update with any details I can and will post pictures if that helps.
Thanks for taking the time to read.
Cheers, R3AL