Database Develop

[Q] How to I use twrp to flash a new rom (adb sideload not working)

I bricked my HTC One, totally not my fault I received a prompt to upgrade and then the thing crashed. Its stuck on the htc screen.
I tried finding a RUU file for my phone, couldnt get one that matched. Now I have installed TWRP, which works. My Bootloader is unblocked and says tampered also s-on. there is no os in the phone now so its ready for flashing a new rom.
I want to get my phone back in order. I've downloaded a custom rom I could use, wanted to ask if this is the same as using a ota file from the htcdev website ?
When I try to use twrp i cant use sideboot to push the roms, it just says trying to connect and doesnt, so I think adb doesnt work.
Can someone put me in the right direction or help out ?
I'm a complete newbie and have come far by unlocking the bootloader and installing twrp, would really appreciate it if someone can help.
Also tried using the option to find the file on my computer from twrp on my phone but it doesnt connect.
Everything is all set up I just need to flash a new rom and get going.
Thanks !

abreu6 said:
I bricked my HTC One, totally not my fault I received a prompt to upgrade and then the thing crashed. Its stuck on the htc screen.
I tried finding a RUU file for my phone, couldnt get one that matched. Now I have installed TWRP, which works. My Bootloader is unblocked and says tampered also s-on. there is no os in the phone now so its ready for flashing a new rom.
I want to get my phone back in order. I've downloaded a custom rom I could use, wanted to ask if this is the same as using a ota file from the htcdev website ?
When I try to use twrp i cant use sideboot to push the roms, it just says trying to connect and doesnt, so I think adb doesnt work.
Can someone put me in the right direction or help out ?
I'm a complete newbie and have come far by unlocking the bootloader and installing twrp, would really appreciate it if someone can help.
Also tried using the option to find the file on my computer from twrp on my phone but it doesnt connect.
Everything is all set up I just need to flash a new rom and get going.
Thanks !
Click to expand...
Click to collapse
The rest of the steps after you have unlocked bootloader
flash custom recovery TWRP 2.6.3.3 from here
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
rename your rom to rom.zip
then in TWRP / Advanced /Sideload - Slide to sideload
Then from PC - adb / fastboot folder ...shift+right click /command prompt here
then it's
adb sideload rom.zip
at the end of sideload install will begin
just be sure the files you flash and sideload are all in the same folder as fastboot and adb

clsA said:
The rest of the steps after you have unlocked bootloader
flash custom recovery TWRP 2.6.3.3 from here
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
rename your rom to rom.zip
then in TWRP / Advanced /Sideload - Slide to sideload
Then from PC - adb / fastboot folder ...shift+right click /command prompt here
then it's
adb sideload rom.zip
at the end of sideload install will begin
just be sure the files you flash and sideload are all in the same folder as fastboot and adb
Click to expand...
Click to collapse
in cmd prompt says 'device not found' when using adb and on twrp on the device says starting adb sideload and does nothing, also shall i use the ota file on the htcdev website ? is that better than the cutsom roms i've downloaded, - do i need s-off ?

abreu6 said:
in cmd prompt says 'device not found' when using adb and on twrp on the device says starting adb sideload and does nothing, also shall i use the ota file on the htcdev website ? is that better than the cutsom roms i've downloaded, - do i need s-off ?
Click to expand...
Click to collapse
Please stop right here and spend a few hours doing research before you brick your device for good.

I have same thing happened before, adb not working, I don't know why, try use a USB OTG, put the rom zip on it, then connected to your phone, flash from OTG, it will be OK!
Sent from my HTC One using XDA Premium 4 mobile app

shukyuen said:
I have same thing happened before, adb not working, I don't know why, try use a USB OTG, put the rom zip on it, then connected to your phone, flash from OTG, it will be OK!
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I dont have a USB OTG Cable, are there any other options ?
Is there a way of getting files on to the sdcard using fastboot ? tried using adb but dont know where I'm going wrong. It connects 'starting on port...etc' then when i run push commands says 'device not connected'.
Updated all the drivers and everything still no luck. Sideloader from twrp doesnt seem to work either.
I have the rom I want to use and a ruu file which i have tried to flash, its comes back with something like ' remote failed: 24 parshing etc'
Any help would be great !

Sorry, I face the same problem, l am not skilled enough to solve it, if you want flash a rom buy a USB OTG!
Sent from my HTC One using XDA Premium 4 mobile app

Sideloading
I'm sort of in the same boat. My m7 got into a bootloop after an OTA Lollipop update attempt.
I tried flashing files (RUUs) with fastboot but there always seemed to be technical problems that stopped me from doing that (noob).
So I decided to try the custom recovery route. And although I've been learning a huge amount in the last week I haven't really got my head around the TWRP basics.
So, considering the incredible amount of knowledge on this website I'd like to try to clear some issues up. All I want is a standard working phone.
Previously during my 'fastboot' adventure people were talking about RUUs. Are they still relevant when it comes to sideloading?
And where does TWRP come into it if ADB is 'pushing' the file accross? What is it there for?
What kind of
I'm 'unlocked' but s-on, is that an issue? Does the phone need to be rooted?
So, in a nutshell, now that I managed to put TWRP on the phone (very pleased with myself!) how does that make it easier for me to get my phone back to serviceability?
Loads of thanks to all the whizz kids out there.

jimbobly said:
Previously during my 'fastboot' adventure people were talking about RUUs. Are they still relevant when it comes to sideloading?
Click to expand...
Click to collapse
No. RUU is a package including the rom (software) and the frimware (hboot, stock recovery, radio, kernel, touch drivers etc.)
RUU.zip are flashed using fastboot
RUU.exe are flashed automatically when laucnhing the .exe (the application handle the required fastboot commands automatically)
When speaking about adb sideload or adb push, the sidelaoded or pushed file is only a rom (software) unlike a ruu (software+firmware). The rom can either be custom or stock (e.g ARHD custom rom or a stock guru reset rom)
And where does TWRP come into it if ADB is 'pushing' the file accross? What is it there for?
Click to expand...
Click to collapse
ADB is used for the computer to communicate with the phone and in this case, to copy the rom from your computer to your phone. ADB doesn't flash (install) the rom on your phone, its only transfer the rom to your phone memory. TWRP is a recovery system, think of an alternate OS you can boot to perform basic tasks like installing rom (flashing rom), backups, restore, file manager ans few more.
BTW with newer versions of TWRP, you don't really need ADB to transfer (push or sideload) the rom to your phone. TWRP now support MTP protocol which mean you'll see your phone as a removable storage on your computer (like a usb thumb drive) when booted in twrp so can simply drag and drop the rom from your desktop to the phone memory.
I'm 'unlocked' but s-on, is that an issue? Does the phone need to be rooted?
So, in a nutshell, now that I managed to put TWRP on the phone (very pleased with myself!) how does that make it easier for me to get my phone back to serviceability?
Loads of thanks to all the whizz kids out there.
Click to expand...
Click to collapse
Better to post the output of "fastboot getvar all" before answering this. Depending on the output, it might be easier to restore your phone using a RUU. Remove your imei and serialno before posting the output here.

