For Android 12 and Android 13
twrp-3.7.0_12-v6.7_A13-ingres-skkk.img2023-01-10104.9 MBtwrp-3.7.0_12-v6.5_A12-ingres-skkk.img2022-11-13104.9 MB
Recovery for Xiaomi devices - Browse /ingres at SourceForge.net
List of relevant recovery in one place
sourceforge.net
Difference between A13 and A12? I mean, isn't recovery independent of android version?
JPMuller said:
Difference between A13 and A12? I mean, isn't recovery independent of android version?
Click to expand...
Click to collapse
Yes but you will be unable to flash A13 ROMs with A12 TWRP, I think.
niiiiikn said:
For Android 12 and Android 13
twrp-3.7.0_12-v6.7_A13-ingres-skkk.img2023-01-10104.9 MBtwrp-3.7.0_12-v6.5_A12-ingres-skkk.img2022-11-13104.9 MB
Click to expand...
Click to collapse
anyone with tutorials on how to flash custom recovery? TWRP's (unofficial) tutorial got me on fastboot loop. Thanks!
niiiiikn said:
For Android 12 and Android 13
twrp-3.7.0_12-v6.7_A13-ingres-skkk.img2023-01-10104.9 MBtwrp-3.7.0_12-v6.5_A12-ingres-skkk.img2022-11-13104.9 MB
Click to expand...
Click to collapse
When trying to boot into it, it is giving me the next error:
downloading 'boot.img'...
OKAY [ 5.325s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Bad Buffer Size)
finished. total time: 5.566s
JPMuller said:
When trying to boot into it, it is giving me the next error:
downloading 'boot.img'...
OKAY [ 5.325s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Bad Buffer Size)
finished. total time: 5.566s
Click to expand...
Click to collapse
You can refer to this: https://forum.xda-developers.com/t/how-to-move-from-miui-13-id-to-miui-14-xiaomi-eu-rom.4547941/
There's a comment where you can correctly flash custom recovery in F4 GT and other devices.. (great help!)
Apparently, you can't use fastboot boot command, you'll get that Bad Bufffer error
can someone help, recovery is installed but there is problem with touchscreen in recovery. System reboot is in bootloop. Help please.
stedroid said:
can someone help, recovery is installed but there is problem with touchscreen in recovery. System reboot is in bootloop. Help please.
Click to expand...
Click to collapse
Can you enter fastboot?
Related
Hey everyone!!
My device is stuck at boot logo.
If i try to open the recovery it also stuck on teamwin logo.
My device is totally unusable now.
please help!!
Thanks in advance.
shubhm said:
Hey everyone!!
My device is stuck at boot logo.
If i try to open the recovery it also stuck on teamwin logo.
My device is totally unusable now.
please help!!
Thanks in advance.
Click to expand...
Click to collapse
Try reflashing the TWRP recovery using fastboot. You can find the steps here.
LijoDXL said:
Try reflashing the TWRP recovery using fastboot. You can find the steps here.
Click to expand...
Click to collapse
Gives Mismatched partition size(recovery) error.
shubhm said:
Gives Mismatched partition size(recovery) error.
Click to expand...
Click to collapse
Mismatched partition size(recovery) should not be a problem, it just saying that your recovery is smaller in size than the stock recovery. Did you got this problem after downgrading from lollipop? As a trial and error thing, try to flash stock recovery and see if it boots.
LijoDXL said:
Mismatched partition size(recovery) should not be a problem, it just saying that your recovery is smaller in size than the stock recovery. Did you got this problem after downgrading from lollipop? As a trial and error thing, try to flash stock recovery and see if it boots.
Click to expand...
Click to collapse
Flashed stock recovery.
got this error in cmd
C:\Users\MOHIT\Desktop\ooo\mfastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.341s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.929s
and on booting in recovery same teamwin logo appears.
Try this command mfastboot flash partition gpt.bin (you must have the stock firmware in the directory)
shubhm said:
Flashed stock recovery.
got this error in cmd
C:\Users\MOHIT\Desktop\ooo\mfastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.341s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.929s
and on booting in recovery same teamwin logo appears.
Click to expand...
Click to collapse
try flashing whole stock 4.4.4 rom. and you didn't mention what you did (upgraded to lollipop/downgraded/ flashed any specific rom) which led to this problem.
zeshan94 said:
try flashing whole stock 4.4.4 rom. and you didn't mention what you did (upgraded to lollipop/downgraded/ flashed any specific rom) which led to this problem.
Click to expand...
Click to collapse
i had put my phone on charging. Then it itself got off. On pressing power button it was stuck on bootlogo.
I did a reset to factory using twrp with lollipop and the phone is stuck at moto logo... help please
LijoDXL said:
Mismatched partition size(recovery) should not be a problem, it just saying that your recovery is smaller in size than the stock recovery. Did you got this problem after downgrading from lollipop? As a trial and error thing, try to flash stock recovery and see if it boots.
Click to expand...
Click to collapse
i got the problem while downgrading from lollipop ...i tried flashing cm12.1 from 4.4.4 stock....but now i am stuck with the boot logo...help please!
Hi,
searched a lot of Threads but no one helped. is there an all in one Solution to get stock Firmware and Recovery back? I tried at last this one: https://forum.xda-developers.com/zenwatch-2/help/watch-update-failing-factory-image-t3573236 but as soon i try to reboot to twrp i get the Error
Code:
[email protected]:~# fastboot boot twrp-v3.0.0-0.jk-v3.recovery.img
downloading 'boot.img'...
OKAY [ 0.369s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.757s
So please help
Thanks in advance
no one?
Gesendrt aus der Tardis aus irgendeiner Zeit
Which model do you have? There's the WI501Q and WI502Q.
Lrs121 said:
Which model do you have? There's the WI501Q and WI502Q.
Click to expand...
Click to collapse
Ah sorry, its the "big" one WI501Q
KleinerKObold said:
Ah sorry, its the "big" one WI501Q
Click to expand...
Click to collapse
Try using this TWRP image. I keep it up to date so it might help you get through the guide.
http://lrsservers.org/downloads/devices/asus/sparrow/
Lrs121 said:
Try using this TWRP image. I keep it up to date so it might help you get through the guide.
http://lrsservers.ddns.net/download/devices/asus/sparrow/twrp-jenkins-sparrow.img
Click to expand...
Click to collapse
Thanks for the file but i coldnt get to twrp. as soon as i type
fastboot boot twrp-v3.0.0-0.jk-v3.recovery.img
i get the Errror
downloading 'boot.img'...
OKAY [ 0.369s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.757s
Is there a chance that i get the watch working again?
KleinerKObold said:
Thanks for the file but i coldnt get to twrp. as soon as i type
fastboot boot twrp-v3.0.0-0.jk-v3.recovery.img
i get the Errror
downloading 'boot.img'...
OKAY [ 0.369s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.757s
Is there a chance that i get the watch working again?
Click to expand...
Click to collapse
I'm not sure, it looks like they may changed something's in the boot that need addressing with twrp.
Lrs121 said:
I'm not sure, it looks like they may changed something's in the boot that need addressing with twrp.
Click to expand...
Click to collapse
Got it, i have to download another TWRP Image now i have my watch working again. But i nedd still a plain stock rom because i have still some that have dnot be there if i have a Stockrom (Advanced Settings and Wear Root check) but how do i get a stock rom?
KleinerKObold said:
Got it, i have to download another TWRP Image now i have my watch working again. But i nedd still a plain stock rom because i have still some that have dnot be there if i have a Stockrom (Advanced Settings and Wear Root check) but how do i get a stock rom?
Click to expand...
Click to collapse
https://forum.xda-developers.com/zenwatch-2/general/dump-zenwatch-2-sparrow-wi501q-build-t3578459
https://forum.xda-developers.com/zenwatch-2/general/m6e69n-twrp-backup-stock-boot-firmware-t3484961
Thread Closed
Thread Closed
Dude, this may work on the xt1772??
If no, you can port to it??
If you need something like the boot image, i can give upload one
Sorry for my english
hetor99 said:
Dude, this may work on the xt1772??
If no, you can port to it??
If you need something like the boot image, i can give upload one
Sorry for my english
Click to expand...
Click to collapse
No, its not working in XT1772.
Please upload your device recovery image & boot image here.
Francesco Franz said:
No, its not working in XT1772.
Please upload your device recovery image & boot image here.
Click to expand...
Click to collapse
https://drive.google.com/file/d/1jbSjLAMabwDar9tcc_VCSlPCNFVizWt1/view?usp=drivesdk
https://drive.google.com/file/d/1tKGXsT4qSkSoXj17Ur-QsdgsGtl1Fz_Q/view?usp=drivesdk
hetor99 said:
https://drive.google.com/file/d/1jbSjLAMabwDar9tcc_VCSlPCNFVizWt1/view?usp=drivesdk
https://drive.google.com/file/d/1tKGXsT4qSkSoXj17Ur-QsdgsGtl1Fz_Q/view?usp=drivesdk
Click to expand...
Click to collapse
Wait, until i upload a test version of twrp here?
After installing stock rom,i m not getting any info(shows null) on SKU in fast boot mode.please help
RagChith said:
After installing stock rom,i m not getting any info(shows null) on SKU in fast boot mode.please help
Click to expand...
Click to collapse
Me too, my device is the xt1772 and as you said, on the bootloader doesn't show any info, sku, model, imei and some other info, but the device is working well when it boot
---------- Post added at 06:47 PM ---------- Previous post was at 06:11 PM ----------
Francesco Franz said:
Wait, until i upload a test version of twrp here?
Click to expand...
Click to collapse
Sure guy, i will wait
@hetor99
You have to wait till this sunday.
Francesco Franz said:
@hetor99
You have to wait till this sunday.
Click to expand...
Click to collapse
It's fine dude, take your time
Im working on build LOS 14.1 for the mediatek variant, but i dont know how to build twrp
hetor99 said:
Me too, my device is the xt1772 and as you said, on the bootloader doesn't show any info, sku, model, imei and some other info, but the device is working well when it boot
Click to expand...
Click to collapse
Don't worry about it, it is kind of normal behavior in the fastboot mode
Sent from my Nexus 7 using Tapatalk
sir ............ can we flash using SP flash tool
rsmani1965 said:
sir ............ can we flash using SP flash tool
Click to expand...
Click to collapse
Yes, you can. But only when you have a working scatter file else use fastboot method.
#UPDATE
Click Here For TWRP Recovery For Moto E4 Plus XT1772 MediaTek Variant !
@Francesco Franz
Well, i think that the recovery is working fine, i tried the functios of wiping partitions like a factory reset and works, it detects the adoptable storage, the unique "bug" is when the recovery boot and stuck on black screen like on other variants.
I tried to take sc from all the options but i dont understand the lenguage that have the recovery pre-selected.
sorry for my english and any misunderstood
I get the following
PS C:\adb> fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13618 KB)...
OKAY [ 0.339s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 0.745s
Nothing changes in my phone i think.
Recovery mode is still the same No command with the dude on his back
DrunkenPanda2000 said:
I get the following
PS C:\adb> fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13618 KB)...
OKAY [ 0.339s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 0.745s
Nothing changes in my phone i think.
Boot to Recovery mode is still the same No command with the dude on his back
EDIT:
Apearantly i have a model 1762 And not 1772 Annyne got anny tips on how t proceed is this a fulitele task or will someone be a hero once again?
Click to expand...
Click to collapse
DrunkenPanda2000 said:
DrunkenPanda2000 said:
I get the following
PS C:\adb> fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13618 KB)...
OKAY [ 0.339s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 0.745s
Nothing changes in my phone i think.
Boot to Recovery mode is still the same No command with the dude on his back
EDIT:
Apearantly i have a model 1762 And not 1772 Annyne got anny tips on how t proceed is this a fulitele task or will someone be a hero once again?
Click to expand...
Click to collapse
Already mentioned its for xt1772 not xt1762.
Upload your device recovery and boot image. i will make one for you.
Click to expand...
Click to collapse
hetor99 said:
@Francesco Franz
Well, i think that the recovery is working fine, i tried the functios of wiping partitions like a factory reset and works, it detects the adoptable storage, the unique "bug" is when the recovery boot and stuck on black screen like on other variants.
I tried to take sc from all the options but i dont understand the lenguage that have the recovery pre-selected.
sorry for my english and any misunderstood
Click to expand...
Click to collapse
Its not a bug anymore since it takes few secs to enter into recovery mode. Black screen issue not at all. since you have a working twrp in your device. if theirs a black screen issue you will be on default recovery.
will fix the language bug soon.
@DrunkenPanda2000
That is because this section of xda is for the moto e4 plus, not the e4
the moto e4 already have twrp and to many roms on development
Hello,
I'm trying to do Flash TWRP Recovery, this is the error message i'm getting:
==========================================================
C:\adb>fastboot flash recovery twrp-3.2.3-0-pollux_windy.img
sending 'recovery' (11774 KB)...
OKAY [ 0.374s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.376s
==========================================================
Info:
Sony Xperia Z tablet (SGP311)
Android Ver. 5.1.1
Build 10.7.A.0.228
Bootloader is unlocked
Device is not rooted.
Is there a tutorial to make this work?
mcwheelz said:
Is there a tutorial to make this work?
Click to expand...
Click to collapse
There is no recovery partition on this device.
Look here.
Cannot boot into TWRP Recovery
Thanks for your reply. it worked!:victory:
I did the follwing steps:
- Root my SGP311 sony tablet (WiFi)
- backup the TA
- unlock bootloader
- install twrp version (twrp-3.3.0-0-pollux_windy.img)
- backup the current rom
- after installing the rom, ( lineage-15.1-20190429-nightly-pollux_windy-signed.zip) i cannot boot into twrp anymore to install the GAPPS
at startup i repeatedly press vol -/+ to access twrp recovery, but the recovery screen of lineageOS appears
I'm able to startup into LineageOS
Do you know a way to access TWRP recovery?
(i tried everyway, with vol up + power and vol down + power)
I hope you can help me! it's very frustrating
Rootk1t said:
There is no recovery partition on this device.
Look here.
Click to expand...
Click to collapse
mcwheelz said:
Do you know a way to access TWRP recovery?
(i tried everyway, with vol up + power and vol down + power)
I hope you can help me! it's very frustrating
Click to expand...
Click to collapse
If you installed TWRP to boot partition, no surprise it was overwritten after you flashed lineage-15-1....zip.
If you need TWRP to stay permanently, you need to flash it to FOTA partition, or use kernel from unofficial 15.1 thread with built-in TWRP.
Every time I wanna flash Rom files with fastboot or adb side load
System partition failed to flash
even I have tried fastboot enhanced tool but it states all .img file is not logical even .img for stock rom.
Before using MSM tool I haven't faced this kinds of problems but once my device stuck in qualcom crush dump mode and I have to use MSM tool to unbrick my device and after that I think my partition type have changed and I can not flash any kind of rom. Every time I got the following error:
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s]
Writing 'system_b' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
My bootloader is unlocked
I have searched a lot and didn't got any solution and there are many users they are also facing the same problem but didn't got any solutions.
Does anyone know how to fix this problem?
Use adb reboot fastboot instead of adb reboot bootloader
御坂19041号 said:
Use adb reboot fastboot instead of adb reboot bootloader
Click to expand...
Click to collapse
Fastboot working fine here no issue with fastboot.
nowshadalve1 said:
Every time I wanna flash Rom files with fastboot or adb side load
System partition failed to flash
even I have tried fastboot enhanced tool but it states all .img file is not logical even .img for stock rom.
Before using MSM tool I haven't faced this kinds of problems but once my device stuck in qualcom crush dump mode and I have to use MSM tool to unbrick my device and after that I think my partition type have changed and I can not flash any kind of rom. Every time I got the following error:
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s]
Writing 'system_b' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
My bootloader is unlocked
I have searched a lot and didn't got any solution and there are many users they are also facing the same problem but didn't got any solutions.
Does anyone know how to fix this problem?
Click to expand...
Click to collapse
maybe on the wrong version or wrong recovery
dfm000 said:
maybe on the wrong version or wrong recovery
Click to expand...
Click to collapse
I have tried to flash fastboot stock rom also.....
Everytime says partition not found or volume full.
Look at the screenshot
nowshadalve1 said:
I have tried to flash fastboot stock rom also.....
Everytime says partition not found or volume full.
Click to expand...
Click to collapse
which oxygen os version you are on
dfm000 said:
which oxygen os version you are on
Click to expand...
Click to collapse
It's oos 11.2.7.7
After using MSM tool this problem appears before I can flash custom rom without any issue.
nowshadalve1 said:
It's oos 11.2.7.7
After using MSM tool this problem appears before I can flash custom rom withoutwh
Click to expand...
Click to collapse
which rom you trying to install
nowshadalve1 said:
It's oos 11.2.7.7
After using MSM tool this problem appears before I can flash custom rom without any issue.
Click to expand...
Click to collapse
use msm tool again to start fresh. update to version 11.2.8.8 from settings after that. use the recovery included with the rom provider. all should work well
dfm000 said:
use msm tool again to start fresh. update to version 11.2.8.8 from settings after that. use the recovery included with the rom provider. all should work well
Click to expand...
Click to collapse
I have tried this process so many times but still not working.
I can't fastboot any system Img any fix?
Every time I wanna flash Rom img files with fastboot System partition failed to flash Invalid sparse file format at header magic Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s] Writing 'system_b' FAILED (remote: 'Partition not...
forum.xda-developers.com
Check the link he also facing same problem...
nowshadalve1 said:
I have tried this process so many times but still not working.
I can't fastboot any system Img any fix?
Every time I wanna flash Rom img files with fastboot System partition failed to flash Invalid sparse file format at header magic Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s] Writing 'system_b' FAILED (remote: 'Partition not...
forum.xda-developers.com
Check the link he also facing same problem...
Click to expand...
Click to collapse
https://t.me/OnePlus9ROfficial ask here
Finally I got the solution :
1. update the oos to 11.2.8.8 from system updater.
2. Then unlock the bootloader. -> fastboot flashing unlock
3. Then flash custom recovery -> fastboot flash recovery recovery.img
4.Then enable adb sideload.
5. Then flash rom using-> adb sideload rom.zip
( After 47% it will show an error msg but don't worry)
6. Then back to recovery and formate user data.(most important otherwise you will stuck in bootloop and have to use msm tool)
7. Then reboot to system.
Done.
Who will face this problem on future follow the steps.
Thanks to https://t.me/OnePlus9ROfficial
And also thanks you bro @dfm000
im unable to enter fastboot mode after updating to OOS 12... anyone facing this issue?
gohaaron said:
im unable to enter fastboot mode after updating to OOS 12... anyone facing this issue?
Click to expand...
Click to collapse
Yes I was facing this issue also...you have to rollback to oos 11.
nowshadalve1 said:
Yes I was facing this issue also...you have to rollback to oos 11.
Click to expand...
Click to collapse
i have... so r u saying i need to root from OOS 11? my phone got bricked just now i had to use Msmtool to reflash back to OOS 11... but ive updated back to 12
Yes currently you need to root from oos 11. I don't weather you can root your device from oos 12 or not.
Ask here: https://t.me/OnePlus9ROfficial
And using MSM tool there is no big deal with Android 12. You will flash your device in edl mode so everything will be fine.
nowshadalve1 said:
Yes currently you need to root from oos 11. I don't weather you can root your device from oos 12 or not.
Ask here: https://t.me/OnePlus9ROfficial
And using MSM tool there is no big deal with Android 12. You will flash your device in edl mode so everything will be fine.
Click to expand...
Click to collapse
ok ive joined thanks
gohaaron said:
ok ive joined thanks
Click to expand...
Click to collapse
If you wanna rollback from 12 to 11 can follow this article:
Steps to Downgrade or Rollback Oneplus 8, 8 pro, 8T & 9R from Stable OxygenOS 12 to OxygenOS 11
Oneplus user are not happy about changes done on OxygenOS 12 for Oneplus 8, 8 pro, 8T & 9R. Now users want to downgrade to Stable.
techibee.in
nowshadalve1 said:
If you wanna rollback from 12 to 11 can follow this article:
Steps to Downgrade or Rollback Oneplus 8, 8 pro, 8T & 9R from Stable OxygenOS 12 to OxygenOS 11
Oneplus user are not happy about changes done on OxygenOS 12 for Oneplus 8, 8 pro, 8T & 9R. Now users want to downgrade to Stable.
techibee.in
Click to expand...
Click to collapse
yes i follow him too... but i saw him enter fastboot with OOS 12