HTC 10 - Bootloader "Lock" flag ? - HTC 10 Questions & Answers

Hi all !
I've a question. It's possible to restore the bootloader status to "Lock" flag ? My device is S-OFF.
Thanks a lot

El-Conkistador said:
Hi all !
I've a question. It's possible to restore the bootloader status to "Lock" flag ? My device is S-OFF.
Thanks a lot
Click to expand...
Click to collapse
Not at present time. If you try using one of the older device methods you will likely damage your phone.

I've make a search. The bootloader flag is stocked in /dev/block/mmcblk0p3 (pg1fs)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If the bootloader flag is modified, the tag "HTCU" or "HTCL" is available there. But an other tag is viewable : "nYZ¾" (6E 59 5A BE) or "¹}Ío" (B9 7D CD 6F).
Just editing the TAG "HTCU" ou "HTCL" is not suffisent. I've not see another difference between the two dump.

mmcblk0p3 -- "pg1fs"
search for the dec 33796 or hex 8404
with HxD edited
locked -- 00 00 00 00
unlocked -- 48 54 43 55 "HTCU"
relocked -- 48 54 43 4C "HTCL"
device reboot into bootloader mode
Code:
fastboot flash pg1fs file-name
E.g
Code:
fastboot flash pg1fs locked.bin

Playing with fire. Playing with fire.
Sent from my HTC6545LVW using Tapatalk

nenebear said:
mmcblk0p3 -- "pg1fs"
search for the dec 33796 or hex 8404
with HxD edited
locked -- 00 00 00 00
unlocked -- 48 54 43 55 "HTCU"
relocked -- 48 54 43 4C "HTCL"
device reboot into bootloader mode
Code:
fastboot flash pg1fs file-name
E.g
Code:
fastboot flash pg1fs locked.bin
Click to expand...
Click to collapse
You have an problem. The second offset is changed if your phone is Relock or Unlock
dottat said:
Playing with fire. Playing with fire.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
No ^^ , I just investigate

Related

