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
Related
Since TWRP is still not ported to V10, so i decided to make a prerooted-boot.img.
Download Link
You can flash this boot.img to root your Honor V10 AL20C00 (6GB+128GB China Edition) on stock firmware (B132)
Usage:
0. Unlock bootloader and close find my phone.
1. Power off your phone
2. Plug your phone to computer
3. Hold power and volume down until boot into fastboot mode
4. flash this boot.img by adb ( fastboot flash ramdisk boot-root-b122.img), please download adb by yourself
5. reboot (fastboot reboot)
Your phone may reboot twice, and you'll get root access.
Declaim:
I only test this on my own phone (BKL-AL20C00), Use this on your own risk. I'm not responsible for your phone's damage.
using this tool means you accept this.
Thanks:
HRT-Lin
@mankindtw for his Mate-10 root boot.img
cofface for his bootimg.exe to unpack and repack boot.img
@worstenbrood for his Huawei Update Extractor
Does this root work on stock BKL-AL20 8.0.0.132 update?
Same question. I got BKL-L09 8.0.0.120
No bootloader unlock needed? And i also hope, someone can confirm this on BKL-09 - 120 .
They didn't lock bootloader? Already preorder international unit
Hi,
Can you be a little more specific? Did you unlock your Bootloader first? When you say stock firmware B132, do you mean version 8.0.0.132 ? Thank you in advance for your reply!
Custom Recovery for V10
Hi ppl. Has a custom recovery been ported for the V10. I have managed to root my phone using the above method, but since there is no custom recovery available, I am unable to flash any mod / roms, etc.
I'm hesitant to try this without more information
harshshah17 said:
Hi ppl. Has a custom recovery been ported for the V10. I have managed to root my phone using the above method, but since there is no custom recovery available, I am unable to flash any mod / roms, etc.
Click to expand...
Click to collapse
Hi harshshah17,
Did you unlock your bootloader first? I think there are methods to flash zip files without having a custom REC. Try Flashfire apk. I've read the phone can get even more "restricted" (many features get blocked) once you root your Honor V10. Is it true in your case? Thanks in advance for your reply.
piphol said:
Hi harshshah17,
Did you unlock your bootloader first? I think there are methods to flash zip files without having a custom REC. Try Flashfire apk. I've read the phone can get even more "restricted" (many features get blocked) once you root your Honor V10. Is it true in your case? Thanks in advance for your reply.
Click to expand...
Click to collapse
Ofcourse i have unlocked my bootloader..Its only after that, that you can root. With regard to your question, I have not experienced any sort of "restriction" with my Honor View 10 post rooting. Seems to be working just as normal. The only thing is that i am unable to install the OTA update.
The reason I am asking for a custom recovery is because i need to remove Super SU and install Magisk instead. In order to remove super SU i need to flash an uninstall zip (I know you a can remove it from the Super SU options, but that doesn't seem to be working). I can certainly use flashfire to flash the uninstall zip but then my phone will be unrooted and I wont be able to flash magisk via flashfire.
If anyone has a solution for the above, suggestions will be appreciated. Thanks!
harshshah17 said:
Ofcourse i have unlocked my bootloader..Its only after that, that you can root. With regard to your question, I have not experienced any sort of "restriction" with my Honor View 10 post rooting. Seems to be working just as normal. The only thing is that i am unable to install the OTA update.
The reason I am asking for a custom recovery is because i need to remove Super SU and install Magisk instead. In order to remove super SU i need to flash an uninstall zip (I know you a can remove it from the Super SU options, but that doesn't seem to be working). I can certainly use flashfire to flash the uninstall zip but then my phone will be unrooted and I wont be able to flash magisk via flashfire.
If anyone has a solution for the above, suggestions will be appreciated. Thanks!
Click to expand...
Click to collapse
U can remove root by flashing the stock ramdisk.img, which can be extracted from the official full-ota update.app
Only thing I've seen that doesn't work with root is face unlock. Also how can I flash magisk since there isn't a recovery yet. Can I use flashify?
Yut kill
dawnc said:
U can remove root by flashing the stock ramdisk.img, which can be extracted from the official full-ota update.app
Click to expand...
Click to collapse
Where can you find the full OTA?
whymista said:
Where can you find the full OTA?
Click to expand...
Click to collapse
Download Firmware Finder for Huawei in Play store. They got partial and full OTAs there.
By the way, flashing custom ROMs for V10 is now also thru Fastboot. So I guess TWRP isn't applicable for V10? Maybe Magisk can also be flashed using Fastboot. I will try to research for custom ROM with Magisk. So far, I only see SuperSU pre-installed. ?
piphol said:
Download Firmware Finder for Huawei in Play store. They got partial and full OTAs there.
By the way, flashing custom ROMs for V10 is now also thru Fastboot. So I guess TWRP isn't applicable for V10? Maybe Magisk can also be flashed using Fastboot. I will try to research for custom ROM with Magisk. So far, I only see SuperSU pre-installed. [emoji25]
Click to expand...
Click to collapse
I did download that and the extractor tool but it says I need the update.app file to extract the boot image an I've yet to find that in either of the three files I tried.
So I know how to use fastboot but will I need the boot image first or can I just flash magisk. The current root method installs su. That's where I'm kind of stuck as far because I've always read that you have to uninstall su first but then wouldn't I lose the ability to flash magisk? I'm currently just rooted on the stock rom.
Didn't even know there was a custom rom hadn't seen it on here yet.
Yut kill
whymista said:
I did download that and the extractor tool but it says I need the update.app file to extract the boot image an I've yet to find that in either of the three files I tried.
So I know how to use fastboot but will I need the boot image first or can I just flash magisk. The current root method installs su. That's where I'm kind of stuck as far because I've always read that you have to uninstall su first but then wouldn't I lose the ability to flash magisk? I'm currently just rooted on the stock rom.
Didn't even know there was a custom rom hadn't seen it on here yet.
Yut kill
Click to expand...
Click to collapse
Do you have BKL-AL20? Here's a non-rooted boot image. I'm not sure if it can be used on other variants / versions. If you have another variant, I can find it for you.
BOOT_BKL-AL20_B132
https://mega.nz/#!Ps4jjIqJ!ssiYej9BAu6kZJZ8RfC8P1JDoyo9Ox36o42i8SMm1Lw
Credits to the custom ROM developer KangVIP for the boot image.
piphol said:
Do you have BKL-AL20? Here's a non-rooted boot image. I'm not sure if it can be used on other variants / versions. If you have another variant, I can find it for you.
BOOT_BKL-AL20_B132
https://mega.nz/#!Ps4jjIqJ!ssiYej9BAu6kZJZ8RfC8P1JDoyo9Ox36o42i8SMm1Lw
Credits to the custom ROM developer KangVIP for the boot image.
Click to expand...
Click to collapse
I have the bkl-l09. I'd appreciate it if you could. I'll try this version since it can't hurt though.
Sent from my ONEPLUS A5000 using Tapatalk
So I tried to flash it through adb and it didn't work this is what I got.
PS C:\> fastboot flash boot C:\Users\charl\OneDrive\BOOT_BKL-AL20_B132\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.362s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.385s
PS C:\> fastboot flash boot C:\Users\charl\OneDrive\BOOT_BKL-AL20_B132\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.362s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.385s
---------- Post added at 03:45 PM ---------- Previous post was at 03:40 PM ----------
I'm trying to use the recovery tool they have that says I need 5 different files but I've no idea where to find them like the system img etc.
Sent from my ONEPLUS A5000 using Tapatalk
This is what it's saying I need to unbrick
{
"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"
}
Sent from my ONEPLUS A5000 using Tapatalk
whymista said:
This is what it's saying I need to unbrick View attachment 4405892
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
It should be "fastboot flash ramdisk <boot image name>".
Second, if it doesn't help, the next step is to enter e-recovery mode. Press Volume Up + Power for 15 seconds. Follow the prompts and it should download the full OTA for you. I think you need your Huawei ID in the process (and a good Wifi signal).
Lastly, I think this is a sure bet but will cost you, google "funkyhuawei honor v10 rebranding guide". You will find a reddit link. They are the only team who "holds" BKL-L09 Full OTA roms that I know of. You need to buy "credits" to download OTAs and unbrick your phone. Unfortunately, team MT (team behind Firmware Finder) hasn't got a hold of a full OTA of BKL-L09.
From my experience, the first suggested solution should already work. I hope you don't get to the third solution.
How to Install TWRP:
Note: that version is UNOFFICIAL TWRP-3.3.0-0524
.Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here https://devsjournal.com/usb-drivers-...d-devices.html
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here https://devsjournal.com/download-min...boot-tool.html
Pre-Requisite 3
Your device needs this with unlocked bootloader
if it is not unlocked do the tutorial to unlock HERE
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
------------------------------------------------
1) Download TWRP: recovery-TWRP-3.3.0-0524-LENOVO_Z5PRO_GT-CN-wzsx150.img
2) After getting the TWRP file put it in the same ADB folder
3) Now start the phone in bootlader by doing this:
Connect the phone to the PC
Start the Minimal ADB & Fastboot program from the PC
On the PC screen, type:
adb reboot bootloader
(A request may appear on the phone screen with permission of USB debugging, accept it)
The phone will now restart in Bootloader mode.
4) Now that you are in bootloader mode, from the PC, from the screen
Minimal ADB and Fastboot type:
fastboot flash recovery recovery-TWRP-3.3.0-0524-LENOVO_Z5PRO_GT-CN-wzsx150.img
Sending 'recovery' (98304 KB) OKAY [ 5.970s]
Writing 'recovery' OKAY [ 0.539s]
Done !
---------
.How to Install Root Magisk:
{
"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"
}
Done !
Credits:
Maker: wzsx150
Developer Team: LR.Team
Is there any issues related to this recovery?
firemax13 said:
Is there any issues related to this recovery?
Click to expand...
Click to collapse
I had no problem with this recovery
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
BlueIce84 said:
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
Click to expand...
Click to collapse
Have the same scenario as you but I haven't done the tutorial yet as I read your post and I got concerned. Have you fix you issue? Is it safe to do this tutorial?
No solution so far. No twrp and no root
Now I have flashed the original rom with ZUI 10. Works well and updated to ZUI 11.
luigi0824 said:
Have the same scenario as you but I haven't done the tutorial yet as I read your post and I got concerned. Have you fix you issue? Is it safe to do this tutorial?
Click to expand...
Click to collapse
I've read somewhere that you need to flash vbmeta.img if verified boot is enabled, however I couldn't find the correct img to flash anywhere. Maybe if we ask someone that has the phone already rooted.
Can anyone post wzsx150's newest TWRP 3.3.1 from October 4? It's in this thread but the download link is for registered users only. I can't sign up for a Club Lenovo account.
BlueIce84 said:
No solution so far. No twrp and no root
Now I have flashed the original rom with ZUI 10. Works well and updated to ZUI 11.
Click to expand...
Click to collapse
What method would you follow to install the stock rom, like you, it comes with the bootloader unlocked by the seller and I don't know how to flash stock rom
Use this guide:
https://forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945
carlshark said:
Can anyone post wzsx150's newest TWRP 3.3.1 from October 4? It's in this thread but the download link is for registered users only. I can't sign up for a Club Lenovo account.
Click to expand...
Click to collapse
I gave up on clublenovo. They require SMS authentication to post so even when you log in you can't post and download. TWRP 3.3.1 is also available from 4PDA. That's what I used.
I was able to flash the TWRP 3.3.1 but i cant root nor i cant flash anything as the folders inside the sdcard directory is showing in weird names
luigi0824 said:
I was able to flash the TWRP 3.3.1 but i cant root nor i cant flash anything as the folders inside the sdcard directory is showing in weird names
Click to expand...
Click to collapse
You need to decrypt the internal storage.
normally this is done by entering to ping code to unlock the phone in TWRP on start up.
thorvall said:
You need to decrypt the internal storage.
normally this is done by entering to ping code to unlock the phone in TWRP on start up.
Click to expand...
Click to collapse
Will I lose any data if I decrypt my phone? And where do I find that pin code?
luigi0824 said:
Will I lose any data if I decrypt my phone? And where do I find that pin code?
Click to expand...
Click to collapse
Its the pin code you use to open the phone.
And enabling does not remove data, but it does give twrp read/write permission
Is it possible to implement support for OTA updates through TWRP?
BlueIce84 said:
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
Click to expand...
Click to collapse
i had the same issue and discover a solution
1) you have to manually go to your phone after you finish the flash below. DO NOT cmd fastboot reboot as it will flash stock
recovery
a) fastboot flash recovery twrp.img ( i rename the tweak recovery file to twrp.img)
b) http://4pda.ru/forum/index.php?showtopic=973179&st=0
(tweak recovery version 3.31)
2) after flash quickly go to your phone fastboot mode ( reminder again: do not tyoe fastboot reboot after flash successful appear in cmd)
3) manually select recovery , select english then select reboot and TWRP will appear
issues
1) i cannot manually tweak recovery via phone ( power +volume down ) as stock recovery will appear again.
A) so you need to go your PC to redo flash recovery again
B) i did a back up and redo PC flassh recovery again and mine files are stored successful
c) there is no install root in TWRP
D) about backup...
.best to back up via OTA-USB. pixel GCI crash ( QUALCOMM CRASH DUMP MODE ) my phone and my restore
file was missing as TWRP rename the restore file. spent one hour it so decide to do stock rom
current
a) I have not flash any rom yet and my original ANTUTU benchmark hovers around 300000 to 350000 based on vendor custom global rom
b) my phone model is 8gb 128gb android version 9 and lenovo version 11.0.084
c) updatess and NFC not supported
d) i opt not too root
e) bootloader still unlock
REQUEST...
would appreciate a ROM recommendation
a) have anyone flash a rom (not china stock rom) wirh an antutu beachmark abve 400000 ?
from a novice... after 2 weeks i can finally flash tweak recovery from the phonE.
about flashing stock rom..
i opt for stock rom and my antutu hovers around 409000 to 418000. from LENOVO app centre you can install play store
butterx2341 said:
i had the same issue and discover a solution
1) you have to manually go to your phone after you finish the flash below. DO NOT cmd fastboot reboot as it will flash stock
recovery
a) fastboot flash recovery twrp.img ( i rename the tweak recovery file to twrp.img)
b) http://4pda.ru/forum/index.php?showtopic=973179&st=0
(tweak recovery version 3.31)
2) after flash quickly go to your phone fastboot mode ( reminder again: do not tyoe fastboot reboot after flash successful appear in cmd)
3) manually select recovery , select english then select reboot and TWRP will appear
issues
1) i cannot manually tweak recovery via phone ( power +volume down ) as stock recovery will appear again.
A) so you need to go your PC to redo flash recovery again
B) i did a back up and redo PC flassh recovery again and mine files are stored successful
c) there is no install root in TWRP
D) about backup...
.best to back up via OTA-USB. pixel GCI crash ( QUALCOMM CRASH DUMP MODE ) my phone and my restore
file was missing as TWRP rename the restore file. spent one hour it so decide to do stock rom
current
a) I have not flash any rom yet and my original ANTUTU benchmark hovers around 300000 to 350000 based on vendor custom global rom
b) my phone model is 8gb 128gb android version 9 and lenovo version 11.0.084
c) updatess and NFC not supported
d) i opt not too root
e) bootloader still unlock
REQUEST...
would appreciate a ROM recommendation
a) have anyone flash a rom (not china stock rom) wirh an antutu beachmark abve 400000 ?
from a novice... after 2 weeks i can finally flash tweak recovery from the phonE.
about flashing stock rom..
i opt for stock rom and my antutu hovers around 409000 to 418000. from LENOVO app centre you can install play store
Click to expand...
Click to collapse
If you boot your ZUI system, your twrp will be overwritten by a stock recovery.
However if you flash magisk, your twrp won't be overwritten anymore. If you want to preserve your twrp after rebooting on ZUI, you need to flash magisk.
whatever I do.. the twrp wont be installed (let alone the root/magisk). ADB does say the twrp is flashed... but it will always boot to or the bootloader.. or the system (not the lenovo recovery or twrp recovery). Quiet frustrating... what can I do? Want this boy rooted!
Edit: done. The twrp linked in the tutorial is not correct use this one: https://drive.google.com/file/d/13mt0RLmT83BHSUBpH-J7EhaeZQ-MPYUu/view
That worked!
I want to unlock my bootloader but the site where you request the image file for unlocking it wont accept my IMEI1.. any idea guys?
{
"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"
}
Root & TWRP 3.4.0 for Android 10.
Root and absolutely working TWRP 3.4.0 on Android 10!
In the new TWRP and Root installation method described below, there is no need to format the Data partition to remove the encryption.
Thanks to TWRP's built-in FB Encryption (File Based Encryption), the contents of the Data partition are available with encryption preserved. The folders on the external memory have the correct names and structure.
Temporary flaw: each new firmware requires a new TWRP.
1. Download archive for up-to-date firmware (as of 09.12.20 - QPHS30.29-Q3-28-13-6) with files for installation TWRP and Magisk Root_TWRP_QPHS30.29-Q3-28-13-6.zip
2. Extract files:
- TWRP-Q-3.4.0-parker-nemo-nemo.img to the drivers adb & fastboot folder;
- Magisk-disable-dm-verity-v20.4.zip to the SD Card.
3. Boot the phone in fastboot mode, connect it to a PC and perform the following commands:
Code:
fastboot flash boot C:\adb\TWRP-Q-3.4.0-parker-nemo-nemo.img
4. After installation is complete, restart the phone in Recovery.
5. Go to the "Install" section. Click on "Select Storage" button, select Micro SD card, OK. Install Magisk-disable-dm-verity-v20.4.zip.
6. Reboot into the system.
Attention, it's important!
In case of release of new stock firmware RETEU, or you have a device for other regions, you can update TWRP yourself in the following way:
So, in order for you to have TWRP, mobile communications and Wi-Fi, you need to do the following:
- Copy to SD Card boot.img from Stok firmware archive, which is currently installed on your phone;
- Copy to the SD card twrp-installer-3.4.0-0-parker-nemo-nemo.zip;
- Follow step 3 of the basic instructions;
- Install directly in the TWRP boot.img itself under Boot;
- Install the twrp-installer;
- Install Magisk-disable-dm-verity-v20.4.zip.
Earlier versions of TWRP
QPHS30.29-Q3-28-13-2
QPHS30.29-Q3-28-13
Old Instruction:
1. Download archive with files for installation Magisk and TWRP Google Drive.
2. Extract files:
- boot_magisk_q.img to the drivers adb & fastboot folder;
- Magisk-ddmv-v20.4.apk, Magisk-disable-dm-verity-v20.4.zip, twrp-installer-3.4.0-0-parker-nemo-nemo.zip to the SD Card.
3. Boot the phone in fastboot mode, connect it to a PC and perform the following commands:
Code:
fastboot flash boot C:\adb\boot_magisk_q.img
4. Reboot into the system and install Magisk-ddmv-v20.4.apk.
5. Run the application Magisk Manager, go to the "Modules" tab and select twrp-installer-3.4.0-0-parker-nemo-nemo.zip.
6. After installation is complete, restart the phone in fastboot mode and then in Recovery.
7. Go to "Wipe" section and press "Format data" for decryption. Type "Yes" on request. Go to the TWRP Main Menu and reboot again in the Recovery.
8. Go to the "Install" section. Click on "Select Storage" button, select Micro SD card, OK. Install Magisk-disable-dm-verity-v20.4.zip.
9. Reboot into the system.
Updated TWRP to firmware version QPHS30.29-Q3-28-13-2.
Hey, thanks for doing this. I'm a newbie, but I got through your instructions and it worked! At least at first. After I OEM-unlocked and installed TWRP, Android seemed to be working fine. I went into TWRP installed Magisk and when I restarted it seems my wifi (wifi mac address is "unavailable") and the service state of my radio is off. I can't figure out how to get it back on.
I tried messing around with settings in *#*#4636#*#* , no luck.
I put my sim card in an old phone and it still works (I wondered if I got locked out by my carrier?)
Think it might be connected at all or do I have a separate issue going on here?
EDIT: Nevermind - I used Lenovo's Rescue Smart Assistant and got it fixed...
Thanks!
Wijitmaker said:
Hey, thanks for doing this. I'm a newbie, but I got through your instructions and it worked! At least at first. After I OEM-unlocked and installed TWRP, Android seemed to be working fine. I went into TWRP installed Magisk and when I restarted it seems my wifi (wifi mac address is "unavailable") and the service state of my radio is off. I can't figure out how to get it back on.
I tried messing around with settings in *#*#4636#*#* , no luck.
I put my sim card in an old phone and it still works (I wondered if I got locked out by my carrier?)
Think it might be connected at all or do I have a separate issue going on here?
EDIT: Nevermind - I used Lenovo's Rescue Smart Assistant and got it fixed...
Thanks!
Click to expand...
Click to collapse
What Software Channel intended your phone? I have a RETEU. If you have a different region, this is most likely the reason.
So, in order for you to have TWRP and work mobile communication and Wi-Fi, you need to do the following:
- from the Stock Firmware archive, which is currently installed on your phone, copy boot.img to SD Card;
- twrp-installer-3.4.0-0-parker-nemo-nemo.zip copy to SD Card (see at the attached files).
Install directly in TWRP boot.img and then install TWRP-installer.
Then reinstall Magisk-disable-dm-verity-v20.4.zip (see at the attached files) and whatever you want.
Hi do you have a way to apply OTA update without remove twrp?
Hey,
I have a brand new One Zoom here and like to root it.
Don't wanna brick it, so I have two silly noob questions:
Before performing step 3 in first post above
(fastboot flash boot C:\adb\TWRP-Q-3.4.0-parker-nemo-nemo.img)
I still have to unlock the bootloader, right???
On github, currently there is Magisk v21.1 out. Can I use this newer version or do I MUST use the version provided by ilia3367 in first post?
Thanks to all of you
Solo8000 said:
Hey,
I have a brand new One Zoom here and like to root it.
Don't wanna brick it, so I have two silly noob questions:
Before performing step 3 in first post above
(fastboot flash boot C:\adb\TWRP-Q-3.4.0-parker-nemo-nemo.img)
I still have to unlock the bootloader, right???
On github, currently there is Magisk v21.1 out. Can I use this newer version or do I MUST use the version provided by ilia3367 in first post?
Thanks to all of you
Click to expand...
Click to collapse
Yes your bootloader need to be unlock.
For me with use or twrp I can t install OTA update for résolve that I Have flash again m'y phone with stock Rom and use magisk patch way to Root m'y phone
I have write some instruction on that here
Updated TWRP to version QPHS30.29-Q3-28-13-6, updated the manual.
Solo8000 said:
On github, currently there is Magisk v21.1 out. Can I use this newer version or do I MUST use the version provided by ilia3367 in first post?
Click to expand...
Click to collapse
Use Magisk which is in the Instruction Manual.
This is a special version of Magisk for Motorola devices.
Magisk v21.4 刷机包 Motorola 修改版 | 云梦
介绍 Motorola 有个奇怪的 hab 保护技术，这个组件会保护系统不受侵害。如果不去除这个组件，在开机状态修改系统后，重启将会还原更改，在 TWRP 下修改系统，将无法开机。所以我做了一个修改版 Magisk，以彻底去除这个东西。 注意：仅适用于 Motorola 机型。 特性 - 强制去除 dm-verit
www.htcp.net
When I flash your version of TWRP my network connections go away. I had to reflash the original boot image to get it back.
finally got it. didn't realize you had included the modified zip file in another post.
Just a report:
did the process today, worked like a charme.
One caveat: unlocking bootloader via this stupid motorola web service did not work at first; yesterday evening submitting the correct unlock string always returned "Your Device Does Not Qualify For Bootloader Unlocking"; tried exact same procedure this morning - worked immediately; so I guess this is a problem with Motorola servers.
Right now I have TWRP, Magisk and as it looks ALL smartphone functions including wifi, radio, fingerprint.
My device: Moto Zoom, reteu, build number QPHS30.29-Q3-28-13-6; it's brand new and I did not set up any lock mechanism (like fingerprint) before this process (because some people complain that their fingerprint reader does not work anymore after flashing/rooting; maybe this is a solution to that problem)
Hello, I have a problem/question.
Recently I have a notification of system update available: QPH30.29-Q3-28-13-10, Im' currently on (QPH30.29-Q3-28-13-6) with TWRP an Magisk Installed.
When I try to make the update with the normal System Update it can't apply the update (no specific error).
So I would like to make the update manually; I downloaded the full image zip from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Then I think I could flash it with MotoFlashPro (using servicefile.xml), but what are the steps to keep everything working (TWRP, Magisk, and all network and fingerprint)?
Are these correct?
So, in order for you to have TWRP, mobile communications and Wi-Fi, you need to do the following:
- Copy to SD Card boot.img from Stok firmware archive, which is currently installed on your phone; (so I have to download the current full image and use the boot.img from this one and not the new firmware?)
- Copy to the SD card twrp-installer-3.4.0-0-parker-nemo-nemo.zip;
- Follow step 3 of the basic instructions;
- Install directly in the TWRP boot.img itself under Boot;
- Install the twrp-installer;
- Install Magisk-disable-dm-verity-v20.4.zip.
Sorry for the stupid questions but I don't want to start the process and brick the phone or lose something.
Thank you
TWRP already got official, is there a small chance to see custom roms like lineage os 18 in future?
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 !