Database Develop

installing Magisk on Xiaomi A2 fails

First I unlocked the boot loader, although I doubt that’s needed for installing Magisk:
A2/Android (Oreo 8.1): Enabled developer options, enabled unlocking of boot loader, enabled debugging via USB.
PC/Linux: $ adb reboot bootloader
A2 boots into boot loader.
PC/Linux: $ fastboot oem unlock
Then I tried installing Magisk:
A2/Android: Re-enabled developer options, enabled debugging via USB, disabled automatic system updates (just in case, for later).
PC/Linux: $ adb reboot recovery
A2/Android: On the dialog asking for permission to allow USB debugging, selected to always allow from this computer and hit OK.
A2 displays screen with lying robot, saying No command. I held power, pressed volume-up once, released power.
A2 boots into recovery.
A2/Recovery: Selected Apply update from ADB.
PC/Linux:
$ adb sideload Magisk-v16.0.zip
Total xfer: 1.01x
A2/Recovery: Error message failed to verify whole-file signature
PC/Linux: Checked the zip file. It can be unzipped just fine, so it’s OK.
What else can I try?
PS: I do have detailed screen shots of the critical steps, but I don’t find an option to upload them to the forum.

You can't sideload the Magisk zip on a stock recovery. If you don't have a custom recovery installed you'll have to patch the boot image first with the Manager and then flash the patched image manually with fastboot. Check the installation instructions in the release thread.

Didgeridoohan said:
You can't sideload the Magisk zip on a stock recovery.
Click to expand...
Click to collapse
Thanks!
If you don't have a custom recovery installed you'll have to patch the boot image first with the Manager and then flash the patched image manually with fastboot. Check the installation instructions in the release thread.
Click to expand...
Click to collapse
Tried that, but did something extremely stupid in the process, knowing full on that this could cause an issue (I assumed things are easy to fix in case something goes wrong):
I did not run any system updates, leaving the Android 8.1 ROM at V9.6.5.0. (no problem so far)
I downloaded V9.6.10.0 of the ROM, and had Magisk patch the included boot.img to create patched_boot.img (still no problem)
I flashed patched_boot.img onto my A2. Now the device did not boot anymore. It hung at the loader animation showing a horizontal bar with varying colors.
To get the A2 to boot again, I obtained V9.6.9.0 of the ROM, I flashed the included boot.img, and I cleared the cache. Unfortunately, while the device boots into Android now, I cannot enable WLAN. It simply doesn’t work. Again, no surprise: V9.6.9.0 ≠ V9.6.5.0
Not being able to find the V9.6.5.0 ROM, I got the idea to update the half broken A2 to the latest ROM, i.e. V9.6.10.0. But how, without WLAN? Well, I found out that it is possible to use the WLAN connection of another Android device via Bluetooth. This is what I used, and I had to be very patient – it’s dog slow. Anyhow, I waited, and the installer started to do its job. The download succeeded, but the installation failed.
Phew, for now I’m out of options, and I’ve a non functioning device.
In another thread on the XDA Forums, I did find an unofficial dump of V9.6.5.0. But 1. I’m hesitant to install from unofficial dumps, and 2. the dump does not include a boot.img. Instead it includes one big payload.bin. Don’t know what to make out of that.
The alternative could be to install either V9.6.10.O or V9.6.9.O manually, possibly by flashing each partition image individually from fastboot. I don’t know, however, if that is a great idea.
PS: Sorry about the confusion with all those numbers.

Oh man... Flashing an update manually (each partition should work fine) is probably a good idea at this point.

Didgeridoohan said:
Oh man... Flashing an update manually (each partition should work fine) is probably a good idea at this point.
Click to expand...
Click to collapse
Went ahead with that. In fact, included in the full ROM archive are scripts for doing the update, sorted by an increasing number of steps performed:
flash_all_except_data.sh
flash_all.sh
flash_all_lock.sh
flash_all_lock_crc.sh
The last one also flashes CRC check sums into crclist and sparsecrclist. Included is a script to generate these check sums form the image files: flash_gen_crc_list.py
Here’s how I got back to a system that boots up fine:
PC/Linux: $ tar xfz jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz
PC/Linux: $ cd jasmine_global_images_V9.6.10.0.ODIMIFE_8.1
PC/Linux: $ fastboot flashing unlock
(reboot)
PC/Linux: $ fastboot flashing unlock_critical
(possibly reboot again)
PC/Linux: $ ./flash_all_lock_crc.sh
(went through smoothly, flashing CRC possibly not necessary)
Following this success, I did another attempt at installing Magisk:
PC/Linux: $ cp ../patched_boot.img images/boot.img
(created with Magisk Manager from the V9.6.10.0 boot.img)
PC/Linux: $ python2.7 flash_gen_crc_list.py
(thought it’s a good idea, but doesn’t help – see below)
PC/Linux: $ fastboot flashing unlock
(reboot)
PC/Linux: $ fastboot flashing unlock_critical
(possibly reboot again)
PC/Linux: $ ./flash_all_lock_crc.sh
(went through smoothly, flashing CRC possibly not necessary)
Unfortunately, upon reboot I get:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
Eventually the device doesn’t show the message anymore, instead hanging permanently at a androidone logo.
Not locking the boot loader after flashing solves the issue, but: For security reasons, I don’t want to use a device with an unlocked boot loader!
Any idea?

Uh-oh! Now it seems like I eclipsed my previous stupidity.
In the Android developer settings, I disabled OEM unlocking. Then I rebooted the device, locked the boot loader: fastboot oem lock This was still possible.
As result, I get the aforementioned error message:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
But now I cannot unlock the device anymore. fastboot oem unlock gives: FAILED (remote: Flashing Unlock is not allowed)
Bricked for good, right? :crying:

