Database Info

Error while unlocking boot loader XT1033

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.

Marquis MP977 MarquisPad serial disabled

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

Boot is in RAW, can't flash with fastboot[SOLVED]

So, I managed to wipe my filesystem when trying to root (going by the board that happens way too often I noticed).
I posted about it here https://forum.xda-developers.com/showpost.php?p=80579913&postcount=295 first.
But despite the quick and nice suggestions it still won't work.
Going by https://forum.xda-developers.com/showthread.php?t=3984875 I also tried to flash boot.img for Fastboot.
Yes, it's the right model ( GM21BA ) for Europe/Global 12gb/256
From make_f2fs.exe I get the following:
PS C:\temp> .\make_f2fs.exe [SERIAL]
F2FS-tools: mkfs.f2fs Ver: 1.9.0 (2017-11-13)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is enabled
Error: Failed to get device size!
Click to expand...
Click to collapse
Which has me thinking the filesystem is gone.
And then I erased and formated boot twice, and am still left with RAW fs.
PS C:\temp> fastboot format:ext4 boot
Warning: boot type is raw, but ext4 was requested for formating.
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
target reported max download size of 805306368 bytes
sending 'boot' (5688 KB)...
OKAY [ 0.021s]
writing 'boot'...
OKAY [ 0.107s]
finished. total time: 0.130s
Click to expand...
Click to collapse
And then I tried F2FS with Fastboot Format:
PS C:\temp> fastboot format:f2fs boot
Warning: boot type is raw, but f2fs was requested for formating.
Formatting is not supported for filesystem with type 'f2fs'.
Click to expand...
Click to collapse
So, as I'm writing this I'm reading up on make_f2fs to have it format a new 'boot' for me to flash unto.
Well, at least I have fastboot even if I can't seem to manage flashing anything, so it could be lot worse...

User MSM tool to restore to factory default. It will ease everything, but you will have a working phone. Follow the directions on the thread located here.

For future reference, I'll write how I did manage to fix this:
I had tried using MSM earlier, but couldn't get the qualcom-drivers installed (as mentioned in the thread linked).
So, I tried having the tool already active (and certificates installed) as I pressed both volume up & down and plugged in the phone.
Now a port reacted and I could (with great excitment and haste) press install:
{
"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"
}
As expected it's back to stock.

[DEV] "Empty" userdata-Partition of AVD/Genymotion Emulator

Hey,
i want to analyse the partitions of my Android Emulator using Autopsy for a prototype i am developing. I started with the userdata partition. However, it seems like that the partition does not contain any data, even though i produced some data (installed apps, phone calls, messages, browsing, etc). It is basically "empty" besides the default stuff that was already there before producing data (see the picture at the bottom). I dont really understand why this is the case. I also tried to reboot the emulator as i thought that the data i produced might be cached somewhere and is written to the userdata partition during shutdown (i checked if the generated data is still there after the reboot). Still, the size of the partition did not change. Other images (not created by me), which i analysed using autopsy during my digital forensic class, contained way more data in der userdata partition and were also produced using an emulator. Besides the AVD Emulator i tried the Genymotion Emulator. Nothing changed except the mapping.
This is what i did to extract the userdata:
1. Launched the emulator (latest API Level) and generated some data
2. Checked the connection via ADB (adb devices)
3. Become and verify root (adb root; whoami; id)
4. List the partition mapping (adb shell; ls -l /dev/block/mapper/)
emulator64_x86_64_arm64:/ # ls -l /dev/block/mapper/
total 0
drwxr-xr-x 2 root root 160 2022-03-26 11:09 by-uuid
lrwxrwxrwx 1 root root 15 2022-03-26 11:09 product -> /dev/block/dm-2
lrwxrwxrwx 1 root root 15 2022-03-26 11:09 system -> /dev/block/dm-0
lrwxrwxrwx 1 root root 15 2022-03-26 11:09 system-verity -> /dev/block/dm-4
lrwxrwxrwx 1 root root 15 2022-03-26 11:09 system_ext -> /dev/block/dm-1
lrwxrwxrwx 1 root root 15 2022-03-26 11:09 userdata -> /dev/block/dm-5
lrwxrwxrwx 1 root root 15 2022-03-26 11:09 vendor -> /dev/block/dm-3
5. Extracted the partition (adb pull /dev/block/dm-5 /DESTINATION_PATH)
6. Renamed the file to .img and created a new autopsy case
I expected the image to atleast contain data within the /app and /data folder.
Also: I would like to know if there is a possibility to extract the whole file system using the ADB only.
Thanks in advance!
{
"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"
}

[ERROR] Unpack/Repack ROM SM-G930S (Samsung S7)

I downloaded the ROM from the link below:
[up_vnROM.net]_G930SKSU3ETJ1_G930SSKC3ETJ1_SKC_8.0.zip
drive.google.com
I use this project to unpack/repack on Ubuntu:
GitHub - anestisb/android-simg2img: Tool to convert Android sparse images to raw images
Tool to convert Android sparse images to raw images - GitHub - anestisb/android-simg2img: Tool to convert Android sparse images to raw images
github.com
I execute these commands:
lz4 system.img.lz4 system.img
[email protected]:~$ ./android-simg2img/simg2img system.img system.raw.img
[email protected]:~$ ./android-simg2img/img2simg system.raw.img system.new.img
Click to expand...
Click to collapse
Result file system.img loaded success, but file system.new.img received FAIL result when using Odin.
I noticed something unusual when comparing 2 files:
1. Check file info:
[email protected]:~$ file system*
system.img: Android sparse image, version: 1.0, Total of 1075200 4096-byte output blocks in 5625 input chunks.
system.new.img: Android sparse image, version: 1.0, Total of 1075200 4096-byte output blocks in 3469 input chunks.
system.raw.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents)
Click to expand...
Click to collapse
2. Check simg_dump.py:
[email protected]:~$ ./android-simg2img/simg_dump.py system.img
simg_dump.py: system.img: The file header size was expected to be 28, but is 32.
[email protected]:~$ ./android-simg2img/simg_dump.py system.new.img
system.new.img: Total of 1075200 4096-byte output blocks in 3469 input chunks.
Click to expand...
Click to collapse
3. Open with 7z:
- File system.img
{
"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"
}
- File system.new.img
I used many tools: ext2simg, make_ext4fs to repack but it doesn't work. Looking forward to help.

quangnguyen7616 said:
I downloaded the ROM from the link below:
[up_vnROM.net]_G930SKSU3ETJ1_G930SSKC3ETJ1_SKC_8.0.zip
drive.google.com
I use this project to unpack/repack on Ubuntu:
GitHub - anestisb/android-simg2img: Tool to convert Android sparse images to raw images
Tool to convert Android sparse images to raw images - GitHub - anestisb/android-simg2img: Tool to convert Android sparse images to raw images
github.com
I execute these commands:
lz4 system.img.lz4 system.img
Result file system.img loaded success, but file system.new.img received FAIL result when using Odin.
I noticed something unusual when comparing 2 files:
1. Check file info:
2. Check simg_dump.py:
3. Open with 7z:
- File system.img
View attachment 5811597
- File system.new.img
View attachment 5811599
I used many tools: ext2simg, make_ext4fs to repack but it doesn't work. Looking forward to help.
Click to expand...
Click to collapse
you have too name the system_new.img the same name as stock one was and add back the .ext4 on the end you may also have to turn it back into a sparse image for odin to flash it successfully