Hi,
A quick one. I'm having a problem rooting the phone. I've been attempting to follow a tutorial that suggests to root is simple just go to recovery mode and install magisk.zip ... however, not that simple. The device doesn't seem to find it.
So trying the manual way but can't seem to find an image for TWRP for my device. Any assistance appreciated.
----
Extra Info.
As suggested my main goal is to root the device, I really don't mind how. I'm not wedded to a given method.
KingRoot failed
KingoRoot failed (no Linux version :/)
{
"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"
}
Yep that's why I'm here. I believe there's a way to get an unofficial TWRP but I've no clue how. That said if anyone knows how I could root without it, that would be great too. I can't seem to locate boot.img
Thanks for responding.
Compile a suitable TWRP at your own:
Compile TWRP for Your Device
www.xda-developers.com
first step, as always, unlock bootloader. for rooting, no TWRP required, you're reading the wrong guide. official Magisk has installation instructions on github.
alecxs said:
first step, as always, unlock bootloader. for rooting, no TWRP required, you're reading the wrong guide. official Magisk has installation instructions on github.
Click to expand...
Click to collapse
It says get a copy of boot.img or init_boot.img. I can find neither. All indications are that I need root access to find it so that I can root.
Thanks for engaging.
use mtkclient to get boot.img
Turns out didn't need to do that.
Grab the rom from
Firmware,Service
Firmware,Service
www.doogee.cc
Extract.
Use the boot.img and the vbmeta.img. According to the magisk instructions from github (buried slightly), use don't use [_x] just `boot`. Seems to autofind the correct partition.
Not sure how to lock up the bootloader when done though as it leaves the device in an error state
AffectedCacti said:
Not sure how to lock up the bootloader when done though...
Click to expand...
Click to collapse
You don't!
AffectedCacti said:
Turns out didn't need to do that.
Grab the rom from
Firmware,Service
Firmware,Service
www.doogee.cc
Extract.
Use the boot.img and the vbmeta.img. According to the magisk instructions from github (buried slightly), use don't use [_x] just `boot`. Seems to autofind the correct partition.
Not sure how to lock up the bootloader when done though as it leaves the device in an error state
Click to expand...
Click to collapse
Lucky, your phone has stock firmware direct from the manufacturer. Just a reminder that you need to patch vbmeta.img when rooting with magisk if your stock firmware contains vbmeta.img, otherwise you will be soft bricked, I had this happen to me, luckily SP flash tool was able to reflash vbmeta in brom, since I had no access to fastboot.
If you have access to fastboot you can accomplish this with:
Code:
fastboot --disable-verification flash vbmeta "C:\path\to\vbmeta.img"
If you do not like I did a blank image will work, you can create it with:
Code:
python avbtool.py make_vbmeta_image --flags 2 --padding_size 4096 --output vbmeta_disabled.img
Here is a link to avbtool.py which only requires python to run: https://1drv.ms/u/s!AvFNhY9dpwLfhf5TJ3xmoYCQqYfHOA?e=aGLyqu
Make sure to replace the padding size with the size of your image. Then you can flash that blank image using whatever flash tool your processor comes with, for me it was SP Flash tool because I have an MTK processor.
I guess if you have your stock firmware and a manufacturer provided flash tool, it doesn't really matter if you brick your device though. Anyways, Cheers!
Wasn't sure what the hell vbmeta was in all fairness, but I did this along with the instructions provided by Magisk.
Thanks for the heads up!
I don't think Doogee provide a flashing too but it seems that they provide the roms, which naturally, includes a copy of the vbmeta.img.
Related
The only command prompt that seems to be working is fastboot flash boot twrp.img but when I type fastboot flash recovery the flash fails. I use Minimal ADB and Fastboot command prompt. The latest version too. I downgraded my android 11 to 10 successfully. I have no problems rooting magisk through ADB but why can't TWRP permenantly stick? How can I force it to stick as my main recovery no matter what rom I flash?
Crap. I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10. Sorry for the confusion. Any tips of how to retain twrp? Having problems with my unlocked pixel 4a.
This guide shows you how to get TWRP to stick:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
P4a doesn't have a recovery partition anymore, recovery is part of the boot.img. That's why the fastboot cmd fails.
UltimateGamer83 said:
Crap. I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10. Sorry for the confusion. Any tips of how to retain twrp? Having problems with my unlocked pixel 4a.
Click to expand...
Click to collapse
You can't flash recovery on this phone. It's part of boot.img. Put the TWRP.img file in your internal storage of your phone. Flash the TWRP temporarily first. Fastboot boot TWRP.img. When TWRP boots, click install, then select install image. Choose your TWRP file and select install Ramdisk. Swipe to flash. TWRP will then be installed permanently. You must also be using a custom kernel with TWRP compression support because the partition is not big enough and must be compressed otherwise you will run into issues like TWRP freezing or touch screen issues.
I tried that and twrp still wont stick even after a OTA update flash. I installed ram disk twrp even after the update. What gives?
I fixed it. My mistake was flashing magisk boot img after the ramdisk installation and two kenel. I just flashed magisk.zip instead and got things working.
UltimateGamer83 said:
I fixed it. My mistake was flashing magisk boot img after the ramdisk installation and two kenel. I just flashed magisk.zip instead and got things working.
Click to expand...
Click to collapse
Yes, if you flash magisk boot img it will replace TWRP. Flashing the zip is the way to go. Glad you got it working.
UltimateGamer83 said:
I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10.
Click to expand...
Click to collapse
I've move your thread out of development, for which it doesn't qualify.
And I assumed your consent and edited the thread title.
In order to edit a title, click the "Edit" button of your OP and you'll see the title at the very top, which you're able to edit:
Spoiler: Screenshots
{
"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"
}
Regards
Oswald Boelcke
Senior Moderator
UltimateGamer83 said:
I tried that and twrp still wont stick even after a OTA update flash. I installed ram disk twrp even after the update. What gives?
Click to expand...
Click to collapse
I'm curious....you said you are on Android 10, but then you mentioned above installing an OTA update.....I thought all the currently available OTA updates are only for android 11?
My 10 cents worth. Magisk kills fastboot and adb in MY armor x5 mt6765, in 10_Q, so had no choice but to load boot-debug.img just to 'test'.
Try an android 9 bootloader designed for them 'super' .img's, this is the only way I could LOAD magisk, only to find what I read here.
Also note, in 10_Q, the gsi ability found in dev options dissapears when magisk is flashed, so I cant flash gsi, never mind use fastboot or adb.
Thank you.
{
"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"
}
I've an infinix note 8i with following build number :
X683-H694EFGHIJUW-Q-OP-210831V351
I've unlocked the bootloader. But I can't find the firmware that matches my phones build number. The latest firmware that I found was :
Infinix_Note_8i_X683_MT6768_V332_210305
So obviously the build numbers are not the same. So I need solutions on what to do? Should I use this unmatched build version firmware to root my device? Or maybe I can extract my stock firmware somehow? And also another thing, some were saying I needed to flash empty vbmeta file before flashing patched boot image. So where would I get the empty vbmeta file?
Thanks In Advance.
With regards to vbmeta.img:
It doesn't matter what kind of vbmeta is used, because fastboot only changes 2 bytes on a specfic address in it which are parsed by the botloader. But the vmeta must have at least a size of 4KB.
Have attached a blank vbmeta.
jwoegerbauer said:
With regards to vbmeta.img:
It doesn't matter what kind of vbmeta is used, because fastboot only changes 2 bytes on a specfic address in it which are parsed by the botloader. But the vmeta must have at least a size of 4KB.
Have attached a blank vbmeta.
Click to expand...
Click to collapse
Thanks A Lot, Just finished rooting my device finally, though I experienced one bootloop but fixed it via SP Flash Tool. Guess I would post a detailed thread of how I did it cause there isn't much help on the internet about this model.
sharifrafid said:
Thanks A Lot, Just finished rooting my device finally, though I experienced one bootloop but fixed it via SP Flash Tool. Guess I would post a detailed thread of how I did it cause there isn't much help on the internet about this model.
Click to expand...
Click to collapse
Did you manage to root it with this build number or did you downgrade?
anthonymatar1 said:
Did you manage to root it with this build number or did you downgrade?
Click to expand...
Click to collapse
Well, first I tried with this build number and root was successful but then my Bluetooth and Wifi was not working at all. So then I had to downgrade to v332 and then root again. Now things are running perfectly.
sharifrafid said:
Well, first I tried with this build number and root was successful but then my Bluetooth and Wifi was not working at all. So then I had to downgrade to v332 and then root again. Now things are running perfectly.
Click to expand...
Click to collapse
Did you try to update your device after rooting it?
@anthonymatar1 Nope, but I think there's a high chance that updating your device will result in a brick or something. I wouldn't suggest it.
INFINIX NOTE 8i UNOFFICIAL TWRP X683
DOWNLOAD
Just Follow the Guide
mastersenpai05 said:
INFINIX NOTE 8i UNOFFICIAL TWRP X683
DOWNLOAD
Just Follow the Guide
Click to expand...
Click to collapse
Will it work for this build number X683-H694EFGHIJUW-Q-OP-220318V387
I have a CUBOT Note 20 Pro (rooted) and today I tried to install the android 11 GSI when I got an error saying "FAILED (remote: 'This partition doesn't exist')" when trying to flash using the fastboot command line and this command specifically "fastboot flash system system.img". I looked around the scatter file and there seems to be no use of the system.img file whatsoever.
I have attached the scatter file and a screenshot of the error.
Any help would be highly appreciated.
{
"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"
}
[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition
Disclaimer: Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything...
forum.xda-developers.com
aIecxs said:
[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition
Disclaimer: Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything...
forum.xda-developers.com
Click to expand...
Click to collapse
How exactly do I use this tool?
read back super.img from SP Flash Tool, patch it, replace system.img, whatever, and flash new super.img back from fastboot
aIecxs said:
read back super.img from SP Flash Tool, patch it, replace system.img, whatever, and flash new super.img back from fastboot
Click to expand...
Click to collapse
Can you explain the steps a bit more? I'm really new and have no clue how to do this.
sorry apparently TWRP is required, but you can also use official tools on PC
https://forum.xda-developers.com/showthread.php?t=4041843
https://forum.xda-developers.com/showthread.php?t=4196625
aIecxs said:
sorry apparently TWRP is required, but you can also use official tools on PC
https://forum.xda-developers.com/showthread.php?t=4041843
https://forum.xda-developers.com/showthread.php?t=4196625
Click to expand...
Click to collapse
So, lets review the steps:
1. Unpack the super.img using the links you provided
2. Modify the system.img inside the super
3. flash
another approach is DSU Loader from Developer Options
DSU Sideloader lets you easily boot any custom GSI via Android DSU Loader
DSU Sideloader is an open source app that greatly simplifies the custom GSI installation process of the Android DSU Loader. Check it out!
www.xda-developers.com
https://forum.xda-developers.com/t/cubot-note-20-pro.4383027
Good night everyone.
I have a Nokia 2.2 TA-1188 to which I recently unlocked the bootloader successfully using the method from this guide:
[GUIDE] How to unlock the bootloader for Nokia 2.2
To content farms: DO NOT COPY AND PASTE THE ENTIRE GUIDE! Now the last piece of puzzle of Nokia x.2 series bootloader unlock line has been completed, thanks to the help of a member called Woke_World. After I read his procedure, I decided to...
forum.xda-developers.com
However, when I tried to flash the latest TWRP (v3.6.2) over stock Android 9 (the ROM used to unlock the bootloader from the guide above) following the exact procedure shown on TWRP's site, using both the recovery IMG and the vbmeta linked within the instructions (the vbmeta apparently comes direct from Google), the phone became bricked and totally unresponsive apart from periodic short vibrations whenever I try to boot in any way (system, fastboot, recovery, etc.).
What can I do to try revive it?
kevriveroc said:
Good night everyone.
I have a Nokia 2.2 TA-1188 to which I recently unlocked the bootloader successfully using the method from this guide:
[GUIDE] How to unlock the bootloader for Nokia 2.2
To content farms: DO NOT COPY AND PASTE THE ENTIRE GUIDE! Now the last piece of puzzle of Nokia x.2 series bootloader unlock line has been completed, thanks to the help of a member called Woke_World. After I read his procedure, I decided to...
forum.xda-developers.com
However, when I tried to flash the latest TWRP (v3.6.2) over stock Android 9 (the ROM used to unlock the bootloader from the guide above) following the exact procedure shown on TWRP's site, using both the recovery IMG and the vbmeta linked within the instructions (the vbmeta apparently comes direct from Google), the phone became bricked and totally unresponsive apart from periodic short vibrations whenever I try to boot in any way (system, fastboot, recovery, etc.).
What can I do to try revive it?
Click to expand...
Click to collapse
If you can connect to the phone with SP Flash Tool you should be able to flash it with Android 9 again and start over. Just download though, not format + download, because then you'll need to restore your IMEI and serial numbers.
djinc91 said:
If you can connect to the phone with SP Flash Tool you should be able to flash it with Android 9 again and start over. Just download though, not format + download, because then you'll need to restore your IMEI and serial numbers.
Click to expand...
Click to collapse
I have just tried to do so, but to to no avail. I keep getting the following error message:
STATUS_STOR_LIFE_EXHAUST (0xC003001D)
The storage on your device has reached end of life, please change to use new device to do operations
I used the DA bundled with SP Flash Tool and drivers linked in one of the folders, apparently MTK ones.
Here's a screenshot of the error message:
{
"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"
}
I was able to download the firmware again after unchecking the Storage Life Cycle Check box within SP Flash Tool's options, and the phone is now up and running, no troubles up so far.
Thank you very much for your help djinc91!
Uhm Ur phones storage chip is literally dying
Thats emmc for u
areallydumbperson said:
Uhm Ur phones storage chip is literally dying
Thats emmc for u
Click to expand...
Click to collapse
I've had no trouble with my storage during all the years I've owned this phone. Never experienced slowdown, errors, loss of data, etc, not now, not before.
Even so, this is just a backup/2nd device used for nothing important, so it doesn't bother or worry me in the slightest. I'll just keep it using it as is until it dies or I just can't make it usable anymore.
Thank you for your heads up, though.
If you not like ZUI firmware - you can flash Pseudo_Global to your tablet. I've tested this way and sharing it here.
Pseudo_global fw was built on ZUI, it has A11 inside and you never can to get some system updates - no one is doing them.
Your data will gone away.
YOU ARE WARNED !
And so:
I've tryed this on ZUI 14.0.127 with unlocked bootloader and active slot _a. Active slot can be checked with
Code:
adb shell /bin/getprop ro.boot.slot_suffix
and answer must be _a
If not, you need change boot slot with command in fastboot mode:
Code:
fastboot set_active other
And now you can reboot in EDL mode and start to flash all needed partitions from unpacked archive Pseudo_ROW_J716Fl.7z
You need unpacked ZUI 12.6.211 from lolinet https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro_2021/TB-J716F/ for working with QPST Partition Manager.
How it looks you can see in this video:
You must flash ALL partitions archive contains. Files in Add.rar not need, it for any case.
MANDATORY ! After flashing you need at first to boot in recovery and make reset to factory settings, it will format userdata. Without this action you can't boot.
Spoiler: IS
{
"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"
}
Good Luck !
f1tm0t said:
If you not like ZUI firmware - you can flash Pseudo_Global to your tablet. I've tested this way and sharing it here.
Pseudo_global fw was built on ZUI, it has A11 inside and you never can to get some system updates - no one is doing them.
Your data will gone away.
YOU ARE WARNED !
And so:
I've tryed this on ZUI 14.0.127 with unlocked bootloader and active slot _a. Active slot can be checked with
Code:
adb shell /bin/getprop ro.boot.slot_suffix
and answer must be _a
If not, you need change boot slot with command in fastboot mode:
Code:
fastboot set_active other
And now you can reboot in EDL mode and start to flash all needed partitions from unpacked archive Pseudo_ROW_J716Fl.7z
You need unpacked ZUI 12.6.211 from lolinet https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro_2021/TB-J716F/ for working with QPST Partition Manager.
How it looks you can see in this video:
You must flash ALL partitions archive contains. Files in Add.rar not need, it for any case.
MANDATORY ! After flashing you need at first to boot in recovery and make reset to factory settings, it will format userdata. Without this action you can't boot.
Spoiler: IS
View attachment 5783891View attachment 5783993View attachment 5783995
Good Luck !
Click to expand...
Click to collapse
It was exactly what I was looking for and trying for days, but following your tutorial I still couldn't, it didn't turn on, I had to upload the rom 12.6.211 again. I wanted to leave it with multiple languages.
augustobfe said:
still couldn't, it didn't turn on
Click to expand...
Click to collapse
OK, I will re-check it in 2-3 days. Although I think you did something wrong.
f1tm0t said:
will re-check it in 2-3 days
Click to expand...
Click to collapse
Dude, I have some bad news for you. Your hands are crooked. That needs to be fixed.
My method works without fail. It only takes half an hour.
Try it again.
Spoiler: Look this: