Develop Bugs

[solved] G4 H815 - What kind of loop I have entered ? TWRP and supersu on marshmallow

I have rooted all my phones.
I was following a tutorial to root my LG and instead of flashing TWRP I was advised to boot TWRP which I did (fastboot boot recovery.img)
Using TWRP in that mode I flased supersu.zip, then phone went into a loop.
Not sure where I ended up
When I enter "adb devices" it shows my G4 as offline.
How can I move from this point please ?

Hi guys?
Any ideas ? Please.

birkopf said:
Hi guys?
Any ideas ? Please.
Click to expand...
Click to collapse
if you can enter download mode vol up connect usb then download corresponding KDZ file and flash with LGUP using the refurbihsed option. good luck

adb offline means you have to accept the popup on the phone when connecting to the phone from that pc. If your screen is not accesible then you have to flash the kdz as mentioned above.
Next time, when you enable the USB debug, also connect to the pc and answer that popup. and you should be good.

Thanks guys
Are you sure I would be able to flash KDZ ?
I flashed supersu.zip without TWRP installed and now when I turn on my phone, LG logo shows up but boot process isn't progressing.
Probably too early for PC to detect mobile and I suspect thtats why it shows offline in adb...
I'm very cautious about guide/how-to I follow now. If you have any links on flashing KDZ that you could share I would appreciate.
Also - what will flashing KDZ do exactly ? Flash new system directly to /system partition ? (just trying understand)

If using LG UP you can choose Upgrade that will only write the system, or choose Refurbish, this will erase /data so you will end up fresh. It depends on what you want.

I am sorry for late reply. Very busy week, and needed to sleep a bit...
Fortunately LGUP is working. I have Uk version of my G4 (exactly H815 unbranded. No more info under battery).
- How can I be sure I am getting correct KZD file?
I'm downloading H81520D_00_0115.kdz but never used those and I don't want to flash wrong one...
I have found also H81520h_00_-516.kdz.
Don't want to be a pest but... if it's a matter of quick google search for you - could you be so kind and drop correct link for me ?
I cannot check anything with phone in this state

birkopf said:
I am sorry for late reply. Very busy week, and needed to sleep a bit...
Fortunately LGUP is working. I have Uk version of my G4 (exactly H815 unbranded. No more info under battery).
- How can I be sure I am getting correct KZD file?
I'm downloading H81520D_00_0115.kdz but never used those and I don't want to flash wrong one...
I have found also H81520h_00_-516.kdz.
Don't want to be a pest but... if it's a matter of quick google search for you - could you be so kind and drop correct link for me ?
I cannot check anything with phone in this state
Click to expand...
Click to collapse
V20h is newer so you should flash that. If you go to general threads section you will see that there is v20l that is even newer than v20h, and is from UK. Happy flashing
Edit: here you go with the link to the new firmware thread http://forum.xda-developers.com/showthread.php?t=3480887

OK, I'm not sure what is the problem here but thanks to your advise I restored system. Everything was working fine. Then I installed TWRP. Then using TWRP I flashed UPDATE-SuperSU-v2.46.zip and then... phone wen to the same loop as it was before.
Could it be some incompatibility of supersu ? Or perhaps I need some kernel or other items. Or perhaps other root manager ?

Ok, found the problem. On Marshmallow flashing supersu will not work - I flashed pre-rooted kernel and works like a charm. Just a shame I had to spend half of my sunday flashing, erasing, backing up, restoring, etc.
Thanks for your help guys!