GT-I9000_GB_Update3.zip - new kernel/platform sources from Samsung (2012/07/30)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
new source file upload from Samsung (with KERNEL and PLATFORM) :
(2012/08) GT-I9000_GB_Update3.zip (130 760 896 bytes)
list of previously released source files from Samsung:
(2012/04) GT-I9000_Opensource_GB_Update2.zip (130 448 844 bytes)
(2011/09) GalaxyS_OpenSource_GB_Update2.zip (137 626 058 bytes)
(2011/06) GT-I9000_OpenSource_GB_Update.tar.gz (130 834 699 bytes)
(2011/04) GT-I9000_OpenSource_GB.zip (131 262 550 bytes)
Only for devs?
Sent from my GT-I9000 using Tapatalk 2
Abyv said:
Means we can flash GB via Cwm or what?
Thanks
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Face palm...
Sent from my GT-I9000 using xda premium
DanielSanchez said:
Face palm...
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Oh really ? Thanks for being so unhelpful.
Sent from my GT-I9000 using Tapatalk 2
platform - comparison to previous release (2012-update3 vs 2012-update2)
same files with different content:
Code:
device/samsung/GT-I9000/alsa-lib/Android.mk
extension/brcm/adaptation/dtun/dtunc_bz4/dtun_clnt.c
extension/brcm/adaptation/dtun/dtunc_bz4/dtun_hcid.c
extension/brcm/adaptation/dtun/include/dtun.h
external/bluetooth/bluez/src/adapter.c
external/bluetooth/bluez/src/agent.c
external/bluetooth/bluez/src/agent.h
external/bluetooth/bluez/src/dbus-hci.c
external/bluetooth/bluez/src/device.c
external/bluetooth/bluez/src/textfile.c
external/iproute2/man/man8/tc-pfifo.8
external/webkit/WebCore/rendering/RenderBlock.cpp
external/webkit/WebCore/rendering/RenderObjectChildList.cpp
external/webkit/WebCore/rendering/RenderObjectChildList.h
external/webkit/WebCore/rendering/RenderObject.h
external/webkit/WebKit/android/jni/WebViewCore.cpp
SECUI/apps/Email/src/org/mozilla/intl/chardet/Big5Statistics.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/EUCJPStatistics.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/EUCKRStatistics.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/EUCTWStatistics.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/GB2312Statistics.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsBIG5Verifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsCP1252Verifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsDetector.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsEUCJPVerifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsEUCKRVerifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsEUCSampler.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsEUCStatistics.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsEUCTWVerifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsGB18030Verifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsGB2312Verifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsHZVerifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsICh****tDetectionObserver.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsICh****tDetector.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsISO2022CNVerifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsISO2022JPVerifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsISO2022KRVerifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsPSMDetector.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsSJISVerifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsUCS2BEVerifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsUCS2LEVerifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsUTF8Verifier.java
SECUI/apps/Email/src/org/mozilla/intl/chardet/nsVerifier.java
only in update2:
Code:
external/webkit/WMLScriptCore/wmlscr/grammar
external/webkit/WMLScriptCore/wmlscr/wmlsbcgen
platform/external/webkit/WMLScriptCore/wmlsec
only in update3:
Code:
device/samsung/GT-I9000/alsa-lib/aserver
external/bluetooth/bluez/audio/MODULE_LICENSE_GPL
external/bluetooth/bluez/audio/NOTICE
external/bluetooth/bluez/compat/MODULE_LICENSE_GPL
external/bluetooth/bluez/compat/NOTICE
external/bluetooth/bluez/gdbus/MODULE_LICENSE_GPL
external/bluetooth/bluez/gdbus/NOTICE
external/bluetooth/bluez/input/MODULE_LICENSE_GPL
external/bluetooth/bluez/input/NOTICE
external/bluetooth/bluez/lib/MODULE_LICENSE_GPL
external/bluetooth/bluez/lib/NOTICE
external/bluetooth/bluez/plugins/MODULE_LICENSE_GPL
external/bluetooth/bluez/plugins/NOTICE
external/bluetooth/bluez/tools/MODULE_LICENSE_GPL
external/bluetooth/bluez/tools/NOTICE
external/bluetooth/glib/glib/MODULE_LICENSE_GPL
external/bluetooth/glib/glib/NOTICE
external/iproute2/CleanSpec.mk
external/iptables/extensions/libip6t_HL.man
external/iptables/extensions/libip6t_MARK.man
external/iptables/extensions/libipt_connmark.man
external/iptables/extensions/libipt_dscp.man
external/iptables/extensions/libipt_ECN.man
external/iptables/extensions/libipt_mark.man
external/iptables/extensions/libipt_SET.man
external/iptables/extensions/libipt_TCPMSS.man
external/iptables/extensions/libipt_tos.man
external/iptables/extensions/libipt_TTL.man
kernel - comparison to previous release (2012-update3 vs 2012-update2)
same files with different content:
Code:
arch/arm/configs/aries_eur_defconfig
arch/arm/configs/aries_jpn_defconfig
arch/arm/mach-s5pv210/mach-aries.c
arch/microblaze/boot/dts/system.dts
drivers/gpu/pvr/bridged_pvr_bridge.c
drivers/gpu/pvr/dbgdrv/hostfunc.c
drivers/gpu/pvr/dbgdrv/main.c
drivers/gpu/pvr/device.h
drivers/gpu/pvr/hash.c
drivers/gpu/pvr/Kconfig
drivers/gpu/pvr/Makefile
drivers/gpu/pvr/mem_debug.c
drivers/gpu/pvr/mutils.h
drivers/gpu/pvr/osfunc.c
drivers/gpu/pvr/osfunc.h
drivers/gpu/pvr/power.c
drivers/gpu/pvr/pvrsrv.c
drivers/gpu/pvr/pvrversion.h
drivers/gpu/pvr/queue.c
drivers/gpu/pvr/s3c_bc/s3c_bc.c
drivers/gpu/pvr/s3c_bc/s3c_bc.h
drivers/gpu/pvr/s3c_bc/s3c_bc_linux.c
drivers/gpu/pvr/s3c_bc/s3c_bc_linux.h
drivers/gpu/pvr/s3c_bc/s3c_bc_params.h
drivers/gpu/pvr/s3c_lcd/s3c_displayclass.c
drivers/gpu/pvr/s5pc110/sysconfig.c
drivers/gpu/pvr/servicesext.h
drivers/gpu/pvr/sgx/bridged_sgx_bridge.c
drivers/gpu/pvr/sgxerrata.h
drivers/gpu/pvr/sgxinfo.h
drivers/gpu/pvr/sgx/sgxconfig.h
drivers/gpu/pvr/sgx/sgxinit.c
drivers/gpu/pvr/sgx/sgxpower.c
drivers/gpu/pvr/sgx/sgxreset.c
drivers/gpu/pvr/sgx/sgxtransfer.c
drivers/gpu/pvr/sgx/sgxutils.c
drivers/gpu/pvr/sgx/sgxutils.h
drivers/gpu/pvr/syscommon.h
drivers/input/touchscreen/qt602240.h
drivers/media/video/samsung/mfc50/mfc_interface.h
drivers/media/video/samsung/mfc50/mfc_memory.h
drivers/net/wireless/bcm4329/src/dhd/sys/dhd_linux.c
drivers/net/wireless/bcm4329/src/wl/sys/wl_iw.c
drivers/staging/android/binder.c
drivers/usb/gadget/f_mtp_samsung.c
drivers/usb/gadget/s3c_udc_otg_xfer_dma.c
drivers/usb/gadget/u_ether.c
fs/proc/base.c
sound/soc/codecs/wm8994_aries.c
sound/soc/codecs/wm8994_def.h
sound/soc/codecs/wm8994_samsung.c
sound/soc/codecs/wm8994_samsung.h
interesting stuff in update3 kernel :
drivers/input/touchscreen/qt602240.h
- here we have QT602240_firmware blog, which was not present in update2 (but this is not new file, it can be found in other sources)
arch/microblaze/boot/dts/system.dts
- empty 34 bytes (was not empty in update2)
drivers/gpu/pvr/pvrversion.h
- lower Imagination driver build 3947 & version 1.6.16.3947 (update2 have build 4131 and version 1.6.16.4131)
memory usage increased in various files, including decoders/encoders
interesting stuff in update3 platform :
extension/brcm/adaptation/dtun/
external/bluetooth/bluez/src/
- CTS patches : new Broadcom Bluetooth feature ([sic] "Broadocm Bluetooth feature - CTS VERI")

