Develop Bugs

How Do I Flash Factory Image?

It's been some time since I've done this so I'm hoping someone can point me in the right direction. I've had my Pixel 2 XL for like a month now...but since day one I've gotten occasional force closes of various apps. Well next week I'm going with a new carrier (Koodo here in Canada) and I thought it would be a great time to flash a factory image to make sure everything is correct. Also when does Google release monthly updates? Is it the first week of April, maybe I'll just wait and flash that factory image when it comes out. Thanks for the help.

acheney1990 said:
It's been some time since I've done this so I'm hoping someone can point me in the right direction. I've had my Pixel 2 XL for like a month now...but since day one I've gotten occasional force closes of various apps. Well next week I'm going with a new carrier (Koodo here in Canada) and I thought it would be a great time to flash a factory image to make sure everything is correct. Also when does Google release monthly updates? Is it the first week of April, maybe I'll just wait and flash that factory image when it comes out. Thanks for the help.
Click to expand...
Click to collapse
If your wanting to flash a factory image, you'll need a few things first.
I would highly recommend that you look over the linked thread carefully. It has many links and tips to help you on your way :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

acheney1990 said:
It's been some time since I've done this so I'm hoping someone can point me in the right direction. I've had my Pixel 2 XL for like a month now...but since day one I've gotten occasional force closes of various apps. Well next week I'm going with a new carrier (Koodo here in Canada) and I thought it would be a great time to flash a factory image to make sure everything is correct. Also when does Google release monthly updates? Is it the first week of April, maybe I'll just wait and flash that factory image when it comes out. Thanks for the help.
Click to expand...
Click to collapse
https://developers.google.com/android/images

Make sure you have the latest adb and fastboot. Get them from Google...
Go get the latest image and Unzip it. Do not Unzip the folder inside. Move everything you just unzipped into the folder with adb and fastboot.
Now, if you've unlocked and unlocked critical, great. If you haven't unlocked critical, you'll have to. The system image won't install if the bootloader is out of date. Sadly, this will wipe your data.
If both are already unlocked, then open the flash-all file with a text editor and remove the,"-w" and the space preceding, then save the file. Removing the -w will keep your data. Run the flash-all.bat file and in about 10 minutes everything will be flashed.

back to stock
how to back on stock ....i sell the phone and want all stock...no root no boot loader unlocked ...what is the fastest way pls

lomski said:
how to back on stock ....i sell the phone and want all stock...no root no boot loader unlocked ...what is the fastest way pls
Click to expand...
Click to collapse
First thing!! Forget fast!! You need to fastboot flash a full factory image with the -w still in the script. Maybe even do it twice. Then go in and do a factory reset from the OS for good measure. Once that is done and you know it reboots you can go through the locking command. I would NOT toggle the OEM switch in dev though.
Sent from my Pixel 2 XL using XDA Labs

So this has been a a very frustrating experiance but I think I've got everything working again. I don't know how many times I've flashed different factory images and then tried to install TWRP and then install a new custom rom. So I want to explain all of the steps I took (if I remember them all).
0. I couldn't boot into my system but had TWRP installed. At this point I should have tried to get all my data from the sd card via "adb pull /sdcard" .
1. I didn't find any option to fix my system. So I followed this guide to install a factory image (link).
3. I skipped through all of the setup processes and gave my phone wifi. Then I went into the system and did a factory reset.
4. After skipping thourgh the setup again I enabled adb and bootet into the bootloader "adb reboot bootlader"
5. From the bootloader I booted into TWRP by "fastboot boot twrp-3.3.0.0-taimen.img. In the recovery I set the display time out to 300s because for some reason once the phone timed out I could get into twrp any more and the screen stayed black.
6. I transferred the twrp installer and my rom by " adb push TWRP_installer.zip /sdcard/Download" and " adb push ROM.zip /sdcard/Download"
7. I first added the TWRP installer to the flash queue and then I added the rom and then falshed them both. This allowed me to install the rom.
8. For some reason TWRP was not installed. So repeat step 5 and only flash the TWRP_installter.zip
Problems I had:
- In twrp I often got errors that said unable to mount system or vendor. I decided to ignore the error but this thread might help
- Installing TWRP while the stock rom is installed led to the problem that touch didn't work in TWRP
- Entering a pin for the stock rom and then installing TWRP led to TWRP asking for a pin to decrypt my data. Apparently this is not the case if you use a stock image which is older