Stuck in fastboot. No recovery... no bueno :(

So I had my ze551ml / Z00A rooted, was loving life, all was great. Then I tried getting XPosed access and didn't read up on it prior. Anyways, now my phone is stuck in fastboot, I'm able to flash partitions and all, including recovery partition, yet I cannot enter any mode but the hung ASUS logo, or fastboot. I weas even able to load CM's "upgrade to MM bootloader" package, but still the same thing only with green letters where they once were blue..... Please help, I need my beloved phone back.....

I'm not a pro but if you can access fastboot it is just a soft brick and I'm sure many people can point you on the right thread to recover it.

I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....

joecost85 said:
I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....
Click to expand...
Click to collapse
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?

timbernot said:
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?
Click to expand...
Click to collapse
0094.0183

joecost85 said:
0094.0183
Click to expand...
Click to collapse
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link

timbernot said:
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link
Click to expand...
Click to collapse
So I've yet to try your solution, but I do have an update, I was able to, one by one, flash all the stock files (stock as in the stuff I downloaded from asus site) and was almost able to boot to recovery, but when I got to the red triangle android, I couldn't get it to go further. I've heardf alternate key combos for proceeding from there, and tried them all, but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**

joecost85 said:
So I had my ze551ml / Z00A rooted, was loving life, all was great. Please help I need my beloved phone back.....
Click to expand...
Click to collapse
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
joecost85 said:
So I've yet to try your solution,
but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**
Click to expand...
Click to collapse
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108

timbernot said:
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108
Click to expand...
Click to collapse
Here's the thing. I'm super stubborn, and I think I know everything (cuz I do....) so of course I decided that I could figure something out, so I tried my way first............ didn't pan out.... anyway, I'm finding any time I flash a TWRP file, I have no access to recovery mode. Regardless if I do it manually through fastboot, or CM upgrade/downgrade or even the giovix fix (yes I tried it). My question is this, Where is there a return to stock option? of the giovix DLs I could find, I see a 'magisk root' 'TWRP' 'bootloader unlocker' and 'Xposed' tools, nothing else.... Am I missing something? or am I just skimming over that part?
I do appreciate all the help, seriously. Even if it seems like I'm not taking suggestions very well. It's moreso I don't have access to a computer most of the day, and it's not a huge priority since I went and bought a zfone 3 max a few days ago (decent phone for what it is....crazy battery life)

https://forum.xda-developers.com/zenfone2/general/tool-ze551mlmodder-t3458145
Functions:
1- Check connection status
2- Bootloader Unlocker
3- Flash TWRP 3.0.2-0 M1
4- Full-auto xposed flasher!
5- Full-auto root flasher!
5B- Full-auto root (Magisk+Phh's) compatible with 184!
6- ADB Shell
7- Return back to stock
8- Erase /system, /data and /cache for a clean upgrade
9 (HIDE)- Auto-reboot to bootloader
10- More functions inside!

well then forgive me for not downloading the correct option. I nowhere see this list among anything I downloaded, so maybe specify which is which ('full' or 'auto')....... I'm already downloading both of them again, because I'm not sure which I already had. But yea, one of the 2 only has the 4 options I mentioned.

Its not rocket science

timbernot said:
Its not rocket science
Click to expand...
Click to collapse
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?

joecost85 said:
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?
Click to expand...
Click to collapse
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )

timbernot said:
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )
Click to expand...
Click to collapse
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.