Thanks Alray,
That was a great reply. Just the sort of concise information I need.
Here is the getvar.
\Desktop\android-sdk-windows\platfo
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.14.206.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---
(bootloader) imei: ---
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4314mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also, several members pointed me to an RUU that would get me back to stock, here is the contents of the unziped file. I'd like to know which files are relevant with TWRP. The interesting thing is that the download was about 1.7Gigs but the unpacked files aren't remotely close to that so something doesn't seem to add up!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Brilliant assistance, I love fiddling with this stuff but so far drawn a bit of a blank with this one.
BTW I put TWRP on yesterday so I assume it's the latest version.
---------- Post added at 07:18 AM ---------- Previous post was at 07:08 AM ----------
alray said:
No. RUU is a package including the rom (software) and the frimware (hboot, stock recovery, radio, kernel, touch drivers etc.)
RUU.zip are flashed using fastboot
RUU.exe are flashed automatically when laucnhing the .exe (the application handle the required fastboot commands automatically)
When speaking about adb sideload or adb push, the sidelaoded or pushed file is only a rom (software) unlike a ruu (software+firmware). The rom can either be custom or stock (e.g ARHD custom rom or a stock guru reset rom)
ADB is used for the computer to communicate with the phone and in this case, to copy the rom from your computer to your phone. ADB doesn't flash (install) the rom on your phone, its only transfer the rom to your phone memory. TWRP is a recovery system, think of an alternate OS you can boot to perform basic tasks like installing rom (flashing rom), backups, restore, file manager ans few more.
BTW with newer versions of TWRP, you don't really need ADB to transfer (push or sideload) the rom to your phone. TWRP now support MTP protocol which mean you'll see your phone as a removable storage on your computer (like a usb thumb drive) when booted in twrp so can simply drag and drop the rom from your desktop to the phone memory.
Better to post the output of "fastboot getvar all" before answering this. Depending on the output, it might be easier to restore your phone using a RUU. Remove your imei and serialno before posting the output here.
Click to expand...
Click to collapse
Thanks Alray,
That was a great reply. Just the sort of concise information I need.
Here is the getvar.
\Desktop\android-sdk-windows\platfo
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.14.206.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---
(bootloader) imei: ---
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4314mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also, several members pointed me to an RUU that would get me back to stock, here is the contents of the unziped file. I'd like to know which files are relevant with TWRP. The interesting thing is that the download was about 1.7Gigs but the unpacked files aren't remotely close to that so something doesn't seem to add up!
Brilliant assistance, I love fiddling with this stuff but so far drawn a bit of a blank with this one.
BTW I put TWRP on yesterday so I assume it's the latest version.

jimbobly said:
Thanks Alray,
That was a great reply. Just the sort of concise information I need.
Here is the getvar.
\Desktop\android-sdk-windows\platfo
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.14.206.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---
(bootloader) imei: ---
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4314mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also, several members pointed me to an RUU that would get me back to stock, here is the contents of the unziped file. I'd like to know which files are relevant with TWRP. The interesting thing is that the download was about 1.7Gigs but the unpacked files aren't remotely close to that so something doesn't seem to add up!
Brilliant assistance, I love fiddling with this stuff but so far drawn a bit of a blank with this one.
BTW I put TWRP on yesterday so I assume it's the latest version.
---------- Post added at 07:18 AM ---------- Previous post was at 07:08 AM ----------
Thanks Alray,
That was a great reply. Just the sort of concise information I need.
Here is the getvar.
\Desktop\android-sdk-windows\platfo
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.14.206.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---
(bootloader) imei: ---
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4314mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also, several members pointed me to an RUU that would get me back to stock, here is the contents of the unziped file. I'd like to know which files are relevant with TWRP. The interesting thing is that the download was about 1.7Gigs but the unpacked files aren't remotely close to that so something doesn't seem to add up!
Brilliant assistance, I love fiddling with this stuff but so far drawn a bit of a blank with this one.
BTW I put TWRP on yesterday so I assume it's the latest version.
Click to expand...
Click to collapse
What is the file name of this ruu? You should not be able to open the ruu.zip because they are encrypted. You could try to relock the bootloader and flash the 7.18.206.2 ruu.zip posted here http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944. instruction how to flash in the same thread.
or
You can restore this stock backup using twrp then you can reflash the stock recovery and download the latest ota update.

alray said:
You can restore this stock backup using twrp then you can reflash the stock recovery and download the latest ota update.
Click to expand...
Click to collapse
That's great. I'll try going down this road first, can you briefly outline how to handle this process with TWRP please?
Many thanks. :good:

jimbobly said:
That's great. I'll try going down this road first, can you briefly outline how to handle this process with TWRP please?
Many thanks. :good:
Click to expand...
Click to collapse
boot in twrp, select "backup" then make a backup of "boot" only (this is only to generate a backup path on your phone: /sdcard/TWRP/BACKUPS/YOUR_SERIAL_NUMBER/DATE_OF_BACKUP). Once the backup is done, navigate to that folder and delete all the files in that folder, but do not delete the folder and then take all the files in the backup you have downloaded and copy them to this folder (/sdcard/TWRP/BACKUPS/YOUR_SERIAL_NUMBER/DATE_OF_BACKUP).
Go back in twrp main menu, select "restore" and select the only backup available. Wait for the restore to complete and reboot.

alray said:
boot in twrp, select "backup" then make a backup of "boot" only (this is only to generate a backup path on your phone: /sdcard/TWRP/BACKUPS/YOUR_SERIAL_NUMBER/DATE_OF_BACKUP). Once the backup is done, navigate to that folder and delete all the files in that folder, but do not delete the folder and then take all the files in the backup you have downloaded and copy them to this folder (/sdcard/TWRP/BACKUPS/YOUR_SERIAL_NUMBER/DATE_OF_BACKUP).
Go back in twrp main menu, select "restore" and select the only backup available. Wait for the restore to complete and reboot.
Click to expand...
Click to collapse
Thanks, I'm on the case now. To be sure, the file that you specified starting /sdcard/ is different from the file where the phone just made the back up files.
The only file path I can access on the PC is Computer\One\Internal Storage\TWRP\BACKUPS\FA36PW918055.
Is this correct?
I assume that references to an sdcard in file names is just nominal or a partition of the main drive.
Just like to be 100% clear.
Ah, I discovered that there is a file manager in TWRP! I now see that Those files are in the folder that you specified correctly.
However, when I go to the backup folder there is no file available. Are the files from the nandroid zip to be extracted first or is the zip file supposed to be copied whole?
I tried both methods and there is still no file to be seen in the restore window!
Have I done something wrong?

jimbobly said:
The only file path I can access on the PC is Computer\One\Internal Storage\TWRP\BACKUPS\FA36PW918055.
Is this correct?
Click to expand...
Click to collapse
Yes on your pc you'll see Computer\One\Internal Storage\TWRP\BACKUPS\FA36PW918055\date_of_your_backup\Backup_files_here
On your phone its /sdcard/TWRP/BACKUPS/FA36PW918055/date_of_your_backup/Backup_files_here
Make a backup of boot only, then using your computer navigate to that folder (Computer\One\Internal Storage\TWRP\BACKUPS\FA36PW918055\date_of_backup) and delete all files in this folder and replaced them with all files from the backup you have downloaded. Then in twrp select "restore" and restore all partitions of this backup.