After flashing stock ROM ota and twrp installer zip the only way to get TWRP to respond to touch is if you disable screen lock and connect to your PC before booting TWRP.
I've found the most reliable way to flash factory images is do it manually with fastboot, latest platform tools installed and a Linux OS like Ubuntu or pop os.
But first do some research and get comfortable with fastboot commands. And dear god don't relock your bootloader unless you're ?% sure it's totally stock.

@schpongo,
Also, a good point to keep when flashing via TWRP is to flash/install ONE AT A TIME. As per the great @Az Biker, you should even reboot to the bootloader after each subsequent flash/install. So, in your case, it seems that you might/should be rebooting to the bootloader three times; one for TWRP installation, one for flashing the custom ROM, and one more for any other subsequent installation (i.e. custom kernel or custom font)...
Also, as it's been said before, but stock kernel doesn't play nice with touch commands on TWRP, and (usually) the only way around it is to reboot into bootloader using the adb command -- as opposed to holding the volume-down button or from an app.
I know you figured this all out already, but it might bear repeating just in case you didn't know and/or to help any other users here...

Would this procedure work? (install magisk and twrp on 10.0.3.0)

First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
Code:
tar -xzf ********.tgz
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.

i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.

12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.

viking777 said:
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.
Click to expand...
Click to collapse
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little

12:121390 said:
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little
Click to expand...
Click to collapse
Anti roll back is disabled and not an issue if bootloader is unlocked

Nice thread. Tried it as well but no chance 10.0.3.00 + twrp + magisk. And you are right the problem is twrp.
Sent from my Phh-Treble vanilla using Tapatalk

12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/

12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
brother i also want to install RR PIE Rom can you please give me the guide link?

hossman said:
Anti roll back is disabled and not an issue if bootloader is unlocked
Click to expand...
Click to collapse
correct it is not. what happened was.. lol. i thought i was crafty and did some file swapping and made miflash setups that would flash so the stock files as usual , but with gsi's like RR and/or bootleggers for the system image. and it works, up until i flashed from RR to bootleggers with those setups described previously . there is where my genius was flawed. lol. lesson learned
---------- Post added at 06:43 AM ---------- Previous post was at 06:38 AM ----------
marstonpear said:
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/
Click to expand...
Click to collapse
for me, i have not come across anything caused by the GSI. any issues I've faced are purely self inflicted.

I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!

Voodoojonny said:
I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!
Click to expand...
Click to collapse
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).

viking777 said:
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).
Click to expand...
Click to collapse
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.

Voodoojonny said:
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.
Click to expand...
Click to collapse
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.

viking777 said:
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.
Click to expand...
Click to collapse
There seems to be some bugs restoring system and vendor... Some users talked about... I usually only save and restore the data and boot partition and I never had any problems with that. For all other partitions you can use miflash or fastboot...

Yeah all my twrp full backups don't work after a fresh stock installment either, that's very annoying.
The twrp version for daisy is bugged. Backups are not working, the wifi with GSI Roms on pie stock is not working anymore as soon as twrp is installed as well.
Sent from my Phh-Treble vanilla using Tapatalk

Thanks for the replies above. @voodoojohnny
In my case it was the data partition that caused the restore to fail, vendor and system and boot all seemed to go through normally. @cd492
Based on what you say along with my own experiences and those of voovoojohnny, it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.

viking777 said:
First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.
Click to expand...
Click to collapse
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.

InfinityXDA said:
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.
Click to expand...
Click to collapse
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.
Click to expand...
Click to collapse
I meant it, at least for now, but maybe your post will help somebody else.

viking777 said:
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
I meant it, at least for now, but maybe your post will help somebody else.
Click to expand...
Click to collapse
Yes I didn't see that post but understand I didn't give you links to the official TWRP, I gave you the unofficial fixed TWRP which actually features SD Card Support and trust me it works completely fine I haven't had a problem yet. This took me hours upon hours to figure out what I was doing wrong.
The only specific reason you are not successfully getting TWRP is because you didn't flash the aboot.img after installing the zip.
I hope this helps you in the future!