Oh... I saw your first message about getting things working (post #5), but I didn't have time to answer (work, work, work).
Now I wished I would have had the time, since I would have posted that you should never lock your bootloader on a modded device. The risk of something going wrong and not being able to unlock the bootloader again is too great...
If you're lucky there's still some kind of hack available that you can use, but you'd have to take that in your device's forum, where they know the device best.
That sucks... I hope you get things sorted. Good luck.

Didgeridoohan said:
Now I wished I would have had the time, […]
Click to expand...
Click to collapse
Don’t worry. I like to take systems to their limit.
[…] since I would have posted that you should never lock your bootloader on a modded device.
Click to expand...
Click to collapse
For security reasons, I don’t like the idea of leaving the boot loader open. While I understand that – due to encryption – it’s not possible to access my data, I assume it would be feasible to modify boot.img to install a rootkit in a few minutes. Just the thought of this being possible makes me uncomfortable and not trust the device for productivity use.
I wonder if I would also get the your device is corrupt message with Lineage installed.
If you're lucky there's still some kind of hack available
Click to expand...
Click to collapse
Yes, I’m betting on that, or perhaps the Xiaomi Mi Flash Tool can be used. (looking for an official download location)

feklee said:
I wonder if I would also get the your device is corrupt message with Lineage installed.
Click to expand...
Click to collapse
Did you preserve dm-verity when you patched the boot image? That sounds like dm-verity complaining...

Didgeridoohan said:
Did you preserve dm-verity when you patched the boot image? That sounds like dm-verity complaining...
Click to expand...
Click to collapse
No:
I’m almost certain that I did not enable dm-verity.
The device is corrupt message appears right after the reboot following ./flash_all_lock.sh or ./flash_all_lock_crc.sh, i.e. without any setup by Magisk Manager, and dm-verity is disabled by default.
BTW I got around to trying Xiaomi Mi Flash Tool, but it’s useless: It seems to be simply an ugly GUI for the fastboot commands. It cannot flash a device in locked state. In the end I was able to revive the device by opening it and using the test point method. Phew, gotta be more careful the next time…

Mi 8 soft brick

Hi guys
Sorry for my bad English
My device was running Android 10
miui 11
After I accidentally used an application to raise the screen frequency to 84Hz
The devics did a reboot and then stopped on the fastboot logo
I tried to enter recovery mode but was back to fastboot mode
I tried to flash twrp via adb and fastboot but the method did not work and the device returned to fastboot mode
Finally I downloaded the ROM file global Version Android 9
miui 11 and when i flashed the system via "xiaomi flash tool " the operation was successful until it reached the end of the process it showed me an error and the flash failed
I restarted the process and noticed that the flashing process gives me the error when the download arrives at "flashing boot"
I searched a lot for the version of Android 10 miui 11 but I did not find
What is the problem!
Can anyone explain what the problem is?
Thank you very much
Edit : solved With the help of my friend and brother @tsongming thanks bro

You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2

tsongming said:
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
Click to expand...
Click to collapse
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due

ahmadbasher said:
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
Click to expand...
Click to collapse
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.

tsongming said:
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
Click to expand...
Click to collapse
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem

ahmadbasher said:
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
Click to expand...
Click to collapse
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.

tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
thanks for replay bro i will tri it

tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
I tri it and no change
Again reboot to fastboot

ahmadbasher said:
I tri it and no change
Again reboot to fastboot
Click to expand...
Click to collapse
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.

tsongming said:
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
Click to expand...
Click to collapse
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me ? But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again

Is it possible that this is part of the problem..!
I can't check it
@tsongming

ahmadbasher said:
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Click to expand...
Click to collapse
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img

ahmadbasher said:
Is it possible that this is part of the problem..!
I can't check it
@tsongming
Click to expand...
Click to collapse
No that is just encryption, if the issue was related to encryption the flashall.bat method would have resolved it.
If you had a persist issue, you would see specific messages about not being able to mount the persist partition.

tsongming said:
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
Click to expand...
Click to collapse
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?

ahmadbasher said:
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
Click to expand...
Click to collapse
Hey sorry for the delay in getting back to you, I sent you the link for the file via PM.
Also, I would strongly suggest using the stock miui initially. Just until you know it's resolved. Also while Miui is installed make a full TWRP backup and save it to your desktop. This way you always have a full backup to resolve any serious issues.
Then once you know everything is working as it should then go back to what you prefer..

For the record this issue was solved. Anyone reading this, make sure that you have a full working TWRP backup of your working device, it will save you a lot of headaches. The solution for the refresh rate is issue is restoring stock DTBO, and then flashing Miui Stock.

Stuck on G logo after root.

I just received my direct from Google Pixel 4 XL running the June 2020 update and proceeded to root it using the instructions found here https://www.xda-developers.com/google-pixel-4-root-magisk/ after flashing the patched boot.img and rebooting the phone doesn't boot past the G logo; the status bar just loops indefinitely. Is there something I'm missing? Any help would be much appreciated.
I have no modules loaded, no custom kernel or ROM.

Go to recovery and reset the phone,
And reboot the phone in each steps

The guide looks mostly like what I do every month, though I haven't done June yet.
I don't think this will solve your issue, but usually I flash the patched boot image to both slots as Magisk in-place updates seem to fail if I don't...
Code:
fastboot flash boot magisk_patched.img --slot=all
I assume you didn't have any obvious issues with the guide steps aside from not booting after Step 5?
Make sure your platform tools are the newest you can get. Also make sure that you didn't get the Telstra variant of the June update.
If all else fails, try to revert by dirty flashing the (correct) June 2020 stock ROM. You'll only lose root if you do it correctly. (you don't have working root anyways)
Take the giant ZIP file you downloaded to get the boot image, merge it with platform tools and edit the flash-all.bat file... near the bottom, remove the "-w " from the command so it reads
Code:
fastboot update image-coral-qq3a.200605.001.zip
Save the changes and run the .bat file after booting the phone to fastboot and making sure its visible to platform tools.

jljtgr said:
The guide looks mostly like what I do every month, though I haven't done June yet.
I don't think this will solve your issue, but usually I flash the patched boot image to both slots as Magisk in-place updates seem to fail if I don't...
Code:
fastboot flash boot magisk_patched.img --slot=all
I assume you didn't have any obvious issues with the guide steps aside from not booting after Step 5?
Make sure your platform tools are the newest you can get. Also make sure that you didn't get the Telstra variant of the June update.
If all else fails, try to revert by dirty flashing the (correct) June 2020 stock ROM. You'll only lose root if you do it correctly. (you don't have working root anyways)
Take the giant ZIP file you downloaded to get the boot image, merge it with platform tools and edit the flash-all.bat file... near the bottom, remove the "-w " from the command so it reads
Code:
fastboot update image-coral-qq3a.200605.001.zip
Save the changes and run the .bat file after booting the phone to fastboot and making sure its visible to platform tools.
Click to expand...
Click to collapse
Your first suggestion results in the phone booting, but ending up on a black screen with only the power menu
dirty flashing results in a successful unrooted boot, but rooting seems to not be possible for some users including myself. No clue why

Try flashing the patched boot to both boots but don't use the all slots command, do them one at a time, A, then B. See if that gets it.

So I am a fool.
I didn't run these commands using the latest "platform-tools"
but I will remember this instructions if I have issues in the future!

I am on latest platform tools and have tried all options presented and still get black screen with adb access and power menu. Other thoughts?

I just downloaded the full image and was getting ready to patch the boot image and flash it on my 2 day old Pixel 4xl. Maybe I will wait unless others have had success with this. I am on the June update. I made sure I didn't download the Telstra version.
Is there any reason to not just use the "Download Zip" option in Magisk? That always worked fine for me on my last phone.
Thanks, Chris
---------- Post added at 06:27 PM ---------- Previous post was at 06:12 PM ----------
I took the plunge and it booted just fine. I am on a G020J if that help. Hardware MP1.0.
I did not realize that TWRP was not available for the Pixel 4xl yet. What is everyone using for a custom recovery?

reedc83 said:
I just downloaded the full image and was getting ready to patch the boot image and flash it on my 2 day old Pixel 4xl. Maybe I will wait unless others have had success with this. I am on the June update. I made sure I didn't download the Telstra version.
Is there any reason to not just use the "Download Zip" option in Magisk? That always worked fine for me on my last phone.
Thanks, Chris
---------- Post added at 06:27 PM ---------- Previous post was at 06:12 PM ----------
I took the plunge and it booted just fine. I am on a G020J if that help. Hardware MP1.0.
I did not realize that TWRP was not available for the Pixel 4xl yet. What is everyone using for a custom recovery?
Click to expand...
Click to collapse
I feel like the options inside Magisk are for phones that are already rooted to update Magisk. I guess what your edit is saying is that you used to use TWRP with the ZIP?
Anyways, there are no custom recoveries for the same reason there is not TWRP. The partition scheme for Pixel phones that come with Android 10 pre-installed is too different for TWRP to live on it. I don't know enough about this subject, but I thought I read there was no separate recovery partition that could be made custom.

