Related
Hi, is anyone here able to backup their persist.img and share it here? I somehow corrupted my partition and my sensors aren't working. I don't know if this applies to this device, but I found this guide on a Xiaomi Mi A1 guide (https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/), or else you can try this (https://youtu.be/LGkDZtQ_ERE?t=124) from 2:04 . If you can achieve the result with a different method you can also share the file here. Thanks in advance to whoever does this.
You're going to need to specify which exact build you're looking for this from...
..or you could just use "Payload Dumper" to extract all the img files from the released packages :
https://androidfilehost.com/?fid=818070582850510260
Didn't think it would matter, anyways, I'm on 9.5.5 GM1913, but if needed I can switch to 9.5.4
@djsubterrain https://i.imgur.com/Z1GyAlR.png no persist here. Do you mind sharing yours?
MrVoshel said:
@djsubterrain https://i.imgur.com/Z1GyAlR.png no persist here. Do you mind sharing yours?
Click to expand...
Click to collapse
Unfortunately TWRP doesn't list that as a backup option so I don't think I can unless you know how.
djsubterrain said:
Unfortunately TWRP doesn't list that as a backup option so I don't think I can unless you know how.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=ma.wanam.partitions&hl=it
can you try using this app?
Gm1917 9.5.6 if it helps you
https://www.dropbox.com/s/8q8hy66obsnfdmw/persist_backup_2019-05-31_17-36-15.img?dl=0
Sent from my GM1917 using Tapatalk
OK, Here you go. Just to confirm I'm on EU 9.5.5, I have Rice magisk module enabled and ElementalX latest kernel, also rooted with latest Magisk :
https://www.androidfilehost.com/?fid=6006931924117886178
The folder contained the img and 2 other files so I just stuck them in there too.
I note that you're in the US so, the post above mine is T-Mobile version (9.5.6 isn't on other versions I don't think), if that's the one you have you might want to go with theirs.
Thanks guys, both working. I'm not in the US, I randomly chose a country. Anyways I flashed the GM1917 9.5.6 on my GM1913 9.5.4, and no problems. Also tested the 9.5.5 GM1913 and working. I don't think persist is phone/update-dependant, also because OnePlus hasn't done any updates or specific changes to the sensors directly from the persist partition. For anyone interested, just get a persist.img, reboot to fastboot and connect your phone to the computer, type this command into fastboot "fastboot flash persist persist_name_xxxx.img" and reboot.
MrVoshel said:
Thanks guys, both working. I'm not in the US, I randomly chose a country. Anyways I flashed the GM1917 9.5.6 on my GM1913 9.5.4, and no problems. Also tested the 9.5.5 GM1913 and working. I don't think persist is phone/update-dependant, also because OnePlus hasn't done any updates or specific changes to the sensors directly from the persist partition. For anyone interested, just get a persist.img, reboot to fastboot and connect your phone to the computer, type this command into fastboot "fastboot flash persist persist_name_xxxx.img" and reboot.
Click to expand...
Click to collapse
Glad to hear you're back up and running.
Glad to hear it worked. I don't think 9.5.6 is a T-Mobile patch. Non T-Mobile phones were getting it ota and it fixed an issue for Verizon users. I think 1+is unifying their build numbers back together.
Sent from my GM1917 using Tapatalk
MrVoshel said:
Thanks guys, both working. I'm not in the US, I randomly chose a country. Anyways I flashed the GM1917 9.5.6 on my GM1913 9.5.4, and no problems. Also tested the 9.5.5 GM1913 and working. I don't think persist is phone/update-dependant, also because OnePlus hasn't done any updates or specific changes to the sensors directly from the persist partition. For anyone interested, just get a persist.img, reboot to fastboot and connect your phone to the computer, type this command into fastboot "fastboot flash persist persist_name_xxxx.img" and reboot.
Click to expand...
Click to collapse
if you mess up persist.img
does it flash from the MSM tool?
virtyx said:
if you mess up persist.img
does it flash from the MSM tool?
Click to expand...
Click to collapse
It didn't for me, took a little bit to figure out why my wifi wasn't working with any of the custom kernels that inline the wifi module in the boot img. Used msm tool as well as fastboot ROM... No luck. After finding this persist img and fastboot flashing, no problem since. Was on 9.5.7 Global when flashed.
zoman7663 said:
It didn't for me, took a little bit to figure out why my wifi wasn't working with any of the custom kernels that inline the wifi module in the boot img. Used msm tool as well as fastboot ROM... No luck. After finding this persist img and fastboot flashing, no problem since. Was on 9.5.7 Global when flashed.
Click to expand...
Click to collapse
really? i wouldve thought the MSM tool would bring it back
do you have the persist.img? do you have a link for those of us who break things.
virtyx said:
really? i wouldve thought the MSM tool would bring it back
do you have the persist.img? do you have a link for those of us who break things.
Click to expand...
Click to collapse
I got the img from this thread, first or second post...
zoman7663 said:
I got the img from this thread, first or second post...
Click to expand...
Click to collapse
Thank you
When fastboot flashing does it wipe persist before flashing the IMG?
virtyx said:
Thank you
When fastboot flashing does it wipe persist before flashing the IMG?
Click to expand...
Click to collapse
Not that I'm aware of, I think it just overwrites it
[/COLOR]
zoman7663 said:
Not that I'm aware of, I think it just overwrites it
Click to expand...
Click to collapse
great! thanks
Sorry to ressurect an old thread. I was just wondering if this persist.img(or this method) can be used to flash the relevant persist.img onto a oneplus 7t pro to restore widevine L1?
So I was using PixelExperiece ROM and decided to switch back to MIUI. I downloaded latest fastboot ROM from MIUI website, Flashed it using MI FLash Tool.
While flashing my phone displayed "System has been destroyed" in between. And MIFlash tool showed some error.
So, I tried flashing again and MIFlash tool now said Bootloader was locked. (Because lock_all_and_install was selected previously).
Therefore I downloaded MI Bootloader unlock tool. (The phone still shows "System has been destroyed"). Ignoring that warning, I went to fastboot and ran unlocker. To my surprise, after unlocking was complete and phone restarted it booted into MIUI. I thought "System has been destroyed" problem would be solved. But later I realised, my camera was not focusing on close range object. It wasnt focusing at all. Then after playing around to check everything I found out, my camera was not focusing, gyro was not working (No auto rotate and noting in CIT test) neither was my compass working. So there is some kind of problem with my hardware now.
Later I tried flashing same fastboot ROM again hoping it will install fully now and not ending up in "System has been destroyed" error. And I also chose option to not lock bootloader while flashing in MI Flash tool. This time the phone did started on to MIUI but in MI Flash tool it kept showing flashing as status. Even after I disconnected my phone USB cable it said flashing. And those hardware things are still not working.
While using PixelExperience I did changed SELinux mode to make ANXCamera work. Would it (SELinux mode) be a problem for hardware not working? Or is there any other problem?
Thanks in advance for any help.
DragonSlayer7# said:
So I was using PixelExperiece ROM and decided to switch back to MIUI. I downloaded latest recovery ROM from MIUI website, Flashed it using MI FLash Tool.
While flashing my phone displayed "System has been destroyed" in between. And MIFlash tool showed some error.
So, I tried flashing again and MIFlash tool now said Bootloader was locked. (Because lock_all_and_install was selected previously).
Therefore I downloaded MI Bootloader unlock tool. (The phone still shows "System has been destroyed"). Ignoring that warning, I went to fastboot and ran unlocker. To my surprise, after unlocking was complete and phone restarted it booted into MIUI. I thought "System has been destroyed" problem would be solved. But later I realised, my camera was not focusing on close range object. It wasnt focusing at all. Then after playing around to check everything I found out, my camera was not focusing, gyro was not working (No auto rotate and noting in CIT test) neither was my compass working. So there is some kind of problem with my hardware now.
Later I tried flashing same recovery ROM again hoping it will install fully now and not ending up in "System has been destroyed" error. And I also chose option to not lock bootloader while flashing in MI Flash tool. This time the phone did started on to MIUI but in MI Flash tool it kept showing flashing as status. Even after I disconnected my phone USB cable it said flashing. And those hardware things are still not working.
While using PixelExperience I did changed SELinux mode to make ANXCamera work. Would it (SELinux mode) be a problem for hardware not working? Or is there any other problem?
Thanks in advance for any help.
Click to expand...
Click to collapse
Wait what u said u flashed recovery rom via mi flash ? U have to flash persist.img (u will find this in your fastboot rom) from custom recovery in system/persist partition. Thats it.
hackermssharma said:
Wait what u said u flashed recovery rom via mi flash ? U have to flash persist.img (u will find this in your fastboot rom) from custom recovery in system/persist partition. Thats it.
Click to expand...
Click to collapse
Im sorry, my mistake. I flased fastboot ROM only. Not recovery. MIFlash tool won't allow you to flash recovery ROM at all.
DragonSlayer7# said:
Im sorry, my mistake. I flased fastboot ROM only. Not recovery. MIFlash tool won't allow you to flash recovery ROM at all.
Click to expand...
Click to collapse
Mmmm... No need to worry extract persist.img from fastboot rom folder and flash via OF recovery in system/persist partition. Then boot u get all your sensors back.
hackermssharma said:
Mmmm... No need to worry extract persist.img from fastboot rom folder and flash via OF recovery in system/persist partition. Then boot u get all your sensors back.
Click to expand...
Click to collapse
Instead of fixing existing sensors, flashing persist.img screwed up my wifi and hotspot. After flashing whole fastboot ROM againg they are now working. But other sensors are still not working.
DragonSlayer7# said:
Instead of fixing existing sensors, flashing persist.img screwed up my wifi and hotspot. After flashing whole fastboot ROM againg they are now working. But other sensors are still not working.
Click to expand...
Click to collapse
Really? I mean i used same method last time for my sensors to work again and that worked for me. Next workaround is u should clean flash miui 10 fastboot rom then update to miui 11 using updater app. Hope it should work for u.
flashing persist.img worked for me.
hackermssharma said:
Really? I mean i used same method last time for my sensors to work again and that worked for me. Next workaround is u should clean flash miui 10 fastboot rom then update to miui 11 using updater app. Hope it should work for u.
Click to expand...
Click to collapse
I flashed same MIUI fastboot ROM again, and miraculously all sensors started working again.:good::good:
DragonSlayer7# said:
I flashed same MIUI fastboot ROM again, and miraculously all sensors started working again.:good::good:
Click to expand...
Click to collapse
Great ??
Sensors
DragonSlayer7# said:
I flashed same MIUI fastboot ROM again, and miraculously all sensors started working again.:good::good:
Click to expand...
Click to collapse
I am also facing the same problem (sensors are not working) after i switched back from Pixel Experience to MIUI 11. Though i read all replies i did get some ideas but not clearly. Can you please little explain how to do it. Step by step method explanation will be much appriciated !! (only installation part, i have all required software and ROM ready for fastboot) I am just not clear how fix my sensors.
--------------------------------------------------------------
EDIT: No need guide. I understood how to do it. Some the things mentioned in reply were new for me so it was hard time for me to understand?.. I am new to Redmi phone
Widevine L1
hackermssharma said:
Mmmm... No need to worry extract persist.img from fastboot rom folder and flash via OF recovery in system/persist partition. Then boot u get all your sensors back.
Click to expand...
Click to collapse
Well i just got to know that by flashing 'persist.img' from a recovery will void Widevine L1 certification (Netflix with no HD, also other HD content streaming platform that requires Widevine L1 certification). I heard it will be permanent warrenty void and i don't know it can be fixed or not.
Azhar001 said:
I am also facing the same problem (sensors are not working) after i switched back from Pixel Experience to MIUI 11. Though i read all replies i did get some ideas but not clearly. Can you please little explain how to do it. Step by step method explanation will be much appriciated !! (only installation part, i have all required software and ROM ready for fastboot) I am just not clear how fix my sensors.
--------------------------------------------------------------
EDIT: No need guide. I understood how to do it. Some the things mentioned in reply were new for me so it was hard time for me to understand?.. I am new to Redmi phone
Click to expand...
Click to collapse
This persist.img thing might work for you or might not.
The full proof way is to reinstall Pixel Experience (Android 10) so that you get your sensors up and running again, then flash MIUI 10 and upgrade to MIUI 11 using system updater app.
Azhar001 said:
Well i just got to know that by flashing 'persist.img' from a recovery will void Widevine L1 certification (Netflix with no HD, also other HD content streaming platform that requires Widevine L1 certification). I heard it will be permanent warrenty void and i don't know it can be fixed or not.
Click to expand...
Click to collapse
Its fine. Just install Netflix from ApkMirror (not from Google Play) and it should work.
Azhar001 said:
Well i just got to know that by flashing 'persist.img' from a recovery will void Widevine L1 certification (Netflix with no HD, also other HD content streaming platform that requires Widevine L1 certification). I heard it will be permanent warrenty void and i don't know it can be fixed or not.
Click to expand...
Click to collapse
Also if you are coming back to MIUI, use this method...
DragonSlayer7# said:
This persist.img thing might work for you or might not.
The full proof way is to reinstall Pixel Experience (Android 10) so that you get your sensors up and running again, then flash MIUI 10 and upgrade to MIUI 11 using system updater app.
Click to expand...
Click to collapse
DragonSlayer7# said:
This persist.img thing might work for you or might not.
The full proof way is to reinstall Pixel Experience (Android 10) so that you get your sensors up and running again, then flash MIUI 10 and upgrade to MIUI 11 using system updater app.
Click to expand...
Click to collapse
should i flash MIUI 10 using custom recovery or fastboot after reinstalling Pixel Experience ?
Azhar001 said:
should i flash MIUI 10 using custom recovery or fastboot after reinstalling Pixel Experience ?
Click to expand...
Click to collapse
Fastboot ROM using MIFlashTool
DragonSlayer7# said:
Fastboot ROM using MIFlashTool
Click to expand...
Click to collapse
okay, i willl let you know if it works
I think you should try reflashing the stock firmware using the Mi Flash and select wipe data option.
Sent from my Redmi Note 7 Pro using Tapatalk
DragonSlayer7# said:
Fastboot ROM using MIFlashTool
Click to expand...
Click to collapse
I got all the sensors back again, everything working fine.
Here is what is did (using PC):
1) i installed Pixek Experience ROM (Android 10) using ADB Fastboot method.
Pros: Every sensors started to work, back to normal.
Cons: None i noticed.
2) Then i turn off the phone and entered into fastboot mode
3) I flashed MIUI 10 fastboot ROM using MIFlash Tool. Though i didn't get the "Success" message on MIFlash Tool but phone booted itself (did show MIUI 10 during boot up, and Set Up screen was appearing) so i assumed flashing was complete. Then i unplugged phone from USB cable.
After setup,
Pros: Every sensors was working perfectly fine.
Cons: None i noticed.
4) i updated from MIUI 10 to MIUI 11 using System update on phone. Now i am on MIUI 11 and everything works FINE!!
So what i found is there is some problem with MIUI 11 fastboot ROM itself. Directly flashing MIUI 11 fastboot ROM is the reason sensors stops working!!
Azhar001 said:
I got all the sensors back again, everything working fine.
Here is what is did (using PC):
1) i installed Pixek Experience ROM (Android 10) using ADB Fastboot method.
Pros: Every sensors started to work, back to normal.
Cons: None i noticed.
2) Then i turn off the phone and entered into fastboot mode
3) I flashed MIUI 10 fastboot ROM using MIFlash Tool. Though i didn't get the "Success" message on MIFlash Tool but phone booted itself (did show MIUI 10 during boot up, and Set Up screen was appearing) so i assumed flashing was complete. Then i unplugged phone from USB cable.
After setup,
Pros: Every sensors was working perfectly fine.
Cons: None i noticed.
4) i updated from MIUI 10 to MIUI 11 using System update on phone. Now i am on MIUI 11 and everything works FINE!!
So what i found is there is some problem with MIUI 11 fastboot ROM itself. Directly flashing MIUI 11 fastboot ROM is the reason sensors stops working!!
Click to expand...
Click to collapse
Yes, its kernel problem. It happens if you are flashing MIUI 11 based on Android Pie from any AOSP based ROM running Android 10.
Does any one know how to root POCO X2 running on MIUI 12 ?
I tried each and every method which worked on MIUI 11 but always ended up in bootloop
Plz help......
KartikBapna said:
Does any one know how to root POCO X2 running on MIUI 12 ?
I tried each and every method which worked on MIUI 11 but always ended up in bootloop
Plz help......
Click to expand...
Click to collapse
I successfully rooted the EU miui 12 rom earlier and there wasn't any bootloop.
KartikBapna said:
Does any one know how to root POCO X2 running on MIUI 12 ?
I tried each and every method which worked on MIUI 11 but always ended up in bootloop
Plz help......
Click to expand...
Click to collapse
Be careful brother, there are no fastboot images of MIUI 12. If you end up bricking it, you'll have to wait 1 whole month for "miui 12 fastboot imgs" to arrive.
tuskan_supa said:
I successfully rooted the EU miui 12 rom earlier and there wasn't any bootloop.
Click to expand...
Click to collapse
superminnu said:
Be careful brother, there are no fastboot images of MIUI 12. If you end up bricking it, you'll have to wait 1 whole month for "miui 12 fastboot imgs" to arrive.
Click to expand...
Click to collapse
How did you did it ?
You did it on POCO X2 ?
And also do you know how to disable Dm-Verity to write in system partition ?
KartikBapna said:
How did you did it ?
You did it on POCO X2 ?
And also do you know how to disable Dm-Verity to write in system partition ?
Click to expand...
Click to collapse
Are you on the Indian build or EU build?
tuskan_supa said:
Are you on the Indian build or EU build?
Click to expand...
Click to collapse
Indian
KartikBapna said:
Indian
Click to expand...
Click to collapse
I did successfully on the EU build not on Indian. I guess you should wait few days maybe someone will try and figure it out.
KartikBapna said:
How did you did it ?
You did it on POCO X2 ?
And also do you know how to disable Dm-Verity to write in system partition ?
Click to expand...
Click to collapse
Isn't flash Magisk will always disable dm-verity?
Never_Sm1le said:
Isn't flash Magisk will always disable dm-verity?
Click to expand...
Click to collapse
It didn't disable it in my POCO....
KartikBapna said:
It didn't disable it in my POCO....
Click to expand...
Click to collapse
And now I realize the problem in you answer. Why did you need to write into the system partition?
Never_Sm1le said:
And now I realize the problem in you answer. Why did you need to write into the system partition?
Click to expand...
Click to collapse
What is the advantage of root access if you can only read partitions not write them
And also, I want to install and uninstall apps in system partition.
KartikBapna said:
What is the advantage of root access if you can only read partitions not write them
And also, I want to install and uninstall apps in system partition.
Click to expand...
Click to collapse
You can't, because since Android 10 Google made the /system partition read-only. You can use adb to disable those app, uninstall apps in /system does not help you gain any free space anyway.
Never_Sm1le said:
You can't, because since Android 10 Google made the /system partition read-only. You can use adb to disable those app, uninstall apps in /system does not help you gain any free space anyway.
Click to expand...
Click to collapse
I don't want any free space just want to remove bloatware and install some apps in system like appninja's app
KartikBapna said:
I don't want any free space just want to remove bloatware and install some apps in system so like appninja's app
Click to expand...
Click to collapse
you can remove bloat with adb command, and install app in system using app systemizer. Install things in /system is old-school
Never_Sm1le said:
you can remove bloat with adb command, and install app in system using app systemizer. Install things in /system is old-school
Click to expand...
Click to collapse
Can't install apps with systemizer because app always crashes after moving to system.
Root is used for many things like running modules so my problem is still there how to root Poco X2 running on MIUI 12
Also systemizer is a module which requires root as well as magisk
KartikBapna said:
Can't install apps with systemizer because app always crashes after moving to system.
Root is used for many things like running modules so my problem is still there how to root Poco X2 running on MIUI 12
Also systemizer is a module which requires root as well as magisk
Click to expand...
Click to collapse
Do as usual? Or there's a different thing involved? On my redmi K30 MIUI 12, things is as simple as unlock bootloader, boot the recovery, do not swipe modify system then flash the recovery, reboot to recovery then flash magisk. I have never encounter dm-verity before when follow these steps.
Never_Sm1le said:
Do as usual? Or there's a different thing involved? On my redmi K30 MIUI 12, things is as simple as unlock bootloader, boot the recovery, do not swipe modify system then flash the recovery, reboot to recovery then flash magisk. I have never encounter dm-verity before when follow these steps.
Click to expand...
Click to collapse
Things I have tried after unlocking bootloader and then flashing the recovery
1) flash magisk zip result bootloop
2) flash patched boot.img result bootloop
3) flash patched recovery.img result bootloop
In MIUI 11 method 2 worked
Method 1 always gave bootloop
KartikBapna said:
Things I have tried after unlocking bootloader and then flashing the recovery
1) flash magisk zip result bootloop
2) flash patched boot.img result bootloop
3) flash patched recovery.img result bootloop
In MIUI 11 method 2 worked
Method 1 always gave bootloop
Click to expand...
Click to collapse
Did you use fastboot flash twrp.img or fastboot boot twrp.img?
Never_Sm1le said:
Did you use fastboot flash twrp.img or fastboot boot twrp.img?
Click to expand...
Click to collapse
I flashed twrp that means I used
fastboot flash recovery twrp.img
And then to boot
fastboot boot twrp.img
I flashed patched boot.img from twrp.
My phone boots up with twrp flashed.
KartikBapna said:
I flashed twrp that means I used
fastboot flash recovery twrp.img
And then to boot
fastboot boot twrp.img
I flashed patched boot.img from twrp.
My phone boots up with twrp flashed.
Click to expand...
Click to collapse
Try my way: boot TWRP then flash TWRP.img from TWRP. Reboot to recovery again then flash Magisk zip. Flash patched boot.img is unnecessary, like Topjohnwu said it's only for devices without TWRP. Beside if you want to use the patched method, you must patch the stock recovery image not TWRP.
I hope you already know how to flash GSI on devices with dyamic partition already. If not then you can follow this guide: https://forum.xda-developers.com/t/...ynamic-super-partition.4256667/#post-85271987
If youre on stock before flashing GSI then dont "fastboot delete-logical-partition product" like other tutorials may suggest. Just flash the product image (fastboot flash product [insert img here]) attached below and it will get resized automatically as well, giving you plenty of space to flash your GSI.
If youve already flashed GSI before following this guide and have done "fastboot delete-logical-partition product" then just create product partition (fastboot create-logical-partition product [size]) and flash the img on product.
whichever course youve taken you can now flash magisk through twrp or patch the boot img and flash that.
Please note that this product image wasnt made by me and the credit for it goes to: @Allexwin50
tested on infinix zero 8 X687
Thanks for the tutorial, I will give it a try but have one question: you said to" create product partition and give size " I don't understand about size!
shjeanpy said:
Thanks for the tutorial, I will give it a try but have one question: you said to" create product partition and give size " I don't understand about size!
Click to expand...
Click to collapse
when you create partition you also need to specify its size, just add some number
kusti420 said:
when you create partition you also need to specify its size, just add some number
Click to expand...
Click to collapse
What size would you advise me please
shjeanpy said:
What size would you advise me please
Click to expand...
Click to collapse
idk, i used 400000000
Thank you very much for your great tutorial. it worked for me on my device.
Thanks a lot for putting this together. I was stuck for a day and a half trying to figure out how to flash Magisk with no product partition. Great work.
nickelnine said:
Thanks a lot for putting this together. I was stuck for a day and a half trying to figure out how to flash Magisk with no product partition. Great work.
Click to expand...
Click to collapse
and i was stuck for multiple months...
@kusti420 if I've flashed a GSI on to stock (apart from flashing vbmeta and TWRP) can I fastboot flash that product.img and then successfully TWRP flash magisk or patch with app (using Phh SU temporarily for root) ? is that enough ?
EDIT 1: thought I'd just see for myself, flashed the product_gsi.img and my phone (S20FE 5G) still booted. tried flashing magisk 21.4 zip from TWRP and got a bootloop. will check later if I can patch my boot.img and post.
Hey, where did you take this product_gsi.img? I think it does not work with Android 12, I wonder if it can be updated or something like that.
felipecassiors said:
Hey, where did you take this product_gsi.img? I think it does not work with Android 12, I wonder if it can be updated or something like that.
Click to expand...
Click to collapse
it was sent to me in telegram, where i also traced it back to @Allexwin50, afaik he made it. worked fine on android 10 and 11. asking him for img for a12 could be an option
Sir, When I Flashed any GSI rom A11 , any way to remove the standard superuser root from rom ? if some solution , please advise me , (my device use fastboot commands not use twrp)
gamal001 said:
Sir, When I Flashed any GSI rom A11 , any way to remove the standard superuser root from rom ? if some solution , please advise me , (my device use fastboot commands not use twrp)
Click to expand...
Click to collapse
idk wtf u mean by "standard superuser root" prolly phh su, if yes then there is definetly a way to get rid of that
Right, so what to do after installing the GSI like this. How to install Magisk? I don't have TWRP. Do I have to "securize" first? Help.
K1569GHENT said:
Right, so what to do after installing the GSI like this. How to install Magisk? I don't have TWRP. Do I have to "securize" first? Help.
Click to expand...
Click to collapse
maybe, cant remember by heart, dont have enough time to test it out myself
Working on Nippon Android Tiramisu SGSI on Pixel 3a, very nice
K1569GHENT said:
Right, so what to do after installing the GSI like this. How to install Magisk? I don't have TWRP. Do I have to "securize" first? Help.
Click to expand...
Click to collapse
Obtain a stock copy of your boot.img.
Patch it through the magisk app before you do your whole thing installing your chosen gsi.
Once you have the patched image, you can fastboot it using fastboot flash boot boot.img in cmd onto your gsi ROM.
Make sure to install the boot.img to both slots A and B. Then go back to your active slot.
ninjasinabag said:
Obtain a stock copy of your boot.img.
Patch it through the magisk app before you do your whole thing installing your chosen gsi.
Once you have the patched image, you can fastboot it using fastboot flash boot boot.img in cmd onto your gsi ROM.
Make sure to install the boot.img to both slots A and B. Then go back to your active slot.
Click to expand...
Click to collapse
he talked about removing phh-superuser
kusti420 said:
he talked about removing phh-superuser
Click to expand...
Click to collapse
It's locked to your boot image, so using 100% stock image removes superuser since it's no longer system as root.
kusti420 said:
I hope you already know how to flash GSI on devices with dyamic partition already. If not then you can follow this guide: https://forum.xda-developers.com/t/...ynamic-super-partition.4256667/#post-85271987
If youre on stock before flashing GSI then dont "fastboot delete-logical-partition product" like other tutorials may suggest. Just flash the product image (fastboot flash product [insert img here]) attached below and it will get resized automatically as well, giving you plenty of space to flash your GSI.
If youve already flashed GSI before following this guide and have done "fastboot delete-logical-partition product" then just create product partition (fastboot create-logical-partition product [size]) and flash the img on product.
whichever course youve taken you can now flash magisk through twrp or patch the boot img and flash that.
Please note that this product image wasnt made by me and the credit for it goes to: @Allexwin50
Click to expand...
Click to collapse
Hello kusti420
I had already deleted the product partition when I found your post.
The GSI was not cool.
I reflash the product partition and reflash the GSI, now it's good.
Thanks for the file and the tip.
Hello Guys,
I see that there's no section for red magic 7s Pro, anyway, I need to know before to buy:
1- do you guys face overheating issues ? does the fan really cools ?
2- is there bugs and glitches and bootloop for no reason (like previous series) ?
I have the 7s pro:
1. 3dmark "Wild life stress test" 97,9% stability....
2. I had the same worries, but haven't had any issues restoring my backup from Google or any major bugs, turning on/off VoLTE you need to choose max 4G not 5G to see the button.
I have had it for a week now, it's my daily driver....
freddykr said:
I have the 7s pro:
1. 3dmark "Wild life stress test" 97,9% stability....
2. I had the same worries, but haven't had any issues restoring my backup from Google or any major bugs, turning on/off VoLTE you need to choose max 4G not 5G to see the button.
I have had it for a week now, it's my daily driver....
Click to expand...
Click to collapse
amazing, nice to hear that,
what about the weight ? does it feel confortable in the hand ?
It's a heavy phone, but I have always had kinda heavy phones
does anyone have the stock rom? I am looking for it to be able to root it
cams93 said:
does anyone have the stock rom? I am looking for it to be able to root it
Click to expand...
Click to collapse
I root my red magic 7s pro global v4.11.
How did you root it, and where did you get the global ROM? Ithe one that is installed with me is NX709S_UNCommon_V3.11
cams93 said:
How did you root it, and where did you get the global ROM? Ithe one that is installed with me is NX709S_UNCommon_V3.11
Click to expand...
Click to collapse
I'm don't have full rom I get boot.img from same phone
Ahh makes sense, can you share how you got the boot.img? I tried using fastboot but had no lock. So far I just have the bootloader unlocked.
cams93 said:
Ahh makes sense, can you share how you got the boot.img? I tried using fastboot but had no lock. So far I just have the bootloader unlocked.
Click to expand...
Click to collapse
First you need unlock bootloader.
And you need take any boot.img is rooted for any nubia phone.
You have to check what solt are you use
A or B.
Go fastboot
Cmd..
(Fastboot flash boot_a .....img)
Be careful if you do something wrong, it will destroy your device
Only change one solt A or B not both.
(fastboot reboot)
Now your device is rooted but not same original boot.img
Go termex application right
Su
Give him root permissions right again
(cd /dev/block/by-name)
cp boot_a /sdcard
Or
cp boot_a /sdcard
Now you will see your boot in your phone storage send in your laptop or computer.
Now do again fastboot to return the original boot.img without any issues in the device.
Great
iibr.n said:
First you need unlock bootloader.
And you need take any boot.img is rooted for any nubia phone.
You have to check what solt are you use
A or B.
Go fastboot
Cmd..
(Fastboot flash boot_a .....img)
Be careful if you do something wrong, it will destroy your device
Only change one solt A or B not both.
(fastboot reboot)
Now your device is rooted but not same original boot.img
Go termex application right
Su
Give him root permissions right again
(cd /dev/block/by-name)
cp boot_a /sdcard
Or
cp boot_a /sdcard
Now you will see your boot in your phone storage send in your laptop or computer.
Now do again fastboot to return the original boot.img without any issues in the device.
Click to expand...
Click to collapse
Great thanks, one last question do I pick any partition boot_a or boot_b or does it has to be a particular one?
If I pick boot_b then I need to copy the boot.img from boot_a?
Do both a and b partitions have the stock boot.img? That way as long as I don't flash both of them I am safe?
cams93 said:
Great
Great thanks, one last question do I pick any partition boot_a or boot_b or does it has to be a particular one?
If I pick boot_b then I need to copy the boot.img from boot_a?
Do both a and b partitions have the stock boot.img? That way as long as I don't flash both of them I am safe?
Click to expand...
Click to collapse
My active partition was boot_a I flashed into boot_b then set the b partition as my current one but after rebooting I got black screen.
I set as active partition a (the original one) and I can use my phone again.
Am I doing something wrong I used a magisk patched boot.img from Nubia 7Pro.
Which one did you use?
I
cams93 said:
Great
Great thanks, one last question do I pick any partition boot_a or boot_b or does it has to be a particular one?
If I pick boot_b then I need to copy the boot.img from boot_a?
Do both a and b partitions have the stock boot.img? That way as long as I don't flash both of them I am safe?
Click to expand...
Click to collapse
You need backup both because maybe you do wrong or something.
iibr.n said:
I
You need backup both because maybe you do wrong or something.
Click to expand...
Click to collapse
How do I backup both without root?
I
cams93 said:
Great
Great thanks, one last question do I pick any partition boot_a or boot_b or does it has to be a particular one?
If I pick boot_b then I need to copy the boot.img from boot_a?
Do both a and b partitions have the stock boot.img? That way as long as I don't flash both of them I am safe?
Click to expand...
Click to collapse
You need backup both because maybe you do wrong or something
cams93 said:
My active partition was boot_a I flashed into boot_b then set the b partition as my current one but after rebooting I got black screen.
I set as active partition a (the original one) and I can use my phone again.
Am I doing something wrong I used a magisk patched boot.img from Nubia 7Pro.
Which one did you use?
Click to expand...
Click to collapse
You did something wrong, I told you to be careful
Contact me in telegram please IbrAlnaqbi
abdouyakuzataleb said:
Hello Guys,
I see that there's no section for red magic 7s Pro, anyway, I need to know before to buy:
1- do you guys face overheating issues ? does the fan really cools ?
2- is there bugs and glitches and bootloop for no reason (like previous series) ?
Click to expand...
Click to collapse
I have no issue at all i upgraded from 5G to 7s pro. Only issue i have is the function in the game launcher menu but that's is going to get fixed next patch