alray said:
boot in twrp, select "backup" then make a backup of "boot" only (this is only to generate a backup path on your phone: /sdcard/TWRP/BACKUPS/YOUR_SERIAL_NUMBER/DATE_OF_BACKUP). Once the backup is done, navigate to that folder and delete all the files in that folder, but do not delete the folder and then take all the files in the backup you have downloaded and copy them to this folder (/sdcard/TWRP/BACKUPS/YOUR_SERIAL_NUMBER/DATE_OF_BACKUP).
Go back in twrp main menu, select "restore" and select the only backup available. Wait for the restore to complete and reboot.
Click to expand...
Click to collapse
alray said:
Make a backup of boot only, then using your computer navigate to that folder (Computer\One\Internal Storage\TWRP\BACKUPS\FA36PW918055\date_of_backup) and delete all files in this folder and replaced them with all files from the backup you have downloaded. Then in twrp select "restore" and restore all partitions of this backup.
Click to expand...
Click to collapse
Ah, I discovered that there is a file manager in TWRP! I now see that Those files are in the folder that you specified correctly.
However, when I go to the backup folder there is no file available. Are the files from the nandroid zip to be extracted first or is the zip file supposed to be copied whole?
I tried both methods and there is still no file to be seen in the restore window!
Have I done something wrong?
---------- Post added at 11:37 PM ---------- Previous post was at 11:06 PM ----------
jimbobly said:
Ah, I discovered that there is a file manager in TWRP! I now see that Those files are in the folder that you specified correctly.
However, when I go to the backup folder there is no file available. Are the files from the nandroid zip to be extracted first or is the zip file supposed to be copied whole?
I tried both methods and there is still no file to be seen in the restore window!
Have I done something wrong?
Click to expand...
Click to collapse
Just managed to attempt a restore.
Response from system is ' Restore Complete Failed' E:No Partitions Selected for restore'!
Any ideas on this?
Thanks
James
---------- Post added 10th April 2015 at 12:00 AM ---------- Previous post was 9th April 2015 at 11:37 PM ----------
jimbobly said:
Ah, I discovered that there is a file manager in TWRP! I now see that Those files are in the folder that you specified correctly.
However, when I go to the backup folder there is no file available. Are the files from the nandroid zip to be extracted first or is the zip file supposed to be copied whole?
I tried both methods and there is still no file to be seen in the restore window!
Have I done something wrong?
---------- Post added at 11:37 PM ---------- Previous post was at 11:06 PM ----------
Just managed to attempt a restore.
Response from system is ' Restore Complete Failed' E:No Partitions Selected for restore'!
Any ideas on this?
Thanks
James
Click to expand...
Click to collapse
jimbobly said:
Thanks, I'm on the case now. To be sure, the file that you specified starting /sdcard/ is different from the file where the phone just made the back up files.
The only file path I can access on the PC is Computer\One\Internal Storage\TWRP\BACKUPS\FA36PW918055.
Is this correct?
I assume that references to an sdcard in file names is just nominal or a partition of the main drive.
Just like to be 100% clear.
Ah, I discovered that there is a file manager in TWRP! I now see that Those files are in the folder that you specified correctly.
However, when I go to the backup folder there is no file available. Are the files from the nandroid zip to be extracted first or is the zip file supposed to be copied whole?
I tried both methods and there is still no file to be seen in the restore window!
Have I done something wrong?
Click to expand...
Click to collapse
Holy Crap!
I did it! It worked!!
Amazing, thanks so much.
Wow, what an adventure that was. Funny, I just learned loads about my phone and android totally by accident thanks to the community on here, great job!
---------- Post added at 12:18 AM ---------- Previous post was at 12:00 AM ----------
What would be the way to get the ota update for lollipop now?

jimbobly said:
Ah, I discovered that there is a file manager in TWRP! I now see that Those files are in the folder that you specified correctly.
However, when I go to the backup folder there is no file available. Are the files from the nandroid zip to be extracted first or is the zip file supposed to be copied whole?
I tried both methods and there is still no file to be seen in the restore window!
Have I done something wrong?
---------- Post added at 11:37 PM ---------- Previous post was at 11:06 PM ----------
Just managed to attempt a restore.
Response from system is ' Restore Complete Failed' E:No Partitions Selected for restore'!
Any ideas on this?
Thanks
James
---------- Post added 10th April 2015 at 12:00 AM ---------- Previous post was 9th April 2015 at 11:37 PM ----------
Holy Crap!
I did it! It worked!!
Amazing, thanks so much.
Wow, what an adventure that was. Funny, I just learned loads about my phone and android totally by accident thanks to the community on here, great job!
---------- Post added at 12:18 AM ---------- Previous post was at 12:00 AM ----------
What would be the way to get the ota update for lollipop now?
Click to expand...
Click to collapse
Sorry for the late reply, glad to know that you have managed to restore the backup. To be able to install ota update you'll need to flash the stock recovery over twrp.
Stock recovery for your version can be downloaded from this link: https://www.androidfilehost.com/?fid=95897840722646670
save it in the same folder where you have adb and fastboot on your computer and flash it like you did for twrp:
reboot your phone in bootloader / fastboot usb mode then open a command prompt from your adb/fastboot folder:
Code:
fastboot flash recovery M7_UL_Stock_Recovery_6.14.206.2.img
fastboot erase cache
fastboot reboot
Once rebooted in the os and the stock recovery flashed, you can install the ota updates: settings --> about --> Software info --> check for updates.

alray said:
Sorry for the late reply, glad to know that you have managed to restore the backup. To be able to install ota update you'll need to flash the stock recovery over twrp.
Stock recovery for your version can be downloaded from this link: https://www.androidfilehost.com/?fid=95897840722646670
save it in the same folder where you have adb and fastboot on your computer and flash it like you did for twrp:
reboot your phone in bootloader / fastboot usb mode then open a command prompt from your adb/fastboot folder:
Code:
fastboot flash recovery M7_UL_Stock_Recovery_6.14.206.2.img
fastboot erase cache
fastboot reboot
Once rebooted in the os and the stock recovery flashed, you can install the ota updates: settings --> about --> Software info --> check for updates.
Click to expand...
Click to collapse
Thanks very much for the support, great community on here, love it.
Really thought that was the end of my One but it's incredible what a bit of perseverance does for you.
I'll give that update a go, maybe now I have the confidence to experiment a bit more with the phone.
Thanks again!

help me please, I lost my os.

I'm using TWRP for a factory reset , but I hit the wrong press the Format Data , and now can not do anything with it . Help me I'm going to do next . In order to give the computer back to normal. My machine is detailed
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000.
(bootloader) version-baseband: 4A.21.3263.04.
(bootloader) version-cpld: None.
(bootloader) version-microp: None.
(bootloader) version-main: 3.63.61.1.
(bootloader) version-misc: PVT SHIP S-ON.
(bootloader) serialno: FA395WXXXXX
(bootloader) imei: 35XXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064.
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good.
(bootloader) battery-voltage: 3800mV.
(bootloader) partition-layout: Generic.
(bootloader) security: on
(bootloader) build-mode: SHIP.
(bootloader) boot-mode: FASTBOOT.
(bootloader) commitno-bootloader: dirty-b0a25cb2.
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
ADB sideload is Failed :crying::crying::crying:
but can use adb fastboot
help me please

I am kinda trying to figure out the same issue, I will post a reply in here if I get it working. I think from what I have read you might need to relock your device and flash an appropriate RUU in fastboot usb using the apropriate adb commands. I am a newbie though and still learning the android architecture so I would wait for someone more qualified to respond. If I get my device back to a stable ROM I will update you on the steps I took!

adb push?

Yep like he said. In recovery adb push ROM.zip /sdcard/
Sent from my HTC One using XDA Premium 4 mobile app

thank for help
svenell said:
I am kinda trying to figure out the same issue, I will post a reply in here if I get it working. I think from what I have read you might need to relock your device and flash an appropriate RUU in fastboot usb using the apropriate adb commands. I am a newbie though and still learning the android architecture so I would wait for someone more qualified to respond. If I get my device back to a stable ROM I will update you on the steps I took!
Click to expand...
Click to collapse
I can relock it again, but I have no ruu for cid: ORANG001 trying to hard.:crying::crying:

thank for help
nateboi81 said:
Yep like he said. In recovery adb push ROM.zip /sdcard/
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you recommend a rom for my device that you can use nandroid or not.
I'm finding it difficult
Thank you

tell me please

"adb sideload", while convenient, is less reliable than the old-fashioned method of pushing to /sdcard and using TWRP to install it. For this to work:
- TWRP must be installed (2.6.3.3 or newer).
- If not installed, make sure the bootloader is unlocked and install it with "fastboot flash recovery name-of-recovery.img", then clear cache just to be safe.
- Boot to TWRP through the bootloader using volume/power buttons (look for instructions online)
- Use "adb devices" to make sure ADB is working and detecting the phone
- Use "adb push rom.zip /sdcard/"
- If the push fails, make sure you are typing the correct path/filename to the ROM zip you want to install.
- If the push fails with an error about can't write or "no such file or directory", your data partition may be corrupted or not mounted (or maybe even out of space). You can solve this within TWRP. The most drastic (and most effective) solution is to format userdata, but you'll lose everything on the phone. There are other ways to solve this, but it's a case-by-case thing.
- If you try something to fix the "push" and want to try again, make sure /data and /sdcard are mounted (in the TWRP mounts section).
- After "push", you should check the md5sum of the file to make sure it hasn't been corrupted (check to see that it agrees with the md5sum on the download page). If there is no md5sum on the download page, ask in a forum.
- The command to check the md5sum for ALL zip files on /sdcard (because this is accident-proof) is:
Code:
adb shell "md5sum /sdcard/*.zip"
- Then you can "install" the normal way, using TWRP, without sideload.
Depending on which step fails, there are different things to try to fix the problem. If something fails, please provide ALL details of what you did, and all details about the error (write down the exact error message). If the error is in your TWRP usage, get the "recovery.log" file, which you can copy to the computer with
Code:
adb pull /tmp/recovery.log
---------- Post added at 09:06 AM ---------- Previous post was at 09:03 AM ----------
Oh, and I forgot to mention, the ROM that most people seem to use (also the one that looks the most like the stock ROM) is Android Revolution HD. Note that there's a bug in the installer: if you don't have the newest firmware, you should choose "Wipe Data" when the Aroma Installer asks whether you want to wipe data. For some reason this is not the same as a factory reset in the TWRP menus.

fenstre said:
"adb sideload", while convenient, is less reliable than the old-fashioned method of pushing to /sdcard and using TWRP to install it. For this to work:
Click to expand...
Click to collapse
I'm having a similar issue but my internal sd won't mount when I start it, It says unable to moung /system, /cache and so forth. I'm running out of things to try.
---------- Post added at 04:11 PM ---------- Previous post was at 04:04 PM ----------
fenstre said:
"adb sideload", while convenient, is less reliable than the old-fashioned method of pushing to /sdcard and using TWRP to install it. For this to work:
Click to expand...
Click to collapse
I'm having a similar issue but my internal sd won't mount when I start it, It says unable to moung /system, /cache and so forth. I'm running out of things to try.

You can use fastboot to wipe all those partitions. Fastboot erase system.....cache...etc. then format those ones in twrp
Sent from my HTC One using XDA Premium 4 mobile app

REQUEST: Telus TWRP Backup

FOR SPECIFIC INSTRUCTIONS ON HOW TO DO THIS BACKUP, PLEASE GO DOWN A COUPLE POSTS, SPECIFICALLY HERE: http://forum.xda-developers.com/showpost.php?p=59150233&postcount=3
Thanks!
So far during this weekend there has been considerable progress on the quest to completely dominate this phone. Member jodge managed to get his VM/Sprint S-OFF and right after that SuperCID of course. You can pickup the story here. However there is something we need in order to move forward and we need it badly: a Telus TWRP Backup.
I am not one to charge for helping out whenever I can, but I have helped a few Telus guys, even PMed them requesting a Telus backup and so far no one has come forward and honestly I am little disappointed. I know it's a pain if you did not make a backup before you set up your phone, but we really need a Telus TWRP stock backup. I can provide complete instructions if you need. PM me at will.
Thanks very much!

NOT TRYING TO BE RUDE OR ANYTHING, BUT . . . .
C'mon all you the people that complain
and/or ask constantly about the potential to
unlock the sim, this would be your time
to help out and further the cause!
I'm sure other GSM carrier backups would be
helpful as well.
IT'S YOUR TIME TO SHINE AND BE
THE CONTRIBUTION!​

Hi
pls check the following thing before do anything:
phone in fastboot mode:
Code:
fastboot getvar platform
platform: hTCBmsm8226 <--- just this cpu works!
After that we need the whole backup! Unfortunately nandroid backup not enough
This process won't harm your phone, it's just a simple reading
You need at least 8gb sd card in the phone
A phone with unlocked boot (htcdev.com)
in the pc (phone in fastboot mode)
Code:
[B]fastboot boot openrecovery-twrp-2.8.5.0-a11.img[/B]
in the twrp--> mount --> tick system
int the pc:
Code:
[B]
adb shell[/B]
Code:
[B]ls -al /dev/block/platform/msm_sdcc.1/by-name[/B]
<-- you get all partitons by name and by number
Code:
[B]dd if=/dev/block/mmcblk0p1 of=/external_sd/1.bin[/B]
Code:
[B]dd if=/dev/block/mmcblk0p2 of=/external_sd/2.bin[/B]
Code:
[B]dd if=/dev/block/mmcblk0p3 of=/external_sd/3.bin[/B]
and all other partition (40-44 pcs)
thx

I have a 64 bit phone. So there is no twrp for me otherwise I'd love to get this for you even though I'm not using a telus build.

If this depended on you Burtrum57, we would have had it a couple of month ago
Burtrum57 said:
I have a 64 bit phone. So there is no twrp for me otherwise I'd love to get this for you even though I'm not using a telus build.
Click to expand...
Click to collapse

Your lord and saviour is here. I'm not experienced at backing up and stuff but I have an unlocked bootloader and yes, I am on Telus. I am willing to help you guys and I know jdmederios I pm'd you before asking you if you needed a backup and you said it was okay. Since you helped me out, it's only fair to help you right? So if you guys can walk me through this process, I'll be completely fine with helping you guys out!
How will I backup my current data so I can restore it after everything? Just make a TWRP backup of what I have now?

Great to hear from you karmasblade! Stand by as I prepare a script, test it on my phone and send it to you. I imagine you have TWRP installed. I will PM you as soon as I test my script on my phone, just to make sure it works fine. Thanks a lot for your help!
karmasblade said:
Your lord and saviour is here. I'm not experienced at backing up and stuff but I have an unlocked bootloader and yes, I am on Telus. I am willing to help you guys and I know jdmederios I pm'd you before asking you if you needed a backup and you said it was okay. Since you helped me out, it's only fair to help you right? So if you guys can walk me through this process, I'll be completely fine with helping you guys out!
How will I backup my current data so I can restore it after everything? Just make a TWRP backup of what I have now?
Click to expand...
Click to collapse

I decided to place the instructions here in the open so that others can review them and eventually find some mistakes. karmasblade you owe me absolutely nothing and if you decide this is too much of a pain I completely understand.
karmasblade, BEFORE YOU DO THIS I WOULD LIKE 2 OR 3 SENIOR MEMBERS TO VALIDADE THESE INSTRUCTIONS; THAT'S WHY THEY ARE HERE INSTEAD OF ME JUST PM YOU
If you decide to do it, make sure you copy paste the commands whenever possible. The following steps are needed to make sure you do not share any personal information. If your phone did not have any personal information you would just have to do steps 16 through 19 and then upload the folder.
1. You will need your Unlock_code.bin from HTCDEV; if you still have it great (it may still be in your email) otherwise you need to go through the bootloader unlock procedure up to the step where you get an email from HTC with the file Unlock_code.bin which you should place in the folder where you have fastboot.exe
2. You will need openrecovery-twrp-2.8.5.0-a11.img which you can get here http://techerrata.com/file/twrp2/a11/openrecovery-twrp-2.8.5.0-a11.img and save it in the same folder where you have fastboot.exe
3. Download this RUU https://mega.co.nz/#!6Z4SQDTA!3W89qbflxnQhE8fr_QnJMBFAO3aCHKcdkegFtxQ6tuY rename it to 0PCVIMGXXX and place it in the root of the sdcard
4. Connect the phone to the PC and run “abd shell”, “su” and then “cat /proc/emmc” From this list you need to find out the highest numbered block. In my case it’s mmcblk0p44 and therefore the number is 44.
5. Connect the phone to the PC and run "adb reboot recovery" When the recovery menu comes up on the phone press "Backup" On the top of the screen, press "Backup Name", add a few characters to the name so you know it's this backup and hit the return key
6. After the backup is complete, from the main menu, press "Wipe", then "Advanced Wipe" and select the first 4 options: Dalvik, System, Cache, Data; Slide to Wipe
7. From the PC run "adb shell" and then execute "mv /external_sd/0PCVIMGXXX /external_sd/0PCVIMG.zip"
8. From the main menu Press "Reboot" and then "Bootloader". It will say "No OS Installed! Are you sure you wish to reboot?" Press "Swipe to Reboot". It will then say "Install SuperSU?" and you should press "Do Not Install". After a few seconds (about 8) it will reboot. It will say "FASTBOOT USB" in red and "HBOOT" in the blue bar.
9. From the PC run "fastboot oem lock". The phone will reboot and come back to the same screen.
10. Press the Power button once; when you do this it will search your sdcard looking for the 0PCVIMG.zip and it will install it. Eventually it will say "Update Complete..." press <POWER> to reboot. Hit the "Power" button to reboot.
11. Once the phone boots, got to settings and turn on developer options and usb debuging. On the phone run the File Manager application, open the sdcard and rename 0PCVIMG.zip to 0PCVIMGXXX.
12. From the PC run "adb reboot bootloader"
13. Unlock the bootloader... from the PC run "fastboot flash unlocktoken Unlock_code.bin" and the phone will reboot.
14. From the PC run "adb reboot bootloader"
15. From the PC install recovery “fastboot flash recovery openrecovery-twrp-2.8.5.0-a11.img”
16. Reboot to Recovery by pressing the Power button and then VOL down to select RECOVERY followed by the Power button again, It will go to the Recovery menu.
17. Form the PC run “adb shell”
18. Inside the shell run “mkdir /external_sd/mmcblks”
19. For this step you will need the number from Step 4. If it’s not 44 then change the 44 in the following command. Inside the shell run
Code:
for i in `seq 1 44`; do dd if=/dev/block/mmcblk0p$i of=/external_sd/mmcblks/mmcblk0p$i.bin; done
This will take a while as it copies the memory blocks to the folder mmcblks in the sdcard.
20. From the Recovery menu, select Restore, select the backup you did on Step 5 and restore your phone. Reboot system and you should have your original phone back.
21. If you had a kernel other than the stock kernel installed you will have to install it again. To do that you would reboot to fastboot running “adb reboot bootloader” and then “fastboot flash boot xxxxxxxxxxx.img”.
22. That’s it; you would then have to upload the folder mmcblks to a place like Mega.
jdmedeiros said:
Great to hear from you karmasblade! Stand by as I prepare a script, test it on my phone and send it to you. I imagine you have TWRP installed. I will PM you as soon as I test my script on my phone, just to make sure it works fine. Thanks a lot for your help!
Click to expand...
Click to collapse

Would a Fido back up (same model number as Telus) help?
Sent from my HTC Desire 510 using XDA Free mobile app

...a lady for the rescue. About time
Please do this:
1. Connect the phone to the usb port and run:
Code:
adb shell cat /proc/emmc
Your last line should say something like mmcblk0p44: 48000000 00000200 "userdata". What is you last memory block number? Mine is 44.
2. Run
Code:
adb reboot bootloader
3. After it reboots, run:
Code:
fastboot getvar platform
If it says "platform: hTCBmsm8226" and your last memory block is around 44 then you could certainly help us.
4. Run
Code:
fastboot reboot
to restart your phone.
Thank you!
CrankyCatLady said:
Would a Fido back up (same model number as Telus) help?
Sent from my HTC Desire 510 using XDA Free mobile app
Click to expand...
Click to collapse

My last memory block number is also 44 "mmcblk0p44: 20000000 00000200 "userdata""
And for Getvar, here's the complete information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1372.19.0918
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****************
(bootloader) imei: ********************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a11_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0PCV22000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 74b2d0b4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please let me know if it still looks good. I guess I will follow the instruction on the previous post for the backup.
jdmedeiros said:
...a lady for the rescue. About time
Please do this:
1. Connect the phone to the usb port and run:
Code:
adb shell cat /proc/emmc
Your last line should say something like mmcblk0p44: 48000000 00000200 "userdata". What is you last memory block number? Mine is 44.
2. Run
Code:
adb reboot bootloader
3. After it reboots, run:
Code:
fastboot getvar platform
If it says "platform: hTCBmsm8226" and your last memory block is around 44 then you could certainly help us.
4. Run
Code:
fastboot reboot
to restart your phone.
Thank you!
Click to expand...
Click to collapse

Yes, that is exactly what we are looking for and thank you for being willing to help us. Please follow this post http://forum.xda-developers.com/showpost.php?p=59172863&postcount=8 and be sure to copy paste as much as possble; for example in step 3 I say "...rename it to 0PCVIMGXXX..." That first character looks like the letter "O" but it's actually a zero. Also make sure that each step completes without error before moving on to the next step. I edited the post adding a little more information to steps 11 and 16. Let me know if you have any problem. Thank you!
CrankyCatLady said:
My last memory block number is also 44 "mmcblk0p44: 20000000 00000200 "userdata""i
And for Getvar, here's the complete information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1372.19.0918
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****************
(bootloader) imei: ********************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a11_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0PCV22000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 74b2d0b4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please let me know if it still looks good. I guess I will follow the instruction on the previous post for the backup.
Click to expand...
Click to collapse

great news
thx for the support

One quick question before I really proceed to wipe anything through TWRP 2.8.5.0, would my original ROM be wiped and I can be running in boot loop?? In particular: "6. After the backup is complete, from the main menu, press "Wipe", then "Advanced Wipe" and select the first 4 options: Dalvik, System, Cache, Data; Slide to Wipe"
PS would need to gather a few things to really proceed (ie looking to find a spare/blank microSD card), should be done on the weekend.
jdmedeiros said:
Yes, that is exactly what we are looking for and thank you for being willing to help us. Please follow this post http://forum.xda-developers.com/showpost.php?p=59172863&postcount=8 and be sure to copy paste as much as possble; for example in step 3 I say "...rename it to 0PCVIMGXXX..." That first character looks like the letter "O" but it's actually a zero. Also make sure that each step completes without error before moving on to the next step. I edited the post adding a little more information to steps 11 and 16. Let me know if you have any problem. Thank you!
Click to expand...
Click to collapse

Looking for a Rogers RUU
I am looking for this file RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Rogers_WWE_1.18. 631.2_Radio_1.101.1372.19.0918_10.24.4205.00L_rele ase_397685_signed.exe which is available here http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/A11_UL/
If any of your guys have access to it I would appreciate if you could share it. My access expired a few weeks ago and that was how I was able to get all the files I have been sharing with you. Thanks!

jdmedeiros said:
I am looking for this file RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Rogers_WWE_1.18. 631.2_Radio_1.101.1372.19.0918_10.24.4205.00L_rele ase_397685_signed.exe which is available here http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/A11_UL/
If any of your guys have access to it I would appreciate if you could share it. My access expired a few weeks ago and that was how I was able to get all the files I have been sharing with you. Thanks!
Click to expand...
Click to collapse
Im guessing it requires a membership of some sort? If so how much, Im a bit strapped for cash so you'll have to wait a couple weeks for me to get to it if so.

Thanks, but no, don't worry about it, eventually it pop up or someone with access will share it, just like I have done with so many files.
howlingmoon12 said:
Im guessing it requires a membership of some sort? If so how much, Im a bit strapped for cash so you'll have to wait a couple weeks for me to get to it if so.
Click to expand...
Click to collapse

Bricked, no adb in recovery, rru needed?

I tried to install a custom rom on the device, it never worked, i ended formatting the system + data by accident.
I have philz recovery on it, i tried to mount the data folder and transfer files via abd, this never worked, sideloading through the recovery doesn't work either, i've spent about 6 hours straight on this, tried every driver i could find, still no adb.
I download a ruu, i don't have access to a linux machine in order to change the file for the cid though, I could not for the life of me find the proper ruu file.
Fastboot is working!
heres some info.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 01.02.010_U10251_37.08.40820
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CC523Y403558
(bootloader) imei: 35xxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a11_ul
(bootloader) platform: hTCBmsm8916
(bootloader) modelid: 0PCV20000
(bootloader) cidnum: HTC__052
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cfaddc6b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 1001
Any advice on where i go from here would be good, if anyone has the proper ruu file i need that would be awesome!
Thanks
*note i have no sd card, and no access to one.

jpno5 said:
I tried to install a custom rom on the device, it never worked, i ended formatting the system + data by accident.
I have philz recovery on it, i tried to mount the data folder and transfer files via abd, this never worked, sideloading through the recovery doesn't work either, i've spent about 6 hours straight on this, tried every driver i could find, still no adb.
I download a ruu, i don't have access to a linux machine in order to change the file for the cid though, I could not for the life of me find the proper ruu file.
Fastboot is working!
heres some info.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 01.02.010_U10251_37.08.40820
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CC523Y403558
(bootloader) imei: 35xxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a11_ul
(bootloader) platform: hTCBmsm8916
(bootloader) modelid: 0PCV20000
(bootloader) cidnum: HTC__052
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cfaddc6b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 1001
Any advice on where i go from here would be good, if anyone has the proper ruu file i need that would be awesome!
Thanks
*note i have no sd card, and no access to one.
Click to expand...
Click to collapse
what service provider do you have?

MrMike2182 said:
what service provider do you have?
Click to expand...
Click to collapse
I'm pretty sure it was Tesco Mobile.

jpno5 said:
I'm pretty sure it was Tesco Mobile.
Click to expand...
Click to collapse
So you're on 64 bit since you're out of the Country. (USA).
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
jpno5 said:
I'm pretty sure it was Tesco Mobile.
Click to expand...
Click to collapse
Who do you make a payment to for service? Because I can't find Tesco mobile on the HTC website.

MrMike2182 said:
So you're on 64 bit since you're out of the Country. (USA).
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
Who do you make a payment to for service? Because I can't find Tesco mobile on the HTC website.
Click to expand...
Click to collapse
It is Tesco mobile, They run on the same network as o2, on htc dev the only reference i could find to tesco was this..
Desire 510
HTC
WWE Tesco
CRC
3.10.28
v4.4.3 441 MB
1.09.1107.1
and yeah i'm assuming its 64bit.

jpno5 said:
It is Tesco mobile, They run on the same network as o2, on htc dev the only reference i could find to tesco was this..
Desire 510
HTC
WWE Tesco
CRC
3.10.28
v4.4.3 441 MB
1.09.1107.1
and yeah i'm assuming its 64bit.
Click to expand...
Click to collapse
Yeah download that to your computer and then relock the phones bootloader by booting the phone into fastboot but first make sure your device is connected by typing fastboot devices and after it pops up some numbers type fastboot oem lock then while still in fastboot and run the ruu that you downloaded and it should return to stock.
Edit: For future reference don't do anything to the phone without an sd card and especially without having a rom to use. You can unlock the bootloader using the same token you got from HTC the first time that way you can root your phone and everything but there is no roms available yet for the 64 bit desire 510 so I'm really lost to why you would wipe your system off like that when you've got nothing to install?

MrMike2182 said:
Yeah download that to your computer and then relock the phones bootloader by booting the phone into fastboot but first make sure your device is connected by typing fastboot devices and after it pops up some numbers type fastboot oem lock then while still in fastboot and run the ruu that you downloaded and it should return to stock.
Edit: For future reference don't do anything to the phone without an sd card and especially without having a rom to use. You can unlock the bootloader using the same token you got from HTC the first time that way you can root your phone and everything but there is no roms available yet for the 64 bit desire 510 so I'm really lost to why you would wipe your system off like that when you've got nothing to install?
Click to expand...
Click to collapse
That file just contained 2 tar files, kernelxxx.tar and platformxxx.tar, the ruu exe i downloaded was for europe wwe i think, it would't install to the phone as the cid never matched. I also locked the bootloader again when trying that.
cheers.
*edit It's not actually my phone, i should have looked into it more, I just grabbed the first rom i seen and basically done what i usually do on my oneplus one. I never imagined there would be an issue like this where im struggling this much to get back from.

jpno5 said:
That file just contained 2 tar files, kernelxxx.tar and platformxxx.tar, the ruu exe i downloaded was for europe wwe i think, it would't install to the phone as the cid never matched. I also locked the bootloader again when trying that.
cheers.
*edit It's not actually my phone, i should have looked into it more, I just grabbed the first rom i seen and basically done what i usually do on my oneplus one. I never imagined there would be an issue like this where im struggling this much to get back from.
Click to expand...
Click to collapse
Go back into fastboot and make sure your device is connected again with fastboot devices and then try this "fastboot flash boot <htc_orginal_ruu>" without the quotes.

MrMike2182 said:
Go back into fastboot and make sure your device is connected again with fastboot devices and then try this "fastboot flash boot <htc_orginal_ruu>" without the quotes.
Click to expand...
Click to collapse
sorry not too clued up on this, am i meant to replace <htc_orginal_ruu> with a filename ?

jpno5 said:
sorry not too clued up on this, am i meant to replace <htc_orginal_ruu> with a filename ?
Click to expand...
Click to collapse
Type it just the way it is if it fails come back and I'll try one more thing that I know of.

MrMike2182 said:
Type it just the way it is if it fails come back and I'll try one more thing that I know of.
Click to expand...
Click to collapse
it says the syntax of the command is incorrect.

jpno5 said:
it says the syntax of the command is incorrect.
Click to expand...
Click to collapse
Ok take that . zip ruu that you downloaded from the HTC website and rename it to just Rom.zip
Go into fastboot and then type
fastboot oem rebootRUU
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder
fastboot flash zip Rom.zip
This takes a couple minutes and you will most likely get a error
(pre-hboot update: please flush immediately)
Make sure device is still in ruu mode(black HTC screen). If not rerun
fastboot oem rebootRUU
now simply reflash the rom.zip
fastboot flash zip Rom.zip
Let it run and it should finish this time
It will reboot to a fully stock build.
just remember, anytime you get a "flush immediately" error, just make sure your still in ruu mode and reflash the zip.
The most common error is typically
(Error 155)
You did not re lock your bootloader first
-go relock and flash again
If this doesn't work it's most likely because of it being the wrong ruu but it's worth a shot.
---------- Post added at 11:55 PM ---------- Previous post was at 11:46 PM ----------
jpno5 said:
it says the syntax of the command is incorrect.
Click to expand...
Click to collapse
You never told me what country you're in.

C:\tools\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.011s]
finished. total time: 0.012s
C:\tools\platform-tools>fastboot flash zip rom.zip
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
C:\tools\platform-tools>fastboot flash zip rom.zip -S0
sending 'zip' (451235 KB)...
OKAY [ 17.525s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 47.056s
i had to add the -S0 to get it to transfer as i was getting that invalid sparse file format. The error now is the signature checking, anyway round that ?
*edit, I'm in the UK.

jpno5 said:
C:\tools\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.011s]
finished. total time: 0.012s
C:\tools\platform-tools>fastboot flash zip rom.zip
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
C:\tools\platform-tools>fastboot flash zip rom.zip -S0
sending 'zip' (451235 KB)...
OKAY [ 17.525s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 47.056s
i had to add the -S0 to get it to transfer as i was getting that invalid sparse file format. The error now is the signature checking, anyway round that ?
*edit, I'm in the UK.
Click to expand...
Click to collapse
it was checking to see if that was the right ruu and it was apparently not right so give me a minute to look for something.
---------- Post added at 12:08 AM ---------- Previous post was at 12:02 AM ----------
jpno5 said:
C:\tools\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.011s]
finished. total time: 0.012s
C:\tools\platform-tools>fastboot flash zip rom.zip
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
C:\tools\platform-tools>fastboot flash zip rom.zip -S0
sending 'zip' (451235 KB)...
OKAY [ 17.525s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 47.056s
i had to add the -S0 to get it to transfer as i was getting that invalid sparse file format. The error now is the signature checking, anyway round that ?
*edit, I'm in the UK.
Click to expand...
Click to collapse
Download this one and either see if it'll work on the computer or if it fails try changing it to Rom.zip again and flashing in fastboot since fastboot avoids some of the checks.
http://dl4.htc.com/RomCode/Source_and_Binaries/a11ul-3.10.28-g72f7e8d.zip

MrMike2182 said:
it was checking to see if that was the right ruu and it was apparently not right so give me a minute to look for something.
---------- Post added at 12:08 AM ---------- Previous post was at 12:02 AM ----------
Download this one and either see if it'll work on the computer or if it fails try changing it to Rom.zip again and flashing in fastboot since fastboot avoids some of the checks.
http://dl4.htc.com/RomCode/Source_and_Binaries/a11ul-3.10.28-g72f7e8d.zip
Click to expand...
Click to collapse
I't wont let me download that link, but by going with the filename, i've already got and tried it, there was 2 on the htc site that i thought would work, a11ul-3.10.28-g72f7e8d.zip, and a11ul-3.10.28-g930be6d.zip
What do you mean by see if it will work on the computer ? the only way i've tried is flashing via fastboot.
Thanks

jpno5 said:
I't wont let me download that link, but by going with the filename, i've already got and tried it, there was 2 on the htc site that i thought would work, a11ul-3.10.28-g72f7e8d.zip, and a11ul-3.10.28-g930be6d.zip
What do you mean by see if it will work on the computer ? the only way i've tried is flashing via fastboot.
Thanks
Click to expand...
Click to collapse
This is a backup of your system that someone else uploaded and I'm not really to sure if you can push this to Philz Touch Recovery so you can restore this one but you can try but first you need to unlock the bootloader again using the same token you had and flash philz touch recovery again and then I'll see if this can be pushed to Philz through adb if that doesn't work your last chance is to simply hold on to this file that I'm giving you then go find an sd card and put this file in the root of the sd card and use Philz to restore it. That's all that can be done at this point so go unlock the bootloader again and then install Philz Touch Recovery again and then download this file and then check back here to see if it can be pushed to Philz without an sd..
File. https://www.dropbox.com/s/yg4q8dy3g4vwhlu/Stock_rom_20150519_082814.zip?dl=0
---------- Post added at 12:48 AM ---------- Previous post was at 12:33 AM ----------
jpno5 said:
I't wont let me download that link, but by going with the filename, i've already got and tried it, there was 2 on the htc site that i thought would work, a11ul-3.10.28-g72f7e8d.zip, and a11ul-3.10.28-g930be6d.zip
What do you mean by see if it will work on the computer ? the only way i've tried is flashing via fastboot.
Thanks
Click to expand...
Click to collapse
If you want to see if you can get that to flash without an sd card you can try..
Again change the zip name to Rom.zip MAKE SURE YOU DELETE ALL THE OTHER ROM.ZIPS YOU MADE BEFORE SO YOU DON'T FLASH THE WRONG ONE!!
Boot up your phone to recovery. Move your ROM file to the adb directory where fastboot is and start a command line prompt.
adb shell
mount data
Ctrl+C
adb push C:\adb\Rom.zip /data/
Wait until the push finishes, and restart your device to recovery again with "adb reboot-bootloader"
Type
mount data
type again exactly what you see
mount /data /sdcard (mount the data folder into your sdcard folder, so your recovery will think that you have an SD card installed)
Locate the ROM .zip file you wish to flash.
Confirm the flash by following the on-screen phone instructions (ie: pressing the power button, etc.)
If no errors arise during the flashing process then the ROM flash was successful. Reboot the device.

I have that file from earlier, i had tried it. For some reason no matter what i try i just can't get adb. It's like 6am here and i've been at this for more than 12 hours straight lol, so time to grab some sleep, if i wake early enough i'll pop into town today and grab an sd card, what do you think the chances of it working are with an sd card? Thanks for your help man, much appreciated.

jpno5 said:
I have that file from earlier, i had tried it. For some reason no matter what i try i just can't get adb. It's like 6am here and i've been at this for more than 12 hours straight lol, so time to grab some sleep, if i wake early enough i'll pop into town today and grab an sd card, what do you think the chances of it working are with an sd card? Thanks for your help man, much appreciated.
Click to expand...
Click to collapse
With an sd card 100% and yeah it's 1am over here I stayed up way past my bedtime.
---------- Post added at 12:59 AM ---------- Previous post was at 12:56 AM ----------
jpno5 said:
I have that file from earlier, i had tried it. For some reason no matter what i try i just can't get adb. It's like 6am here and i've been at this for more than 12 hours straight lol, so time to grab some sleep, if i wake early enough i'll pop into town today and grab an sd card, what do you think the chances of it working are with an sd card? Thanks for your help man, much appreciated.
Click to expand...
Click to collapse
adb is supposed to be on your computer in the same spot fastboot is and if it's not then just download the mini adb and fastboot that's all you need on the computer.
If you don't have adb working then that's why everything we're doing isn't working because it needs adb and fastboot.

Adb just doesn't seem to be a feature on this 64bit model, i tried everything man, every driver i could find, the phone just wouldn't expose the interface.
Anyway, popped into town today and bought a 2gb sd card, got home and realised i had no way of plugging it into the computer so after another trip to town lol i managed to transfer that stock install over and flash it and it seems to be fine. I've not had a sim card in it yet to check it calls out. Thanks for your help man, its much appreciated.

jpno5 said:
Adb just doesn't seem to be a feature on this 64bit model, i tried everything man, every driver i could find, the phone just wouldn't expose the interface.
Anyway, popped into town today and bought a 2gb sd card, got home and realised i had no way of plugging it into the computer so after another trip to town lol i managed to transfer that stock install over and flash it and it seems to be fine. I've not had a sim card in it yet to check it calls out. Thanks for your help man, its much appreciated.
Click to expand...
Click to collapse
I told you 100% with an sd card!
---------- Post added at 03:04 PM ---------- Previous post was at 02:50 PM ----------
jpno5 said:
Adb just doesn't seem to be a feature on this 64bit model, i tried everything man, every driver i could find, the phone just wouldn't expose the interface.
Anyway, popped into town today and bought a 2gb sd card, got home and realised i had no way of plugging it into the computer so after another trip to town lol i managed to transfer that stock install over and flash it and it seems to be fine. I've not had a sim card in it yet to check it calls out. Thanks for your help man, its much appreciated.
Click to expand...
Click to collapse
By the way adb is working on your phone because If it wasn't you wouldn't have been able to install a recovery period or unlock the bootloader... I think you're just confused with fastboot and adb..

Out of Options and Ideas - Need Help Please [Boot Loop][Soft Brick][Solved!]

*UPDATE*: The issue has been resolved. Read through for more details.
So I plug my HTC One (Model: HTC6500L) into my PC to transfer some SSL certifications to my phone. However, before I can manage that HTC Sync says Verizon has an update for me, which I found odd anyway. Against my better judgment I go ahead and try updating. Phone restarts multiple times during the update, nothing abnormal. I check back on Sync's progress once I notice my phones not loading the update anymore and it says it failed. Now whenever I power my phone on it goes through the htc android white screen and then . . . does nothing. It just stays on a black screen until I force power it off, which actually just makes it reboot and do the same thing (looping). Here's the kicker, my PC no longer recognizes my phone and the recovery and factory reset options in the bootloader don't work. I've erased my cache and formatted it from a half working recovery screen, but it won't actually recover anything.
So, my question is can I somehow recover my phone to factory settings using fastboot that I'm not aware of? My bootloader is locked and it's a VZW phone so yea. It's also running HBOOT 1.61. I'd be more than happy to use sunshine, but I'm under the impression that the phone has to be usable before I can use sunshine to unlock my bootloader. The phone was completely stock before this.
Not sure it helps any but I can contact my phone using fastboot usb and here is the getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.13.41.1209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.22.605.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA37HS915851
(bootloader) imei: 990004280452313
(bootloader) meid: 99000428045231
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4342mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.101s
I'm open to any ideas you guys may have, or something that I may be missing.

TGblaQk said:
So I plug my HTC One (Model: HTC6500L) into my PC to transfer some SSL certifications to my phone. However, before I can manage that HTC Sync says Verizon has an update for me, which I found odd anyway. Against my better judgment I go ahead and try updating. Phone restarts multiple times during the update, nothing abnormal. I check back on Sync's progress once I notice my phones not loading the update anymore and it says it failed. Now whenever I power my phone on it goes through the htc android white screen and then . . . does nothing. It just stays on a black screen until I force power it off, which actually just makes it reboot and do the same thing (looping). Here's the kicker, my PC no longer recognizes my phone and the recovery and factory reset options in the bootloader don't work. I've erased my cache and formatted it from a half working recovery screen, but it won't actually recover anything.
So, my question is can I somehow recover my phone to factory settings using fastboot that I'm not aware of? My bootloader is locked and it's a VZW phone so yea. It's also running HBOOT 1.61. I'd be more than happy to use sunshine, but I'm under the impression that the phone has to be usable before I can use sunshine to unlock my bootloader. The phone was completely stock before this.
Not sure it helps any but I can contact my phone using fastboot usb and here is the getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.13.41.1209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.22.605.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA37HS915851
(bootloader) imei: 990004280452313
(bootloader) meid: 99000428045231
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4342mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.101s
I'm open to any ideas you guys may have, or something that I may be missing.
Click to expand...
Click to collapse
Flash the 6.22.605.6 ruu https://www.androidfilehost.com/?fid=24367857647222996.
Instructions how to flash in the general section. see the ruu collection thread (sticky thread)
Sent from my HTC One using XDA Labs

alray said:
Flash the 6.22.605.6 ruu <Link>
Instructions how to flash in the general section. see the ruu collection thread (sticky thread)
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Sounds great, but your link is dead.

TGblaQk said:
Sounds great, but your link is dead.
Click to expand...
Click to collapse
It's a copy/paste problem remove the last dot in the link or Just go on androidfilehost.com and do a search for 6.22.605.6 and download the file that is 1.4gb
Sent from my HTC One using XDA Labs

alray said:
It's a copy/paste problem remove the last dot in the link or Just go on androidfilehost.com and do a search for 6.22.605.6 and download the file that is 1.4gb
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Lol, I was actually doing just that search, but there were a few so I was unsure. However, the copy/pasting link worked. Thanks!
I'll update later and letcha know how it turns out.
Edit: So I've made it all the way to c:\adb\fastboot flash zip RUU.zip and it throws this:
Code:
error: preprocess_file : Cannot open file RUU.zip
I downloaded the file you linked me, didn't extract it, just renamed it to RUU and threw it into my adb folder. Also, yes I'm using htc_fastboot, just didn't rename it. However the first command oem rebootRUU did work and now my phone is just displaying a black screen with htc on it.

TGblaQk said:
Lol, I was actually doing just that search, but there were a few so I was unsure. However, the copy/pasting link worked. Thanks!
I'll update later and letcha know how it turns out.
Edit: So I've made it all the way to c:\adb\fastboot flash zip RUU.zip and it throws this:
Code:
error: preprocess_file : Cannot open file RUU.zip
I downloaded the file you linked me, didn't extract it, just renamed it to RUU and threw it into my adb folder. Also, yes I'm using htc_fastboot, just didn't rename it. However the first command oem rebootRUU did work and now my phone is just displaying a black screen with htc on it.
Click to expand...
Click to collapse
Can you post a screen shot of your command window and a screenshot of what's inside your c:/adb folder?
When youve renamed the file to "ruu" did you add "ruu.zip" or just "ruu" ? If youve type "ruu.zip" then your file name is now RUU.zip.zip (double file extension). Windows is hiding file extension for known file type by default. In the command windows, try to type "fastboot flash zip RUU" then hit your TAB key and it should auto-complete the file name.
If you need to exit RUU mode you can simply use "fastboot reboot-bootlaoder" to go back in booloader or "fastboot power off" to turn off the phone.

alray said:
Can you post a screen shot of your command window and a screenshot of what's inside your c:/adb folder?
When youve renamed the file to "ruu" did you add "ruu.zip" or just "ruu" ? If youve type "ruu.zip" then your file name is now RUU.zip.zip (double file extension). Windows is hiding file extension for known file type by default. In the command windows, try to type "fastboot flash zip RUU" then hit your TAB key and it should auto-complete the file name.
If you need to exit RUU mode you can simply use "fastboot reboot-bootlaoder" to go back in booloader or "fastboot power off" to turn off the phone.
Click to expand...
Click to collapse
Sure! Attached both screenshots.
At first I did make the mistake of adding .zip when I renamed it. When it failed the first time, it clicked; "You idiot, you just named that file RUU.zip.zip . . . " and so I changed it to just RUU. However, as you see it failed again.
Edit: Hitting TAB didn't finish the extension. ._.

TGblaQk said:
Sure! Attached both screenshots.
At first I did make the mistake of adding .zip when I renamed it. When it failed the first time, it clicked; "You idiot, you just named that file RUU.zip.zip . . . " and so I changed it to just RUU. However, as you see it failed again.
Edit: Hitting TAB didn't finish the extension. ._.
Click to expand...
Click to collapse
Was the md5 value good?
It should be 574ed7acdcf77263ac60943e2f001d2a
Try to type "fastboot flash zip " then drag the RUU.zip file and drop it to your command window and hit enter

alray said:
Was the md5 value good?
It should be 574ed7acdcf77263ac60943e2f001d2a
Try to type "fastboot flash zip " then drag the RUU.zip file and drop it to your command window and hit enter
Click to expand...
Click to collapse
Well either what you suggested worked or what I did worked. I dragged and dropped it like you said, but since I was clearly specifying the location before, that shouldn't have made a difference.
So here is what I did; since you mentioned the md5 value I just wanted to check the properties of said file to see if anything was out of the ordinary (never checked the md5 btw). That's when I noticed under the "General" tab in "Properties" at the bottom next to "Security" it states the following:
Code:
This file came from another computer and might be blocked to help protect this computer.
This is followed by a checkbox that says "Unblock". I'm attaching a screenshot just for visual reference of what I'm describing. Finished following the guide, rebooted to bootloader, then rebooted. Currently in the middle of the upgrading process.
Again, thanks for all your help, and maybe I've contributed a bit as well. Not sure if that security feature is a default setting for everyone or not, but it's nice to have documentation of it!
Final update: After rebooting and as the phone was optimizing apps, the UI failed (SIM wasn't inserted at the time). So I basically just had a tablet. Powered it down, inserted SIM ran factory reset again and now my phone is functioning at 110%!
Again, big thanks to alray for his guidance and support along the way.