Everyone has been doing it all along, when people have issues it's usually the wrong boot image, wrong complete image, flashed boot image to wrong slot, used the factory cable (yes, it's a thing, don't use it or flashing), don't have the correct and/or latest tools. There was an issue with windows 8.1 and flashing, I don't remember what that was but those of you flashing and still on 8.1 you'll want to do a search for that.
@Brakiss, you may want to try the whole smash if all else has failed... THIS WILL DELETE YOUR DATA!
Start by going over to Goog ---> https://developers.google.com/android/images and getting the full factory image and the latest tools; even if you already did it do it again being careful to verify you have the correct image. While you're grabbing goods get the Magisk APK so you can install it after the image is flashed. For the flashing portion please follow the directions on that page to the letter. Do not use the factory cable; use an A to C. Before you flash run these commands one at a time
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
After flashing get the boot image directly from the factory image you downloaded and not any other source and move it over to your phone along with the Magsik APK. Install magisk manager and then use it patch the boot image. You'll take that over to your PC and flash it as usual but do it to both slots and do them separately, do not use the all slots.

jljtgr said:
I feel like the options inside Magisk are for phones that are already rooted to update Magisk. I guess what your edit is saying is that you used to use TWRP with the ZIP?
Anyways, there are no custom recoveries for the same reason there is not TWRP. The partition scheme for Pixel phones that come with Android 10 pre-installed is too different for TWRP to live on it. I don't know enough about this subject, but I thought I read there was no separate recovery partition that could be made custom.
Click to expand...
Click to collapse
Correct, there is no recovery partition anymore. That has been a thing for a while now and not specific to the Pixel. My Moto x4 that I used prior to the Pixel 4xl had the recovery in the boot image but there was still TWRP for it. Whenever rooting that phone you have to boot a custom recovery image then from in there flash the separate custom recovery image/zip installer. It would modify the recovery that is embedded into the boot image.
I really hope that devs smarter than myself will figure it out and make a way to get TWRP on there.

On Android 11 Beta 2.5, I patch the original boot image, I then send it via fastboot, I tried flashing all partitions, manually _a and _b and stuck on Google logo ... When I put back the original boot.img, everything works properly. Miss my root but haven't seen any help on this :| Worked until I switched to 11 Beta ...

I have the problem too
Just as Chronos300 reported, I got stuck on the G logo. Some of my problem may be self-inflicted since I was not careful enough in following the directions: evidently it's important to finish the process for unlocking the bootloader before going to fastboot again to flash the Magisk boot image. I got stuck on the G logo but thought that I would have my way out by flashing the July factory image.
Most of that process worked out: things were good until the end when I saw a lot of messages about files that aren't present in image-coral-qq3a.200805.001.zip like boot.sig or recovery.img. I guess these are optional: the *.sig files may be intended to contain a checksum or hash and the recovery.img may just have gone away with the recovery partitions. Finally was an error that was fatal:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Click to expand...
Click to collapse
That's awful cheery. I see that the difference between flash-all.sh and flash-base.sh is that the former has the "fastboot -w update" that Shayded talks about. I tried running the update command as Shaded recommends, without the -w switch. This time it got farther, but this time the final message was "failed to extract 'product.img': I/O error"
Sure enough, image-coral-qq3a.200805.001.zip contains no product.img file. Is this my problem, or is the solution somewhere else? Would an older factory image have the missing file?

Sigh of relief
My phone's back in the land of the living. I had noticed the links on the factory-image page for the flash tool. Thinking that maybe these were better maintained, I thought to try out the August update for coral.
The flash tool downloaded whatever big image it grabs and then started into the installation. After a few minutes the fastbootd screen came up and the progress bar went to about 80%--and then everything hung. Hoping on hope, I decided I could leave it like this all night if I had to.
It might have taken half an hour, but it did finally come up with the screen saying everything had updated. Sure enough, it made it through the boot and came up to the setup screens.
Enabled developer mode, saw that the bootloader was indeed unlocked, and went about setting some settings. Haven't tried root yet, but it's sure great to be back in business!

