Database Users

Anyone with 337a...

Has anyone gotten the L update? I won't get any updates as I'm on prepaid service, but was wondering if it's even available to us or did AT&T just say screw you?

pre4speed said:
Has anyone gotten the L update? I won't get any updates as I'm on prepaid service, but was wondering if it's even available to us or did AT&T just say screw you?
Click to expand...
Click to collapse
It's not available yet. None of the AT&T branded models have gotten an official update yet, not even the 10.1

thisisapoorusernamechoice said:
It's not available yet. None of the AT&T branded models have gotten an official update yet, not even the 10.1
Click to expand...
Click to collapse
Thanks so that's a big SCREW YOU from AT&T. Too busy buying Directv which also sucks.

My AT&T T337A has lollipop. It was OTA upgraded but I have an update.zip you can flash. Now ... can anyone help debrick my device since I went and mucked it up trying to get Viper on it?

uudruid74 said:
My AT&T T337A has lollipop. It was OTA upgraded but I have an update.zip you can flash. Now ... can anyone help debrick my device since I went and mucked it up trying to get Viper on it?
Click to expand...
Click to collapse
Code:
[email protected]:/t-src/Heimdall/bin# ./heimdall download-pit --output pit
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Ending session...
Rebooting device...
Releasing device interface...
dude pm, i haven't tested write yet but if pit spits correct then write should do, thanks @sub77 :good:
Code:
[email protected]:/t-src/Heimdall/bin# file pit
pit: Partition Information Table for Samsung smartphone, 30 entries;
#1 APNHLOS (0x1) "NON-HLOS.bin";
#2 MODEM (0x2) "modem.bin";
#3 SBL1 (0x3) "sbl1.mbn";
#4 DBI (0x4) "sdi.mbn";
#5 DDR (0x5);
#6 ABOOT (0x6) "aboot.mbn";
#7 RPM (0x7) "rpm.mbn";
#8 TZ (0x8) "tz.mbn";
#9 PAD (0x9);
#10 PARAM (0xa);
#11 EFS (0xb) "efs.img.ext4";
#12 MODEMST1 (0xc) "nvrebuild1.bin";
#13 MODEMST2 (0xd) "nvrebuild2.bin";
#14 BOOT (0xe) "boot.img";
#15 RECOVERY (0xf) "recovery.img";
#16 FOTA (0x10); #17 BACKUP (0x11);
#18 FSG (0x12)
[email protected]:/t-src/Heimdall/bin#
seems a bit short, but let me try a write of aboot and see what happens, if it goes good i'll uplload a zip of the heimdall build i'm using and the program sub77 pointed me too.
DAMMIT !!!
Code:
[email protected]:/t-src/Heimdall/bin# ./heimdall flash --ABOOT aboot-6
....
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
WARNING: Setting protocol to 1
Downloading device's PIT file...
PIT file download successful.
Uploading ABOOT
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: ABOOT upload failed!
Ending session...
Rebooting device...
i didn't brick but the write still breaks... grumble
okay when ./heimdall print-pit, this looks odd
Code:
...
...
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 139904
Partition Block Count: 4096
[COLOR="Red"]File Offset (Obsolete): 0
File Size (Obsolete): 0[/COLOR]
Partition Name: ABOOT
Flash Filename: aboot.mbn
FOTA Filename:
...
...
Okay, I'm being stoppped by Qualcomm secure boot Secure check aboot
..dang flabbit.

Droid RAZR M: Qflash Utility Help

QFLASH Problem
What the hell .. squint emoticon
"No data read from USB. This may not be an error. Trying again..."
if anyone knw about it so Guide me .i am very close :|
D:\Downloads\Compressed\Moto.X.Unbrick\Python27>python 8960_blankflash.py
Emergency download enumeration detected on port - com3
Starting qflash!
Executing command qflash.exe -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloa
der_singleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM3
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
Still no data, giving up!
dmss_go : failed to receive ACK
Error loading MPRG8960.hex into device
Blank flashing successful
Device will now enumerate in fastboot mode
D:\Downloads\Compressed\Moto.X.Unbrick\Python27>pause
Press any key to continue . .

Full RAW flash dump

