Hey guys. I've noticed that recently my advance power menu app has started acting weird it seems to be losing root access. The only way to get it to work, is to open the app, at which point it's granted root access. It will work once. Each subsequent time it requires being opened again before it will work. I'm on stock rooted us998 20H, with latest magisk.
Ballroomblitz said:
Hey guys. I've noticed that recently my advance power menu app has started acting weird it seems to be losing root access. The only way to get it to work, is to open the app, at which point it's granted root access. It will work once. Each subsequent time it requires being opened again before it will work. I'm on stock rooted us998 20H, with latest magisk.
Click to expand...
Click to collapse
Which Magisk are you on? You can update to later, past 18.x now that you are on last Oreo. Maybe that will help.
Also with stock Pie (which you are not on), we found couldn't use Advanced Power Menu, so had to go back to using Reboot Recovery app shortcut like in the old days. So, you can install that as backup method to get to TWRP. Install, give it root privileges, make shortcut on the desktop.
My Advanced Power Menu is still working fine with Magisk 18.1, but trying to help you find a solution...
ChazzMatt said:
Which Magisk are you on? You can update to later, past 18.x now that you are on last Oreo. Maybe that will help.
Also with stock Pie (which you are not on), we found couldn't use Advanced Power Menu, so had to go back to using Reboot Recovery app shortcut like in the old days. So, you can install that as backup method to get to TWRP. Install, give it root privileges, make shortcut on the desktop.
My Advanced Power Menu is still working fine with Magisk 18.1, but trying to help you find a solution...
Click to expand...
Click to collapse
I had updated to 20.4. that may be part of the problem. I'm going to downgrade to 20.1 and see if that has any effect.
Thanks.
I tried going back to Magisk 20.0, but APM is still requiring that i provide it superuser rights everytime.
Just out of curiosity, if I wanted to completely clean my device and start fresh, what would you recommend?
Ballroomblitz said:
I tried going back to Magisk 20.0, but APM is still requiring that i provide it superuser rights everytime.
Just out of curiosity, if I wanted to completely clean my device and start fresh, what would you recommend?
Click to expand...
Click to collapse
Try one other thing. In TWRP, flash the Magisk uninstaller and then install Magisk 19.3 in TWRP.
When you went back to 20.0 did you flash the uninstaller in TWRP first?
ChazzMatt said:
Try one other thing. In TWRP, flash the Magisk uninstaller and then install Magisk 19.3 in TWRP.
When you went back to 20.0 did you flash the uninstaller in TWRP first?
Click to expand...
Click to collapse
I did. I haven't tried 19.3 yet. I'll give that a try. Something else going on that I don't understand. When I try to download files from someone's Google drive I keep getting an error message that drive has stopped unexpectedly. Don't know if it's related. No problems downloading on my laptop. AIX files FYI.
Ballroomblitz said:
I did. I haven't tried 19.3 yet. I'll give that a try. Something else going on that I don't understand. When I try to download files from someone's Google drive I keep getting an error message that drive has stopped unexpectedly. Don't know if it's related. No problems downloading on my laptop. AIX files FYI.
Click to expand...
Click to collapse
Installed magisk uninstaller. Installed 19.3. APM still requires that I open it so it is granted root access before it works. Got to do it everytime for it to work. Still can't access files on drive either. Still wondering if I need to clean the phone and start over from scratch. I don't necessarily mind doing that. I've tried flashing us998 pie as well as vs996 pie and had issues with both. Now I just want things to work correctly on 20H. I did some kdz flashing after messing with the pie ROMs. I might have done some of that incorrectly.
Ballroomblitz said:
Installed magisk uninstaller. Installed 19.3. APM still requires that I open it so it is granted root access before it works. Got to do it everytime for it to work. Still can't access files on drive either. Still wondering if I need to clean the phone and start over from scratch. I don't necessarily mind doing that. I've tried flashing us998 pie as well as vs996 pie and had issues with both. Now I just want things to work correctly on 20H. I did some kdz flashing after messing with the pie ROMs. I might have done some of that incorrectly.
Click to expand...
Click to collapse
Any other thoughts on this @ChazzMatt?
Ballroomblitz said:
Any other thoughts on this @ChazzMatt?
Click to expand...
Click to collapse
Will answer tonight to give you range of options.
I simply open Magisk Manager | Modules and use the advanced reboot options there for the infrequent times I need to boot to recovery or bootloader.
Bawdy George said:
I simply open Magisk Manager | Modules and use the advanced reboot options there for the infrequent times I need to boot to recovery or bootloader.
Click to expand...
Click to collapse
That's a good point. I don't reboot to recovery much myself. No real reason to. Outside of the occasional backup I might run, getting to recovery isn't regularly needed. As I mentioned to Chazz, however, I'm a little anal about things running the way they're supposed to on my phone. When I push the power button, I like to know that I have the option right then to select recovery without issue. I didn't have a good reason that explains why it no longer works, and that bugs me.
Bawdy George said:
I simply open Magisk Manager | Modules and use the advanced reboot options there for the infrequent times I need to boot to recovery or bootloader.
Click to expand...
Click to collapse
Even easier way is Reboot Recovery app shortcut on desktop. Whereas, the Magisk Manager option is like 3 levels deep in that app.
We used this originally with Oreo, then I found the Advance Power Menu. But Advance Power Menu doesn't work with Pie, so for those KDZ I have to recommend this again:
STRONG SUGGESTION: After successfully doing all this, when you finally boot back to system, install an app like this to easily facilitate rebooting to TWRP recovery in the future: Recovery Reboot. Allow it root privileges when asked by Magisk and put icon shortcut on your desktop.
{
"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"
}
Ballroomblitz said:
That's a good point. I don't reboot to recovery much myself. No real reason to. Outside of the occasional backup I might run, getting to recovery isn't regularly needed. As I mentioned to Chazz, however, I'm a little anal about things running the way they're supposed to on my phone. When I push the power button, I like to know that I have the option right then to select recovery without issue. I didn't have a good reason that explains why it no longer works, and that bugs me.
Click to expand...
Click to collapse
Yeah, I can relate. I got my cheap used V30 with the express intention to tinker with it, and for the wired audio.
Ballroomblitz said:
I tried going back to Magisk 20.0, but APM is still requiring that i provide it superuser rights everytime.
Just out of curiosity, if I wanted to completely clean my device and start fresh, what would you recommend?
Click to expand...
Click to collapse
Here are three options -- each one successively more powerful but also harder.
Option 1
Boot into TWRP. Go to Wipe, at bottom choose to Swipe to Factory Reset. You should still have Oreo US998 20h system installed. You aren't wiping internal memory. You will need to reflash Magisk before rebooting.
If you are slightly OCD, you will also reflash the other two root files -- Encryption Disabler (Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip) and Root Check Disabler (AK3_RCTD_Remover.zip). You shouldn't NEED to do that -- as you are just factory resetting what you already have -- but I would rather do it and not need it, than not do it and then find out "Oh, for some reason you did need to do it". (You can find those two files in the Option 3 link.) Flash Magisk, then the Encryption Disabler, Root Check Disabler, then Magisk AGAIN. Then reboot.
Option 2.
Boot into TWRP. Go to Wipe, at bottom choose to Swipe to Factory Reset. Furthermore, wipe internal memory. You will be asked to confirm with YES. You will have no OS, so do NOT reboot from TWRP until you fix that. Before you use this option, you will need US998 Oreo 20e, 20f, 20g, 20g, 20h TWRP flashable zips + Magisk + Encryption Disabler + Root Check Disabler stored on microSD card ahead of time OR connect phone to PC while in TWRP mode and drag over all the files like with a flash drive. If you are depending on TWRP drag-and-drop to transfer files after wiping phone's internal memory, please test this functionality ahead of time. You don't want to wipe your internal memory and then find your phone TWRP can't see your PC via USB cable.
Flash all the TWRP flashable zips back-to-back, then flash Magisk, then the Encryption Disabler, Root Check Disabler, then Magisk AGAIN. Then reboot. You can "stack" them all to flash back-to-back in TWRP, then hit the install button and they will successively go through the list you create.
Option 3
Use Dev Patched LGUP to flash US998 20h Oreo KDZ in Refurbish mode. This will totally take you back to stock firmware, but you will still have unlocked bootloader. Then, follow this post instructions below to reinstall TWRP and root. It's basically Section 6 of WTF Instructions in a standalone post. IGNORE that it says it's for Pie. I wrote it for people who updated to Pie through KDZ and needed to reinstall TWRP. It will work for you on US998 20h Oreo.
INSTALL or REINSTALL TWRP on stock KDZ with ALREADY-UNLOCKED BOOTLOADER
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3285
ChazzMatt said:
Option 1
Boot into TWRP. Go to Wipe, at bottom choose to Swipe to Factory Reset. You should still have Oreo US998 20h system installed. You aren't wiping internal memory. You will need to reflash Magisk. If you are slightly OCD, you will reflash the other two root files also -- encyrption disabler and root check disabler. You shouldn't NEED to do that, but I would rather do it and not need it, than not do it and then find out "oh, for some reason you did need to do it".
Option 2.
Boot into TWRP. Go to Wipe, at bottom choose to Swipe to Factory Reset. Furthermore, wipe internal memory. You will be asked to confirm with YES. You will have no OS. So, before you do this, you will need US998 Oreo 20e, 20f, 20g, 20g, 20h TWRP flashable zips + Magisk + encryption disabler + root check disabler on microSD card ahead of time or connect phone to PC while in TWRP mode and drag over like a flash drive. If you are depending on TWRP drag and drop, test this functionality ahead of time. You don't want to wipe your internal memory and find your phone TWRP can't see your PC via USB cable.
Flash all the TWRP flashable zips back to back, then flash Magisk, then the encryption disabler, root check disabler, then Magisk again. Then reboot.
Option 3
Use Dev Patched LGUP to flash US998 20h Oreo KDZ in Refurbish mode. This will totally take you back to stock firmware, but you will still have unlocked bootloader. Follow this post to reinstall TWRP and root. It's basically Section 6 of WTF Instructions in a standalone thread. IGNORE that it says it's for Pie. I wrote it for people who updated to Pie through KDZ and needed to reinstall TWRP. It will work for you on US998 20h Oreo.
INSTALL or REINSTALL TWRP on stock KDZ with ALREADY-UNLOCKED BOOTLOADER
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3285
Click to expand...
Click to collapse
Man! Don't know what to say, but thank you for taking the time to provide such an in-depth assist. I'll start picking away tomorrow, and let you know what happens.
Related
WORK IN PROGRESS: This all started in a quest to stay locked, but have root and Magisk running on my phone, and eventually unlocking to install a custom kernel which wouldn't trip SafetyNet.
I've had to compromise on staying locked as unlocking the boot loader was ultimately necessary. As of this update to the guide, I have root, Magisk, and system-less Xposed working with each other. SafetyNet, however, is partially broken.
This is my experience on my new ZTE Axon 7 unlocked U.S. variant (A2017U), running build B29.
I'm certain that most of my problems had to do with the write-protected /system partition, as well as the encryption of fstab (verity check encryption/SE Linux status). I finally got some things working by using the method that follows, and I've opened this thread for anyone wishing to learn from what I've done, and possibly sharing with us, better methods of achieving this:
-> Device needs to have its bootloader unlocked, or else you will get a boot-loop into EDL mode. Use your prefered method for this.
-> TWRP 3.0.2.0
-> Last working SuperSU v2.65, which should install in systemless mode (tenfar's patched boot.img doesn't work for me).
-> A way to disable fstab encryption. I got it done using both: a custom kernel called Kali Kernel (also check this post for a stripped down version of the kernel) and through DrakenFX's script available here.
-> Magisk Manager, and Magisk flashable zip versions available here (look under downloads, v2.5 and v9 respectively as of this writing): [url]http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445[/URL]
-> ADB shell (you can either use Terminal Emulator from the Play Store or ADB Shell on your computer.
After you have unlocked the bootloader, with any of the unlocking guides here on XDA (I used DrakenFX's zip, ultimately. God bless that dude!): Boot into TWRP, flash SuperSU v2.65 mentioned above.
Proceed to flash DrakenFX's boot loop patch.
Boot into the system.
Update SuperSU to the latest version through the Play Store (v2.79 as of this writing, should be automatic).
Open the SuperSU APK and update the SU binary at the prompt. Reboot the system.
Once booted back into the system: Open an ADB shell (either through terminal emulator, or through ADB shell on a computer) and type the following:
Code:
su
reboot disemmcwp
The phone will reboot.
Boot into TWRP and flash the Magisk v9 zip file.
Here, I would advise flashing the Kali kernel as well (if you're interested in passing SafetyNet validation, or even if you aren't as it worked for me this way). There is a stripped down version of the kernel available here (source post here).
Boot back into the system.
Once you're up, proceed to install the Magisk Manager.
If it is still showing up undetected then reinstall through the app, reboot into TWRP and flash the Magisk v9 .zip file as well, and reboot into the system.
Reboot system at the prompt.
A word of caution regarding Magisk's implementation of suHIDE: it can't be used with this method as it breaks root after a while, and apparently has no impact on a superuser system which is not a Magisk module. I am exploring Chainfire's suHIDE implementation in the coming days.
Hope it works for you all!
Edits: Updated guide to reflect my current research gains, and removed superfluous text. I will upload screenshots of my status as soon as I get back to my computer.
Updated screenshots to the current state.
{
"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"
}
Still no work for me. I can install it but when i reboot Magisk disapear. And i don't know why but magisk worked good before i do a factroy reset.
Alright, still working on streamlining my methods, and I've managed to get root, Magisk, and system-less Xposed playing nice together.
The next step was to try to not trip SafetyNet with this setup, and I've made some progress on that front. It involves installing the patched Kali kernel (as I've done so far) and suHIDE from Chainfire (next test, tomorrow).
I'll update the OP tomorrow, with screenshots!
Good for you!
Everything I try to install it didn't survive to reboot ðŸ™.
I make a fresh install and same. I don't know why. Last time I tried it worked.
I tried everything 😢
Znuf said:
Good for you!
Everything I try to install it didn't survive to reboot ðŸ™.
I make a fresh install and same. I don't know why. Last time I tried it worked.
I tried everything 😢
Click to expand...
Click to collapse
I've just updated the guide. Do you want to give it a shot and see whether it works for you?
It's exactly what I do many time, at least 10.
But it's never activated after boot. :sad:
If I found a way I'll post here
I found a way.
On unlocked phone.
Install supersu 2.65 from here https://download.chainfire.eu/921/SuperSU
Reboot system.
Update supersu via play store
Download magisk and magisk manager from here. http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Install magisk manager.
Install magisk v9.
Reboot when it prompt but Boot directly in twrp.
Flash magisk v9.
Reboot system.
This worked for me.
Znuf said:
I found a way.
On unlocked phone.
Install supersu 1.65
Reboot system.
Update supersu via play store
Download magisk and magisk manager from here. http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Install magisk manager.
Install magisk framwork
Reboot when it prompt but Boot directly in twrp.
Flash magisk v9
Reboot system.
This worked for me. 😀
Click to expand...
Click to collapse
I have a couple of doubts about your procedure before testing it twice:
1. Are you sure you have to install SU v1.65? Why not SU v2.65?
2. you are referring to the magisk framwork, but I do not find it. Were you referring to Xposed framework maybe?
It would be easier if could provide some links to the download pages, just to match versions.
Thanks
I update my post. Sorry for the poor precision. It was late. ?
Znuf said:
I update my post. Sorry for the poor precision. It was late.
Click to expand...
Click to collapse
Thanks for the clarification, I understand that when you say install Magisk v9, you rever to install within the Magisk manager app, and then later, booting directly to TWRP flashing the Magisk v9 zip file.
I have been experimenting with Safetynet helper and I have found that it doesn't pass when the phone is unlocked. As soon as I unlock the bootloader, the safetynet helper reports a CTS profile doesn't match. Even when using the stock boot and stock system without any root!!!!
Any thought on this???
blue skies
So Android Pay is working with this method?
JKSurf said:
So Android Pay is working with this method?
Click to expand...
Click to collapse
Not for me.
I am still experimenting, there must be a way.
---------- Post added at 17:30 ---------- Previous post was at 17:23 ----------
Znuf said:
I found a way.
On unlocked phone.
Install supersu 2.65 from here https://download.chainfire.eu/921/SuperSU
Reboot system.
Update supersu via play store
Download magisk and magisk manager from here. http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Install magisk manager.
Install magisk v9.
Reboot when it prompt but Boot directly in twrp.
Flash magisk v9.
Reboot system.
This worked for me.
Click to expand...
Click to collapse
I have done exactly that with the B29 ROM with stock boot and system. For some reason Magisk manager keep asking for Magisk v9 even after the whole process has been completed. I have root thanks to SuperSU, but safetynet helper test doesn't pass.
A better question is if you can pass the SafetyNet check apps.
I posted this in the thread that started this one, but with the official TWRP you can flash recent versions of SuperSU, not just 2.65 anymore (that was a limitation of the unofficial).
I know this thread relates to getting Magisk working, but unless there's a specific module you're looking to use, I don't see a benefit to using it for systemless root over SuperSU. I had tried to install it before using unofficial TWRP and had problems, but I think those, like the inability to install SuperSU past 2.65 we're due to faults with the unofficial TWRP. Official TWRP should install Magisk just fine (haven't cared to try it).
That said, if Android Pay is you're concern SuperSU might be the way to go. I am running SuperSU 2.79, Xposed 86.2, suhide 0.55, and Root Switch 1.3.3.2 and am able to pass both of the popular SN test apps (SafetyNet Helper and SafetyNet Playground). I don't use AP to know if that functions, but Pokémon GO, which also relies on SafetyNet runs just fine.
Also, as far as kernel goes, if you want one that doesn't have all the extra stuff the Kali NetHunter kernel does, there's a stock kernel patched for SafetyNet, kcal, and exFAT in this post of the same thread.
If you don't care about Xposed, SuperSU and Root Switch should be all you need to pass.
And as I mentioned in the other thread, this will likely all be rendered useless by the Nougat update hopefully coming next month.
The method I posted as an update in the OP the other day closely follows @Znuf's method, and all the relevant files are linked in the OP. Still a bit busy to experiment more, but this is how far I had gotten with the method I had posted, and, in theory, should work with suHIDE. Even the Kali Kernel I have linked to is the patched one without the extra tools.
With suHIDE my config should be similar to @-Duir-'s configuration, except that I've installed Xposed through Magisk (Xposed v87) instead.
I'll try this out and update it soon. Screenshots attached is my progress on the last update..
Has anyone tried to replicate this using a2017g? From what I can tell it should all work but I'm worried about flashing the bootloop fixer script that is designed for a2017u
H0lmEd said:
Has anyone tried to replicate this using a2017g? From what I can tell it should all work but I'm worried about flashing the bootloop fixer script that is designed for a2017u
Click to expand...
Click to collapse
The bootloop fixer script should work on all devices as it just disables forced encryption in your bootloader. Make backups and try it out. If you experience a problem just restore the backed-up boot partition.
I'm on 2017g no bootloop.
Erahgon said:
With suHIDE my config should be similar to @-Duir-'s configuration, except that I've installed Xposed through Magisk (Xposed v87) instead.
Click to expand...
Click to collapse
suhide will only work with Xposed 86.2 (which is provided in the same post).
Do those configurations support SafetyNet while Xposed modules are loaded? I don't want to softboot the phone when I am in a store and I have to pay.
Thanks
Oki said:
Do those configurations support SafetyNet while Xposed modules are loaded? I don't want to softboot the phone when I am in a store and I have to pay.
Thanks
Click to expand...
Click to collapse
Yep, Xposed modules still work, all you're toggling is root and no reboot required to disable/enable root. It's worth clarifying that while modules will still work, root apps obviously won't while disabled. Also, while root is disabled, Xposed installer will say Xposed isn't installed - as long as Xposed installer is green when root is enabled you're good.
DISCLAIMER: So if you're thinking this is the same as [GUIDE] TWRP, ROOT and XPosed - Only J320FN ! you're right, but you're also wrong. The process is somewhat the same of course, but i did not followed that guide nor use any of his files, i'll explain a lot of things, introduce you to magisk.... And here we're talking of the J320F and J320F/DS , which is the variant I have. Yes FN stuff works on F and F/DS most of the time, i'm aware.
With that out of th way let's talk business, I'm running stock 5.1.1 on my Samsung Galaxy J3 2016 J320F. This guide is for Stock ROM, custom roms come pre-rooted or use their own Root addon like Lineage, in the other hand, Samsung's stock roms based on Android L and M are not compatible with the official Xposed Framework from Rovo89, it will bootloop the device, instead we have to use a modified Xposed made by Wanam, more on that later.
I'm going to split this guide in 3 parts, first we're gonna install the custom recovery TWRP via Odin, the recovery will enable us to flash zip files which will allows us to Root the device and finally install Xposed.
How to Install TWRP on the J3 J320FThe tool to flash firmwares files on Samsung phones running Android is called Odin, and in order for Odin to recognize your phone in Download Mode (more on that later) it also needs some drivers. You can download both things from the following links:
Odin 3.10 from MEGA*
<Mod Edit> 4shared link removed
PLEASE READ [*]
1. Both files are in .RAR5, so you need to use WinRAR 5 or above to be able open them.
2. They also are password protected (sorry about that, but i offer them on several sites already). Password is: Tecnoriales
TWRP 3.0.2 for J320F - is a *.tar file, leave it as is, i mean don't extract it.
Before you star please charge your battery to 100%.
1. Install the Samsung Drivers.
2. In your J320F go to Settings>About phone>Software Info and tap 7 times on the Build Number, you'll see a toast message about "Developers Options" being now enabled.
3. Head back to Settings and now youll see Developer Options, enter there turn the toggle for Disable OEM Unlock, you'll face your security challenge, whatever it is you have (pin, password, pattern...).
NOTE: From now on leave Disable OEM Unlock thicked (what i mean is, if you turn the toggle to his original state will enable OEM Unlock). otherwise when you reboot your phone it won't boot again showing you the Custom Binary blocked by FRP Block" error in red letter. This can only be fixed Flashing the stock rom on your J320F, although you might not lose your data you will lose TWRP, root and Xposed. So, BE CAREFUL!
4. Turn off your phone and enter Download Mode pressing Vol+- Home and Power. You'll see a warning in the screen, accept it pressing Vol+.
{
"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"
}
5. Plug your phone to the PC using your usb cable and give it some time for the driver to kick in if it is the very first time.
6. Run Odin as Admin. Check the COM Port is illuminated and you see Added in the log below.
7. Click the AP button and load the *.tar file of the TWRP.
8. Go to Options Tab and disable Auto-Reboot.
9. Press Start and wait Odin to say Pass in green. It's only a couple of seconds.
10. Unplug your phone from the PC and remove the battery and put it back. Now turn in on with the key combo: Vol+, Home and power.
Your J320F will boot straight to TWRP- Change the language from Russian to whatever you want and swipe to the right the slider in the bottom of the screen to enable the TWRP to modify the system. That's it.
How to ROOT the J3 J320F using SuperSu or MagiskGrab your rooting tool:
SuperSu - Good old SuperSu from Chainfire. Might hang from time to time and refuse to grant root access, kinda has bad temper.
or
Magisk + Magisk Manager APK. Newest and systemless root. Works like a charm, I used v16.0.
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy the *.zip file to the sdcard of your J320F
2. Boot into TWRP.
3. Go to Install and navigate to your sdcard to find and select the zip file.
4. Swipe to the right the slider control on the bottom of the screen to start the flashing process, which you can follow in the log.
5. Once it has finished touch on Reboot System and wait for the phone to boot. It might take a loot of time if you installed SuperSu.
You will have in your launcher the app of your root manager app. Test that root is working with root checker, Link2Sd, or whatever needs root access.
Note: If you rooted with Magisk and don't see Magisk Manager on your launcher, install the apk manually.
How to Install Xposed Framework on the J3 J320FAs I said at the beginning of this post, YOU CAN'T USE OFICIAL XPOSED on Samsungs stock roms (Android 5.x and 6.x) it will make your device loop on the boot process. This is due to the heavy modifications Samsung make to Android to turn it into his TouchWiz UI.
To install Xposed you need:
Xposed Framework by Wanam - The current (and probably final) version is 87.1, download the zip for ARM and SDK22. Optional: Also download Xposed Uninstaller zip in case you get a bootloop.
Xposed Installer App - Is an APK file attached to this thread, which by the way is the official Xposed Framework thread by Rovo89, don't used Xposed zips from there!
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy files to your sdcard. And install Xposed Installer.
2. Boot into TWRP, go to install and select the xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125 zip.
3. Swipe to the right the slider control on the bottom of the screen to start the flashing process and wait.
4. When it finishes select Reboot System. This will be a long boot, be patient.
After booting go to the Xposed Installer, or install it if you havent already, and see if Xposed is enabled. You should see the version and the samsung warning like in this pick
NOTE: DO NOT UPDATE XPOSED from the Xposed Installer app, it will flash official Xposed and you will get ****ed, i mean, a bootloop.
Xposed has tons, and tons, and tons of modules, most of them won't work on Samsung roms, again, due to all the changes Samsung made to Android in his stock roms. Always read carefully the info of any module before installing it, believe me they are state it when they wont work on Samsung roms. There's one module you should never even try to install:
It's called Gravity Box... The most powerful and famous module of all, and no, it wont work on your Samsung.
However, theres something called Wanam Xposed, made by the same dev from the modified Xposed we are using, it has some of the features you can find in GB.
All the above information is in this video i made. Video is in Spanish tough.
Sorry for my english, good luck and happy flashing.
can you make an English video please thx!
DeblaGaming said:
can you make an English video please thx!
Click to expand...
Click to collapse
Not happening.
DeblaGaming said:
can you make an English video please thx!
Click to expand...
Click to collapse
Seems pretty straight forward. A word of advice. When doing things like this for first time and if you don't know what to do rather follow text tutorials than videos. Easier to keep up...
Can twrp be updated with latest version or is this some custom twrp only for this model?
I haven't played a lot with flashing on samsungs so I'm doing my reading before. I have FN model. Is there some custom ROM that offers better experience or should I just root stock and get rid of bloatware and tweak it as I like with xposed?
the_bulk said:
Seems pretty straight forward. A word of advice. When doing things like this for first time and if you don't know what to do rather follow text tutorials than videos. Easier to keep up...
Can twrp be updated with latest version or is this some custom twrp only for this model?
I haven't played a lot with flashing on samsungs so I'm doing my reading before. I have FN model. Is there some custom ROM that offers better experience or should I just root stock and get rid of bloatware and tweak it as I like with xposed?
Click to expand...
Click to collapse
Theres no official TWRP for Speadtrum based 2016 J3s. There are newer versions for the J30F/FN i think, but atm i don't care/need it.
Since we don't have an Exynos or Qualcomm SoC, the custom rom scene doesn't look so good. Pretty much you have Lineage (MM & N), RR (N) and more recently DotOS (N), but they all suffer from pretty much the same problems give or take, in top of that most of the other roms are dead since the devs moved on to other phones, the ones I mentioned before don't really receive updates oftem. Right now im using stock with root and Xposed, is working fine, however im thinking about giving a second chance this rom: https://forum.xda-developers.com/galaxy-j3-2016/development/j2-pro-port-markus-rooted-t3657383 is stock MM, a port from the j210F wich i think is newer and somewhat better than this other j2 port: https://forum.xda-developers.com/galaxy-j3-2016/development/marshmallow-rom-j320f-t3623551
Can it flash newest SuperSu v2.82 flashable zip,through TWRP?
Odin Faild
Hi Guys!
I tried to flash the TWRP recovery on my J3 (2016) , but odin saids its faild could you help me with it please?
milewap said:
Can it flash newest SuperSu v2.82 flashable zip,through TWRP?
Click to expand...
Click to collapse
I flashed latest Magisk v18,with TWRP and yes TWRP vorks great tnx dev...for all :good:
Here's another one TWRP custom recovery,this one he has a bekap EFS....downloaded from 4pda ru site.All credits goes to them
SM-J320F-TWRP-F2FS.tar.md5
And here SM-J320FN-TWRP-F2FS.tar.md5 for FN but it does,on J320F i flashed today and works without problems.
Here it is PIT J320F if someone needs it...
Need help
mauriciognr said:
DISCLAIMER: So if you're thinking this is the same as [GUIDE] TWRP, ROOT and XPosed - Only J320FN ! you're right, but you're also wrong. The process is somewhat the same of course, but i did not followed that guide nor use any of his files, i'll explain a lot of things, introduce you to magisk.... And here we're talking of the J320F and J320F/DS , which is the variant I have. Yes FN stuff works on F and F/DS most of the time, i'm aware.
With that out of th way let's talk business, I'm running stock 5.1.1 on my Samsung Galaxy J3 2016 J320F. This guide is for Stock ROM, custom roms come pre-rooted or use their own Root addon like Lineage, in the other hand, Samsung's stock roms based on Android L and M are not compatible with the official Xposed Framework from Rovo89, it will bootloop the device, instead we have to use a modified Xposed made by Wanam, more on that later.
I'm going to split this guide in 3 parts, first we're gonna install the custom recovery TWRP via Odin, the recovery will enable us to flash zip files which will allows us to Root the device and finally install Xposed.
How to Install TWRP on the J3 J320FThe tool to flash firmwares files on Samsung phones running Android is called Odin, and in order for Odin to recognize your phone in Download Mode (more on that later) it also needs some drivers. You can download both things from the following links:
Odin 3.10 from MEGA*
<Mod Edit> 4shared link removed
PLEASE READ [*]
1. Both files are in .RAR5, so you need to use WinRAR 5 or above to be able open them.
2. They also are password protected (sorry about that, but i offer them on several sites already). Password is: Tecnoriales
TWRP 3.0.2 for J320F - is a *.tar file, leave it as is, i mean don't extract it.
Before you star please charge your battery to 100%.
1. Install the Samsung Drivers.
2. In your J320F go to Settings>About phone>Software Info and tap 7 times on the Build Number, you'll see a toast message about "Developers Options" being now enabled.
3. Head back to Settings and now youll see Developer Options, enter there turn the toggle for Disable OEM Unlock, you'll face your security challenge, whatever it is you have (pin, password, pattern...).
NOTE: From now on leave Disable OEM Unlock thicked (what i mean is, if you turn the toggle to his original state will enable OEM Unlock). otherwise when you reboot your phone it won't boot again showing you the Custom Binary blocked by FRP Block" error in red letter. This can only be fixed Flashing the stock rom on your J320F, although you might not lose your data you will lose TWRP, root and Xposed. So, BE CAREFUL!
4. Turn off your phone and enter Download Mode pressing Vol+- Home and Power. You'll see a warning in the screen, accept it pressing Vol+.
5. Plug your phone to the PC using your usb cable and give it some time for the driver to kick in if it is the very first time.
6. Run Odin as Admin. Check the COM Port is illuminated and you see Added in the log below.
7. Click the AP button and load the *.tar file of the TWRP.
8. Go to Options Tab and disable Auto-Reboot.
9. Press Start and wait Odin to say Pass in green. It's only a couple of seconds.
10. Unplug your phone from the PC and remove the battery and put it back. Now turn in on with the key combo: Vol+, Home and power.
Your J320F will boot straight to TWRP- Change the language from Russian to whatever you want and swipe to the right the slider in the bottom of the screen to enable the TWRP to modify the system. That's it.
How to ROOT the J3 J320F using SuperSu or MagiskGrab your rooting tool:
SuperSu - Good old SuperSu from Chainfire. Might hang from time to time and refuse to grant root access, kinda has bad temper.
or
Magisk + Magisk Manager APK. Newest and systemless root. Works like a charm, I used v16.0.
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy the *.zip file to the sdcard of your J320F
2. Boot into TWRP.
3. Go to Install and navigate to your sdcard to find and select the zip file.
4. Swipe to the right the slider control on the bottom of the screen to start the flashing process, which you can follow in the log.
5. Once it has finished touch on Reboot System and wait for the phone to boot. It might take a loot of time if you installed SuperSu.
You will have in your launcher the app of your root manager app. Test that root is working with root checker, Link2Sd, or whatever needs root access.
Note: If you rooted with Magisk and don't see Magisk Manager on your launcher, install the apk manually.
How to Install Xposed Framework on the J3 J320FAs I said at the beginning of this post, YOU CAN'T USE OFICIAL XPOSED on Samsungs stock roms (Android 5.x and 6.x) it will make your device loop on the boot process. This is due to the heavy modifications Samsung make to Android to turn it into his TouchWiz UI.
To install Xposed you need:
Xposed Framework by Wanam - The current (and probably final) version is 87.1, download the zip for ARM and SDK22. Optional: Also download Xposed Uninstaller zip in case you get a bootloop.
Xposed Installer App - Is an APK file attached to this thread, which by the way is the official Xposed Framework thread by Rovo89, don't used Xposed zips from there!
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy files to your sdcard. And install Xposed Installer.
2. Boot into TWRP, go to install and select the xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125 zip.
3. Swipe to the right the slider control on the bottom of the screen to start the flashing process and wait.
4. When it finishes select Reboot System. This will be a long boot, be patient.
After booting go to the Xposed Installer, or install it if you havent already, and see if Xposed is enabled. You should see the version and the samsung warning like in this pick
NOTE: DO NOT UPDATE XPOSED from the Xposed Installer app, it will flash official Xposed and you will get ****ed, i mean, a bootloop.
Xposed has tons, and tons, and tons of modules, most of them won't work on Samsung roms, again, due to all the changes Samsung made to Android in his stock roms. Always read carefully the info of any module before installing it, believe me they are state it when they wont work on Samsung roms. There's one module you should never even try to install:
It's called Gravity Box... The most powerful and famous module of all, and no, it wont work on your Samsung.
However, theres something called Wanam Xposed, made by the same dev from the modified Xposed we are using, it has some of the features you can find in GB.
All the above information is in this video i made. Video is in Spanish tough.
Sorry for my english, good luck and happy flashing.
Click to expand...
Click to collapse
Hey man youre the best guid i found on the internet
I have a j320f, stock rom, 5.1.1.OS and i rooted it twice with superus and magisk. I flashed em with twrp
At first the root checker said root is not installed correctly. Then i rooted it with kingo root and problem solved
I didnt install Xposed
But after some hours my phone restarted and kept bootlooping. I flashed the firmware... my phone worked again. Then again i rooted it but this time i made a backup.
I flashed magisk again (your exact version) and pressed root on kingo root again to make the root checke say the device is rooted
And the bootloop happened again
I wanna know that XposedFramework by wanam does prevent bootloop?
Or is there anything that can be done for preventing bootloop?
AminNadery said:
Hey man youre the best guid i found on the internet
I have a j320f, stock rom, 5.1.1.OS and i rooted it twice with superus and magisk. I flashed em with twrp
At first the root checker said root is not installed correctly. Then i rooted it with kingo root and problem solved
I didnt install Xposed
But after some hours my phone restarted and kept bootlooping. I flashed the firmware... my phone worked again. Then again i rooted it but this time i made a backup.
I flashed magisk again (your exact version) and pressed root on kingo root again to make the root checke say the device is rooted
And the bootloop happened again
I wanna know that XposedFramework by wanam does prevent bootloop?
Or is there anything that can be done for preventing bootloop?
Click to expand...
Click to collapse
You should use latest Magisk. If you install magisk you dont need anything else, if you dont see the magisk app after rebooting just go an download an install latest magisk manager from their thread. Stay away from kingo, use magisk, pay atention to what you are doing, youre using magisk and kingo at the same time, of course youll get a bootloop.
PD: Never quote OP.
Sorry for bothering again.
mauriciognr said:
You should use latest Magisk. If you install magisk you dont need anything else, if you dont see the magisk app after rebooting just go an download an install latest magisk manager from their thread. Stay away from kingo, use magisk, pay atention to what you are doing, youre using magisk and kingo at the same time, of course youll get a bootloop.
PD: Never quote OP.
Click to expand...
Click to collapse
Hey man thanks for the help...i did as you told and i installed magisk v19 using the TWRP.the magisk manager was installed after the reboot BUT the root checker said that the root was not installed properly. In fact the prompt and grant pop up never showed up. I had this problem with superSU too and that was the reason i used the kingo root. And only after that i could see the phone is rooted in root checker...i didnt installed kingo root this time. Thanks for the warning.
But what can i do? My apps does not have root permission.
I tried installing different versions of magisk. The latest v19 and the one u used v16.0. It didnt helped.
The app was not hibernated i checked but it was never in the running apps in application manager
SuperSU had the same problem.
What should i do?
Any solutions?
Youre the best. Thanks
AminNadery said:
Hey man thanks for the help...i did as you told and i installed magisk v19 using the TWRP.the magisk manager was installed after the reboot BUT the root checker said that the root was not installed properly. In fact the prompt and grant pop up never showed up. I had this problem with superSU too and that was the reason i used the kingo root. And only after that i could see the phone is rooted in root checker...i didnt installed kingo root this time. Thanks for the warning.
But what can i do? My apps does not have root permission.
I tried installing different versions of magisk. The latest v19 and the one u used v16.0. It didnt helped.
The app was not hibernated i checked but it was never in the running apps in application manager
SuperSU had the same problem.
What should i do?
Any solutions?
Youre the best. Thanks
Click to expand...
Click to collapse
First, perform a factory reset and flash your stock ROM (with odin), afterwards twrp and then magisk. Whatever problem you might have it will go away after a clean install of your rom. Use latest magisk.
Odin
Can I do this without computer???
So today i decided to update magisk to its latest versio, it all whet well,i did within android. later on in the day i decided to reboot myphone, and to my surprise it got stuck o thelgv30 thinq scree, after decide 10m was enough i rebooted and the it was stuck in bootloop, so i decided to restore my nanddroid , after it was done i hit reboot to system, and now it will only noot to fastootmode,, its as if there is nothing flashed to boot or system. any help will greatly appreciated.
EDIT: VERY OLD POST; WE CAN NOW USE NEWER MAGISK
____________
By "latest" you mean Magisk beta? You can only use stable 16.0 Magisk. Stated in the bootloader unlock/TWRP/root instructions that beta Magisk will mess up your phone.
Download Magisk or SuperSu. Magisk 16 (Use stable Magisk -- which right now is 16.0! Magisk "beta" will mess up your phone.)
Click to expand...
Click to collapse
You may need to Master Reset (wipe everything), reflash TWRP, etc. Good luck.
ChazzMatt said:
By "latest" you mean beta Magisk. You can only use stable 16.0 Magisk. Stated in the bootloader unlock instructions that beta Magisk will mess up your phone.
You may need to Master Reset (wipe everything), reflash TWRP, etc. Good luck.
Click to expand...
Click to collapse
yea that what i did fml. what do i do reflash the oreo kdz?
siulmagic said:
yea that what i did fml. what do i do reflash the oreo kdz?
Click to expand...
Click to collapse
Probably. First Master Reset to clear everything. SEE if that works. Post 101 of the Frankenstein thread.
If that doesn't work, then go into download mode manually, then open dev patched LGUP and reflash Oreo KDZ.
Then use ADB to reinstall TWRP, and go from there. Your bootloader will already be unlocked so you'll continue to get the "scary" bootloader unlock warning. But you'll otherwise be following the instruction of the bootloader unlock thread, except for the bootloader unlock part.
ChazzMatt said:
Probably. First Master Reset to clear everything. SEE if that works. Post 101 of the Frankenstein thread.
If that doesn't work, then go into download mode manually, then open dev patched LGUP and reflash Oreo KDZ.
Then use ADB to reinstall TWRP, and go from there. Your bootloader will already be unlocked so you'll continue to get the "scary" bootloader unlock warning. But you'll otherwise be following the instruction of the bootloader unlock thread, except for the bootloader unlock part.
Click to expand...
Click to collapse
Isint the master reset disabled with twrp? master reset only boots twrp, when you have twrp installed, i will try to wipe with lgup.
Thanks for the help man, phone is backup and running.
siulmagic said:
Thanks for the help man, phone is backup and running.
Click to expand...
Click to collapse
I've tried using LgUP to try and get me back onto an OS, but it will not boot into the OS, only into fastboot. Anything I can do?
If you were using Trebel TWRP you have to use normal TWRP and restore the backup GPT in order for a stock nandroid to work or a stock based clean flash...
jmej88 said:
I've tried using LgUP to try and get me back onto an OS, but it will not boot into the OS, only into fastboot. Anything I can do?
Click to expand...
Click to collapse
To fix stuck in fastboot or download mode
Connect phone in download mode
go in patched LGUP flash h93320f_00_open_ca_op_0612.kdz
With partition dl option
(not working go in device manager select modem
Then lge mobile usb modem right click disable driver try again)
help me:,(
ChazzMatt said:
Probably. First Master Reset to clear everything. SEE if that works. Post 101 of the Frankenstein thread.
If that doesn't work, then go into download mode manually, then open dev patched LGUP and reflash Oreo KDZ.
Then use ADB to reinstall TWRP, and go from there. Your bootloader will already be unlocked so you'll continue to get the "scary" bootloader unlock warning. But you'll otherwise be following the instruction of the bootloader unlock thread, except for the bootloader unlock part.
Click to expand...
Click to collapse
I had the same problem but I tried many different versions but it was still stuck in fastboot i'm so scared help me pls
Im stuck in fastboot mode too after chip reset. Tried kdz us998 10 with no luck.
Anybody have other suggestions?
....edit.
Fixed flashing Canadian kdz.
mines wont go into download mode just keeps going to fastbootloader
r3m3dy478 said:
mines wont go into download mode just keeps going to fastbootloader
Click to expand...
Click to collapse
Flash twrp and flash rom.
Sent from my VS996 using Tapatalk
r3m3dy478 said:
mines wont go into download mode just keeps going to fastbootloader
Click to expand...
Click to collapse
Download kdz flashable zip then extract it. Flash the system.img and boot.img file via fastboot
This just happened to me today. It was either from the newest Magisk (v22) or from the newest YouTube Vanced. Those were the only things that changed recently on my phone. Rebooted today and it will only go to Fastboot mode and that's it.
Master Reset will get me into TWRP, but I think my USB port on the phone is damaged, it will charge but neither my Windows nor Linux PCs will recognize that it's plugged in. So it's like only USB charging works but not USB data. So I think I'm screwed, idk if it's fixable. Sad day.
Am also stack here qhile trying to unlock my bootloader using @bilong9 thread on my v300l .please help
This also happened to me while trying to update to Magisk 22. First I had an error with Magisk in a restart cycle, then when I tried to update manually from the APK I got stuck in a fastboot loop with no ADB access. I was able to boot to TWRP from fastboot on my PC, then re-flash the Pie image. My settings were all lost, but I did get my phone back at least. BEWARE of Magisk 22, or at least until it's fixed for the V30!
edit: I found that I COULD install Magisk 22.0.zip while following these instructions for restoring my phone:
LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions)
(WTF...!) LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions) WTF...! LG V30,V30+,V30S (MOST VARIANTS) BOOTLOADER UNLOCK, TWRP, ROOT INSTRUCTIONS HERE >>>CLICK HERE TO POST #193
forum.xda-developers.com
after a few extra prompts from the Magisk app, v22 now works.
I've had no issues using Magisk v22 with an LOS 17.1 (Android 10) based ROM. It could just be that there's a problem with it on either LG stock or Pie ROMs.
UPDATE
* Variant: US998 US Cellular/Carrier Unlocked
* ROM: Rooted Stock Pie (US99830b)
* Magisk: v21.4
So it seems the issue is not that it "soft bricks", but something about the new installation process of Magisk v22 goes wrong with the /boot partition, causing the phone to only be able to boot into Fastboot mode.
After getting my phone fully recovered and restored from the last failed attempt (and making a new TWRP backup), I attempted the v22 update again. First Magisk attempted to download and install the new v22 app, and then a popup notification said "additional setup is required for your device, press OK to reboot". So I hit okay, and that's when once again I got stuck in Fastboot with no other options.
If you have a TWRP/nandroid backup, you can easily fix this by performing the Master Reset process in order to boot into TWRP, and then just Restoring the /boot partition from your TWRP backup. This will get you back to Magisk v21.4 where you were before, which is where I'm currently at.
At this time, unless Magisk releases a TWRP-flashable .zip for v22, or unless there's a way to update to v22 via Fastboot, it doesn't look like updating to v22 will be possible, at least for the Stock Pie ROM.
I've seen on both reddit and XDA that several people are saying they updated to v22 without issue, but it's unclear if they were on Stock or Custom ROM. My guess would be that Custom ROMs are probably working fine and it's the Stock ROM that's having the issue.
At this time, unless Magisk releases a TWRP-flashable .zip for v22, or unless there's a way to update to v22 via Fastboot, it doesn't look like updating to v22 will be possible, at least for the Stock Pie ROM.
Click to expand...
Click to collapse
I simply renamed the available .apk to .zip and it flashed in TWRP.
edit: the ROM I'm using is from this thread, which says it is 99% stock, whatever that means.
Hi,
I have a H932, unlocked bootloader and twrp installed twice as advised in thisthread.
I've tried liquid, lineage and Resurrection and all of them except RR bootloop. I'm assuming because it is a GSI? I'm flashing the H932 versions of all these roms.
I must have missed something so if anyone has any suggestions?
I wonder if it's because I'm using TWRP 3.2.3-7 instead of 3.3.0 but I couldnt flash the No_Verity files using the latest version so had to drop back to 3.2.3-7. If this is the case, how do I flash those files to ensure I don't get encrypted. What happens if I don't flash the files and end up encrypted?
I am clutching at straws here, so any help would be greatly appreciated.
My lineage is tested on H932, and works ?
Whats your flashing process exactly?
Wipe system, data, cache and dalvik cache (after you took a backup)
and then flash
ROM, Gapps, (optionally) Magisk
For encryption: all AOSP roms have /data set to encryptable, not forceencrypt, so except you (try to) enable encryption in the settings, it wont do anything (and even that is broken to my knowledge)
ddevey said:
I wonder if it's because I'm using TWRP 3.2.3-7 instead of 3.3.0 but I couldnt flash the No_Verity files using the latest version so had to drop back to 3.2.3-7. If this is the case, how do I flash those files to ensure I don't get encrypted. What happens if I don't flash the files and end up encrypted?
I am clutching at straws here, so any help would be greatly appreciated.
Click to expand...
Click to collapse
You are using the right TWRP.
SGCMarkus said:
My lineage is tested on H932, and works ?
Whats your flashing process exactly?
Wipe system, data, cache and dalvik cache (after you took a backup)
and then flash
ROM, Gapps, (optionally) Magisk
For encryption: all AOSP roms have /data set to encryptable, not forceencrypt, so except you (try to) enable encryption in the settings, it wont do anything (and even that is broken to my knowledge)
Click to expand...
Click to collapse
Hey, thanks for the response. I'm just reading through the [ROOT] H932 - lafploit 1.5 up to v20k thread again and realised I haven't flashed a stock Oreo TWRP flashable rom before flashing lineage. Do I need to do this?
I have factory reset in TWRP and wiped system, data, cache / dalvik and then flashed the rom, gapps, magisk and No_Verity 6.
If not flashing an Oreo rom is the issue, can you recommend one? I've got a 3 gig H932_20o.zip from the root thread, but really I'm just interested in the custom roms.
ddevey said:
Haven't flashed a stock Oreo TWRP flashable rom before flashing lineage. Do I need to do this?
If not flashing an Oreo rom is the issue, can you recommend one? I've got a 3 gig H932_20o.zip from the root thread, but really I'm just interested in the custom roms.
Click to expand...
Click to collapse
That's old. Flash the H932 20S
Yeah you shouldn't go from Nougat H932 firmware to Pie custom ROMs.
People have fingerprint sensor issues, etc. if they don't have at least Oreo firmware when flashing custom ROMs
https://forum.xda-developers.com/lg-v30/development/stock-t-mobile-lg-v30-stock-collection-t3909237
ChazzMatt said:
That's old. Flash the H932 20S
Yeah you shouldn't go from Nougat H932 firmware to Pie custom ROMs.
People have fingerprint sensor issues, etc. if they don't have at least Oreo firmware when flashing custom ROMs
https://forum.xda-developers.com/lg-v30/development/stock-t-mobile-lg-v30-stock-collection-t3909237
Click to expand...
Click to collapse
Oh my gosh! Sweet freedom thanks guys. My heart's been in my mouth all day with this process........... thanks very much for the help.
ddevey said:
Oh my gosh! Sweet freedom thanks guys. My heart's been in my mouth all day with this process........... thanks very much for the help.
Click to expand...
Click to collapse
Well, I hope that solves your issues. But yeah, you are using correct TWRP and yeah you do need newer stock firmware than Nougat before flashing custom ROMs.
Sent via open market LG US998 V30/V30+
Thanks again, I'm rocking Lineage from February and everything seems to be working great.
I'm just wondering if someone can actually clarify what I've done by following the H932 TWRP and Root guide. I've been flashing roms since the days of the original XDA and the HTC HD2, but this seems like one of the wierder devices and I'd really like to understand what's going on.
So I have 2 versions of TWRP. One on LAF and one on the bootloader?
What is LAF?
In my haste I flashed the old H932_20o which works for now and has made the february Pie roms work, but I would like to flash the H932_20r from here, as from what I understand this is necessary to ensure less issues with the April pie roms. If I flash the full version of this, will it overwrite LAF?
Do I even need to retain TWRP on LAF when it's already on the bootloader? Do I need to boot back into FWUL and run the script from there to get TWRP back onto LAF if the 20o rom overwrote it? I'd try and find out myself, but it seems the only way to get into the TWRP on the LAF is to hold down and go through that wipe process with the white screens, which i'd rather avoid.
No one seems to talk about vendor images being flashed to match the latest security updates. Is this becuase LG are so slow in releasing vendor updates?
Apologies for all the questions. I appreciate that these have probably been answered already, but they are spread across multiple vendors of hundereds of pages and I'm having trouble piecing all this information together.
ddevey said:
Thanks again, I'm rocking Lineage from February and everything seems to be working great.
I'm just wondering if someone can actually clarify what I've done by following the H932 TWRP and Root guide. I've been flashing roms since the days of the original XDA and the HTC HD2, but this seems like one of the wierder devices and I'd really like to understand what's going on.
So I have 2 versions of TWRP. One on LAF and one on the bootloader?
What is LAF?
In my haste I flashed the old H932_20o which works for now and has made the february Pie roms work, but I would like to flash the H932_20r from here, as from what I understand this is necessary to ensure less issues with the April pie roms. If I flash the full version of this, will it overwrite LAF?
Do I even need to retain TWRP on LAF when it's already on the bootloader? Do I need to boot back into FWUL and run the script from there to get TWRP back onto LAF if the 20o rom overwrote it? I'd try and find out myself, but it seems the only way to get into the TWRP on the LAF is to hold down and go through that wipe process with the white screens, which i'd rather avoid.
No one seems to talk about vendor images being flashed to match the latest security updates. Is this becuase LG are so slow in releasing vendor updates?
Apologies for all the questions. I appreciate that these have probably been answered already, but they are spread across multiple vendors of hundereds of pages and I'm having trouble piecing all this information together.
Click to expand...
Click to collapse
Why 20r? Why not newer 20s?
LAF TWRP is redundant and you no longer have LGUP Download mode, since you wiped it out from flashing 2nd copy of TWRP over your LAF partition.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Why 20r? Why not newer 20s?
LAF TWRP is redundant and you no longer have LGUP Download mode, since you wiped it out from flashing 2nd copy of TWRP over your LAF partition.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
20s says it hasn't been tested on the H932.
ddevey said:
20s says it hasn't been tested on the H932.
Click to expand...
Click to collapse
coming...
weakNPCdotCom said:
Just got my hands on the 20s KDZ. Ill have packages ready this weekend
Click to expand...
Click to collapse
Yeah you can flash H932 20r for now.
https://forum.xda-developers.com/lg-v30/development/stock-t-mobile-lg-v30-stock-collection-t3909237
So if I flash the full stock, it'll update the LAF, recovery, bootloader and modem firmware. Which is presumably what I want if I want to be on the most up to date vendor, modem etc.
But if it overwrites LAF and the bootloader with stock presumably somehow I've got to get TWRP back onto it? Can I just flash a TWRP image to the bootloader straight after the stock flash or do I need to go back to FWUP to do this?
I think I'll wait for the 20s version, but it'd be useful to fully understand what's going on so I don't brick it.
If I do brick it, can I just go back to LG UP and flash the 10d version and follow the guide again?
OK, should read properly:
None of these Zips flash the Recovery partition.
Besides StockLAF, these Zips DO NOT flash the LAF partition.
ddevey said:
So if I flash the full stock, it'll update the LAF, recovery, bootloader and modem firmware. Which is presumably what I want if I want to be on the most up to date vendor, modem etc.
But if it overwrites LAF and the bootloader with stock presumably somehow I've got to get TWRP back onto it? Can I just flash a TWRP image to the bootloader straight after the stock flash or do I need to go back to FWUP to do this?
I think I'll wait for the 20s version, but it'd be useful to fully understand what's going on so I don't brick it.
If I do brick it, can I just go back to LG UP and flash the 10d version and follow the guide again?
Click to expand...
Click to collapse
This is TWRP-flashable zip. You will not lose TWRP custom recovery. Why would you brick it?
You need to read the instructions, please.
IF you flash the LAF file, you will regain Download mode and "lose" the redundant copy of TWRP you also flashed over your LAF partition.
"Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode"
"None of these Zips flash the Recovery partition."
You may have to flash the no encryption and no root check files again, besides Magisk.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
You need to read the instructions, please.
Click to expand...
Click to collapse
I think I'm misunderstanding where TWRP is actually located on the device. I am reading, just failing to understand.
ChazzMatt said:
IF you flash the LAF file, you will regain Download mode and "lose" the redundant copy of TWRP you also flashed over your LAF partition.
Click to expand...
Click to collapse
So basically never flash a LAF zip or a recovery partition and I'll never loose TWRP. Stay away from unmodified KDZ's.
ddevey said:
I think I'm misunderstanding where TWRP is actually located on the device. I am reading, just failing to understand.
So basically never flash a LAF zip or a recovery partition and I'll never loose TWRP. Stay away from unmodified KDZ's.
Click to expand...
Click to collapse
You have it in two places right now. In your recovery partition (normal), as it's TWRP custom recovery that replaces the useless stock recovery.
And due to the way the H932 root Instructions are written you also flashed it over your LAF partition, where your Download mode WAS. Right now, you no longer have LGUP Download mode if you wanted to use that, and instead you have TWO copies of TWRP.
In the WTF INSTRUCTIONS, we never do that. However, the dev who rooted the H932 (and wrote those Instructions) feels there's an advantage to having TWO copies of TWRP and giving up LGUP Download mode. Been discussed in depth elsewhere and we've agreed to disagree.
When you flash H932 20R TWRP flashable zip, you can choose to keep both copies of TWRP or you can choose to restore your Download mode and have the normal recovery partition copy of TWRP. Your choice.
Sent via open market LG US998 V30/V30+
---------- Post added at 02:23 AM ---------- Previous post was at 02:11 AM ----------
ddevey said:
So basically never flash a LAF zip or a recovery partition and I'll never loose TWRP. Stay away from unmodified KDZ's.
Click to expand...
Click to collapse
Right now you couldn't flash a KDZ if you wanted to, as you no longer have Download mode. Instead you have redundant 2nd copy of TWRP where LGUP Download mode used to live.
All you can install right now is TWRP- flashable zips or ROMs.
Thank you, that's super helpful. I really appreciate your patience.
So just one last question and I think I'm clear........ I'll avoid getting into a debate about the merits of 2 TWRP's vs Download mode.........
If I restore LAF and have a download mode at any point I can flash the 10d firmware and start over.
The flip side, is that I can then only get into TWRP by holding down + power - hold and release power and going through the "factory reset" process to access the recovery, or getting an app that boots directly into TWRP. But the assumption is that the rom is bootable for that to work.
Seems strange that it makes you do a factory rese to the device to access the recovery.
Basically, just don't flash anything over the recovery.
ddevey said:
Thank you, that's super helpful. I really appreciate your patience.
So just one last question and I think I'm clear........ I'll avoid getting into a debate about the merits of 2 TWRP's vs Download mode.........
If I restore LAF and have a download mode at any point I can flash the 10d firmware and start over.
The flip side, is that I can then only get into TWRP by holding down + power - hold and release power and going through the "factory reset" process to access the recovery, or getting an app that boots directly into TWRP. But the assumption is that the rom is bootable for that to work.
Seems strange that it makes you do a factory rese to the device to access the recovery.
Basically, just don't flash anything over the recovery.
Click to expand...
Click to collapse
I never get into TWRP that way. What you are describing is the hardware button dance, which is only for emergencies.
To boot to TWRP initially (first time after installation) you simply use fastboot boot recovery command. You're already connected to the computer.
After that your use the Reboot Recovery app, as STONGLY suggested in the WTF INSTRUCTIONS. Put shortcut on your main screen.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
I never get into TWRP that way. What you are describing is the hardware button dance, which is only for emergencies.
To boot to TWRP initially (first time after installation) you simply use fastboot boot recovery command. You're already connected to the computer.
After that your use the Reboot Recovery app, as STONGLY suggested in the WTF INSTRUCTIONS. Put shortcut on your main screen.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
See screenshot.
{
"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"
}
Here's the relevant section of TWRP Instructions from WTF, which also works for H932 (the TWRP installation part is universal)
_________
TLDR:
* flash twrp: fastboot flash TWRP.img (TWRP-3.2.3-7-default.img re-named as just "TWRP.img")
* boot twrp: fastboot boot TWRP.img (TWRP-3.2.3-7-default.img re-named as just "TWRP.img")
* swipe to allow modifications (do NOT leave read-only, TWRP NEEDS to be able to make changes to your system.)
* select WIPE, then also FORMAT DATA, then type yes
* wipe cache, dalvik, data
* flash magisk 18.0.
* flash encryption disabler
* flash root disabler
* reboot
STRONG SUGGESTION: After successfully doing all this, when you finally boot back to LG Oreo, install THIS app to easily facilitate rebooting to TWRP recovery in the future: Recovery Reboot
Also, please make another TWRP backup.
ddevey said:
If I restore LAF and have a download mode at any point I can flash the 10d firmware and start over.
Click to expand...
Click to collapse
Yes. Whereas without Download mode, you could NOT flash 10d KDZ and start over. Now you are beginning to understand why I (personally, my opinion) do not advocate giving up Download mode...
ChazzMatt said:
I never get into TWRP that way. What you are describing is the hardware button dance, which is only for emergencies.
To boot to TWRP initially (first time after installation) you simply use fastboot boot recovery command. You're already connected to the computer.
After that your use the Reboot Recovery app, as STONGLY suggested in the WTF INSTRUCTIONS. Put shortcut on your main screen.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
If it's H932, there's no way you can access twrp via fastboot. Fastboot just fancy bootloader (un)locker there. Is that all about twrp on laf Vs. twrp on recovery? I know, we can boot up twrp via device reset combination, but then how to access laf's twrp? Does vol up + power works? Let me assume that twrp only managed to handle "customization things" and DL mode laf for "lastest hope". If one twrp can't handle some "recovery" task, so two trwp(s) won't get things better. But download mode certainly does.
Hi,
I tried to update my P6 using the magisk OTA update method:
-Unistall / Restore image
-Install OTA, no reboot
-Install magisk on inactive slot
-Reboot
My phone was on the SQ3A.220705.001.B2 update, few months old.
When I rebooted, I was prompted with the "device corrupted" message. I pressed the power key to continue, and was stuck at the Google logo boot loop.
I forced turned off the phone (hold power + vol up a few sec), and the phone rebooted, no corruption message to my surprise, and booted correctly. However, my system did not update (still on SQ3A.220705.001.B2).
I'm a rookie on device rooting, but my understanding is that my inactive slot (partition b) as the update installed but is corrupted and goes in boot loop, while partition a is not updated but not corrupted either.
The thing is, I only did "install on inactive slot", so magisk was uninstalled on partition a, and rebooting made me lost root on that partition.
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
SleinBuyt said:
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
Click to expand...
Click to collapse
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
SleinBuyt said:
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
Click to expand...
Click to collapse
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
m_pastuszek said:
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
Click to expand...
Click to collapse
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Strephon Alkhalikoi said:
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Click to expand...
Click to collapse
I agree on this side, but actually editing script that makes something similar comes down to the same thing
That was the same case for me.
After latest OTA update, no matter how many time I tried to flash full factory image via fastboot, stil showing device corrupted.
A couple of things everyone having this issue should be aware of.
Currently, "Flash to Inactive Slot" breaks verification/dm-verity on the Pixel 6/7, and I believe that's responsible for the "Device corrupted" error. The Magisk devs are aware but don't have a fix yet. I haven't been able to test because there have been no OTAs since I disabled those myself (which PixelFlasher can do for you), but I believe disabling them should prevent that problem during OTAs, but be advised I think doing so requires wiping /data when you do it.
Also, if you're still getting "device corrupted" even after reflashing stock, first watch for any errors during flashing in PixelFlasher (I may have a fix for anyone that has USB issues on Windows devices, but it involves the registry so it makes some people nervous), but if it isn't working then try Google's Android Flash Tool by finding your device and desired firmware here and clicking Flash. You'll need to be using Chrome. That's never failed for me. Once you have it up and running again *then* use PixelFlasher to patch and flash the boot image.
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Jaitsu said:
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Click to expand...
Click to collapse
To root the Pixel 6 on QPR2 Beta 1 you can patch the Pixel 7 boot image and then flash that on the Pixel 6.
Compression method of ramdisk in Pixel 6 boot image is incorrect · Issue #6441 · topjohnwu/Magisk
After switching to the beta version can't patch boot img and succesfully get root, with the stable version works. Device: Pixel 6a Android version: Android 13 QPR2 Beta 1 (T2B1.221118.006) Magisk v...
github.com
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
SleinBuyt said:
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
Click to expand...
Click to collapse
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Lughnasadh said:
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Click to expand...
Click to collapse
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
SleinBuyt said:
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
Click to expand...
Click to collapse
It's important if you don't want to brick your device. Did you read the link I gave you?
Lughnasadh said:
It's important if you don't want to brick your device. Did you read the link I gave you?
Click to expand...
Click to collapse
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
SleinBuyt said:
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
Click to expand...
Click to collapse
fastboot flash bootloader --slot=all <A13 bootloader image>
My situation is a bit bizarre. I'm on beta and recently got an update notification that was 190mb. I went to magisk to restore images and magisk says stock backup does not exist. From there and went ahead and use my PC to flash my stock boot image and rebooted. Once an Android it's still says the same thing but when I go back to the update it says installation problem Even though I am on stock. That's where I'm at right now. Haven't messed with it since just rolled with no root and stock boot image.
{
"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"
}
Lughnasadh said:
fastboot flash bootloader --slot=all <A13 bootloader image>
Click to expand...
Click to collapse
And it's done ! Thanks for potentially saving my phone later !