epic_task said:
{...}
Sure enough, image-coral-qq3a.200805.001.zip contains no product.img file. Is this my problem, or is the solution somewhere else? Would an older factory image have the missing file?
Click to expand...
Click to collapse
Personally, I don't understand how you ended up without product.img... it's literally half of the internal ZIP file. (you're not supposed to extract this ZIP, anyways)

jljtgr said:
Personally, I don't understand how you ended up without product.img... it's literally half of the internal ZIP file. (you're not supposed to extract this ZIP, anyways)
Click to expand...
Click to collapse
No, I never altered that zip file and was not trying to extract individual files from it when making that final run of fastboot update.
What I can tell you is that I was sleepy by the time I was doing that. There were two things I missed noting at the time but see this morning: product.img is indeed in the internal zip file and a message a couple of lines above the final error message (I had left the terminal window open):
extracting product.img (2102 MB) to disk...ziparchive W 08-18 00:00:43 31524 31524 Zip: unable to allocate 2204832024 bytes at offset 0: No space left on device
Click to expand...
Click to collapse
I would think that my failing to wait for a complete boot with an unlocked bootloader before attempting to flash magisk_patched.img did something unfortunate to the partitioning scheme. Evidently the web-based flash tool cleared it up.

Maybe I'm suggesting the obvious... but do you have 2-4GB available on every drive? It's complaining there's no available space. Typically product.img is split into 500MB parts and sent separately... so you'd need at least 2x the space available for the parts.

The flash-all is generic and looks for some files which are not used by these phones. This failure described is usually the wrong cord, you must use a USB A to USB C rather than a C to C. If not that it's going to be a tools/driver issue. There are a number of guides which can show how to find and delete old drivers and reinstall new drivers. Removing the W gets rid of the wipe but doesn't otherwise affect the flashing and will have nothing to do with it's success or failure; you are in effect dirty flashing when you remove it from the flash-all.

Need help with TWRP patching - V409N

Hello everyone.
My phone is currently on V409N30f_00_LGU_KR_OP_0126.kdz, i was successful in unlocking it via 9008 method, and just a moment ago i was also successful in patching it with magisk (thanks to great guide here: https://forum.xda-developers.com/t/root-eu-lmv405ebw-magisk.3912959/ ). I had some problems, mainly i didn't know that you actually need proper abl_a/abl_b to boot the OS (i thought it's not a part of boot process, unless you push some buttons, but that doesn't seem to be the case). My final problem is that i can't seem to be able to get a proper permanent fastboot installed, and by proxy i can't get TWRP as well. Therefore i have couple of questions here:
1. How to get proper fastboot on an encrypted phone with android Q? Do i have to get rid of the encryption? How?
2. From what I understand, the boot partition needs to be patched to include TWRP, similar to how magisk was prepared - is there guide how to do that?
3. Why the phone fails to boot if i try to sideload/fastboot to TWRP image provided on this forum?
Thanks in advance for all your support

Scorcerer said:
Hello everyone.
My phone is currently on V409N30f_00_LGU_KR_OP_0126.kdz, i was successful in unlocking it via 9008 method, and just a moment ago i was also successful in patching it with magisk (thanks to great guide here: https://forum.xda-developers.com/t/root-eu-lmv405ebw-magisk.3912959/ ). I had some problems, mainly i didn't know that you actually need proper abl_a/abl_b to boot the OS (i thought it's not a part of boot process, unless you push some buttons, but that doesn't seem to be the case). My final problem is that i can't seem to be able to get a proper permanent fastboot installed, and by proxy i can't get TWRP as well. Therefore i have couple of questions here:
1. How to get proper fastboot on an encrypted phone with android Q? Do i have to get rid of the encryption? How?
2. From what I understand, the boot partition needs to be patched to include TWRP, similar to how magisk was prepared - is there guide how to do that?
3. Why the phone fails to boot if i try to sideload/fastboot to TWRP image provided on this forum?
Thanks in advance for all your support
Click to expand...
Click to collapse
Follow this link for the 30f boot_a with twrp injected.
Let me try to clarify a bit; The engineering v35 abl is Oreo. So if you have it installed, the phone won't boot, unless your OS is Oreo (which it isn't).
So the purpose of having that abl isn't to boot the phone, it's only to be used for things like 'fastboot oem unlock' or 'fastboot flash abl_a abl_original_a.img'
it's not to boot the phone. And yes, absolutely it's a part of the boot process abl stands for 'android boot loader'.
So to make use of that v35 eng abl (after you've unlocked the boot loader), would be to flash it to the inactive slot on the phone (most people that would be abl_b). That way, you can use twrp to switch slots, use fastboot, then switch back to the active slot.
To use that proved boot_twrp_a.img, you need to 1st, save your original boot partition, just in case. Then flash it (using qfil) to boot_a (assuming that's your active slot). Then, don't boot the device, go directly to recovery. Once in twrp, format data. Then reboot recovery. Then flash magisk and dm_verity.
then u should be all set.
cheers

AsItLies said:
Follow this link for the 30f boot_a with twrp injected.
Let me try to clarify a bit; The engineering v35 abl is Oreo. So if you have it installed, the phone won't boot, unless your OS is Oreo (which it isn't).
So the purpose of having that abl isn't to boot the phone, it's only to be used for things like 'fastboot oem unlock' or 'fastboot flash abl_a abl_original_a.img'
it's not to boot the phone. And yes, absolutely it's a part of the boot process abl stands for 'android boot loader'.
So to make use of that v35 eng abl (after you've unlocked the boot loader), would be to flash it to the inactive slot on the phone (most people that would be abl_b). That way, you can use twrp to switch slots, use fastboot, then switch back to the active slot.
To use that proved boot_twrp_a.img, you need to 1st, save your original boot partition, just in case. Then flash it (using qfil) to boot_a (assuming that's your active slot). Then, don't boot the device, go directly to recovery. Once in twrp, format data. Then reboot recovery. Then flash magisk and dm_verity.
then u should be all set.
cheers
Click to expand...
Click to collapse
Thanks for the TWRP image, i'm gonna flash it after weekend, when i'll have acces to the phone and will report back
One more question here though, are fastboot flashable files also flashable via qfil ?

Scorcerer said:
Thanks for the TWRP image, i'm gonna flash it after weekend, when i'll have acces to the phone and will report back
One more question here though, are fastboot flashable files also flashable via qfil ?
Click to expand...
Click to collapse
Yes, absolutely. With qfil you can pretty much flash anything to any partition. That's why it's wise to be very very cautious, you could flash the wrong image to a partition, it won't stop you, and it could be too big of an image for that partition but qfil will keep writing it and write over the neighboring partition(s)!

Alright,
I went in and flashed v35 eng abl via qfill into abl_a. That gave me fasboot, which i used to do:
fastboot flash boot_b boot-twrp-30f_a.img (the twrp image i've got from you)
and
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
Then, i switched over to b slot, and rebooted straight to recovery.
In TWRP, i wiped data with formatting it, rebooted to recovery again (didn't got asked for password, i think that's a good thing), then installed magisk.zip via sideload (didn't have it on sd card) and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip afterwards.
I still have 2 problems though:
1. I can't mount vendor - in the log i'm getting "Failed to mount /vendor" (unknown error 150)
2. If i try to boot to system it loops over, i have to wait till it switches over to a slot, which gives me fastboot back, which i'm using to boot to recovery on slot B.
Should i just YOLO it and try to install Lineage directly from here (as i have TWRP)? That's my end goal...
EDIT:
I just noticed by DDing off the vendor_a it's reeeeeally different form vendor_b, and i'm considering copying stuff over, especially since i already did KDZ couple of times, so i'm not afraid of starting over.
EDIT: this let me mount /vendor finally, but boot to OS still loops.

Scorcerer said:
Alright,
I went in and flashed v35 eng abl via qfill into abl_a. That gave me fasboot, which i used to do:
fastboot flash boot_b boot-twrp-30f_a.img (the twrp image i've got from you)
and
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
Then, i switched over to b slot, and rebooted straight to recovery.
In TWRP, i wiped data with formatting it, rebooted to recovery again (didn't got asked for password, i think that's a good thing), then installed magisk.zip via sideload (didn't have it on sd card) and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip afterwards.
I still have 2 problems though:
1. I can't mount vendor - in the log i'm getting "Failed to mount /vendor" (unknown error 150)
2. If i try to boot to system it loops over, i have to wait till it switches over to a slot, which gives me fastboot back, which i'm using to boot to recovery on slot B.
Should i just YOLO it and try to install Lineage directly from here (as i have TWRP)? That's my end goal...
EDIT:
I just noticed by DDing off the vendor_a it's reeeeeally different form vendor_b, and i'm considering copying stuff over, especially since i already did KDZ couple of times, so i'm not afraid of starting over.
EDIT: this let me mount /vendor finally, but boot to OS still loops.
Click to expand...
Click to collapse
First thing I see is that you flashed, assuming what you typed above is exactly what you did, vbmeta wrong.
it should be fastboot --disa... --disa... flash vbmeta_b vbmeta_blank.img
The 1st parameter, after 'flash' should be the partition you want to flash to. Then, after that, the image you want to flash to it.
2nd, just ignore the 'can't mount vendor' in the output of when you zip install magisk or dm_verity, it's irrelevant.
So why is it bootlooping when trying to get to system? Possibly the incorrect vbmeta command? Or maybe you didn't format data? (for format, you have to type in 'yes'). Possibly it's not the right image for the os? It is, beyond doubt, 30f that you flashed?
cheers

AsItLies said:
First thing I see is that you flashed, assuming what you typed above is exactly what you did, vbmeta wrong.
it should be fastboot --disa... --disa... flash vbmeta_b vbmeta_blank.img
The 1st parameter, after 'flash' should be the partition you want to flash to. Then, after that, the image you want to flash to it.
Click to expand...
Click to collapse
But that's what i did - i didn't change the command in my command and i copy-pasted it straight from command line and it says vbmeta_b everywhere...
AsItLies said:
2nd, just ignore the 'can't mount vendor' in the output of when you zip install magisk or dm_verity, it's irrelevant.
So why is it bootlooping when trying to get to system? Possibly the incorrect vbmeta command? Or maybe you didn't format data? (for format, you have to type in 'yes'). Possibly it's not the right image for the os? It is, beyond doubt, 30f that you flashed?
cheers
Click to expand...
Click to collapse
Yup, i didn't change name of the boot image you provided so i won't make any mistake here. Also, i noticed that after i restored from KDZ it forced me to grant access to internet and downloaded some kind of patches - can it be that those affected the booting sequence somehow and i should just take clean dump of abl_b for example so that it can be patched properly?
Oh, just now it occured to me, i can basically take two dumps, one after kdz restore and the other after booting it, then compare them with md5 and i'll know if it actually does something to them...
EDIT: one more question, is KDZ restoring both slots properly? or only the currently active one?

Scorcerer said:
But that's what i did - i didn't change the command in my command and i copy-pasted it straight from command line and it says vbmeta_b everywhere...
Yup, i didn't change name of the boot image you provided so i won't make any mistake here. Also, i noticed that after i restored from KDZ it forced me to grant access to internet and downloaded some kind of patches - can it be that those affected the booting sequence somehow and i should just take clean dump of abl_b for example so that it can be patched properly?
Oh, just now it occured to me, i can basically take two dumps, one after kdz restore and the other after booting it, then compare them with md5 and i'll know if it actually does something to them...
EDIT: one more question, is KDZ restoring both slots properly? or only the currently active one?
Click to expand...
Click to collapse
hmmmm, confusing. So u speak of clean dump abl_b so it can be patched... but we never patch abl (a or b).
and no, the 'downloaded some kind of patches' are just updates to their specific apps, it's not making any change to 'system'.
when using lgup, you should first use Part D/L and choose all partitions (you can clearly see it's doing both a & b by the list). Also, if doing a 'refurbish', it should be updating both slots. Only 'upgrade' would do one side and then switch to that side.
cheers

Okay, so, step-by step, i'll try it once again and will also be taking notes meanwhile
First, i restored from KDZ by refurbishing V409N30f_00_LGU_KR_OP_0126.kdz to be exact.
Just now i flashed eng35 into abl_a which got me into fastboot no problem - the fastboot screens says SECURE BOOT is "yes" and DEVICE STATE "unlocked" which seems okay i guess...
Flashing the TWRP image you provided with
fastboot flash boot_b boot-twrp-30f_a.img
I intend to leave abl_a with fastboot for the future and so i plan to boot from b side
Now the vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
went in just fine.
Reboothing to recovery - set the b slot to be active:
fastboot set_active b
rebooting form the phone buttons directly into recovery...Got TWRP 3.3.1-0 - asks for password, i have to cancel it obviously. Swiping to allow modifications and going directly to Wipe->Format Data->yes - works and done, but complains about /vendor and /data/media/TWRP/.twrps.
Going back a bit and rebooting TWRP to recovery again - This time it doesn't ask me for password so i think i got rid of the encryption.
Flashing Magisk-v22-0.zip from their webpage, i'm clicking on add more zips and adding Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip as well, clicking on reboot system aaaaand bootloop

Okay good, making progress for sure.when I get back to my computer I'll post a link to the magisk and DM verity I use that I know will work. Not positive that those are the problem, but everything else seems to be exactly what you should be doing.

Scorcerer said:
Okay, so, step-by step, i'll try it once again and will also be taking notes meanwhile
First, i restored from KDZ by refurbishing V409N30f_00_LGU_KR_OP_0126.kdz to be exact.
Just now i flashed eng35 into abl_a which got me into fastboot no problem - the fastboot screens says SECURE BOOT is "yes" and DEVICE STATE "unlocked" which seems okay i guess...
Flashing the TWRP image you provided with
fastboot flash boot_b boot-twrp-30f_a.img
I intend to leave abl_a with fastboot for the future and so i plan to boot from b side
Now the vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
went in just fine.
Reboothing to recovery - set the b slot to be active:
fastboot set_active b
rebooting form the phone buttons directly into recovery...Got TWRP 3.3.1-0 - asks for password, i have to cancel it obviously. Swiping to allow modifications and going directly to Wipe->Format Data->yes - works and done, but complains about /vendor and /data/media/TWRP/.twrps.
Going back a bit and rebooting TWRP to recovery again - This time it doesn't ask me for password so i think i got rid of the encryption.
Flashing Magisk-v22-0.zip from their webpage, i'm clicking on add more zips and adding Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip as well, clicking on reboot system aaaaand bootloop
Click to expand...
Click to collapse
check this folder for the version of Magiisk I know works. Don't remember why, but have read the latest version of Magisk is a problem somehow. Pretty sure if you follow the steps as u did above, with this magisk, it will work.
cheers

Hiho, thanks for sticking with me.
I did everything the same except for using the Magisk you provided, and when i finally got to it, it bootlooped all the same
I tried to flash stuff in different order and stuff, but accomplished nothing.
And then I remembered i read somewhere that the OTA only does update one slot at a time, so i thought maybe Refurbish behaves the same and flashes the other slot (in my case it'd be A since i'm trying TWRP and stuff on B)
I started comparing partitions, and almost all of them were the same, except:
515cddf67500d0be189f6fc386bad7c7 /dev/block/by-name/OP_a
7fe5ca2a051d6dbb9ef191fbee0af98c /dev/block/by-name/OP_b
a4b4bbed1d0a0aa668d76558a9d10fb4 /dev/block/by-name/abl_a
4c47ecd7254de2dd84f88dbc3e31ccc2 /dev/block/by-name/abl_b
65c4413067309174d839b98b3c7eff0e /dev/block/by-name/laf_a
e7e47f8e1e05f21cf06c638bf537be67 /dev/block/by-name/laf_b
c62e2c813eeaba8682bb7dd5e26ffa8b /dev/block/by-name/oem_a
65b0e730e47fd0017c11852917ef1d2b /dev/block/by-name/oem_b
dd90de59c1b08c949326d1625a8e4d55 /dev/block/by-name/system_a
d192b99fd2cc8a48dd3f106d9f0f8233 /dev/block/by-name/system_b
Obviously abl_a is different since i installed v35 eng to it, but the rest should be the same, right?
Since they're not, can i just dd from a to be and be done with it? A slot always booted fine, but since I'm installing eng into it I never tried to do twrp and stuff there...

Aaaand it works
So the trick was just to make sure that the proper OS is actually here, and then, well, everything works like a charm i guess I used newer magisk, and so far everything looks okay
Now i'm gonna put in Lineage, but this should be easy
This also means that Refubish doesn't flash everything as we thought it's supposed to be

Scorcerer said:
Aaaand it works
So the trick was just to make sure that the proper OS is actually here, and then, well, everything works like a charm i guess I used newer magisk, and so far everything looks okay
Now i'm gonna put in Lineage, but this should be easy
This also means that Refubish doesn't flash everything as we thought it's supposed to be
Click to expand...
Click to collapse
yeah the only one I trust to flash everything would be part D/L. When doing it, you select ea individual partition, and they are all listed, both a and b slots.
The purpose of the 'dual' slots (and no recovery partition any longer) is to update 1 slot at a time, while the other slot is the older OS version. That's the way OTA's are suppose to happen. But if you use LGUP and do a Part D/L, then both sides have the same OS.
it's confusing. Good u got it working!
cheers

Hi AsltLies,
I could see that you sent a 30f boot_a image with TWRP injected on it for Scorcerer. I'm on identical situation. Only difference that i want to stay on Pie. Probably i cant use that file as i'm on Pie.
Could you point me please how do i get to inject TWRP on a boot_a pie firmware. My devide and situation is identical as for Mr. Scorcerer. V409N, korea version.
I would like to try this guide here as it seems very confiable
Thanks in advance.

sptw said:
Hi AsltLies,
I could see that you sent a 30f boot_a image with TWRP injected on it for Scorcerer. I'm on identical situation. Only difference that i want to stay on Pie. Probably i cant use that file as i'm on Pie.
Could you point me please how do i get to inject TWRP on a boot_a pie firmware. My devide and situation is identical as for Mr. Scorcerer. V409N, korea version.
I would like to try this guide here as it seems very confiable
Thanks in advance.
Click to expand...
Click to collapse
If you want to stay on Pie, your situation is easier, you can just follow the guide to unlock and then use fastboot to boot twrp, use 'ramdisk inject' to inject the twrp image. Reboot to recovery, format data, reboot recovery again, flash magisk and dm_verity.
cheers

sptw said:
Hi AsltLies,
I could see that you sent a 30f boot_a image with TWRP injected on it for Scorcerer. I'm on identical situation. Only difference that i want to stay on Pie. Probably i cant use that file as i'm on Pie.
Could you point me please how do i get to inject TWRP on a boot_a pie firmware. My devide and situation is identical as for Mr. Scorcerer. V409N, korea version.
I would like to try this guide here as it seems very confiable
Thanks in advance.
Click to expand...
Click to collapse
Didn't realize it was available, but follow for the 20n boot+magisk boot image. This Link
I'd suggest using qfil to (first backup your original boot partition) to flash this to your active boot partition. Then exit edl mode and use the key combo to go directly to recovery (now twrp). Format data, then reboot recovery, then flash magisk and dm_verity. All set!
cheers

Hi AsltLies,
Thanks for both of informations. Let me try to explain a bit more. I am able to root the device with magisk. I made a boot_a patched using magisk apk and inject diretly into boot_a using qfill. It works like a charm. No problem at all.
The problem is that there are something wrong with viper4android using magisk. I want the older 2.3.4 driver and it has a kind of problem using convolver and system inject. User app method does not work.
I own a LG V20 with viper4android on it, and i can confirm that there are something wrong with viper on LG V40. My LG V20 is not a Bang & Olufsen and not even Merodian tune. Maybe the problem lies on this meridian audio tuned on LG V40. Chances are great about that. Devices sound differents and i have to accept this. But...
I would like to try the method that i used to root the LGV20 : Supersu and not magisk. I dont care about safety net. I dont use it. And a second problem with magisk : two apk refuse to open with magisk root method. I know they work with rooted devices but using rootcloack on xposed and xposed is very hard to get to work on magisk ( very limited )
So, i would like to use SuperSu method and not magisk to inject the old 2.3.4 viper4android directly on TWRP. I know how i can do it to works using the original drive and apk from the original devs. ( I dont like the new version 2.7 )
So, sorry for the long explanation, but do you know how i can install TWRP without to use magisk? ( That [TWRP] LG V40 / Judypn does not work. I only get bootloop ).
Thanks again.
In time: Maybe i'm doing something wrong to install TWRP. Do i need to instal it in both slots ( a and b? Do i need to access TWRP using the slot that is not active and make the zips install from there and not from the active slot? It's a kind of confusion for me. I already read a lot about it, but i'm still in doubt how it really works. I'm not interested to use another ROM, just stock.

sptw said:
Hi AsltLies,
Thanks for both of informations. Let me try to explain a bit more. I am able to root the device with magisk. I made a boot_a patched using magisk apk and inject diretly into boot_a using qfill. It works like a charm. No problem at all.
The problem is that there are something wrong with viper4android using magisk. I want the older 2.3.4 driver and it has a kind of problem using convolver and system inject. User app method does not work.
I own a LG V20 with viper4android on it, and i can confirm that there are something wrong with viper on LG V40. My LG V20 is not a Bang & Olufsen and not even Merodian tune. Maybe the problem lies on this meridian audio tuned on LG V40. Chances are great about that. Devices sound differents and i have to accept this. But...
I would like to try the method that i used to root the LGV20 : Supersu and not magisk. I dont care about safety net. I dont use it. And a second problem with magisk : two apk refuse to open with magisk root method. I know they work with rooted devices but using rootcloack on xposed and xposed is very hard to get to work on magisk ( very limited )
So, i would like to use SuperSu method and not magisk to inject the old 2.3.4 viper4android directly on TWRP. I know how i can do it to works using the original drive and apk from the original devs. ( I dont like the new version 2.7 )
So, sorry for the long explanation, but do you know how i can install TWRP without to use magisk? ( That [TWRP] LG V40 / Judypn does not work. I only get bootloop ).
Thanks again.
In time: Maybe i'm doing something wrong to install TWRP. Do i need to instal it in both slots ( a and b? Do i need to access TWRP using the slot that is not active and make the zips install from there and not from the active slot? It's a kind of confusion for me. I already read a lot about it, but i'm still in doubt how it really works. I'm not interested to use another ROM, just stock.
Click to expand...
Click to collapse
Well... i got to install TWRP in slot a. No more encrypt data. Install Selinux ( SuperSu ) too. Reboot to recovery and no more ask for password, so it works. Data continue to be there. TWRP see the Selinux root, but it always return to TWRP. It does not matter reboot to system, recovery and power off, it always return to TWRP. So, i go to the EDL mode, install v35eng on abl_a, install ablpiestock again to abl_a and...TWRP again...I cant boot.

sptw said:
Well... i got to install TWRP in slot a. No more encrypt data. Install Selinux ( SuperSu ) too. Reboot to recovery and no more ask for password, so it works. Data continue to be there. TWRP see the Selinux root, but it always return to TWRP. It does not matter reboot to system, recovery and power off, it always return to TWRP. So, i go to the EDL mode, install v35eng on abl_a, install ablpiestock again to abl_a and...TWRP again...I cant boot.
Click to expand...
Click to collapse
Hmmm, not sure yet what's going on but I updated the link above in prev post, it now points to a gdrive folder called 20n.
There's a new boot image in it that has just twrp injected, no magisk. Try that and see if it doesn't help. Be sure though of which is your active slot. The way a treble enabled device does ota updates is it will update the inactive slot, with the new version, switch slots, and then boots the new version. What that means is the OLD version is now the inactive slot.
So if u are on 20n, be sure to flash the new image to that slot, not the old one. If need be, use twrp or fastboot (getvar all) will tell you which slot is active.
cheers

How to install GSI ROM on OnePlus n100.

Good morning guys.

bentalebnordine said:
Recently I installed lineage os 11 gsi rom on my OnePlus n100 and I wanted to share this experience with you guys :
Click to expand...
Click to collapse
- First you need to download This mini sdk
one_plus_nord_sdk.zip
drive.google.com
It is necessary for the cmd commands to work
- you need also to install the drivers , just go to
Universal ADB Drivers
OnePlus-USB-Drivers.zip
drive.google.com
You need to install both drivers clockworkmod and one plus drivers.
- To unlock the bootloader of your oneplus device just connect it to a Windows computer with USB debugging on and run the following commands from the mini sdk folder that just downloaded
adb devices
Then check your device for confirmation. Then
adb reboot bootloader
Then run the command
fastboot oem unlock
A factory screen will pop-up asking for confirmation, you need to confirm using the volume buttons and the power button.
The phone will reboot into recovery and wipe the data. Please do not interrupt this process or the device will not boot anymore.
So just be patient until the phone finishes booting and set it up and turn the USB debugging on.
bentalebnordine said:
2: after that you need to boot your device on fastboot mode, simply by running the code
adb reboot bootloader
And run the command
fastboot --disable-verity flash vbmeta vbmeta.img
Then this command
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Click to expand...
Click to collapse
Note that you need to flash both files only once, unless you returned to stock rom.
bentalebnordine said:
Then run the command
fastboot reboot fastboot
Then flash the system of your choice by visiting
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
Note that the file downloaded would be in Xz format, so you need to extract it with 7zip or beanzip and put it on sdk folder.
The file downloaded must end with arm64_bvS.img. Xz and not with arm64_avS.img.xz (bvS not avS) or the phone will stuck on bootloop.
And the file extracted must not exceed 2.6 gB or you will get an error of resizing the system partition.
After flashing the system with the command
fastboot flash system <your system >.img
Run the command
fastboot -w
And finely the command
fastboot reboot
And good luck.
Click to expand...
Click to collapse
If you updated to Android 11 Oxygen OS 11 you need to switch slots by running the command
fastboot --set-active=a
Because android 11 were installed in the b slot.
If you have a problem booting into fastboot mode try extracting the mini sdk provided in the tmp folder on your desktop computer.
The working Android versions are 10,11,12. Now I am running Resurrection Remix ROM android 10 just amazing
NAMING
Some information you should know about knowing what type of gsi it is
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
Z = dynamic superuser included
-lite = for VNDK Lite vendors (also can help with broken camera even on normal VNDK vendors)
so in most common example "arm64_avZ" is ARM64 A-only vanilla with dynamic superuser
you can simply look to the attached text file.

I am unable to flash any of the .bvs.img gsi files on a Metropcs (11) phone -- BE2015 following the guide. Bootloader is unlocked.
Any help is appreciated.

joegib said:
I am unable to flash any of the .bvs.img gsi files on a Metropcs (11) phone -- BE2015 following the guide. Bootloader is unlocked.
Any help is appreciated.
Click to expand...
Click to collapse
Me I have a BE2013 variant and I was able to flash it with gsi roms using just this guide. I should mention that I am not an expert on rom development.

If I am not mistaken, the BE2013 variant is the global factory unlocked. If so, then maybe these carrier devices will not work with your excellent guide. That being said, I was able to get the DSU to work fine -- AOSP 12.

If you're on the Metro firmware it's a bit tricky. You'll most likely have to still be running Android 10 but you can decrypt the data partition and mount system r/w. After you've accomplished that then it's a piece of cake. Follow this thread, I've been able to remount the system partition read/write on both my Google Pixel running Android 11 and Metro Firmware of OnePlus Nord n100. https://forum.xda-developers.com/t/...-superrw-featuring-makerw-read-write.4247311/

Is GSI for nord n100 updated?

VPH20 said:
Is GSI for nord n100 updated?
Click to expand...
Click to collapse
I'm running Project Arcana Android 12 GSI on my n100 without any issues. I've flashed serval different GSI ROMS but it's by far the best. There's a few things you need to know to successfully flash it but if the steps are followed exactly it's not a problem at all. Here are a few screenshots. It passes safety net basically out the gate with Magisk installed. You'll definitely have to flash the Global firmware to the Metro variant If you happen to be on that version. Luckily, if that's the case someone has already created a modified MSM flash tool that works without any other modifications.
{
"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"
}

Thanks, the link please.

bentalebnordine said:
Thanks, the link please.
Click to expand...
Click to collapse
There's no verified instructions on this but I took the liberty to upload the necessary files to my Google drive that I used to successfully flash this GSI. First and foremost you'll need to revert back to the global stock firmware 10.5.5 using the msm tool. If you're on the the European firmware then I'm not sure if this will work for you or not and it definitely won't work on the Metropcs version but if you happen to be on the Metro version then you can flash the Global firmware to that device which is what I did. Once you're on stock 10.5.5 enable debugging and oem unlock in developer options and reboot to bootloader. If your bootloader isn't already unlocked enter the command fastboot flashing unlock_critical and use the volume keys to select unlock the bootloader. Your device will be wiped. Wait for the system to reboot then go back into developer options and enable debugging again. Once again reboot to the bootloader. Once there enter the command fastboot -w and wait for it to finish. Once it's complete enter fastboot reboot fastboot and wait to enter fastbootd mode. Use the vendor.img that's included in the zip file I have linked and enter fastboot flash vendor_a (name of vendor).img. Once it's complete enter fastboot reboot bootloader. Once you're back into the bootloader interface enter fastboot -w and wait for it to complete. Then with the twrp file I've supplied enter fastboot boot twrp10.img to boot to recovery (Don't flash only boot!!) When you enter recovery choose wipe, then format data and type yes. Reboot to the bootloader once again. Enter fastboot reboot fastboot and wait to enter fastbootd mode. Once there enter fastboot flash product_a product_gsi.img. Then enter fastboot erase system_a. Next enter fastboot resize-logical-partition system_a 4210000000. Once that's complete enter fastboot reboot bootloader. Once you're in the bootloader enter fastboot -w once again. Once complete boot back to twrp with fastboot boot twrp10.img. This is when you'll flash the GSI and it has to be loaded on your sdcard. Flash it to the system partition and reboot to the bootloader once it's complete. Your next move is important if you want it to boot. Again with the images I've supplied enter fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img then fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img. Now you can reboot to the system. For some reason twrp won't boot anymore once this GSI is flashed so I've also included the stock boot.img you can patch with Magisk and flash via fastboot to root and pass safety net.
Oneplus_files.zip
drive.google.com
https://xiaomemeindex.com/treble/Arcana/20220226/ProjectArcana_v402-arm64-bgS_20220226.img.xz

sdflowers32 said:
There's no verified instructions on this but I took the liberty to upload the necessary files to my Google drive that I used to successfully flash this GSI. First and foremost you'll need to revert back to the global stock firmware 10.5.5 using the msm tool. If you're on the the European firmware then I'm not sure if this will work for you or not and it definitely won't work on the Metropcs version but if you happen to be on the Metro version then you can flash the Global firmware to that device which is what I did. Once you're on stock 10.5.5 enable debugging and oem unlock in developer options and reboot to bootloader. If your bootloader isn't already unlocked enter the command fastboot flashing unlock_critical and use the volume keys to select unlock the bootloader. Your device will be wiped. Wait for the system to reboot then go back into developer options and enable debugging again. Once again reboot to the bootloader. Once there enter the command fastboot -w and wait for it to finish. Once it's complete enter fastboot reboot fastboot and wait to enter fastbootd mode. Use the vendor.img that's included in the zip file I have linked and enter fastboot flash vendor_a (name of vendor).img. Once it's complete enter fastboot reboot bootloader. Once you're back into the bootloader interface enter fastboot -w and wait for it to complete. Then with the twrp file I've supplied enter fastboot boot twrp10.img to boot to recovery (Don't flash only boot!!) When you enter recovery choose wipe, then format data and type yes. Reboot to the bootloader once again. Enter fastboot reboot fastboot and wait to enter fastbootd mode. Once there enter fastboot flash product_a product_gsi.img. Then enter fastboot erase system_a. Next enter fastboot resize-logical-partition system_a 4210000000. Once that's complete enter fastboot reboot bootloader. Once you're in the bootloader enter fastboot -w once again. Once complete boot back to twrp with fastboot boot twrp10.img. This is when you'll flash the GSI and it has to be loaded on your sdcard. Flash it to the system partition and reboot to the bootloader once it's complete. Your next move is important if you want it to boot. Again with the images I've supplied enter fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img then fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img. Now you can reboot to the system. For some reason twrp won't boot anymore once this GSI is flashed so I've also included the stock boot.img you can patch with Magisk and flash via fastboot to root and pass safety net.
Oneplus_files.zip
drive.google.com
https://xiaomemeindex.com/treble/Arcana/20220226/ProjectArcana_v402-arm64-bgS_20220226.img.xz
Click to expand...
Click to collapse
Thank you very much my friend for the help, I have the E2013 and it worked.

Awesome, I'm glad to hear it boots on the E2013. If you're on the the Metro version as I was it's difficult but not impossible. Unfortunately for myself I had no guide, just a few pieces of information I picked up here and there that I was able to bundle together into one long process. The great thing about OnePlus is the MSM flash tool. I've flashed firmware from just about every Android manufacturer but it's by far the easiest if you happen to brick your device. So easy even someone with no prior experience wouldn't have an issue using it.
I'd also like to mention that if you're into theming your device, the infamous dev kdragOn has developed an app called repainter that's quite amazing and works really well on this device and ROM. I'm in no way affiliated with him or the advertisement of his app but just making an honest recommendation

sdflowers32 said:
Awesome, I'm glad to hear it boots on the E2013. If you're on the the Metro version as I was it's difficult but not impossible. Unfortunately for myself I had no guide, just a few pieces of information I picked up here and there that I was able to bundle together into one long process. The great thing about OnePlus is the MSM flash tool. I've flashed firmware from just about every Android manufacturer but it's by far the easiest if you happen to brick your device. So easy even someone with no prior experience wouldn't have an issue using it.
Click to expand...
Click to collapse
Exactly.

bentalebnordine said:
Exactly.
Click to expand...
Click to collapse
I sent you a PM if that's okay please and thank you.

sdflowers32 said:
Awesome, I'm glad to hear it boots on the E2013. If you're on the the Metro version as I was it's difficult but not impossible. Unfortunately for myself I had no guide, just a few pieces of information I picked up here and there that I was able to bundle together into one long process. The great thing about OnePlus is the MSM flash tool. I've flashed firmware from just about every Android manufacturer but it's by far the easiest if you happen to brick your device. So easy even someone with no prior experience wouldn't have an issue using it.
I'd also like to mention that if you're into theming your device, the infamous dev kdragOn has developed an app called repainter that's quite amazing and works really well on this device and ROM. I'm in no way affiliated with him or the advertisement of his app but just making an honest recommendation
Click to expand...
Click to collapse
Can I ask a stupid question most likely. I have the BE2015 variant and I followed your instructions to a T and they worked so thank you very much for that.
However if I wish to use another ROM as myself I personally like Android 10 which ROM would you recommend works with our devices? I tried using LineageOS but the Gapps file does not want to install each time I get error.
Edit: Might be time I update my signature lol

Markus214 said:
Can I ask a stupid question most likely. I have the BE2015 variant and I followed your instructions to a T and they worked so thank you very much for that.
However if I wish to use another ROM as myself I personally like Android 10 which ROM would you recommend works with our devices? I tried using LineageOS but the Gapps file does not want to install each time I get error.
Edit: Might be time I update my signature lol
Click to expand...
Click to collapse
Go to this page you will find extra details about how to resize system partition and install larger system files.
https://forum.xda-developers.com/conversations/gsi-roms.14701453/#convMessage-15038845

Okay I just want to say thank you first and foremost to @bentalebnordine and @sdflowers32 because without your both helpful and informative guides I would have taken much longer lol! I can get a guide going completely. With the above guide that sdflowers posted make sure you follow this to a T or you won't boot trust me. Also the GSI images that work best for our device must be the following
system-arm64-ab-img.xz and they will work with no issues I'll put up a cleaned up guide as well to hopefully help others but again this is all only possible with the help of you two first and foremost so thank you!

Markus214 said:
Can I ask a stupid question most likely. I have the BE2015 variant and I followed your instructions to a T and they worked so thank you very much for that.
However if I wish to use another ROM as myself I personally like Android 10 which ROM would you recommend works with our devices? I tried using LineageOS but the Gapps file does not want to install each time I get error.
Edit: Might be time I update my signature lol
Click to expand...
Click to collapse
DOT (Droid on Time) is another GSI that works beautifully on this device but it's Android 11. I personally haven't tried any 10 GSI'S. If you want to update to 11 through stock firmware I already have a DOT super.img I repacked that I'm pretty sure can be flashed without issues with the Android 11 twrp for this device and I'm certain can be flashed via fastbootd mode. Other than project arcana it's the only one I've been impressed with and I've flashed 7 or 8. At least 3 of them I could never get to completely boot after trying every trick of the trade. Arcana is by far the best but DOT runs a tight race. If interested let me know and I'll upload the super.img. I packed it myself so if I ever get bored and just want to go back it would be a much less painless process to flash and I've tested it and it works perfectly.

sdflowers32 said:
DOT (Droid on Time) is another GSI that works beautifully on this device but it's Android 11. I personally haven't tried any 10 GSI'S. If you want to update to 11 through stock firmware I already have a DOT super.img I repacked that I'm pretty sure can be flashed without issues with the Android 11 twrp for this device and I'm certain can be flashed via fastbootd mode. Other than project arcana it's the only one I've been impressed with and I've flashed 7 or 8. At least 3 of them I could never get to completely boot after trying every trick of the trade. Arcana is by far the best but DOT runs a tight race. If interested let me know and I'll upload the super.img. I packed it myself so if I ever get bored and just want to go back it would be a much less painless process to flash and I've tested it and it works perfectly.
Click to expand...
Click to collapse
Thank you very much that would be great! I just downloaded DOT to try it out. I used it before on my 7T and it's great. I just am stubborn I'll say where I like Android 10 the most and 11 not bad but 12 I just don't like the interface and magisk 24 especially for what I do with the phones. I ideally would love to be able to use lineage but when it came time to flash Gapps I kept getting storage error even with resizing. I just want to again say seriously thank you so much without your guide I'd still be screwed

Instructions for flashing DOT GSI
(Start by flashing to stock 10.5.5 with the MSM tool for the device and follow the previous instructions to unlock the bootloader but only to this point)
I decided to edit this because it's been so long since I've removed encryption on this device I completely left out the steps to do so which are imperative. It's much easier to remove encryption on Android 10 than 11 with this device but as far as I know this is the sure fire way to flash an Android 11 GSI on this device. Maybe it can be flashed from 10 but I can't guarantee it as I can with this so here is the revised instructions.
1. Use the MSM tool to revert back to stock and unlock the bootloader
2. Upgrade OTA as far as you can up until version 11.0.4 (Most likely you'll have to use the file I've included in the attachment and perform a local upgrade by placing the zip file in your internal storage to get on this version) Remember this is only for the global firmware but it can be cross flashed with a modded MSM tool.
3. Once you're on 11.0.4 you'll need to format an SD card to exfat which can be done easily with windows because you're going to have to place the super.img on it to be flashed in TWRP. Android supports exfat but for reasons beyond my understanding when you purchase an SD card for Android it comes formatted as fat32 which has a 4 gig limitation.
4. Unzip the 11.0.4 super.img and load it on the SD card along with Magisk.apk. You can either rename the extension from Magisk.apk to Magisk.zip and keep just the one file on your card or copy it and place them both on but nevertheless you'll need the zip file to flash in TWRP after flashing the super partition. Use the TWRP11.img provided in this devices thread and have it placed in your platform-tools folder on PC. Reboot to the bootloader and enter fastboot boot twrp11.img (Or whatever the name of the image happens to be). Once you're in recovery choose wipe, format data and enter yes. Go back and choose install image then select the super11.0.4.img and flash to the super partition. Go back and flash Magisk.zip.
5. Now boot to the bootloader and with the volume keys enter stock recovery.
6. Wipe Data, Cache and System and reboot. I usually reboot back to the bootloader then boot TWRP again just to make sure I can mount all partitions assuring that the device is decrypted.
7. Now all you have to do is place the DOT_SUPER.img on your SD just as you previously did, wipe and format data, then flash it to the super partition just as you did with the stock 11.0.4 super. The boot image is provided as well but I wouldn't advise uninstalling Magisk. Upgrade if you like but it may not boot if you flash the stock boot.img
DOT Files