android 10 - Blu Bold N1 Questions & Answers

has anyone tried flashing the android 10 gsi files? i have pi rooted with magisk right now , just downloaded the gsi/s and am about to flash through bootloader. twrp is still not supported for this device. i have factory image, and a magisk patched image, so i should be okay if this flsh doesnt work......hopefully?
im going to try to usde magisk to patch the new 10 gsi system file and then just flash the patched image...ill let you guys know how it goes!

Sergeantslaughter said:
has anyone tried flashing the android 10 gsi files? i have pi rooted with magisk right now , just downloaded the gsi/s and am about to flash through bootloader. twrp is still not supported for this device. i have factory image, and a magisk patched image, so i should be okay if this flsh doesnt work......hopefully?
im going to try to usde magisk to patch the new 10 gsi system file and then just flash the patched image...ill let you guys know how it goes!
Click to expand...
Click to collapse
AOSP / android 10 = quack
Here is thread already on that.
https://forum.xda-developers.com/bold-n1/how-to/aosp-quack-gsi-t3994409

Related

Stuck in bootloop after Xposed install [Magisk][Exposed][Recovery]

Device is stuck in bootloop after I installed Xposed framework module from magisk manager .
I've tried uninstalling magisk , but the uninstall package terminates with error .
Then I flashed stock boot.img , it is booting but I cannot disable the module as magisk isn't installed.
Is there a way I can removed magisk's files / uninstall magisk modules manually from twrp .
Thanks !
(If there is some more relevant place for this thread , please let me know I'll post this there.)
Edit: Fixed it!
you will have to reflash entire system.img + boot.img again with proper wiping.
I never got xposed working on R6 stock.. (i got it magically working on GSI tho) I really want Xposed tho.. :/
TanRayCz said:
I never got xposed working on R6 stock.. (i got it magically working on GSI tho) I really want Xposed tho.. :/
Click to expand...
Click to collapse
which gsi image & twrp you are using? I flashed rr gsi-nosu-vanilla but it keeps bootloop.
abkdmn said:
which gsi image & twrp you are using? I flashed rr gsi-nosu-vanilla but it keeps bootloop.
Click to expand...
Click to collapse
LOS Treble. Call/SMS issues though. LR Team TWRP.
TanRayCz said:
LOS Treble. Call/SMS issues though. LR Team TWRP.
Click to expand...
Click to collapse
i tried flashing the los (15.1 arm A only) gsi image, stuck at bootloop.
how can u succeed?
Michaelw7 said:
i tried flashing the los (15.1 arm A only) gsi image, stuck at bootloop.
how can u succeed?
Click to expand...
Click to collapse
If youll get into bootloop i suggest you trying to wipe system and data partitions from fastboot (important), then flash stock ROM and then flash the GSI. This most of the time worked for me as clear GSI flash. So steps may not be necessary.
TanRayCz said:
If youll get into bootloop i suggest you trying to wipe system and data partitions from fastboot (important), then flash stock ROM and then flash the GSI. This most of the time worked for me as clear GSI flash. So steps may not be necessary.
Click to expand...
Click to collapse
thank u for the help. i will try it
TanRayCz said:
If youll get into bootloop i suggest you trying to wipe system and data partitions from fastboot (important), then flash stock ROM and then flash the GSI. This most of the time worked for me as clear GSI flash. So steps may not be necessary.
Click to expand...
Click to collapse
[official] miui 10 recovery & fastboot ROM
tried wipe system and data partition from fastboot.
and then flash stock rom (from [official] miui 10 recovery & fastboot ROM thread in kernel sub forum), and then instal the gsi image los 15.1.
still bootloop. idk what i did wrong. still no clue
Michaelw7 said:
[official] miui 10 recovery & fastboot ROM
tried wipe system and data partition from fastboot.
and then flash stock rom (from [official] miui 10 recovery & fastboot ROM thread in kernel sub forum), and then instal the gsi image los 15.1.
still bootloop. idk what i did wrong. still no clue
Click to expand...
Click to collapse
Try to flash stock kernel/boot.img or remove Magisk trough uninstaller. This magically helped me one time
TanRayCz said:
Try to flash stock kernel/boot.img or remove Magisk trough uninstaller. This magically helped me one time
Click to expand...
Click to collapse
where can ai get the stock kernel file?
Michaelw7 said:
where can ai get the stock kernel file?
Click to expand...
Click to collapse
You can restore boot.img by installing Magisk uninstaller update ( it's available on Magisk thread I think) , or download a fastboot update for your device to get stock boot.img
Michaelw7 said:
where can ai get the stock kernel file?
Click to expand...
Click to collapse
You can extract it from firmware ZIP
Michaelw7 said:
where can ai get the stock kernel file?
Click to expand...
Click to collapse
go to this site. (not promoting it or something) https://extract.me paste this link [ http://bigota.d.miui.com/V10.0.1.0....FH_20180919.0000.00_8.1_global_794ccbbe18.tgz ] wait a few second then you will see all files from this archive, download what you want from it. It will save you a lot of time to download entire archive. Trust me.

Lineage OS 17 unable to root with Magisk

Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks
vehz said:
Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks
Click to expand...
Click to collapse
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP
ISoreo said:
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP
Click to expand...
Click to collapse
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time
vehz said:
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time
Click to expand...
Click to collapse
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot
ISoreo said:
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot
Click to expand...
Click to collapse
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root
vehz said:
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root
Click to expand...
Click to collapse
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!
jonapiron said:
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!
Click to expand...
Click to collapse
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
https://drive.google.com/drive/folders/1UdPbIbM3luYIiOdXMXb7raAnWLERjssh
beyond0lte folder is for S10E.
vehz said:
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
beyond0lte folder is for S10E.
Click to expand...
Click to collapse
Oh I'm so stupid, I had seen the Magisk boot img in the files but ended up using another one... It seems to work now, thank you sooo much!!
It still cannot pass SafetyNet check (ctsProfile), I'll investigate that...
I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).
I am trying root Lineage 18.1 on my s10. I have tried differtent magisk-files from TWRP, but still no root access.
What are the required files for 18.1 for Galaxy s10 and steps to get root-access?
Hafizp5100 said:
I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).
Click to expand...
Click to collapse
Dude, thanks so much. I faced the exact same problem with my Z2, now it's running magisk just fine. You saved me a bunch of headaches.

