Hi there
I just uninstalled xposed but my huawei themes' still not working. I can download them and apply them but nothing changes.
Is there a way to enable it again?
Thanks
@muradulislam Have you rebooted the device? And did you use official Xposed Uninstaller?
DigiGoon said:
@muradulislam Have you rebooted the device? And did you use official Xposed Uninstaller?
Click to expand...
Click to collapse
Yes on both accounts. Rebooted many times over
muradulislam said:
Yes on both accounts. Rebooted many times over
Click to expand...
Click to collapse
@m_esser is right, I forgot the step of changing
the ro.config.hwtheme=1
Sent from my Huawei Honor 7
I assume that a factory reset will not solve the problem because this step does not touch the files that have to be changed.
In order to reactivate the theme engine you have to change two files:
/system/build.prop
/system/emui/base/prop/local.prop
In both files the following entries have to be changed:
ro.config.hwtheme <- change from 0 to 1
ro.config.hw_theme <- change from 0 to 1
Please ensure that you will keep the file related access rights when editing the files. Needless to say that you device need to be rooted.
After rebooting the device the theme engine should be working again.
Best regards
m_esser
m_esser said:
I assume that a factory reset will not solve the problem because this step does not touch the files that have to be changed.
In order to reactivate the theme engine you have to change two files:
/system/build.prop
/system/emui/base/prop/local.prop
In both files the following entries have to be changed:
ro.config.hwtheme <- change from 0 to 1
ro.config.hw_theme <- change from 0 to 1
Please ensure that you will keep the file related access rights when editing the files. Needless to say that you device need to be rooted.
After rebooting the device the theme engine should be working again.
Best regards
m_esser
Click to expand...
Click to collapse
build.prop doesn't have any entry of ro.config.hwtheme, changing it in local.prop will do, and its ro.config.hwtheme only, not ro.config.hw_theme.
Sent from my Huawei Honor 7
m_esser said:
I assume that a factory reset will not solve the problem because this step does not touch the files that have to be changed.
In order to reactivate the theme engine you have to change two files:
/system/build.prop
/system/emui/base/prop/local.prop
In both files the following entries have to be changed:
ro.config.hwtheme <- change from 0 to 1
ro.config.hw_theme <- change from 0 to 1
Please ensure that you will keep the file related access rights when editing the files. Needless to say that you device need to be rooted.
After rebooting the device the theme engine should be working again.
Best regards
m_esser
Click to expand...
Click to collapse
DigiGoon said:
build.prop doesn't have any entry of ro.config.hwtheme, changing it in local.prop will do, and its ro.config.hwtheme only, not ro.config.hw_theme.
Click to expand...
Click to collapse
Thanks for the suggestions and your valuable time
It's already set to
ro.config.hwtheme=1
In local.prop but still the same issue
Inserted one by myself in build.prop. still nothing
muradulislam said:
Thanks for the suggestions and your valuable time
It's already set to
ro.config.hwtheme=1
In local.prop but still the same issue
Inserted one by myself in build.prop. still nothing
Click to expand...
Click to collapse
Device reads build.prop first then local.prop, it doesn't make any difference if you put two entries. And you used official Xposed Uninstaller no?
Sent from my Huawei Honor 7
DigiGoon said:
Device reads build.prop first then local.prop, it doesn't make any difference if you put two entries. And you used official Xposed Uninstaller no?
Click to expand...
Click to collapse
I have official Xposed Uninstaller now but I installed, uninstalled multiple times, may be one of those times it was not, I strongly suspect so.
Anyway to salvage this situation now?
I am even ready to force install B370 again if it comes to that coz I love themes.
By the way, for educational purposes, Can I do a 3-btn forced install of B370 over a B370?
muradulislam said:
I am even ready to force install B370 again if it comes to that coz I love themes.
By the way, for educational purposes, Can I do a 3-btn forced install of B370 over a B370?
Click to expand...
Click to collapse
Okay now if you are willing to do that here are the steps on how to do it properly.
If your device isn't rooted then directly do the 3-button forced install by placing UPDATE.APP in dload folder in root of your external sdcard.
If it is rooted then first unroot it and do the following.
Boot into bootloader mode ([Volume Down] + [Tap on Power Button]).
If you know how to extract img files from UPDATE.APP do that first and extract these files: (boot.img), (system.img), (recovery.img), (cust.img).
Then from bootloader mode flash them by executing these commands:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
Then reboot your device by firing this command:
Code:
fastboot reboot
After it boots up place B370's UPDATE.APP in dload folder in external sdcard.
Power-Off your device, and do the 3-button press to flash B370 properly.
DigiGoon said:
Okay now if you are willing to do that here are the steps on how to do it properly.
If your device isn't rooted then directly do the 3-button forced install by placing UPDATE.APP in dload folder in root of your external sdcard.
If it is rooted then first unroot it and do the following.
Boot into bootloader mode ([Volume Down] + [Tap on Power Button]).
If you know how to extract img files from UPDATE.APP do that first and extract these files: (boot.img), (system.img), (recovery.img), (cust.img).
Then from bootloader mode flash them by executing these commands:
Then reboot your device by firing this command:
After it boots up place B370's UPDATE.APP in dload folder in external sdcard.
Power-Off your device, and do the 3-button press to flash B370 properly.
Click to expand...
Click to collapse
Thanks for the info. Will definitely do that. One more thing, will I retain my apps and files etc? As I am not flashing data.img so I guess, I should.
muradulislam said:
Thanks for the info. Will definitely do that. One more thing, will I retain my apps and files etc? As I am not flashing data.img so I guess, I should.
Click to expand...
Click to collapse
Yes, I think so, but it never hurts to take a backup, so I recommend you to take a backup first.
Sent from my Huawei Honor 7
DigiGoon said:
Yes, I think so, but it never hurts to take a backup, so I recommend you to take a backup first.
Click to expand...
Click to collapse
It seems that all my apps and data were wiped out after updating through this method but good thing, I kept a backup
Thanks for your help.
muradulislam said:
It seems that all my apps and data were wiped out after updating through this method but good thing, I kept a backup
Thanks for your help.
Click to expand...
Click to collapse
I'm glad your problem is solved now. And yes always keep a backup in case things get sideways.
DigiGoon said:
Okay now if you are willing to do that here are the steps on how to do it properly.
If your device isn't rooted then directly do the 3-button forced install by placing UPDATE.APP in dload folder in root of your external sdcard.
If it is rooted then first unroot it and do the following.
Boot into bootloader mode ([Volume Down] + [Tap on Power Button]).
If you know how to extract img files from UPDATE.APP do that first and extract these files: (boot.img), (system.img), (recovery.img), (cust.img).
Then from bootloader mode flash them by executing these commands:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
Then reboot your device by firing this command:
Code:
fastboot reboot
After it boots up place B370's UPDATE.APP in dload folder in external sdcard.
Power-Off your device, and do the 3-button press to flash B370 properly.
Click to expand...
Click to collapse
Hi ..
I am having the same issue in P9 Plus , can i follow the same method to try ?
thanks
leofungwai said:
.
Hi ..
I am having the same issue in P9 Plus , can i follow the same method to try ?
thanks
Click to expand...
Click to collapse
Yep, for sure... Use your phone's firmware and everything is good to go.
Sent from my PLK-L01 using XDA Labs
DigiGoon said:
Okay now if you are willing to do that here are the steps on how to do it properly.
If your device isn't rooted then directly do the 3-button forced install by placing UPDATE.APP in dload folder in root of your external sdcard.
If it is rooted then first unroot it and do the following.
Boot into bootloader mode ([Volume Down] + [Tap on Power Button]).
If you know how to extract img files from UPDATE.APP do that first and extract these files: (boot.img), (system.img), (recovery.img), (cust.img).
Then from bootloader mode flash them by executing these commands:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
Then reboot your device by firing this command:
Code:
fastboot reboot
After it boots up place B370's UPDATE.APP in dload folder in external sdcard.
Power-Off your device, and do the 3-button press to flash B370 properly.
Click to expand...
Click to collapse
muradulislam said:
Yep, for sure... Use your phone's firmware and everything is good to go.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
not working ... it still nothing change after i appl the theme
leofungwai said:
Then reboot your device by firing this command:
After it boots up place B370's UPDATE.APP in dload folder in external sdcard.
Power-Off your device, and do the 3-button press to flash B370 properly.
not working ... it still nothing change after i appl the theme
Click to expand...
Click to collapse
It worked for me, you have some other problem. You already quoted DigiGoon, he will come along soon and troubleshoot it.
Sent from my PLK-L01 using XDA Labs
Hi everyone.
In case someone needs a solution to the theme engine problem, there is another threat: "[Solved] Can't Apply Themes after downloaded" by user somboons. Works like a charm.
http://forum.xda-developers.com/mate-8/general/solve-apply-themes-downloaded-t3318265
---------- Post added at 05:55 PM ---------- Previous post was at 05:49 PM ----------
somboons said:
Hi all
I want to share how to apply themes after downloaded.Anyone who unlock bootloader + rooted, then can't apply themes from themes manager, please following step by step below.
1. Download hw_init.zip > https://www.androidfilehost.com/?fid=24421527759882525
2. Unzip hw_init.zip
3. Copy folder hw_init to /data
4. Reboot
5. Apply themes
6. Enjoy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Thanks to somboons!
Related
Support to issues will no longer be considered as i don't own the device now
thread will be closed as soon as moderators respond to my request of removal of this thread
WARNING: this method of rooting voids your phone's warranty
because you can flash system as usual and as it used to be, so don't worry
root with your own risk
this method works for WW SKU(i don't know about other SKU images but you can always give a try if you are on other SKU)
here am posting two methods of rooting
whatever the method it is , all we need is our zenfone 5 to be rooted. right??
one is root process by shakalaca and you can find his post here(use google translate in his page)(you can find the english translated here in the end of this post)
the second process is here as i posted below
make sure you have adb n fastboot drivers, intel mobile usb drivers, asus usb drivers
usb debugging must be turned on(settings-->developer options)
to get developer options goto settings-->about-->build number(tap on it 7times) now go back n u will find developers options
first of all download the bootloader.zip attached below
download SuperSU flashable zip attached below and place this UPDATE-SuperSU-v2.02.zip file into your internal storage(lets flash it later why so hurry?)
extract the bootloader.zip and place the extracted files in your adb or fastboot folder(or simply place them in c:\users\xxx )
turn on the usb debugging option(settings-->developer options-->usb debugging)
connect your zenfone 5 to your windows pc
open command prompt on your computer and run these following commands
adb devices(you will see your device serial number)
adb reboot-bootloader(now your device will boot(startup) in droidboot menu
fastboot flash dnx dnx_fwr_ctp_a500cg.bin
fastboot flash ifwi ifwi_ctp_a500cg_unlock.bin
now your bootloader is unlocked so that we can flash custom recovery
best part: it is unofficial bootloader unlocking and when you update the next firmware via OTA the bootloader relocks by itself(yep you will receive OTA updates even after this)
my bootloader relocked after OTA update ofV2.19.40.18 n it relocked my bootloader
now i hope u unlocked your bootloader
download this recovery recovery_philz_t00f.tar(attached below)
extract it and you wil find the recovery_philz_t00f.img file
place that recovery in your fastboot folder and run these following commands
fastboot reboot-bootloader
fastboot devices (just to make sure your device is connected)
fastboot flash recovery recovery_philz_t00f.img
give it time to write the recovery( takes 3-4 seconds)
now that you have philz recovery
now run this command
fastboot reboot-bootloader
now your Zenfone reboots to bootloader menu and select recovery option by scrolling down(use volume-) and select( use power button)
u can disconnect your device now and u are in recovery
the recovery is a little bit laggy but works fine
select the option install zip from sd card
select the UPDATE-SuperSU-v2.02.zip file that u placed in your internal storage earlier
now you have options to say yes or no.. select yes and let the recovery flash SuperSU
I hope u have flashed successfully
now opt for reboot system now
guess what your ZenFone is rooted Buddy
check it using any root checker app or install any root related app or you can check that SuperSU is working without any error
screenshots????
well attached below for proof
Want to relock the bootloader??
i suggest you not to relock the bootloader coz the OTA update relocks the bootloader automatically
still want to relock bootloader?
read below posts before relocking the bootloader because some members faced problems
here you go
refer to this link
http://www.asuszenfoneblog.com/2014/09/how-to-relock-bootloader-on-asus-zenfone.html
Stuck at USB logo????
WELCOME BACK
here is the solution:
flash this modified stock recovery https://www.dropbox.com/s/xvauuk0tzid1o3i/1.18.40.9_ww_recovery.img?dl=0 in droidboot menu
fastboot flash recovery <filename>.img (filename can be anything or the name of recovery you downloaded from above)
download the last JB update package V1.18.40.10
now goto recovery n wipe data/cache
then sideload the JB update package V1.18.40.10(how to sideload????? explained below)
it will work for sure
after updating wipe data n cache again
now reboot system n go through initial setup n everything will be fine
well you will be on JB now but if you want Kitkat then sideload the Kitkat update package
and follow the root process from the beginning
finally i suggest you not to relock the bootloader because when you sideload the update it will relock the bootloader)
OTA updates are available after rooting by this process
yes OTA updates are still available(even if the bootloader is unlocked)
image attached below to show ota update
i got OTA update of 2.19.40.18_20141003_8008 release-keys and downloaded it n updated successfully without any issues
if you can't find OTA update from your ZenFone 5 then download the update package from asus website
whenever you get OTA update check for ASUS website and download the package from there
here is the link to asus website for downloading future updates http://www.asus.com/in/Tablets_Mobile/ZenFone_5_A500CG/HelpDesk_Download/
there just click on select OS and select android and then you will find the update packages
after downloading the package extract it and u will fing another zip of name like UL-ASUS_T00F-WW-2.19.XX.X-user.zip
place that .zip file in your internal storage and the system detects it as update file and notifies you whether to update
if it fails then sideload the update via ADB
applying OTA updates via adb
Just download the package from the ASUS website stated above(click on the link)
place the package UL-ASUS_T00F-WW-2.19.XX.X-user.zip to your adb or fastboot folder
now enter into droidboot menu(power off your phone and hold power button+volume up till you see droidboot menu) of your Zenfone 5 and connect it to your PC
now scroll down(use volume keys) to recovery and select it(use power key) and your phone will boot to recovery
now that you are in recovery(you can see a droid symbol lying down with red triangle over its stomach)
press n keep holding volume down button, press volume up button(press vol+ button while still vol- button holding)
now you will see recovery commands
scroll to apply update from ADB
now open the command prompt on your PC and type this following command
adb sideload UL-ASUS_T00F-WW-2.19.XX.X-user.zip
now wait for the process to complete till 100%
now the system update starts and HURRAY you just updated the firmware successfully
(if you have installed xposed framework or Lucky Patcher then you have to follow these steps before updating 2.19.40.18_20141003_8008 release-keys)
for those who have xposed installed on Zenfone 5 the latest update will fail
but here is the solution for that
open the .zip package of firmware you have present on your Zenfone 5
for example the UL-ASUS_T00F-ww-V2.19.40.6-user.zip
open it using winrar and navigate to system/framework
find the files core.odex
core.jar
services.jar
services.odex
drag them out on your desktop
now copy them into your internal storage
now use a file manager like ROOT EXPLORER and navigate to /system/framework
delete the core.odex
core.jar
services.jar
services.odex files because these are patched by xposed framework and wont let the system to update
now after deleting the patched files
move the files
core.odex
core.jar
services.jar
services.odex files you dragged from zip package and pasted in your internal storage to the folder/system/framework and change the permission to like this rw-r--r--
image attached below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
for all the four file(now you restored all the system actual files)
now update it using OTA or by ADB SIDELOAD it wont give you any error
i did this and i updated sucessfully
you will lose root access for the first boot but dont worry
reboot your device again and you will get back the root access
happy updating
root process by shakalaca
enable USB DEBUGGING in settings-->developer options
now download this package root by shakalaca and open in your windows pc
extract it and connect your Zenfone to pc in normal mode
do not remove or unplug your zenfone during this process
now double the root-zenfone-5-ww.bat(select tw if your SKU is TW or CHT if its CHT SKU)
follow instructions
now sit back and relax
dont panic during this process your zenfone reboots many times(like 6 times i guess)
and when it says finished just look out for SuperSU in your App Drawer
and yes you are rooted
sorry for grammatical errors(if any)
After done this.. have u done relock bootloader?
Do u think we still can get/do ota/sideload update whenever available later?
Updates:
Well good to know u've removed step to use official Asus apk to unlock bootloader in ur guide. So my reply posted in this thread r no longer relevant bcoz all of it regarding question on that official apk. Glad u finally accept my suggestion not to use that apk since we can unlock bootloader via adb (unofficially), & most important it is safer for our device (by not sending any device id such as imei etc to Asus) :good::good::good:
yeah, have you ever tried to relock your zenfone 5? using that app too? or another app?
Nice! Finally updated rooting method for Zenfone 5 (KitKat). Thanks for sharing.
Sent from my ASUS_T00J using XDA Free mobile app
vnzdeath said:
yeah, have you ever tried to relock your zenfone 5? using that app too? or another app?
Click to expand...
Click to collapse
yep i tried relocking
i even got ota update of V2.18.9.40.18
screenshot attached below
remove .zip extension and rename it to .jpg extension
Enjoy
bbadilla11 said:
Nice! Finally updated rooting method for Zenfone 5 (KitKat). Thanks for sharing.
Sent from my ASUS_T00J using XDA Free mobile app
Click to expand...
Click to collapse
hit thanks button if it helped you in rooting
enjoy being rooted
:good: :good: :good:
yeah here you go
k0m3n9 said:
After done this.. have u done relock bootloader?
Do u think we still can get/do ota/sideload update whenever available later?
Click to expand...
Click to collapse
vnzdeath said:
yeah, have you ever tried to relock your zenfone 5? using that app too? or another app?
Click to expand...
Click to collapse
read the first post
Does it need to be online?
Guys.. when ya run UnLock_A500CG_a500cg_platform_rel.apk, does it require u to be online? Have someone check what it can access that mentioned during waiting u to proceed with installation.
k0m3n9 said:
Guys.. when ya run UnLock_A500CG_a500cg_platform_rel.apk, does it require u to be online? Have someone check what it can access that mentioned during waiting u to proceed with installation.
Click to expand...
Click to collapse
yes you need to be online at least at the last stage of UnLock_A500CG_a500cg_platform_rel.apk where you see the unlock button in the last step of unlocking bootloader
don't worry about wifi issues or data issues because it wont give you any wifi issues or data issues after unlocking bootloader
How about putting the original black asus boot logo? is there a way for that?
cgren said:
How about putting the original black asus boot logo? is there a way for that?
Click to expand...
Click to collapse
i don't know how to bring back that logo on boot
sorry
How to re-lock bootloader??
Sent from my ASUS_T00J using XDA Free mobile app
RajGopi said:
i don't know how to bring back that logo on boot
sorry
Click to expand...
Click to collapse
Even if i flash with Stock Firmware will i get white asus boot?
---------- Post added at 04:21 AM ---------- Previous post was at 03:45 AM ----------
I just flashed with stock KK everything went back to normal.... boot is black again hehe.
Where did u get the stock Kitkat?
Sent from my ASUS_T00J using XDA Free mobile app
to relock the bootloader
Extract the recovery.img,fastboot.img and boot.img from the update package and flash them using fastboot commands
it ensures that all system files are flashed back before relocking the bootloader
if you done all above then refer to this link
http://www.asuszenfoneblog.com/2014/09/how-to-relock-bootloader-on-asus-zenfone.html
or here it is
drag out the ifwi.zip file from the update package like UL-ASUS_T00F-WW-2.19.40.10-user.zip
from the ifwi.zip file drag dnx_fwr_ctp_a500cg.bin and drag out ifwi_ctp_a500cg.bin
then open your command prompt and run the following commands
fastboot flash dnx dnx_fwr_ctp_a500cg.bin
fastboot flash ifwi ifwi_ctp_a500cg.bin
fastboot reboot-bootloader
It relocks your bootloader
Sent from my ASUS_T00J using XDA Premium 4 mobile app
cgren said:
Even if i flash with Stock Firmware will i get white asus boot?
---------- Post added at 04:21 AM ---------- Previous post was at 03:45 AM ----------
I just flashed with stock KK everything went back to normal.... boot is black again hehe.
Click to expand...
Click to collapse
You mean u flashed the UL_ASUS-T00F-WW-2.19.40.10-USER.ZIP flashed again and you got black logo back???
Sent from my ASUS_T00J using XDA Premium 4 mobile app
Yup it did, but it messed up my Root... so i flashed recovery v17 then V18 firmware. then Manual Update via ADB
Help.
unknown partition 'recovery_philz_t00f.img'
error: cannot determine image filename for 'recovery_philz_t00f.img'
I follow this TUT for rooting and i succeeded but just ask if i can update via OTA??
Sent from my ASUS_T00J using XDA Free mobile app
yep
kennybajande31 said:
I follow this TUT for rooting and i succeeded but just ask if i can update via OTA??
Sent from my ASUS_T00J using XDA Free mobile app
Click to expand...
Click to collapse
read the first post
answer is in there
Avoid and pass by a fool and a madman
How to root Black Shark 2 Global (short way)
Avoid and pass by a fool and a madman
Avoid and pass by a fool and a madman
A few guide to fix your bricked or bad-conditioned phone
Avoid and pass by a fool and a madman
Avoid and pass by a fool and a madman
Thank you for this great guide, I'm sure it will help a lot of people.
The update file I used in my post was from this link, I just rename to make it easier to update.
KM7 said:
Thank you for this great guide, I'm sure it will help a lot of people.
The update file I used in my post was from this link, I just rename to make it easier to update.
Click to expand...
Click to collapse
Wow, thank you very much for the full name link. I think I found something great. I think, now, you can try to root directly on latest firmware, and save lots of time. I will test it... and post it soon.
How to download the latest update as full-sized, factory stock roms
Under Construction....
Sorry for deleting this post.
BS team never open the stock rom download site. I think we can build one, but I couldn't gather enough information.
I was able to find all my own factory stock rom OTAs including the latest, but not others due to lack of information. Further problem is that after I share how to find & download your own latest factory stock rom directly, that site is really slowed down now. Maybe lots read it, download, never share, or due to other reason... The region and ota link is enough to build the stock rom download site, but now the server is slowed down, no one shares... so I stop here.
I will re-open this if I could gather enough information.
wga0 said:
Hey guys, I realized that I neither need to provide a detailed explain nor can.
I can't attach any files, pictures, links... even I can write now. There are too much restriction.
(I must delete all links I included here You can search it in xda-dev forum)
So, here's the shortest and fastest way to root your black shark 2 global.
If anybody want a long detail, more safe way, let me know. I will add later if possible.
If something goes wrong, end to brick your phone, you can always revive that with safe way.
As you know, though safety is increased greatly (Thanks very much to a/b slot system),
but accident can happen anytime. It's on your own responsibility, at your own risk.
Pre-Requirements:
adb/fastboot drivers, Magisk Manager latest version, global OTA1 update
(I skip all the details of 3 firmware regions, payload_dumper, twrp, all others)
(Backup your data. It requires several factory reset)
Steps (also skip all detail. I wish you familiar with adb, fastboot, a/b slot)
1. Unlock the bootloader
1) fastboot oem bs2_unlock (Thanks greatly to Bave Lee)
2) fastboot oem bs2_unlock_critical (I'm not certain this is mandatory, I just do it at first)
2. flash the global OTA1 update and reboot
1) find and set active your not using slot
fastboot getvar all
fastboot set_active x
2) flash the global OTA1 images to that slot
fastboot flash partition_x partition.img (flash all of it, not partially)
fastboot reboot (It will be reboot again to do factory reset, than will boot successfully)
3. Patch the boot.img with Magisk Manager and flash it
Now, you have a working old version boot image. Patch it, flash it and reboot
4. Backup the latest, your own boot.img
Now, your phone is rooted with old version. Backup your original latest boot image
1) adb shell
su
dd if=/dev/block/bootdevice/by-name/boot_x(your using_latest slot) of=...(any folder you prefer)/boot.img
2) copy the boot.img to your PC (with adb pull or mtp)
5. patch your own latest boot.img
1) Set back the active slot to your original slot, reboot
2) do factory reset (because of using OTA1, OTA2 update request will be remained to your current slot)
3) push the magisk manager, boot.img again and repeat the job (patch, pull out, reboot, flash and reboot again)
6. Now, you have the latest updated, rooted phone with stock & modified boot image
7. Don't forget to backup all your stock ROM before doing anything!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you done well, you can check the root status. It's rooted with magisk systemless root, all function's normal.
And be careful. Don't share the patched or stock boot image directly. There's multiple global version.
This is the latest version from my own black shark 2 global. It definitely different from yours.
If you flash different region version, your phone will be bricked. That's why I didn't share it and write this long method.
(If anyone want, I will explain details later with more safe way, what I did. But It's quite long way, takes long time)
Click to expand...
Click to collapse
Here is my region skyw1991010Os00mp5,can u help me with this?
Avoid and pass by a fool and a madman
Flauros7 said:
Here is my region skyw1991010Os00mp5,can u help me with this?
Click to expand...
Click to collapse
you have same region with me,
do you still need the files ? i have magisk rooted boot.img if you want.
Need help
I am successful root my BS2
it run Magsik perfect
but the Build number is SKYW1908301CN00MP6 and wifi does not work, also i cant update build number to Build SKYW1910291CN00MP7
use *#*#1027#*#* to locall update with the
SKYW1907040OS01MP3 Stock Factory Image not work too, it said Error the package unauthorized
can u help me solve this problem,
does the Global OTA 1 boot can fix it?
Can u send me your boot file i cant find it
thank you very much!!!
Avoid and pass by a fool and a madman
The MP7 China OTA update...
IT'S WORKED!!!
thank you very much!
now i'm trying to root new version
exynos 540 said:
you have same region with me,
do you still need the files ? i have magisk rooted boot.img if you want.
Click to expand...
Click to collapse
Hi can you sent me the stock boot image for skw1991010Os00mp5? I really need it.
Hello , Please I need Stock boot.img for this region SKYW1902180OS00MP2 android version 9.
Mustafa9698 said:
Hello , Please I need Stock boot.img for this region SKYW1902180OS00MP2 android version 9.
Click to expand...
Click to collapse
Are you sure your revision SKYW1902180OS00MP2? Isn't it SKYW1904180OS00MP2?
exynos 540 said:
you have same region with me,
do you still need the files ? i have magisk rooted boot.img if you want.
Click to expand...
Click to collapse
Yes bro can u send me the file?
wga0 said:
You mean your revision is SKYW1911010OS00MP5. Right? If you didn't try anything to your roms, you'll have previous revision SKY1909192OS00MP4 at the inactive slot. Here is the factory boot image of it. How to root is similar as above.
Before doing, backup all your data and unlock the bootloader. In this time, unlock_critical is not needed.
1. adb reboot bootloader
2. fastboot getvar current-slot (let's assume it returns b)
fastboot set_active a <- set the opposite slot as active
3. fastboot reboot
After factory reset, this will bring you to previous revision SKYW1909192OS00MP4. Install Magisk Manager and patch the boot image.
4. adb pull /sdcard/Download/patch_boot.img (let's assume you save the image to Download directory)
5. fastboot flash boot_a patch_boot.img <- flash that patched image to same slot (you just set active)
Your phone is now rooted with previous revision. You can backup all of your latest stock rom.
6. adb shell
7. su
8. dd if=/dev/block/bootdevice/by-name/boot_b of=/sdcard/Download/boot.img <- example of boot image. For insurance, just backup all your stock roms.
Now back to your original latest slot, root your own image.
9. fastboot set_active b
and repeat the rooting again with your own roms.
As you know, adb command can be used with USB Debugging, fastboot can be used in bootloader mode.
Or... if you need all of those images, let me know. I will upload full MP4 OTA factory images for your region. You can flash this to your inactive slot and it will fix all problems during updating to MP5 to your active slot.
Click to expand...
Click to collapse
Can u give me the file again because the link is dead?
Boot images, Factory(Full) OTA images for known regions/revisions
Avoid and pass by a fool and a madman
I am not responsible for your actions, but I will try to help.
I'm going to assume you have unlocked bootloader and ADB/Fastboot tools installed.
1. Download latest Magisk and make 2 copies of it. Install one of them on your phone. Change the extension of 2nd from .apk to .zip, then move it to your phone`s storage
2. Download Pitch Black recovery for Redmi 9C
3. Move recovery.img to both your ADB folder (can be found at C:\adb) and phone`s storage
5. Download DM-VERITY, FORCED ENCRYPTION
6. Rename it to enfec.zip and place in phone`s storage
4. Download attached vbmeta.img and place it in your ADB folder
5. Go into fastboot mode
5. On your PC, open cmd-here.exe in adb folder
6. fastboot flash recovery recovery.img
7. fastboot flash vbmeta vbmeta.img
8. fastboot reboot recovery
9. Sometimes recoveries don't work with touchscreen. In this case, flash other region's ROM. To do this, find and download fastboot version of ROM. Unzip it, run flash_all.bat while being in a fastboot mode (this will erase all data). WARNING: DO NOT RUN flash_all_and_lock.bat. THIS WILL LOCK THE BOOTLOADER AND YOU WILL HAVE TO WAIT ANOTHER WEEK!
Next retry again the whole tutorial. You can also use USB-OTG mouse.
10. Navigate to 'Install' section. Check every option except 'Reboot after installation is complete', 'Zip signature verification' and 'Advanced remove of Forced Encryption'. Select recovery image that you previously moved to your storage and install it 'as Recovery'.
11. In recovery, move to 'backup' and make a backup to your SD card (optional, but highly recommended). Usually, it doesn`t work out of the box. Try searching for guides.
12. In the same section install enfec.zip and then Magisk.zip. If you get errors like 'Failed to mount /nv_data', ignore them.
13. Reboot to system, copy external_sd/PBRB/tools -> storage/0/emulated/PBRB/
Done!
How to pass SafetyNet (tested on 05.05.21 dd/mm):
Simply enable MagiskHide. This will only work if you haven`t modified the /system with modules that don`t hide themselves.
If you did heavy modifications, install UniversalSafetyNetFix (USNF) (repo) or install both MagiskHide Props Config (can be found in Magisk`s modules) and USNF. Instructions to installation of Props Config can be found in the README or on the web. Experiment with it, this is device specific.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It seems like you are using redmi 9C NFC
I am using redmi 9C Global
Did you tested this recovery on your phone?
I downloaded a recovery from GitHub for redmi 9c flashed it after flashing I flashed vbmeta too but can't boot into recovery
I am currently on global EU ROM 12.0.3 which I flashed yesterday
Before that I was on miui global 12.0.10
I tried to root it with magisk and after flashing magisk patched boot.img flashed vbmeta too
But can't get root access
Before I was on miui global 12.0.8
I rooted with magisk and got root access
In order to get root access I downgraded back to miui 12.0.8 but can't get root access
What should I do now?
It seems like you are using redmi 9C NFC
Click to expand...
Click to collapse
True
I am using redmi 9C Global
Click to expand...
Click to collapse
That doesn`t really matter
Did you tested this recovery on your phone?
Click to expand...
Click to collapse
Yes
I downloaded a recovery from GitHub for redmi 9c
Click to expand...
Click to collapse
Which recovery have you flashed? I provided link to SouceForge, not GitHub
I downloaded a recovery [...] flashed it after flashing I flashed vbmeta too but can't boot into recovery
Click to expand...
Click to collapse
Try fastboot reboot recovery.img
If that doesn`t work, try updating your ADB/Fastboot tools. Just download needed files from any site and place them in your ADB folder.
Also, since this recovery is unofficial port, it is a bit different from original. To boot into recovery, you don`t have to hold power+volume_up untill you see recovery menu. Instead, hold it untill screen goes black.
I tried to root it with magisk and after flashing magisk patched boot.img flashed vbmeta too
But can't get root access
Click to expand...
Click to collapse
From my guide:
No users report bootloops, but in some cases root isn't granted. In this case follow next steps.
Click to expand...
Click to collapse
Before I was on miui global 12.0.8
I rooted with magisk and got root access
In order to get root access I downgraded back to miui 12.0.8 but can't get root access
Click to expand...
Click to collapse
I don`t really get what you say, but there is no need to downgrade/upgrade. If I were you, I would flash latest MIUI, though
What should I do now?
Click to expand...
Click to collapse
Try flashing latest eu MIUI (I can help with that, if you want) and then follow method B) step by step, without making any changes and reading everything that I wrote
Hope this helps!
Can't make a backup as your tutorial because i got an error, and what i need to backup just the 'one' selected from the recobery ? can i skip this step and just install the enfec.zip and then Magisk.zip ?
I am stuck from the step 8 and 9 because i got that error and i have no idea what select from the list of the backup...
Backup is an optional step. I get an error too and I have no idea why.
Seems like it worked very well. but the safetynet failed, should download Magisk v21.4 zip because the newest one failed at the moment to flash it, and if you get an error at the end of flashing the DM-VERITY, FORCED ENCRYPTION it's ok still working anyway. thanks for sharing the post
@0purple
Btw personally skip the step 8 and 9, if you failed to get into recovery with the bottons just try again the step 5,6,7
Knox6 said:
but the safetynet failed, should download Magisk v21.4 zip because the newest one failed at the moment to flash it,
Click to expand...
Click to collapse
Updated the post, try it
I have the European version 12.06 of the redmi 9c. I tried to boot into recovery, but the touch doesn't work in any way, so I can't do anything... help me
i just enabled magisk hide option in magisk manager setting it fixed it
MHaseebpk said:
View attachment 5278627View attachment 5278627i just enabled magisk hide option in magisk manager setting it fixed it
Click to expand...
Click to collapse
does the root work for you? I have the EUropera version 12.0.6 and it doesn't work
sephirot91 said:
does the root work for you? I have the EUropera version 12.0.6 and it doesn't work
Click to expand...
Click to collapse
Yes
MHaseebpk said:
Yes
Click to expand...
Click to collapse
See this
MHaseebpk said:
See this View attachment 5278773
Click to expand...
Click to collapse
how did you do it? I followed the guide perfectly and it doesn't work. On the other hand, with the second method, the pitch recovery touch does not respond to commands
sephirot91 said:
how did you do it? I followed the guide perfectly and it doesn't work. On the other hand, with the second method, the pitch recovery touch does not respond to commands
Click to expand...
Click to collapse
I just followed seconds method and I am on global rom
You should flash global rom and should try again
MHaseebpk said:
I just followed seconds method and I am on global rom
You should flash global rom and should try again
Click to expand...
Click to collapse
Ok thanks, I could try. Do you have a guide to flash the global version? thank you very much
https://c.mi.com/oc/miuidownload/detail?guide=2
is it okay? for flashing rom global
sephirot91 said:
Ok thanks, I could try. Do you have a guide to flash the global version? thank you very much
Click to expand...
Click to collapse
First you need to download angelica global latest (12.0.10) fastboot rom from Here
Download miflash pro english from Here
Extract mi flash pro zip file install mi flash pro and extract angelica global image too in your PC
Now power off you phone
Hold volume down and power button simultaneously for 5 seconds
Your phone will boot into fastboot mode
Now open miflash pro login with your mi account connect your phone
When you will connect your phone your phone will be automatically detected
And miflash pro will recommend you to flash in recovery click on it
Next select package (fastboot rom) which you downloaded and extracted before and select script flash all.bat
Wait for 5 to 6 minutes
Your phone will be flashed
After that setup your phone
Boot again into fastboot mode
Setup adb in your PC
Install mediatek USB vcom drivers
And next follow second method
MHaseebpk said:
First you need to download angelica global latest (12.0.10) fastboot rom from Here
Download miflash pro english from Here
Extract mi flash pro zip file install mi flash pro and extract angelica global image too in your PC
Now power off you phone
Hold volume down and power button simultaneously for 5 seconds
Your phone will boot into fastboot mode
Now open miflash pro login with your mi account connect your phone
When you will connect your phone your phone will be automatically detected
And miflash pro will recommend you to flash in recovery click on it
Next select package (fastboot rom) which you downloaded and extracted before and select script flash all.bat
Wait for 5 to 6 minutes
Your phone will be flashed
After that setup your phone
Boot again into fastboot mode
Setup adb in your PC
Install mediatek USB vcom drivers
And next follow second method
Click to expand...
Click to collapse
I don't lose the unlocked bootloader, right?
sephirot91 said:
I don't lose the unlocked bootloader, right?
Click to expand...
Click to collapse
Yes select flash all.bat your bootloader will remain unlock and your phone will be flashed
Don't select flash all and lock script otherwise bootloader of your phone will be locked and you will have to wait for 7 days to unlock bootloader
It might be common sense for some, but I didn't see this as a separate post and it might help people get around this.
Once you unlock the bootloader and root with Magisk, you can't have OTA updates from the phone itself.
But what you can do to get these updates is to use the Xperia Companion tool.
You have to go to Magisk first and click on Uninstall and choose Restore images. This will bring back your original boot image from a backup Magisk does when patching the image.
Once this is done, reboot and connect the phone with Xperia Companion. Allow file transfers through USB. No need for USB debugging.
If there's an update available, it will download and transfer it to your phone. You'll see the install process in the status bar.
Once this is done, you can reboot and verify the update was installed. Now it's time to use Magisk to patch the new boot image.
There's a good guide already made - here.
In short use XperiFirm to download the latest FW, get the boot-x... sin file, put it in the folder where you have unsin executable file and just drag it over unsin. This will produce an image file, which you copy to your phone. Start Magisk, Magisk -> Install, it will ask you where the image file is, so point to the location where you saved it.
The result file will be put in Downloads on your phone. Copy it over to your PC.
Reboot the phone to Fastboot (Volume Up and Power buttons, or turn off the phone and press Volume Up, then connect the USB cable), you'll see you're in Fastboot if the LED is blue.
Open CMD, point to the location where you have ADB files copied and type in:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Where magisk_patched.img is your image file, so just put in the name and location to that file.
For example: fastboot flash boot_a c:\temp\boot_X-FLASH-ALL-4BA8.img
If the command fails, type in fastboot devices and that should list one device - the phone you connected.
If no devices are listed, check if you have the drivers for your phone. The article link above lists all driver and utilities downloads.
I've used newflasher and it soft bricked my phone. Maybe it's something I did wrong, but using the above is way easier and safer, in my opinion.
Hope it helps you too!
i tried your guide, and magisk don`t have backup of boot,
Was there any sort of an error message from Magisk?
It worked straight out for me.
Can't find Magisk's backup folder though, so I can see what I have inside.
unicastbg said:
Was there any sort of an error message from Magisk?
It worked straight out for me.
Can't find Magisk's backup folder though, so I can see what I have inside.
Click to expand...
Click to collapse
yes
Sakuma_Eitarou said:
yes
Click to expand...
Click to collapse
Emm, ok, what was the error message? I can guess one or two, but better ask than assume the wrong thing.
unicastbg said:
Emm, ok, what was the error message? I can guess one or two, but better ask than assume the wrong thing.
Click to expand...
Click to collapse
I did't deal with blocking the bootloader, but I expressed my thoughts
Let's see if someone else has the same issue.
I found Magisk uses root/data/magisk_backup_xxxxxxxxx folders, where xxxx is a combination of numbers and letters. There's a boot image copy in there.
When I flashed my magsik patched boot file, I had to factory reset my phone, otherwise on boot android would tell me my file system is currupt.
Any ideas why that might be?
cheesepuff said:
When I flashed my magsik patched boot file, I had to factory reset my phone, otherwise on boot android would tell me my file system is currupt.
Any ideas why that might be?
Click to expand...
Click to collapse
reflash with newflasher and use 2.4,3 of magisk ad\nd upgrade from that point
bountyman334 said:
reflash with newflasher and use 2.4,3 of magisk ad\nd upgrade from that point
Click to expand...
Click to collapse
I'm not 100% sure what all that means.
What's ad/nd?
And I'm not sure what 2.4,3 means in regards to magisk
Pretty sure that was a typo and they meant "and". Plus the magisk Number is the variant for example I'm on 25.2 which should be the latest one...
unicastbg said:
It might be common sense for some, but I didn't see this as a separate post and it might help people get around this.
Once you unlock the bootloader and root with Magisk, you can't have OTA updates from the phone itself.
But what you can do to get these updates is to use the Xperia Companion tool.
You have to go to Magisk first and click on Uninstall and choose Restore images. This will bring back your original boot image from a backup Magisk does when patching the image.
Once this is done, reboot and connect the phone with Xperia Companion. Allow file transfers through USB. No need for USB debugging.
If there's an update available, it will download and transfer it to your phone. You'll see the install process in the status bar.
Once this is done, you can reboot and verify the update was installed. Now it's time to use Magisk to patch the new boot image.
There's a good guide already made - here.
In short use XperiFirm to download the latest FW, get the boot-x... sin file, put it in the folder where you have unsin executable file and just drag it over unsin. This will produce an image file, which you copy to your phone. Start Magisk, Magisk -> Install, it will ask you where the image file is, so point to the location where you saved it.
The result file will be put in Downloads on your phone. Copy it over to your PC.
Reboot the phone to Fastboot (Volume Up and Power buttons, or turn off the phone and press Volume Up, then connect the USB cable), you'll see you're in Fastboot if the LED is blue.
Open CMD, point to the location where you have ADB files copied and type in:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Where magisk_patched.img is your image file, so just put in the name and location to that file.
For example: fastboot flash boot_a c:\temp\boot_X-FLASH-ALL-4BA8.img
If the command fails, type in fastboot devices and that should list one device - the phone you connected.
If no devices are listed, check if you have the drivers for your phone. The article link above lists all driver and utilities downloads.
I've used newflasher and it soft bricked my phone. Maybe it's something I did wrong, but using the above is way easier and safer, in my opinion.
Hope it helps you too!
Click to expand...
Click to collapse
Going through relock and using xperia companion to update is way too slow, inefficient and you loose your data in the mean time.
Just download latest fw from xperifirm, get the new bootimage (unsin ), magisk it, flash the whole fw with new flasher in flash mode (usb + vol down), goto fastboot, flash magisk boot image, reboot, done !
You've lost 0 data, didn't lost root, and you have the new fw
That's nice, but bootlocker remains unlocked during the procedure I wrote about. Therefore no data is lost in the process.
I used newflasher before and softbricked my phone.
And it's always good to have an alternative.
All of the options are way too complicated, compared to using TWRP. But we sadly don't have custom recovery.
unicastbg said:
That's nice, but bootlocker remains unlocked during the procedure I wrote about. Therefore no data is lost in the process.
I used newflasher before and softbricked my phone.
And it's always good to have an alternative.
All of the options are way too complicated, compared to using TWRP. But we sadly don't have custom recovery.
Click to expand...
Click to collapse
I don't get how you soft bricked with newflasher, bad firmware maybe ? model crossflashing ?
I've always used newflasher since it's out, before I was using flashtool by androixyde and didn't had issues too
It stopped on the very last step. To be honest the first time I used FW for another region. When I realized that, I tried flashing the proper one, but newflasher always stopped on the very last step. Can't recall what it was checking or verifying for.
Today LSposed was updated and I ended up in bootloop. As @fastbooking was saying why not use newflasher. So I did. And I ended up exactly where I was before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
unicastbg said:
Today LSposed was updated and I ended up in bootloop. As @fastbooking was saying why not use newflasher. So I did. And I ended up exactly where I was before.
View attachment 5758521
Click to expand...
Click to collapse
Try an usb 2.0 port maybe
I tried everything the guys proposed on the newflasher xda thread. Sadly it made no difference. I tried different USB ports, cables, Windows, Linux... I'm giving up on an otherwise app with a great potential.
unicastbg said:
It might be common sense for some, but I didn't see this as a separate post and it might help people get around this.
Once you unlock the bootloader and root with Magisk, you can't have OTA updates from the phone itself.
But what you can do to get these updates is to use the Xperia Companion tool.
You have to go to Magisk first and click on Uninstall and choose Restore images. This will bring back your original boot image from a backup Magisk does when patching the image.
Once this is done, reboot and connect the phone with Xperia Companion. Allow file transfers through USB. No need for USB debugging.
If there's an update available, it will download and transfer it to your phone. You'll see the install process in the status bar.
Once this is done, you can reboot and verify the update was installed. Now it's time to use Magisk to patch the new boot image.
There's a good guide already made - here.
In short use XperiFirm to download the latest FW, get the boot-x... sin file, put it in the folder where you have unsin executable file and just drag it over unsin. This will produce an image file, which you copy to your phone. Start Magisk, Magisk -> Install, it will ask you where the image file is, so point to the location where you saved it.
The result file will be put in Downloads on your phone. Copy it over to your PC.
Reboot the phone to Fastboot (Volume Up and Power buttons, or turn off the phone and press Volume Up, then connect the USB cable), you'll see you're in Fastboot if the LED is blue.
Open CMD, point to the location where you have ADB files copied and type in:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Where magisk_patched.img is your image file, so just put in the name and location to that file.
For example: fastboot flash boot_a c:\temp\boot_X-FLASH-ALL-4BA8.img
If the command fails, type in fastboot devices and that should list one device - the phone you connected.
If no devices are listed, check if you have the drivers for your phone. The article link above lists all driver and utilities downloads.
I've used newflasher and it soft bricked my phone. Maybe it's something I did wrong, but using the above is way easier and safer, in my opinion.
Hope it helps you too!
Click to expand...
Click to collapse
hi, I have some questions, could you please help me explain:
1. Uninstalling magisk and rebooting backup boot image will wipe device data?
2. If I can't find back up of boot image, can I use the one downloaded from Xperifirm with the same build number of my device?
3. Is there any other way to update ota without haveing to reset device. Thanks
dieuluucanh said:
hi, I have some questions, could you please help me explain:
1. Uninstalling magisk and rebooting backup boot image will wipe device data?
2. If I can't find back up of boot image, can I use the one downloaded from Xperifirm with the same build number of my device?
3. Is there any other way to update ota without haveing to reset device. Thanks
Click to expand...
Click to collapse
Hi,
1. This won't wipe the device data nor change any system or user apps.
2. Yes, you can use a boot image of the same FW version as the one installed on the phone.
I even did it with a different version, by a mistake, and the phone booted OK. But I don't know what might go wrong so I can't recommend this.
3. OTA doesn't work with the patched by Magisk boot image. So you need to replace the image with the original one, restart, apply the OTA (via Xperia Companion), restart, replace with the patched file of the new FW boot image.
This process doesn't reset your data as it's on another partition. If you have a custom boot animation (the first one), it might be lost.
If we had a full TWRP support, the whole process would have been way easier. Developers are trying to get it to work, for which I'm grateful even if it doesn't work at the end.
Hi,
I tried to update my P6 using the magisk OTA update method:
-Unistall / Restore image
-Install OTA, no reboot
-Install magisk on inactive slot
-Reboot
My phone was on the SQ3A.220705.001.B2 update, few months old.
When I rebooted, I was prompted with the "device corrupted" message. I pressed the power key to continue, and was stuck at the Google logo boot loop.
I forced turned off the phone (hold power + vol up a few sec), and the phone rebooted, no corruption message to my surprise, and booted correctly. However, my system did not update (still on SQ3A.220705.001.B2).
I'm a rookie on device rooting, but my understanding is that my inactive slot (partition b) as the update installed but is corrupted and goes in boot loop, while partition a is not updated but not corrupted either.
The thing is, I only did "install on inactive slot", so magisk was uninstalled on partition a, and rebooting made me lost root on that partition.
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
SleinBuyt said:
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
Click to expand...
Click to collapse
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
SleinBuyt said:
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
Click to expand...
Click to collapse
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
m_pastuszek said:
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
Click to expand...
Click to collapse
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Strephon Alkhalikoi said:
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Click to expand...
Click to collapse
I agree on this side, but actually editing script that makes something similar comes down to the same thing
That was the same case for me.
After latest OTA update, no matter how many time I tried to flash full factory image via fastboot, stil showing device corrupted.
A couple of things everyone having this issue should be aware of.
Currently, "Flash to Inactive Slot" breaks verification/dm-verity on the Pixel 6/7, and I believe that's responsible for the "Device corrupted" error. The Magisk devs are aware but don't have a fix yet. I haven't been able to test because there have been no OTAs since I disabled those myself (which PixelFlasher can do for you), but I believe disabling them should prevent that problem during OTAs, but be advised I think doing so requires wiping /data when you do it.
Also, if you're still getting "device corrupted" even after reflashing stock, first watch for any errors during flashing in PixelFlasher (I may have a fix for anyone that has USB issues on Windows devices, but it involves the registry so it makes some people nervous), but if it isn't working then try Google's Android Flash Tool by finding your device and desired firmware here and clicking Flash. You'll need to be using Chrome. That's never failed for me. Once you have it up and running again *then* use PixelFlasher to patch and flash the boot image.
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Jaitsu said:
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Click to expand...
Click to collapse
To root the Pixel 6 on QPR2 Beta 1 you can patch the Pixel 7 boot image and then flash that on the Pixel 6.
Compression method of ramdisk in Pixel 6 boot image is incorrect · Issue #6441 · topjohnwu/Magisk
After switching to the beta version can't patch boot img and succesfully get root, with the stable version works. Device: Pixel 6a Android version: Android 13 QPR2 Beta 1 (T2B1.221118.006) Magisk v...
github.com
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
SleinBuyt said:
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
Click to expand...
Click to collapse
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Lughnasadh said:
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Click to expand...
Click to collapse
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
SleinBuyt said:
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
Click to expand...
Click to collapse
It's important if you don't want to brick your device. Did you read the link I gave you?
Lughnasadh said:
It's important if you don't want to brick your device. Did you read the link I gave you?
Click to expand...
Click to collapse
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
SleinBuyt said:
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
Click to expand...
Click to collapse
fastboot flash bootloader --slot=all <A13 bootloader image>
My situation is a bit bizarre. I'm on beta and recently got an update notification that was 190mb. I went to magisk to restore images and magisk says stock backup does not exist. From there and went ahead and use my PC to flash my stock boot image and rebooted. Once an Android it's still says the same thing but when I go back to the update it says installation problem Even though I am on stock. That's where I'm at right now. Haven't messed with it since just rolled with no root and stock boot image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lughnasadh said:
fastboot flash bootloader --slot=all <A13 bootloader image>
Click to expand...
Click to collapse
And it's done ! Thanks for potentially saving my phone later !