This is not for soft bricked devices.
This is for hard bricked devices that cant go into recovery or download mode.
This is for devices on the Version 2 Bootloader like samfail v2 or any normal V2 bootloader.
It may work on other bootloader versions with some modification.
If you have a hard bricked device let me know and I will help you test this.
I don't want to just post the files and have people cause bricks by flashing this to non-v2 bootloaders.
People with other versions of the bootloader and a bricked device let me know and we will test some things.
If you need this let me know and we will do some testing.
How to Unbrick
First you need to install the drivers for QDL.
Option A is to install QPST.
I think then the drivers will automatically install in windows when you connect a device in edl mode.
Or you can manually choose the driver to install if you know how.
I will upload both.
Get the device in EDL mode.
It might go automaticall (hopefully).
If not you need a EDL Cabel or Deep Flash Cable.
Theres instruction around how to make one.
After device is in edl mode and connected to the computer open windows device manager.
Under Ports you should see .
https://photos.app.goo.gl/ibD8KYy9GVQFvJheA
I doubt you will see Portable Devices. I have it because of a special sd card.
After you see Qualcomm-HS-USB QDloader under ports your ready to unbrick.
Copy the N950U2 FOLDER TO C:\ ON YOUR COMPUTER.
Open command prompt as administrator.
In search bar in windows type cmd
Right click on command prompt and run as administrator.
cd to the n950u folder
Code:
cd c:\N950U2
https://photos.app.goo.gl/VzJjwsU6NWLdyDCc6
type
Code:
N950U2_Recovery.bat
You should get this window.
https://photos.app.goo.gl/F7hcuPCCqrci9A1KA
type the com port of your edl device and hit enter.
Be sure to copy the log in the terminal window and save it to share with us later.
Heres the files.
https://www.mediafire.com/file/9bb4vgx1kmir4gz/QPST.2.7.472_2018.zip/file
https://www.mediafire.com/file/eo9wcbtdle1xsc8/Qualcomm_Drivers_QDLoader.zip/file
https://www.mediafire.com/file/dfzy3zo8ibrh1p7/Unbrick-Samsung-Qualcom-9008-Files.zip/file
After the flash completes the phone should boot to download mode.
If not try to boot it to download mode.
Look at secure boot status and all of that when you boot to download mode.
If you dont see it power the device off then reboot into download mode again.
Were looking for any change in the bootloader status.
Maybe the edl bootloader is unlocked.
After that its just normal flash by ODIN back to whater you were on.
PLEASE REPORT BACK YOUR EXPERIENCE WHEN YOU DO THIS.
Note I had screenshots but there not showing. Ill try to fix them. Just Click the links for now.
link not working
can you redo the link for the last download please
lilbowza1985 said:
can you redo the link for the last download please
Click to expand...
Click to collapse
All links are working for me.
If you are going to flash the EDL let me know.
I would be grateful to help you see what the state of the edl bootloader is.
Possibly unlockable!!
Please update to BL v5 if possible.
Hey I just gave it a shot to the steps and it did not work. I think maybe because my n8 has a higher BL version, I think v5 actually. Thanks for the post. Hope you could help out updating the recovery to a BL v5. Here are the logs I got.
Input Port Number[1~300,x:Exit]:10
10
Start Recovery.
emmcdl.exe -p COM10 -f prog_ufs_firehose_8998_ddr.elf -MemoryName ufs -SetActivePartition 1 -x rawprogram0.xml -x rawprogram1.xml -x rawprogram2.xml -x rawprogram3.xml
Version 2.10
Downloading flash programmer: prog_ufs_firehose_8998_ddr.elf
Successfully open flash programmer to write: prog_ufs_firehose_8998_ddr.elf
Expecting SAHARA_END_TRANSFER but found: 0
!!!!!!!! WARNING: Flash programmer failed to load trying to continue !!!!!!!!!
Programming UFS device using SECTOR_SIZE=4096
<?xml version = "1.0" ?><data><configure MemoryName="ufs" ZLPAwareHost="1" SkipStorageInit="0" SkipWrite="0" MaxPayloadSizeToTargetInBytes="1048576"/></data>
ERROR: No response to configure packet
Status: 21 The device is not ready.
Finish!!
I got the same error,
I got the same error.......
Can i use this for g892u rev 3
BigCountry907 said:
All links are working for me.
If you are going to flash the EDL let me know.
I would be grateful to help you see what the state of the edl bootloader is.
Possibly unlockable!!
Click to expand...
Click to collapse
my phone cant turn on,i cant go to recovery mode and download mode,what i must do?
plz help
qban-it-solution said:
Hey I just gave it a shot to the steps and it did not work. I think maybe because my n8 has a higher BL version, I think v5 actually. Thanks for the post. Hope you could help out updating the recovery to a BL v5. Here are the logs I got.
Input Port Number[1~300,x:Exit]:10
10
Start Recovery.
emmcdl.exe -p COM10 -f prog_ufs_firehose_8998_ddr.elf -MemoryName ufs -SetActivePartition 1 -x rawprogram0.xml -x rawprogram1.xml -x rawprogram2.xml -x rawprogram3.xml
Version 2.10
Downloading flash programmer: prog_ufs_firehose_8998_ddr.elf
Successfully open flash programmer to write: prog_ufs_firehose_8998_ddr.elf
Expecting SAHARA_END_TRANSFER but found: 0
!!!!!!!! WARNING: Flash programmer failed to load trying to continue !!!!!!!!!
Programming UFS device using SECTOR_SIZE=4096
<?xml version = "1.0" ?><data><configure MemoryName="ufs" ZLPAwareHost="1" SkipStorageInit="0" SkipWrite="0" MaxPayloadSizeToTargetInBytes="1048576"/></data>
ERROR: No response to configure packet
Status: 21 The device is not ready.
Finish!!
Click to expand...
Click to collapse
i have same problem..
Note 8 Bricked after using COMBINATION_FA71_N950USQU5ARJ1_CL13942288_QB203914 89_REV00
seansha said:
i have same problem..
Click to expand...
Click to collapse
Did you get an answer? I can't find a firmware that will work! I'm totally bricked
I flashed this:
COMBINATION_FA71_N950USQU5ARJ1_CL13942288_QB20391489_REV00_user_mid_noship_MULTI_CERT.tar
And i was bricked after.
m4r20 said:
Did you get an answer? I can't find a firmware that will work! I'm totally bricked
I flashed this:
COMBINATION_FA71_N950USQU5ARJ1_CL13942288_QB20391489_REV00_user_mid_noship_MULTI_CERT.tar
And i was bricked after.
Click to expand...
Click to collapse
I am having the same problem and I was working off of the guide to install EDL and Root the Phone Here: https://forum.xda-developers.com/galaxy-note-8/development/root-t3942403
I have been searching for a way to resolve the same behavior and found this post. I noticed the original Guide I followed did not have me install any Qualcomm drivers, I am HOPING to do so using the ones provided here may fix things.
I am also not really happy with the CMD script they used in both this and the other method, it makes the process harder by using a setp to pause at the end instead of a pause or something obvious and by setting the max lines on the CONsole to 40 which over-flowed my screen, so I had to comment it out. Also not sure why they didn't just list the ports in a menu and have you choose or try to guess for you based off how they get it. But thats just somme griping.
I am HOPINNG that the FACTORY BINARY >>>>>> screen I get to in my phone is "EDL" it's unclear to me from the info on these sites, rooting guides have continued to become less clear over the years assuming everyone knows every step like the back of their hands.
im stuck here too. its like I have no bootloader, and I cant flash. no download mode, no recovery. No light when I plug it in to charge...just upload mode. the phone was on BL 6.
Bricked here as well...Same error with failed to load flash programmer..Still stabbing at it with no results as of yet.
please keep me in the loop
Surgeman said:
Bricked here as well...Same error with failed to load flash programmer..Still stabbing at it with no results as of yet.
Click to expand...
Click to collapse
A lot of people don't listen or read anything and @BigCountry907 specifically said this is for bootloader version 2 and it might work for others with "SOME MODIFICATION" but anyone with common sense would know this isn't going to work on version 5 of the bootloader!!
MrMike2182 said:
A lot of people don't listen or read anything and @BigCountry907 specifically said this is for bootloader version 2 and it might work for others with "SOME MODIFICATION" but anyone with common sense would know this isn't going to work on version 5 of the bootloader!!
Click to expand...
Click to collapse
I beg the differ....I have actually got it to flash using the old bootloader jig for the older Notes..But it won't repair the eMMC portion...
@MrMike
Check PM
Sent from my SM-N975U using Tapatalk
My phone is currently the same. If only I could get into edl mode, it would be fixed. But I don't know how to get into edl mode using only hardware
Can I ask a question. A HOW TO exactly would be awesome. Ok I have Sm-N950U running 7.1.1 you know with the 80% only battery. All runs great. Its the Snapdragon version. HOW can I get it back to before I got it this way. Before I did all this it had.. I forget V6..somthing.
Or can you point me to somewhere that really explains this. Getting it to 7.1.1 seem easy vs now trying to get it back.
Thanks
Hi @BigCountry907, i used your method n950u2 with QFIL on my n950w (N950WVLS7DTA1) by enter EDL mode, but got no luck.
Below is the log of QFIL:
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\KN\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\temp\n950w\UnbrickQC-9008\N950U2\prog_ufs_firehose_8998_ddr.elf
21:19:39: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
21:19:39: ERROR: function: sahara_main:924 Sahara protocol error
21:19:39: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
I also tried with eMMC Dongle app but no luck also.
Loading GUID Partition Table
EMPTY SKIPPING
=> it's mean the main partition is corrupted
Would you mind help me by teaching me the correct way to booting from sdcard then repartition the main Qualcomm’s memory?
The problem of brick: i messed up the Qualcomm’s partition while playing around with "boot.img dqmdbg.img.ext4 storsec.mbn msadp.mbn apdp.mbn sec.dat recovery.img NON-HLOS.bin xbl.elf tz.mbn abl.elf bksecapp.mbn keymaster.mbn cmnlib64.mbn rpm.mbn hyp.mbn cmnlib.mbn devcfg.mbn pmic.elf adspso.bin modem.bin" then flash with Oddin via BL slot.
Many thanks and best regards!
Related
I get this error every time when using htc dev boot unlocker. error: cannot load 'unlock_code.bin'
any ideas please
Is the unlock_code.bin file in the same directory as all the other unlock files?
still wont work
My Unlock_code.bin file is in the same file as the fastboot, yet it still wont load...
UPDATE
FIXED: had to change the directory in Command Prompt from c:\user to the location of the .bin file.
Duckvdm said:
My Unlock_code.bin file is in the same file as the fastboot, yet it still wont load...
UPDATE
FIXED: had to change the directory in Command Prompt from c:\user to the location of the .bin file.
Click to expand...
Click to collapse
finally something worked for me
blackbolo said:
finally something worked for me
Click to expand...
Click to collapse
I have the same problem, exactly like the op posted, but I did change the directory to the same one where the unlock bin file was which also included the 3 files that htcdev.com/bootloader told me to put in there (such as fastboot)
But still doesn't work. In fact I can provide a screenshot clearly showing the directory where the unlock file and other files are, aswell as my command prompts and errors.
Please help me don't disregard my post : P I have been trying to figure this out for hours, I even called htcdev support and they couldn't help, told me to ask in forums LOL? why is there a support number if they won't help?
pontypool said:
I have the same problem, exactly like the op posted, but I did change the directory to the same one where the unlock bin file was which also included the 3 files that htcdev.com/bootloader told me to put in there (such as fastboot)
But still doesn't work. In fact I can provide a screenshot clearly showing the directory where the unlock file and other files are, aswell as my command prompts and errors.
Please help me don't disregard my post : P I have been trying to figure this out for hours, I even called htcdev support and they couldn't help, told me to ask in forums LOL? why is there a support number if they won't help?
Click to expand...
Click to collapse
*facepalm* Um Sir, if your fastboot, adb, and UNLOCK_TOKEN files are all in the folder "aaa" why are you directing your command prompts to the non-existent "abd" folder? In your case the very first thing you should be typing into the command prompt is: cd E:\aaa Now you can actually execute fastboot commands because that is where all the files are.
JnNn98 said:
*facepalm* Um Sir, if your fastboot, adb, and UNLOCK_TOKEN files are all in the folder "aaa" why are you directing your command prompts to the non-existent "abd" folder? In your case the very first thing you should be typing into the command prompt is: cd E:\aaa Now you can actually execute fastboot commands because that is where all the files are.
Click to expand...
Click to collapse
my mistake. i had two folders aaa and abd with identical files. but the error still remains nevertheless, as seen in the new screenshot
it's just a stupid mistake of mine. i didnt put the CD part in.. i assume that was for people who had the files on a cd.
* walks away in shame *
pontypool said:
my mistake. i had two folders aaa and abd with identical files. but the error still remains nevertheless, as seen in the new screenshot
it's just a stupid mistake of mine. i didnt put the CD part in.. i assume that was for people who had the files on a cd.
* walks away in shame *
Click to expand...
Click to collapse
So does it work now? BTW "cd" is just something you would type when you have to change the directory in the cmd, it actually has nothing to do with actual CD's (Compact Discs)
---------- Post added at 03:38 PM ---------- Previous post was at 03:22 PM ----------
pontypool said:
my mistake. i had two folders aaa and abd with identical files. but the error still remains nevertheless, as seen in the new screenshot
it's just a stupid mistake of mine. i didnt put the CD part in.. i assume that was for people who had the files on a cd.
* walks away in shame *
Click to expand...
Click to collapse
So does it work now? BTW "cd" is just something you would type when you have to change the directory in the cmd, it actually has nothing to do with actual CD's (Compact Discs)
JnNn98 said:
So does it work now? BTW "cd" is just something you would type when you have to change the directory in the cmd, it actually has nothing to do with actual CD's (Compact Discs)
---------- Post added at 03:38 PM ---------- Previous post was at 03:22 PM ----------
So does it work now? BTW "cd" is just something you would type when you have to change the directory in the cmd, it actually has nothing to do with actual CD's (Compact Discs)
Click to expand...
Click to collapse
yes it works now. I realise now, but at the time I assumed it was a suggested directory if the files are stored on a cd.
Unknown error
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
E:\Documents and Settings\MovilSol#2\Desktop>fastboot flash unlocktoken unlock_code.bin
error: cannot load 'unlock_code.bin': Unknown error
Please help me! D:
That should be a capital U in Unlock_code.bin
Sent from my Evo 3D CDMA using xda premium
xion009 said:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
E:\Documents and Settings\MovilSol#2\Desktop>fastboot flash unlocktoken unlock_code.bin
error: cannot load 'unlock_code.bin': Unknown error
Please help me! D:
Click to expand...
Click to collapse
Try to generate the Unclock_code.bin from htcdev website again.
Replace the new file in the fastboot directory . It should work .
XDA-Dev. said:
Try to generate the Unclock_code.bin from htcdev website again.
Replace the new file in the fastboot directory . It should work .
Click to expand...
Click to collapse
I already tried to generate the unlock_code.bin alot of times in htcdev and none works /:
error
Duckvdm said:
My Unlock_code.bin file is in the same file as the fastboot, yet it still wont load...
UPDATE
FIXED: had to change the directory in Command Prompt from c:\user to the location of the .bin file.
Click to expand...
Click to collapse
yes thanks for that mate was getting same eror so i dropped the 2 files into the path that command prompt was displaying
Help Im having the same problem
Im using a window pc runing windows 8. I have done everthing gotten the .bin file and now i get cannot load 'unlock_code.bin
Thank you! This fixed my issue, though it was a small blow to my ego (seems obvious in retrospect). Still having trouble actually rooting my phone, but at least I'm closer now?
Use kingoroot in fastboot mode no need unlock code.bin
Try it
Can't get my Unlock_code.bin to initiate
I have all my files in one folder and I still cannot get this last step to initiate and I am meet with the following
Johns-MacBook-Pro:~ johnsummersjr$ Users/johnsummersjr/Desktop/Android/fastboot flash unlocktoken Unlock_code.bin
-bash: Users/johnsummersjr/Desktop/Android/fastboot: No such file or directory
Johns-MacBook-Pro:~ johnsummersjr$
/Users/johnsummersjr/Desktop/Screen Shot 2015-11-30 at 9.59.55 PM.png
HTC BootLoader Via Macbook pro
JohnSnow2015 said:
I have all my files in one folder and I still cannot get this last step to initiate and I am meet with the following
Johns-MacBook-Pro:~ johnsummersjr$ Users/johnsummersjr/Desktop/Android/fastboot flash unlocktoken Unlock_code.bin
-bash: Users/johnsummersjr/Desktop/Android/fastboot: No such file or directory
Johns-MacBook-Pro:~ johnsummersjr$
/Users/johnsummersjr/Desktop/Screen Shot 2015-11-30 at 9.59.55 PM.png
Click to expand...
Click to collapse
UPDATE 12/3/15
I got everything into one directory and entered: /Users/johnsummersjr/Desktop/HTC\ Unlock\ BootLoader/adt-bundle-mac-x86_64-20140321/sdk/platform-tools/fastboot unlocktoken Unlock_code.bin. Yet I am met with the following
Johns-MacBook-Pro:~ johnsummersjr$ /Users/johnsummersjr/Desktop/HTC\ Unlock\ BootLoader/adt-bundle-mac-x86_64-20140321/sdk/platform-tools/fastboot unlocktoken Unlock_code.bin
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
Fixed
cal4877 said:
I get this error every time when using htc dev boot unlocker. error: cannot load 'unlock_code.bin'
any ideas please
Click to expand...
Click to collapse
use fastboot folder provided by htc
you can find it on htc site
first select your device for unlocking bootloder then on next page there have given steps 1,2,3..
on the last there will be fastboot downloading links :good:
It will absolutely solve your problem
Hi there,
i have a following problem:
One of our Clients, bought in February last year three Dell Streak 5, which ones after it entirely until August, in a drawer stored. These would have liked being put to use in a September, but their starting it, O2 his software being a filling attribute came forward, since then though only an, the pictogram indicating the mistake of the battery (red, cross out battery).
The distributor received that answer in the course of the procedure under guarantee from Dell, that the software of the phone was modified, his guarantee was rejected though because of this.
I would add it to it, at this client hard-to-imagine, that let anybody reach into things like this.
The distributor's administrator added so much to it that he does not have a solution for the problem, so all three telephones, never-used, turned into a brick.
From among the telephones I tried to put one right, Streakflash, concerned QDL tool, this single telephone signals the process of the filling on the one hand since then, on the other hand in the course of a boot at Dell logo stops.
The QDL tool stops with this error:
"Wait for ADB device .........
ERROR[D2]: wait ADB fastboot mode timeout!
Please check that device is exist and driver is properly installed.
Download Fail! - 2011/12/18 01:02:51"
I can't turn on the recovery mode, and the fastboot mode, these methods are unavailable.
Thank You for the ideas, helps.
Little supplement:
models:
UMTS900/2100 EDGE/GSM 850/900/1800/1900
model no: M01M
PPID: CN-0WK2PN-74261-07O-00I9-A00
I don't have a solution for you, but I have a couple of questions that might help someone else answer:
1) Is there something wrong with the innerSD? You mentioned it in the title, but I didn't see a reference within your post.
2) Are you sure your battery is charged/charging? If it isn't I don't think you can ADB.
Lastly, I do not know warranty information in Europe, but I thought in the US it was a 1 year, might want to try sending them into Dell!
which version of qdltool did you use?
i beleive from the log youve shown us you used 2.7.4.8?? or something along those lines?
if you use version 2.7.4.5 it should install and repair the boot image, without the "waiting for adb" command
Please use the Q&A Forum for questions Thanks
Moving to Q&A
streakflash.zip – This version of the QDLTool is used to recover semi-bricked Streaks. Search the forums and read before using. If you need this you are in trouble and research will aid you more than haste. Usually recovering your Streak with this involves a successful run of this tool then the QDLTool to 309.
qdtool-to-309-repairtool.zip – this version of the QDLTool will install the baseband 309 ROM on your Streak
These files are also available here.
marvin02, thanks for putting that reply in there i wouldve done that myself, but have no idea hot to put the links in like you do lol
Okay, thank You.
But.
I obtained these files earlier already, tested. Unfortunately, the QDLtool-howto pdf (AndroidUSBDriverUserGuide.pdf) for me not unambiguous, the telephone does not restart during QDLtool (the streakflash ran down perfectly), that let as 'ADB' recognise it.
If it could be asked for getting a step-by-step tutorial?
Let us put it up, freshly installed Windows XP, and I did not install a driver yet for this phone.
The QDLTool log:
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Mon Jan 02 21:38:39 2012
Check image DBL: C:\!STREAK\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: C:\!STREAK\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: C:\!STREAK\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: C:\!STREAK\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: C:\!STREAK\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: C:\!STREAK\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: C:\!STREAK\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: C:\!STREAK\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: C:\!STREAK\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: C:\!STREAK\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: C:\!STREAK\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: C:\!STREAK\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: C:\!STREAK\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device .........
ERROR[D2]: wait ADB fastboot mode timeout!
Please check that device is exist and driver is properly installed.
Download Fail! - 2012/01/02 21:39:09
Elapsed Time: 29.51 sec
Thank You for helping me.
ok from that log youre using 2.7.4.8, you need to use qdl tool version 2.7.4.5 as this doesnt ask for the adb connection at the end which is where your failing,
the post above by marvin02 has links to streakflash.zip download that, and flash your streak with that and it should repair it
Yes, i already tried same the 2.7.4.8, as the 2.7.4.5.
Both versions ends with green, but after, the phone still at the previous state, only dell logo, and when i charge with the wall charger, shows the graphic battery logo.
Only the volume up-press-and-attach-to-computer story works, in this case, computer shows as qualcomm device, and can be installed as Qualcomm HS-USB Diagnostics 9002 device.
kovacsbela said:
Yes, i already tried same the 2.7.4.8, as the 2.7.4.5.
Both versions ends with green, but after, the phone still at the previous state, only dell logo, and when i charge with the wall charger, shows the graphic battery logo.
Only the volume up-press-and-attach-to-computer story works, in this case, computer shows as qualcomm device, and can be installed as Qualcomm HS-USB Diagnostics 9002 device.
Click to expand...
Click to collapse
Sounds like the proper driver is installed. What version of Windows are you using? IIRC QDLTool seemed to work for more people using WinXP. Also try removing all reference to the drivers (including registry entries and all old files) and reinstalling them from scratch. Remove any other similar drivers from the computer used. You may also want to try remove the external Sd card while using QDLTool. Other suggestions are to make sure that you are connected to a USB port that is directly wired to the motherboard (no hubs), use a OEM Streak USB cable, and try both USB 2 and slower USB ports is available (timing issue?).
I don't know if the internal SD Card would cause this issue, but it might be worth a try to replace it. This thread has some related info. I have Clonezilla images available here for both BB 360 and BB 406.
Thanks, i will try the recover under a fresh installed XP,
Before, i tried all your propositions, ideas, with no results.
The distributor's service technician will help me with two inner cards, these are come from damaged and rollouted european version of Streaks.
any luck
hi, just wanted to know if you managed to get a solution. i am having the same problem in that with my device initially, just the three lights were coming on. now, nothing comes on any more and the QDL tool stops at this:
###QDLTool: M 2.7.4.5, build ID: 1.302.20100910, time stamp: Thu Mar 15 04:28:58 2012
Check image DBL: C:\Users\shelay\Downloads\streakflash\streakflash\images\dbl.mbn ...
Check image FSBL: C:\Users\shelay\Downloads\streakflash\streakflash\images\fsbl.mbn ...
Check image OSBL: C:\Users\shelay\Downloads\streakflash\streakflash\images\osbl.mbn ...
Check image AMSS: C:\Users\shelay\Downloads\streakflash\streakflash\images\amss.mbn ...
Check image DSP1: C:\Users\shelay\Downloads\streakflash\streakflash\images\dsp1.mbn ...
Check image APPSBL: C:\Users\shelay\Downloads\streakflash\streakflash\images\appsboot.mbn ...
Check image DT: C:\Users\shelay\Downloads\streakflash\streakflash\images\DT.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#AMSS to DDR success
#DSP1 to DDR success
#DT to DDR success
#APPSBL to DDR success
#backup FSBL to DDR success
#backup OSBL to DDR success
#backup DT to DDR success
#backup APPSBL to DDR success
ERROR[D14]: Run HEX Failed!
ERROR: Download fail!
Please remove the battery and try again.
Wait for modem set up ......
Download Fail! - 2012/03/15 04:35:28
Elapsed Time: 389.90 sec
i tried taking out the battery and all that but no luck. i have ordered a new battery so will give it another go when the new battery gets here. i also took out the internal memory card and replaced with a Scandik 2gb but no luck. i would appreciate any help as my streak is as good as new cosmetically.
innerSD360.zip
marvin02 said:
Sounds like the proper driver is installed. What version of Windows are you using? IIRC QDLTool seemed to work for more people using WinXP. Also try removing all reference to the drivers (including registry entries and all old files) and reinstalling them from scratch. Remove any other similar drivers from the computer used. You may also want to try remove the external Sd card while using QDLTool. Other suggestions are to make sure that you are connected to a USB port that is directly wired to the motherboard (no hubs), use a OEM Streak USB cable, and try both USB 2 and slower USB ports is available (timing issue?).
I don't know if the internal SD Card would cause this issue, but it might be worth a try to replace it. This thread has some related info. I have Clonezilla images available here for both BB 360 and BB 406.
Click to expand...
Click to collapse
Hi can you send me these files? innerSD360.zip for Dell Streak 5 2 GB sd card.
@matrixablade: You might want to PM marvin. He hasn't frequented this forum in over a year now and won't be seeing your request.
Strephon Alkhalikoi said:
@matrixablade: You might want to PM marvin. He hasn't frequented this forum in over a year now and won't be seeing your request.
Click to expand...
Click to collapse
I do check in once in a while, but who knows when I'll stop popping in.
I did get matrixblade's PM.
Simple af. Just short them.
{
"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"
}
For incase that doesn't work;
One question can we make lg g6 go to edl mode using edl cable? I don't want to open the device and make a mess
Ashley david said:
One question can we make lg g6 go to edl mode using edl cable? I don't want to open the device and make a mess
Click to expand...
Click to collapse
I tried it (shorting GND with DATA -) not working.
badmaan said:
Simple af. Just short them.
For incase that doesn't work;
Click to expand...
Click to collapse
It works! My phone was 100% dead and now I am in Qualcomm 9008 mode! (using the test points under the flash)
unfortunately it seems to be another dead path with this phone. No firehose and no xml to flash with QFIL
I have hoses but i don't think any are the proper ones. I can get my software/hardware to load some but not perform any operations with one hose and the other nothing at all.
try using the firehose from here. https://forum.xda-developers.com/t/lg-g6-unbrick-new-method.3935924/
i had been given a dead G6 no partitions (fried) and none of the tools work for reflashing. found a bunch of tools to use in Linux since the drivers/windows kept reseting the connection every time i plugged in and was getting no response so it always ended up in failure. (Note if really is dead bricked as mine was you literally have to pull the pins and get back to edl using the test points every time for each operation as it resets and stops responding after each)
Managed to create proper rawprogram0-6.xml using https://github.com/ANEP-ET/kdztools
unkdz -f myfile.kdz -x
undz -f kdzextracted/myfile.dz -c
undz -f kdzextracted/myfile.dz -r
(creates rawprogram xml files for each primary_gpt file you likely have)
cp rawprogram*.xml dzextracted/
make sure to edit all the separate rawprogram files and edit the files to match the letters associated with the extracted files in dzextracted.
for example in rawprogram1.xml prefix all the files listed in there with B.
for rawprogram2.xml prefix all the files listed in there with C.
and so on. BUT do not rename the first file, rawprogram0.xml does not need to append A. to it as the first one did not get created as such.
tried this tool where it was getting the phone was getting detected properly and the programmer file was uploaded but it was iffy to get it to do anything but cool tool and lots of programmer files with it https://github.com/bkerler/edl
what finally worked with my newly created rawprogam files and the programm was using Qualcoms qdl tool (requires compiling it in Linux, port on github) from here https://github.com/andersson/qdl
by doing
qdl --storage ufs prog_ufs_firehose_lge_g6.elf rawprogram0.xml
and repeat for all the rawprogram files 0 through 6 (or however many there was autogenerated) you generated from above making sure to pull the battery and force it back into edl mode if its reseting the connection afterward like it did for me. Note the name for the firehose there might be something else for you just replace the name with the right file.
Oh i forgot that you probably need to patch the kdztools from https://github.com/ANEP-ET/kdztools because it may fail on newer files the PR for the patch is on the patch already on there a PR #1 @ https://github.com/ANEP-ET/kdztools/pull/1
Lastly before i forget this as well run qdl from within the dzextracted directory so i can find all the bin/image files enumerated in the rawprogram xml files that you copied over into and flash them properly.
draekko said:
try using the firehose from here. https://forum.xda-developers.com/t/lg-g6-unbrick-new-method.3935924/
i had been given a dead G6 no partitions (fried) and none of the tools work for reflashing. found a bunch of tools to use in Linux since the drivers/windows kept reseting the connection every time i plugged in and was getting no response so it always ended up in failure. (Note if really is dead bricked as mine was you literally have to pull the pins and get back to edl using the test points every time for each operation as it resets and stops responding after each)
Managed to create proper rawprogram0-6.xml using https://github.com/ANEP-ET/kdztools
unkdz -f myfile.kdz -x
undz -f kdzextracted/myfile.dz -c
undz -f kdzextracted/myfile.dz -r
(creates rawprogram xml files for each primary_gpt file you likely have)
cp rawprogram*.xml dzextracted/
make sure to edit all the separate rawprogram files and edit the files to match the letters associated with the extracted files in dzextracted.
for example in rawprogram1.xml prefix all the files listed in there with B.
for rawprogram2.xml prefix all the files listed in there with C.
and so on. BUT do not rename the first file, rawprogram0.xml does not need to append A. to it as the first one did not get created as such.
tried this tool where it was getting the phone was getting detected properly and the programmer file was uploaded but it was iffy to get it to do anything but cool tool and lots of programmer files with it https://github.com/bkerler/edl
what finally worked with my newly created rawprogam files and the programm was using Qualcoms qdl tool (requires compiling it in Linux, port on github) from here https://github.com/andersson/qdl
by doing
qdl --storage ufs prog_ufs_firehose_lge_g6.elf rawprogram0.xml
and repeat for all the rawprogram files 0 through 6 (or however many there was autogenerated) you generated from above making sure to pull the battery and force it back into edl mode if its reseting the connection afterward like it did for me. Note the name for the firehose there might be something else for you just replace the name with the right file.
Click to expand...
Click to collapse
Good to hear that there is some hope, i bricked my G6 (h870) 2 months ago while in download mode the laptop turn off. I tried the new unbricked method but got same issue of connection reset. Will try this and update. Also can you share rawprogram xmls please.
kurogami555 said:
Good to hear that there is some hope, i bricked my G6 (h870) 2 months ago while in download mode the laptop turn off. I tried the new unbricked method but got same issue of connection reset. Will try this and update. Also can you share rawprogram xmls please.
Click to expand...
Click to collapse
Nope it was an H873 canadian model. You can make your own using the kdz for your model as i described though.
draekko said:
try using the firehose from here. https://forum.xda-developers.com/t/lg-g6-unbrick-new-method.3935924/
i had been given a dead G6 no partitions (fried) and none of the tools work for reflashing. found a bunch of tools to use in Linux since the drivers/windows kept reseting the connection every time i plugged in and was getting no response so it always ended up in failure. (Note if really is dead bricked as mine was you literally have to pull the pins and get back to edl using the test points every time for each operation as it resets and stops responding after each)
Managed to create proper rawprogram0-6.xml using https://github.com/ANEP-ET/kdztools
unkdz -f myfile.kdz -x
undz -f kdzextracted/myfile.dz -c
undz -f kdzextracted/myfile.dz -r
(creates rawprogram xml files for each primary_gpt file you likely have)
cp rawprogram*.xml dzextracted/
make sure to edit all the separate rawprogram files and edit the files to match the letters associated with the extracted files in dzextracted.
for example in rawprogram1.xml prefix all the files listed in there with B.
for rawprogram2.xml prefix all the files listed in there with C.
and so on. BUT do not rename the first file, rawprogram0.xml does not need to append A. to it as the first one did not get created as such.
tried this tool where it was getting the phone was getting detected properly and the programmer file was uploaded but it was iffy to get it to do anything but cool tool and lots of programmer files with it https://github.com/bkerler/edl
what finally worked with my newly created rawprogam files and the programm was using Qualcoms qdl tool (requires compiling it in Linux, port on github) from here https://github.com/andersson/qdl
by doing
qdl --storage ufs prog_ufs_firehose_lge_g6.elf rawprogram0.xml
and repeat for all the rawprogram files 0 through 6 (or however many there was autogenerated) you generated from above making sure to pull the battery and force it back into edl mode if its reseting the connection afterward like it did for me. Note the name for the firehose there might be something else for you just replace the name with the right file.
Click to expand...
Click to collapse
Good solid info. Thanks
draekko said:
try using the firehose from here. https://forum.xda-developers.com/t/lg-g6-unbrick-new-method.3935924/
i had been given a dead G6 no partitions (fried) and none of the tools work for reflashing. found a bunch of tools to use in Linux since the drivers/windows kept reseting the connection every time i plugged in and was getting no response so it always ended up in failure. (Note if really is dead bricked as mine was you literally have to pull the pins and get back to edl using the test points every time for each operation as it resets and stops responding after each)
Managed to create proper rawprogram0-6.xml using https://github.com/ANEP-ET/kdztools
unkdz -f myfile.kdz -x
undz -f kdzextracted/myfile.dz -c
undz -f kdzextracted/myfile.dz -r
(creates rawprogram xml files for each primary_gpt file you likely have)
cp rawprogram*.xml dzextracted/
make sure to edit all the separate rawprogram files and edit the files to match the letters associated with the extracted files in dzextracted.
for example in rawprogram1.xml prefix all the files listed in there with B.
for rawprogram2.xml prefix all the files listed in there with C.
and so on. BUT do not rename the first file, rawprogram0.xml does not need to append A. to it as the first one did not get created as such.
tried this tool where it was getting the phone was getting detected properly and the programmer file was uploaded but it was iffy to get it to do anything but cool tool and lots of programmer files with it https://github.com/bkerler/edl
what finally worked with my newly created rawprogam files and the programm was using Qualcoms qdl tool (requires compiling it in Linux, port on github) from here https://github.com/andersson/qdl
by doing
qdl --storage ufs prog_ufs_firehose_lge_g6.elf rawprogram0.xml
and repeat for all the rawprogram files 0 through 6 (or however many there was autogenerated) you generated from above making sure to pull the battery and force it back into edl mode if its reseting the connection afterward like it did for me. Note the name for the firehose there might be something else for you just replace the name with the right file.
Click to expand...
Click to collapse
Ok, so i tried this method in Ubuntu but Qdl just waits for EDL device nothing happens. I check the attached usb devices there it shows that Qualcomm 9008 is connected but Qdl script doesn't detect it. Some help please.
kurogami555 said:
Ok, so i tried this method in Ubuntu but Qdl just waits for EDL device nothing happens. I check the attached usb devices there it shows that Qualcomm 9008 is connected but Qdl script doesn't detect it. Some help please.
Click to expand...
Click to collapse
did you reset the device by pulling the battery and putting it back into edl mode for each time you ran qdl? if you don't it won't work as the connect resets every time and will stop communicating after each command sent. Also make sure you have the right programmer file.
draekko said:
did you reset the device by pulling the battery and putting it back into edl mode for each time you ran qdl? if you don't it won't work as the connect resets every time and will stop communicating after each command sent. Also make sure you have the right programmer file.
Click to expand...
Click to collapse
yes, i removed battery again and again short circuited the edl pin the device immediately gets detected as Qualcomm 9008 in usb list but the Qdl script still shows waiting for Edl device.
If you use the programmer file with this tool at https://github.com/bkerler/edl does it show the cpu/serialnumbers/other info when trying to get a partitions list or other commands? If not either the programmer file is wrong or the device is too dead to respond.
draekko said:
If you use the programmer file with this tool at https://github.com/bkerler/edl does it show the cpu/serialnumbers/other info when trying to get a partitions list or other commands? If not either the programmer file is wrong or the device is too dead to respond.
Click to expand...
Click to collapse
what command should i run to check if the firehose is good or not ?
kurogami555 said:
what command should i run to check if the firehose is good or not ?
Click to expand...
Click to collapse
try anything that reads data, try printpgt for example. If it doesn't list the cpu type and serial number it means you have the wrong programmer file for your device. Note that it may fail to actually print any data as it failed on mine but will show the SN/cpu information with the right one.
draekko said:
try anything that reads data, try printpgt for example. If it doesn't list the cpu type and serial number it means you have the wrong programmer file for your device. Note that it may fail to actually print any data as it failed on mine but will show the SN/cpu information with the right one.
Click to expand...
Click to collapse
Sorry for this but i don't get how to use this edl script it's too complicated. Can you please check whether the firehose i attached is good or not. Please.
kurogami555 said:
Sorry for this but i don't get how to use this edl script it's too complicated. Can you please check whether the firehose i attached is good or not. Please.
Click to expand...
Click to collapse
I can't do that the phone is sealed up now and can't be thrown back into edl mode.
Try the loaders github repo for edl, 0005f0e100310000_2cf7619a278d2607_fhprg_peek.bin should theoretically be the right one. https://github.com/bkerler/Loaders
If you install the edl tool per instructions it should include that file as well.
If that fails might be totally bricked or require one of the boxes to revive it.
draekko said:
I can't do that the phone is sealed up now and can't be thrown back into edl mode.
Try the loaders github repo for edl, 0005f0e100310000_2cf7619a278d2607_fhprg_peek.bin should theoretically be the right one. https://github.com/bkerler/Loaders
If you install the edl tool per instructions it should include that file as well.
If that fails might be totally bricked or require one of the boxes to revive it.
Click to expand...
Click to collapse
What I do not understand is that how to use firehose in that EDl script. After I connect the phone in edl mode than what ?
I'm looking to pinout both test pins. I bought this phone a few days ago. I unlocked it with TWRP, I looked at the possibilities. I made a mistake with TWRP by switching the system to sideload B (I chose between A and B) and the system refused to start. I do not have access to the bootloader with the buttons. I only enter QDLoader HS-USB Driver mode working. I read the instructions on how to make a blank flash. I took the 18 files out of the phone and made a new blank flash for this model - moto g9 power / but in the end it gives me an error. Now I'm looking for a solution. - "C: \ Documents and Settings \ Administrator \ Desktop \ MOTO G9 POWER blankflash \ Blankflash for G9 POWER>. \ Qboot.exe blank-flash Motorola qboot utility version 3.86 [0.000] Opening device: \\. \ COM4 [0.000] Detecting device [0.000] ... cpu.id = 333 (0x14d) [0.000] ... cpu.sn = 2936128399 (0xaf01c38f) [0.000] Opening singleimage [0.000] Loading package [0.000] ... filename = pkg.xml [0.000] Loading programmer [0.000] ... filename = programmer.elf [0.000] Sending programmer [0.156] Handling things over to programmer [0.156] Identifying CPU version [0.156] Waiting for firehose to get ready [3.297] ... SM_KAMORTA_H 1.0 [3.297] Determining target secure state [3.297] ... secure = yes [3.375] Configuring device ... [3.391] Flashing GPT ... [3.391] Flashing partition with gpt.bin [3.406] Initializing storage [3,484] ... blksz = 512 [37.016] Re-initializing storage ... [37.016] Initializing storage [37328] Flashing bootloader ... [37.344] Flashing abl_a with abl.elf [37.344] partition abl_a not found! [37.359] ERROR: do_package () -> do_recipe () -> do_flash () -> pt_find () -> not found [37.375] Check qboot_log.txt for more details [37.375] Total time: 37.375s FAILED: qb_flash_singleimage () -> do_package () -> do_recipe () -> do_flash () -> pt_find () -> not found "the last message puzzles me. I want to transfer the system to sideload A again, so I have to reset the device firmly. Are there people familiar with the possibilities?
2 I built a blankflash for the Moto G8
1 How To Blank Flash & Fix/Repair Hard Bricked Motorola Devices/Moto G8+|Tutorial Get It Working Again - YouTube
Version Bootloader MBM-3.O-cebu retail 232f3ba894-201209
motostockrom.com/motorola-moto-g9-power-xt2091-3
I'm looking to pinout both test pins.
Have you tried using LMSA?
It recovered a dead phone for me once.
Rescue and Smart Assistant (LMSA)
Also, I too once accidentally switched slot to B, and system didn't boot. However, I was able to get into fastboot mode and switch by entering the command to switch slots.
https://support.lenovo.com/bg/en/downloads/ds101291 i saw this but my computer is 32 bit / i am looking for the program qualcomm edl mode flash tool or something like Axon10Pro_ (More) _EDL_Tools_v1.1d because i want to make active a siteloader because i saw that this can be done not so difficult otherwise for edl pinout I saw how it works and no problem
man88nam said:
https://support.lenovo.com/bg/en/downloads/ds101291 i saw this but my computer is 32 bit / i am looking for the program qualcomm edl mode flash tool or something like Axon10Pro_ (More) _EDL_Tools_v1.1d because i want to make active a siteloader because i saw that this can be done not so difficult otherwise for edl pinout I saw how it works and no problem
Click to expand...
Click to collapse
qualcomm edl mode flash tool / Axon10Pro_ (More) _EDL_Tools_v1.1d
In those .XML files, can you delete the line that says "abl" and try again?
I will do, but these files can be downloaded according to the instructions on how to make closed files extracted from the phone itself
https://www.reddit.com/r/MotoG/comments/k73n66
I downloaded from the bootloader 18 files that are original, this is in connection with blank flash, where in the end there is an error, because eight made active "B" sector instead of A
I removed the ABL file from the XML, but the error remains, plus the message for a missing ABL file ELF
[ 37.297] file abl.elf not found in singleimage.bin!
[ 37.297] ERROR: do_package()->do_recipe()->do_flash()->not found
[ 37.297] Check qboot_log.txt for more details
[ 37.297] Total time: 37.297s
I'm just looking for an EDL program that works similar to this command line Set Bootable Partition- Slot A / run_AB-partition-swap - but here it wants some text file for the presence of a port, port_trace.txt
I'm sorry, I can't help further here. Even though the active slot is B, the partition abl_a should exist and should be flashable regardless. It looks as though there isn't such a partition at all, which I don't even know how that happened.
The tool which you are using is correct, it's doing its job properly. Are you sure you have the right firmware version and software channel? Because bootloader.img differ depending on the firmware version and the carrier. I'd also suggest downloading from https://mirrors.lolinet.com/firmware/moto/cebu/official/, instead of the link you mentioned, motostockroms.
Also, try asking in this Telegram group: https://t.me/lolinet. There are people on there who are more knowledgeable, maybe they can help.
After trying the firmware image from lolinet and trying the process again with that firmware, I'd try to get into bootloader mode once again through power buttons, and if that doesn't work, send the phone into the service center.
Motorola_Moto_G9_Power_XT2091-3_RETUK_CEBU_RETAIL_QZC30.Q4-22-57_10_by_(motostockrom.com) With the TWRP program I chose with active slot B / I don't know if it deleted the content from slot A of the bootloader. By the way, I downloaded the original product firmware XT2091-3 according to the instructions for this, which I get when I try blank flash / I have no idea what to do, so I'm looking for a program "qualcomm edl mode flash tool" and I constantly get Indian sites with dangerous behavior.
I thank you for your time
Hey,
Today I found EDL points for Moto G9 power. Infact im also facing firmware issue.
I accidentally locked bootloader with stockrom again trying to unlock but not working.
Causing No valid OS to boot.
if i try unlock again showing message like " enable OEM unlocking in developer options"
unfortunately not podsible. But still waiting for proper EDL flash tool.
feel free to guide if any one got resolution.
Hi everyone, this is a short guide on how to flash a GSI on the A7 Lite (without TWRP).
Its a nice little tablet for the price but it doesn't have a very powerful SOC and for me the One UI is barely usable on this device. The launcher and the whole system UI feel extremely laggy, but apps generally run fine.
I tried phhusson's custom Android 12 GSI and the device was almost resurrected. Much much less UI lag and the battery life is the same as stock ROM. The only thing i found not working is MTP but i don't need it.
Since i saw a couple users here asking about GSIs i decided to make a very simple guide.
As always do this at your own risk. You may brick your device. You will void your warranty.
Follow the guide only if you know what your are doing. Read each step carefully and avoid copy pasting stuff randomly.
I won't go deep into details as i believe you should have some basic knowledge if you decide to do this.
The procedure sould work for both T220 and T225 (i tested it on a T220).
I did this on Windows using WSL for some of the steps.
Sources
Thanks to @kkoo and @Brepro1 for the useful info
- https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/
- https://forum.xda-developers.com/t/...r-img-and-flashing-our-modifications.4196625/
Requirements
- Unlocked bootloader
If you haven't done this already follow the steps in parts 1-2 from:
[TUTORIAL] How To Unlock & Root Tab A7 Lite T220/T225, & Install LSPosed, Magisk, Mods
While some of these instructions are copied from other sources, I combined all the different things I learned, because no one guide was sufficient, and all needed additional info, so I expanded it all to one place. Part I is partly from...
forum.xda-developers.com
- Latest official ROM
I used T220XXU1AVE1 for EUX region
Samsung Galaxy Tab A7 Lite Firmware Download SM-T220 Free Download
Samsung Galaxy Tab A7 Lite Firmware Download SM-T220 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
- Download your preferred GSI
I used AOSP 12.1 v414 with gapps from phhusson
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
- Clean vbmeta.img from Google
https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Tools
- lz4
Releases · lz4/lz4
Extremely Fast Compression algorithm. Contribute to lz4/lz4 development by creating an account on GitHub.
github.com
- simg2img
[DEV][Tools] simg2img for Windows
Hello, although I'm working in Linux (VM too) I rewrote the SIMG2IMG so far for Windows (PE32, x86) Usage: simg2img.exe -i -o Optional: -d for debugging messages, listing all chunks of the image...
forum.xda-developers.com
- lpunpack and lpmake
[GUIDE] OTA Tools LPUnpack
Please see this URL https://android.googlesource.com/platform/build.git/+/eec4a7cba4face3370acb6293ab357879920b467 and this for more information. Hi everyone. I'm surprised I havent seen a thread about ota tools yet and lpunpack. This zip file...
forum.xda-developers.com
- tar-md5-script-tool
Use the attached tar-md5-script-tool.zip
Steps
1. Extract official ROM files (BL, AP, CP, CSC)
2. Extract AP .tar.md5
3. Decompress the extracted super.img.lz4
Code:
lz4 -d super.img.lz4 super.img
4. Convert the sparse super.img
Code:
simg2img super.img super.ext4.img
5. Unpack super.ext4.img
Code:
lpunpack super.ext4.img
I got 4 partitions in my image (should be the same for all T220/T225 ROMs):
- odm.img
- product.img
- system.img
- vendor.img
6. Replace system.img with your GSI (rename it to system.img)
7. Get the size of all partitions and the size of the original super.ext4.img (not the sparse super.img)
Code:
stat -c '%n %s' IMG_FILE.img
8. Repack super.img
Code:
lpmake --metadata-size 65536 \
--super-name super \
--metadata-slots 2 \
--device super:ORIGINAL_SUPER_IMG_SIZE \
--group main:SUM_OF_ALL_PARTITIONS_SIZES \
--partition odm:readonly:ODM_PARTITION_SIZE:main \
--image odm=./odm.img \
--partition product:readonly:PRODUCT_PARTITION_SIZE:main \
--image product=./product.img \
--partition system:readonly:SYSTEM_PARTITION_SIZE:main \
--image system=./system.img \
--partition vendor:readonly:VENDOR_PARTITION_SIZE:main \
--image vendor=./vendor.img \
--sparse \
--output ./super_new.img
Replace ORIGINAL_SUPER_IMG_SIZE, SUM_OF_ALL_PARTITIONS_SIZES, ODM_PARTITION_SIZE, PRODUCT_PARTITION_SIZE, SYSTEM_PARTITION_SIZE, VENDOR_PARTITION_SIZE with the values you obtained in step 7.
Read lpmake docs for a more detailed expalation of the args used above:
partition_tools - platform/system/extras - Git at Google
9. Compress the repacked super_new.img
Code:
lz4 -B6 --content-size super_new.img super_new.img.lz4
10. Compress the clean vmbeta.img
Code:
lz4 -B6 --content-size vbmeta.img vbmeta.img.lz4
11. Extract tar-md5-script-tool.zip
12. Put all the *.img.lz4 files extracted from AP .tar.gz in tar-md5-script-tool dir
13. Replace super.img.lz4 and vbmeta.img.lz4 in tar-md5-script-tool dir with your repacked and compressed super_new.img.lz4 (rename it to super.img.lz4) and the clean compressed vbmeta.img.lz4
14. Run batch.bat in tar-md5-script-tool dir
You will find the new AP .tar.md5 in the temp-folder subdir
15. Flash your custom AP .tar.md5 with Odin along with BL, CP, CSC from original ROM
16. Reboot into recovery and do a factory reset
17. Done
Can you share screenshot as I think treble projects are only stable on SD chipset.
Abish4i said:
Can you share screenshot as I think treble projects are only stable on SD chipset.
Click to expand...
Click to collapse
System lang is italian but should be easy to understand.
I found only a couple bugs so far in phhusson's GSI:
- in the launcher dragging apps from drawer to homescreen doesn't always work (just use another launcher)
- crashed once while searching in settings app
I use the tablet only for media consumption and some retrogaming, so there are probably other bugs i haven't noticed.
This is a generic guide, it won't include a "known issues" section since it largely depends on what GSI you choose.
I haven't tested this on the LTE version so i can't say for sure if mobile network works or not.
Unfortunately i don't have the time to make a custom ROM, test it and keep it updated here on the forum but maybe if there is enough interest someone will do it.
I hope other users will try to flash a GSI and share their experience here so we can gather some info on working/broken stuff, especially on the LTE model since i can't test that.
Hello,
I'm sorry but what am I missing here?
I'm a little fustrated cause after hours and hours of headaches I got to the second to last step which involves tar-md5-script-tool
I simply put all the .img.lz4 files from AP and replace super & vbmeta files which the ones that I converted and try to run the batch.bat as instructed.
However nothing happens and this is what the program spits out.
On the tar tool xda forum it says that it convers .img files, not .img.lz4 . Are we supposed to extract all the .img files from inside the .lz4 files?
I appreciate the guide but there are a lot of missing details I had to fill in and figure out myself, like the fact that from step 4 to step 8 you need to use WSL or a Linux distro (using simg2img for Windows messes things up so please use the one from otatools inside a linux bash)
Also for people that are not familiar with linux you need to type "./" in front of directed commands ( in this case ./simg2img ./lpunpack ./lpmake)
I'm not a developer or a programmer, maybe you wrote this guide for people more inclined to that, but for me this was pretty hard.
Noob here, but I'm running the "simg2img super.img super.ext4.img" and nothing happens for 5 min and when I'm aborting I'm getting a "Error reading sparse file header".
Any suggestions?
DanneSwe said:
Noob here, but I'm running the "simg2img super.img super.ext4.img" and nothing happens for 5 min and when I'm aborting I'm getting a "Error reading sparse file header".
Any suggestions?
Click to expand...
Click to collapse
Are you using the Windows version of simg2img? If yes, use the one from otatools inside Windows Subsystem for Linux
ReubenMCSM said:
Are you using the Windows version of simg2img? If yes, use the one from otatools inside Windows Subsystem for Linux
Click to expand...
Click to collapse
I can confirm simg2img doesn't seem to work on Windows, i used WSL.
@ReubenMCSM i will update the guide with more details in the future but i don't have much time right now.
For you specific issue, try to use the attached tar-md5-script-tool.
Great thanks!
What's the process with tar-md5-script-tool? Just moving the super.img to the folder and running the batch.bat didn't work the output file in the temp folder is 11 kb. Tried to change super.img to super.tar but no change.
Thanks for the tool, but unfortunately the output is the same, like the problem @DanneSwe has
It looks like the batch.bat script from the tar md5 tool linked in the guide is a bit different from the one i used. I will update the guide.
Try again with the version i attached in the post above.
- Extract the AP tar md5 from official rom
- Copy all .img.lz4 files in the tar-md5-script-tool folder
- Replace super.img.lz4 and vbmeta.img.lz4 (step 13)
- Launch batch.bat, output should look like this
- You will find AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5 in temp-folder
It finally worked! I redid everything and also moved my folder to drive C instead of drive D, maybe this made the difference
ReubenMCSM said:
It finally worked! I redid everything and also moved my folder to drive C instead of drive D, maybe this made the difference
Click to expand...
Click to collapse
What GSI did you pick and could you upload the files you flashed?
I got simg2img to work by using
.\simg2img -i super.img -o super.ext4.img
packed img filename: super.img
output img filename: super.ext4.img
Wrote "super.ext4.img"
The lpunpack and lpmake step isnt working for me ive been at this for days, no luck.
Can someone please help me out by uploading custom AP .tar.md5(file with GSI, the modded one) along with BL, CP, CSC from original ROM to google drive?
thanks!
ramz.pa said:
The lpunpack and lpmake step isnt working for me ive been at this for days, no luck.
Can someone please help me out by uploading custom AP .tar.md5(file with GSI, the modded one) along with BL, CP, CSC from original ROM to google drive?
thanks!
Click to expand...
Click to collapse
I had the same issue. :/
Can someone help me with the T225 LTE model by compiling the AP please? Because for some reason the tar-md5-script tool isnt working for me
Thanks.
Successfully flashed GSI with magisk on my T220 following the OP's procedure. MTP is not working as the OP said. However, I can use my flash drive so I don't really miss MTP.
I chose "system-squeak-arm64-ab-vndklite-gapps-secure.img.xz" for GSI. "Treble Info" app can tell you what image would be compatible with your device.
If you want to use a different launcher like Nova instead of the default one, change the "Smallest width" setting from 600 to 598 in Developer options to hide the annoying taskbar.
AOSP-Mods and "Project Themer - Android 12+" work fine for me.
Here is my build for my device SM-T220 (SM-T220_EUX_T220XXU1AVE1):
GSI: system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
Custom AP: https://www.filehosting.org/file/details/7045394/AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5
Custom AP with Magisk patch: https://www.filehosting.org/file/details/7045714/magisk_patched-25101_cauJQ.tar
You can extract BL and Home_CSC from SM-T220_EUX_T220XXU1AVE1.
Notes: My device is actually SM-T220 XAR, but I have been updating it with SM-T220 EUX firmware versions without any issue.
Pleasance said:
Can someone help me with the T225 LTE model by compiling the AP please? Because for some reason the tar-md5-script tool isnt working for me
Thanks.
Click to expand...
Click to collapse
Here is the custom AP based on the following. Since I don't have SM-T225 device, can't verify it. However, I compiled the AP the same way I did for my SM-T220.
- SM-T225_EUX_T225XXU1AUJ1
- GSI: system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
https://www.filehosting.org/file/details/7046296/AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5
xpdragon said:
Here is the custom AP based on the following. Since I don't have SM-T225 device, can't verify it. However, I compiled the AP the same way I did for my SM-T220.
- SM-T225_EUX_T225XXU1AUJ1
- GSI: system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
https://www.filehosting.org/file/details/7046296/AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5
Click to expand...
Click to collapse
Thank you so much for compiling the AP for me bro but when i try to flash it with odin i get this error
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> preloader.img.lz4
<ID:0/004> FAIL!
For your information the current OS build on my tablet is INS with the baseband version of T225XXU1AVB2 and security patch of 1 Feb 2022 hope this helps you.
DanneSwe said:
What GSI did you pick and could you upload the files you flashed?
I got simg2img to work by using
.\simg2img -i super.img -o super.ext4.img
packed img filename: super.img
output img filename: super.ext4.img
Wrote "super.ext4.img"
Click to expand...
Click to collapse
GSI-12_SM-T220_EUX_T220XXU1AVE1_fac.zip
drive.google.com
Use this ONLY on SM-T220 (without SIM card) and on EUX version.
Pleasance said:
Thank you so much for compiling the AP for me bro but when i try to flash it with odin i get this error
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> preloader.img.lz4
<ID:0/004> FAIL!
For your information the current OS build on my tablet is INS with the baseband version of T225XXU1AVB2 and security patch of 1 Feb 2022 hope this helps you.
Click to expand...
Click to collapse
Here is GSI build for SM-T225_INS_T225XXU1AVB2
https://www.filehosting.org/file/details/7129248/GSI-12_SM-T225_INS_T225XXU1AVB2.zip