Develop Bugs

Tut/Guide-statusbar mod-data speed indicator without xposed -all g2 variants

DISCLAIMER: I ACCEPT NO RESPONSIBILITY WHATSOEVER IF YOU BRICK YOUR PHONE, LOSS OF DATA OR YOU HAVE BOOTLOOPS USING THIS MOD. THE INFORMATION SHARED FOR HELPING THOSE HELP THEMSELVES. MADE ONLY FOR THE XDA PRINCIPLE OF "SHARING KNOWLEDGE". FOR ROOTED PHONES ONLY & OBVIOUSLY
Everyone is requested not to post unnecessary questions. I am making the OP very clear so you need no further assistance. Critics will be ignored and use of foul language and ungrateful words will be reported.
As seen very often network data speed in statusbar is a nice mod to have but it involves some editing of your smali and xml files. This mod aims to make it very simple for people to incorporate the mod yourself.
FEATURES
1. Speed shown only when connected.
2. Unit in Bytes/Kilobytes/Megabytes selected automatically....no need to worry.
3. Speed shown for data / wifi.
4. Speed indicator vanishes the moment you disconnect.
For making it simple I have made all necessary changes to the files attached. So you need not break your head in making smali edits....Simply cut-copy paste....
THIS METHOD WORKS 100% ON ANY G2...ANY ROM & ANY VERSION OF ANDROID GB/ICS/JB/KK...
STEP I
> DECOMPILE YOUR SYSTEMUI.APK (MUST BE DEODEXED VERSION)
> DOWNLOAD AND UNZIP THE ZIP ATTACHED. SIMPLY COPY ALL THE FILES TO THE FOLLOWING FOLDER
"/smali/com/android/systemui/statusbar/policy"
STEP II
EDIT /res/layout/status_bar.xml with notepad ++ and find the following line
"
HTML:
<com.android.systemui.statusbar.StatusBarIconView android:id="@id/moreIcon" android:visibility="gone" android:layout_width="0.0dip" android:layout_height="fill_parent" android:src="@drawable/stat_notify_more" />
"
SIMPLY ADD THE FOLLOWING LINE EXACTLY ABOVE IT AND SAVE
[SIZE="2"[I]][HTML]<com.android.systemui.statusbar.policy.Traffic android:textAppearance="@style/TextAppearance.StatusBar.Clock" android:textSize="11.0dip" android:textStyle="normal" android:textColor="#ffffffff" android:gravity="left|center" android:layout_width="wrap_content" android:layout_height="fill_parent" android:singleLine="true" />[/HTML][/I][/SIZE][/COLOR]
[B][U][SIZE="2"]NOTE: IN THE ABOVE LINE[/SIZE][/U][/B]
android:textColor="#ffffffff"----CHANGE HEX CODE TO HAVE THE COLOR OF YOUR CHOICE
android:textSize="10.0dip"-----CHANNGE THE DIP FOR SIZE OF SPEED INDICATOR
REMOVING THE ABOVE LINE FROM YOUR STATUS_BAR.MAL WILL DEACTIVATE/REMOVE DATA SPEED
STEP III
>>>>>>>RECOMPILE AS NewLGSystemUI.APK . OPEN THE ORIGINAL LGSystemUI.apk in 7zip.
>>>>>>>Drag and copy the META-INF folder and AndroidManifest.xml to your NewLGSystemUI.APK also opened in 7zip.
>>>>>>>Rename the file to LGSystemUI.apk and push to /system/priv-app with 644/-rw-r--r-- permission.
REBOOT AND ENJOY THE MOD.
I HOPE THIS SIMPLE GUIDE HELPS EVERYONE WHO WANT THE MOD WITHOUT WANTING TO USE XPOSED
DO NOT FORGET TO PRESS THANKS IF YOU LIKED THIS TUT/GUIDE. YOU PRESSING THANKS MAKES ME HAPPY
THIS WORK IS FREE FOR USE BY ANYONE IN ANY ROM. YOU HAVE MY PERMISSION. I DONT DO THIS FOR MONEY OR DONATION. I WOULD BE VERY HAPPY TO GET CREDIT FOR THIS....BE GOOD STAY GOOD AND BE SAFE

STEP I
> DECOMPILE YOUR SYSTEMUI.APK (MUST BE DEODEXED VERSION)
so it means first we need to learn how to deodex
then how to decompile
can u post some easy links for these ? or apps u use to deodex and decompile

rastigo said:
EDIT /res/layout/status_bar.xml with notepad ++ and find the following line
""
SIMPLY ADD THE FOLLOWING LINE EXACTLY ABOVE IT AND SAVE
[SIZE="2"[I]][/I][/SIZE][/COLOR]
[/QUOTE]
okay so the first question is what lines because they are not written there[COLOR="Silver"]
---------- Post added at 10:44 AM ---------- Previous post was at 10:41 AM ----------
mor_1228 said:
STEP I
> DECOMPILE YOUR SYSTEMUI.APK (MUST BE DEODEXED VERSION)
so it means first we need to learn how to deodex
then how to decompile
can u post some easy links for these ? or apps u use to deodex and decompile
Click to expand...
Click to collapse
you can check out universaldeodexer for deodexing apps and ticklemyandroid for decompiling/recompiling which can both be found on xda with many guides on how to use; I prefer to use virtoustenstudio but there are no guides on how to use and a little troublesome for beginners but everyone uses something that works for them
Click to expand...
Click to collapse

Oh ok. I did type them.... Where did they go. Am i supposed to put a text box or something. Those lines just vanished mate,