[OOS] [11] Open_Beta_2_HD01BA [EU] [Stock/Patched boot.img] [Stock/ADB Recovery] [Full ZIP] [OOS 10.0.13]

OxygenOS 11 OP7TPro_ O2_BETA_02
Magisk v21.4 Manager 8.0.7 Patched Root Boot Image
https://www.androidfilehost.com/?fid=17248734326145729690
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145729691
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145729692
Stock Recovery Image
https://www.androidfilehost.com/?fid=17248734326145729693
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322771
OxygenOS 11 OP7TPro_ O2_BETA_01
Magisk v21.4 Manager 8.0.7 Patched Root Boot Image
https://www.androidfilehost.com/?fid=17248734326145719958
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145719959
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719960
Stock Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719961
Full ZIP OxygenOS HD01BA 11 Open Beta
https://androidfilehost.com/?fid=17248734326145719998
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322187
May need to install Magisk Manager manually
OxygenOS 10.0.4 EU was kindly picked up by @t-ryder Linked Below
https://forum.xda-developers.com/t/...-rom-oxygen-os-10-0-14.4236633/#post-84539771
OxygenOS 10.0.13 HD01BA Magisk/Stock Boot Images, ADB/Stock Recovery
Magisk v21.1 Manager 8.0.3 Patched Root Boot Image
https://www.androidfilehost.com/?fid=10763459528675591459
May need to install Magisk Manager manually
Full ZIP OxygenOS HD01BA 10.0.13
https://www.androidfilehost.com/?fid=10763459528675591484
Stock Boot Image
https://www.androidfilehost.com/?fid=10763459528675591455
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591468
Stock Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591462
Combined Folders
https://www.androidfilehost.com/?w=files&flid=320311
Usage (Unlocked Bootloader)
adb devices (give permission on device)
adb reboot fastboot
fastboot devices (to confirm that device is being detected)
fastboot flash boot path/to/patched_boot.img or fastboot flash recovery path/to/patched_recovery.img
fastboot reboothttps://www.androidfilehost.com/?fid=17248734326145729693
Thanks for posting these very useful resources... much appreciated...
How's the full zip upload coming along?
I thought I was clever and used the patched magisk image for 10.0.13 HD01BA on my firmware (updated OTA) version 10.0.13 HD01AA... all seems to be working fine barring one crucial function, that being wifi which is greyed out...
I'm assuming the broken wifi radio is symptomatic of the differing firmware versions?
sand_man said:
How's the full zip upload coming along?
I thought I was clever and used the patched magisk image for 10.0.13 HD01BA on my firmware (updated OTA) version 10.0.13 HD01AA... all seems to be working fine barring one crucial function, that being wifi which is greyed out...
I'm assuming the broken wifi radio is symptomatic of the differing firmware versions?
Click to expand...
Click to collapse
I'm grabbing what I think is the HD01AA Full ZIP from Oxygen Updater, I'll grab the stock boot and try making a magisk patched img for you as well, If they work I might add HD01AA to my supported devices manifest.
digidude512 said:
I'm grabbing what I think is the HD01AA Full ZIP from Oxygen Updater, I'll grab the stock boot and try making a magisk patched img for you as well, If they work I might add HD01AA to my supported devices manifest.
Click to expand...
Click to collapse
That's very kind of you sir! I've flashed BA and WiFi is working now. I think my device, as are many others, are impartial to firmware version. BA/AA/global/European, seems to all be the same barring 1 or 2 minor differences. Using the right patched magisk boot image is critical though.
Having said that I'm yet to flash boot the patched image so let's see what effect it has on WiFi (it any)...
Once again thank you for providing these resources. [emoji1303]
sand_man said:
That's very kind of you sir! I've flashed BA and WiFi is working now. I think my device, as are many others, are impartial to firmware version. BA/AA/global/European, seems to all be the same barring 1 or 2 minor differences. Using the right patched magisk boot image is critical though.
Having said that I'm yet to flash boot the patched image so let's see what effect it has on WiFi (it any)...
Once again thank you for providing these resources. [emoji1303]
Click to expand...
Click to collapse
Hope this helps
https://forum.xda-developers.com/7t-pro/how-to/oos-10-0-13-hd01aa-t4195159
@digidude512 Every Update needs a new Thread... interesting.
Stop this sh!t.
K3V1991 said:
@digidude512 Every Update needs a new Thread... interesting.
Stop this sh!t.
Click to expand...
Click to collapse
Your feedback has been taken.
Original Post has been updated for OxygenOS 11 Open Beta.
OOS 10.0.13 is still in original post but moved to spoiler.
Thanks for the update. Will probably stay on 10.0.13 for now though, as it is super stable and practically bug free.
Hello,
I just want to confirm is it really that simple to get Magisk & Root Access just by flashing patched boot image? Won't I need to full system & data wipe? I have stock OOS 10.0.13.
Athum said:
Hello,
I just want to confirm is it really that simple to get Magisk & Root Access just by flashing patched boot image? Won't I need to full system & data wipe? I have stock OOS 10.0.13.
Click to expand...
Click to collapse
yes
Thread updated with Open Beta 2
In the beta 2 A11 i have problem with magisk. Update and bootloop. All steps install correct and finnaly bootloop.
Any steps to fix it?
Magisk 21.4
chudy34 said:
In the beta 2 A11 i have problem with magisk. Update and bootloop. All steps install correct and finnaly bootloop.
Any steps to fix it?
Magisk 21.4
Click to expand...
Click to collapse
Just to confirm are you using a OnePlus 7T Pro EU Model.
HD01BA is for EU, I will be updating my second thread for 7T Global (HD01AA) and India models later.
digidude512 said:
Just to confirm are you using a OnePlus 7T Pro EU Model.
HD01BA is for EU, I will be updating my second thread for 7T Global (HD01AA) and India models later.
Click to expand...
Click to collapse
yes my model is EU.
I updated ota and install magisk unactive slot and the same boot to recovery and bootloop. Maybe problem is in magisk?
Flashing via OTA full ROM works great. After installation was completed I installed magisk to inactive slot and rebooted my device after this and my device is still rooted! Automatic brightness works much better with Beta 2
kaplatz said:
Flashing via OTA full ROM works great. After installation was completed I installed magisk to inactive slot and rebooted my device after this and my device is still rooted! Automatic brightness works much better with Beta 2
Click to expand...
Click to collapse
I get an error. And what version of magisk do you use? I used the latest 21407 and unfortunately bootloop after uploading.
I use 21.4 (21400) and it works like a charm.
Do we get patched boot image or diy instructions for Beta 3?
I see the release candidate for Android 11 has dropped! Anyone have access to the full download file? All I can find is the open_beta 4 which isn't going to work patched and flashed running the RC...
Have anyone can upload the last oos A11 adb recovery please