joecost85 said:
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.
Click to expand...
Click to collapse
EDIT"""" because i got it wrong too , i dont even think about , i just do it
It`s ->
From powered off position
Press Power and Vol +
at two vibes, release power
at boot up screen ,release vol+
in bootloader ,scroll vol up or down to and then select(press power) at recovery selection.
At dead android guy -> press vol + and power for 4 seconds -> release Vol +
You should be in recovery.

i am replying in this post since i have a similar problem, and I am as stubborn as OP. Me posting here is a big step in acknowledging my defeat at last. Hours of digging through the internet didn't solve my problem
I have changed my ifwi and dnx more times than i can remember. (my clean slate is mostly using xFSTK downloader with xFSTK_ZE551ML-sal358-amtech.vn files)
Using the above mentioned method (giovix`s modder tool) to go back to stock i still boot into fastboot, not recovery mode.
trying to unlock bootloader it says on the phone "unlock fail"
Using asus flash tool with raw files i get "gpt command failed"
Using a manual method i get the "gpt command failed" on the "6. fastboot oem partition /tmp/partition.tbl" step
in my opinion as soon as i get some kind of recovery my problems are solved. But have been working four hours on this problem with all possible solutions i could think of, nothing but frustration.
info: current ifwi 0094.0183 (wich should be M)
serial 01234........EF
and using the toolkit on "https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293" i found out my device firmware version is 198 (wich is probably not good in combo with the ifwi)
little update in a certain config (android 5 / ifwi 0094.177 / stock recovery) i can boot up untill the dead android icon, but with whatever key combo can't get past it... (vol up + power) / (vol down + power)
fastboot flash boot recovery.img (yep i am really desperate to get into recovery) doesn't even give me the dead android.
thank you beforehand!

Last paragraph with android 5 ifwi 0094.0177
Is your serial correct ?
Press vol + once is it correct?, if not you will have to xfstk first again and flash raw (twice) with temp bootloader 0094.1069
See my unbrick video for help

First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?

Speybrouck said:
First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?
Click to expand...
Click to collapse
Did you get this device in this condition ?
If not, what happened so that you lost serial ?
Anyway , i have never tried this because i have ALWAYS succeeded flashing raw (twice) to correct serial BUT it may work for you.( i am not sure you have a device that can have the serial corrected due to whether its been tampered with previous ) which affects recovery and IMEI.
Usually , xFSTK is used to install temp bootloader - Its supposed to be the lowest level form of unbricking procedure and restores temp bootloader so you can fastboot after-- flashing raw in fastboot via AFT(twice) restores serial -- 1st flash approx 3mins is with incorrect serial and temp bootloader.
After a couple of mins, cmds on phone pauses on RESULT=OK on phone.
You close AFT and open AFT again , input raw and set AFT up -- press Vol+ on phone -> once, serial will be corrected and 2nd flash can be started and left until it boots into android 5 by itself.
If GPT trouble , that link may help.
There is other programmes for starting to create serial and restoring .
Usually people who use these , have to dig deep into buildprop stuff which if tampered with can end up with problem such that you have.
Good luck
see if anything here helps
https://forum.xda-developers.com/showpost.php?p=70223946&postcount=8

Moto g6 play not booting need help ASAP

while following these instructions in the youtube video named Moto G6 2018 Install Twrp & Root Easy Tutorial 757 or 12:44 at this part i must have downloaded the wrong file since my build model is XT1922-9 type M373B could someone help me resolve me issue so i can fix my phone and finish the root cause my phone refuses to boot

Provide more info about your device including device variant, os version. More info the better so we know how to help you.

Jleeblanch said:
Provide more info about your device including device variant, os version. More info the better so we know how to help you.
Click to expand...
Click to collapse
It's a moto g6 play android 8 or it still turns on but it's stuck on the bootloader screen and I need help fixing that and finishing the rooting of my phone

kc02141994 said:
It's a moto g6 play android 8 or it still turns on but it's stuck on the bootloader screen and I need help fixing that and finishing the rooting of my phone
Click to expand...
Click to collapse
I figured out that much from your first post, I was referring to which variant specifically (ex: 192x-x) and do you know what the stock factory firmware version is?

Jleeblanch said:
I figured out that much from your first post, I was referring to which variant specifically (ex: 192x-x) and do you know what the stock factory firmware version is?
Click to expand...
Click to collapse
i dont know but all i know is my phones build model is XT1922-9 TYPE M373B the phone still turns on but it goes to the bootloader menu with the error message start up failed your device didint start up successfully use the sofware repair assistant on your computer to repair your device connect your device to your computer to get the software repair assistant AP fastboot flash mode secure error failed to load kernal fastboot reason fall through from normal boot i want to fix my phone and finish rooting it so i can use the wifi tether app and i dont know what to do which is why im asking for help i followed the instructions from that video but i downloaded and put in the wrong file i think my phone can be finished rooting and fixed so if i could just get the file i need i can finish rooting and use my phone again

kc02141994 said:
i dont know but all i know is my phones build model is XT1922-9 TYPE M373B the phone still turns on but it goes to the bootloader menu with the error message start up failed your device didint start up successfully use the sofware repair assistant on your computer to repair your device connect your device to your computer to get the software repair assistant AP fastboot flash mode secure error failed to load kernal fastboot reason fall through from normal boot i want to fix my phone and finish rooting it so i can use the wifi tether app and i dont know what to do which is why im asking for help i followed the instructions from that video but i downloaded and put in the wrong file i think my phone can be finished rooting and fixed so if i could just get the file i need i can finish rooting and use my phone again
Click to expand...
Click to collapse
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after

Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
ok that problem solved now im stuck on an infinite bootloop after i do the parts where the guy says wipe then download those files from the sd card and when i reboot the phone it does says N/A on the top left and starts boot looping

Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
i really need help on this i cant finish the root i dont know what im doing wrong im up to the part in the video i watched and after i finished doing that part it begins infinite rebooting and i dont know what to do i installed the right file did everything he did but instead of getting the message in the center i get N/A on the top left and then infinite reboots

Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
new problem i cant install magiks and now it says theres no OS installed this phone is seriously screwed up and its one of my only sources of internet

kc02141994 said:
new problem i cant install magiks and now it says theres no OS installed this phone is seriously screwed up and its one of my only sources of internet
Click to expand...
Click to collapse
Ok, well we're getting somewhere at least. Sounds like you have the right boot.img at the very least. Now we need to find you the right stock firmware (or even at minimum a system.img and vendor.img from some else with the same device).
I'll look around to see what I can find.
Next thing I need from you is to connect your device to the computer and reboot to bootloader and get me the output of..
Code:
fastboot getvar all
and copy/paste it to https://hastebin.com or copy/paste it to a text file and upload the text file as an attachment here (or wherever you want and post the link) so I can review it. That should tell me what I need to know to help you a little better. Do NOT just copy/paste the output into a post please.

Relock bootloader via download mode (only) for bootlooping G4?

So, straight to the point--anybody here have an idea about how to relock the bootloader on an H811 when ONLY download mode is available?
Over the last few days, this H811 has progressively succumbed to the dreaded G4 bootloop plague, and it is now purely bootlooping (doesn't even get to T-Mobile logo). Before it got so bad, I was able to flash it back to factory state (minus the unlocked bootloader) with the 20x KDZ using LGUP (reason why I did this will be explained below...). But this means that recovery is not available to get get into bootloader mode that way. And I have not yet had a complete successful boot after the KDZ flash to enable USB debugging, which would allow me to get into bootloader mode with the adb reboot bootloader command. So essentially, only download mode is available at this point, uggh...
The back story is that I just bought this used H811 to try out steadfasterX's LOS16, which, by the way, is fantastic! And almost immediately, the phone started displaying bootloop-ish symptoms. For example, like after the initial bootloader unlock, which I did immediately on receiving the device just a few days ago, the phone crashed during the optimizing apps step of the subsequent reboot (it probably overheated). I should have just relocked the bootloader at that point, and sent it back to the vendor for replacement. But I was anxious to try LOS16, and between occasional crashes, I eventually got it installed. But over the next few days, the crashing and occasional bootlooping became so progressively worse that I decided I really did need to send it back for replacement. So today I reflashed the 20x KDZ with LGUP, and that worked fine. But I'd like to relock the bootloader, too, so the vendor doesn't claim I screwed with it, and thus, that they are not responsible for replacing it. But as I mentioned, the only mode available at this point is download mode because it is purely bootlooping on the initial text screen without even getting to the TMo logo.
If I could get into bootloader mode, I could try to do either a a.) fastboot oem lock (given it is fully stock with the recent 20x KDZ flash, there should be no chance of bricking...), or b.) I could also flash just the misc partition extracted from the 20x KDZ. But again, without recovery, nor the possibility to enable USB debugging, I cannot get into bootloader mode. So that's why download mode is my only option.
steadfasterX's SALT works with download mode, but it cannot flash single partitions yet to follow the misc partition flashing strategy I mentioned above.
So what options does this leave me?
Option 1.) phone is in the freezer right now to see if I can get just one more good boot in order to get enable USB debugging, and thus, get to bootloader mode via adb; and from there, then relock the bootloader so the vendor doesn't see the bootloader unlocked message, and claim that I am responsible for the problems...; yeah, the freezer method is a long shot, but in the past with a VS986 that was bootlooping, I did get one final boot out of it for data rescue using this freezer method...
Option 2.) in download mode and via SALT, I can get a shell into the phone; maybe there is a way to flash just the misc partition (extracted from the 20x KDZ) via a command line in that shell, and thus, get the system back to a locked state?
Option 3.) well, send it back to the vendor as is, and hope that they do not try to claim it is my fault because the see the unlocked bootloader message...
Option 4.) if options 1-3 do not work, well, perhaps give LG a call to see if they will fix the circuit board; by the way, they did it for the VS986 I mentioned above without any questions whatsoever; but the difference is that I was the original purchaser of that VS986 whereas this H811 is a secondhand purchase, and LG might use that as a reason for not fixing it.
Any other options that I might be missing? Thanks for any wisdom or suggestions you might be able to provide!
Anyway, my learning lesson from all of this is patience--like I said, I should have returned the device immediately on seeing the first signs of bootlooping because in my experience with both the VS986, and this newly received H811, well, once bootlooping symptoms start, they progress very quickly...

verbage said:
So, straight to the point--anybody here have an idea about how to relock the bootloader on an H811 when ONLY download mode is available?
Over the last few days, this H811 has progressively succumbed to the dreaded G4 bootloop plague, and it is now purely bootlooping (doesn't even get to T-Mobile logo). Before it got so bad, I was able to flash it back to factory state (minus the unlocked bootloader) with the 20x KDZ using LGUP (reason why I did this will be explained below...). But this means that recovery is not available to get get into bootloader mode that way. And I have not yet had a complete successful boot after the KDZ flash to enable USB debugging, which would allow me to get into bootloader mode with the adb reboot bootloader command. So essentially, only download mode is available at this point, uggh...
The back story is that I just bought this used H811 to try out steadfasterX's LOS16, which, by the way, is fantastic! And almost immediately, the phone started displaying bootloop-ish symptoms. For example, like after the initial bootloader unlock, which I did immediately on receiving the device just a few days ago, the phone crashed during the optimizing apps step of the subsequent reboot (it probably overheated). I should have just relocked the bootloader at that point, and sent it back to the vendor for replacement. But I was anxious to try LOS16, and between occasional crashes, I eventually got it installed. But over the next few days, the crashing and occasional bootlooping became so progressively worse that I decided I really did need to send it back for replacement. So today I reflashed the 20x KDZ with LGUP, and that worked fine. But I'd like to relock the bootloader, too, so the vendor doesn't claim I screwed with it, and thus, that they are not responsible for replacing it. But as I mentioned, the only mode available at this point is download mode because it is purely bootlooping on the initial text screen without even getting to the TMo logo.
If I could get into bootloader mode, I could try to do either a a.) fastboot oem lock (given it is fully stock with the recent 20x KDZ flash, there should be no chance of bricking...), or b.) I could also flash just the misc partition extracted from the 20x KDZ. But again, without recovery, nor the possibility to enable USB debugging, I cannot get into bootloader mode. So that's why download mode is my only option.
steadfasterX's SALT works with download mode, but it cannot flash single partitions yet to follow the misc partition flashing strategy I mentioned above.
So what options does this leave me?
Option 1.) phone is in the freezer right now to see if I can get just one more good boot in order to get enable USB debugging, and thus, get to bootloader mode via adb; and from there, then relock the bootloader so the vendor doesn't see the bootloader unlocked message, and claim that I am responsible for the problems...; yeah, the freezer method is a long shot, but in the past with a VS986 that was bootlooping, I did get one final boot out of it for data rescue using this freezer method...
Option 2.) in download mode and via SALT, I can get a shell into the phone; maybe there is a way to flash just the misc partition (extracted from the 20x KDZ) via a command line in that shell, and thus, get the system back to a locked state?
Option 3.) well, send it back to the vendor as is, and hope that they do not try to claim it is my fault because the see the unlocked bootloader message...
Option 4.) if options 1-3 do not work, well, perhaps give LG a call to see if they will fix the circuit board; by the way, they did it for the VS986 I mentioned above without any questions whatsoever; but the difference is that I was the original purchaser of that VS986 whereas this H811 is a secondhand purchase, and LG might use that as a reason for not fixing it.
Any other options that I might be missing? Thanks for any wisdom or suggestions you might be able to provide!
Anyway, my learning lesson from all of this is patience--like I said, I should have returned the device immediately on seeing the first signs of bootlooping because in my experience with both the VS986, and this newly received H811, well, once bootlooping symptoms start, they progress very quickly...
Click to expand...
Click to collapse
For boot looping tricks see my signature while I think freezer is your best bet here .
In SALT -> advanced menu -> wipe partitions
Choose misc and wipe only that.
Locked again .
Sent from my OnePlus 6T using XDA Labs

steadfasterX said:
For boot looping tricks see my signature while I think freezer is your best bet here .
In SALT -> advanced menu -> wipe partitions
Choose misc and wipe only that.
Locked again .
Click to expand...
Click to collapse
Ah, wonderful! I was thinking that there were some special bits in the misc partition, and thus, it had to be flashed. But if I can simply wipe it, perfect! Thanks so much, steadfasterX, for your unending generosity with helping the community here!

No luck with the freezer technique after several attempts. I did get as far as the T-Mobile logo on one try, but it went back to bootlooping immediately. So I proceeded with the misc partition wipe via SALT, and the operation appeared go fine with a success message. But then on rebooting, the bootloader unlocked message still appeared. Not that it should make a difference, but I repeated the operation several times and used several different reboot mechanisms--via that SALT reboot button, pulling the battery, etc., but the bootloader unlocked message still sticks. So it looks like I might have to send it back as is.

verbage said:
No luck with the freezer technique after several attempts. I did get as far as the T-Mobile logo on one try, but it went back to bootlooping immediately. So I proceeded with the misc partition wipe via SALT, and the operation appeared go fine with a success message. But then on rebooting, the bootloader unlocked message still appeared. Not that it should make a difference, but I repeated the operation several times and used several different reboot mechanisms--via that SALT reboot button, pulling the battery, etc., but the bootloader unlocked message still sticks. So it looks like I might have to send it back as is.
Click to expand...
Click to collapse
Ah yea the h811 is different then the others .. I rem again.. There are also persist and others involved for the h811 . You could flash the ilapo TWRP from my leech server and flash the following partitions with dd:
devinfo, misc, persist, persistent, drm, sns
Ensure you use the exact same firmware as your current bootloader stack
Sent from my OnePlus 6T using XDA Labs

steadfasterX said:
Ah yea the h811 is different then the others .. I rem again.. There are also persist and others involved for the h811 . You could flash the ilapo TWRP from my leech server and flash the following partitions with dd: devinfo, misc, persist, persistent, drm, sns
Click to expand...
Click to collapse
Hmmm, I wish I could flash the ilapo TWRP, but after recently flashing the official 20x KDZ using LGUP, I have not been able to get even one successful, complete boot to enable USB debugging. And of course, the TWRP recovery partition was vaped by flashing the KDZ, too. So the only functionality available at this point is download mode. But I have not yet found a way to flash only select partitions (like the six you mentioned) in download mode. For sure, it must be possible (maybe like by using dd for manual, command line flashing using the limited shell provided by SALT). But I am not at that level of expertise yet
This said, I have been doing some exploring regarding the six partitions you mentioned. I used SALT to unpack the original H811 20x KDZ image, and it seems that five of the six partitions (devinfo, misc, persistent, drm, sns) are just filled with zeros. So I suspect there is no real need to actually flash those directly--I think I can just wipe them with SALT for the same effect, right? This leaves just the sixth partition--persist--which is almost all zeros itself, too, with the exception of about 3,500 non-zero bytes spread throughout the file. So maybe in the long run this might boil down to simply having to flash one partition (i.e. persist) as the rest can be wiped since they are all zeros anyway? Whatever the case, whether I have to flash just one partition or all six, the problem remains--there is no straightforward path available to me for flashing a single selected partition via download mode.
-------------------------------
Okay, I have been sitting on the above paragraphs for a couple of days, which gave me some more time to ponder the situation, and make some useful observations. In particular, I have closely watched the dim screen on the H811 while using LGUP to flash the official 20x KDZ image. At one point about halfway through the process, it starts quickly flashing up the names of partitions as it presumably flashes them by name. It appears that the persist partition is one of those which is flashed... And so (maybe?) eureka--could this solve my dilemma of having to flash just a single, selected partition via download mode???
More specifically, if I just load the full KDZ image via LGUP, which takes care of the persist partition, and then if I just wipe the other five partitions (devinfo, misc, persistent, drm, sns) under SALT, well, will this effectively relock the bootloader???
Happy to hear any comments about this before I attempt it!

verbage said:
Hmmm, I wish I could flash the ilapo TWRP, but after recently flashing the official 20x KDZ using LGUP, I have not been able to get even one successful, complete boot to enable USB debugging. And of course, the TWRP recovery partition was vaped by flashing the KDZ, too. So the only functionality available at this point is download mode. But I have not yet found a way to flash only select partitions (like the six you mentioned) in download mode. For sure, it must be possible (maybe like by using dd for manual, command line flashing using the limited shell provided by SALT). But I am not at that level of expertise yet
This said, I have been doing some exploring regarding the six partitions you mentioned. I used SALT to unpack the original H811 20x KDZ image, and it seems that five of the six partitions (devinfo, misc, persistent, drm, sns) are just filled with zeros. So I suspect there is no real need to actually flash those directly--I think I can just wipe them with SALT for the same effect, right? This leaves just the sixth partition--persist--which is almost all zeros itself, too, with the exception of about 3,500 non-zero bytes spread throughout the file. So maybe in the long run this might boil down to simply having to flash one partition (i.e. persist) as the rest can be wiped since they are all zeros anyway? Whatever the case, whether I have to flash just one partition or all six, the problem remains--there is no straightforward path available to me for flashing a single selected partition via download mode.
-------------------------------
Okay, I have been sitting on the above paragraphs for a couple of days, which gave me some more time to ponder the situation, and make some useful observations. In particular, I have closely watched the dim screen on the H811 while using LGUP to flash the official 20x KDZ image. At one point about halfway through the process, it starts quickly flashing up the names of partitions as it presumably flashes them by name. It appears that the persist partition is one of those which is flashed... And so (maybe?) eureka--could this solve my dilemma of having to flash just a single, selected partition via download mode???
More specifically, if I just load the full KDZ image via LGUP, which takes care of the persist partition, and then if I just wipe the other five partitions (devinfo, misc, persistent, drm, sns) under SALT, well, will this effectively relock the bootloader???
Happy to hear any comments about this before I attempt it!
Click to expand...
Click to collapse
I just know that the mentioned partitions are involved in unlocking the bootloader on a h811 - so they are involved in locking it down as well.
while doing my PoC for unlocking all g4's we found that if you backup ALL these partitions when your device is unlocked and re-flash them on the same device (h811 only) while it is locked it will be unlocked again.
the thing is lgup will never flash ALL partitions on a regular flash and thats why you keep your unlocked state (usually) after flashing a new kdz.
For sure thats the case for misc and very likely for the above mentioned.
afaik selecting the refurbish mode will flash any of them.
so TLDR; you COULD wipe the above partitions in SALT, one by one and boot after each to see if its enough.
the second option is to use the lgup developer version. it might be able to flash single partitions (havent used that for long time). would give it a try but you have to google for it.
the third option is opening a shell with SALT while in download mode (advanced menu) and see if you can do this:
https://forum.xda-developers.com/showpost.php?p=74433698&postcount=149
btw: what is the LAF protocol version shown in the SALT main window? could you pls share the debug log (advanced menu -> debug log -> upload button)
yea and the last resort would be to bring the device down to 9008 mode and using QFIL to re-flash all partitions involved (requires a lot of knowledge and preparation though)
.-

steadfasterX said:
I just know that the mentioned partitions are involved in unlocking the bootloader on a h811 - so they are involved in locking it down as well.
Click to expand...
Click to collapse
Thanks for all the pointers and great guidance! I will see where it takes me this weekend.
For the moment, the LAF protocol version is listed as 1000001, and I posted the SALT debug log at https://bpaste.net/show/eqxU.

verbage said:
Thanks for all the pointers and great guidance! I will see where it takes me this weekend.
For the moment, the LAF protocol version is listed as 1000001, and I posted the SALT debug log at https://bpaste.net/show/eqxU.
Click to expand...
Click to collapse
thats great. this version is fully supported in SALT for flashing!
start SALT in a terminal with
Code:
sudo ~/programs/SALT/salt --experimental
and you get new buttons in the main window.
That makes things a lot easier I guess
-.

steadfasterX said:
thats great. this version is fully supported in SALT for flashing!
start SALT in a terminal with
Code:
sudo ~/programs/SALT/salt --experimental
and you get new buttons in the main window.
That makes things a lot easier I guess
-.
Click to expand...
Click to collapse
Yes, I saw the flashing temporarily not auto-enabled comment in the log, and was about to hunt down how to do it, but now that I know the needed switch, perfect. In fact, I just did it, and I see the new buttons with extended functionality--great! I can't play any more now, but for sure, this weekend!
Thank you so much, steadfasterX, for your generous and unending support for the user community here!

verbage said:
I can't play any more now, but for sure, this weekend!
Click to expand...
Click to collapse
Okay, okay, okay--I had time to play...
I first backed up the six H811 partitions in question (i.e. devinfo, misc, persist, persistent, drm, sns) just in case... And then wiped all six of them in SALT.
Now the phone reboots with no unlocked bootloader message on startup--great. Still crazy bootlooping, though, but now without the unlocked bootloader warning so I feel much more confident in exchanging it for a replacement.
In sum, wiping those six partitions does the trick--no need to flash just the persist partition as was discussed in previous postings. For sure, that might wreak havoc with the MAC addresses or similar, but in this case, it doesn't really matter because the phone is already completely disfunctional because of the bootlooping.
Thanks again, steadfasterX!

verbage said:
Okay, okay, okay--I had time to play...
I first backed up the six H811 partitions in question (i.e. devinfo, misc, persist, persistent, drm, sns) just in case... And then wiped all six of them in SALT.
Now the phone reboots with no unlocked bootloader message on startup--great. Still crazy bootlooping, though, but now without the unlocked bootloader warning so I feel much more confident in exchanging it for a replacement.
In sum, wiping those six partitions does the trick--no need to flash just the persist partition as was discussed in previous postings. For sure, that might wreak havoc with the MAC addresses or similar, but in this case, it doesn't really matter because the phone is already completely disfunctional because of the bootlooping.
Thanks again, steadfasterX!
Click to expand...
Click to collapse
Haha great ! Glad it worked for you ! Hope the replacement goes fine now
Sent from my OnePlus 6T using XDA Labs

[SOLVED] boot loop after i tried to fix broken root

I tried for like 3 hours to find a boot.img and i had root on my phone, but without wifi and sound.
a quick google search showed me that it was because i had a wrong version of the boot.img, afterwards i found another one and now after i have tried installing twrp, booting and flashing using adb (stock and modified versions of boot.img) but it just keeps bootlooping. in twrp i cant wipe, make a backup, see any files in /storage/ and i have no clue what to do next.

What model 7T do you have? HD1907? What was the rom that you were using before you installed TWRP on? OOS12 does not support TWRP. Custom rom A13 does not support TWRP. Only a few custom rom A12 and OOS11 support TWRP.

Idk but I'm just wondering if flashing the last working rom image (dirty flash)? That would eliminate TWRP(?) and eliminate Magisk(?) while hopefully keeping the device from being wiped possibly?
*** Hopefully someone could/would verify this before you attempt... ***

i was on android 11 but i cant remember the version, i have HD1903 (EU ver). i THINK i had the one from the oneplus website(https://service.oneplus.com/us/search/search-detail?id=2096229) but idk anymore

I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore

MimKA22 said:
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
Click to expand...
Click to collapse
Msmtool back to oos11

can you describe how to use it or send a link to tutorial or smth thx man <3

MimKA22 said:
can you describe how to use it or send a link to tutorial or smth thx man <3
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

i cant find the file for my current version and it doesnt work if i try it with the only version that is android 11

and i cant turn my phone back on
and after i installed the drivers i had to restart my pc and now there is this thing at the bottom right:
testmode
windows 10 pro
...

i waited until my phone had no more battery charge and now im bootlooping again :/

nvm it just booted

im downgrading it now and i dont get the error "smth communication smth" in msmtool anymore
alr it worked my phone is wiped again but i can turn on wifi and sound
but how do i root my phone now? I have an Idea, im gonna write step by step what i think gets me a rooted phone please confirm if that would not break my phone ^^' (bootloader already unlocked)
1. enable usb debugging and allow my pc
2. download and install the latest magisk version from the github
3. download magisk patched boot.img for ver 11.0.5.1BA BUT since i cant find anything on the internet im gonna have to use the zip file from the unbrick tool thing (https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/EU_HD65BA/R/) and then patch the boot.img using magisk myself
4. then use platform tools and type following commands: "adb reboot fastboot", "fastboot flash boot {the patched boot image file}"
5. then use magisk to direct install the root thing

i just realisized the unbrick thing that i wanted to use instead of a boot.img doesnt have a boot.img in it... WHERE CAN I FIND A BOOT.IMG brooo androidfilehost.com doesnt have it the unbrick tool doesnt have it
omg i realized i could update my phone to 11.0.9.1 then download the same version from official website and use the dumper to get the boot.img **** meee

wait it sais its 11.0.9.1HD65 AA and not BA **** me

k nvm i just changed the site settings to germany and now its BA

i just went for it and now my phone is rooted thank you very much for your help i would've prob tried to revert back to stock for like 2 weeks and then cry that i cant root my phone thank you so much xd