thanks InfinityXDA for the tutorial, you should create a post just for it~

[Magisk] Root for the Galaxy S10 Series

Here comes official Magisk support for the Galaxy S10!
Let's get Magisk to kick start the development of these Samsung devices!
Link to Instructions
Carefully read through everything in the page linked above! Follow the instructions closely so you don't end up bricking your device
Technical Details
Google enforces all devices that ships with Android 9.0 to use system-as-root in part of "Project Treble", so Samsung finally introduced their own "flavor" of the implementation. More details regarding system-as-root can be found in the official Google dev site. Samsung is using the A-only system-as-root setup, meaning that its boot image will only contain the kernel binary without ramdisk included. Similar setup has already been deployed on many new devices, and the solutions for those devices are rather simple: add a new ramdisk section into the boot image and hexpatch the kernel to always use ramdisk as rootfs. However in Samsung's case, the bootloader simply does not load anything other than the kernel binary to the memory, meaning no matter what we do the kernel will always use the system partition as root directory. This leaves us no option but to install Magisk onto the recovery partition.
Installing to the recovery partition have its own issues: first is that a service called "flash_recovery" will run when the system starts up, which will restore the recovery image back to stock on startup. This is unacceptable because not only does it uninstall Magisk in the process, the data encryption key will also be changed due to fact that Samsung's data encryption keys are tied to the bootloader status and boot/recovery image signatures, and thus causing the device unable to boot in following reboots unless factory reset. The solution to this problem is to simply repack the boot image to remove the binary integrity and also the signature of the partition. The second issue is that since Magisk and recovery shares the same partition, how can we actually boot into recovery? (e.g. to factory reset your device, or have custom recovery co-exist with Magisk) Fortunately a solution that detects button key presses is introduced, which details are already provided in instructions.
To make matters even worse, Samsung introduced a "VaultKeeper" service, which adds another "lock" on top of the OEM lock of the bootloader. By default the service will "relock" the bootloader after data is wiped. Only after the initial setup will it verify the OEM lock option and changes the bootloader state accordingly. If you are running custom firmware with stock system, DO NOT try to wipe data or else you might end up bricking your device due to vaultkeeper locking your bootloader up, which will eventually lead to bootloader refusing to boot because unofficial partitions are detected.
For custom ROM developers, the first few things you would want to remove is VaultKeeper to protect your users from bricking their devices. For stock ROM users, just make sure to always boot to Magisk after a data wipe, or never power off your device before finishing the initial setup and verify OEM lock is enabled.

thx

Yay.

The best day of my life!!

Can I ask, when we install Magisk what sammy stuff will be broken? I understand Knox will be tripped but what 'features' will still be available.
Does the fingerprint still work for instance
Amazing work though, well done buddy

Fantastic!
I hope people carefully read those instructions!

ok, who's trying it first on an European S10+ ?

..

Amazing! Is this for unlocked Snapdragon too?

S9 Exynos not install
On S9 the installation does not give error, but on restart Magisk is no longer installed.

ooonea said:
On S9 the installation does not give error, but on restart Magisk is no longer installed.
Click to expand...
Click to collapse
I'm aware of this issue

cant even boot into download mode with the way you have given... is there a step missing?
ahh, turn the phone off, USB connected and press Bixby and Volume Down.

Fix?
topjohnwu said:
I'm aware of this issue
Click to expand...
Click to collapse
Will you fix it?

A couple of questions:
1. What will happen if I boot from boot partition after installing magisk? What steps will be needed to recover from that?
2. Why final wipe after installing magisk is needed?

ooonea said:
Will you fix it?
Click to expand...
Click to collapse
What an odd question... obviously.

I got some questions about Safetynet
1. Is Safetynet still passing with this method when you boot to system with magisk?
2. Also if you boot to system without pressing any button, so system without magisk, is Safetynet passing or failing?
Thanks for your hard work.

Download Mode doesn´t work for mee
is there a step missing?

Memento_Mori said:
Download Mode doesn´t work for mee
is there a step missing?
Click to expand...
Click to collapse
The cable must be in too