[Q] App data dated in the future?

I have been having an issue for some time now where if I install a new app, or upgrade an existing app, the .so files in the data/data/"app name"/lib folder get dated up to a month in the future. I first noticed this in Titanium Backup when sorting get by data freshness. For example, on 10/10 I downloaded an update to Google Earth from the Play Store. Titanium Backup shows the data changed 11/8/12:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here is the data/data/com.google.earth/lib folder contents in ES Explorer:
If I use a terminal emulator and display the directory with BUSYBOX LS -AL, I get:
=/data/local/bin:$PATH <
-al /data/data/com.google.earth/lib <
drwxr-xr-x 2 system system 4096 Oct 10 23:37 .
drwxr-xr-x 8 app_334 app_334 4096 Oct 10 23:01 ..
-rwxr-xr-x 1 system system 18181840 Nov 8 2012 libearthmobile.so
[email protected]:/ $
The incorrectly dated .so files display a year instead of a time, which the correctly dated files display.
This issue has survived multiple stock roms (including a data wipe to FI03) and multiple versions of Agat's Source kernel. Does anyone have any idea what could be causing this or how I might fix it? Thanks!
The only way I have been able to deal with this issue is to redate the files in the lib/ folders, which is a loosing battle. Anyone have any idea what could be causing this?
it's in dd/mm/yy mode
supersaeed said:
it's in dd/mm/yy mode
Click to expand...
Click to collapse
Thanks... how do I get it out of that mode?
I've searched here and on Google and can't find anything about a dd/mm/yy mode? Can anyone help me with this? :banghead:
i haven't a clue lol sorry
supersaeed said:
i haven't a clue lol sorry
Click to expand...
Click to collapse
Yeah, lol, I had a feeling you didn't have a clue when I read your original original answer, but I am desperate... :banghead:
Issue still exists after upgrading to FI27 (not that I thought it wouldn't), still looking for an answer to this. Apparently, this 'feature' is UNIQUE to my phone, so if there are any collectors out there, I'll sell it to you for $999.98...

US Firmware XT1644 Moto G4 Plus MPJ24.136-64 ATHENE

I received the update US Firmware XT1644 Moto G4 Plus MPJ24.139-64 ATHENE today and I am sure it is old news. I want to create a mirror for the update but I have not unlocked my device as of yet, so did not retrieve the update. If someone could send me the update so I can post it and any discussion on issues.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Where is this update located? I have it downloaded but cant find the zip
edit: The update I have is MPJ24.139-64
It could be a tar or zip. Unsure how motorola does there ota. Please if you have it, send me a link so I may upload it for everyone that has a US device. Thanks
The update can be found in the /cache folder after download. If you have something like Root Explorer, you can copy + paste the file to your internal or external storage from there.
It's located here:
Code:
/data/data/com.motorola.ccc.ota/app_download
That must be original cause my device Xt1644(US) is on build # MPJ24.139-49.
Original FW was MPJ24.139-48. The MPJ24.139-49 was a FW posted here only, supposedly shared by Moto with someone here - I have installed it too.
So the MPJ24.139-64 would be a newer one...

			
				
mikerowes69 said:
View attachment 3896100
Click to expand...
Click to collapse
Thread title has the wrong number.
Im having issuses with mine. the baseband reads (M8952_70009.08.03.45a ATHENE_RETUSA_CUST Ive been trying to find the right firmware but none are working. My IMEI is 0 so I cant get mobile signal
Your baseband is wrong, for XT1644 it should read M8952_70009.08.03.45R ATHENE_RETUSA_CUST. Don't know how you update the firmware, but you are doing it wrong - if you used the file XT1625-XT1644_ATHENE_RETUS_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Stop using random firmwares, it just messes up the phone more. Use only the ones that are for your phone.
Why does mine say 45a and not 45R?
Sent from my Moto G4 Plus using Tapatalk
Anyone got idea which filesystems are need to do a restore?
DDR
aboot
abootbak
boot
cache
cid
clogo
cmnlib
config
customize
devcfg
dip
dsp
frp
fsc
fsg
hw
hyp
hypbak
keymaster
kpan
limits
logo
logs
metadata
misc
modem
modemst1
modemst2
mota
oem
padC
persist
recovery
rpm
rpmbak
sbl1
sbl1bak
sec
sp
ssd
syscfg
system
tz
tzbak
userdata
utags
utagsBackup
ThaHaloMilitia said:
Why does mine say 45a and not 45R?
Click to expand...
Click to collapse
A is for amazon r is for retail from Motorola
I want to thank you for sharing the firmware with us

Restoring Serial Number - SN

Needs Root ROOT YOUR V30!
1. Download Ftm - partition from phone.
adb shell
su
dd if=/dev/block/bootdevice/by-name/ftm of=/sdcard/ftm.bin
2. You need to know your Serial Number so go imei24.com or imeipro.info and type yours IMEI.
3. Now open Ftm.bin with Hex.exe ( attached )
Then go Navigation -> Go to Offset... and type 73728
Type SN and save changes.
4. Copy ftm.bin to internal sdcard and flash it back in phone.
adb shell
su
dd if=/sdcard/ftm.bin of=/dev/block/bootdevice/by-name/ftm
reboot
Done!
SaiLas said:
Needs Root. For unlocking and rooting please read Bootloader Unlock and Root Instruction
Click to expand...
Click to collapse
Thanks for the useful information.
Thanks for fixing the link.
thanks, copy \ paste ....
actions for V35 and V30 are almost the same, my mistake
fixed
do you have video tutorials
do you have video tutorials?
SaiLas said:
Needs Root ROOT YOUR V30!
1. Download Ftm - partition from phone.
adb shell
su
dd if=/dev/block/bootdevice/by-name/ftm of=/sdcard/ftm.bin
2. You need to know your Serial Number so go imei24.com or imeipro.info and type yours IMEI.
3. Now open Ftm.bin with Hex.exe ( attached )
Then go Navigation -> Go to Offset... and type 73728
Type SN and save changes.
4. Copy ftm.bin to internal sdcard and flash it back in phone.
adb shell
su
dd if=/sdcard/ftm.bin of=/dev/block/bootdevice/by-name/ftm
reboot
Done!
Click to expand...
Click to collapse
help me ! I can't check s / n with imei
serial: 0 and s / n empty. Is it normal? how to fix? help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SaiLas said:
thanks, copy \ paste ....
actions for V35 and V30 are almost the same, my mistake
Click to expand...
Click to collapse
Hello, I read your post about V30 and V35, it seems that the operation steps are the same. My phone is V30+, and the system version is 30B. After following your method, I did not see the SN in "Settings-About phone-Hardware info and Status". I don't know if it succeeded.
Laygle said:
Hello, I read your post about V30 and V35, it seems that the operation steps are the same. My phone is V30+, and the system version is 30B. After following your method, I did not see the SN in "Settings-About phone-Hardware info and Status". I don't know if it succeeded.
Click to expand...
Click to collapse
Hi.
As far I remember SN not present in "Settings-About phone..." on 9 andr. v30, 30+.
Try read ftm partition again and check. Also you can check it flashing 8 or 7 andr.
hallo knows where the sn number is written for the LG v60 model?

Question About Unlocking Bootloader of TCL 20 SE

TCL customer service replied as follow when asking about unlock bootloader​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So there is no official way to unlock bootloader.​sometimes there is a unofficial way to unlock bootloader with firehose (edl mode)​
Magisk Patched Boot TCL 20 SE
Download
TWRP TCL 20 SE
Download
if you have the ability to unlock bootloader try above
(Sri Lanka) said:
TCL customer service replied as follow when asking about unlock bootloader​View attachment 5649523
View attachment 5649525
So there is no official way to unlock bootloader.​sometimes there is a unofficial way to unlock bootloader with firehose (edl mode)​
Magisk Patched Boot TCL 20 SE
Download
TWRP TCL 20 SE
Download
if you have the ability to unlock bootloader try above
Click to expand...
Click to collapse
You have tested the TWRP?
mutahharbashir said:
You have tested the TWRP?
Click to expand...
Click to collapse
no i count able to unlock bootloader
smiley9000 said:
TCL customer service replied as follow when asking about unlock bootloader​View attachment 5649523
View attachment 5649525
So there is no official way to unlock bootloader.​sometimes there is a unofficial way to unlock bootloader with firehose (edl mode)​
Magisk Patched Boot TCL 20 SE
Download
TWRP TCL 20 SE
Download
if you have the ability to unlock bootloader try above
Click to expand...
Click to collapse
Hi, how exactly do you obtain the boot.img? I have unlocked the bootloader but I don't have the stock firmware of it.
Edit: I tried to flash the magisk_patched.img that you've provided, but it has failed to flash, I guess this wasn't because of the image's fault.
Code:
E:\TCL\T671H>fastboot flash boot magisk_patched-25000_08uFS_from_xda.img
Sending 'boot_a' (98304 KB) OKAY [ 2.268s]
Writing 'boot_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed

Categories

Resources