How to Downgrade Android Version in Samsung Devices if Device is in Higher BineryView attachment Samsung-Logo-MSP.webp
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers
Note :-
Samsung binery is impossible to downagrade. This method will do install old stock as a custom rom (signature removed stock rom). So this method only can downgarde android version. This method cannot downgrade modem or radio or bootlooder such as (aboot,lk,non-holes) like critical images. if you try that it will dead your device
Click to expand...
Click to collapse
Not Tested in All Devices. So I Don't know this method is working for all samsung devices. Proofs are at the end. You Have to try and tell
What you need
Latest binery of stock rom that you need to downgrade
Bootloader Unlocked Device
Lz4 Unpacker
Simg2img.exe
Hxd
Android Image kitchen
Odin
7zip
Windows Computer
If you have super.img device shipped with Android 10 or Android 10+You must have unlocked bootloaderIf your device cannot use magisk this method will not work for you. (A20s user cannot do this)
1. Unlock your device bootloader2. Download the Latest binery of stock rom that you need to downgrade (samfw)3. Extract the whole Ap.....tar.md5Get all boot.img.lz4 recovery.img.lz4 super.img .lz4(vendor.img.ext4.lz4 and system.img.ext4.lz4)
{
"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"
}
4. Convert .lz4 to imgGrag and drop lz4 file to lz4.exe5. Then Patched the boot.img with magisk and unpack and repack recovery.img using android image kitchen (aik)6. Then paste simg2img.exe to where converted super.img located.
7. Then open cmd from there and type simg2img super.img super.rawthen you will get a super.raw
8. Open HXD and grag and drop super.raw to hxd9. Then CTRL+F and search all the U number of the firmware you downlodedAccording to me it is U4
9. Then Find a phases like this and fill all phases with zero bytes (there should be more than one)
10. Then Save it and remove the super.raw.bak11. Then Rename the super.raw to super.img and make tar with 7zip including patched boot.img recovery.img and super.img12. Flash it and Format data
Patched vbmeta is not essential due to magisk patched boot.img
If you Have System.img and Vendor.img Device Shipped with Android 7 8 91.Do all the steps untill number 62.Then convert system.img.ext4 and vendor.img.ext4 to raw by open cmd then, simg2img.exe system.ext4.img.raw and same to vendor3.Open both System.ext4.img.raw form Hxd and Countinue with step 94.Then save Both vendor and system and delete the .bak files5.Then rename system.img.ext4.raw to system.img.exe4 and vendor.img.ext4.raw to vendor.img.ext46.Then Convert to Lz4 by open cmd and lz4 -1 system.img.ext47.Then Make tar using Magisk patched boot.img and repacked recovery.img and system.img.ext4.lz4 and vendor.img.ext4.lz48. Flash and wipe Data
Patched vbmeta is not essential due to magisk patched boot.imgProof Tested Devices,
Samsung Galaxy M01 (Qualcomm)
Downgrade Android 12 to android 10 (u4 to u3)
Samsung Galaxy A71 Qualcomm
Android 13 to Android 10 (U8 to U3)
Updates
Some users said they cannot flash super.img in a51 and s20 exyons version. May be this method will not work for exyons. I dont know that need to test more
Downgrade success for s20 fe 5g qcom using this method
Still not tested on MTK
Video Tutorial
Remove Signature from Super or System/Vendor
DownloadsHxd
This method also can use for update android version without upgrading binery version.
Interesting.. I'll try it when I get back my pc
tested in my samsung a52 5g. Downside is, on-screen fingerprint sensor always not responding
oznear said:
tested in my samsung a52 5g. Downside is, on-screen fingerprint sensor always not responding
Click to expand...
Click to collapse
Try with replace vendor/firmware from u4 stock (dosent depend on android version)
Hi, If I flashed it through Odin, do I still need to supply the BL, CP, CSC? Thanks in advance.
A10 -> A9 9 on SD S10: the flashing itself works but device's now stuck on booting - cannot get to A9 recovery
jq555888 said:
Android 10 -> Android 9 on snapdragon S10: the flashing itself appeared to work but device's now stuck on booting - cannot get to Android 9's recovery for some reason which I suspect is due to a different partition layout (device's shipped with Android 9); tried to erase userdata with Android 10's recovery but still can't get it to finish booting. Any ideas?
Click to expand...
Click to collapse
You used latest version of android 9?
smiley9000 said:
You used latest version of android 9?
Click to expand...
Click to collapse
Yeah - this was last version of A10 - A9
jq555888 said:
Yeah - this was going from G9700ZHU4DTL2 (last version of Android 10) to G9700ZCS2ASJU (last version of Android 9)
Click to expand...
Click to collapse
stuck in android boot animation?
smiley9000 said:
stuck in android boot animation?
Click to expand...
Click to collapse
yes! it's like the startup screen
jq555888 said:
yes! it's like the startup screen where it usually says the phone's model (with the text "this phone is not running official software"). it's the one after pressing the side button, but not the "SAMSUNG" screen.
Click to expand...
Click to collapse
enable usb debugging and try to get logs
smiley9000 said:
enable usb debugging and try to get logs
Click to expand...
Click to collapse
thank you! any way to achieve this by modifying the official A9 rom?
jq555888 said:
thank you! any way to achieve this by modifying the official A9 rom?
booting to twrp for A9 also fails not sure if it's a parition problem but A10 twrp works
Click to expand...
Click to collapse
maybe due to kernel
hello ! i have a problem with Android image kitchen , when i click repackimg.bat he say me
Fichier introuvable
Paramètre incorrect.
Android Image Kitchen - RepackImg Script
by osm0sis @ xda-developers
Packing ramdisk (as root) . . .
Windows sudo required but not found.
*** Reinstall Android Image Kitchen, then add ***
*** sudo.exe to your antivirus exceptions! ***
Error!
how can i fix this pls?
Thanks for taking the trouble to make this thread @smiley9000
Anyone tried this on s10e exynos variant with android 12 - downgrade to android 10 ?
Related
Reason for edit: Change title so more users can find this method since for now TWRP is working but not to root
Click to expand...
Click to collapse
Hello fellow XDA users,
On this post I'm going to explain how I got root on my own Nokia 8 TA-1004, please be patient because this is my first thread under any development section!!
I've been following all threads here on XDA and for the last few days its like a boom of new information, yesterday a Senior Member provided me with the Unlock Key generated with my IMEI1 and the phone's bootloader is now unlocked:
{
"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"
}
Now the next logical part I would be installing TWRP to flash the magisk flashable zip to the phone, but there is no TWRP built to our phones (old information, there is now an official TWRP build)..
To my surprise there is this thread that offers boot images already patched with root ( @nummerok are they patched under magisk?), I tried flashing first with:
Code:
fastboot boot NB1-0-484A-00WW-boot.img
But it did not worked, no matter what the installed Magisk Manager would not find the Magisk Module on the system.
Then I found out that some users were getting root but with the problem of losing wifi connectivity, that was found to be the fault of the phone having the March Security Patch (00WW_4_84A_SP01) while flashing the boot image of the phone with the February Security Patch (00WW_4_84A).
As of this new A-B partition scheme on Android, when your boot image does not pass dm-verity it restores the older version automatically (Am I right on this point?? can please someone confirm?!)
Since my phone WAS on the march patch I saw no other option but to wait someone to grab the march boot image to patch it Magisk Manager and get root.
Buut since my generation doesn't like to sit and wait I found that there was a way to roll back to the previous firmware!
What I did was, run this code below on adb to know which slot my phone was:
Code:
adb shell getprop ro.boot.slot_suffix
Then take note of the slot and run:
Code:
adb reboot bootloader
After the device starts up in Download Mode you need to switch to the other boot slot. Just run:
Code:
If you are currently on slot A, type this: [B][I]fastboot --set-active=_b[/I][/B]
Or on slot B type this: [B][I]fastboot --set-active=_a[/I][/B]
You should see something like this:
Code:
Setting current slot to 'a'... OKAY [ 0.046s] finished. total time: 0.046s
Now run the code below and cross your fingers!
Code:
fastboot reboot
Once the phone has booted, check in Settings/System/About Phone if your Android security patch level has downgraded to the February one and proceed to the next step.
I've downloaded the full NB1-484A-0-00WW-B03.nb0 firmware from @blackpanther0582 thread under the google drive link and extracted the boot image using the tool made by @heineken78 available over here (be sure to have lots of ram available for the unpack process :fingers-crossed.
With the file NB1-0-484A-00WW-boot.img at hand I've copied it to the Nokia 8 internal storage and ran Magisk Manager to patch it, follow instructions here under Via Magisk Manager (Only support v14.0+) part.
Now grab the patched_boot.img file provided by Magisk from the phone and save it (adb pull or whatever) to your pc and run these commands:
Code:
adb reboot bootloader
After the phone boots up in Download Mode run:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
With that done, after the boot you can open Magisk Manager to see it fully installed and later on install some root checker app just to be sure of the sucess of your rooting:
Split-screen to the rescue lol
This Nokia 8 is officially rooted but with the previous February patch and I'm itching to install the March OTA provided by @2WildFirE here, any thoughts on that? What about the official system update that still lists the 2018-03 security patch? Would any of which work?
And that is all for now folks!
I would like to thank @the_laser @heineken78 @topjohnwu @blackpanther0582 @nummerok and many others in this invaluable path to learning more about this phone and the Android system in general!
Good Luck!!
Reserved
Nice, this will help some people to understand.
Powered by Nokia 8 with open bootloader
2WildFirE said:
Nice, this will help some people to understand.
Click to expand...
Click to collapse
That's the idea @2WildFirE !
btw just to make things clear, the official system update is running for like 10 hours and it seems it's not going anywhere.. would I get success by doing the march update thru the zip you've found?
Yep was working fine here, to bring my wifi back, but lost root [emoji6] what we Really need is twrp and or a method to extract the boot.img from the *. Bin file included in the update zip.
Powered by Nokia 8 with open bootloader
I used your method, but it doesn't work.
When I type "fastboot --set-active=_a",it shows "fastboot usage". I try it fifth time, but it still. I haven't deal anythings about root Nokia8, is it the reason ?
contrahelix said:
I used your method, but it doesn't work.
When I type "fastboot --set-active=_a",it shows "fastboot usage". I try it fifth time, but it still. I haven't deal anythings about root Nokia8, is it the reason ?
Click to expand...
Click to collapse
It should work only if you have your bootloader unlocked @contrahelix
You might get it unlocked officially by Nokia or wait for an alternative method.
Also you should update your adb/fastboot tools, then you would get the right error message telling you about the still locked bootloader!
On this post I'm going to explain how I got root on my own Nokia 8 TA-1004, please be patient because this is my first thread under any development section!!
Click to expand...
Click to collapse
I have a TA-1012 i assume it won't work for me?
For everyone with unlocked bootloader, this is the method to root without TWRP !
Now that we have unlocked bootloaders, is it possible that this can be updated to simply use the latest image instead of rolling back? Or are we still rolling back...
Raithlin said:
Now that we have unlocked bootloaders, is it possible that this can be updated to simply use the latest image instead of rolling back? Or are we still rolling back...
Click to expand...
Click to collapse
Still have to rollback to official image.. you cannot upgrade with patched img unfortunately
As u have unlocked bootloader and installed magisk i have a question .
Is it worth to unlock bootloader and install magisk.......?
And one more any custom rom available for nokia8 ta1004.......?
شرا
{
"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"
}
Hello, I've been making a catalog with a lot of files related to the G7.
That includes boot, system and vendor images as well as some KDZ files that i need.
You can probably find most of the stuff you need here.
The link: https://drive.google.com/open?id=1bZwJVypZZLT6m9r_N2u1rJAxCz8kdiH2Folder content and how to navigate:
Boot images
This folder contains some boot images for the g7 (specifically G710EM)
If the image has _patched in its name it means that it has Magisk included.
If the image has twrp_ in its name it means that it has TWRP included.
If it has both then it means that it has TWRP and Magisk included.
"TWRP_Pie.img" is for phones that run custom ROMs (9.0 + 8.1) with 8.0 vendor (old guide) (10b-10f)
"TWRP_RealPie.img" is for phones that run custom ROMs (9.0 + 8.1) with 9.0 vendor (new guide) (20c)
Click to expand...
Click to collapse
KDZs
This folder mostly contains KDZs for the G710EM but it also contains some KDZs from G710N and V405/409 (LG v40)
Still that doesn't mean that its finished because KDZ files take a lot of storage and i don't have terabytes of it.
Theres also LGUP installers and a LGUP dll for the G7 in "LGUP" folder.
ANd of course a lonely driver installer in the "Drivers" folder.
Click to expand...
Click to collapse
Other files
Nothing to care about. Move on.
Click to expand...
Click to collapse
Stock images
It contains plenty of images for different firmware versions (Mostly for the G710EM but its specified when its not from it).
It has System images, Vendor images, Boot images, apple images and some other not specified.
Everything completly pulled from stock.
Click to expand...
Click to collapse
Vendors
This folder contains patched vendor images for the G7.
"vendor_10b_securityoff.img" was the first vendor to be used for AOSP now we have a new guide with new files.
"vendor_10k_securityoff.img" same as above but for v10k firmware.
"vendor_gsi.img" this vendor is based on 20c G710N and its used for AOSP (new guide)
Click to expand...
Click to collapse
If you have any questions please ask them here!
Thank you!
The boot_v10s.img in v10s folder is unpatched? I've to flash boot_10s-magisk.img in order to root the device?
pi3troz said:
Thank you!
The boot_v10s.img in v10s folder is unpatched? I've to flash boot_10s-magisk.img in order to root the device?
Click to expand...
Click to collapse
Yeah
LameMonster82 said:
Yeah
Click to expand...
Click to collapse
Thanks mate
Which one do I need to get magisk on Korean Pie upgraded G710EM model?
Michiel0912 said:
Which one do I need to get magisk on Korean Pie upgraded G710EM model?
Click to expand...
Click to collapse
Try TWRP_RealPie.img
Tried it. Did a data format to have access to data in TWRP but after booting I get a decryption unsuccessful message and keeps looping.
Michiel0912 said:
Tried it. Did a data format to have access to data in TWRP but after booting I get a decryption unsuccessful message and keeps looping.
Click to expand...
Click to collapse
Install back stock boot image. While TWRP works on stock data must stay untoched
Edit: you can download magisk manager and manually patch the stock boot image
Ok, I patched the boot image and everything is working. I will send you a link so you can put it on your drive. It is stock 20c boot with Magisk patch.
https://1drv.ms/u/s!AnYjRY0QyVw8jzHXdUC04lE9R5ER
Michiel0912 said:
Ok, I patched the boot image and everything is working. I will send you a link so you can put it on your drive. It is stock 20c boot with Magisk patch.
https://1drv.ms/u/s!AnYjRY0QyVw8jzHXdUC04lE9R5ER
Click to expand...
Click to collapse
No need. I have some boot images on my PC already patched. Also most people that are using this tutorial can't really use it
Can we use lg v40 kdz on lg g7?
sdiown said:
Can we use lg v40 kdz on lg g7?
Click to expand...
Click to collapse
No
I can't understand the steps that I have to do in order to get root on stock Korean Pie.
Do I have to follow this ones?
1. Download the patched Boot.img
2. Reboot to fastboot (and unlock bootloader????)
3. Flash the new boot.img with the commands fastboot flash boot_a pathtoboot.imghere and then fastboot flash boot_b pathtoboot.imghere
4. Reboot and install Magisk Manager Apk
delpere said:
I can't understand the steps that I have to do in order to get root on stock Korean Pie.
Do I have to follow this ones?
1. Download the patched Boot.img
2. Reboot to fastboot (and unlock bootloader????)
3. Flash the new boot.img with the commands fastboot flash boot_a pathtoboot.imghere and then fastboot flash boot_b pathtoboot.imghere
4. Reboot and install Magisk Manager Apk
Click to expand...
Click to collapse
Yes that's correct
Edit: right now there's no magisk patched Korean pie boot image on my gdrive so I will make one later. Don't install any other one. It will not work
I have seen that you uploaded the patched boot image for the G710N on Google Drive.
Can I use that for my G710EM?
delpere said:
I have seen that you uploaded the patched boot image for the G710N on Google Drive.
Can I use that for my G710EM?
Click to expand...
Click to collapse
If the software version matches then yes
Is anyone working on a bootloader unlock for other G7 models? I have a G7+ (LG710EAW)
What about installing only the TWRP on Korean Pie?
Do I need only to use this command?
HTML:
fastboot --set-active=a flash boot_a [TWRP_RealPie.img full path]
Thank you so much.
delpere said:
What about installing only the TWRP on Korean Pie?
Do I need only to use this command?
fastboot --set-active=a flash boot_a [TWRP_RealPie.img full path]
Thank you so much.
Click to expand...
Click to collapse
Yeah
An excellent compilation of files - everything what's posible to been necessary in one place ... But there is a question: when to expect boot v10t with magisk?
Anyone know how to do it?
Either by Magisk or by SuperSU.
More info here:
How to Root Infinix Note 8 Without PC & Via Magisk
Are you waiting to Root Infinix Note 8 Smartphone? Follow our tutorial to guide you through the process to gain Superuser privileges without TWRP Recovery
www.thenextdroid.com
jwoegerbauer said:
Either by Magisk or by SuperSU.
More info here:
How to Root Infinix Note 8 Without PC & Via Magisk
Are you waiting to Root Infinix Note 8 Smartphone? Follow our tutorial to guide you through the process to gain Superuser privileges without TWRP Recovery
www.thenextdroid.com
Click to expand...
Click to collapse
I try everything its not working, even using kingoroot pc
first...did you unlock the bootloader?how to unlock bootloader on infinix note 8 ?
kalingkx said:
first...did you unlock the bootloader?how to unlock bootloader on infinix note 8 ?
Click to expand...
Click to collapse
Yeah we must unlock bootloader frist. But there is no driver for infinix note 8 to connect fastboost
Amazdd said:
Yeah we must unlock bootloader frist. But there is no driver for infinix note 8 to connect fastboost
Click to expand...
Click to collapse
The Infinix Note 8 is based on Mediatek Helio G80 chipset, hence you must install Android USB Driver suitable for this chipset.
More info here:
Download MTK USB All Drivers for Windows (Official MediaTek Drivers)
Download the latest version of MTK USB All Drivers (MediaTek Driver) to connect any MediaTek Device with the Windows Computer.
androidmtk.com
up..pls. help .,anyone know how to root infinix note 8?
do it your own risk..im not responsible for any happening to your unit...
Back Up....Back up!
activate OEM unlocking in Developers Option and use this file to unlock.
https://dropmb.com/u7agJ
Disable DMverity or flash the IN8 with empty vbmeta(img) before rooting!!!! to prevent bootlop....
then use magisk manager to root, google the procedure......
install magisk apk to IN8
copy boot.img from your back up firmware to IN8 (or get from hovatek)
now patch this boot.img using magisk.
copy the patched boot.img to the folder of the extracted file i attached and flash it in fastboot mode..
Reboot....
and your done..
credits to :
magisk manager devs.
root cheker devs.
Hope this help ...
{
"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"
}
is there an easy solution for Rooting the device?
kalingkx said:
do it your own risk..im not responsible for any happening to your unit...
Back Up....Back up!
activate OEM unlocking in Developers Option and use this file to unlock.
https://dropmb.com/u7agJ
Disable DMverity or flash the IN8 with empty vbmeta(img) before rooting!!!! to prevent bootlop....
then use magisk manager to root, google the procedure......
install magisk apk to IN8
copy boot.img from your back up to IN8 (or get from hovatek)
now patch this boot.img using magisk.
copy the patched boot.img to the folder of the extracted file i attached and flash it in fastboot mode..
and your done..
credits to :
magisk manager devs.
root cheker devs.
Hope this help ...
View attachment 5283257
Click to expand...
Click to collapse
Wow, but scare'd to do it
yes it is risky...i exprienced some bootloops and deadboot while rooting my IN8 til i got that procedure, but no worries, if i have GSM tools that will revived it,
kalingkx said:
do it your own risk..im not responsible for any happening to your unit...
Back Up....Back up!
activate OEM unlocking in Developers Option and use this file to unlock.
https://dropmb.com/u7agJ
Disable DMverity or flash the IN8 with empty vbmeta(img) before rooting!!!! to prevent bootlop....
then use magisk manager to root, google the procedure......
install magisk apk to IN8
copy boot.img from your back up to IN8 (or get from hovatek)
now patch this boot.img using magisk.
copy the patched boot.img to the folder of the extracted file i attached and flash it in fastboot mode..
and your done..
credits to :
magisk manager devs.
root cheker devs.
Hope this help ...
View attachment 5283257
Click to expand...
Click to collapse
Can you share the empty
kalingkx said:
do it your own risk..im not responsible for any happening to your unit...
Back Up....Back up!
activate OEM unlocking in Developers Option and use this file to unlock.
https://dropmb.com/u7agJ
Disable DMverity or flash the IN8 with empty vbmeta(img) before rooting!!!! to prevent bootlop....
then use magisk manager to root, google the procedure......
install magisk apk to IN8
copy boot.img from your back up to IN8 (or get from hovatek)
now patch this boot.img using magisk.
copy the patched boot.img to the folder of the extracted file i attached and flash it in fastboot mode..
and your done..
credits to :
magisk manager devs.
root cheker devs.
Hope this help ...
View attachment 5283257
Click to expand...
Click to collapse
Can you please share the infinix note 8 empty vbmeta(img)
here
kalingkx said:
here
Click to expand...
Click to collapse
Thank you
kalingkx said:
here
Click to expand...
Click to collapse
Thank you
kalingkx said:
here
Click to expand...
Click to collapse
Hi,
Can I use the same vbmeta.img for Infinix Note 8i? Please help? Struggling to find any solution here.
Well, just putting it here. If anyone wonder where's the TWRP for this particular device, here it is: https://forum.xda-developers.com/t/unofficial-twrp-3-6-1-for-infinix-note-8-x692.4441931/
リェンーゆく said:
Well, just putting it here. If anyone wonder where's the TWRP for this particular device, here it is: https://forum.xda-developers.com/t/unofficial-twrp-3-6-1-for-infinix-note-8-x692.4441931/
Click to expand...
Click to collapse
Òwó i try not to be dumb but, is it need the same version of recovery file? Like boot img does?
Amazdd said:
Òwó i try not to be dumb but, is it need the same version of recovery file? Like boot img does?
Click to expand...
Click to collapse
You don't need to. However if you use newer boot kernel and you've formatted the /data partition on that kernel, it will became unreadable in TWRP. This is sadly an intended behaviour of F2FS. You need to unmount the /data partition before quitting TWRP to avoid corruption.
If your boot kernel is older (or the same), those won't happen and you still can access the /data partition normally
how to make normal again help me
I attempted to root my Pixel 4a with Android 12 using Magisk. While executing commands, I received an error stating the partition was not found. I dont have the latest version of Andriod. My phone debugger mode is checked.
XZNZI said:
I attempted to root my Pixel 4a with Android 12 using Magisk. While executing commands, I received an error stating the partition was not found. I dont have the latest version of Andriod. My phone debugger mode is checked.
Click to expand...
Click to collapse
Not a lot to go on from you description,, So is this what's been done? Bootloader unlocked, oem unlocking toggled, magisk installed,,, magisk patched boot.img available and the adb command sent "fastboot flash boot patchedboot.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"
}
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
XZNZI said:
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
Click to expand...
Click to collapse
What version of ADB Platform Tools are you using?
Are you absolutely sure you're using the right firmware?
Why did you downgrade?
Are you following one of the several guides? If not, you should be.
XZNZI said:
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
Click to expand...
Click to collapse
Maybe some of the steps on this page might help you:
[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
EngineerMind said:
Maybe some of the steps on this page might help you:
[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
Click to expand...
Click to collapse
That guide is very out of date.
V0latyle said:
That guide is very out of date.
Click to expand...
Click to collapse
It is, but since he mentioned Android 10, some of it might help him with his issue because it relates to Andorid 10
XZNZI said:
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
Click to expand...
Click to collapse
You could make sure your platform tools are upto date from here https://developer.android.com/studio/releases/platform-tools then try again, you could also try Pixel Flasher, it works great, slight learning curve but all in all pretty easy,
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
hammered58 said:
You could make sure your platform tools are upto date from here https://developer.android.com/studio/releases/platform-tools then try again, you could also try Pixel Flasher, it works great, slight learning curve but all in all pretty easy,
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
Click to expand...
Click to collapse
I download a mini version of the andriod tools and rooted my phone. I attempted to flash TWRP 3.5 for Android 10 for Pixel which failed. Error: Not allowed to flash to recovery. Debugging on Unlocked and rooted..
Hello everyone, I want to install TWRP Custom Recovery on my Phone. But, when I tried some videos, all of them aren't working. But why?
I tried the following:
fastboot boot recovery.img (resulted: FAILED (status read failed (Too many links)))
fastboot flash recovery recovery.img (resulted: FAILED (remote: This partition doesn't exist))
I tried also,
fastboot flast boot recovery.img (resulted: bootloop)
I checked many comments, most of them saying that it doesn't work, others say that there is no recovery partition
Now my recovery partition is gone, leaving only to restart instead.
So, is there something I can do about it? Is there a solution for this problem that I'm facing? Looking forward to replies.
My phone is a Xiaomi Redmi 10 (non-2022 edition), codenamed selene.
And this that I am using is the unofficial TWRP (ver 3.6.1).
Thank you.
Update: Nevermind, the recovery is there. Regular Xiaomi recovery.
dasdsad1 said:
Hello everyone, I want to install TWRP Custom Recovery on my Phone. But, when I tried some videos, all of them aren't working. But why?
I tried the following:
fastboot boot recovery.img (resulted: FAILED (status read failed (Too many links)))
fastboot flash recovery recovery.img (resulted: FAILED (remote: This partition doesn't exist))
I tried also,
fastboot flast boot recovery.img (resulted: bootloop)
I checked many comments, most of them saying that it doesn't work, others say that there is no recovery partition.
Now my recovery partition is gone, leaving only to restart instead.
So, is there something I can do about it? Is there a solution for this problem that I'm facing? Looking forward to replies.
My phone is a Xiaomi Redmi 10 (non-2022 edition), codenamed selene.
Thank you.
Click to expand...
Click to collapse
Please respond quickly.
Xiaomi.eu post:
Couldn't install TWRP recovery on Redmi 10.
Yo guys, I have a feeling about this, but TWRP Can't. Be. Installed. On. My. Redmi 10? Because I said so. So, I wanted to install TWRP, but there was a problem. See, I tried tens of hundreds of videos, but to no avail. Tried commands like: fastboot boot recovery.img fastboot flash recovery...
xiaomi.eu
On which rom is the phone(Android version) and which Twrp(link)?
NOSS8 said:
On which rom is the phone(Android version) and which Twrp(link)?
Click to expand...
Click to collapse
MIUI Global 13.0.10 Stable (SKUIDXM)/Android 12, Indonesian region ROM
TWRP link: https://unofficialtwrp.com/twrp-3-6-1-root-redmi-10/?amp#google_vignette
Model: Redmi 10 (codename selene, non-2022 version), 21061119DG
From UNofficialtwrp.com
Tried various tools. XiaoMiTool V2 said unknown error, XiaoMiFlash.exe is only for flashing ROMs, and REDMI 10 2022 (SELENE), only for MIUI 12.5 (from TAPIN RECOVERY INSTALLER).
Are you sure of the version?
SELENE 21061119AG, 21061119AL, 21061119BI, 21121119SG, 21121119VL, 22011119TI
Not sure this TWRP works on A12, did you flash the VBmeta as shown on the link?
NOSS8 said:
On which rom is the phone(Android version) and which Twrp(link)?
Click to expand...
Click to collapse
I bought the device over a year ago.
NOSS8 said:
Are you sure of the version?
SELENE 21061119AG, 21061119AL, 21061119BI, 21121119SG, 21121119VL, 22011119TI
Not sure this TWRP works on A12, did you flash the VBmeta as shown on the link?
Click to expand...
Click to collapse
Just a moment
NOSS8 said:
Are you sure of the version?
SELENE 21061119AG, 21061119AL, 21061119BI, 21121119SG, 21121119VL, 22011119TI
Not sure this TWRP works on A12, did you flash the VBmeta as shown on the link?
Click to expand...
Click to collapse
Already did, but still not working.
And the phone won't restart?
NOSS8 said:
And the phone won't restart?
Click to expand...
Click to collapse
It restarts to Stock ROM.
Tried different ports, cables, disabled driver signature enforcement, CMD and PowerShell, many restarts, but still the same error that I am occurring.
{
"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"
}
NOSS8 said:
Are you sure of the version?
SELENE 21061119AG, 21061119AL, 21061119BI, 21121119SG, 21121119VL, 22011119TI
Not sure this TWRP works on A12, did you flash the VBmeta as shown on the link?
Click to expand...
Click to collapse
flashed different vbmeta.img
Download PlatformTools and put the Twrp in the folder and run all your commands from this folder.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
You must flash the VBmeta corresponding to the installed rom
My PC:
Device name: DESKTOP-K3DHSR3
Processor: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz 2.40 GHz
Installed RAM: 16.0 GB (15.9 GB usable)
Device ID: EC895DCA-D7C0-41EF-A114-8C0CD8F42698
Product ID: 00330-50316-52505-AAOEM
System type: 64-bit operating system, x64-based processor
Pen and touch: No pen or touch input is available for this display
Manufacter: Lenovo
NOSS8 said:
Download PlatformTools and put the Twrp in the folder and run all your commands from this folder.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
You must flash the VBmeta corresponding to the installed rom
Click to expand...
Click to collapse
O.K.
dasdsad1 said:
O.K.
Click to expand...
Click to collapse
I'll let you updated in a short moment.
I did, the vbmeta flash worked, but still no response on the fastboot boot twrpredmi10.img or any TWRP img.
Complete log: