Related
HERO XC SHIP S-OFF
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.41.05.02.99
Mar 1 2010, 16:02:39
RUU
This is what happened after i installed the latest ruu htc_sprint_hero_mr_2.27.651.6.exe
Error 110 open file error
a black screen is appeared first then after plugin the usb the server HTC logo appears and when i disconnect it
This appears
HERO XC SHIP S-OFF
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.41.05.02.99
Mar 1 2010, 16:02:39
RUU
i cant use the HBoot , by any of the method s
and cant use recovery mod , flashing using flashboot or ADB ,
but i can open my phone by using flashboot oem boot
but its troubling whenever the battery is down i have to open it again using computer
here is the problem while flashing using fastboot
fastboot flash radio radio1.img
sending 'radio' (21376 KB)...
OKAY [ 24.089s]
writing 'radio'...
FAILED (remote: image type not support)
finished. total time: 24.108s
or here when i use flash the zip
fastboot flash zip update.zip
sending 'zip' (118067 KB)...
OKAY [129.171s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 132.015s
why does the (remote: image type not support) or the (remote: 24 parsing android-info fail) appear
> fastboot devices
HT9BEHF03035 fastboot
and when i used this command
>fastboot flash zip HERCIMG.zip
sending 'zip' (114210 KB)...
OKAY [129.813s]
writing 'zip'...
its stuck on writing 'zip' and havent done anything for more than 20 min , whats wrong here ??!!
Can anybody help please :crying::crying::crying::crying::crying:
Try flashing this img found here http://forum.xda-developers.com/showpost.php?p=9944755&postcount=9
hope it helps. it is the hercimg in zip format to install directly on your phone.
jamstewonline said:
Try flashing this img found here http://forum.xda-developers.com/showpost.php?p=9944755&postcount=9
hope it helps. it is the hercimg in zip format to install directly on your phone.
Click to expand...
Click to collapse
I cant follow this instruction
Press and hold your Volume Down button, and while still holding it press the power button to power your phone back up into HBoot mode.
because I cant enter HBoot by any method
I've tried a number of different combinations to get my HTC One running on a custom ROM, and none of them seem to work.
S-ON
HBOOT=1.56.0000
Click to expand...
Click to collapse
I've tried using both TWRP and CWM, and tried installing both the latest Viper and Bad Boyz roms. Regardless, installation completes successfully (apparently) and the phone reboots. It gets past the loading screen, then to a locked home screen. Upon unlock, all I see is a white screen with the HTC logo.
Sometimes, I'll get a dialog with the following error:
Process com.htc.htcdialer isn't responding
Click to expand...
Click to collapse
The phone then reboots itself, and the cycle begins again.
I will happily through a beer, coffee, or other beverage of choice (or equivalent) to whomever is able to help me out. Thank you!
You did do a full wipe in recovery correct? I've flashed both of those no problem.
Sent from my HTCONE using Tapatalk
Bairdog35 said:
You did do a full wipe in recovery correct? I've flashed both of those no problem.
Click to expand...
Click to collapse
I have, yes. Does not appear to make a difference, unfortunately. Performed full wipes, made sure to wipe both caches upon install, still stuck.
kadjar said:
I have, yes. Does not appear to make a difference, unfortunately. Performed full wipes, made sure to wipe both caches upon install, still stuck.
Click to expand...
Click to collapse
You are using a Sprint HTC one correct? May be a stupid question for me to ask, but you'd be surprised how easily people get lost here!
Sent from my HTCONE using Tapatalk
Bairdog35 said:
You are using a Sprint HTC one correct? May be a stupid question for me to ask, but you'd be surprised how easily people get lost here!
Click to expand...
Click to collapse
I am indeed I appreciate you making sure! I can't help but wonder if I did something similarly dumb to bungle this thing.
kadjar said:
I am indeed I appreciate you making sure! I can't help but wonder if I did something similarly dumb to bungle this thing.
Click to expand...
Click to collapse
You are in a pickle haha, this is what I would do. If your phone is not in a working state, RUU back to stock, then unlock the boot loader again, flash TWRP recovery, try flashing your Rom of choice. I bet after that process your Rom will boot and run just fine.
Sent from my HTCONE using Tapatalk
Bairdog35 said:
You are in a pickle haha, this is what I would do. If your phone is not in a working state, RUU back to stock, then unlock the boot loader again, flash TWRP recovery, try flashing your Rom of choice. I bet after that process your Rom will boot and run just fine.
Click to expand...
Click to collapse
Darn. Do you happen to know if there's any way to RUU on a mac? Everything I've seen so far seems to utilize a .exe
I would also re-download your ROM/S you wish to try, it's amazing how easily an error can come from the download itself and not show up until it's flashed
Process of Elimination.
Bashing away at my HTC Desire C
kadjar said:
I've tried a number of different combinations to get my HTC One running on a custom ROM, and none of them seem to work.
I've tried using both TWRP and CWM, and tried installing both the latest Viper and Bad Boyz roms. Regardless, installation completes successfully (apparently) and the phone reboots. It gets past the loading screen, then to a locked home screen. Upon unlock, all I see is a white screen with the HTC logo.
Sometimes, I'll get a dialog with the following error:
The phone then reboots itself, and the cycle begins again.
I will happily through a beer, coffee, or other beverage of choice (or equivalent) to whomever is able to help me out. Thank you!
Click to expand...
Click to collapse
try reflashing the latest radio with twrp recovery, you can find them in flashable zips here in the threads.
kadjar said:
Darn. Do you happen to know if there's any way to RUU on a mac? Everything I've seen so far seems to utilize a .exe
Click to expand...
Click to collapse
Man this is just not your day haha
Download this http://www.androidfilehost.com/?fid=23329332407573774
Unzip it, you will find Rom.zip inside the folder.
I'm assuming you have fastboot working on your Mac
Reboot your phone into boot loader, select fastboot, plug into Mac.
Make sure you relock your boot loader.
Move that Rom.zip into the folder that fastboot is found on mac.
Type the following commands
1. fastboot oem rebootRUU
2. fastboot flash zip rom.zip
3. fastboot flash zip rom.zip
4. fastboot reboot
Yes you need to do fastboot flash zip Rom.zip twice, it will fail the first time.
Let it do its thing then reboot. You should have your phone back to stock!
Sent from my HTCONE using Tapatalk
Followed your instructions, but it seems to be failing (more than once)
Any guesses as to what I'm doing wrong?
Code:
➜ platform-tools ./fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
ERROR: usb_read failed with status e00002c0
FAILED (status read failed (No such file or directory))
finished. total time: 1.131s
➜ platform-tools ./fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.035s]
finished. total time: 0.035s
➜ platform-tools ./fastboot flash zip /Users/garrett/Dev/android/stock.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 120085191 is not a multiple of the block size 4096
sending sparse 'zip' (1476856 KB)...
error: write_sparse_skip_chunk: don't care size 120085191 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 120085191 is not a multiple of the block size 4096
OKAY [ 86.741s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 237.804s
➜ platform-tools ./fastboot flash zip /Users/garrett/Dev/android/stock.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 124279495 is not a multiple of the block size 4096
sending sparse 'zip' (1478186 KB)...
error: write_sparse_skip_chunk: don't care size 124279495 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 124279495 is not a multiple of the block size 4096
OKAY [ 70.744s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 222.003s
➜ platform-tools ./fastboot flash zip /Users/garrett/Dev/android/stock.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 128047815 is not a multiple of the block size 4096
sending sparse 'zip' (1476924 KB)...
error: write_sparse_skip_chunk: don't care size 128047815 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 128047815 is not a multiple of the block size 4096
OKAY [ 69.791s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 220.860s
Your fastboot exe may be bad, try installing from this thread - http://forum.xda-developers.com/showthread.php?t=2588979
Bairdog35 said:
Man this is just not your day haha
Download this http://www.androidfilehost.com/?fid=23329332407573774
Unzip it, you will find Rom.zip inside the folder.
I'm assuming you have fastboot working on your Mac
Reboot your phone into boot loader, select fastboot, plug into Mac.
Make sure you relock your boot loader.
Move that Rom.zip into the folder that fastboot is found on mac.
Type the following commands
1. fastboot oem rebootRUU
2. fastboot flash zip rom.zip
3. fastboot flash zip rom.zip
4. fastboot reboot
Yes you need to do fastboot flash zip Rom.zip twice, it will fail the first time.
Let it do its thing then reboot. You should have your phone back to stock!
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
You, sir, I owe a beer. Back up and running on stock, managed to root stock as well. PM me your paypal?
kadjar said:
You, sir, I owe a beer. Back up and running on stock, managed to root stock as well. PM me your paypal?
Click to expand...
Click to collapse
Seems you found it, thank you greatly. If you need anything, don't be afraid to pm me
Sent from my HTCONE using Tapatalk
Htc one A9 firmware flashing problem
htc one a9 (model: 2PQ9100) see the error below i'm facing please help me i am very upset :crying:
C:\adb>fastboot oem rebootRUU
...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1166400000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 617001178 is not a multiple of the block size 4096
sending sparse 'zip' (1139061 KB)...
error: write_sparse_skip_chunk: don't care size 617001178 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 617001178 is not a multiple of the block size 4096
OKAY [ 53.554s]
writing 'zip'...
(bootloader) HOSD CL#853511
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_z
(bootloader) EOonp
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 91.572s
First thing I would do is get a fresh download of the RUU update and try that.
Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?
YOUNG MAN. said:
Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?
Click to expand...
Click to collapse
Try to use the mfastboot, because the system.img is to big to use the normal fastboot
libnijunior said:
Try to use the mfastboot, because the system.img is to big to use the normal fastboot
Click to expand...
Click to collapse
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s
YOUNG MAN. said:
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s
Click to expand...
Click to collapse
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.
juliospinoza said:
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.
Click to expand...
Click to collapse
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx
YOUNG MAN. said:
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx
Click to expand...
Click to collapse
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
Yes, they are synonyms. I would install Motorola Device Manager to your PC and let it attempt to repair your phone.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
If it doesn't repair your phone, post back here.
YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager, what should i do next?
JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager and tried again, it still did't work.
code:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s
YOUNG MAN. said:
I installed Motorola Device Manager and tried again, it still did't work.
Click to expand...
Click to collapse
Did it detect your device at all? Did it try to repair it?
YOUNG MAN. said:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s
Click to expand...
Click to collapse
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
http://rootjunkysdl.com/?device=Adb Fastboot Files
Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095
JulesJam said:
Did it detect your device at all? Did it try to repair it?
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
Click to expand...
Click to collapse
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed
YOUNG MAN. said:
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed
Click to expand...
Click to collapse
Did you try RSDLite?
JulesJam said:
Did you try RSDLite?
Click to expand...
Click to collapse
it can't detect my phone
YOUNG MAN. said:
it can't detect my phone
Click to expand...
Click to collapse
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.
JulesJam said:
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.
Click to expand...
Click to collapse
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60
YOUNG MAN. said:
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60
Click to expand...
Click to collapse
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.
JulesJam said:
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.
Click to expand...
Click to collapse
it shows this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
device
dustin_b said:
Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095
Click to expand...
Click to collapse
NO,my recovery is TWRP now ,and I can't flash the original recovery ,it failed.
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
GuardianUSMC said:
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
Click to expand...
Click to collapse
No, you cannot ad root to the image before flashing.
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
gee2012 said:
No, you cannot ad root to the image before flashing.
Click to expand...
Click to collapse
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
Click to expand...
Click to collapse
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
GuardianUSMC said:
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
Click to expand...
Click to collapse
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
gee2012 said:
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
Click to expand...
Click to collapse
Got it, thank you very much for your assistance.
Too bad the Factory Images from Google are not already rooted.
GuardianUSMC said:
So the factory images provided directly by Google are NOT at root already either?
Click to expand...
Click to collapse
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
So for example on a linux machine you will have the root directory:
/
Within root, you will have other directories such as:
/bin
/etc
/usr
See here for more information:
http://www.thegeekstuff.com/2010/09/linux-file-system-structure/
So root is kind of like the C:\ drive on a Windows PC. Everything to do with the OS and User directories are within there.
Your Android device is the same, however, /bin, /etc (etc) are not at the root of the device. They sit within the system partition, which sits within root. so /system/bin, /system/etc. When you flash a factory image, it flashes the images to /system, /cache, /userdata (and a few other places) where as the root of the device remains largely untouched.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
@rootSU,
Excellent mini tutorial. I wish this could be stickied on the General roll up thread. Thank you very much.
rootSU said:
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
Click to expand...
Click to collapse
I appreciate that and forgive me I know I used the terms interchangeably and that's my bad.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
Click to expand...
Click to collapse
yes I am familiar with that and I was using the term to mean having root privileges, again my bad.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
Click to expand...
Click to collapse
Understood, I have done that and my device is currently rooted. I was more looking into making an image that is already rooted, to borrow a term from Windows, slipstream the root functionality pre-flashing. I was told not going to happen, that's fine. Although when I had my HTC Evo 4G, I had pre-rooted images that I had created with the bloat removed and I was flashing them with root functionality out of the box, but that's another story, I guess Nexus 6 is a different animal and dealing with Lollipop probably more difficult than Gingerbread.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
Click to expand...
Click to collapse
No but I appreciate you taking the time, thank you.
Right now mostly I am frustrated with the fact that the factory images provided by google will not flash right and keep *****ing about missing .sig files. I have tried flashing them individually by taking the root, system, recovery images out of the zip file and doing them individually as been suggested all over the place but no luck there there, keeps *****ing about the partitions instead, makes no sense. The bootloader and radio images go through without a hitch but the rest is just a mess.
Just to share, I am trying to flash the factory image that I mentioned in my original post, so I won't repost it. Here is what did so far to no avail, so any assistance would be greatly appreciated:
I issue the command adb reboot bootloader and it successful reboots the phone into the bootloader
Extracting the folder shamu-lmy47i containing the following files:
bootloader-shamu-moto-apq8084-71.08.img
flash-all.bat
flash-all.sh
flash-base.sh
image-shamu-lmy47i.zip
radio-shamu-d4.0-9625-02.95.img
Opening the batch file you see the following (I have removed the copyright header for sake of brevity)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
echo Press any key to exit...
pause >nul
exit
Since the only thing I want to add to this is root, I add this after the image update:
Code:
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
So we let it rip and this is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.548s]
finished. total time: 0.674s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.720s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.102s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
downloading 'boot.img'...
OKAY [ 0.393s]
booting...
OKAY [ 0.024s]
finished. total time: 0.419s
Press any key to exit...
As we can see, bootloader image flashes just fine
The radio image flashes just fine
System image on the other hand does not update complaining about missing .sig files:
fastboot -w update image-shamu-lmy47i.zip said:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
Click to expand...
Click to collapse
The files inside this system zip are:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Ironically the SuperSU image flashes just fine and reboots the phone
I am frustrated by the fact that the system image update step fails and nothing out there explains why? I have even tried to extract each of those images from the zip file and flashing them individually using the fastboot flashall but getting the same error as well as other errors.
Can anyone lend an assist on this and help me figure out how to overcome that hurdle PLEASE?
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Evolution_Freak said:
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Click to expand...
Click to collapse
I did provide everything step by step the only thing I didn't provide was the errors on the individual images that are within the update zip file. Which I suppose is my bad:
Code:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
and I have tried flashall last because documentation states it will do boot, recovery and system but I have also done them using individual commands too. But more on that after I take a look at what you posted in the link. Stay tuned. Thank you.
Alright, good news, it worked and thank you for pointing to the resource that allowed me to figure out why I was getting the partition errors, now I know.
I modified the batch file as follows:
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
adb reboot bootloader
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
echo Press any key to exit...
pause >nul
exit
it went through the whole process and here is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.508s]
finished. total time: 0.632s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.722s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.110s]
finished. total time: 3.834s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
target reported max download size of 536870912 bytes
sending sparse 'system' (522196 KB)...
OKAY [ 22.442s]
writing 'system'...
OKAY [ 7.691s]
sending sparse 'system' (510114 KB)...
OKAY [ 21.723s]
writing 'system'...
OKAY [ 6.674s]
sending sparse 'system' (514997 KB)...
OKAY [ 21.128s]
writing 'system'...
OKAY [ 7.778s]
sending sparse 'system' (189177 KB)...
OKAY [ 7.652s]
writing 'system'...
OKAY [ 2.328s]
finished. total time: 97.428s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 11.844s]
sending 'userdata' (138868 KB)...
OKAY [ 4.518s]
writing 'userdata'...
OKAY [ 1.949s]
finished. total time: 18.315s
target reported max download size of 536870912 bytes
sending 'boot' (7681 KB)...
OKAY [ 0.247s]
writing 'boot'...
OKAY [ 0.110s]
finished. total time: 0.359s
target reported max download size of 536870912 bytes
sending 'recovery' (8273 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.116s]
finished. total time: 0.384s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.013s]
sending 'cache' (6248 KB)...
OKAY [ 0.204s]
writing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.318s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.399s]
booting...
OKAY [ 0.035s]
finished. total time: 0.436s
Thank you for everyone's input and assistance here, you rock.
Hello, am new at this, but I really need some assistance, I wipe my M7 but I cannot reinstall a new rom, first my computer said that it cannot find the android 1.0 driver, I try using pdanet but requested me to active the debugging option that is inside the OS but i dont have one, can someone help, also I try to send a file from my computer to the device but keeps saying it cant, am assuming cause the driver failure, I already have TWRP, unlocked and superus, can someone guide me, also am not that smart if you please keep simply instruction will be great, appreciated
adrianponce said:
Hello, am new at this, but I really need some assistance, I wipe my M7 but I cannot reinstall a new rom, first my computer said that it cannot find the android 1.0 driver, I try using pdanet but requested me to active the debugging option that is inside the OS but i dont have one, can someone help, also I try to send a file from my computer to the device but keeps saying it cant, am assuming cause the driver failure, I already have TWRP, unlocked and superus, can someone guide me, also am not that smart if you please keep simply instruction will be great, appreciated
Click to expand...
Click to collapse
Usb debugging is only needed to get adb commands working from a booted OS. You don't need to have USB Debugging turned on to use adb commands from TWRP. Anyway pdanet will not work from twrp...
You'll need to install the right drivers so you can use adb commands (form TWRP) and fastboot commands (from bootloader) to fix your phone.
Download and install the latest driver version for HTC: http://www.mediafire.com/download/1ulx1xl5k1zhk5j/HTC_Driver_4.17.0.001.exe
Once done, connect your phone to your computer and reboot it in bootloader mode. Make sure that you can see "fastboot usb" highlighted in red (like in this picture). If yes, open a command window from your computer adb/fastboot folder and type "fastboot getvar all" (without the quotes) and hit enter. Copy/paste the output here so we can know a little more about your phone and how to help you get the correct rom on it (remove your IMEI and SERIALNO before posting).
Btw do you want it to run a stock or custom rom? What is your TWRP version?
"alray" I download the drivers and install them, I connected the phone in fastboot and is highlighted red with the usb as well, I open the command center and type "fastboot getvar all", but it says waiting for any device, and stays there does not do anything, I wait almost 30 minutes and nothing, am i doing something wrong?, thanks
apparently even after installing the drivers, the device manager still not recognize my phone, although in the fastboot bootloader says usb, I do not know how to insert and image about my device manager, phone and installation programs, sorry
"alray", finally got it, is used this link http://forum.xda-developers.com/showthread.php?p=48915118#post48915118, version 1.3, and drivers were installed correctly, this is the information you requested me,
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.1540.51
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4289mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-46c17580
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.180s
Regarding the rom, I dont have any preference, I even not know the difference, can you recommend me one?, and TWRP version 3.0.2-0, now what would be the next step?, thanks
@alray [alray][/alray], which rom should I install and how, I try to download htc gen unlock, dev edition unlock, and once connected to the phone in fastboot usb, using command fastboot update "*.zip (zip file I download)", but says that "error: update package 'C:\fastboot\m7wlv-3.4.10-g7875f0c.zip' has no android-info.txt", should I install a different one?, thanks
@alray [alray][/alray], which rom should I install and how, I try to download htc gen unlock, dev edition unlock from http://www.htcdev.com/devcenter/downloads, and once connected to the phone in fastboot usb, using command fastboot update "*.zip (zip file I download)", but says that "error: update package 'C:\fastboot\m7wlv-3.4.10-g7875f0c.zip' has no android-info.txt", should I install a different one?, thanks
adrianponce said:
@alray [alray][/alray], which rom should I install and how, I try to download htc gen unlock, dev edition unlock from http://www.htcdev.com/devcenter/downloads, and once connected to the phone in fastboot usb, using command fastboot update "*.zip (zip file I download)", but says that "error: update package 'C:\fastboot\m7wlv-3.4.10-g7875f0c.zip' has no android-info.txt", should I install a different one?, thanks
Click to expand...
Click to collapse
This file is not for your phone, better to delete it you'll not need it.
I would suggest that you flash a RUU, this will get back your phone to the stock rom. The process is a little different from flashing a rom from TWRP but imo, the result is better.
download htc_fastboot.exe and save it in the same folder where you already have adb.exe and fastboot.exe
Download this RUU and save it in the same folder where you already have adb.exe, fastboot.exe and htc_fastboot.exe
Note that there is currently maintenance on the website hosting these files, if you can't download the files wait a few hours and try again.
Connect your phone to your computer, reboot it in bootloader mode and make sure "fastboot usb" is highlighted in red
Start a command window from your adb/fastboot folder
Type:
Code:
fastboot oem rebootRUU
Your phone will reboot in RUU mode, a black screen with silver HTC logo.
Type
Code:
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
Wait for the file to be flashed (it will take several minutes).
Once the RUU is sucesfully flashed reboot the phone using this command:
Code:
fastboot reboot
Note that the first boot after flashing a RUU can take a little more time than usual.
Btw sorry for the delay, got a problem here just after replying to your PM.
alray said:
This file is not for your phone, better to delete it you'll not need it.
I would suggest that you flash a RUU, this will get back your phone to the stock rom. The process is a little different from flashing a rom from TWRP but imo, the result is better.
download htc_fastboot.exe and save it in the same folder where you already have adb.exe and fastboot.exe
Download this RUU and save it in the same folder where you already have adb.exe, fastboot.exe and htc_fastboot.exe
Note that there is currently maintenance on the website hosting these files, if you can't download the files wait a few hours and try again.
Connect your phone to your computer, reboot it in bootloader mode and make sure "fastboot usb" is highlighted in red
Start a command window from your adb/fastboot folder
Type:
Code:
fastboot oem rebootRUU
Your phone will reboot in RUU mode, a black screen with silver HTC logo.
Type
Code:
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
Wait for the file to be flashed (it will take several minutes).
Once the RUU is sucesfully flashed reboot the phone using this command:
Code:
fastboot reboot
Note that the first boot after flashing a RUU can take a little more time than usual.
Btw sorry for the delay, got a problem here just after replying to your PM.
Click to expand...
Click to collapse
@alray, problem for the time you are the one helping me, this is what the command center gave me after I fallow your instructions
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.031s]
finished. total time: 0.031s
C:\fastboot>fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.
51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
FAILED (data transfer failure (Unknown error))
finished. total time: 7.361s
What should I do?
@alray, I did it again a few time and like twice change the notification to the follow
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.042s]
finished. total time: 0.043s
C:\fastboot>fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.
51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
OKAY [ 65.303s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 65.507s
adrianponce said:
@alray, I did it again a few time and like twice change the notification to the follow
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.042s]
finished. total time: 0.043s
C:\fastboot>fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.
51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
OKAY [ 65.303s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 65.507s
Click to expand...
Click to collapse
Sorry my bad, the command is
Code:
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.
51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
Note that the difference is "htc_fastboot" instead of "fastboot"
Sent from my HTC One using XDA Labs
adrianponce said:
Hello, am new at this, but I really need some assistance, I wipe my M7 but I cannot reinstall a new rom, first my computer said that it cannot find the android 1.0 driver, I try using pdanet but requested me to active the debugging option that is inside the OS but i dont have one, can someone help, also I try to send a file from my computer to the device but keeps saying it cant, am assuming cause the driver failure, I already have TWRP, unlocked and superus, can someone guide me, also am not that smart if you please keep simply instruction will be great, appreciated
Click to expand...
Click to collapse
Hello bud. I'm quiet experienced with the HTC One (M7) and would be more the happy to help you with your issue. Are you trying to update to the latest HTC firmware or lollipop?
¤-TIP FROM THE NOOB-¤-¤-
1. enable USB Debugging before flashing custom recovery.
2. back up system before granting apk's root permission, editing system files, and flashing a new rom.
? better safe than sorry ?
?May the Angels lead your way Tom (Tony Stark) . You will be missed bud ?
Tony the noob :D said:
Hello bud. I'm quiet experienced with the HTC One (M7) and would be more the happy to help you with your issue. Are you trying to update to the latest HTC firmware or lollipop?
¤-TIP FROM THE NOOB-¤-¤-
1. enable USB Debugging before flashing custom recovery.
2. back up system before granting apk's root permission, editing system files, and flashing a new rom.
? better safe than sorry ?
?May the Angels lead your way Tom (Tony Stark) . You will be missed bud ?
Click to expand...
Click to collapse
Glad you are joining the discussion cause I'll eventually leave to work. OP should be able to flash the RUU with your help, just forgot to mention that he/she had to use htc_fastboot for flashing the RUU hence the "Invalid sparse file format" error (See post above yours).
Btw no offense intended but I think tip #1 is leading to confusion. USB debugging is not required to flash a custom recovery nor it is required to use adb from recovery. USB debugging is only enabling ADB access from a booted rom...:good:
alray said:
Glad you are joining the discussion cause I'll eventually leave to work. OP should be able to flash the RUU with your help, just forgot to mention that he/she had to use htc_fastboot for flashing the RUU hence the "Invalid sparse file format" error (See post above yours).
Btw no offense intended but I think tip #1 is leading to confusion. USB debugging is not required to flash a custom recovery nor it is required to use adb from recovery. USB debugging is only enabling ADB access from a booted rom...:good:
Click to expand...
Click to collapse
I know. Just been told. Sudo fastboot flash recovery.img is needed to flash it. I'm pro HTC and never found the reason why to enable it in system settings
Sent from my latest and greatest HTC One M7 UL
-¤-¤-TIP FROM THE NOOB-¤-¤-
1. enable USB Debugging before flashing custom recovery.
2. Create system back-up before granting apk's root permission, editing system files, and flashing a new rom.
? better safe than sorry ?
?May the Angels lead your way Tom (Tony Stark) . You will be missed bud ?
@alray @Tony the noob :D, first thanks for your help, just want to mention that I run the htc_fastboot,
C:\fastboot>htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.1
401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 7.19.401.51
found large-zip header, file count: 5
processing file 1/5...
But it stock there, been like 30 minutes, and my phone got out of the HTC gray logo, and now is in the white screen loader, but instead of saying fastboot and all that stuff, only says RUU, is that ok?
@alray @Tony The noob ,after cleaning the cache and try it again this is the notification
C:\fastboot>htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.
401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 7.19.401.51
found large-zip header, file count: 5
processing file 1/5...
sending 'zip' (50228 KB)...
OKAY [ 3.136s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 4.900s
preupdate done, rebooting...
resending command...
sending 'zip' (50228 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 10.441s
htc_fastboot finished. total time: 26.124s
@alray @Tony the noob :D, after trying few time more, finally I could, I just want to say appreciated for all the directions you gave me.
adrianponce said:
@alray @Tony the noob :D, after trying few time more, finally I could, I just want to say appreciated for all the directions you gave me.
Click to expand...
Click to collapse
Good to hear that. If you need any other assistance, please post or send me PM.
Sent from my latest and greatest HTC One M7 UL
-¤-¤-TIP FROM THE NOOB-¤-¤-
Create system back-up before granting apk's root permission, editing system files, and flashing a new rom.
? better safe than sorry ?
?May the Angels lead your way Tom (Tony Stark) . You will be missed bud ?