Related
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) OKAY
sending time = 2.555 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 7(s)
MY GETVAR
C:\Users\Admin\.android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.31.50.0215
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA484MZ00350
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: A1000037D94F05
(bootloader) product: a5_dwg
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C51000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 09813c97
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 13(ms)
And i Get this error
C:\Users\Admin\.android>fastboot oem unlock
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
Help Me Out!!!
My Device Is HTC DESIRE 816 Dual Sim (INDIA)
sujay123 said:
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) OKAY
sending time = 2.555 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 7(s)
MY GETVAR
C:\Users\Admin\.android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.31.50.0215
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA484MZ00350
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: A1000037D94F05
(bootloader) product: a5_dwg
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C51000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 09813c97
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 13(ms)
And i Get this error
C:\Users\Admin\.android>fastboot oem unlock
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
Help Me Out!!!
My Device Is HTC DESIRE 816 Dual Sim (INDIA)
Click to expand...
Click to collapse
Do you have HTC drivers installed?
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
Do you have HTC drivers installed?
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
Yeah I guess, I'm new to this stuff. So could you be a bit more Specific.
sujay123 said:
Yeah I guess, I'm new to this stuff. So could you be a bit more Specific.
Click to expand...
Click to collapse
Do you have HTC Sync installed is what I'm asking
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
Do you have HTC Sync installed is what I'm asking
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
Yeah, But its unable to recognize the device.
sujay123 said:
Yeah, But its unable to recognize the device.
Click to expand...
Click to collapse
1st. Remove imei and imei 2 from first post for safety reasons.
2. Uninstall HTC Sync but keep everything else it installed..
3. Make sure you have Java installed ( not sure if you need it , but I always have it installed )
4. Have you tried flashing the zip again ? Boot loader locked ?
fastboot flash zip (name of zip)
If fails it should say flush again.. then redo the command.
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
1st. Remove imei and imei 2 from first post for safety reasons.
2. Uninstall HTC Sync but keep everything else it installed..
3. Make sure you have Java installed ( not sure if you need it , but I always have it installed )
4. Have you tried flashing the zip again ? Boot loader locked ?
fastboot flash zip (name of zip)
If fails it should say flush again.. then redo the command.
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
1) Done
2) Done
3) Have It
4)
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) OKAY
sending time = 2.558 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 6(s)
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) OKAY
sending time = 2.554 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 6(s)
C:\Users\Admin\.android>fastboot oem unlock
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 0(ms)
sujay123 said:
1) Done
2) Done
3) Have It
4)
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) OKAY
sending time = 2.558 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 6(s)
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) OKAY
sending time = 2.554 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 6(s)
C:\Users\Admin\.android>fastboot oem unlock
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 0(ms)
Click to expand...
Click to collapse
Okay lock boot loader first if it's already unlocked
fastboot oem lock
Then try flashing the zip again.
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
Okay lock boot loader first if it's already unlocked
fastboot oem lock
Then try flashing the zip again.
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
C:\Users\Admin\.android>fastboot oem lock
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) WARM RESET: 9
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
Execution time is 1(s)
And WNIDOWS ERROR : FASTBOOT.EXE Has Stopped Working
Now Waiting for my battery to drain
sujay123 said:
C:\Users\Admin\.android>fastboot oem lock
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) WARM RESET: 9
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
Execution time is 1(s)
And WNIDOWS ERROR : FASTBOOT.EXE Has Stopped Working
Now Waiting for my battery to drain
Click to expand...
Click to collapse
Okay I need to know what you did that left your phone in the state that it is.
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
Okay I need to know what you did that left your phone in the state that it is.
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
First I Rooted it, Via CWM
Then I tried to Partition My SD card ,but failed , so i got it back to its original state.
Then Tried to install some random theme.zip through CWM
That's when the problem started (Stuck At black screen on Booting)
Then I'm not sure about this : I probably formatted the SYSTEM via CWM (Probably the reason for absent OS)
And I'm Not sure how I lost CWM : probably while flashing stock recovery.img (via Fastboot)
and then FASTBOOT OEM LOCK, tried to unlock it but i keep getting the same error.
and then i downloaded and installed this HTC SPECIAL FASTBOOT DRIVER DOWNLOAD & ADB SETUP DRIVER
and again tried to flash RECOVER.IMG, but failed.
So I Repeated the unlock procedure from the HTC website.
I get option , I select unlock , The Device REBOOTS, and FASTBOOT OEM UNLOCK : FAILED
But , even then I try to Flash 0P9CIMG.zip which fails again and again.
I have no Idea Whats going on
I can only Access the bootloader menu.
Cannot Access recovery , a red triangle and ! appears.
PLEASE TELL ME YOU HAVE A SOLUTION.
I'M READY TO DOWNLOAD A NEW RECOVERY.IMG AND RUU FOR A5_DWG
sujay123 said:
First I Rooted it, Via CWM
Then I tried to Partition My SD card ,but failed , so i got it back to its original state.
Then Tried to install some random theme.zip through CWM
That's when the problem started (Stuck At black screen on Booting)
Then I'm not sure about this : I probably formatted the SYSTEM via CWM (Probably the reason for absent OS)
And I'm Not sure how I lost CWM : probably while flashing stock recovery.img (via Fastboot)
and then FASTBOOT OEM LOCK, tried to unlock it but i keep getting the same error.
and then i downloaded and installed this HTC SPECIAL FASTBOOT DRIVER DOWNLOAD & ADB SETUP DRIVER
and again tried to flash RECOVER.IMG, but failed.
So I Repeated the unlock procedure from the HTC website.
I get option , I select unlock , The Device REBOOTS, and FASTBOOT OEM UNLOCK : FAILED
But , even then I try to Flash 0P9CIMG.zip which fails again and again.
I have no Idea Whats going on
I can only Access the bootloader menu.
Cannot Access recovery , a red triangle and ! appears.
PLEASE TELL ME YOU HAVE A SOLUTION.
I'M READY TO DOWNLOAD A NEW RECOVERY.IMG AND RUU FOR A5_DWG
Click to expand...
Click to collapse
Have you tried placing zip on external SDCard and name it 0P9CIMG.zip and let the boot loader do the RUU Update it's self.
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
Have you tried placing zip on external SDCard and name it 0P9CIMG.zip and let the boot loader do the RUU Update it's self.
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
Okay I Think This is it (Hope It Works)
Flashing ZIP file....
:fingers-crossed:
Do you Want to Start Update
<VOL UP> Yes
<VOL DOWN> No
Going With Yes
sujay123 said:
Okay I Think This is it (Hope It Works)
Flashing ZIP file....
:fingers-crossed:
Do you Want to Start Update
<VOL UP> Yes
<VOL DOWN> No
Going With Yes
Click to expand...
Click to collapse
Well?
Sent from my HTC Desire EYE using Tapatalk
xXminiWHOOPERxX said:
Well?
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
I got the OS- (2.34.720.1)
Update is in progress
flashing zip file
Is this it?
xXminiWHOOPERxX said:
Well?
Sent from my HTC Desire EYE using Tapatalk
Click to expand...
Click to collapse
OMG :crying: Thank you So Much , I LOVE YOU.
Just A few More Queries
1 ) Can/How Do I Unlock OEM
2) How do I get to know the status of My Device rooted/unrooted
3) Which one is preferred CWM/TWRP , and do I put it back using the normal procedure.?
4) Can I modify/Change the Stock recovery.img
5) Should I install the SuperSU.zip/apk
sujay123 said:
OMG :crying: Thank you So Much , I LOVE YOU.
Just A few More Queries
1 ) Can/How Do I Unlock OEM
2) How do I get to know the status of My Device rooted/unrooted
3) Which one is preferred CWM/TWRP , and do I put it back using the normal procedure.?
4) Can I modify/Change the Stock recovery.img
5) Should I install the SuperSU.zip/apk
Click to expand...
Click to collapse
1) To sim unlock I'm unsure of because I don't own a dual sim device ..
Unlock boot loader on htcdev.com
2&3) install official twrp from their website and download SuperSU 2.56
Sent from my HTC Desire EYE using Tapatalk
Red triangle with stock recovery flash
Cannot Access recovery , a red triangle and ! appears.
Just to chime in on the red triangle issue . I had that same issue when reflashing my stock recovery back to my rooted 816 single SIM and the issue was that the stock recovery was there but had that screen due to the fact that I had altered the phone and the triangle is an indicator of that for HTC I guess. I was able to get into the stock recovery by pressing and holding the power button then pressing volume up and waiting . When the stock recovery screen shows up you release the volume button I believe but it might be releasing both. It's been a while. Either way I got into the stock recovery but I ended up just reflashing TWRP custom recovery back and not doing my stock update as the zip file kept failing. Glad you got expert help with your issues and got it resolved.
sujay123 said:
C:\Users\Admin\.android>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (38480 KB) O
And i Get this error
C:\Users\Admin\.android>fastboot oem unlock
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
Help Me Out!!!
My Device Is HTC DESIRE 816 Dual Sim (INDIA)
Click to expand...
Click to collapse
Could u plz post the link to that zip file, becos im also using a5dwg
thoctor said:
Cannot Access recovery , a red triangle and ! appears.
Just to chime in on the red triangle issue . I had that same issue when reflashing my stock recovery back to my rooted 816 single SIM and the issue was that the stock recovery was there but had that screen due to the fact that I had altered the phone and the triangle is an indicator of that for HTC I guess. I was able to get into the stock recovery by pressing and holding the power button then pressing volume up and waiting . When the stock recovery screen shows up you release the volume button I believe but it might be releasing both. It's been a while. Either way I got into the stock recovery but I ended up just reflashing TWRP custom recovery back and not doing my stock update as the zip file kept failing. Glad you got expert help with your issues and got it resolved.
Click to expand...
Click to collapse
I had tried every combination, nothing worked. It was either restart or was stuck at the boot screen (HTC white Logo) or a Black screen.
Yeah me too!!
Probably not all have noticed the last Marshmallow 6.0 update 6.12.401.4 for the HTC M8 European edition. Greets to the uploader.
Here it is:
http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
To be clear, this is just (leaked) firmware.zip, not the ROM.
Folks seem trigger-happy to make threads about the 401 update, when there isn't one yet?
---------- Post added at 12:31 PM ---------- Previous post was at 11:32 AM ----------
Stock flashable ROM is here: http://forum.xda-developers.com/htc-one-m8/development/rom-sense-6-12-401-4-mra58k-stock-t3296066
There is also apparently a (leaked?) RUU around somewhere?
Is this the RUU?
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
https://www.androidfilehost.com/?fid=24369303960687057
David_UK said:
Is this the RUU?
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
https://www.androidfilehost.com/?fid=24369303960687057
Click to expand...
Click to collapse
looks like it. flashing in 5, 4, 3,...
kukubau said:
looks like it. flashing in 5, 4, 3,...
Click to expand...
Click to collapse
How to flash? Rename to 0P6BIMG.zip and flashing with hboot?
forgiveMySin said:
How to flash? Rename to 0P6BIMG.zip and flashing with hboot?
Click to expand...
Click to collapse
I don't know if you need to rename it to 0P6BIMG.zip. I have S-OFF and the bootloader unlocked and I hadn't to.
Download htc_fastboot.exe from somewhere or get it from inside any RUU exe after the files were unpacked and the wizard has started.
1. Boot into bootloader
2. type with the phone connected at your computer:
Code:
fastboot oem rebootRUU
3.
Code:
htc_fastboot flash zip <path to the rom.zip file>/rom.zip
, named accordingly
wait...
done
David_UK said:
Is this the RUU?
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
https://www.androidfilehost.com/?fid=24369303960687057
Click to expand...
Click to collapse
Flashed, it works great. Thanks!
When I tried to flash it says:
Target reported max download size of 1826152448 bytes
Error: cannot load c:\adb\0P6BIMG.zip
I have tried to download again, but it stil gives me the same error.
target reported max download size of 1826418688 bytes
sending 'zip' (1687272 KB)...
OKAY [ 64.343s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 126.091s
OTA over wifi failed. This one also (maybe because of relocked bootloader?)
No I get FAILED (remote: 32 header error)
kukubau said:
I don't know if you need to rename it to 0P6BIMG.zip. I have S-OFF and the bootloader unlocked and I hadn't to.
Download htc_fastboot.exe from somewhere or get it from inside any RUU exe after the files were unpacked and the wizard has started.
1. Boot into bootloader
2. type with the phone connected at your computer:
Code:
fastboot oem rebootRUU
3.
Code:
htc_fastboot flash zip <path to the rom.zip file>/rom.zip
, named accordingly
wait...
done
Click to expand...
Click to collapse
so, if i have an unlocked bootloader and s-off can i follow your procedure ?
Here it is ...
All official ...
Majland said:
When I tried to flash it says:
Target reported max download size of 1826152448 bytes
Error: cannot load c:\adb\0P6BIMG.zip
I have tried to download again, but it stil gives me the same error.
Click to expand...
Click to collapse
I downloaded 3 times and still get corrupt file.... MD5 is ok though...
Now Im trying to restore to go via OTA....
David_UK said:
Is this the RUU?
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
https://www.androidfilehost.com/?fid=24369303960687057
Click to expand...
Click to collapse
Thank you very mych for the link!!!
HTC OTA update fu*k up my phone (my phone is untouched - not rooted moded and so - unlocked version). Update process stop unexpectedly (not able to mount SDCARD or something like that ) and my phone was unusable - unable to start android and goes automatically to recovery. I had to preform manual upgrade with RUU from the link. The only drawback is that the update wipe all my phone including internal memory and I lost all my pictures (not big deal of price of bricked phone). The HTC backup restore almost everything and now phone working like charm.
I cant find any normal, human language tutorial, to fix this **** up without s-off. My htc was rooted, I flashed su... Now I'm on stock recovery. Only this is my prob:
fakitol said:
target reported max download size of 1826418688 bytes
sending 'zip' (1687272 KB)...
OKAY [ 64.343s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 126.091s
OTA over wifi failed. This one also (maybe because of relocked bootloader?)
No I get FAILED (remote: 32 header error)
Click to expand...
Click to collapse
I have exactly the same problem
I downloaded the file:
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
from:
androidfilehost fid=24369303960686952 (I can't post the link because I'm a forum baby...)
md5 compare downloaded file and website is same (good download) - 469c3b8504ce2a2c8aae0fde17bfe028
Did anyone have success with the above file?
C:\adb>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1687272 KB)...
OKAY [ 65.280s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 126.942s
---------- Post added at 04:22 PM ---------- Previous post was at 04:13 PM ----------
Pepaaa said:
I have exactly the same problem
I downloaded the file:
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
from:
androidfilehost fid=24369303960686952 (I can't post the link because I'm a forum baby...)
md5 compare downloaded file and website is same (good download) - 469c3b8504ce2a2c8aae0fde17bfe028
Did anyone have success with the above file?
C:\adb>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1687272 KB)...
OKAY [ 65.280s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 126.942s
Click to expand...
Click to collapse
Just found that this ZIP method will most likely not work if your phone is S-ON
Then my phone can't be revived without the original RUU.EXE or "unmodified" RUU.ZIP method.
Any ideas? Please share...
When I read my phone info, I get this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45*********
(bootloader) imei: <hidden>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Pepaaa said:
I have exactly the same problem
I downloaded the file:
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
from:
androidfilehost fid=24369303960686952 (I can't post the link because I'm a forum baby...)
md5 compare downloaded file and website is same (good download) - 469c3b8504ce2a2c8aae0fde17bfe028
Did anyone have success with the above file?
C:\adb>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1687272 KB)...
OKAY [ 65.280s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 126.942s
---------- Post added at 04:22 PM ---------- Previous post was at 04:13 PM ----------
Just found that this ZIP method will most likely not work if your phone is S-ON
Then my phone can't be revived without the original RUU.EXE or "unmodified" RUU.ZIP method.
Any ideas? Please share...
When I read my phone info, I get this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45*********
(bootloader) imei: <hidden>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
error 12 is when bootloader is locked.
Pepaaa said:
I have exactly the same problem
I downloaded the file:
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
from:
androidfilehost fid=24369303960686952 (I can't post the link because I'm a forum baby...)
md5 compare downloaded file and website is same (good download) - 469c3b8504ce2a2c8aae0fde17bfe028
Did anyone have success with the above file?
C:\adb>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1687272 KB)...
OKAY [ 65.280s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 126.942s
Click to expand...
Click to collapse
You don't read properly what is written on post #6
You need htc_fastboot.exe to flash the RUU zip. Normal/google fastboot.exe won't work.
Also S-On device must relock bootloader.
htc_fastboot.exe - https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
For S-On
fastboot oem lock (to relock bootloader)
fastboot reboot-bootloader (reboot to bootloader after relock)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
For S-Off
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
---------- Post added at 03:58 PM ---------- Previous post was at 03:35 PM ----------
fakitol said:
I cant find any normal, human language tutorial, to fix this **** up without s-off. My htc was rooted, I flashed su... Now I'm on stock recovery. Only this is my prob:
Click to expand...
Click to collapse
You can't OTA on a rooted device.
You can get the non-rooted 4.16.401.13 backup from my thread linked in my signature
then try restore system partition only then redo OTA process again and see how it goes.
restore system partition only will keep your data intact.
If this fails, then you need to restore all boot, data, system.
ckpv5 said:
You don't read properly what is written on post #6
You need htc_fastboot.exe to flash the RUU zip. Normal/google fastboot.exe won't work.
Also S-On device must relock bootloader.
htc_fastboot.exe -
For S-On
fastboot oem lock (to relock bootloader)
fastboot reboot-bootloader (reboot to bootloader after relock)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
For S-Off
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
Click to expand...
Click to collapse
You rock! RUU has started now using htc_fastboot and I have some progress
It says it's completed successfully:
"OKAY
Flash Zip Complete
Execution time is 349(s)"
And I/m back on the command line.
Now I have black screen with silver htc logo and full green progress bar (indicating 100% - but not percentage is shown, just full)
Do I need to reboot the phone manually or just wait?
Pepaaa said:
You rock! RUU has started now using htc_fastboot and I have some progress
It says it's completed successfully:
"OKAY
Flash Zip Complete
Execution time is 349(s)"
And I/m back on the command line.
Now I have black screen with silver htc logo and full green progress bar (indicating 100% - but not percentage is shown, just full)
Do I need to reboot the phone manually or just wait?
Click to expand...
Click to collapse
Once it is completed, you run fastboot reboot-bootloader and check your bootloader is correct with new info then you can reboot for the rest of the process. (or you can simply reboot - fastboot reboot)
lorezz said:
so, if i have an unlocked bootloader and s-off can i follow your procedure ?
Click to expand...
Click to collapse
yes.
hey guys i have a htc one m9+
cid:htc__038
i accidentally deleted my os and i have twrp running in it.
i tried returning to stock buy download the RUU from the method stated below but could not succeed can anyone please help cause i have invested a lot and bought this phone.....
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08. 1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
1.79 GB https://mega.nz/#!MEVWDS6a!K_LTgIXX4...oJVJo2hwju71SI
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08 .707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
2.10 GB https://mega.nz/#!FFslyDzD!8INOzNsGk...q0z93JP_GNTBqU
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08. 709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
2.25 GB https://mega.nz/#!xNN1nTiS!yS6U9RQOk...VsDp23NwfUWzQ8
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.4 01.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
2.09 GB https://mega.nz/#!IRtz1A6b!EFsQgQyZ8...8K-pI2grk8hrwg
MD5s:
7a2e7e2e973f3209eaeff1db96bed859 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08 .709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
e28e0736489da46fee6e0ae72aff8471 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08 .1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
ed8436646f3dc4542f3b2036300d6e2d *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.0 8.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
8fa1b59afcd28f2e229728306aba3c6a *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08. 401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
To flash this on S-On, you must have your device Relocked (on S-Off you don't need to relock) and then in fastboot mode:
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
Please be aware that you'll lose all data doing this.
If you're S-On you can only flash the zip that is for you CarrierID (CID). With superCID or modified CID value through S-OFF you can try to flash other regions RUUs.
DISCLAIMER:
All responsibility and risk you take on yourself downloading and using these in any way. Be sure to know what you do!
Read about similar topic here: http://forum.xda-developers.com/show....php?t=2251800
Which version of your M9+?
cid:htc__038 --> Indian version ,you should download *hTC_Asia_WWE_1.08 .707.4* ...
In download mode, check your version first.
> fastboot getvar all
If you are s-off,you could flash the ROM.zip.
But if you are S-ON, your version should not be newer than 1.08.707.* .
Can u help me i need step by step tutorial for returning to stock so that i can update to MM rom.
now i am on Clean Slate 1.2.3
my status.
software status Modified
Unlocked
HTC HIAU ML 128 SHIP S-ON
CID-HTC 031
LK-1.01.0000 68332ab2
OS-1.90.401.3
Thanks
Sent from my HTC One M9PLUS using Tapatalk
Since your M9+ is s-on,download the RUU you need.
https://forum.xda-developers.com/one-m9/one-m9-general/europe-1-90-403-1-ruu-t3478310
Here is the step by step tutorial.
https://forum.xda-developers.com/showpost.php?p=61801034&postcount=8
So I have to relock it , put zip on SD card , get to download mode and flash @yvtc75
Sent from my HTC One M9PLUS using Tapatalk
vipi77 said:
So I have to relock it , put zip on SD card , get to download mode and flash @yvtc75
Click to expand...
Click to collapse
Relocked your bootloader. Put the ROM.zip on the same fastboot/ADB directory in your local PC. Connect your device to PC by usb cable and execute these command to flash it.
Ok thanks. does it matter that the phone was Factory unlocked?
Sent from my HTC One M9PLUS using Tapatalk
Please Help Me
My Current VER is As Following(HTC One M9+) On MM
--------------------------------------------------------------------------------------------
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: ******************
(bootloader) version-main: 2.30.707.1
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: HTC__038
all:
finished. total time: 0.004s
----------------------------------------------------------------------------------------------------------
If i Flash Following Rom
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed
Which Contains My CID_038
I wants revert toStock Rom For Some Touch Related Issue
Also In Future I wants to Upgrade To Next Android Os
So Please Tell me is it Ok Or i am Wrong ?
Thanks In Advance...
rKsREDMI1s said:
Please Help Me
My Current VER is As Following(HTC One M9+) On MM
--------------------------------------------------------------------------------------------
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: ******************
(bootloader) version-main: 2.30.707.1
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: HTC__038
all:
finished. total time: 0.004s
----------------------------------------------------------------------------------------------------------
If i Flash Following Rom
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed
Which Contains My CID_038
I wants revert toStock Rom For Some Touch Related Issue
Also In Future I wants to Upgrade To Next Android Os
So Please Tell me is it Ok Or i am Wrong ?
Thanks In Advance...
Click to expand...
Click to collapse
U need s-off for flashing ruu older than ur device's vers
yvtc75 said:
Relocked your bootloader. Put the ROM.zip on the same fastboot/ADB directory in your local PC. Connect your device to PC by usb cable and execute these command to flash it.
Click to expand...
Click to collapse
i can not relock bootloader from fastboot. stuck again
FAILED unkonwn command
what*s next?
T3snake said:
U need s-off for flashing ruu older than ur device's vers
Click to expand...
Click to collapse
Thanks
-----------------------------------------------
There is One Available here
https://forum.xda-developers.com/one-m9/one-m9-general/ruu-m9-hiauml-ruu-collection-t3547166
(Asia WWE:
0PK711000 / HTC__044, HTC__038
0PK7IMG_HIAU_ML_TUHL_M60_SENSE70_MR_hTC_Asia_WWE_2 .30.707.1_Radio_1.1550V70.2501.0304_HT[W.T]_release_487633_signed_2_4.zip)
Can You Please Tell Me
Is this RUU i can apply when My Phone is S On ?
Thanks
rKsREDMI1s said:
Thanks
-----------------------------------------------
There is One Available here
https://forum.xda-developers.com/one-m9/one-m9-general/ruu-m9-hiauml-ruu-collection-t3547166
(Asia WWE:
0PK711000 / HTC__044, HTC__038
0PK7IMG_HIAU_ML_TUHL_M60_SENSE70_MR_hTC_Asia_WWE_2 .30.707.1_Radio_1.1550V70.2501.0304_HT[W.T]_release_487633_signed_2_4.zip)
Can You Please Tell Me
Is this RUU i can apply when My Phone is S On ?
Thanks
Click to expand...
Click to collapse
Damn if i knew earlier i wouldn't have to do s off but i guess nougat will be easy to update since i have soff
Anyway the one you mentioned will work on s-on u just need to relock bootloader to flash it
Thanks...
Now Downloading ....
Will Give Results After flashing .....
failed
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2481537560 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2481537560 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2481537560 is not a multiple of the block size 4096
OKAY [ 1.016s]
writing 'zip' 1/1...
(bootloader) HOSD CL#821792
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_E
(bootloader) 9E6Cl
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap )
finished. total time: 3.094s
yvtc75 said:
Which version of your M9+?
cid:htc__038 --> Indian version ,you should download *hTC_Asia_WWE_1.08 .707.4* ...
In download mode, check your version first.
> fastboot getvar all
If you are s-off,you could flash the ROM.zip.
But if you are S-ON, your version should not be newer than 1.08.707.* .
Click to expand...
Click to collapse
HI there,finally someone wrote something about the Indian version .I own an HTC One m9plus prime camera edition phone which is the Indian version of m9+.I want to root it but haven't been sure of it since I haven't been able to find the stock ROM for if.it's still on lollipop.and there are some bloatware I want to remove .if I could just find I right and safe way to root it. And also probably upgrade to atleast marshmallow.
Hello,
i am trying different RUUs for my HTC ONE M9+ since i flashed the wrong one once.
Now i cannot install any RUU anymore, no matter what recovery i am using.
When i try to flash via
htc_fastboot flash zip [ruu.zip], I always get this error
ending 'zip'... (70108 KB) OKAY
sending time = 3.236 secs
writing 'zip'... (bootloader) HOSD CL#670935
FAIL9: SD_SECURITY_FAIL zip from usb command in download mode
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
Execution time is 3(s)
Click to expand...
Click to collapse
When i simply put the 0PK7IMG.zip on sdcard and start download mode, it just skips installation.
My phone info:
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: 3574******7
(bootloader) version-main: 2.27.401.1
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: 11111111
Click to expand...
Click to collapse
S-ON.
I recently flashed hosd with a new hos_verified.hosd. Could it be related?
ANY IDEAS?
DarthLuda said:
Hello,
i am trying different RUUs for my HTC ONE M9+ since i flashed the wrong one once.
Now i cannot install any RUU anymore, no matter what recovery i am using.
When i try to flash via
htc_fastboot flash zip [ruu.zip], I always get this error
When i simply put the 0PK7IMG.zip on sdcard and start download mode, it just skips installation.
My phone info:
S-ON.
I recently flashed hosd with a new hos_verified.hosd. Could it be related?
ANY IDEAS?
Click to expand...
Click to collapse
Have you flash it after "fastboot oem rebootRUU"?
antonmandara said:
Have you flash it after "fastboot oem rebootRUU"?
Click to expand...
Click to collapse
I can't because the command fails
c:\fastboot>fastboot oem rebootRU
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.035s]
finished. total time: 0.036s
Click to expand...
Click to collapse
had the bootloader unlocked and ended up giving hardbrick after an update via OTA.
I managed to recover but had the alert that the bootloader was unlocked, so I wanted to block again, then by fasstboot, I made the command: fastboot flashing lock, and apois this alert began to appear.
I'm afraid to give a factory reset and give hardbrick.
image attached
https://drive.google.com/file/d/1V_UK0iGIhDO31dETqs9t83uZ_TOHHYIJ/view?usp=sharing
What device do you have and what firmware did you use to lock your device with? I'd check your ADB folder and make sure you've extracted the correct firmware. Also, that should give you an opportunity to delete any old stock ROMs - updating via OTA after flashing an old stock ROM runs a risk of hard bricking.
When you're locking your device bootloader, your device will be wiped anyway.
echo92 said:
What device do you have and what firmware did you use to lock your device with? I'd check your ADB folder and make sure you've extracted the correct firmware. Also, that should give you an opportunity to delete any old stock ROMs - updating via OTA after flashing an old stock ROM runs a risk of hard bricking.
When you're locking your device bootloader, your device will be wiped anyway.
Click to expand...
Click to collapse
I'm going to put the prints here of the device and the folder that I used to pass the mobile;
one detail that I realized is that the rom that step is at ATHENE_NPJS25.93-14-18, but on the device shows ATHENE_NPJS25.93-14-4.
https://drive.google.com/file/d/1ivZZP275zHBteiykw5hgF2elSkatCAOs/view?usp=sharing
https://drive.google.com/file/d/1znezKwp4esAJ6Q1rJFoeJtg-gmhZjAXy/view?usp=sharing
the rom was supposed to be the April 2018 patch but appears in March 2017;
I really wanted to reset the factory; but I'm afraid to brick it again
luis dambrowski said:
I'm going to put the prints here of the device and the folder that I used to pass the mobile;
one detail that I realized is that the rom that step is at ATHENE_NPJS25.93-14-18, but on the device shows ATHENE_NPJS25.93-14-4.
https://drive.google.com/file/d/1ivZZP275zHBteiykw5hgF2elSkatCAOs/view?usp=sharing
https://drive.google.com/file/d/1znezKwp4esAJ6Q1rJFoeJtg-gmhZjAXy/view?usp=sharing
the rom was supposed to be the April 2018 patch but appears in March 2017;
Click to expand...
Click to collapse
Hmm, you have the March 2017 stock ROM but the Feb/April 2018 baseband. I wonder if you've got a firmware mismatch in your ADB folder?
I'd delete all the stock ROM files from your ADB folder (except the ADB and fastboot files and your flashing scripts), then extract a fresh copy of the NPJS25.93-14-18 firmware, then copy the extracted files to your ADB folder (don't extract directly to the ADB folder if your ADB folder is on C drive, sometimes UAC can block the extraction. Extract then copy to the C drive). That way, you can be sure the firmware you're flashing is not mixed up (despite the same timestamps, have you verified the md5 checksums of the extracted files match the md5 checksums in the flashfile.xml or servicefile.xml? You can use a program like WinMD5Free to check).
When you recovered from the hard brick, did you flash a working GPT and bootloader before you attempted to lock your device?
What flashing commands are you using and what are the outputs? I'd suggest trying to flash the stock ROM again, provided you've cleaned out your ADB folder as suggested above.
Can you also post your getvar all info here please?
1)Boot your device to the bootloader, connect your device to your computer via USB.
2)Open an ADB terminal on your computer. Type 'fastboot getvar all' without quotes in the terminal. Press Enter.
3)Please post or paste the getvar all output in a text file and upload to this thread, or paste the output here. You may wish to omit your IMEI. This should give us an idea of your device health.
echo92 said:
Hmm, you have the March 2017 stock ROM but the Feb/April 2018 baseband. I wonder if you've got a firmware mismatch in your ADB folder?
I'd delete all the stock ROM files from your ADB folder (except the ADB and fastboot files and your flashing scripts), then extract a fresh copy of the NPJS25.93-14-18 firmware, then copy the extracted files to your ADB folder (don't extract directly to the ADB folder if your ADB folder is on C drive, sometimes UAC can block the extraction. Extract then copy to the C drive). That way, you can be sure the firmware you're flashing is not mixed up (despite the same timestamps, have you verified the md5 checksums of the extracted files match the md5 checksums in the flashfile.xml or servicefile.xml? You can use a program like WinMD5Free to check).
When you recovered from the hard brick, did you flash a working GPT and bootloader before you attempted to lock your device?
What flashing commands are you using and what are the outputs? I'd suggest trying to flash the stock ROM again, provided you've cleaned out your ADB folder as suggested above.
Can you also post your getvar all info here please?
1)Boot your device to the bootloader, connect your device to your computer via USB.
2)Open an ADB terminal on your computer. Type 'fastboot getvar all' without quotes in the terminal. Press Enter.
3)Please post or paste the getvar all output in a text file and upload to this thread, or paste the output here. You may wish to omit your IMEI. This should give us an idea of your device health.
Click to expand...
Click to collapse
about having incompatibility, I do not know what to do, what I did was download the rom that was supposed to be the april of 2018 and add the fastboot files and the .bat OEM lock and OEM Flash files, and run the OEM lock.bat
about the procedure of extracting the files, I believe that I have nothing mixed, I just do not understand how it does not load the right version, but I can do it if I think it's the problem
luis dambrowski said:
about having incompatibility, I do not know what to do, what I did was download the rom that was supposed to be the april of 2018 and add the fastboot files and the .bat OEM lock and OEM Flash files, and run the OEM lock.bat
about the procedure of extracting the files, I believe that I have nothing mixed, I just do not understand how it does not load the right version, but I can do it if I think it's the problem
Click to expand...
Click to collapse
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go... never mind, I had a look at my ADB folder and the same is for me
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Edit 2: can you repeat the flash without the locking commands please (the two initial OEM lock commands and the final OEM lock command)
echo92 said:
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go...
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Click to expand...
Click to collapse
a piece of the log
"
D:\Downloads\Nova pasta (2)\teste>fastboot oem lock begin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Not in unlocked state
OKAY [ 0.174s]
finished. total time: 0.175s
D:\Downloads\Nova pasta (2)\teste>fastboot oem lock begin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Not in unlocked state
OKAY [ 0.176s]
finished. total time: 0.178s
D:\Downloads\Nova pasta (2)\teste>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.137s]
finished. total time: 0.146s
D:\Downloads\Nova pasta (2)\teste>fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.128s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) flash permission denied
(bootloader) will fail: flash:cmnlib
FAILED (remote failure)
finished. total time: 0.329s
D:\Downloads\Nova pasta (2)\teste>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.078s]
writing 'logo'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.095s
D:\Downloads\Nova pasta (2)\teste>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.176s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.194s
D:\Downloads\Nova pasta (2)\teste>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 1.241s]
writing 'recovery'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.254s
D:\Downloads\Nova pasta (2)\teste>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.540s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.553s
D:\Downloads\Nova pasta (2)\teste>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [ 3.140s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 3.149s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 16.071s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.079s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (250846 KB)...
......
"
echo92 said:
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go...
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Edit 2: can you repeat the flash without the locking commands please (the two initial OEM lock commands and the final OEM lock command)
Click to expand...
Click to collapse
I will do now,
D:\Downloads\Nova pasta (2)\teste>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.067s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.137s]
finished. total time: 0.209s
D:\Downloads\Nova pasta (2)\teste>fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) flash permission denied
(bootloader) will fail: flash:cmnlib
FAILED (remote failure)
finished. total time: 0.368s
D:\Downloads\Nova pasta (2)\teste>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.105s]
writing 'logo'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.120s
D:\Downloads\Nova pasta (2)\teste>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.738s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.755s
D:\Downloads\Nova pasta (2)\teste>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.707s]
writing 'recovery'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.723s
D:\Downloads\Nova pasta (2)\teste>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.696s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.710s
D:\Downloads\Nova pasta (2)\teste>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [ 4.547s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.555s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
luis dambrowski said:
I will do now,
.
Click to expand...
Click to collapse
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?
echo92 said:
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?
Click to expand...
Click to collapse
I have already done the process with another cable and another port and using the commands manually, without positive results.
exactly was using the blankflash, then it was stuck on the screen with the "start" in the bootloader, after this tried to flash several roms and without result, nothing worked.
Yes I tried to make GPT / bootloader flash, (gpt and boot), but it did not work.
So I downloaded that rom that I sent the print with the adb files that should be April 2018, and the phone revived, but with the red bootlader alert unlocked, and so I was using it without problems. but I wanted to remove the alert, and tried to block the bootloader, I used the command: fastboot flashing lock, and asked to flash again from a rom, but at the moment I did not have the files and just rebooted.
So I got that yellow alert, everything works normally, but I wanted to fix this problem, so I can make updates via OTA in the future.
Sorry for the bad English.
echo92 said:
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?
Click to expand...
Click to collapse
and if I do a blankflash again now and do the rom flash, would it work?
luis dambrowski said:
I have already done the process with another cable and another port and using the commands manually, without positive results.
exactly was using the blankflash, then it was stuck on the screen with the "start" in the bootloader, after this tried to flash several roms and without result, nothing worked.
Yes I tried to make GPT / bootloader flash, (gpt and boot), but it did not work.
So I downloaded that rom that I sent the print with the adb files that should be April 2018, and the phone revived, but with the red bootlader alert unlocked, and so I was using it without problems. but I wanted to remove the alert, and tried to block the bootloader, I used the command: fastboot flashing lock, and asked to flash again from a rom, but at the moment I did not have the files and just rebooted.
So I got that yellow alert, everything works normally, but I wanted to fix this problem, so I can make updates via OTA in the future.
Sorry for the bad English.
Click to expand...
Click to collapse
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)
echo92 said:
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)
Click to expand...
Click to collapse
When I did the GPT / bootloader flash (gpt and boot) process, there was apparently no change.
do you suggest doing the flash with that (bootloader.img and gpt.bin) now? to remove this alert?
in fact this alert does not bother me, but I intend to remove it for future upgrade via OTA.
finally I will try to redo the process with ADB v1.4.3.
echo92 said:
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)
Click to expand...
Click to collapse
I did all the procedures, separated and together, with no results.
I made a "Format Factory" for the recovery and did the rom flash again also did not work.
it is in the same way.
* should i try to update via OTA
luis dambrowski said:
I did all the procedures, separated and together, with no results.
I made a "Format Factory" for the recovery and did the rom flash again also did not work.
it is in the same way.
* should i try to update via OTA
Click to expand...
Click to collapse
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.
echo92 said:
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.
Click to expand...
Click to collapse
ainda esta no firmware de março de 2017!
Tive uma ideia de desbloquear o bootloader e instalar o TWRP e colocar uma custom rom. No entanto, o código de desbloqueio não pode ser encontrado no site da motorola, mas sim o desbloqueio do bootloader.
Pois bem, o probloma aqui é o bootloader !!
Estou sem ideias de como prosseguir.
Sera que quando sair de novo update, (talvez algum) de certo o processo?
echo92 said:
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.
Click to expand...
Click to collapse
good news!!! solved problem.
What did I do:
I used the command: fastboot flashing unlock
then he asked to repeat the command and then unlocked the bootloader, with the alert that was yellow turned red.
There I did the rom flash of April 2018 and it went without errors.
rom update and no bootloader alert.
echo92 thank you very much for your attention. big hug!!!