Patched Magisk 10.3.12

Having issues flashing a patched Magisk boot.img for 10.3.12 for op6t-fajita. I did update from Android 9 but messed up somewhere along the way and lost magisk root.
Side loaded twrp and installed it to recovery slot a/b.
I downloaded the full update from the Xda post. Took payload.bin and put it in the auto extracted input folder. Took the boot.img and patched it on my phone through magisk. Flashed it through adb, constantly led to a boot loop until I reflashed the same boot.img but unpatched. Flashing magisk as a zip also causes the boot loop.
Anyone with a clue of what's going on?
Weird0ne said:
Having issues flashing a patched Magisk boot.img for 10.3.12 for op6t-fajita. I did update from Android 9 but messed up somewhere along the way and lost magisk root.
Side loaded twrp and installed it to recovery slot a/b.
I downloaded the full update from the Xda post. Took payload.bin and put it in the auto extracted input folder. Took the boot.img and patched it on my phone through magisk. Flashed it through adb, constantly led to a boot loop until I reflashed the same boot.img but unpatched.
Anyone with a clue of what's going on?
Click to expand...
Click to collapse
This is stupid question.. Did you downloaded the right file for you device??
SOK seila said:
This is stupid question.. Did you downloaded the right file for you device??
Click to expand...
Click to collapse
Pretty sure I did since my phone works fine with the version I downloaded and flashed.