I have replaced new empty eMMC flash memory in change of previous dead one.
Reason: bootloop, google logo, no boot, no fastboot (no LED blinking), device detected only in Intel DNX fastboot (MOOREFIELD):
Code:
New USB device found, idVendor=8086, idProduct=0a2c, bcdDevice= 0.a0
New USB device strings: Mfr=2, Product=1, SerialNumber=3
Product: MOOREFIELD
Manufacturer: INTEL
Instead of android fastboot mode:
Code:
New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice=ff.ff
New USB device strings: Mfr=2, Product=3, SerialNumber=4
Product: fugu
Manufacturer: Android
xFSTK Downloader (used files from ZenFone) doesn't work. Player disconnecting during flashing.
Actually I need partitions dumps or full RAW dump.
Code:
Setting interface to EasyJtag2/E-Socket
Setting bus width to 8 Bit
Setting frequence to 42 MHz
EMMC Device Information :
EMMC CID: 110100303038474530006625C95B71F1
EMMC CSD: D05E00320F5903FFFFFFFFEF924000D3
EMMC Manufacture : TOSHIBA , EMMC NAME: 008GE0 , HEX: 303038474530 , S/N: 6625C95B , rev. 0x00
EMMC Manufacture ID: 0x11 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 7/2014
EMMC ROM 1 (Main User Data) Capacity: 7456 MB (0001D2000000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 KB (000000400000) Counter: 716 , Response: Not Clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.7 (MMC 5.0, MMC 5.01)
Boot configuration [PARTITION_CONFIG]: 0x00 , Boot from: no boot
Boot Bus Config: 0x00 , width 1bit
H/W Reset Function [RST_N_FUNCTION]: 0x00, RST_n signal is temporarily disabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
Backup saved: 008GE0_6625C95B_20191117_171608.extcsd
EMMC Init completed.
Warning: Health report is very BAD
Device Life Time Estimation (MLC) [269]: 0x00 Not defined
Device Life Time Estimation (SLC) [268]: 0x0B Exceeded its maximum estimated device life time
Pre EOL information [267]: 0x01 Normal
Scanning soft partitions
GPT header is found and is valid
Partition: boot, [000000005000 - 000001005000], size: 000001000000 (16,0 MB)
Partition: recovery, [000001005000 - 000002005000], size: 000001000000 (16,0 MB)
Partition: fastboot, [000002005000 - 000003005000], size: 000001000000 (16,0 MB)
Partition: factory, [000003005000 - 000003605000], size: 000000600000 (6,00 MB)
Partition: splashscreen, [000003605000 - 000003A05000], size: 000000400000 (4,00 MB)
Partition: panic, [000003A05000 - 000003E05000], size: 000000400000 (4,00 MB)
Partition: misc, [000003E05000 - 000003F05000], size: 000000100000 (1,00 MB)
Partition: temp, [000003F05000 - 000004F05000], size: 000001000000 (16,0 MB)
Partition: cache, [000004F05000 - 000014F05000], size: 000010000000 (256 MB)
Partition: system, [000014F05000 - 000054F05000], size: 000040000000 (1,00 GB)
Partition: userdata, [000054F05000 - 0001D1FFBE00], size: 00017D0F6E00 (5,95 GB)
GPT header successfully parsed
Dump status:
ROM1 - failed !
ROM2/3 (bootloader = ifwi - 164 bytes ?) - ok
RPMB - ok
Partially I can get boot, recovery, fastboot (droidboot), splashscreen, system from official google firmwares.
But more important is factory partition.
Anyway it would be nice to have full RAW dump.
Thanks.

Hardbricked - flashing fastboot rom doesn't seem to work?

Hi folks,
So my MI 9T was hardbricked when I stopped a flashing mid-process. I'm using a UMT dongle with authorization credits to flash a fastboot rom via EDL mode. According to the flashing software (QCfire v5.1) the process is successful, but the phone won't turn on. Can someone help me out and tell me what I'm doing wrong? Am I flashing the wrong ROM?
Model: M1903F10G
Purchased in Germany
ROM: davinci_eea_global_images_V10.3.15.0.PFJEUXM_20190921.0000.00_9.0_eea
QCfire log:
Operation : Flash
Checking for existing devices...Found
Port : Qualcomm HS-USB QDLoader 9008 (COM10)
Driver Info : Qualcomm Incorporated, qcusbser.sys, 2.1.0.5
Opening Port...OK
Init Handshake Sequence...OK
Hardware ID : E1600E00 [E1600E00] 00007200
OPK_DATA : 4B60244704D721E5B96DD5BB7233886E38F2198FBDE6433FCE1D25A7B0472DD7
Initializing Protocol...OK
Sending Loader [prog_ufs_firehose_sdm855_ddr.elf]...Done
Executing Loader...OK
Auth Enabled Device! You need Mi Auth Account to service!
Reading Auth Blob...OK
Blob : NDE1MTQxNDE0MTQ3MzA0MjQxNDE0Mjc2MzU0RTRGNTE0NDUzNEY0QTRCNTM0QzQ0NjM2ODZBNjE1NzQ3MzAzNTU4NDczNjM5Mzg0MT==
Requesting UMT Server for Auth Data...OK
Credits Left: 0
Authenticating...OK
Detecting Chip Type...OK
Using Alternate Method...
Hardware : E1600E00, UFS, 64 GB
LU Count : 6 [0x00E98800] [0x00000800] [0x00000800] [0x00002000] [0x00040000] [0x0000A000]
WARNING! High Speed Driver is not installed.
Please install driver from QcFire\Drivers folder using Device Manager.
Payload Info : In: 65536 [65536], Out: 1048576, Sector Size: 4096
Writing [dummy.img] -> [switch] ...Done
Writing [misc.img] -> [misc] ...Done
Writing [logfs_ufs_8mb.bin] -> [logfs] ...Done
Writing [vendor.img ] -> [vendor]...Done
Writing [system.img ] -> [system]...Done
Writing [imagefv.elf] -> [imagefv] ...Done
Writing [recovery.img] -> [recovery] ...Done
Writing [cache.img ] -> [cache]...Done
Writing [cust.img ] -> [cust]...Done
Writing [userdata.img ] -> [userdata]...Done
Writing [gpt_main0.bin] -> [PrimaryGPT] ...Done
Writing [gpt_backup0.bin] -> [BackupGPT] ...Done
Applying Patches................Done
Resetting device...Done
Operation Finished.
QcFire Ver. 5.1

Hello !
I'm in the exact same situation as you (hardbricked) but with the global image "davinci_global_images_V10.3.11.0.PFJMIXM_20190802.0000.00_9.0_global".
Could you indicate me how were you able to flash the image through EDL ? Was it using Xiaomi Flash tool ? I tried that and it says that i'm not authorized to do that operation
Thanks in advance !

u can't if u don't have a EDL authorized Account and u won't get one. Unless you pay around $50 for a EDL Flash.

As long as I can fix this expensive paperweight I think that even paying is fine... Do you have the details on how to do it ?

Phone Flash Tool V 4.4.4 does not recognize Lenovo_Yoga_Tablet_2_1050L

hi forum guys, I try to flash firmware on Lenovo_Yoga_Tablet_2_1050L with Phone Flash Tool V 4.4.4. I installed IntelAndroidDrvSetup1.5.0.exe,iSocUSB-Driver-Setup-1.2.0.exe,Phone FlashTool 4.4.4.1, I put tablet in DNX state(I got message "fastboor starting" on the screen, however Phone Flash Tool does not recognize it, this is what I got from logs:
11/09/21 15:47:29.502 INFO : Phone Flash Tool V 4.4.4-1 Win32 External (build on Mon Apr 28 09:56:35 UTC 2014)
11/09/21 15:47:29.502 INFO : Using xFSTK version: 1.5.3
11/09/21 15:47:29.696 INFO : Using Android Debug Bridge version 1.0.31
11/09/21 15:47:29.699 INFO : OS version detected: Windows 8 (x64)
11/09/21 15:47:30.329 INFO : Adb and fastboot binaries OK
11/09/21 15:47:30.333 INFO : Phone Flash Tool initialized successfully
11/09/21 15:47:30.370 INFO : Loading Flash file ...
11/09/21 15:47:30.371 INFO : Ready to flash!
11/09/21 15:47:50.111 INFO : Loading Flash file (D:/02.Android/Yoga tab 2 1050l/Lenovo_Yoga_Tablet_2_1050L_USR_S000215_150324/Lenovo_Yoga_Tablet_2_1050L_USR_S000215_150324/Firmware/flash.xml)
11/09/21 15:47:50.115 INFO : GP_Flag is set to 0x80000045
11/09/21 15:47:50.118 INFO : Ready to flash!
pls help!