Thanks,
I have one question, after install Magisk can I still install OTA update ?

tiho5 said:
The cable must be in too
Click to expand...
Click to collapse
I know, but it doesn´t work for me too

Global firmware

I need Global firmware. The version number is KLE2005121OS00MP1.Or other newer versions.
If you have any, you can send me a private message.
Thank you!

johnny886 said:
I need Global firmware. The version number is KLE2005121OS00MP1.Or other newer versions.
If you have any, you can send me a private message,
I will make it into an unbrick tool, which can repair the phone in 9008 mode.
And I will announce the method of unlocking the bootloader for Black Shark 3 and Black Shark 3Pro.
It is free and does not require any payment.
Thank you!
Click to expand...
Click to collapse
i have this phone on my hand the same version what you are looking for, but i dont know how to read the firmware or read dump etc.. sense this phone is new
do you have any other tool to back up the firmware for this device?

renskie said:
i have this phone on my hand the same version what you are looking for, but i dont know how to read the firmware or read dump etc.. sense this phone is new
do you have any other tool to back up the firmware for this device?
Click to expand...
Click to collapse
He cant do none of this he just want the firmware to sold it to peoples

bouyhy01 said:
He cant do none of this he just want the firmware to sold it to peoples
Click to expand...
Click to collapse
I released it for free. You can read my post. ROG2 and redmagic5G files, you don’t know the trouble, don’t talk nonsense.

johnny886 said:
I released it for free. You can read my post. ROG2 and redmagic5G files, you don’t know the trouble, don’t talk nonsense.
Click to expand...
Click to collapse
Redmagic and rog 2 firmwares are all over the net and the oems provides everythings so your argument is pointless

bouyhy01 said:
Redmagic and rog 2 firmwares are all over the net and the oems provides everythings so your argument is pointless
Click to expand...
Click to collapse
sb, what I publish for free is the unbrick tool. Is there any use not you alone

johnny886 said:
sb, what I publish for free is the unbrick tool. Is there any use not you alone
Click to expand...
Click to collapse
you mean edl files firehose etc

KLE2005121OS00MP1
this is incremental ota
how to get full of it
if u dont hav rooted bs3 phone :v

If u want to hav firmware
Lets share your loader firehose file
I will get full firmware for u

Need BS3S global rom. im using CN rom KLEN2011100CN00MQ3 with joyui12. As i know latest global rom for BS3S version is KLEN2010281OS00MP3 WITH JOYUI11. want to convert to global. any have global rom please share it here. thanks

xSasori said:
Need BS3S global rom. im using CN rom KLEN2011100CN00MQ3 with joyui12. As i know latest global rom for BS3S version is KLEN2010281OS00MP3 WITH JOYUI11. want to convert to global. any have global rom please share it here. thanks
Click to expand...
Click to collapse
There is no global ROM for 3s. You have to wait until there is a global version of the phone available and someone shares the link to Blackshark servers/dumps it.
in the meantime check out chinese firmware https://forum.xda-developers.com/t/...l-and-up-to-date-china-rom-downloads.4197717/
If you talk english its fine. You can also install magisk and use a system app disabler/"remover" so you can at least disable all the trash from china.
If you are uncomfortable with an English UI you could try installing a GSI-image (e.g. Lineage / MIUI / etc), which should basically work (just make sure to backup everything first and unlock bootloader in case sth goes wrong):
1. boot TWRP and wipe everything
2. install KLEN2011100CN00MQ3 from my thread
3. Download an A/B GSI ROM (refered to gsi.img later on)
Now there are different methods:
1. reboot to fastboot, "fastboot erase system" if it does not work try "fastboot reboot fastboot" and try to erase system again. if this does not work try "fastboot reboot fastbootd" and erase system (if it was successful stay in the mode it worked and go to 2., if you did not succeed with any, reboot to bootloader and go to 2 as well)
2. Flash GSI by either (you have to try what works):
2.1 fastboot flash system gsi.img, check if boots
2.2 fastboot flash super gsi.img, check if boots
2.3 fastboot reboot fastboot and then try 2.1 and 2.2, check if boots
2.4 fastboot reboot fastbootd and then try 2.1 and 2.2, check if boots
3. Report back if it worked (Exact steps so i can reproduce what you did and which GSI u used) if sth bugs you can send me a logcat (PM!), what the problem is (e.g. WLAN not working) and i can check if there is an easy solution.
It would be great to see if users stuck on china rom can just install a GSI and have full Languages.

