Hello every one!
i cant install my twrp and i need help
C:\Users\admin\OneDrive\Desktop\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) slot-suffi: not found
target reported max download size of 536870912 bytes
sending 'recovery' (29252 KB)...
FAILED (remote: unknown command)
finished. total time: 0.003s
the file what i used
https://eu.dl.twrp.me/evert/twrp-3.2.3-0-evert.img.html (i renamed file name to twrp.img)
UPDATE!!!!!!!!
i have boot file but i cant install twrp permanently
UPDATE 2!!!!!!!
my computer does not recognize my phone
Install LineageOS on evert | LineageOS Wiki
wiki.lineageos.org
I don't have the device, but the manual says to flash to the boot partition, not to recovery.
ze7zez said:
Install LineageOS on evert | LineageOS Wiki
wiki.lineageos.org
I don't have the device, but the manual says to flash to the boot partition, not to recovery.
Click to expand...
Click to collapse
ok i will try
Seems you have downloaded the website instead of the recovery
(Therefore the ending with *.html. Changing the filename won't change the filetype...)
On your mentioned website, click on the download-link which is named
Download twrp-3.7.0_9-0-evert.imgNow you should get a file, which is really a *.img
ze7zez said:
Install LineageOS on evert | LineageOS Wiki
wiki.lineageos.org
I don't have the device, but the manual says to flash to the boot partition, not to recovery.
Click to expand...
Click to collapse
it didnt work
chrysopra said:
Seems you have downloaded the website instead of the recovery
(Therefore the ending with *.html. Changing the filename won't change the filetype...)
On your mentioned website, click on the download-link which is named
Download twrp-3.7.0_9-0-evert.imgNow you should get a file, which is really a *.img
Click to expand...
Click to collapse
i can just delete ".html" in my link or add it to yours so tell me how does it works?
just saying
For me the easiest way to install twrp and not break anything is to download the installer zip and img rename the img to twrp.img then copy the installer zip to sd card and use "fastboot boot twrp.img" while in fastboot then click on install and install the zip.
Perhaps you could try downloading fom an alternative site:
Download TWRP for evert
Download TWRP Open Recovery for evert
dl.twrp.me
I wonder, if you got a complete file. Download-size is 32.5 MB. Sending recovery command gave a lower value (29252 KB) . Maybe itś correct and there is some file-overhead, but itś worth a try...?
10Maximus10 said:
For me the easiest way to install twrp and not break anything is to download the installer zip and img rename the img to twrp.img then copy the installer zip to sd card and use "fastboot boot twrp.img" while in fastboot then click on install and install the zip.
Click to expand...
Click to collapse
i tryed to boot twrp but it didnt work
Unknown_PL said:
i tryed to boot twrp but it didnt work
Click to expand...
Click to collapse
Uninstall Minimal ADB and Fastboot, check if you have unlocked the bootloader and use >Google platform-tools<.
In addition to the comment "does not work", include the results of your commands.
Nobody but you can see them.
Unknown_PL said:
Hello every one!
i cant install my twrp and i need help
Click to expand...
Click to collapse
Yeah flashing twrp on boot worked, but now i cant turn on system
I recently ran into a similar situation. Try booting into recovery. In TWRP check if the Folder "data" is mounted. On my device, the 3.7.0 had problems. Formatting data as ext2 and back to ext4 made it readable, although of course formatting deleted all data. That worked until the next boot...
Solution was, to flash an older version of TWRP (3.2.x), afterwards it could be reflashed with the most recent version which now worked without problems.
Also, on some systems, if you flash TWRP once and try to reboot into System, the boot partition is being "repaired" by your system an TWRP is gone...
chrysopra said:
I recently ran into a similar situation...
Click to expand...
Click to collapse
then what i need to do?
use 3.2.3-0 and flash it to the boot?
Exactly. Flash 3.2, reboot into recovery. Within TWRP you can mount USB drive, which lets you easy install anything else. (TWRP 3.7, root, ROM...)
Unknown_PL said:
use 3.2.3-0 and flash it to the boot?
Click to expand...
Click to collapse
Did you ever heard of A/B slots? The Moto G6+ uses A/B slots and does not have a partition /recovery. Of course there is a recovery but it 's merged in the boot.img. So the boot.img is able to boot into recovery and also into system.
Your TWRP image is recovery only and isn't able to boot into system!
***
What will happen when flashing TWRP to partition /boot?
In that case your boot.img = twrp.img and will only boot into recovery.
How to install TWRP permanently on your device?
First of all you should have a look at https://twrp.me/motorola/motorolamotog6plus.html
TWRP provides an installation guide for every device and it´s recommended to follow these steps.
***
Here´s a more detailed guide:
1. In your case you have to restore the boot.img since it got overwritten by flashing your twrp.img to /boot.
If available use a backup of /boot. Otherwise flash the stock boot.img from your current running firmware version. Firmware builds can be found here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
(take care of your software channel, i.e. RETUS)
*** Be aware that by flashing your stock boot.img Magisk will be deinstalled from ***
your device and as a result of this you will LOOSE ROOT ACCESS!!
2. Run
fastboot boot <TWRP.IMG>
3. On TWRP main screen go to Advanced => Install Recovery Ramdisk and pick the twrp.img:
{
"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"
}
WoKoschekk said:
Did you ever heard of A/B slots? The Moto G6+ uses A/B slots and does not have a partition /recovery. Of course there is a recovery but it 's merged in the boot.img...
Click to expand...
Click to collapse
Yeah I think that will work but you need other link beauce that one twrp link is not working
Can I try it on normal evert twrp link?
And what one folder (from lolnet) should I pick?
Unknown_PL said:
Yeah I think that will work but you need other link beauce that one twrp link is not working
Click to expand...
Click to collapse
It's fixed.
Unknown_PL said:
And what one folder (from lolnet) should I pick?
Click to expand...
Click to collapse
It depends on your software channel:
RETAIL = general software build, w/o any region
RETUS = builds for U.S. region
RETIN = builds for India region
...and so on.
Beside that, there are also builds for carrier branded phones.
To find your software channel:
a) Open a terminal app and run
getprop ro.carrier
b) settings > about the phone > software channel
c) fastboot getvar all has also an entry for that, but I don't know exactly what name it is.
d) the specific model no.: XT1926-???
The last digit depends on your software channel.
WoKoschekk said:
It's fixed.
It depends on your software channel...
Click to expand...
Click to collapse
Well I booted twrp and install recovery rom but what file from lolnet should I pick i know what folder but where are 4 files and I don't know what I need to do
Unknown_PL said:
but where are 4 files and I don't know what I need to do
Click to expand...
Click to collapse
I don't know what you mean. What folder? Which 4 files? The downloaded firmware is a ZIP file with one folder inside. Inside that folder are more than 20 files.
WoKoschekk said:
I don't know what you mean. What folder? Which 4 files? The downloaded firmware is a ZIP file with one folder inside. Inside that folder are more than 20 files.
Click to expand...
Click to collapse
sorry i mean there not were and i used RETEU and there is 5 files
Related
Zenfone 3 Deluxe ZS550KL / ZS570KL / ZS570KL PRO
How to change device SKU to WWDisclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about procedures,
* tools or terms in this thread before proceeding! YOU are choosing to
* make these modifications, and if you point the finger at me for
* messing up your device, I will laugh at you.
*/
The are two main reasons to change our SKU from TIM, CN or JP to WW. Firstly, the WW firmware is apparently getting OTA updates first. In second place, Marshmallow 6.0 Bootloader Unlock process requires 4.12.40.1698 firmware version and above, but only WW got the update (you may find this useless as 7.0 update is here, but some 6.0 users may need it). This will guide you in the process.
Warning!
Always have your original firmware, recovery and boot files in case things don't go as expected
Backup all of your personal data!
PLEASE MAKE SURE you are using the respective files for your CPU (ZS570KL SD820 2.15Ghz - ZS570KL PRO SD821 2.3GHz)
Prerequisites
Adb and Fastboot installed. I recommend you to install it from HERE.
Drivers installed. Try using these or Universal ADB Drivers
Python 2.X or 3.X installed.
WW target firmware. You can download it from the ASUS official website or from AndroidFileHost mirror: ZS570KL SD820 or ZS570KL PRO SD821.
Respective firmware stock recovery. You can download it from here: ZS570KL SD820 or ZS570KL PRO SD821
sdat2simg toolkit (you can find img2simg linux binary in second post).
Guide
In this case we are going to change a ZS570KL using the UL-Z016-WW-4.12.40.1698 firmware (the version needed to unlock the bootloader in Android 6.0) and it's respective recovery.
1. Extract the sdat2simg toolkit
Extract the sdat2simg_toolkit.rar and you will have this folder structure:
- sdat2simg_toolkit/
|-> bin / > necessary tools
|-> input/ > input system files
|-> output/ > output system files for flashing
|-> sdat2simg.bat > tool execution2. Extract system files from firmware
Open the firmware zip and extract system.new.dat and system.transfer.list into the input folder.
{
"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"
}
3. Run the tool
Now open the sdat2simg.bat file. There must no be trouble if you have properly installed python.
The tool will first convert the system.new.dat and system.transfer.list into a raw ext4 image, then it will be converted into a sparse flashable image.
When the process has finished, check the output folder. The system.img file is what we are interested in. This is our flashable system image.4. Flash the WW system image
Now we need to reboot into bootloader mode. Turn off the device and press Volume up + Power button. Or by using adb command:
Code:
adb reboot bootloader
Now open a terminal inside output folder and flash the system image by using the fastboot command:
Code:
fastboot flash system system.img
5. Flash the WW recovery image
Then we are going to flash the WW recovery image. Open a terminal where you placed the recovery image and flash it by using fastboot command:
Code:
fastboot flash recovery Z016-WW-4.12.40.1698_recovery.img
5.a. (Optional) Flash WW boot image
You can optionally flash the WW boot image contained inside the firmware zip. Extract it, open a terminal next to the boot.img file and flash it by using the fastboot command:
Code:
fastboot flash boot boot.img
(Not tested)6. Factory reset
Reboot your device by using fastboot command:
Code:
fastboot reboot
Wait until it boots up and power it off. Then boot to recovery mode: Volume down + Power button, wait for the "No command" sign
and keep pressed power button + tap Volume up to show the recovery menu.
To factory reset the device choose the following options:
Code:
Wipe data/factory reset
Wipe cache partition
7. Reboot!
Now you are all up! You can Reboot your device by choosing the Reboot device now option
and you will boot into your new WW firmware. If you changed to WW to unlock the bootloader now you are able to do it.
You can also download OTA updates for WW firmware or you can manually download it and place the firmware in the internal storage, reboot and a window will prompt asking to install the new firmware.
Special thanks
@xpirt
@A.S._id
Additional Information
Building...
Building...
Building...
Building...
Building...
i need ZS550KL CN -> WW :angel:
ken2006i said:
i need ZS550KL CN -> WW :angel:
Click to expand...
Click to collapse
Just follow the steps... I have uploaded CN firmware to AndroidFileHost. I have not been able to find CN stock recovery image... but you can make a dump of yours (and share it!).. Follow this guide https://forum.xda-developers.com/showthread.php?t=2450045
Help me, please! During flash recovery appear this message: FAILED (remote: partition flashing is not allowed
elenanole said:
Help me, please! During flash recovery appear this message: FAILED (remote: partition flashing is not allowed
Click to expand...
Click to collapse
Are you flashing the stock recovery? Try flashing the system partition, reboot and the go to fastboot mode to flash the recovery.
sebastiandg7 said:
Are you flashing the stock recovery? Try flashing the system partition, reboot and the go to fastboot mode to flash the recovery.
Click to expand...
Click to collapse
Yes I want to flash stock recovery but when I try to flash system image once it went well and then when I tried to flash recovery image it came a message partition is not allowed. Now appear partition is protected.
Please you can explain well what I have to do exsactly? Sorry for my english but I thank you for help me.
sebastiandg7 said:
Are you flashing the stock recovery? Try flashing the system partition, reboot and the go to fastboot mode to flash the recovery.
Click to expand...
Click to collapse
this is error
elenanole said:
View attachment 4266710 this is error
Click to expand...
Click to collapse
Show me the exact command you are using. You must do this:
1. Flash the system.img image in the system partiton.
Code:
fastboot flash system system.img
2. Reboot your device and wait until it boots up.
3. Reboot to fastboot mode.
4. Flash the stock recovery image to the recovery partition.
Code:
fastboot flash recovery <stock recoery name>.img
If you need more help you can find me in Telegram as @sebastiandg7
hello to all the guys, before proceeding to the flash, i want to make a backup of my (TIM) recovery because i do not find it. How can I do? Where was stock WW recovery taken?
P.S. My phone is not rooted
xtia87x said:
hello to all the guys, before proceeding to the flash, i want to make a backup of my (TIM) recovery because i do not find it. How can I do? Where was stock WW recovery taken?
P.S. My phone is not rooted
Click to expand...
Click to collapse
Are you able to boot twrp recovery? (Not installing it, check this thread)
sebastiandg7 said:
Are you able to boot twrp recovery? (Not installing it, check this thread)
Click to expand...
Click to collapse
Yes, I'm able to start twrp without installing it. From here how do I save my original recovery?
edit: Sorry I made a mistake i can't boot twrp without installing... The error: FAILED (remote: unlock device to use this command) is there a way to save the recovery without unlocking the bootloader?
Hi, I've been able to make the move finally! And when it gave me a mistake, partition is not allowed was why I had to do a factory reset and clean everything because it seemed to be insufficient memory. Sorry for my english and I hope that I help you
Some one have sotck recovery Z016D_CN please give me .tks
sebastiandg7 said:
Are you able to boot twrp recovery? (Not installing it, check this thread)
Click to expand...
Click to collapse
Do I need to flash the recovery and the firmware in one go? Is there any order I must proceed in? Are you sure I don't need to unlock the bootloader first? ASUS told me the bootloader unlock app also works with my TIM branded version.
---------- Post added at 12:14 AM ---------- Previous post was at 12:10 AM ----------
Also, what do I do if I already have TIM firmware with Android 7? Can I still follow the steps in the tutorial, or how should I proceed? Can/must I downgrade to Android MM, and if yes how? Thanks in advance.
What about dat to img by stupdroid.com? Which is newer? Does it make a difference if i want to get oreo system image?
I tried both tools and dat to img by stupdroid makes a system image with 3,65 GB but sdat2simg 3,54 GB...
Forgive My Poor English
It's For MI 8 SE (Not For MI 8)
A Chinese Developer done this
NEW VERSION IS HERE
The author's Email & Alipay Donate : [email protected]
The author's weibo :WEIBO
NEED UNLOCK BOOTLOADER and you can flash this recovery
Features and Notice:
1.Support Encrypt Data Partition
2.Support Full Size offical MIUI ROM
3.NEED UNLOCK BOOTLOADER and you can flash this recovery
4.You can ROOT(magisk is the default) or UNROOT in this recovery
...
More Partition in BACKUP/RECOVER
flash .bin & .mbn in Recovery(WARNING : DO NOT SELECT WRONG PARTITION)
...
and some other things
DOWNLOAD
DOWNLOAD LINK
HOW TO FLASH
Power off your phone and press volume down key and press power key to boot to Fastboot Mode
Download Fastboot tools...(Sorry I can't provide this tool)
open a command line(cmd or powershell in windows) and change directory to the directory where fastboot tool locate(cd PATH/TO/FASTBOOT/TOOL), then you can use fastboot simplely
use
Code:
fastboot flash recovery [PATH TO THE IMAGE FILE YOU DOWNLOADED]
to flash
then use
Code:
fastboot reboot recovery
to boot the recovery
IF YOUR BOOTLOADER IS LOCKED,but you wanna try it
You can use
Code:
fastboot boot [PATH TO THE IMAGE FILE YOU DOWNLOADED]
to boot the recovery(not flash recovery)
(not sure 100% success)
Do anything on YOUR OWN RISK
Pictures(and How to set language to English )
I'm not the Author,again..
the author is wzsx150 from LR.TEAM
If you are using Xiaomi MI 8 OR OTHER PHONE,DO NOT FLASH THIS RECOVERY IN THIS THREAD.
Pictures:
you can floow these steps to set language to English
Decrypt data partition (input your password or you cant mount data partition)
{
"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"
}
Next screen is 'Keep system partition read-only'
Left bottom is keep system RO,Right Buttom is change Language(no pic )
this is the Main screen and you can follow these steps to change Language to ENGLISH
Is there anyone, who flashed succesfully and booted in a custom rom with this recovery?
Flash the recovery is ok, but boot in a new rom with this is not working for me
You might have to disable secureboot, dm-verity
marcel112 said:
Is there anyone, who flashed succesfully and booted in a custom rom with this recovery?
Flash the recovery is ok, but boot in a new rom with this is not working for me
Click to expand...
Click to collapse
Are there custom roms yet for this device?
Puneeth 676797 said:
Are there custom roms yet for this device?
Click to expand...
Click to collapse
Unfortunately no, but as soon as development kicks in, I'll instantly buy this phone:victory:
Puneeth 676797 said:
Are there custom roms yet for this device?
Click to expand...
Click to collapse
Only one for SE is de Miui EU rom, but all the releases seem to have an issue with booting up
marcel112 said:
Only one for SE is de Miui EU rom, but all the releases seem to have an issue with booting up
Click to expand...
Click to collapse
Download EU rom again, they fixed the bootlopp today!!!
Superwitschi said:
Download EU rom again, they fixed the bootlopp today!!!
Click to expand...
Click to collapse
Are you kidding me!!
Yesterday i was trying to help them and i locked my bootloader by accident flashing using miflash.
Now have to wait 10 days to unlock again :crying::crying::crying::crying:
What about treble? We could use custom roms just like Redmi Note 5 pro with A partition support
balazs312 said:
What about treble? We could use custom roms just like Redmi Note 5 pro with A partition support
Click to expand...
Click to collapse
I have to assume this is the case. I'm planning to buy the phone within the next month.
This recovery did not work for me. I was able to flash it and run it, but could not install any roms after formatting.
Luckily the recovery made by 7to ended up working fine
https://pan.baidu.com/s/1bdVLZsydw22bkbNjCHh2CQ
oddhap said:
This recovery did not work for me. I was able to flash it and run it, but could not install any roms after formatting.
Luckily the recovery made by 7to ended up working fine
https://pan.baidu.com/s/1bdVLZsydw22bkbNjCHh2CQ
Click to expand...
Click to collapse
国内的机友吗？奇兔可以？
Hello, i was able to flash Xiaomi.eu 8.8.3 MIUI version with this TWRP, thanks author! But it seem to have problems with F2FS a was not able to format data and cache to F2FS, look at the attachment, any thoughts?
This version didn't work for flashing treble GSI, but the 7to version did.
q792602257 said:
IF YOUR BOOTLOADER IS LOCKED,but you wanna try it
You can use
Code:
fastboot boot [PATH TO THE IMAGE FILE YOU DOWNLOADED]
to boot the recovery(not flash recovery)
(not sure 100% success)
Do anything on YOUR OWN RISK
Click to expand...
Click to collapse
Has anyone tried to flash TWRP without unlocking the Mi8? (i'll try with v3.2.3)
Can I brick my phone if I try?
Does it include a function to resize system partitions?
If I get to flash it with the bootloader locked.... Will I be able to further flash any ROM without unlocking?
Can I also flash TWRP with MiFlash?
Regards
skanskan said:
Has anyone tried to flash TWRP without unlocking the Mi8? (i'll try with v3.2.3)
Can I brick my phone if I try?
Does it include a function to resize system partitions?
If I get to flash it with the bootloader locked.... Will I be able to further flash any ROM without unlocking?
Can I also flash TWRP with MiFlash?
Regards
Click to expand...
Click to collapse
Not Recommend to modify anything before unlock bootloader
If you just do without modify anything except /data/, it will be fine(try it without flash it)
This Recovery is for Mi8 SE(SE,NOT MI8), and THIS recovery doesnt have a function to resize system partition
you can flash mi8's twrp recovery without unlock(technically,NOT SURE 100% SUCCESS) flash it via recovery(boot the recovery ,and flash recovery in recovery )
You can flash any third party rom Until you unlock bootloader (or flash modified bootloader like this (not let you flash this))
You can flash any recovery via MiFlash(in fastboot(not sure) mode or in 9008 flash mode),it will not check your files(NOT SURE it will boot successfully)
q792602257 said:
you can flash mi8's twrp recovery without unlock(technically,NOT SURE 100% SUCCESS) flash it via recovery(boot the recovery ,and flash recovery in recovery )
Click to expand...
Click to collapse
I don't understand, Do I need to flash the recovery twice?
skanskan said:
I don't understand, Do I need to flash the recovery twice?
Click to expand...
Click to collapse
First you use
fastboot boot [recovery file]
to boot recovery(now the phone goes into recovery)
then use the recovery(you booted) flash the recovery fileinto your phone(you selected recovery file will replace the stock one)
TECHNICALLY, it will successfully flash in and work fine(not fine for miui's ota)
q792602257 said:
First you use
fastboot boot [recovery file]
to boot recovery(now the phone goes into recovery)
then use the recovery(you booted) flash the recovery fileinto your phone(you selected recovery file will replace the stock one)
TECHNICALLY, it will successfully flash in and work fine(not fine for miui's ota)
Click to expand...
Click to collapse
Do this work and can you flash gsi roms nevertheless bootloader is locked ?
Hadi2312 said:
Do this work and can you flash gsi roms nevertheless bootloader is locked ?
Click to expand...
Click to collapse
bootloader must be unlocked
Hello, Possessing two tablets of this brand, I was wondering if a custom recovery existed for this one, I can look everywhere on all the forums, Russian, English, etc ... But, I do not find.
If anyone can create one with this SOURCE CODE from the tablet that would be super nice.
I succeded to install twrp on my lenovo x606F.
1) extract recovery.img from a downloaded full firmware
2) download "Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek" v. 1.6 and use it to create a twrp.img from your recovery
3) flash your twrp image by adb:
fastboot flash recovery twrp.img
4) then flash an empty vbmeta.img that you find on team hovatek site by this command (Method 3 - Flashing vbmeta https://forum.hovatek.com/thread-32719.html ):
fastboot --disable-verity flash vbmeta vbmeta.img
5) reboot in recovery. You will receive a message that your partition is encrypted. tap "cancel" and follow the steps indicated on this page (Method 3 - Patching fstab in /vendor partition using TWRP + Text editor https://forum.hovatek.com/thread-30160.html ). You have to backup on your microsd your two fstab.* files in /vendor/etc folder and then modify as indicated. Then, by twrp, overwite them on your original files.
6) reboot in android and flash your original recovery
7) reboot in your stock recovery and make a full data erase. YOU LOST ALL YOUR PERSONAL DATA.
8) reboot in android and reinstall twrp recovery
9) reboot in your full working twrp recovery and check if it is all ok.
When you boot in your twrp, your screen is black, so you have to push power button to light your screen. You can fix it
by checking all three option in magisk manager (keep encryption, keep verity and recovey mode) and reinstall magisk root.
I'm not responsable for any damage on your device. Sorry for my english
zeldoox said:
3) flash your twrp image by adb:
4) then flash an empty vbmeta.img
Click to expand...
Click to collapse
Are you sure? TWRP Recovery Porter says that vbmeta.img must be flashed BEFORE twrp image.
I made several attempts to install twrp. When I succeeded, I installed vbmeta.img after twrp. But, during my previous attempts, I had already installed vbmeta. So, it is possible that the right steps are to install it first.
So, did anyone else succeed with these steps?
Shijune said:
So, did anyone else succeed with these steps?
Click to expand...
Click to collapse
I haven't tried, I'm afraid a bricked my tablets
Shijune said:
So, did anyone else succeed with these steps?
Click to expand...
Click to collapse
Nope. I tried 3-4 times, no way. The only result is that my tab's clock becomes late 11k seconds after each reboot
Guys someone has a working twrp image for android 10?
maks44 said:
Nope. I tried 3-4 times, no way. The only result is that my tab's clock becomes late 11k seconds after each reboot
Click to expand...
Click to collapse
I just rooted Lenovo M8 FHD TB-8705F (Android 9) using the Hovatek Method 3 guide:
flashed empty vbmeta
flashed boot.img created by Magisk
I tried the steps above with the TB-X606F on Android 10 (I used the lenovo recovery tool to rescue os and ended up with android 10) and I am unable to get it working. If I flash the generated twrp image and the vbmeta one (doesn't matter which order) and reboot recovery I get a black screen and no amount of pushing the power button gets the screen to turn on. I have not tried the boot.img file generated by Magisk yet. Anyone have any thoughts on this?
dpn982 said:
I tried the steps above with the TB-X606F on Android 10 (I used the lenovo recovery tool to rescue os and ended up with android 10) and I am unable to get it working. If I flash the generated twrp image and the vbmeta one (doesn't matter which order) and reboot recovery I get a black screen and no amount of pushing the power button gets the screen to turn on. I have not tried the boot.img file generated by Magisk yet. Anyone have any thoughts on this?
Click to expand...
Click to collapse
Can you share the download link for Lenovo recovery tool? Thanks
MisterVik said:
Can you share the download link for Lenovo recovery tool? Thanks
Click to expand...
Click to collapse
https://download.lenovo.com/consumer/mobiles/rescue_and_smart_assistant_v5.3.0.21_signed_setup.exe
Hi all,
I got my TB-X606F today and I'm having a hard time getting fastboot to work. I installed the official MTK driver from google and in my device manager its visible as Android ADB Interface
on my tablet I see the fastboot mode in the lower left corner.
fastboot devices shows nothing on cmd.
Any ideas?
OS Windows 10
MOD EDIT: See here- https://forum.xda-developers.com/t/...sb-driver-installer-tool-for-windows.3999445/
Смотрите здесь-https://forum.xda-developers.com/t/tool-latest-adb-fastboot-and-usb-driver-installer-tool-for-windows.3999445/
acocalypso said:
Hi all,
I got my TB-X606F today and I'm having a hard time getting fastboot to work. I installed the official MTK driver from google and in my device manager its visible as Android ADB Interface
on my tablet I see the fastboot mode in the lower left corner.
fastboot devices shows nothing on cmd.
Any ideas?
OS Windows 10
Click to expand...
Click to collapse
I have the same problem and can't proceed rooting for this reason.
adb works fine. Device is shown, commands like reboot into fastboot mode works fine. But "fastboot devices" does not show an entry.
I've tried to (re-) install the drivers CDC, VCOM, ... several times. I'v tried the "Latest ADB Fastboot and USB Driver installer tool for Windows". Doesn't work.
In device manager, Android Bootloader Interface is shown with an error.
{
"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"
}
Any ideas?
To fix this update your driver to Samsung's adb interfrance and it will work.
I got my TB-X606F rooted but struggle to install TWRP. I believe I'm on Android 10, the latest? I used [Hovatek] Mediatek Auto TWRP Recovery Porter V1.7a by Team Hovatek because I couldn't find version 1.6. I got the recovery.img directly from TB-X606F_S300007_200923_BMP.zip. I select Android 10 in the Android Version and output the TWRP recovery. Then I flashed and flashed the vbmeta (both the version from my zip file and the version from Hovatek. Then I flashed using multiple instructions. When I boot to recovery, it just gives the orange box screen then eventually fully boots to OS. Anything I'm forgetting?
I upgraded to Android 10. I installed again twrp by "Mediatek Auto TWRP Recovery Porter V1.7a". Android 10 version don't work well. "Pie Kernel 4.9.117" version works perfectly. The steps I follow are similar to my previous post. Insted of "forceencrypt" there is "forcefdeorfbe" in fstab.mt6765 file.
zeldoox said:
I upgraded to Android 10. I installed again twrp by "Mediatek Auto TWRP Recovery Porter V1.7a". Android 10 version don't work well. "Pie Kernel 4.9.117" version works perfectly. The steps I follow are similar to my previous post. Insted of "forceencrypt" there is "forcefdeorfbe" in fstab.mt6765 file.
Click to expand...
Click to collapse
How did you get twrp installed plz help
zeldoox said:
I upgraded to Android 10. I installed again twrp by "Mediatek Auto TWRP Recovery Porter V1.7a". Android 10 version don't work well. "Pie Kernel 4.9.117" version works perfectly. The steps I follow are similar to my previous post. Insted of "forceencrypt" there is "forcefdeorfbe" in fstab.mt6765 file.
Click to expand...
Click to collapse
Can you plz make a video of your steps?
Hello everyone! The camera works on courvus 12L. and cr droid 12L but the battery is big on it. on the courvus 12L the battery is normal.
install twrp and boot into the stock firmware and then boot into twrp again. install the firmware from under twrp as a system image.
enCorvus_vS1.0-Revolt-treble_arm64_ab_vndklite-Gapps-Alpha-0000.img.rar
drive.google.com
this collected all the necessary patches for magisk
patchi.rar
drive.google.com
after installing the firmware, you can flash this recovery.this is recovery-extract the folder from the archive and flash it via fastboot by clicking on the bat file-"1lineage 18.1 recowery.cmd"
lineage 18.1 recowery.rar
drive.google.com
and to run the firmware, be sure to flash it from under recovery
Permissiver_v5.zip
drive.google.com
Sony gallery,fotoredactor sony
Kasper666666 said:
{
"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
Hello kasper666666, that`s what I am looking for! It sounds like a fairy tail!
But.....
my knowledge about AOSP and Magisk is poor and even my trial to install magisk for my H8166 was not successfull.
I started from stock rom H8166_Customized DACHBLX_52.1.A.3.49-R6C and Magisk-v24.3 (or alternatively Magisk-v21.4).
Then I flashed system-squeak-arm64-ab-vndklite-gapps.img.
Error: "non supported Magisk-version"
Can you give any advice?
Thanks for your efforts!
I made a mistake. the camera works on firmware courvus 12 v 1.0.magisk does not work because you need to remove system / bin / phh su, and in build.prop in ro.build.fingerprint = you need to insert your own values, the camera also works on cr droid 12 but on it Big battery zhor with gapps.. https://sourceforge.net/projects/tipzbuilds/files/GSIs/CorvusROM/Alpha/20220315/ and be sure to flash it for the sensors to work https://drive.google.com/file/d/1-4cIIg8BNz1o1SlHEqamFKIprYcx9oOX/view?usp=drivesdk
der.lange said:
Can you give any advice?
Thanks for your efforts!
Click to expand...
Click to collapse
if you can’t do this, I will help you, only I will need your build.prop from vendor
Thank you for your quick response and offer!
My last trial was insatalling "magfisk-phh.apk"; but stuck with Sony-logo.
it was not necessary .... I have a ready-made file, now I will upload it to disk and send a link to the finished firmware
put the usual magisk 24.3. install twrp and boot into the stock firmware and then boot into twrp again. install the firmware from under twrp as a system image
then you can put recovery lineage and it will work
lineage-18.1-20220113-recovery-aurora.img
drive.google.com
put all the files in the topic header
sorry, but I can´t see any attachment....
bytheway: will your solution enable the use of the stock xperia camera? As far as I know Bionic does not allow the use of their cameradrivers for the further development.
all attachments open. camera tama 0.3.0 from denny trank works it is in patchi.rar
it´s a hard piece of work for me and an end not to be seen...
1. flash stock with newflasher: ok
2. flash magisk_patched boot.img: ok
3. install twrp
3.1 fastboot boot twrp-kang.img; adb push twrp-kang.img /; install recovery ramdisk; reboot into recovery (with decryption); reboot system doesn´t work, boots into recovery instead!! Flashing system-squeak.img immediately stops with error.
3.2 fastboot boot twrp-aurora.img; boots but no input possible, dead screen
So what I`m doing wrong? Is there another better twrp?
download the archive. extract the twrp-akari.img file, copy it to the memory card. you must have the official firmware, connect the phone to the computer in fastboot and in the folder that you downloaded, click first on 1vbmeta.cmd then on 2twrp.cmd and wait until the phone reboots into twrp. in twrp select advanced then install recowery ramdisk and select the file on the memory card twrp-akari.img and wait for the firmware to finish. then reboot into the system. you can go to twrp and flash the firmware from twrp in system image. flash recovery lineage 18 on fastboot...magisk flash from under recovery lineage 18
xz2p dual TWRP 3.4.0.rar
drive.google.com
sorry, where can I find vbmeta.cmd and twrp.cmd?
xz2p dual TWRP 3.4.0.rar
drive.google.com
sorry
still no end to be seen!
1. install stockrom (newflasher)
2. boot and install ramdisk recovery (twrp-akari.img)
3. flash system.img via recovery or fastboot flash system_a system.img
4. reboot system: SONY-Logo stuck
what´s wrong with me?
2. boot and install ramdisk recovery (twrp-akari.img)!system reboot required!!3. flash system.img via recovery!! no fastboot!!!!4.flash Permissiver_v5.zip..5.reboot system
That´s exactly what I have done. Permissive-zip: too large; aborted....
I think, there´s not enough room for both twrp and permissive in the ramdisk and I dont know howto increase size. If I change the sequence of the installation twrp-img is too large.
"new image larger than boot partition. Aborting"
did you flash it from twrp.? flash recovery lineage 18 and flash permissiver from it
"It′s been a hard day's night
And I′ve been working like a dog" (Beatles)
Finally successfull!
I highly appreciate your work! Thank You!!
My steps installing android 12
1. install stockrom H8166_Customized DACHBLX_52.1.A.3.49-R6C (newflasher)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2. boot and install ramdisk recovery (twrp-akari.img)
3. reboot recovery ; reboot system ; reboot recovery again
4. push system.img /sdcard and install
5. replace ramdisk recovery with lineage-18.1-20220113-recovery-aurora.img
6. flash Permissiver_v5.zip from it
7. flash Magisk-v24.3.zip
8. reboot system
9. install camera-0.3.0-tama.zip from patchi.rar via magisk
the original SONY Xperia camera is working!!
Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
suhuf said:
Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
How exactly do we
suhuf said:
Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Just flash this via fastboot?
scorpio76r said:
How exactly do we
Just flash this via fastboot?
Click to expand...
Click to collapse
fastboot flash boot boot.img
suhuf said:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
If you're sure the version is global, it should work.
{
"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"
}
scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
Read the explanation and remove the original boot file and fastboot, the phone will boot.
Put the same boot file in the download section of the phone and patch it with magisk, then upload the patched file to the phone with fastboot process.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
Apologies but I'm confused by the steps in the posts above... Can someone post a brief step-by-step guide for this? Thanks!
[EDIT] nevermind, extracted and patched on my own, thanks!
scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
I also got stuck on fastboot. Any solution will be appreciated.
Edit: Had to restore device with MSM Download Tool.
Hi, just updated to official OOS12 and hate it, it appears it also re locked my bootloader which was unlocked, how do I unlock it again? do I follow the same steps? I want to go back to OOS11 and start flashing custom roms
edit: just checked on fastboot mode. it says unlocked in red letters. would still like to flash magisk!
cjvzla said:
Hi, just updated to official OOS12 and hate it, it appears it also re locked my bootloader which was unlocked, how do I unlock it again? do I follow the same steps? I want to go back to OOS11 and start flashing custom roms
Click to expand...
Click to collapse
You sound like me a week ago. Best bet is to msm your phone and start from scratch. Bring your phone up to 11.10.10 then go with the Jaguar rom. It has March security patch, call record and developers literally responds within a few minutes of a post or question.
scorpio76r said:
You sound like me a week ago. Best bet is to msm your phone and start from scratch. Bring your phone up to 11.10.10 then go with the Jaguar rom. It has March security patch, call record and developers literally responds within a few minutes of a post or question.
Click to expand...
Click to collapse
hi, just checked and I still have the bootloader unlocked, which means I could flash a recovery right? I haven't flashed stuff in android phones in a while and I'm a bit rusty, where should I go first?
cjvzla said:
hi, just checked and I still have the bootloader unlocked, which means I could flash a recovery right? I haven't flashed stuff in android phones in a while and I'm a bit rusty, where should I go first?
Click to expand...
Click to collapse
Yes use fastboot twrp image from the official twrp thread. Then install twrp installer.
krakout said:
Apologies but I'm confused by the steps in the posts above... Can someone post a brief step-by-step guide for this? Thanks!
[EDIT] nevermind, extracted and patched on my own, thanks!
Click to expand...
Click to collapse
hi! how did you extracted and patched? did you follow the video? cause I can't understand what hes saying. can you leave me a step-by-step? thanks. I'm on OOS12, bootloader unlocked
cjvzla said:
hi! how did you extracted and patched? did you follow the video? cause I can't understand what hes saying. can you leave me a step-by-step? thanks. I'm on OOS12, bootloader unlocked
Click to expand...
Click to collapse
I just sent you a personal message with a link that will help you out.
Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.
krakout said:
Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.
Click to expand...
Click to collapse
Yes, using windows 10 pc.
krakout said:
Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.
Click to expand...
Click to collapse
hi thanks for the tutorial, managed to extract the OOS12 stock boot img and patched it with magisk 24, but when I connect in fastboot mode and check with the fastboot devices command I get nothing, and nothing on device manager either. even tho my bootloader is unlocked and fastboot drivers are installed, the pc doesnt seem to "see" my phone?
the adb devices command does show my phone when connected and turned on.
That's a bit tricky and I'm not sure why it would do that, never encountered it... Tried restarting adb?
krakout said:
That's a bit tricky and I'm not sure why it would do that, never encountered it... Tried restarting adb?
Click to expand...
Click to collapse
looked for the latest drivers and installed those, now my devices does show up with the fastboot devices command! do I test the patched boot img first? and did you flash it normally or did you use fastboot flash boot_a and fastboot flash boot_b for the a/b partitions?