You are not rooted. re read the original post.hi i think new ota cant use this?
C:\Users\h\Desktop\miniadb>adb shell
shell@htc_m8:/ $ su
su
1|shell@htc_m8:/ $ echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
lock/mmcblk0p6 bs=1 seek=5314564 <
/dev/block/mmcblk0p6: cannot open for write: Permission denied
1|shell@htc_m8:/ $ echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
dd of=/dev/block/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied
1|shell@htc_m8:/ $ exit
exit
my getvar
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.707.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: a3d0cb0d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
tthanks
As long as you meet the criteria specified in the op,yesIs this method still works with latest 4.4.4 and 3.28.401.9 firmware and latest hboot? I want to unlock the bootloader without htcdev
As long as you meet the criteria specified in the op,yes
Sent from my Nexus 9 using Tapatalk
Correct,it will notSuperCID won't stop me from unlocking the bootloader am I right?
I'm on Google Play Edition Lollipop, and want to relock bootloader to get Drive storage. Will my storage be wiped after I relock from this method? If not, then will it be wiped if I unlock again after getting the Drive storage? A bit off-topic but is it possible to get Drive storage on Google Play Edition version?
Thank you, I hope someone can answer these 3 questions
It should. An OTA does not generally change anything at the level at which that this worksScotty -
Will this work with the AT&T update to 4.4.4 OTA that just came out Monday January 26?
I definitely don't want to brick my phone...
Thanks!
It should. An OTA does not generally change anything at the level at which that this works
Sent from my HTC One using Tapatalk
You're writing to the wrong partition. this thread is for m8Bell canada htc one m7 and i copy and pasted the adb command to lock the bootloader
shell@m7:/ $ su
su
root@m7:/ # echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=3
3796
of=/dev/block/mmcblk0p2 bs=1 seek=33796 <
4+0 records in
4+0 records out
4 bytes transferred in 0.018 secs (222 bytes/sec)
root@m7:/ # exit
exit
shell@m7:/ $ exit
exit
C:\Android>adb reboot-bootloader
but my bootloader is still unlocked?? Any ideas guys?
I should have mentioned this earlier, be aware that you have damaged your stock p2 and will brick your phone if you attempt to turn it back to s on.lol duh thats what happens after working a 12 hour midnight shift!!!
You're writing to the wrong partition. this thread is for m8
Sent from my HTC One using Tapatalk
The pics are because I didn't have m8 at the time,and there is an explanation of that afterwards.OK, that makes sense. But it does not make sense that the pictures in the first post are from a m7. That put me on the wrong idea it was for the m7.
I came across this by a search and did not look at the forum title at first.
Can you Scotty or anyone direct or tell me (and maybe some others) (to) the right shell lock/relock lines for the m7
searched the m7 general forum but could not find it.
It would be very much appreciated. Thanks.
OK, that makes sense. But it does not make sense that the pictures in the first post are from a m7. That put me on the wrong idea it was for the m7.
I came across this by a search and did not look at the forum title at first.
Can you Scotty or anyone direct or tell me (and maybe some others) (to) the right shell lock/relock lines for the m7
searched the m7 general forum but could not find it.
It would be very much appreciated. Thanks.
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
Yes it is possible. Having a locked bootloader will NOT prevent you from flashing a recovery, firmware, or an ruu.
Files just need properly packed as a zip file, you cannot use the fastboot flash command.
Sent from my One using Tapatalk
@scotty1223 will this royally mess anything up if I try this on my Sprint M8?
A couple questions:
1). Does this actually change you back to locked the way <fastboot oem lock> would? or is it just changing the header text?
2). I see references to the Sprint M8 and this is in the M8 forum, but would if foul anyting up to try it on a Verizon M8 with the 3.16 HBoot?
Thanks for the clarification.