I recently rooted my Sprint Nexus 6 and everything was going fine. But then I started to run into issues when running the disabling the decryption. I was able to resolve those and install Pure Rom and customize it to my liking before taking a backup. But I logged into my WiFi immediately when setting up that phone. Soon after I turned off the wifi when stepping out, and I saw an Exclamation Point show up next to what was previously a semi full signal strength meter. I tried calling a few numbers and nothing was working.
I updated my PRL to the latest prior to rooting, etc. I know that this is a risk when you root, but does anyone know a possible solution?
My Recovery, ADB, Fastboot and everything works, I just can't get the signal.
I have also tried to update with the factory image from google:
https://developers.google.com/android/nexus/images
It does seem to update the Radio and a few other things, but ultimately fails:
pkalaria-ltm:tools pkalaria$ bash ./flash-all.sh
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.121s]
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.378s]
finished. total time: 0.499s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (67170 KB)...
OKAY [ 2.109s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.905s]
finished. total time: 3.015s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(96115,0xa11b21a8) malloc: *** mach_vm_map(size=1681272832) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679592636 bytes
error: update package missing system.img
pkalaria-ltm:tools pkalaria$
Click to expand...
Click to collapse
Any help is appreciated, thanks.
Pl2lNCE said:
I recently rooted my Sprint Nexus 6 and everything was going fine. But then I started to run into issues when running the disabling the decryption. I was able to resolve those and install Pure Rom and customize it to my liking before taking a backup. But I logged into my WiFi immediately when setting up that phone. Soon after I turned off the wifi when stepping out, and I saw an Exclamation Point show up next to what was previously a semi full signal strength meter. I tried calling a few numbers and nothing was working.
I updated my PRL to the latest prior to rooting, etc. I know that this is a risk when you root, but does anyone know a possible solution?
My Recovery, ADB, Fastboot and everything works, I just can't get the signal.
I have also tried to update with the factory image from google:
https://developers.google.com/android/nexus/images
It does seem to update the Radio and a few other things, but ultimately fails:
Any help is appreciated, thanks.
Click to expand...
Click to collapse
I'm also on Sprint and had the same issue myself, I thinking that since these ROMs are so new that maybe they need our APNs added or something.
Maybe there is another way around this issue for the time being but I didn't investigate it further, I just didn't have time.
Mistertac said:
I'm also on Sprint and had the same issue myself, I thinking that since these ROMs are so new that maybe they need our APNs added or something.
Maybe there is another way around this issue for the time being but I didn't investigate it further, I just didn't have time.
Click to expand...
Click to collapse
I found a workaround, you can manually flash the images inside image-shamu-lrx21o.zip:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
I just flashed the decrypted boot.img, system, userdata, and cache and I was good to go. Fresh install of Stock Rom without Envrcption., and I was able to Update the PRL/Device Config. Now just gotta get it set up and Root again.
hey i may have messed up my nexus 6 already. unlocked the bootloader, rooted it with no problem. downloaded the twrp from play store and installed. got an install error. i looked online for someone having the issue and they said they got error and booted into recovery and it was working. i did the same. once in recovery i did a hard reset just to see if it was working, it worked. after that i hit fix permissions. and then phone would never boot. i was a little drunk so i went into recovery again, and wiped but this time i checked system. not smart i know, but what can i say. now phone boots upto google screen with unlock icon? what do i do?
Reflash factory imagine
Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
El Daddy said:
Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.
uncfan44 said:
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.
Click to expand...
Click to collapse
Sometimes you have to install the drivers on your computer again while your phone is connected and in the boot loader.
Also, if you don't have your environment variables set up correctly, you'll have to open the command prompt from the same folder in which fastboot.exe lies. As well as putting the image files in that folder.
Sent from my Nexus 5 using Tapatalk
and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.
uncfan44 said:
and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.
Click to expand...
Click to collapse
Make sure you have fastboot selected in bootloader and try this tool to make sure fastboot is installed in your machine properly.
http://forum.xda-developers.com/showthread.php?t=2588979
ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!
uncfan44 said:
ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!
Click to expand...
Click to collapse
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!
Make sure you have the newest fastboot and flash everything manually. If you don't have the newest fastboot it'll throw errors.
12MaNy said:
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!
Click to expand...
Click to collapse
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
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.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>
uncfan44 said:
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
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.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>
Click to expand...
Click to collapse
You have the latest fastboot installed? Also the system image from Google was extracted to platform tools? And lastly did u check md5 of original download?
Definitely not something wrong with the commands your using.
yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.
uncfan44 said:
yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.
Click to expand...
Click to collapse
I know im a little late but you can just use wugfresh nexus toolkit and flash back to stock.
last sunday I tried to get on stock lollipop on my xt1052 AsiaRetail and i flashed GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml.zip from Here. Whole Flashing was showing errors after each command,
Code:
C:\Users\VIJAY SINGH\Downloads\Compressed\Moto X BE\Moto X BE\1_Repair_Boot (RSD
Lite)\1052\ASIA>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.329s]
writing '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
OKAY [ 0.444s]
finished. total time: 0.782s
After Reading http://forum.xda-developers.com/moto-x/general/moto-x-unbrick-ota-update-loader-v30-t3153725] This i came to a conclusion that i have the latest bootloader installed on my phone i.e., Version 30.BE and the file i flashed wasn't that latest which was required, I searched for the solution alot but didn't found any, Please help me
The phone is able to go in Fastboot mode and computer too recognise it as Mot Single ADB Interface, so that is not an issue. All my partiitions like recovery system cache and other have gone up.
last FW
XT1052_RETAIL-ASIA-AUSTRALIA-5.1_LPA23.12-15.5_cid7_CFC.xml
ATT_XT1058_5.1_LPA23.12-21.7_cid1_CFC.xml
XT1058_GHOST_RCICA_5.1_LPA23.12-21.7_cid14_CFC.xml
VZW_XT1060_5.1.0-LPA23.12-39.7_cid2_CFC.xml
here https://yadi.sk/d/MCliEyCPfj7ZZ/MOTO.X1
Sir i tried the Last one, as it is lollipop rom, but still same Unsupported variable Error!! and my bootloader is 30.BE. and i flashed an older firmware i guess
vijayid_94 said:
...but still same Unsupported variable Error!! and my bootloader is 30.BE.....
Click to expand...
Click to collapse
Variable Not Supported message is normal, and not an error.
GHOST_RETAIL is usually for the XT1053. IF you have an XT1052, you should be flashing the ROM for your phone.
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 ?