wertus33333 said:
There is no global ROM for 3s. You have to wait until there is a global version of the phone available and someone shares the link to Blackshark servers/dumps it.
in the meantime check out chinese firmware https://forum.xda-developers.com/t/...l-and-up-to-date-china-rom-downloads.4197717/
If you talk english its fine. You can also install magisk and use a system app disabler/"remover" so you can at least disable all the trash from china.
If you are uncomfortable with an English UI you could try installing a GSI-image (e.g. Lineage / MIUI / etc), which should basically work (just make sure to backup everything first and unlock bootloader in case sth goes wrong):
1. boot TWRP and wipe everything
2. install KLEN2011100CN00MQ3 from my thread
3. Download an A/B GSI ROM (refered to gsi.img later on)
Now there are different methods:
1. reboot to fastboot, "fastboot erase system" if it does not work try "fastboot reboot fastboot" and try to erase system again. if this does not work try "fastboot reboot fastbootd" and erase system (if it was successful stay in the mode it worked and go to 2., if you did not succeed with any, reboot to bootloader and go to 2 as well)
2. Flash GSI by either (you have to try what works):
2.1 fastboot flash system gsi.img, check if boots
2.2 fastboot flash super gsi.img, check if boots
2.3 fastboot reboot fastboot and then try 2.1 and 2.2, check if boots
2.4 fastboot reboot fastbootd and then try 2.1 and 2.2, check if boots
3. Report back if it worked (Exact steps so i can reproduce what you did and which GSI u used) if sth bugs you can send me a logcat (PM!), what the problem is (e.g. WLAN not working) and i can check if there is an easy solution.
It would be great to see if users stuck on china rom can just install a GSI and have full Languages.
Click to expand...
Click to collapse
Successfully flashed on my first try

Kraya333 said:
Successfully flashed on my first try
Click to expand...
Click to collapse
Nice! Thanks a lot for trying now we'd have to try if the native shark apps (like rgb control/power overlay) work under lineage

wertus33333 said:
Nice! Thanks a lot for trying now we'd have to try if the native shark apps (like rgb control/power overlay) work under lineage
Click to expand...
Click to collapse
I followed the instructions of Redmi K30 Pro and also used its vbmeta.img because apparently you can't boot into non MIUI(JOYUI in this case) without flashing it.
Reboot to bootloader:
adb reboot bootloader
Flash vbmeta with
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If using wzsx150's unofficial TWRP, flash stock recovery
fastboot flash recovery recovery.img
Reboot to fastbootd
fastboot reboot fastboot
Flash system with
fastboot flash system system.img
Wipe data
fastboot -w
Reboot phone
fastboot reboot
Home
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
I got the vbmeta.img here https://flashxiaomi.com/download-and-install-twrp-on-xiaomi-redmi-k30-pro/
I skipped flashing stock recovery cause I didn't flash twrp in my recovery. I don't know what will happen tho if flashing gsi with twrp installed.
I flashed GSI AOSP 10.0 v220 and v222 and both boot successfully.
Wifi, Bluetooth, and Camera seems working. Unfortunately I can't test Data, Messages and Call because I don't have any signal in my area.
The ROM was pretty smooth overall and they even have 120/90hz supported. Only reason I won't use the ROM as daily driver is because the rgb is always lighting green. Can't seem to find in the settings to turn it off, and even sideloaded the Light Effect app from the stock rom and it goes not responsive every time I open it.
Also, I got bootlooped after pressing Securize which was supposed to unroot superuser that came with the gsi ROM. I did get the phone back to revert to stock ROM.

wertus33333 said:
Nice! Thanks a lot for trying now we'd have to try if the native shark apps (like rgb control/power overlay) work under lineage
Click to expand...
Click to collapse
Also do you know any gsi ROM with working desktop mode? I can't wait for xiaomi to develop one.

Kraya333 said:
I followed the instructions of Redmi K30 Pro and also used its vbmeta.img because apparently you can't boot into non MIUI(JOYUI in this case) without flashing it.
Reboot to bootloader:
adb reboot bootloader
Flash vbmeta with
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If using wzsx150's unofficial TWRP, flash stock recovery
fastboot flash recovery recovery.img
Reboot to fastbootd
fastboot reboot fastboot
Flash system with
fastboot flash system system.img
Wipe data
fastboot -w
Reboot phone
fastboot reboot
Home
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
I got the vbmeta.img here https://flashxiaomi.com/download-and-install-twrp-on-xiaomi-redmi-k30-pro/
I skipped flashing stock recovery cause I didn't flash twrp in my recovery. I don't know what will happen tho if flashing gsi with twrp installed.
I flashed GSI AOSP 10.0 v220 and v222 and both boot successfully.
Wifi, Bluetooth, and Camera seems working. Unfortunately I can't test Data, Messages and Call because I don't have any signal in my area.
The ROM was pretty smooth overall and they even have 120/90hz supported. Only reason I won't use the ROM as daily driver is because the rgb is always lighting green. Can't seem to find in the settings to turn it off, and even sideloaded the Light Effect app from the stock rom and it goes not responsive every time I open it.
Also, I got bootlooped after pressing Securize which was supposed to unroot superuser that came with the gsi ROM. I did get the phone back to revert to stock ROM.
Click to expand...
Click to collapse
Thanks a lot for the detailed instructions . Can i use your research to create a thread for gsi's in the future? (i will mention you ofc). There should be some option for notification lights somewhere in settings, does sth change if you change that?
i think gsi's only work with root.
for desktop mode, i think lineage had such a function in developer options once (no idea if its still there) or you could use linux4android and emulate a full linux (but you can only share your phone display that way--> not possible to use phone normally while using linux. Maybe by simulating a second screen and forcing the vnc viewer to this screen? but you would have to do some research concerning this)

johnny886 said:
I need Global firmware. The version number is KLE2005121OS00MP1.Or other newer versions.
If you have any, you can send me a private message.
Thank you!
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/black-shark-3-global-rom-support-ota-update.4203471/
You r wellcome
This mp3

Kraya333 said:
Also do you know any gsi ROM with working desktop mode? I can't wait for xiaomi to develop one.
Click to expand...
Click to collapse
android 10 has desktop mode by default you just have to activate it
see https://www.xda-developers.com/make-android-10-desktop-mode-useful/

wertus33333 said:
Thanks a lot for the detailed instructions . Can i use your research to create a thread for gsi's in the future? (i will mention you ofc). There should be some option for notification lights somewhere in settings, does sth change if you change that?
i think gsi's only work with root.
for desktop mode, i think lineage had such a function in developer options once (no idea if its still there) or you could use linux4android and emulate a full linux (but you can only share your phone display that way--> not possible to use phone normally while using linux. Maybe by simulating a second screen and forcing the vnc viewer to this screen? but you would have to do some research concerning this)
Click to expand...
Click to collapse
I tried the notification lights in the settings and it didn't work. I flashed back the gsi rom earlier in the morning and used it for a day and I discovered that call volume isn't working. Even when I slide it down to basically 0 call can still be heard at maximum volume. And there is an option on developer settings for desktop mode but there was only black screen on the monitor even after turning on the freeform and resizable settings, the same on joyui rom(there's also desktop mode in settings on joyui). Also audio is broken from the start, you have to disable audio effects on treble settings.
For going back to joyui rom restoring it from backup isn't possible(at least in my case it didn't boot up). You'd have to flash the firmware back. I flashed mine back to stock rom just now, and I just remembered I didn't get to test the shark space bar and what would happen if I slide it on.
And yeah, you can use my research for making the thread. I'm wondering why there's no one talking about flashing gsi on bs3 till now.