Question Can someone help me with rooting my note 10 pro?

I'm new here on this site and idk if I'm doing I correctly but I need help with it. I'm a noob to rooting and Twrp stuff. I have unlocked my bootloader and have tried to watch videos about rooting and read articles but I couldn't understand. That's why I am posting this thread. Could someone explain things to me in the most simple way and how can I avoid bootloops or stuff like that if I come across one. I'd appreciate it very much.
I think it is best to start with reading the "HowTo" guides
Elinx said:
I think it is best to start with reading the "HowTo" guides
Click to expand...
Click to collapse
Alright I'll try it, thanks
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
Elinx said:
I think it is best to start with reading the "HowTo" guides
Click to expand...
Click to collapse
Hello Sir, sorry to disturb you again. I have installed the adb, fastboot and fastbootd drivers. I need your help with something, should i continue with the latest version of Magisk? I have Redmi note 10 pro (sweet)
Because you are a starter, I advice to follow the guide exactly.
If you flash a lower version of Magisk, you always can update afterwards with Magisk manager
You haven't said what the reason is for root.
If you want to flash custom rom, you need Twrp or OrangeFox too
That is also done with ADB
In case of Magisk you patch the original boot.img
(that is why you need an original stock boot.img. Keep a copy for revert back)
Elinx said:
Because you are a starter, I advice to follow the guide exactly.
If you flash a lower version of Magisk, you always can update afterwards with Magisk manager
You haven't said what the reason is for root.
If you want to flash custom rom, you need Twrp or OrangeFox too
That is also done with ADB
In case of Magisk you patch the original boot.img
(that is why you need an original stock boot.img. Keep a copy for revert back)
Click to expand...
Click to collapse
Im following the guide that you have given the link for. And by update do you mean I can install new updates of the phone (because I know after rooting you can't or won't receive updates) or do you mean magisk by it? Well I want to modify and tweak with my Phone appearance and install some modules. For now Im not going for custom roms. Since I just want to root my phone for now, could you please tell me what do you mean by original stock boot.img? Because I have downloaded and extracted the rom contents that i have in my phone (following the guide). I know I am asking too much, sorry
p.s. what would you like to suggest me to use the latest version of magisk or some old version?
I mean update of Magisk.
The older versions are working with the same modules till v23
From v24 Magisk has another base (zygisk) and you need other modules
So decide which modules you need for which Magisk version, before flashing
Inside the stock rom you find boot.img and recovery.img (these are replaced by magisk.img and twrp.img)
If something goes wrong you can flash these original images back with ADB and you have stock Miui without root again and can start again with clean sheets.
Elinx said:
I mean update of Magisk.
The older versions are working with the same modules till v23
From v24 Magisk has another base (zygisk) and you need other modules
So decide which modules you need for which Magisk version, before flashing
Inside the stock rom you find boot.img and recovery.img (these are replaced by magisk.img and twrp.img)
If something goes wrong you can flash these original images back with ADB and you have stock Miui without root again and can start again with clean sheets.
Click to expand...
Click to collapse
Thank you alot. Its really helpful to me. Also I just checked that I do not have the recovery.img but the boot.img
Bilalbilly87 said:
Thank you alot. Its really helpful to me. Also I just checked that I do not have the recovery.img but the boot.img
Click to expand...
Click to collapse
If you only flash Magisk you only need boot.img
I see now what you mean
Normally inside the stock fastboot rom you find all partition images, but you recognize only the boot.img
Boot.img is one of them, also recovery.img is one of about 13 partitions.
Be sure to double check the version. It must be exactly the same as what you have now on the phone.
Elinx said:
If you only flash Magisk you only need boot.img
I see now what you mean
Normally inside the stock fastboot rom you find all partition images, but you recognize only the boot.img
Boot.img is one of them, also recovery.img is one of about 13 partitions.
Be sure to double check the version. It must be exactly the same as what you have now on the phone.
Click to expand...
Click to collapse
I have installed Twrp and Magisk As well. I was able to install some modules but with some modules I'm having this problem and I don't quite understand why. I downloaded it from GitHub like the zip file and after flashing.
Congrats with flashing Twrp and magisk
I understand you speak about Magisk modules?
As I said before, ckeck carefully for which Magisk version the module can be flashed
v.xx t/m v. 23 or v24 t/m 25.3 (zygisk)
Elinx said:
Congrats with flashing Twrp and magisk
I understand you speak about Magisk modules?
As I said before, ckeck carefully for which Magisk version the module can be flashed
v.xx t/m v. 23 or v24 t/m 25.3 (zygisk)
Click to expand...
Click to collapse
Thank you for helping me. Actually i was having problem with flashing the modules, because the contents are in the zip file in a folder and they need to be outside of any folder meaning all those files need to be in the zip instead of being in a folder in the zip. I'm good to go as i checked and its installing now.
kon kkonsay modules use krra ha hmy bhi bta
MehtabMad said:
kon kkonsay modules use krra ha hmy bhi bta
Click to expand...
Click to collapse
English forum....
Laptapper said:
English forum....
Click to expand...
Click to collapse
Laptapper, one thing is happening to my RN10P
I have Lineage Os
I have flashed your vantom kernel
Using magisk in it
Problem is my phone is heating after kernel install, i checked cpu clock speed
when i changed min* clock speed to 300 it always reset back to max
i.e. 2304Mhz min and @2304Mhz max.
MehtabMad said:
Laptapper, one thing is happening to my RN10P
I have Lineage Os
I have flashed your vantom kernel
Using magisk in it
Problem is my phone is heating after kernel install, i checked cpu clock speed
when i changed min* clock speed to 300 it always reset back to max
i.e. 2304Mhz min and @2304Mhz max.
Click to expand...
Click to collapse
For me not.
Clean install? With format data yes?
Which kernel vantom latest?
If yes, try the lineage os original kernel again.
Sorry for late reply. Everything has been working okay with modules altho i didnt install alot of them but a few. So i guess there weren't enough modules which provided me any customization for Miui 13 because i had the wrong concept. Now i want to take it a step further, i want to flash a custom rom. I have looked and searched. Have decided to go for either Pixel Exp A12 or AncientOS A12 (It has alot of customizations). Now i want to ask you a few questions that i have in mind.
1) Should I flash Custom Rom through Twrp?
2) If so, do i need to flash that Dm verity file (because when I installed twrp in my stock rom which im still using rn, they told us to do that to avoid bootloop and to keep Twrp permanent so do i also need to do it with custom rom?
3) And if its safe to flash through Twrp, Could you please tell me how to (through twrp if its safe)?
4) Which Rom should i go for? Pixel or AncientOs
lineage Os
Laptapper said:
For me not.
Clean install? With format data yes?
Which kernel vantom latest?
If yes, try the lineage os original kernel again.
Click to expand...
Click to collapse
yes the problem was with magisk module, thermal profile disabler. i removed it and everything is stable now

Categories

Resources