ok in the meantime I found the traffic line since I still had the yellow systemui with speed mod but when recompiling I get an error recompiling smali folder below is a little log which may help since all the errors are traffic smali related also I am working with cloudyg3 systemui on d800:
Code:
11:33:29.718: [Normal] - SmaliTool.Smali: 'Compiling folder: C:\Users\Ivan\AppData\Local\Temp\6A57BE\smali'
11:33:29.718: [Debug] - SmaliTool.Smali: 'Smali args: -Xmx512m -jar "C:\Program Files (x86)\Virtuous Ten Studio\External\Smali\smali-2.0.3.jar" --api-level 19 --output "C:\Users\Ivan\AppData\Local\Temp\6A57BE\classes.dex" "C:\Users\Ivan\AppData\Local\Temp\6A57BE\smali"'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$1.smali[24,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$1.smali[39,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$1.smali[40,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$1.smali[39,15] mismatched input '"context"' expecting END_METHOD_DIRECTIVE'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$2.smali[24,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$2.smali[39,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$2.smali[39,15] mismatched input '"msg"' expecting END_METHOD_DIRECTIVE'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$3.smali[27,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$SettingsObserver.smali[24,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$SettingsObserver.smali[25,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$SettingsObserver.smali[25,15] mismatched input '"handler"' expecting END_METHOD_DIRECTIVE'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$SettingsObserver.smali[57,15] no viable alternative at input 'resolver''
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$SettingsObserver.smali[57,24] no viable alternative at input 'Landroid/content/ContentResolver;''
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$SettingsObserver.smali[74,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic$SettingsObserver.smali[74,15] mismatched input '"selfChange"' expecting END_METHOD_DIRECTIVE'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[39,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[39,15] mismatched input '"context"' expecting END_METHOD_DIRECTIVE'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[53,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[54,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[53,15] mismatched input '"context"' expecting END_METHOD_DIRECTIVE'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[68,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[69,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[68,15] mismatched input '"context"' expecting END_METHOD_DIRECTIVE'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[70,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[124,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[124,15] mismatched input '"x0"' expecting END_METHOD_DIRECTIVE'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[135,4] Error for input '.parameter': Invalid directive'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[135,15] mismatched input '"x0"' expecting END_METHOD_DIRECTIVE'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[163,15] no viable alternative at input 'connectivityManager''
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[163,35] no viable alternative at input 'Landroid/net/ConnectivityManager;''
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[208,15] no viable alternative at input 'resolver''
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[208,24] no viable alternative at input 'Landroid/content/ContentResolver;''
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[212,15] no viable alternative at input 'newColor''
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[327,15] no viable alternative at input 'filter''
11:33:33.040: [Debug] - SmaliTool.Smali: 'Smali: ..\..\Users\Ivan\AppData\Local\Temp\6A57BE\smali\com\android\systemui\statusbar\policy\Traffic.smali[327,22] no viable alternative at input 'Landroid/content/IntentFilter;''
11:33:33.040: [Normal] - SmaliTool.Smali: 'Smali failed, see log for further information.'
11:33:33.040: [Debug] - SmaliTool.Smali: 'Exitcode: 1'
11:33:33.062: [Error] - SmaliModule.ExecuteInternal: 'LGSystemUI -> Assemble smali files : Assembling smali failed!'
11:33:33.063: [Error] - Script.ExecuteScript: 'Executing LGSystemUI -> Assemble smali files failed!'
edit:might be smali related on my side, what smali/backsmali did you use to decompile/recompile?

Op updated

rastigo said:
> DECOMPILE YOUR SYSTEMUI.APK (MUST BE DEODEXED VERSION)
> DOWNLOAD AND UNZIP THE ZIP ATTACHED. SIMPLY COPY ALL THE FILES TO THE FOLLOWING FOLDER
"/smali/com/android/systemui/statusbar/policy"
STEP II
EDIT /res/layout/status_bar.xml with notepad ++ and find the following line
"
HTML:
<com.android.systemui.statusbar.StatusBarIconView android:id="@id/moreIcon" android:visibility="gone" android:layout_width="0.0dip" android:layout_height="fill_parent" android:src="@drawable/stat_notify_more" />
"
SIMPLY ADD THE FOLLOWING LINE EXACTLY ABOVE IT AND SAVE
[SIZE="2"]
HTML:
<com.android.systemui.statusbar.policy.Traffic android:textAppearance="@style/TextAppearance.StatusBar.Clock" android:textSize="11.0dip" android:textStyle="normal" android:textColor="#ffffffff" android:gravity="left|center" android:layout_width="wrap_content" android:layout_height="fill_parent" android:singleLine="true" />
[/SIZE][/COLOR]
Click to expand...
Click to collapse
this confusing me which line above and which line below ? its like this ?

i cant find this also
> DOWNLOAD AND UNZIP THE ZIP ATTACHED. SIMPLY COPY ALL THE FILES TO THE FOLLOWING FOLDER
"/smali/com/android/systemui/statusbar/policy"
---------- Post added at 12:45 PM ---------- Previous post was at 12:33 PM ----------
bro i guess u forgot to mention we need to deodex both LGSystemUI & lge-res
and then we need to decompile both LGSystemUI & lge-res
because /smali/com is in lge-res folder
i found this lge-res\smali\com\lge
so got these files below : now what ?

mor_1228 said:
bro i guess u forgot to mention we need to deodex both LGSystemUI & lge-res
and then we need to decompile both LGSystemUI & lge-res
because /smali/com is in lge-res folder
i found this lge-res\smali\com\lge
so got these files below : now what ?
Click to expand...
Click to collapse
no, after you decompiled LGSystemUI.apk, this is the exact path
LGSystemUI.apk\smali\com\android\systemui\statusbar\policy\

mor_1228 said:
i cant find this also
> DOWNLOAD AND UNZIP THE ZIP ATTACHED. SIMPLY COPY ALL THE FILES TO THE FOLLOWING FOLDER
"/smali/com/android/systemui/statusbar/policy"
---------- Post added at 12:45 PM ---------- Previous post was at 12:33 PM ----------
bro i guess u forgot to mention we need to deodex both LGSystemUI & lge-res
and then we need to decompile both LGSystemUI & lge-res
because /smali/com is in lge-res folder
i found this lge-res\smali\com\lge
so got these files below : now what ?
Click to expand...
Click to collapse
@mor_1228,..you should be knowing that for decompiling any apk from stock rom, both framework-res.apk and lge-res.apk are required,

rastigo said:
@mor_1228,..you should be knowing that for decompiling any apk from stock rom, both framework-res.apk and lge-res.apk are required,
Click to expand...
Click to collapse
you mean to say bro when decompling i need to paste all 3 files together ramework-res.apk and lge-res.apk & lgsystemui.apk
and when i get option to decompile then i have to decompile only lgsystemui.apk
i will make a video soon for the whole process from deodex to decompile to the end then u can tell me mistakes. :highfive:

mor_1228 said:
you mean to say bro when decompling i need to paste all 3 files together ramework-res.apk and lge-res.apk & lgsystemui.apk
and when i get option to decompile then i have to decompile only lgsystemui.apk
i will make a video soon for the whole process from deodex to decompile to the end then u can tell me mistakes. :highfive:
Click to expand...
Click to collapse
You require framework-res.apk and lge-res.apk for resources.Then decompile the LGSystemUI.apk

rastigo said:
You require framework-res.apk and lge-res.apk for resources.Then decompile the LGSystemUI.apk
Click to expand...
Click to collapse
now i got my mistakes done.
1. deodex both files lge-res and systemui
2. TO decompile first we need to install framework-res.apk and lge-res.apk with this command apktool if framework-res.apk and lge-res.apk
( i was missing this step as i was only installing framework-res.apk and left lge-res)
3. it will decomplie properly now. finally got it properly. :highfive:
now i can see all folders.

while recompile after doing all steps i faced this problem
Code:
C:\apktool>apktool b LGSystemUI
I: Using Apktool 2.0.0-Beta9 on LGSystemUI
I: Checking whether sources has changed...
I: Smaling...
LGSystemUI\smali\com\android\systemui\statusbar\policy\Traffic$1.smali[24,4] Error for input '.parameter': Invalid directive
LGSystemUI\smali\com\android\systemui\statusbar\policy\Traffic$1.smali[39,4] Error for input '.parameter': Invalid directive
LGSystemUI\smali\com\android\systemui\statusbar\policy\Traffic$1.smali[40,4] Error for input '.parameter': Invalid directive
LGSystemUI\smali\com\android\systemui\statusbar\policy\Traffic$1.smali[39,15] mismatched input '"context"' expecting END_METHOD_DIRECTIVE
Exception in thread "main" brut.androlib.AndrolibException: Could not smali file: com/android/systemui/statusbar/policy/Traffic$1.smali
at brut.androlib.src.SmaliBuilder.buildFile(SmaliBuilder.java:72)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:56)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:41)
at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:338)
at brut.androlib.Androlib.buildSources(Androlib.java:299)
at brut.androlib.Androlib.build(Androlib.java:285)
at brut.androlib.Androlib.build(Androlib.java:258)
at brut.apktool.Main.cmdBuild(Main.java:236)
at brut.apktool.Main.main(Main.java:88)

That is quite strange I make it every now and then. No such errors. Try apktool 1.5.2. I read somewhere that 2.0 handles small differently
Sent from my LG-D802 using XDA Premium 4 mobile app

rastigo said:
That is quite strange I make it every now and then. No such errors. Try apktool 1.5.2. I read somewhere that 2.0 handles small differently
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
after using apkttool 1.5.2 i got this error. please check ur pm also sent a video :
C:\apktool>apktool b LGSystemUI
I: Checking whether sources has changed...
I: Smaling...
I: Checking whether resources has changed...
I: Building resources...
aapt: warning: string 'compat_mode_help_body' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
aapt: warning: string 'compat_mode_help_header' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
aapt: warning: string 'jelly_bean_dream_name' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
aapt: warning: string 'quick_settings_wifi_display_label' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
aapt: warning: string 'quick_settings_wifi_display_no_connection_label' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
aapt: warning: string 'status_bar_help_text' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
aapt: warning: string 'status_bar_help_title' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
I: Building apk file...
C:\apktool>
and in the end i got a apk file in dist folder LGSystemUI

mor_1228 said:
after using apkttool 1.5.2 i got this error. please check ur pm also sent a video :
C:\apktool>apktool b LGSystemUI
I: Checking whether sources has changed...
I: Smaling...
I: Checking whether resources has changed...
I: Building resources...
aapt: warning: string 'compat_mode_help_body' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
aapt: warning: string 'compat_mode_help_header' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
aapt: warning: string 'jelly_bean_dream_name' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
aapt: warning: string 'quick_settings_wifi_display_label' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
aapt: warning: string 'quick_settings_wifi_display_no_connection_label' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
aapt: warning: string 'status_bar_help_text' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
aapt: warning: string 'status_bar_help_title' has no default translation in C:\apktool\LGSystemUI\res; found: et km ms
I: Building apk file...
C:\apktool>
and in the end i got a apk file in dist folder LGSystemUI
Click to expand...
Click to collapse
That is not an error mate...congrats you did it. Now drag the meta-inf and the androidmanifest.xml from the original apk to the new one using 7zip. Then replace your file in /system/priv-app with 644 permissions.
Those lines are warnings where apktool cannot find translations to the code in framework-res.apk. Then it looks for the same in lge-res.apk and thus it says found.....
All said and done... You have successfully compiled the mod.... :good:

Well, after a hard work finally got it xD but for remove speed indicator thx for your help

Lol thnkx it means finally I did it will test soon as i am on your stock 20b flashable file from ur thread.
I extracted system . IMG. But fails in deodex
Sent from my LG-D802 using Tapatalk

Thanks @rastigo but I did have some issues on my side but it's all good since my small amount of knowledge on modding helped out and was able to get it working
Sent from my PIKACHU powered LG G3 D800

LG G4 Bricked Qualcomm HS-USB QDLoader 9008

Hello,
I know,I know, you will say yet another topic about LG G4 and Qualcomm 9008 problem.
you have right but this problem intrigues me.
Some people proposed a solution for reviving the phone without a box by short-cutting 2 testpoint on the motherbord before connecting to the computer.
so here is what I did, unfortunately without success, but together we can find where is the problem and find a final solution for this big problem.
1- ONLY connect Smartphone USB Side like this :
{
"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"
}
2- Shortcut with tweezers the two testpoints as described here :
3-On windows 10 x64 Launch QFIL V 2.0.0.5 with Admin Rights :
4- Connect USB Computer side :
5-Choose COM PORT and all settings like this :
6-Clik Download Button
7- unsuccessful operation, this is the log file
Validating Application Configuration
Load APP Configuration
COM:-1
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
SEARCHPATH:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
RAWPROGRAM file path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml
PATCH file path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\patch0.xml
Programmer Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Process Index:0
Start Download
Program Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM4 -s 13:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn 'Current working dir: C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL
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:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
09:28:26: Requested ID 13, file: "C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn"
09:28:26: 273568 bytes transferred in 0.360000 seconds (0.7247MBps)
09:28:26: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
09:28:26: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
Binary build date: Sep 28 2015 @ 17:28:46
Build version: 15.09.28.17.28.46
09:28:30: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml --search_path=C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC
************************************************
09:28:30: INFO: Current working dir (cwd): C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\
09:28:30: INFO: Showing network mappings to allow debugging
09:28:30: INFO:
09:28:30: INFO: Trying to store 'rawprogram0.xml' in string table
09:28:30: INFO: Looking for file 'rawprogram0.xml'
09:28:30: INFO: User wants to talk to port '\\.\COM4'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
09:28:40: {ERROR: It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable}
Writing log to 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Fail:FireHose Fail FHLoader Failrocess fail
Finish Download
port_trace.txt
Validating Application Configuration
Load APP Configuration
COM:-1
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
SEARCHPATH:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
RAWPROGRAM file path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml
PATCH file path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\patch0.xml
Programmer Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Process Index:0
Start Download
Program Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM4 -s 13:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn 'Current working dir: C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL
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:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
09:28:26: Requested ID 13, file: "C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn"
09:28:26: 273568 bytes transferred in 0.360000 seconds (0.7247MBps)
09:28:26: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
09:28:26: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
Binary build date: Sep 28 2015 @ 17:28:46
Build version: 15.09.28.17.28.46
09:28:30: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml --search_path=C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC
************************************************
09:28:30: INFO: Current working dir (cwd): C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\
09:28:30: INFO: Showing network mappings to allow debugging
09:28:30: INFO:
09:28:30: INFO: Trying to store 'rawprogram0.xml' in string table
09:28:30: INFO: Looking for file 'rawprogram0.xml'
09:28:30: INFO: User wants to talk to port '\\.\COM4'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
09:28:40: {ERROR: It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable}
Writing log to 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Fail:FireHose Fail FHLoader Failrocess fail
Finish Download
09:28:30: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml --search_path=C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC
************************************************
09:28:30: DEBUG: Binary build date: Sep 28 2015 @ 17:28:46
09:28:30: DEBUG: Build Version: 15.09.28.17.28.46
09:28:30: INFO: Current working dir (cwd): C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\
09:28:30: INFO: Showing network mappings to allow debugging
09:28:30: DEBUG: Les nouvelles connexions seront m‚moris‚es.
09:28:30: DEBUG:
09:28:30: DEBUG: La liste est vide.
09:28:30: DEBUG:
09:28:30: INFO:
09:28:30: INFO: Trying to store 'rawprogram0.xml' in string table
09:28:30: DEBUG: ==================================================================================
09:28:30: DEBUG: ==================================================================================
09:28:30: INFO: Looking for file 'rawprogram0.xml'
09:28:30: DEBUG: 1. Calling stat(C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml')
09:28:30: DEBUG: 2. Calling fopen('C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml') with AccessMode='rb'
09:28:30: DEBUG: Trying get filesize, calling fseek()
09:28:30: DEBUG: Found 'C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml' (5089 bytes)
09:28:30: DEBUG: 2. Calling fopen('C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml') with AccessMode='r'
09:28:30: DEBUG: Trying get filesize, calling fseek()
09:28:30: DEBUG: User set ZLPAWAREHOST to 1
09:28:30: INFO: User wants to talk to port '\\.\COM4'
09:28:40: DEBUG: port_fd=0xC8
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
09:28:40: {ERROR: OpenPort:5566 It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
So where is the problem ? Shortcutting the two points is supposed to open the FireHose port but i tested with twezzers, cooper cable...ect nothing seem to work
any Idea ?
thank you

PS: I have the Link to the files if you want them

Hello, ¿you can share the links?, I need the files for LG H810.
Thank you in advance.

I got the same problem with my H815T. It only allows me to flash the LS991 files, but I lose the imei
serestma said:
Hello, ¿you can share the links?, I need the files for LG H810.
Thank you in advance.
Click to expand...
Click to collapse
H810: https://mega.nz/#!55tACDZC!Ci1pjEr8_wr9Ng2SrPgj42MwxnGybo60de26w2gtimg

I bought a subscription from easy-firmware hoping that they have right emmc_firehose. They are scammers. I have a bricked LG G4 too and since now I have not found a way to unbrick it. Do not waste your time. For H815 the files are wrong and we also need nonfused emmc_firehose_programmer. Also the SD Card method is not working for me tried it with 10 different images and 4 different cards. I am investigating this issue and if I find a solution I will make a tutorial for all fellas that are in trouble.

AZstyle said:
Hello,
I know,I know, you will say yet another topic about LG G4 and Qualcomm 9008 problem.
you have right but this problem intrigues me.
Some people proposed a solution for reviving the phone without a box by short-cutting 2 testpoint on the motherbord before connecting to the computer.
so here is what I did, unfortunately without success, but together we can find where is the problem and find a final solution for this big problem.
1- ONLY connect Smartphone USB Side like this :
2- Shortcut with tweezers the two testpoints as described here :
3-On windows 10 x64 Launch QFIL V 2.0.0.5 with Admin Rights :
4- Connect USB Computer side :
5-Choose COM PORT and all settings like this :
6-Clik Download Button
7- unsuccessful operation, this is the log file
Validating Application Configuration
Load APP Configuration
COM:-1
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
SEARCHPATH:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
RAWPROGRAM file path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml
PATCH file path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\patch0.xml
Programmer Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Process Index:0
Start Download
Program Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM4 -s 13:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn 'Current working dir: C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL
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:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
09:28:26: Requested ID 13, file: "C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn"
09:28:26: 273568 bytes transferred in 0.360000 seconds (0.7247MBps)
09:28:26: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
09:28:26: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
Binary build date: Sep 28 2015 @ 17:28:46
Build version: 15.09.28.17.28.46
09:28:30: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml --search_path=C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC
************************************************
09:28:30: INFO: Current working dir (cwd): C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\
09:28:30: INFO: Showing network mappings to allow debugging
09:28:30: INFO:
09:28:30: INFO: Trying to store 'rawprogram0.xml' in string table
09:28:30: INFO: Looking for file 'rawprogram0.xml'
09:28:30: INFO: User wants to talk to port '\\.\COM4'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
09:28:40: {ERROR: It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable}
Writing log to 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Fail:FireHose Fail FHLoader Failrocess fail
Finish Download
port_trace.txt
Validating Application Configuration
Load APP Configuration
COM:-1
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
SEARCHPATH:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818
RAWPROGRAM file path: C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml
PATCH file path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\patch0.xml
Programmer Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Process Index:0
Start Download
Program Path:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM4 -s 13:C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn 'Current working dir: C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL
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:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn
09:28:26: Requested ID 13, file: "C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\prog_emmc_firehose_8992_lite.mbn"
09:28:26: 273568 bytes transferred in 0.360000 seconds (0.7247MBps)
09:28:26: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
09:28:26: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
Binary build date: Sep 28 2015 @ 17:28:46
Build version: 15.09.28.17.28.46
09:28:30: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml --search_path=C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC
************************************************
09:28:30: INFO: Current working dir (cwd): C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\
09:28:30: INFO: Showing network mappings to allow debugging
09:28:30: INFO:
09:28:30: INFO: Trying to store 'rawprogram0.xml' in string table
09:28:30: INFO: Looking for file 'rawprogram0.xml'
09:28:30: INFO: User wants to talk to port '\\.\COM4'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
09:28:40: {ERROR: It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable}
Writing log to 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Fail:FireHose Fail FHLoader Failrocess fail
Finish Download
09:28:30: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml --search_path=C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=eMMC
************************************************
09:28:30: DEBUG: Binary build date: Sep 28 2015 @ 17:28:46
09:28:30: DEBUG: Build Version: 15.09.28.17.28.46
09:28:30: INFO: Current working dir (cwd): C:\Users\Amine\AppData\Roaming\Qualcomm\QFIL\
09:28:30: INFO: Showing network mappings to allow debugging
09:28:30: DEBUG: Les nouvelles connexions seront m‚moris‚es.
09:28:30: DEBUG:
09:28:30: DEBUG: La liste est vide.
09:28:30: DEBUG:
09:28:30: INFO:
09:28:30: INFO: Trying to store 'rawprogram0.xml' in string table
09:28:30: DEBUG: ==================================================================================
09:28:30: DEBUG: ==================================================================================
09:28:30: INFO: Looking for file 'rawprogram0.xml'
09:28:30: DEBUG: 1. Calling stat(C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml')
09:28:30: DEBUG: 2. Calling fopen('C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml') with AccessMode='rb'
09:28:30: DEBUG: Trying get filesize, calling fseek()
09:28:30: DEBUG: Found 'C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml' (5089 bytes)
09:28:30: DEBUG: 2. Calling fopen('C:\G4\8992_QFIL_signing_H818\8992_QFIL_signing_H818\8992_QFIL_signing_H818\rawprogram0.xml') with AccessMode='r'
09:28:30: DEBUG: Trying get filesize, calling fseek()
09:28:30: DEBUG: User set ZLPAWAREHOST to 1
09:28:30: INFO: User wants to talk to port '\\.\COM4'
09:28:40: DEBUG: port_fd=0xC8
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
09:28:40: {ERROR: OpenPort:5566 It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
So where is the problem ? Shortcutting the two points is supposed to open the FireHose port but i tested with twezzers, cooper cable...ect nothing seem to work
any Idea ?
thank you
Click to expand...
Click to collapse
qfil needs the firehose.bin i know we dont have one for the sprint varient also have u tried any debrick imgs and sd card method?

Guys just flash the ls991 files and the problem with imei is fixable by flashing some files through fastboot
Do what this says and if you bricked your phone just flash ls991 files again
Only problem which remains is sd card read and write
But you will have a full functional phone

shamescool said:
Guys just flash the ls991 files and the problem with imei is fixable by flashing some files through fastboot
Do what this says and if you bricked your phone just flash ls991 files again
Only problem which remains is sd card read and write
But you will have a full functional phone
Click to expand...
Click to collapse
Please do not mislead other people and try not to answer questions if you didn't try the fixes yourself.
Depending on the bootstack of the CPU SD method might or might nor work.
In theory you can EMMC repair with LS991 but then you will have SecureBoot problems (Error 1006). I didn't try it yet but there is a method where you force off emmc verification by shorting EMMC CMD terminal to GND. But this requires very small soldering, opening the phone and removing the motherboard. The method is tried and working on 4PDA.
EDIT: @AZstyle The firehose are scams, the only working one is the ls991 which I think is a developer one because you will get fastboot access but I can't personally flash anything in LGUP.
When I flash all partitions but bootstack I get 1006 error. I didn't try the soldering method because I have a Medusa Box on the way. I will try USB Repair and if it does not work I will just RMA.

neutrondev said:
Please do not mislead other people and try not to answer questions if you didn't try the fixes yourself.
Depending on the bootstack of the CPU SD method might or might nor work.
In theory you can EMMC repair with LS991 but then you will have SecureBoot problems (Error 1006). I didn't try it yet but there is a method where you force off emmc verification by shorting EMMC CMD terminal to GND. But this requires very small soldering, opening the phone and removing the motherboard. The method is tried and working on 4PDA.
EDIT: @AZstyle The firehose are scams, the only working one is the ls991 which I think is a developer one because you will get fastboot access but I can't personally flash anything in LGUP.
When I flash all partitions but bootstack I get 1006 error. I didn't try the soldering method because I have a Medusa Box on the way. I will try USB Repair and if it does not work I will just RMA.
Click to expand...
Click to collapse
im not misleading anyone here im just sharing my experience
yes you will get 1006 problem by flashing partitions but at least you get a fully functioning phone
the way i mentioned is actually worked for another person here in this forum please test if you still have doubt
my phone is also a refurbished h811 which has a f500l mobo on it and flashing those ls991 files made the phone alive in h811 10n but i did nt have any imei or base band no camera too(even speaker and sensors didnt work)
so i tried flashing some partitions in fastboot and then i had my imei back and also the camera
then i edited f500 tot file with winhex and my phone bricked again(obviously)so i tried flashing ls991 again and now i have a fully functioning phone which cannot be said for sd card...my phone cant write or read any sdcard and its really pissing me of
any suggest for sd card?

H810_ARecovery
¿How to use or flash this files?, tell me please.

neutrondev said:
I bought a subscription from easy-firmware hoping that they have right emmc_firehose. They are scammers. I have a bricked LG G4 too and since now I have not found a way to unbrick it. Do not waste your time. For H815 the files are wrong and we also need nonfused emmc_firehose_programmer. Also the SD Card method is not working for me tried it with 10 different images and 4 different cards. I am investigating this issue and if I find a solution I will make a tutorial for all fellas that are in trouble.
Click to expand...
Click to collapse
u are right, i already tested all this ****, its appear that the only solution is to repair the emmc boot with octopus box or medusa box
next week i'll bring my G4 to a repair store to do this operation.
and I will keep u informed with the results

AZstyle said:
u are right, i already tested all this ****, its appear that the only solution is to repair the emmc boot with octopus box or medusa box
next week i'll bring my G4 to a repair store to do this operation.
and I will keep u informed with the results
Click to expand...
Click to collapse
I bought a medusa box and did the soldering myself. It will not work -_-. I will investigate further but it might need Emmc replacement. Did you try to flash with Qfil using LS991 programmer emmc_firehose? It is very important to know

neutrondev said:
I bought a medusa box and did the soldering myself. It will not work -_-. I will investigate further but it might need Emmc replacement. Did you try to flash with Qfil using LS991 programmer emmc_firehose? It is very important to know
Click to expand...
Click to collapse
Good Remark, I can't remember if I tested with LS911 files, I tested with H815 H818p without sucess.
Do you have the files for LS911? can u share them with me please so i'll give a try.
Thanks

What about that ?
and this

serestma said:
Hello, ¿you can share the links?, I need the files for LG H810.
Thank you in advance.
Click to expand...
Click to collapse
https://mega.nz/#F!1DhXTLAa!kH8MfkbeOKcUWt3T2R6cTQ

@AZstyle Do not flash with those files because I think you will need CPU swap. I think that programmer blows fuses for US version. I did that and now I can't repair it even with MEDUSA I can flash ls991 firmware it boots but with H815 NO.

the_naxhoo said:
I got the same problem with my H815T. It only allows me to flash the LS991 files, but I lose the imei
H810: https://mega.nz/#!55tACDZC!Ci1pjEr8_wr9Ng2SrPgj42MwxnGybo60de26w2gtimg
Click to expand...
Click to collapse
No Problem If You Loosed IMEI I Can Flash IMEI For You Just Poke Me On WhatsApp Only WhatsApp !!!
7000926368
Hope I Can Help You
Sent from my LS-4004 using Tapatalk

neutrondev said:
I bought a medusa box and did the soldering myself. It will not work -_-. I will investigate further but it might need Emmc replacement. Did you try to flash with Qfil using LS991 programmer emmc_firehose? It is very important to know
Click to expand...
Click to collapse
Yes I have flashed ls991 firehose . What do you need to know?
.
Sent from my LG-H815 using XDA Labs

neutrondev said:
I bought a medusa box and did the soldering myself. It will not work -_-. I will investigate further but it might need Emmc replacement. Did you try to flash with Qfil using LS991 programmer emmc_firehose? It is very important to know
Click to expand...
Click to collapse
Medusa Pro Box Works Like Charm !!!
I Fixed 7 LG G4 With It EMMC One
And 3 LG G4 With USB One
If Someone Have Medusa Pro Box And Unable To Fix With It Thats Sure That You Might Have Not Soldered Wire Correct Or Motherboard Has Hardware Problem
Sent from my LS-4004 using Tapatalk

steadfasterX said:
Yes I have flashed ls991 firehose . What do you need to know?
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Dont know where i find a ls992 firehose do you?
I bricked my g5 in a freak bad usb cord accident.

Android 8.0 Oreo Discussion

You guys can discuss things at here or release test builds at here
 @tank0412 @flex1911

Well, i built AOSP O.
But, well, there are major problems with hwcomposer again.
OMG.
https://drive.google.com/open?id=0B-Fin8UxrD6PaHBXTEtDdEFZT2s
LOL.
Code:
08-22 10:50:52.816 158 158 W hw-ProcessState: Opening '/dev/hwbinder' failed: No such file or directory
08-22 10:50:52.816 158 158 E hw-ProcessState: Binder driver could not be opened. Terminating.
08-22 10:50:52.817 158 158 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
08-22 10:50:52.822 158 158 E hwservicemanager: Failed to aquire binder FD. Aborting...
08-22 10:50:52.881 165 165 W hw-ProcessState: Opening '/dev/hwbinder' failed: No such file or directory
08-22 10:50:52.881 165 165 E hw-ProcessState: Binder driver could not be opened. Terminating.
08-22 10:50:52.881 165 165 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
08-22 10:50:52.882 165 165 I ServiceManagement: Removing namespace from process name [email protected] to [email protected]
08-22 10:50:52.882 165 165 F /system/bin/hw/androi[email protected]: service.cpp:24] Unable to register allocator service: -38
--------- beginning of crash
08-22 10:50:52.882 165 165 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 165 ([email protected])
-22 10:50:52.966 175 175 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-22 10:50:52.966 175 175 F DEBUG : Build fingerprint: 'asus/aosp_T00F/T00F:8.0.0/OPR6.170623.010/tank0408220746:eng/test-keys'
08-22 10:50:52.966 175 175 F DEBUG : Revision: '0'
08-22 10:50:52.966 175 175 F DEBUG : ABI: 'x86'
08-22 10:50:52.966 175 175 F DEBUG : pid: 165, tid: 165, name: [email protected] >>> /system/bin/hw/[email protected] <<<
08-22 10:50:52.966 175 175 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
08-22 10:50:52.968 174 174 I crash_dump32: obtaining output fd from tombstoned
08-22 10:50:52.968 174 174 E libc : failed to connect to tombstoned: No such file or directory
08-22 10:50:52.969 174 174 I crash_dump32: performing dump of process 166 (target tid = 166)
08-22 10:50:52.969 174 174 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-22 10:50:52.969 174 174 F DEBUG : Build fingerprint: 'asus/aosp_T00F/T00F:8.0.0/OPR6.170623.010/tank0408220746:eng/test-keys'
08-22 10:50:52.969 174 174 F DEBUG : Revision: '0'
08-22 10:50:52.969 174 174 F DEBUG : ABI: 'x86'
08-22 10:50:52.969 174 174 F DEBUG : pid: 166, tid: 166, name: [email protected] >>> /vendor/bin/hw/[email protected] <<<
08-22 10:50:52.969 174 174 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
08-22 10:50:52.970 175 175 F DEBUG : Abort message: 'service.cpp:24] Unable to register allocator service: -38'
08-22 10:51:11.421 210 210 E IMGSRV : :0: PVRSRVConnect: Unable to enumerate devices.
08-22 10:51:11.421 210 210 E IMGSRV : :0: Couldn't connect to services
08-22 10:51:11.442 210 210 E IMGSRV : :0: SRV_ServicesInit: need wait service init
08-22 10:51:11.442 210 210 E IMGSRV :
08-22 10:51:11.442 210 210 E IMGSRV : :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086849 (strerror returns no value.).
08-22 10:51:11.442 210 210 E IMGSRV : :0: PVRSRVEnumerateDevices: BridgeCall failed

tank0412 said:
Well, i built AOSP O.
But, well, there are major problems with hwcomposer again.
OMG.
https://drive.google.com/open?id=0B-Fin8UxrD6PaHBXTEtDdEFZT2s
LOL.
Code:
08-22 10:50:52.816 158 158 W hw-ProcessState: Opening '/dev/hwbinder' failed: No such file or directory
08-22 10:50:52.816 158 158 E hw-ProcessState: Binder driver could not be opened. Terminating.
08-22 10:50:52.817 158 158 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
08-22 10:50:52.822 158 158 E hwservicemanager: Failed to aquire binder FD. Aborting...
08-22 10:50:52.881 165 165 W hw-ProcessState: Opening '/dev/hwbinder' failed: No such file or directory
08-22 10:50:52.881 165 165 E hw-ProcessState: Binder driver could not be opened. Terminating.
08-22 10:50:52.881 165 165 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
08-22 10:50:52.882 165 165 I ServiceManagement: Removing namespace from process name [email protected] to [email protected]
08-22 10:50:52.882 165 165 F /system/bin/hw/[email protected]: service.cpp:24] Unable to register allocator service: -38
--------- beginning of crash
08-22 10:50:52.882 165 165 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 165 ([email protected])
-22 10:50:52.966 175 175 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-22 10:50:52.966 175 175 F DEBUG : Build fingerprint: 'asus/aosp_T00F/T00F:8.0.0/OPR6.170623.010/tank0408220746:eng/test-keys'
08-22 10:50:52.966 175 175 F DEBUG : Revision: '0'
08-22 10:50:52.966 175 175 F DEBUG : ABI: 'x86'
08-22 10:50:52.966 175 175 F DEBUG : pid: 165, tid: 165, name: [email protected] >>> /system/bin/hw/[email protected] <<<
08-22 10:50:52.966 175 175 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
08-22 10:50:52.968 174 174 I crash_dump32: obtaining output fd from tombstoned
08-22 10:50:52.968 174 174 E libc : failed to connect to tombstoned: No such file or directory
08-22 10:50:52.969 174 174 I crash_dump32: performing dump of process 166 (target tid = 166)
08-22 10:50:52.969 174 174 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-22 10:50:52.969 174 174 F DEBUG : Build fingerprint: 'asus/aosp_T00F/T00F:8.0.0/OPR6.170623.010/tank0408220746:eng/test-keys'
08-22 10:50:52.969 174 174 F DEBUG : Revision: '0'
08-22 10:50:52.969 174 174 F DEBUG : ABI: 'x86'
08-22 10:50:52.969 174 174 F DEBUG : pid: 166, tid: 166, name: [email protected] >>> /vendor/bin/hw/[email protected] <<<
08-22 10:50:52.969 174 174 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
08-22 10:50:52.970 175 175 F DEBUG : Abort message: 'service.cpp:24] Unable to register allocator service: -38'
08-22 10:51:11.421 210 210 E IMGSRV : :0: PVRSRVConnect: Unable to enumerate devices.
08-22 10:51:11.421 210 210 E IMGSRV : :0: Couldn't connect to services
08-22 10:51:11.442 210 210 E IMGSRV : :0: SRV_ServicesInit: need wait service init
08-22 10:51:11.442 210 210 E IMGSRV :
08-22 10:51:11.442 210 210 E IMGSRV : :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086849 (strerror returns no value.).
08-22 10:51:11.442 210 210 E IMGSRV : :0: PVRSRVEnumerateDevices: BridgeCall failed
Click to expand...
Click to collapse
You could try using fugu device tree as reference: https://android.googlesource.com/device/asus/fugu/+/android-8.0.0_r4
But I really recommend you to wait before trying. There's no other ROM than stock-based of Oreo so you can't really have a base for an unnoficial device.

Soo ROM is booting??

Guys, can somebody test new O build?
system.img:
https://drive.google.com/open?id=0B-Fin8UxrD6PT0ZFYk14TFc3N28
boot.img:
https://drive.google.com/open?id=0B-Fin8UxrD6PV19lZ1FfdG5zUHM
I updated binder in kernel sources.
https://github.com/zf5/android_kernel_asus_T00F/commits/aosp8.0
I need logcat and dmesg.
Thanks.

masterofpc said:
Soo ROM is booting??
Click to expand...
Click to collapse
Based on what I understood, they were able to get AOSP Oreo going (with some sort of problem). And even if they manage to fix that "issue", they still need to port the AOSP Oreo for ZenFone 5 based on ASUS sources.
To make it short, yea. The devs are probably getting something going. But it's gonna take a while before even just an "Alpha" build will be available for our use.

cnswico said:
Based on what I understood, they were able to get AOSP Oreo going (with some sort of problem). And even if they manage to fix that "issue", they still need to port the AOSP Oreo for ZenFone 5 based on ASUS sources.
To make it short, yea. The devs are probably getting something going. But it's gonna take a while before even just an "Alpha" build will be available for our use.
Click to expand...
Click to collapse
Thanks a lot

tank0412 said:
Guys, can somebody test new O build?
system.img:
https://drive.google.com/open?id=0B-Fin8UxrD6PT0ZFYk14TFc3N28
boot.img:
https://drive.google.com/open?id=0B-Fin8UxrD6PV19lZ1FfdG5zUHM
I updated binder in kernel sources.
https://github.com/zf5/android_kernel_asus_T00F/commits/aosp8.0
I need logcat and dmesg.
Thanks.
Click to expand...
Click to collapse
I just downloaded and gave a try.
But it stock at bootloader(ASUS logo), then keep rebooting. After several times reboot, it autometically boot into fastboot mode.
Code:
D:\Downloads\Zenfone 5>fastboot devices
0123456789ABCDEF fastboot
D:\Downloads\Zenfone 5>fastboot flash boot boot-O-240817.img
target reported max download size of 611688448 bytes
sending 'boot' (7985 KB)...
OKAY [ 1.458s]
writing 'boot'...
OKAY [ 1.146s]
finished. total time: 2.608s
D:\Downloads\Zenfone 5>fastboot flash system system.img
target reported max download size of 611688448 bytes
sending sparse 'system' (593681 KB)...
OKAY [ 71.458s]
writing 'system'...
OKAY [ 34.281s]
sending sparse 'system' (330425 KB)...
OKAY [ 38.129s]
writing 'system'...
OKAY [ 20.437s]
finished. total time: 164.315s
D:\Downloads\Zenfone 5>adb logcat
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
- waiting for device -
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>fastboot flash boot boot-O-240817.img
target reported max download size of 611218773 bytes
sending 'boot' (7985 KB)...
OKAY [ 1.704s]
writing 'boot'...
OKAY [ 1.128s]
finished. total time: 2.836s
D:\Downloads\Zenfone 5>fastboot flash system system.img
target reported max download size of 611218773 bytes
sending sparse 'system' (593681 KB)...
OKAY [ 82.793s]
writing 'system'...
OKAY [ 34.381s]
sending sparse 'system' (330425 KB)...
OKAY [ 41.286s]
writing 'system'...
OKAY [ 19.840s]
finished. total time: 178.309s
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>
Here's my Zenfone 5 environment:
TWRP 3.1.1.-0 by narueon
Droidboot version: 2.1 BUILD Dec 8 2014 16:02:41
I first go to recovery and wipe /data, /cache, /system, then reboot to fastboot to flash boot and system.
Thx

f870103 said:
I just downloaded and gave a try.
But it stock at bootloader(ASUS logo), then keep rebooting. After several times reboot, it autometically boot into fastboot mode.
Code:
D:\Downloads\Zenfone 5>fastboot devices
0123456789ABCDEF fastboot
D:\Downloads\Zenfone 5>fastboot flash boot boot-O-240817.img
target reported max download size of 611688448 bytes
sending 'boot' (7985 KB)...
OKAY [ 1.458s]
writing 'boot'...
OKAY [ 1.146s]
finished. total time: 2.608s
D:\Downloads\Zenfone 5>fastboot flash system system.img
target reported max download size of 611688448 bytes
sending sparse 'system' (593681 KB)...
OKAY [ 71.458s]
writing 'system'...
OKAY [ 34.281s]
sending sparse 'system' (330425 KB)...
OKAY [ 38.129s]
writing 'system'...
OKAY [ 20.437s]
finished. total time: 164.315s
D:\Downloads\Zenfone 5>adb logcat
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
- waiting for device -
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>fastboot flash boot boot-O-240817.img
target reported max download size of 611218773 bytes
sending 'boot' (7985 KB)...
OKAY [ 1.704s]
writing 'boot'...
OKAY [ 1.128s]
finished. total time: 2.836s
D:\Downloads\Zenfone 5>fastboot flash system system.img
target reported max download size of 611218773 bytes
sending sparse 'system' (593681 KB)...
OKAY [ 82.793s]
writing 'system'...
OKAY [ 34.381s]
sending sparse 'system' (330425 KB)...
OKAY [ 41.286s]
writing 'system'...
OKAY [ 19.840s]
finished. total time: 178.309s
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>adb logcat
- waiting for device -
logcat read failure
D:\Downloads\Zenfone 5>
Here's my Zenfone 5 environment:
TWRP 3.1.1.-0 by narueon
Droidboot version: 2.1 BUILD Dec 8 2014 16:02:41
I first go to recovery and wipe /data, /cache, /system, then reboot to fastboot to flash boot and system.
Thx
Click to expand...
Click to collapse
Thank you.
Thw problem is we must patch binder in kernel sources to at least pass Asus OEM.
I patched it but it looks like patches broke kernel at all.
It said. I am puzzled what to do with it.

I had the same result as you and f870103. bootlooped

tank0412 said:
Guys, can somebody test new O build?
system.img:
https://drive.google.com/open?id=0B-Fin8UxrD6PT0ZFYk14TFc3N28
boot.img:
https://drive.google.com/open?id=0B-Fin8UxrD6PV19lZ1FfdG5zUHM
I updated binder in kernel sources.
https://github.com/zf5/android_kernel_asus_T00F/commits/aosp8.0
I need logcat and dmesg.
Thanks.
Click to expand...
Click to collapse
i tried to flash this new android o but it caused me a bootloop. it doesn't cross the asus logo. whenever i boot my device, it just stuck at the asus logo.

@tank0412 yeah its bootloops.I wait 1 hour.But unfortunately.

Any news ??????

@tank0412
I was looking at lineage os Gerrit.. there are some changes made for Asus Z00D for Lineage Os 15.
Here is the link...
https://goo.gl/w89D8T
I am not sure if it can be of any help but consider looking at it...

narueon said:
@tank0412
I was looking at lineage os Gerrit.. there are some changes made for Asus Z00D for Lineage Os 15.
Here is the link...
https://goo.gl/w89D8T
I am not sure if it can be of any help but consider looking at it...
Click to expand...
Click to collapse
Well, they actually will...

narueon said:
@tank0412
I was looking at lineage os Gerrit.. there are some changes made for Asus Z00D for Lineage Os 15.
Here is the link...
https://goo.gl/w89D8T
I am not sure if it can be of any help but consider looking at it...
Click to expand...
Click to collapse
Yeah, thanks.
I merged all this commits.
https://github.com/zf5/android_device_asus_T00F/commits/aosp8.0
But maybe i did something wrong because it still did not pass Asus OEM logo. What is a shame.
UPD: Asus OEM is passed. Stuck on bootanimation.
Audio server is dead. Dammed.
Build:
https://drive.google.com/open?id=0B-Fin8UxrD6PaHBXTEtDdEFZT2s

Im always trust you tank :victory:

Hi, all.
OREO IS BOOTED ON T00F
EVERYTHING ARE DEAD
{
"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"
}

tank0412 said:
Hi, all.
OREO IS BOOTED ON T00F
EVERYTHING ARE DEAD
Click to expand...
Click to collapse
Great work!! But everything's dead? Is it literal or overstatement?

ZeeJcG said:
Great work!! But everything's dead? Is it literal or overstatement?
Click to expand...
Click to collapse
Only wifi is works.

Zenfone 3 Deluxe brick edl only

hello everyone, I humbly ask for your help, I have had this phone for 2 days, following an update, I find the phone practically dead, connecting it to my PC recognizes it as a Qualcomm driver, and it is already a good sign .... I downloaded Qfil to rifleshare the firmware and I don't complete it by giving me some errors, can I have your opinion? could you help me thank you.
ATTACH THE LOG OF THE FOLLOWING ERROR
16:49:50: INFO: Looking for file 'BTFM.bin'
16:49:50: INFO: Looking for file 'keymaster.mbn'
16:49:50: INFO: Looking for file 'keymaster.mbn'
16:49:50: INFO: Looking for file 'cmnlib.mbn'
16:49:50: INFO: Looking for file 'cmnlib.mbn'
16:49:50: INFO: Looking for file 'cmnlib64.mbn'
16:49:50: INFO: Looking for file 'cmnlib64.mbn'
16:49:50: INFO: Looking for file 'splash.img'
16:49:50: INFO: Looking for file 'gpt_main4.bin'
16:49:50: INFO: Looking for file 'gpt_backup4.bin'
16:49:50: INFO: Looking for file 'gpt_main5.bin'
16:49:50: INFO: Looking for file 'gpt_backup5.bin'
16:49:50: INFO:
Total to be tansferd with <program> or <read> is 3.88 GB
16:49:50: INFO: Sending <configure>
16:49:50: INFO: TARGET SAID: 'Binary build date: Jun 17 2016 @ 10:09:02'
16:49:50: INFO: TARGET SAID: 'Chip serial num: 3066003435 (0xb6bf7feb)'
16:49:50: INFO: TARGET SAID: 'Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke '
16:49:50: INFO: TARGET SAID: 'VIP - Validated Image Programming is enabled - Validation is enabled.'
16:49:50: INFO: TARGET SAID: 'Image Total Size = 0xE4 (228)'
16:49:50: INFO: TARGET SAID: 'HeaderIs80Bytes = 0x0'
16:49:50: INFO: TARGET SAID: 'image_info.sw_type = 0x3 (DeviceProgrammer *insists* on this)'
16:49:50: INFO: TARGET SAID: 'image_info.sw_version = 0x0'
16:49:50: INFO: TARGET SAID: 'image_info.header_len_1 = 0x28'
16:49:50: INFO: TARGET SAID: 'image_info.code_ptr_1 = 0xF54AC112'
16:49:50: INFO: TARGET SAID: 'image_info.code_len_1 = 0x6F636E65'
16:49:50: INFO: TARGET SAID: 'image_info.x509_chain_ptr = 0x1782EE58'
16:49:50: INFO: TARGET SAID: 'image_info.x509_chain_len = 0xA3E3F20'
16:49:50: INFO: TARGET SAID: 'image_info.signature_ptr = 0x5CB92A76'
16:49:50: INFO: TARGET SAID: 'image_info.signature_len = 0x5455223D'
16:49:50: INFO: TARGET SAID: 'image_info.header_ptr_1 = 0x85E14DA0'
16:49:50: INFO: TARGET SAID: 'AuthenticateImage() Returning FALSE, secboot_authenticate() returned 0x2 (not E_SECBOOT_SUCCESS=0x0)'
16:49:50: INFO: TARGET SAID: 'ERROR 1: Line 1140: AUTHENTICATE_IMAGE_FAILURE'
16:49:50: INFO: TARGET SAID: 'Failed to authenticate Digital Signature, resetting validation state'
16:49:50: INFO: TARGET SAID: 'ERROR 11: Line 790: DIGITAL_SIGNATURE_DID_NOT_PASS'
16:49:50: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
16:49:50: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
16:49:50: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
Writing log to 'C:\Users\pp\AppData\Roaming\Qualcomm\QFIL\COMPORT_5\port_trace.txt', might take a minute
Log is 'C:\Users\pp\AppData\Roaming\Qualcomm\QFIL\COMPORT_5\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download

QPST - IMEI repair

Hello everybody,
after days of research, I finally ended up here. Hope that somebody can support me.
Currently I am trying to fix a broken oneplus 5t, classical mac/imei/etc. gone problem.
Unfortunately I have no efs backup for this device, but from another oneplus 5t. But so far I have really tried everything but nothing worked so far.
Let's summarize eveything.
Currently I am running twrp 3.2.x and oxygenos 5.1.7.
But also tried to same stuff with twrp 3.3.x and oxygenos 9.0.9. Same result.
What have I tired:
* restore efs from working phone to broken one via twrp and dd command
* restore via MSM Tool
* restore via QPST
So I am not really sure where this data is stored.
If we trust what we read in the web, it's stored in the efs (modemst1, modemst2). But based on this QPST tool it seems to me somewhere in the nvram.
Could this be the same thing? So does the linux kernel mount it as block devices?
Just for me to get this right.
Further when I trace the kernel logs (stock oxygenOs boot.img) this kind of message keeps looping:
6,112394,1636926453,-;[20180101_12:39:44.068781]@3 subsys-restart: subsystem_shutdown(): [kworker/3:5:6223]: Shutting down modem
6,112395,1636926476,-;[20180101_12:39:44.068806]@3 pil-q6v5-mss 4080000.qcom,mss: MSS is shutting down
SUBSYSTEM=platform
DEVICE=+platform:4080000.qcom,mss
4,112396,1636951535,-;[20180101_12:39:44.093861]@3 pil-q6v5-mss 4080000.qcom,mss: Port 0000000000000000 halt timeout
SUBSYSTEM=platform
DEVICE=+platform:4080000.qcom,mss
6,112397,1636959202,-;[20180101_12:39:44.101527]@3 apr_tal_link_state_cb: edge[mpss] link state[1]
3,112398,1636959474,-;[20180101_12:39:44.101802]@0 <CORE> smem:mpss glink_open: Error 0 - unable to find transport
3,112399,1636959506,-;[20180101_12:39:44.101836]@0 <LBSRV> smem:mpss:LOOPBACK_CTL_APSS glink_lbsrv_open_worker: unable to open channel
6,112400,1636969608,-;[20180101_12:39:44.111934]@3 icnss: Collecting msa0 segment dump
3,112401,1636969631,-;[20180101_12:39:44.111961]@3 Ramdump(ramdump_wcss_msa0): No consumers. Aborting..
3,112402,1636969706,-;[20180101_12:39:44.112035]@3 smd_channel_reset: allocation table not initialized
6,112403,1636969728,-;[20180101_12:39:44.112058]@3 ipa-wan ipa3_ssr_notifier_cb:2541 IPA Received MPSS AFTER_SHUTDOWN
6,112404,1636973889,-;[20180101_12:39:44.116215]@3 ipa-wan ipa3_ssr_notifier_cb:2544 IPA AFTER_SHUTDOWN handling is complete
6,112405,1636990168,-;[20180101_12:39:44.132498]@3 ipa-wan ipa3_ssr_notifier_cb:2547 IPA received MPSS BEFORE_POWERUP
6,112406,1636991968,-;[20180101_12:39:44.134300]@3 ipa-wan ipa3_ssr_notifier_cb:2554 IPA BEFORE_POWERUP handling is complete
6,112407,1636991984,-;[20180101_12:39:44.134317]@3 subsys-restart: subsystem_powerup(): [kworker/3:5:6223]: Powering up modem
14,112408,1636992926,-;[20180101_12:39:44.135257]@0 ueventd: firmware: loading 'modem.mdt' for '/devices/soc/4080000.qcom,mss/firmware/modem.mdt'
14,112409,1636993176,-;[20180101_12:39:44.135509]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.mdt took 0ms
6,112410,1636994121,-;[20180101_12:39:44.136455]@3 pil-q6v5-mss 4080000.qcom,mss: modem: loading from 0x000000008d000000 to 0x0000000094000000
SUBSYSTEM=platform
DEVICE=+platform:4080000.qcom,mss
14,112411,1637012648,-;[20180101_12:39:44.154976]@0 ueventd: firmware: loading 'mba.mbn' for '/devices/soc/4080000.qcom,mss/firmware/mba.mbn'
14,112412,1637013400,-;[20180101_12:39:44.155728]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/mba.mbn took 0ms
14,112413,1637015369,-;[20180101_12:39:44.157697]@1 ueventd: firmware: loading 'msadp' for '/devices/soc/4080000.qcom,mss/firmware/msadp'
11,112414,1637015671,-;[20180101_12:39:44.158002]@1 ueventd: firmware: could not find firmware for msadp
14,112415,1637015769,-;[20180101_12:39:44.158100]@1 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/msadp took 0ms
36,112416,1637015797,-;[20180101_12:39:44.158126]@0 type=1400 audit(1514828382.172:1080): avc: denied { read } for pid=13136 comm="ueventd" name="sde32" dev="tmpfs" ino=9971 scontext=u:r:ueventd:s0 tcontext=ubject_r:mba_debug_dev:s0 tclass=blk_file permissive=0
36,112417,1637015819,-;[20180101_12:39:44.158150]@0 type=1400 audit(1514828384.152:1081): avc: denied { read } for pid=13185 comm="ueventd" name="sde32" dev="tmpfs" ino=9971 scontext=u:r:ueventd:s0 tcontext=ubject_r:mba_debug_dev:s0 tclass=blk_file permissive=0
4,112418,1637016239,-;[20180101_12:39:44.158570]@3 pil-q6v5-mss 4080000.qcom,mss: Debug policy not present - msadp. Continue.
SUBSYSTEM=platform
DEVICE=+platform:4080000.qcom,mss
6,112419,1637016317,-;[20180101_12:39:44.158649]@3 pil-q6v5-mss 4080000.qcom,mss: Loading MBA and DP (if present) from 0x0000000094500000 to 0x0000000094600000 size 100000
SUBSYSTEM=platform
DEVICE=+platform:4080000.qcom,mss
6,112420,1637115354,-;[20180101_12:39:44.257679]@3 pil-q6v5-mss 4080000.qcom,mss: MBA boot done
SUBSYSTEM=platform
DEVICE=+platform:4080000.qcom,mss
14,112421,1637220866,-;[20180101_12:39:44.363198]@3 ueventd: firmware: loading 'modem.b02' for '/devices/soc/4080000.qcom,mss/firmware/modem.b02'
14,112422,1637221579,-;[20180101_12:39:44.363913]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b02 took 0ms
14,112423,1637222139,-;[20180101_12:39:44.364473]@1 ueventd: firmware: loading 'modem.b03' for '/devices/soc/4080000.qcom,mss/firmware/modem.b03'
14,112424,1637222331,-;[20180101_12:39:44.364665]@1 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b03 took 0ms
14,112425,1637223142,-;[20180101_12:39:44.365475]@2 ueventd: firmware: loading 'modem.b04' for '/devices/soc/4080000.qcom,mss/firmware/modem.b04'
14,112426,1637223748,-;[20180101_12:39:44.366081]@2 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b04 took 0ms
14,112427,1637224425,-;[20180101_12:39:44.366758]@1 ueventd: firmware: loading 'modem.b05' for '/devices/soc/4080000.qcom,mss/firmware/modem.b05'
14,112428,1637225220,-;[20180101_12:39:44.367553]@1 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b05 took 0ms
14,112429,1637226070,-;[20180101_12:39:44.368403]@0 ueventd: firmware: loading 'modem.b06' for '/devices/soc/4080000.qcom,mss/firmware/modem.b06'
14,112430,1637226387,-;[20180101_12:39:44.368721]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b06 took 0ms
14,112431,1637227516,-;[20180101_12:39:44.369849]@0 ueventd: firmware: loading 'modem.b07' for '/devices/soc/4080000.qcom,mss/firmware/modem.b07'
14,112432,1637227935,-;[20180101_12:39:44.370269]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b07 took 0ms
14,112433,1637228667,-;[20180101_12:39:44.371001]@0 ueventd: firmware: loading 'modem.b08' for '/devices/soc/4080000.qcom,mss/firmware/modem.b08'
14,112434,1637229521,-;[20180101_12:39:44.371854]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b08 took 0ms
14,112435,1637230383,-;[20180101_12:39:44.372716]@0 ueventd: firmware: loading 'modem.b09' for '/devices/soc/4080000.qcom,mss/firmware/modem.b09'
14,112436,1637235759,-;[20180101_12:39:44.378089]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b09 took 5ms
14,112437,1637236706,-;[20180101_12:39:44.379040]@0 ueventd: firmware: loading 'modem.b10' for '/devices/soc/4080000.qcom,mss/firmware/modem.b10'
14,112438,1637236884,-;[20180101_12:39:44.379219]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b10 took 0ms
14,112439,1637237957,-;[20180101_12:39:44.380290]@0 ueventd: firmware: loading 'modem.b11' for '/devices/soc/4080000.qcom,mss/firmware/modem.b11'
14,112440,1637240473,-;[20180101_12:39:44.382805]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b11 took 2ms
14,112441,1637241259,-;[20180101_12:39:44.383592]@0 ueventd: firmware: loading 'modem.b12' for '/devices/soc/4080000.qcom,mss/firmware/modem.b12'
14,112442,1637279449,-;[20180101_12:39:44.421779]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b12 took 38ms
14,112443,1637280420,-;[20180101_12:39:44.422753]@3 ueventd: firmware: loading 'modem.b13' for '/devices/soc/4080000.qcom,mss/firmware/modem.b13'
14,112444,1637281627,-;[20180101_12:39:44.423960]@3 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b13 took 1ms
14,112445,1637281911,-;[20180101_12:39:44.424244]@1 ueventd: firmware: loading 'modem.b14' for '/devices/soc/4080000.qcom,mss/firmware/modem.b14'
14,112446,1637282088,-;[20180101_12:39:44.424422]@1 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b14 took 0ms
14,112447,1637282810,-;[20180101_12:39:44.425144]@3 ueventd: firmware: loading 'modem.b16' for '/devices/soc/4080000.qcom,mss/firmware/modem.b16'
14,112448,1637284300,-;[20180101_12:39:44.426633]@3 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b16 took 1ms
14,112449,1637284623,-;[20180101_12:39:44.426957]@1 ueventd: firmware: loading 'modem.b17' for '/devices/soc/4080000.qcom,mss/firmware/modem.b17'
14,112450,1637321894,-;[20180101_12:39:44.464225]@5 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b17 took 37ms
14,112451,1637344346,-;[20180101_12:39:44.486678]@0 ueventd: firmware: loading 'modem.b18' for '/devices/soc/4080000.qcom,mss/firmware/modem.b18'
14,112452,1637350380,-;[20180101_12:39:44.492712]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b18 took 6ms
14,112453,1637393143,-;[20180101_12:39:44.535475]@0 ueventd: firmware: loading 'modem.b20' for '/devices/soc/4080000.qcom,mss/firmware/modem.b20'
14,112454,1637394000,-;[20180101_12:39:44.536332]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b20 took 0ms
14,112455,1637395000,-;[20180101_12:39:44.537334]@0 ueventd: firmware: loading 'modem.b21' for '/devices/soc/4080000.qcom,mss/firmware/modem.b21'
14,112456,1637396429,-;[20180101_12:39:44.538761]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b21 took 1ms
14,112457,1637397545,-;[20180101_12:39:44.539878]@0 ueventd: firmware: loading 'modem.b22' for '/devices/soc/4080000.qcom,mss/firmware/modem.b22'
14,112458,1637419880,-;[20180101_12:39:44.562209]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b22 took 22ms
14,112459,1637421146,-;[20180101_12:39:44.563478]@0 ueventd: firmware: loading 'modem.b23' for '/devices/soc/4080000.qcom,mss/firmware/modem.b23'
14,112460,1637421616,-;[20180101_12:39:44.563950]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b23 took 0ms
14,112461,1637422608,-;[20180101_12:39:44.564941]@0 ueventd: firmware: loading 'modem.b24' for '/devices/soc/4080000.qcom,mss/firmware/modem.b24'
14,112462,1637426669,-;[20180101_12:39:44.569001]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b24 took 4ms
14,112463,1637427663,-;[20180101_12:39:44.569996]@0 ueventd: firmware: loading 'modem.b25' for '/devices/soc/4080000.qcom,mss/firmware/modem.b25'
14,112464,1637428662,-;[20180101_12:39:44.570994]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b25 took 1ms
14,112465,1637429630,-;[20180101_12:39:44.571964]@0 ueventd: firmware: loading 'modem.b26' for '/devices/soc/4080000.qcom,mss/firmware/modem.b26'
14,112466,1637429959,-;[20180101_12:39:44.572293]@0 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b26 took 0ms
14,112467,1637431059,-;[20180101_12:39:44.573391]@1 ueventd: firmware: loading 'modem.b27' for '/devices/soc/4080000.qcom,mss/firmware/modem.b27'
14,112468,1637431271,-;[20180101_12:39:44.573606]@1 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b27 took 0ms
14,112469,1637432373,-;[20180101_12:39:44.574706]@1 ueventd: firmware: loading 'modem.b28' for '/devices/soc/4080000.qcom,mss/firmware/modem.b28'
14,112470,1637433518,-;[20180101_12:39:44.575850]@1 ueventd: loading /devices/soc/4080000.qcom,mss/firmware/modem.b28 took 1ms
12,112471,1637487823,-;[20180101_12:39:44.630155]@0 healthd: battery l=85 v=4332 t=27.8 h=2 st=2 c=-1188 chg=a
6,112472,1638159672,-;[20180101_12:39:45.301997]@3 pil-q6v5-mss 4080000.qcom,mss: modem: Brought out of reset
SUBSYSTEM=platform
DEVICE=+platform:4080000.qcom,mss
6,112473,1638291028,-;[20180101_12:39:45.433353]@0 apr_tal_link_state_cb: edge[mpss] link state[0]
6,112474,1638293942,-;[20180101_12:39:45.436269]@3 pil-q6v5-mss 4080000.qcom,mss: Subsystem error monitoring/handling services are up
SUBSYSTEM=platform
DEVICE=+platform:4080000.qcom,mss
6,112475,1638294192,-;[20180101_12:39:45.436519]@2 pil-q6v5-mss 4080000.qcom,mss: modem: Power/Clock ready interrupt received
SUBSYSTEM=platform
DEVICE=+platform:4080000.qcom,mss
6,112476,1638297506,-;[20180101_12:39:45.439834]@3 ipa-wan ipa3_ssr_notifier_cb:2558 ipa3_ssr_notifier_cb:2558 IPA received MPSS AFTER_POWERUP
6,112477,1638297982,-;[20180101_12:39:45.440310]@3 rmnet_ipa3 started initialization
6,112478,1638297999,-;[20180101_12:39:45.440329]@3 IPA SSR support = True
6,112479,1638298013,-;[20180101_12:39:45.440342]@3 IPA ipa-loaduC = True
6,112480,1638298026,-;[20180101_12:39:45.440356]@3 IPA SG support = True
6,112481,1638298040,-;[20180101_12:39:45.440370]@3 IPA Napi Enable = False
6,112482,1638298054,-;[20180101_12:39:45.440384]@3 using default for wan-rx-desc-size = 256
6,112483,1638312713,-;[20180101_12:39:45.455038]@3 rmnet_ipa completed initialization
6,112484,1638314441,-;[20180101_12:39:45.456767]@3 ipa-wan ipa3_ssr_notifier_cb:2563 IPA AFTER_POWERUP handling is complete
6,112485,1638314474,-;[20180101_12:39:45.456803]@3 subsys-restart: subsystem_restart_wq_func(): [kworker/3:5:6223]: Restart sequence for modem completed.
6,112486,1638406859,-;[20180101_12:39:45.549183]@3 service-notifier: root_service_service_arrive: Connection established between QMI handle and 180 service
6,112487,1638410027,-;[20180101_12:39:45.552351]@3 sysmon-qmi: sysmon_clnt_svc_arrive: Connection established between QMI handle and modem's SSCTL service
11,112488,1638425914,-;[20180101_12:39:45.568245]@1 rmt_storage:INFO:kmsg_enable: Enabling KMSG-LOGS!
11,112489,1638425956,-;[20180101_12:39:45.568289]@1 rmt_storage:INFO:rmt_storage_alloc_buff_cb: Received req_size: 0! avail: 2097152
11,112490,1638426738,-;[20180101_12:39:45.569070]@1 rmt_storage:INFO:rmt_storage_rw_iovec_cb: Read iovec request received for /oem/nvbk/static
11,112491,1638426896,-;[20180101_12:39:45.569229]@3 rmt_storage:INFO:rmt_storage_client_thread: Calling Read [offset=0, size=512]for /oem/nvbk/static!
11,112492,1638426926,-;[20180101_12:39:45.569260]@3 rmt_storage:INFO:rmt_storage_client_thread: Done Read (bytes = 512) for /oem/nvbk/static!
11,112493,1638427644,-;[20180101_12:39:45.569977]@1 rmt_storage:INFO:rmt_storage_rw_iovec_cb: Read iovec request received for /oem/nvbk/static
11,112494,1638427788,-;[20180101_12:39:45.570120]@0 rmt_storage:INFO:rmt_storage_client_thread: Calling Read [offset=512, size=1240064]for /oem/nvbk/static!
11,112495,1638428603,-;[20180101_12:39:45.570933]@0 rmt_storage:INFO:rmt_storage_client_thread: Done Read (bytes = 1240064) for /oem/nvbk/static!
11,112496,1638448241,-;[20180101_12:39:45.590567]@2 rmt_storage:INFO:rmt_storage_rw_iovec_cb: Read iovec request received for /oem/nvbk/dynamic
11,112497,1638448706,-;[20180101_12:39:45.591034]@3 rmt_storage:INFO:rmt_storage_client_thread: Calling Read [offset=0, size=512]for /oem/nvbk/dynamic!
11,112498,1638448761,-;[20180101_12:39:45.591091]@3 rmt_storage:INFO:rmt_storage_client_thread: Done Read (bytes = 512) for /oem/nvbk/dynamic!
11,112499,1638450452,-;[20180101_12:39:45.592780]@0 rmt_storage:INFO:rmt_storage_rw_iovec_cb: Read iovec request received for /oem/nvbk/dynamic
11,112500,1638450691,-;[20180101_12:39:45.593021]@2 rmt_storage:INFO:rmt_storage_client_thread: Calling Read [offset=512, size=906240]for /oem/nvbk/dynamic!
11,112501,1638451533,-;[20180101_12:39:45.593862]@2 rmt_storage:INFO:rmt_storage_client_thread: Done Read (bytes = 906240) for /oem/nvbk/dynamic!
11,112502,1638465887,-;[20180101_12:39:45.608211]@1 rmt_storage:INFO:rmt_storage_rw_iovec_cb: Read iovec request received for /boot/modem_fs1
11,112503,1638466117,-;[20180101_12:39:45.608443]@0 rmt_storage:INFO:rmt_storage_client_thread: Calling Read [offset=512, size=512]for /boot/modem_fs1!
11,112504,1638466180,-;[20180101_12:39:45.608507]@0 rmt_storage:INFO:rmt_storage_client_thread: Done Read (bytes = 512) for /boot/modem_fs1!
11,112505,1638468234,-;[20180101_12:39:45.610559]@1 rmt_storage:INFO:rmt_storage_rw_iovec_cb: Read iovec request received for /boot/modem_fs2
11,112506,1638468445,-;[20180101_12:39:45.610771]@0 rmt_storage:INFO:rmt_storage_client_thread: Calling Read [offset=512, size=512]for /boot/modem_fs2!
11,112507,1638468506,-;[20180101_12:39:45.610833]@0 rmt_storage:INFO:rmt_storage_client_thread: Done Read (bytes = 512) for /boot/modem_fs2!
11,112508,1638470849,-;[20180101_12:39:45.613175]@0 rmt_storage:INFO:rmt_storage_rw_iovec_cb: Read iovec request received for /boot/modem_fsg
11,112509,1638471199,-;[20180101_12:39:45.613525]@0 rmt_storage:INFO:rmt_storage_client_thread: Calling Read [offset=0, size=2097152]for /boot/modem_fsg!
11,112510,1638474479,-;[20180101_12:39:45.616802]@0 rmt_storage:INFO:rmt_storage_client_thread: Done Read (bytes = 2097152) for /boot/modem_fsg!
6,112511,1638655509,-;[20180101_12:39:45.797835]@0 Sending QMI_IPA_INIT_MODEM_DRIVER_REQ_V01
3,112512,1638740283,-;[20180101_12:39:45.882608]@0 allocation failed, 5246976
3,112513,1638740310,-;[20180101_12:39:45.882639]@0 In handle_alloc_generic_req,Unable to allocate memory for requested client
3,112514,1638741241,-;[20180101_12:39:45.883569]@0 ipa-wan ipa3_handle_indication_req:152 not send indication
3,112515,1638820774,-;[20180101_12:39:45.963098]@3 Fatal error on the modem.
3,112516,1638820814,-;[20180101_12:39:45.963143]@3 modem subsystem failure reason: rflm_diag_error.cc:347:[email protected]_qlnk.cpp:894 [9,3] RF stuck in QLINK start st.
6,112517,1638820888,-;[20180101_12:39:45.963216]@3 subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED.
6,112518,1638821116,-;[20180101_12:39:45.963444]@3 get_param_by_index_and_offset[77] sid_index = 9 offset = 348 buf = ffffff8c70229364 length = 4
6,112519,1638821139,-;[20180101_12:39:45.963467]@3 set_param_by_index_and_offset[101]sid_index = 9 offset = 348 buf = ffffff8c70229364 length = 4
6,112520,1638827904,-;[20180101_12:39:45.970231]@3 ipa-wan ipa3_ssr_notifier_cb:2526 IPA received MPSS BEFORE_SHUTDOWN
6,112521,1638828227,-;[20180101_12:39:45.970555]@3 get_param_by_index_and_offset[77] sid_index = 9 offset = 24 buf = ffffffed9ac8fcec length = 4
3,112522,1638828246,-;[20180101_12:39:45.970575]@3 subsys-restart: check_crash_restart(): subsystem_restart: check_crash_restart: param_value = 0820180101_12:39:45
6,112523,1638828273,-;[20180101_12:39:45.970602]@3 set_param_by_index_and_offset[101]sid_index = 9 offset = 288 buf = ffffffed9ac8fd40 length = 4
6,112524,1638829140,-;[20180101_12:39:45.971467]@3 set_param_by_index_and_offset[101]sid_index = 9 offset = 292 buf = ffffffed9ac8fd44 length = 4
6,112525,1638829926,-;[20180101_12:39:45.972254]@3 set_param_by_index_and_offset[101]sid_index = 9 offset = 296 buf = ffffffed9ac8fd48 length = 4
6,112526,1638830874,-;[20180101_12:39:45.973201]@3 set_param_by_index_and_offset[101]sid_index = 9 offset = 300 buf = ffffffed9ac8fd4c length = 4
6,112527,1638831681,-;[20180101_12:39:45.974008]@3 set_param_by_index_and_offset[101]sid_index = 9 offset = 304 buf = ffffffed9ac8fd50 length = 4
6,112528,1638832456,-;[20180101_12:39:45.974784]@3 set_param_by_index_and_offset[101]sid_index = 9 offset = 24 buf = ffffffed9ac8fcec length = 4
6,112529,1638835304,-;[20180101_12:39:45.977633]@3 rmnet_ipa started deinitialization
3,112530,1638835322,-;[20180101_12:39:45.977651]@3 ipa ipa3_teardown_sys_pipe:1526 bad parm.
3,112531,1638835349,-;[20180101_12:39:45.977679]@3 ipa-wan ipa3_wwan_remove:2342 Failed to teardown IPA->APPS pipe
3,112532,1638835373,-;[20180101_12:39:45.977702]@3 ipa ipa3_teardown_sys_pipe:1526 bad parm.
3,112533,1638835396,-;[20180101_12:39:45.977725]@3 ipa-wan ipa3_wwan_remove:2347 Failed to teardown APPS->IPA pipe
3,112534,1638836765,-;[20180101_12:39:45.979091]@3 [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_ipa0
3,112535,1638880695,-;[20180101_12:39:46.023019]@3 [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rmnet_ipa0
3,112536,1638881036,-;[20180101_12:39:46.023363]@3 ipa-wan ipa3_del_dflt_wan_rt_tables:403 Deleting Route hdl0x9) with ip type: 0
3,112537,1638882944,-;[20180101_12:39:46.025271]@3 ipa-wan ipa3_del_dflt_wan_rt_tables:412 Deleting Route hdl0xd) with ip type: 1
6,112538,1638884162,-;[20180101_12:39:46.026490]@3 rmnet_ipa completed deinitialization
6,112539,1638884877,-;[20180101_12:39:46.027205]@3 ipa-wan ipa3_ssr_notifier_cb:2538 IPA BEFORE_SHUTDOWN handling is complete
6,112540,1638884914,-;[20180101_12:39:46.027243]@3 icnss: PD service down, pd_state: 2, state: 0x4180: cause: Root PD crashed
6,112541,1638884956,-;[20180101_12:39:46.027285]@3 R0: wlan: [12745:E :QDF] cds_get_context: Module ID 5 context is Null
6,112542,1638884980,-;[20180101_12:39:46.027309]@3 R0: wlan: [12745:E :QDF] cds_get_context: Module ID 5 context is Null
6,112543,1638885002,-;[20180101_12:39:46.027331]@3 R0: wlan: [12745:E :HDD] wlan_hdd_purge_notifier: 1274: hdd context is NULL return!!
6,112544,1638885183,-;[20180101_12:39:46.027511]@3 subsys-restart: subsystem_shutdown(): [kworker/3:2:12745]: Shutting down modem
6,112545,1638885207,-;[20180101_12:39:46.027536]@3 pil-q6v5-mss 4080000.qcom,mss: MSS is shutting down
Seems to me like the kernel is not able to start the modem or whatever.
Another observation from my side. After enabling diag mode via setprop sys.usb.config rndis,diag,adb (adb shell), none of the QPST tool works.
Either there is an communication timeout or something else.
Error messages:
* "The phone has stopped responding to memory read/write commands"
* "The phone you have chosen does not support an embedded file system, ...."
{
"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"
}
But the phone shows up properly in the device manager in the PORT section.
Could be my nv storage broken?
Thanks in advise.

If you have no efs backup, there is no going back. That's the partition where info like this is stored - and it's unique in every phone - so you can't just restore this from another phone.
Maybe oneplus can help, but I don't think there is much hope ?

did you try the unbrick tool to completely restore the phone?
you can find it here :-
https://forum.xda-developers.com/oneplus-5t/how-to/op5t-collection-unbrick-tools-t3898890

Hi, yes I have tried the msm unbrick tool. In my chase it has not restore the efs sections.
Guess contacting one plus one service will be the only way to fix it.