Kraya333 said:
I tried the notification lights in the settings and it didn't work. I flashed back the gsi rom earlier in the morning and used it for a day and I discovered that call volume isn't working. Even when I slide it down to basically 0 call can still be heard at maximum volume. And there is an option on developer settings for desktop mode but there was only black screen on the monitor even after turning on the freeform and resizable settings, the same on joyui rom(there's also desktop mode in settings on joyui). Also audio is broken from the start, you have to disable audio effects on treble settings.
For going back to joyui rom restoring it from backup isn't possible(at least in my case it didn't boot up). You'd have to flash the firmware back. I flashed mine back to stock rom just now, and I just remembered I didn't get to test the shark space bar and what would happen if I slide it on.
And yeah, you can use my research for making the thread. I'm wondering why there's no one talking about flashing gsi on bs3 till now.
Click to expand...
Click to collapse
If you try that again you can try getting a logcat and send it to me so i can see what the problems are. Maybe you could try any xiaomi optimized gsi. if i find the time i'll do some work over christmas.
maybe u have to reflash the original vbmeta after twrp restore to make it boot.
I think noone talks about gsi's bcs its not officially supported by xiaomi (u cant officially unlock bl) and xiaomi does not necessarily build after googles guidelines for compatibility...

Re-Root? Possible partition messup, Lost root now stuck in fastboot

Hello, Sorry to bug you guys...I read multiple different fourms/how2s and I guess I'm a little mixed at what i should do. I Have the oneplus 7t (hd1505) with android 11 rooted, and after that I installed NikGapps after I had it rooted, then flashed nethunter. Was in the terminal as root, all was well..I believe It rebooted and would'nt boot to rom so i went and re'did magisk, may have used a different patched magisk? but now is stuck fastboot. Cant get it to boot.
Sorry for the maybes but I had brain surgry and my memories not the best. Everything was going fine so I didn't document things like normal. Anyways, Is there a program that helps with thiss? MSM somthing? or could anyone please point me in to a nice how2 or some quality links to assist? I really apprricate it, normally I'd just test till I get it, but I think I may be at a point where I could really mess it up.

5k1tz0 said:
Hello, Sorry to bug you guys...I read multiple different fourms/how2s and I guess I'm a little mixed at what i should do. I Have the oneplus 7t (hd1505) with android 11 rooted, and after that I installed NikGapps after I had it rooted, then flashed nethunter. Was in the terminal as root, all was well..I believe It rebooted and would'nt boot to rom so i went and re'did magisk, may have used a different patched magisk? but now is stuck fastboot. Cant get it to boot.
Sorry for the maybes but I had brain surgry and my memories not the best. Everything was going fine so I didn't document things like normal. Anyways, Is there a program that helps with thiss? MSM somthing? or could anyone please point me in to a nice how2 or some quality links to assist? I really apprricate it, normally I'd just test till I get it, but I think I may be at a point where I could really mess it up.
Click to expand...
Click to collapse
If you don't care about data then use msm tools to factory restore. Or you can flash boot image of the rom you were using (unpatched) in fastboot mode itself.

No need to keep data, I'd prefer to wipe device and start fresh instead of getting stuck on the concept of A/B partitions. I get the CMD getvar, but I'm not sure if i flashed the lineage OS to one or both...at 1 point i think i was booted in A, now its saying B. I got overeager and downloaded multiple ROMs and not sure which one worked. In the past I usually downloaded a few and the first one to work I used. Not smart...I know. If I wanted to wipe all and start fresh with gaspps and root, where/how should I do that? I can't just fasatboot oem unlock , could I? Would you recommend stock OS? Lineage? Thanks for your help BTW.

5k1tz0 said:
No need to keep data, I'd prefer to wipe device and start fresh instead of getting stuck on the concept of A/B partitions. I get the CMD getvar, but I'm not sure if i flashed the lineage OS to one or both...at 1 point i think i was booted in A, now its saying B. I got overeager and downloaded multiple ROMs and not sure which one worked. In the past I usually downloaded a few and the first one to work I used. Not smart...I know. If I wanted to wipe all and start fresh with gaspps and root, where/how should I do that? I can't just fasatboot oem unlock , could I? Would you recommend stock OS? Lineage? Thanks for your help BTW.
Click to expand...
Click to collapse
Go to this thread for MSM Tool download and instructions: Unbrick tool to restore your device to OxygenOS