When i proceed to unlock my boot loader an error showing that " Your device does not qualify for bootloader unlocking" ...
Any solution for this ?? Plz help me out....
Refer ss
{
"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"
}
Sent from my XT1033 using XDA Free mobile app
My device doesnot qualify for unlocking bootloader...my cid code is 0*0007...so what to do now?
Vinod check this info
How can do i validate whether my device is unlockable? You can use our online tool, or you can check manually by issuing a fastboot command and looking at the CID value returned.
$ fastboot getvar all
The table below will indicate whether your device is eligible for the bootloader unlock program:
Your device is unlockable if the CID value returned is:
Your device is NOT eligible for bootloader unlock if the CID value returned is one of
0x0000
0x0003
0x0007
0x0009
0x000B
0x000C
0x000D
0x000E
0x0014
0x00DE
0x0001
0x0002
0x0004
0x0005
0x0006
0x0008
0x000A
0x000F
0x0010
0x0011
0x0032
Sent from my XT1033 using XDA Free mobile app
0x0007 can be unlocked
vinodh44u said:
My device doesnot qualify for unlocking bootloader...my cid code is 0*0007...so what to do now?View attachment 2895550
Vinod check this info
How can do i validate whether my device is unlockable? You can use our online tool, or you can check manually by issuing a fastboot command and looking at the CID value returned.
$ fastboot getvar all
The table below will indicate whether your device is eligible for the bootloader unlock program:
Your device is unlockable if the CID value returned is:
Your device is NOT eligible for bootloader unlock if the CID value returned is one of
0x0000
0x0003
0x0007
0x0009
0x000B
0x000C
0x000D
0x000E
0x0014
0x00DE
0x0001
0x0002
0x0004
0x0005
0x0006
0x0008
0x000A
0x000F
0x0010
0x0011
0x0032
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
Dude did you read it right? My device is also 0x0007. And it says Unlockable. Recheck the website. If it cannot be unlocked you wont even get the key. 0x0007 can be unlocked. Relax. and the error, i had the same trouble. They are saying its because of some bug in 4.4 Android.
Related
please Jailbreak after to use.
{
"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"
}
command line:
/dbgview
/writemem "123.exe kernel32.dll+0xc EEFF"
/injectdll 1234 C:\a.dll
Popup 'Copy as path' by without press Shift key
x86:
shell32.dll+004F93CA -> shell32!IContextMenu_QueryContextMenu
crack addr:004F93EC -> 0x90,0x90
ARM:
shell32.dll+002160AC -> shell32!IContextMenu_QueryContextMenu
crack addr:002160C8 -> 0x0,0x0
75DC60BC 2400 movs r4,#0
75DC60BE 461D mov r5,r3
75DC60C0 F410 7F80 tst r0,#0x100 -> keyState,if SHIFT is 0x00020590
75DC60C4 4616 mov r6,r2
75DC60C6 460F mov r7,r1
75DC60C8 D016 beq 75DC60F8 -> nop
75DC60CA F010 0F03 tst r0,#3
75DC60CE D113 bne 75DC60F8
75DC60D0 480E ldr r0,75DC610C
75DC60D2 4C0D ldr r4,75DC6108
75DC60D4 2350 movs r3,#0x50
75DC60D6 6800 ldr r0,[r0]
75DC60D8 6824 ldr r4,[r4]
75DC60DA AA02 add r2,sp,#8
75DC60DC F247 6178 mov r1,#0x7678
75DC60E0 47A0 blx r4 -> LoadStringW
75DC60E2 4C08 ldr r4,75DC6104
75DC60E4 A802 add r0,sp,#8
75DC60E6 9000 str r0,[sp]
75DC60E8 6824 ldr r4,[r4]
75DC60EA 462B mov r3,r5
75DC60EC F44F 6280 mov r2,#0x400
75DC60F0 4631 mov r1,r6
75DC60F2 4638 mov r0,r7
75DC60F4 47A0 blx r4 -> InsertMenuW
XOR EAX,EAX
TEST DWORD PTR SS:[EBP+1C],100
PUSH ESI
MOV ESI,DWORD PTR SS:[EBP+C]
JE SHORT shell32.761F942A -> nop or jo
TEST BYTE PTR SS:[EBP+1C],3
JNZ SHORT shell32.761F942A
PUSH 50
LEA EAX,DWORD PTR SS:[EBP-A4]
PUSH EAX
PUSH 7678
PUSH DWORD PTR DS:[76309AC0]
CALL LoadStringW
LEA EAX,DWORD PTR SS:[EBP-A4]
PUSH EAX
PUSH DWORD PTR SS:[EBP+14]
PUSH 400
PUSH DWORD PTR SS:[EBP+10]
PUSH ESI
CALL InsertMenuW
x86 batfile:
MEMConsole /writemem "explorer.exe shell32.dll+0x4F93EC 9090"
ARM batfile:
MEMConsole /writemem "explorer.exe shell32.dll+0x2160C8 0000"
for AllProcesses:
MEMConsole /writemem "ANY shell32.dll+0x2160C8 0000(or 9090)"
Mircrosoft Windows Update in 2013-4-10 : Popup 'Copy as path' by without press Shift key
ARM batfile:
MEMConsole /writemem "explorer.exe shell32.dll+0x2239B4 0000"
Hi, I am trying to find out how to unbrick a G Stylo LS770 that stuck on Qualcomm HS-USB QDLoader 9008 mode.
First, I need to get the rawprogram0.xml for G Stylo LS770..
from a rooted working LS770 model:
Code:
adb shell su -c 'dd if=/dev/block/mmcblk0 of=/cache/partition0.bin bs=512 count=20480'
Get partition0.bin
{
"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"
}
00 04 00 is sbl1 -Start LBA
00 07 FF is sbl1 - end LBA
In the original Boarddiag tool, there are rawprogram0.xml file for other LG models.
I have to build a new one for LS770 model. Below is the sbl1 entry created based on the information from partition file.
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="sbl1.mbn" label="sbl1" num_partition_sectors="1024" physical_partition_number="0" size_in_KB="512.0" sparse="false" start_byte_hex="0x80000" start_sector="1024" />
num_partition_sectors: End LBA- start LBA+1 = 400, Convert it to HEX, that is 1024
start_sector = Start LBA, and convert it to HEX, that is 1024.
start_byte_hex : 1024*512= 524288 convert to hex, it is 80000
Now we have the rawprogram0.xml
-- I will add other parts later.
Forgive my bad English,..(
How did you get to qdloader 9008 mode? I am missing download mode on a g stylo I just picked up from someone deleting the laf partition and if I can get it to 9008 mode I could possibly fix it from what you posted.
Sent from my LGLS770 using XDA-Developers mobile app
yes. i'm in 9008 too. so you creat the rawprogram0.xml yet???
asialove2013 said:
Hi, I am trying to find out how to unbrick a G Stylo LS770 that stuck on Qualcomm HS-USB QDLoader 9008 mode.
First, I need to get the rawprogram0.xml for G Stylo LS770..
from a rooted working LS770 model:
Code:
adb shell su -c 'dd if=/dev/block/mmcblk0 of=/cache/partition0.bin bs=512 count=20480'
Get partition0.bin
00 04 00 is sbl1 -Start LBA
00 07 FF is sbl1 - end LBA
In the original Boarddiag tool, there are rawprogram0.xml file for other LG models.
I have to build a new one for LS770 model. Below is the sbl1 entry created based on the information from partition file.
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="sbl1.mbn" label="sbl1" num_partition_sectors="1024" physical_partition_number="0" size_in_KB="512.0" sparse="false" start_byte_hex="0x80000" start_sector="1024" />
num_partition_sectors: End LBA- start LBA+1 = 400, Convert it to HEX, that is 1024
start_sector = Start LBA, and convert it to HEX, that is 1024.
start_byte_hex : 1024*512= 524288 convert to hex, it is 80000
Now we have the rawprogram0.xml
-- I will add other parts later.
Forgive my bad English,..(
Click to expand...
Click to collapse
How do I get the raw? I ran it the command in adb but I didn't know where it saved.
Hi. Did this ever get anywhere? i have one LS770 bricked via downgrade and I have been trying to get it fixed since december
Hi,
Because I could not find a reliable rooting mechanism I soldered a serial FTDI UB232, and I gain shell access.
The serial works ok as long I am in u-boot prompt.
Texas Instruments X-Loader 1.41 (Apr 12 2012 - 12:06:17)
OMAP4460: 1.2 GHz capable SOM
**** DDR SDRAM PATTERN TEST ****
DDR SDRAM DATA BUS TEST..... [PASSED]
DDR SDRAM ADDRESS BUS TEST..... [PASSED]
Starting OS Bootloader from EMMC ...
U-Boot 1.1.4 (Nov 9 2012 - 20:33:58)
Load address: 0x80e80000
DRAM: 1024 MB
Flash: 0 kB
Using default environment
printenv
bootargs=console=ttyO2,115200n8 [email protected] [email protected] init=/init vram=48M omapfb.vram=0:32M androidboot.console=ttyO2
bootcmd=booti mmc1
bootdelay=1
baudrate=115200
ipaddr=128.247.77.90
serverip=128.247.77.158
netmask=255.255.254.0
bootfile="uImage"
ethact=KS8851SNL
Environment size: 285/131068 bytes
As soon android boots when everything is settled down, the tty input is totally ignored, though the shell
prints all the os messages. There is no prompt. ?!?
[ 33.844390] wlan0: moving STA 00:90:a9:a5:51:a1 to state 3
[ 58.387908] omap_cpu_thermal_manager:sensor 66200 avg sensor 59795 pcb 0, delta 18897 hot spot 85097
[ 58.397766] omap_monitor_zone:hot spot temp 85097
[ 58.887908] omap_cpu_thermal_manager:sensor 63800 avg sensor 59795 pcb 0, delta 17742 hot spot 81542
[ 58.897827] omap_safe_zone:hot spot temp 81542
no prompt
Any idea how to outcome and enable the shell tty input.
Here are the pictures of the serial soldering and the serial to usb adapter.
(The pictures are mine, from the stack-over-flow post)
{
"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"
}
The ftdi
I found and android for OMAP blaze (GB and a kernel from https://e2e.ti.com/support/omap/f/849/t/310839),
After having all cowboys engineering from Texas headaches I finally end up with:
boot.img cache.img fastboot mkbootimg MLO_es2.1_gp MLO_es2.2_emu ramdisk.img ramdisk-recovery.img recovery.img system.img u-boot.bin userdata.img zImage files.
I tried first a non destructive flash, trying to flash the system, (then boot, kernel, recovery / all of them encountering same error)
Linux console:
sudo fastboot flash system system.img
[sudo] password for mpang:
< waiting for device >
sending 'system' (110304 KB)...
OKAY [ 42.127s]
writing 'system'...
FAILED (remote failure)
finished. total time: 42.137s
marquis tablet serial output, as shown in previous post
OMAP44XX TAB # fastboot
I2C read: I/O error
I2C read: I/O error
Device Serial Number: 5C28000200000001
Fastboot entered...
Starting download of 112951340 bytes
................................................................................... many dots
downloading of 112951340 bytes finished
writing to partition 'system'
Wrong Image... Failed to program
How did we get here fastboot.c 993 ?
Anyone ?, Thank you
Hello.
When I try to turn on NFC, it appears for "ON" and then "OFF".
https://sendvid.com/iykxmguc
I back to stock ROM Android 5.0.2 2.33.401.5. S-OFF, unlock bootloader.
This is my logcat when I try to power ON.
(filtering NFC)
{
"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"
}
logcat without filtering "NFC"
Code:
E/MP-Decision( 1971): Update arg 2
E/QCOM PowerHAL( 964): long long_duration_touch_boost fd -1
E/QCOM PowerHAL( 964): long long_duration_touch_boost fd -1
E/QCOM PowerHAL( 964): long long_duration_touch_boost fd -1
E/QCOM PowerHAL( 964): long long_duration_touch_boost fd -1
E/QCOM PowerHAL( 964): long long_duration_touch_boost fd -1
V/NfcEnabler( 5934): Turn on NFC.
D/NFC ( 5934): callMethod: enable() called with system uid.
D/HtcNfcEnablePromptActivity( 1438): isNeedToBlockCaller: caller uid=1000, follow google flow.
I/NfcService( 1438): getDefaultSE 0
D/NfcService( 1438): Enabling Nfc.
W/Settings( 1438): Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
I/NfcService( 1438): Enabling NFC
D/PMS ( 964): acquireWL(103ea112): PARTIAL_WAKE_LOCK NfcService:mRoutingWakeLock 0x1 1438 1027 null
D/Nfc-Utils( 1438): NFC default protocol route: 2
I/Nfc-Utils( 1438): Disable eSE: false, false
V/NfcEnabler( 5934): handleNfcStateChanged 2
E/MP-Decision( 1971): Update arg 1
W/NFCJNI ( 1438): Firmware update FAILED
D/ContactMessageStore( 1425): MSG_CHECK_DELETION >>
D/ContactMessageStore( 1425): mDeleteTask = null, bDeleting = false
D/AccFlag ( 1425): sku_id=69
D/ContactMessageStore( 1425): MSG_CHECK_DELETION <<
D/ContactMessageStore( 1425): start background delete task...
D/ContactMessageStore( 1425): size: 0 , 0
D/ContactMessageStore( 1425): Background delete complete
W/NFCJNI ( 1438): Firmware update FAILED
W/NFCJNI ( 1438): Firmware update FAILED
E/NFCJNI ( 1438): Unable to update firmware, giving up
W/NfcService( 1438): Error enabling NFC
D/PMS ( 964): releaseWL(103ea112): PARTIAL_WAKE_LOCK NfcService:mRoutingWakeLock 0x1 null
V/NfcEnabler( 5934): handleNfcStateChanged 1
Syndical
This is an alternative to SamLoader - cleaner code, easier to understand and tamper with.
Written purely in C#. SamLoader was, of course, the base of Syndical, but impemented differently.
Current progress can be viewed here: Trello board.
Source code and releases: GitHub.
Why I should use Syndical?
1) It looks a lot better than any other firmware downloaders
2) Download & Decrypt is a lot faster, as it won't download the entire file and then only decrypt it.
3) Because I'll steal your liver
Warning
Resume mode might work not as expected.
Also Samsung ships only two last firmware versions, Fetch is proof.
Screenshots
{
"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"
}
How to use
Arguments
Code:
-m, --mode Required. Which mode I should use
-v, --firmware-version Firmware version
-i, --input File to decrypt
-o, --output Filename for decrypted/downloaded file
-M, --model Required. Device model
-r, --region Required. Device region
-f, --factory Download factory firmware (Binary Nature)
-h, --disable-hash-check Disables hash check in Download mode
-r, --disable-resume Disables resume in Download mode
--help Display this help screen.
--version Display version information.
Modes
Code:
Download Download firmware
Decrypt Decrypt firmware
Fetch Fetch latest firmware
DownloadDecrypt Download and decrypt firmware simultaneously
Examples
Code:
./Syndical.Application -m Download -v A207FXXU2CUI2/A207FOXM2CUI2/A207FXXU2CUI2/A207FXXU2CUI2 -M SM-A207F -r SER -f
./Syndical.Application -m Decrypt -v A207FXXU2CUI2/A207FOXM2CUI2/A207FXXU2CUI2/A207FXXU2CUI2 -M SM-A207F -r SER -f
./Syndical.Application -m DownloadDecrypt -v A207FXXU2CUI2/A207FOXM2CUI2/A207FXXU2CUI2/A207FXXU2CUI2 -M SM-A207F -r SER -f
./Syndical.Application -m Fetch -M SM-A207F -r SER
Credits
TheAirBlow for Syndical itself .
nlscc for SamLoader.
Licence
Mozilla Public License Version 2.0
Interesting. Does it have a GUI?
Slaggy said:
Interesting. Does it have a GUI?
Click to expand...
Click to collapse
It doesn't, and probably it never would get one. Maybe I'll make an Avalonia GUI for Thor Suite (I have plans to make a software bundle: flash tool, firmware downloader, PIT Viewer/Editor, etc.), but I want to make the flash tool and etc. to be written in C++ (it would be faster, I can make my own driver, working with libusb is easier, etc.), but I'm very bad at it, so I need someone with relatively good knowledge to help me. Until I find someone, all Samsung Loki projects would be abandoned (Thor and Syndical)